The console works fine with the stock NAND, you would have to be retarded to try a new mod on a RROD console. However it has been said many times that some RROD console will boot xell. This however is not one of those it is on the current 13599 dash and works fine when stock. And yes I'm reprogramming the CPLD every time I switch consoles. Correct, with I try to glitch it it RROD's when it's stock it's fine. Weird the slim I got first try and it boots most of the time in under 10 seconds. I've had no problem with the slims, it's just the phats. Thanks for the no help, so I'll do the same I could tell you but I just really want to get the console working. Also I've since found that the cmod wiring was wrong I had to disconnect r1 to r2, and then bridge r3. I've done that. Bestpigs ECC glitch generator is the problem for phats as it doesn't use the new build.py. It does however work fine with slims. I've installed python and build the new .ecc but still have the same problems with the consoles not glitching. I just really want to know what the problem is before all the chips start comeing out. I mean I got it work on the slim which was my main goal, but I just wonder why it doesn't work on the others. Hawk
The reason some RROD system boot xell, as the kernal is loaded and E** errors are from Xam.xex, 3 ring errors are stop before the kernal is loaded and will not boot xell. also sent PM for phat systems stuff.
I actually find this problem interesting. There have been several times in which the assembling of an Xbox 360 console causes it to error, yet when disassembled, it works flawlessly. Any idea why?
it was a damaged cable in the end i made sure to tape it like a bitch second time round to stop any thing getting damaged tested it for a few hours seems fine now i put the mod board in the gap between the mobo and chassie this time and used double sided foam tape to secure it. hopefully the console will still work when it gets to australlia
Let me know, and for the he*l of it, for sh*t and giggles, lets try make a Freeboot image for the new exploit for phats, as a theory.
Well progress with your build.py on the zephyr, it sill did not boot, but it did not go RROD. I'm about to try it now with the jasper, just to see if it's more suited for jaspers. Well the jasper doesn't work either, I have no idea what is going on or why they will not work, but as far as I can tell everything is right. Hawk
I picked up some ribbon cable like that in a hobby shop, in the model train section, although a little less festive colors. The sold it by the foot
I was using python common/imgbuild/build.py zephyr.bin common/cdxell/CD common/xell/xell-gggggg.bin I'm about to try python common/imgbuild/build.py zephyr.bin common/cdxell/CDjasper common/xell/xell-gggggg.bin Since you said that thanks, i'll let you know. And yes this is for a zephyr first, I'll do try the jasper after. Edit, Same result with both. Now with the jasper I tried to write the original back, and it RROD's to 0022. I've got 3 complete nand dumps of 512mb, they all match, and 1 64mb dump and none of them will seem to boot the console to stock. Hawk
are you writing the image like +w like they asked? and to return the orginal image, you have to erase the nand and write back normaly, as that happend to me before. Edit: don't know if BB jaspers are supported.
Yeah I'm using +W and bb jaspers are supported a couple people on Xbox scene have stated that they have them going. And I will erase then rewrite later today as I'm in the bed now. It just takes like an hour to write the full image. I have followed all the info that I have been given and still have had no luck with the phats. My slim was simple, it worked first try and has worked every time since, I just cannot seem to get the phats to work. I'm going to redo the socket wiring later today and see if maybe it's just a bad part in there or something, as that's really the last thing I can think of. Hawk
Hawk, use -w to write your original back to the jasper. If you do a full erase first, and if you didn't have anything in the nand MU that you want it's sufficient to write only the 64M dump.
Yeah I'm erasing and flashing it back now. I'll let yall know what happens. I'm going to redo the socket today, and if that doesn't work, I'll just wait for some of the mod chips to get here and use them. Hawk
The hack wont red ring nor do the smc lights as it is loaded from the hacked CD, thus either it is doing the hack and takeing time or it is the clock fault. Clock = coolrunner chip. also use a level shifter to get debug info.
Well after erasing then writing back the console still goes RROD. nothing is connected besides wires. So I guess now I'll have to wait until I can get the CPU key and make a donor nand. Even though all 3 of mine match, there is no reason for it not to work. Hawk
Im guessing you use a USB nand reader. I never had any nand issue, as long the mod chip is not connected nor powered, the system should boot.
Yeah the NAND-X, and this is the first time I've ever had any issues with the console not accepting the stock nand back. Hawk