Strange problem

[andynov123]

I am trying to rgh a jasper 16mb. I read the nand twice and got matching blocks. Then used multibuilder .3 and I couldn't get any green flash. I then used multibuilder .2 after exhausting all other options and sure enough I got green light flashing. Unfortunately it wouldn't glitch, but rather it would just keep flashing. The xbox logo never appeared and neither did any rrod. It was like in some sort of limbo mode. So I decided to flash back to original nand and all was well. I did some other things here and there (can't remember exactly) and nothing was working so I decided to flash back to original nand again and re read nand. I did this twice and verified and it was ok.

Then comes the strange part, I used jtag tool to build a new ecc from the second pair of nand reads but it just hung after about 7 lines from the very beginning of script. So since that didn't work I tried multibuilder .2 and .3 and both resulted in same thing.

So I flashed back to original nand again with the second read and it started to go to that limbo state again (it was flashing probably because I didn't have drive plugged in). So out of curiousity I compared the first read to the second pair of reads and they were different (by over 100 blocks). I read the nand again and compared with the first one and it was off by 3 blocks. So I tried making image from original reads and it still goes to that limbo mode after it finally lets me generate ecc and write. Not sure why it won't work. Anyone have a similar issue?

 

[diaboliq20]

if you have booted the console after the NAND dumps - the nand will have changed

 

[dannyperez]

"I got green light flashing. Unfortunately it wouldn't glitch, but rather it would just keep flashing" this is something thats has happened to many people including me, if you have it in its metal casing remove it and try booting it up while moving the CPU_RST wire around, this seems to be problem with allot of people from what I've read on this forum and others.

 

[esbmaepo]

I am trying to rgh a jasper 16mb.

Post some close up pictures of your wiring.

 

[andynov123]

i used nandx to read xbox twice and they matched so that is my original nand
but i had problems getting glitch to work so i reread the nand thinking i would start the process over from the very beginning and when I reread the nand I got 0 non-matching blocks again so I thought I was ok
then whenever I tried to use those nand files it would not allow me to create .ecc file for some reason, it would just hang onscreen with attempt using jtag tool and nandpro. Then after several attempts the .ecc file wrote (not sure what I did).
At this point with the ecc in and the coolrunner hooked up I booted up the xbox but it went in some type of limbo mode where it wouldn't boot but the green light just flashed (the dvd drive was not hooked in).

So I put it back to original with the 2nd pair I read and it went to a limbo mode again
So out of curiousity i compared the first pair with the second and they don't match
So then i flashed with the 1st pair and then it booted
now what I'm doing is a test on another xbox where ialready read the nand before this craziness and now it's doing it again where i have 0 nonmatching blocks but those blocks don't match with the 1st time I did it. I reset my nandx and now it's giving me even different readings than the first 2 pairs! Is my nandx bad or what?

 

[andynov123]

if you have booted the console after the NAND dumps - the nand will have changed

How will the nand change? I thought it was like a dvd/cpu key where it is always the same (unless flashed to something different of course)

Even if that were the case, how could that explain that limbo mode with the second pair of nands I read. I don't know how that happened but if I didn't have the original nand reads I would have been in trouble. From what you say that would explain why the two pairs aren't matching but not the limbo part.

EDIT: I just tested it and you're right it does change on boot. So I'm guessing that it only changes non important stuff since when you read the nand for safekeeping it could easily change slightly just from booting it once more. That whole limbo thing is still bothering me though.

 

[mocalacace]

How will the nand change? I thought it was like a dvd/cpu key where it is always the same (unless flashed to something different of course)

Even if that were the case, how could that explain that limbo mode with the second pair of nands I read. I don't know how that happened but if I didn't have the original nand reads I would have been in trouble. From what you say that would explain why the two pairs aren't matching but not the limbo part.

EDIT: I just tested it and you're right it does change on boot. So I'm guessing that it only changes non important stuff since when you read the nand for safekeeping it could easily change slightly just from booting it once more. That whole limbo thing is still bothering me though.

I have the same damn problem, but with a falcon. Have you tried positioning the wires differently?

If you somehow manage to get it to work let me know and post what you did because mine won't boot xell and I've tried everything