100%, there is nothing I could of messed up, all the points are easy and it's a really simple install. Hawk
it may be pulling to much power away from the gpu causing the problem double check your soldering, and disconnect the mod just to double check u didnt kill your board
Ok so I got a nand from someone else patched in my encrypted config and kv, then wrote it to the console it just RROD on me. Then I just wrote my nand back and turned it on and it booted right up. I then unplugged it and tried to turn it back on and it doesn't boot. So something veru weird is going on. I'm a try to repeat that later and see if I can get it to boot again. More info if I turn it on, then unplug the video cable, then replug it it will boot every time, any ideas? Hawk
What do you mean, when it don't boot? The attack can take time to do it's, thing. also do you want the rebooter on it? As i got a theory.
I'm talking about my jasper big block, I've finally got it back working although sporadically. But at least it is booting, probably once a dashboard update comes out and I can update it it will work as it should again, or once I try the hack on it again. I have not been able to get any phats to boot xell with the reset glitch. I've only had success with the slims on the reset glitch. So I'll have to wait to test any rebooters for phats at the moment. I'm supposed to be getting in a bunch of different chips this week, and I'll use them to try to get it to boot xell. Hawk
Yup, and I've even had other people build it for me now that I have failed the past couple of days. And those do not boot either so I has to be something in my wiring, I've got the cmod programmed correctly, and have r2 removed, and r3 bridged and still no Xell on a Zephyr or a Jasper. So I'm not sure what the problem can be other then the wiring but I've checked it countless times and it looks right to me, so I don't know what else to do. Hawk
Already did buddy, take a look at post #35. I just want to say I've never had this big of a problem with a hack/mod/glitch ever, the first jtag only took like a couple hours to figure out, the slim was complete and working on the first try. So I do not know whats wrong. Both Consoles where at 13599, but that should not matter, at least for now. Hawk
yeah I used The Reset Glitch Hack_Xbox360FAT_Tutorial_V1.1_EN to double check everything. Unless they have added a new file to flash to the cmod that I do not know about, as long as the first one is still the correct one, everything is up to date. The only thing different is I grounded the shield instead of the copper on the bottom of the board. Hawk
Did you remove the R2 resistor, short the R3, have a 22k resistor, 3 1N4148 diodes, a 1k resistor, and a 100n cap. for the phats. Wait for the mod chips so the correct resistors and connections are in place.
Yeah all those are right. It could be a problem with the cb verison that I've been looking for more info about it and for jaspers cb version 6750 are confirmed as working, but I haven't heard anything about 6751. Hawk
ahhh i know the problem now you need to downgrade ur 6751 down to 6750 there will be a fix very soon im told by the guys over at #libxenon edit: just found this http://do.not.emailmehere.com/aide-necessaire.html
So just an update, I have not been able to get either the jasper or zephyr to boot xell. I was sent some tracking info earlier for some of the new mod chips, I guess they will get their test in these consoles. I'll be doing my other slim that I use for live, but really just to get the KV info incase it ever dies I can clone it. It's all stock no DVD mods, and for that fact it's never even been opened. So hopefully my first slim wasn't a fluke. As for the jasper it sill boots randomly and so it still has some issues, but hopefully the next dashboard update or the mod chips will fix it, that is if the cb timings are figured out. Hawk