RGH Bad nand flash

A

arpsachin2

Full Member
Feb 12, 2007
29
0
Okay so I got the RGH to work. I even got it to boot freeboot. I turned it off and turned it on again and it took like 5 secs.

I tried doing it again but this time it took a while but nothing happened, so I did some research and read that reflashing the nand would help.

I tried that using Jtag Tools but to my dismay, it kept on giving me errors (like errors after every block) and now I can't read/write ANY nand.

:mad2:
 
A

arpsachin2

Full Member
Feb 12, 2007
29
0
keil423 said:
what kind of console is it? When you got it to glitch the first time no trouble was it out of the metal frame? When it started to give errors was it after you put it back in the case and all back together?
Click to expand...
slim and it was in the whole frame the whole time
 
Last edited:
A

arpsachin2

Full Member
Feb 12, 2007
29
0





---------- Post added at 01:34 ---------- Previous post was at 01:33 ----------

Software - I tried using both JTAG tool and Nandpro but both will sometime read the nand. As far as writing goes, it starts giving error from the 1st block itself.
 
A

arpsachin2

Full Member
Feb 12, 2007
29
0
keil423 said:
those pics are so tiny! I cant see a damn thing
Click to expand...
click on it. It will take you to the zoomed in version


BTW-

THis is the error message:


NandPro v3.0a by Tiros

Looking for usb interface device
usb_bulk_read failed -116
Incompatible ARM firmware for this version of NandPro!
usb_bulk_read failed -116
Flash Config: 0x00413787
Block Size: 16KB Block Limits: 0x000000..0x0003FF
File: FreeBOOT.bin
Writing
usb_bulk_read failed -116
Error:74A298DA Programming block 0
usb_bulk_read failed -116
Error:74A298DA Programming block 1
usb_bulk_read failed -116
Error:74A298DA Programming block 2
usb_bulk_read failed -116
Error:74A298DA Programming block 3
usb_bulk_read failed -116
Error:74A298DA Programming block 4
usb_bulk_read failed -116
Error:74A298DA Programming block 5
usb_bulk_read failed -116
Error:74A298DA Programming block 6
usb_bulk_read failed -116
Error:74A298DA Programming block 7
usb_bulk_read failed -116
Error:74A298DA Programming block 8
usb_bulk_read failed -116
Error:74A298DA Programming block 9
usb_bulk_read failed -116
Error:74A298DA Programming block A
usb_bulk_read failed -116
Error:74A298DA Programming block B
usb_bulk_read failed -116
Error:74A298DA Programming block C
usb_bulk_read failed -116
Error:74A298DA Programming block D
usb_bulk_read failed -116
Error:74A298DA Programming block E
usb_bulk_read failed -116
Error:74A298DA Programming block F
usb_bulk_read failed -116
Error:74A298DA Programming block 10
usb_bulk_read failed -116
Error:74A298DA Programming block 11
0012
Click to expand...
 
Last edited:
S

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Looks more like a NAND flasher problem than a CoolRunner prob. Try unplugging and replugging your nand-x from USB. Or press the reset button with a paperclip.

Edit: Can you read the nand without those errors?

Edit2: Looking over your pics again, I did notice that a few of your points for the QSB did not fully "wet" the pads on the motherboard (can still see copper). A little touch-up with flux might help.
 
Last edited:
BL4K3Y

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
I see you are using the QSB.....

Re-check your soldering, this has nothing to do with the CoolRunner (it may be bad soldering on the QSB preventing the CoolRunner from operating properly).
 
A

arpsachin2

Full Member
Feb 12, 2007
29
0
srt4fun said:
Looks more like a NAND flasher problem than a CoolRunner prob. Try unplugging and replugging your nand-x from USB. Or press the reset button with a paperclip.

Edit: Can you read the nand without those errors?

Edit2: Looking over your pics again, I did notice that a few of your points for the QSB did not fully "wet" the pads on the motherboard (can still see copper). A little touch-up with flux might help.
Click to expand...
Tried resetting it many times. It reads sometimes and then sometimes it doesn't..
Okay will try that

blakey8 said:
I see you are using the QSB.....

Re-check your soldering, this has nothing to do with the CoolRunner (it may be bad soldering on the QSB preventing the CoolRunner from operating properly).
Click to expand...
But see the problem - I was able to dumb the nand once, flash the ecc and flash the nand.

But when I tried again, thats when the error came up
 
BL4K3Y

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
If it was a "dodgy" solder connection, it's possible that it came loose if the console was knocked or moved at all.

It doesn't hurt to rule out all the possibilities, the process of elimination works every time :).
 
I

ishockin

VIP Member
Feb 4, 2011
275
23
Ohio
Did you update your NAND-X to 3.0 as you are using nand pro v3 and it gives you an error incompatible arm version
 
A

arpsachin2

Full Member
Feb 12, 2007
29
0
blakey8 said:
If it was a "dodgy" solder connection, it's possible that it came loose if the console was knocked or moved at all.

It doesn't hurt to rule out all the possibilities, the process of elimination works every time :).
Click to expand...
Yup. Just checked it again.

The fact that I was able to erase it ALL again (just a min go) means that its all intact.

I was even able to write it till "156" after that each block started getting ERROR 0 block 156 and so on

---------- Post added at 09:21 ---------- Previous post was at 09:20 ----------
ishockin said:
Did you update your NAND-X to 3.0 as you are using nand pro v3 and it gives you an error incompatible arm version
Click to expand...
Yes. I was able to get it to boot freeboot too. I dont know why it says incompatible arm

---------- Post added at 09:22 ---------- Previous post was at 09:21 ----------

I reallly don't think it's the soldering problem.

I was able to get it too boot Xell, get the CPU key and flash the nand image means the soldering is pretty good. Even then I double checked everything.
 
You must log in or register to reply here.