Nand dump random reads(V3) Should i continue with RGH?

dmind

Junior Member
Dec 27, 2012
16
0
Hi all!
So i installed my qsb and tried dumping my nand with j-runner (287).
First time didn't work. Suspected bad soldering on r2c6 r2c7 resistors. Fixed it.
Second time worked like a charm! 2 nand reads exactly the same!
After moving nands to safe place on pc, i tried again to check the stability of the qsb install by dumping nand again.
Only once i managed to get a successfull read of nand (2nd read gave me errors).

This is what i get:
-----------------
Connection Error
Filechecks disabled - No Filechecks carried out
Version: 03
Flash Config: 0x00043000
CB Version: 13181
Corona
Reading Nand to C:\Users\Administrator\Downloads\J-Runner v02 Beta (284) Core Pack (1)\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Can not Continue
------------------------
or
------------------------
Connection Error
Filechecks disabled - No Filechecks carried out
Version: 03
Flash Config: 0x00043000
CB Version: 13181
Corona
Reading Nand to C:\Users\Administrator\Downloads\J-Runner v02 Beta (284) Core Pack (1)\J-Runner v02 Beta (284) Core Pack\J-Runner v02 Beta (284) Core Pack\output\nanddump1.bin
Reading Nand
Error: 000 reading block 0
Error: 000 reading block 1
Error: 000 reading block 2
Error: 000 reading block 3
Error: 000 reading block 4
Error: 000 reading block 5
Error: 000 reading block 6
and so on...
-------------------------
or sometimes it doesn't even auto recognize my MB type (have to select it)

the errors seem to vary when i disconnect/reconnect power supply on xbox.
The qsb install seems good to me...

What do you guys think?
Since i've already managed to get the nand dump without errors,is it ok to proceed with the rgh process?

Thank you in advance
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
You have far too much solder on those points.

Look at the left area - you almost have points touching there.

Get some desoldering braid and remove a lot of that.
 
  • Like
Reactions: dmind

TheGlichter

Full Member
Dec 8, 2011
97
8
Europe
If you get the same error reading again with this or another mobo try to twist the wires from the NandX connector and see if it starts reading normally. Mine NandX came with two wire sets for heavy use;) It came well in handy
 
  • Like
Reactions: dmind

dmind

Junior Member
Dec 27, 2012
16
0
everything is new...
thanks for replies. i really didn't notice those points on the left. i will fix it even though i think they aren't touching.

thank u very much
 

dmind

Junior Member
Dec 27, 2012
16
0
well i tried it and i get the feeling that when reading nand for first time (after a while without touching it) all goes well. the following attempts always give me those errors.

Is it supposed to read nand successfully everytime i click read nand?
(it's a v3 with missing resistors)

Couldn't it be a j-runner problem?

tu
 
Last edited:

dmind

Junior Member
Dec 27, 2012
16
0
i've done it. now it works everytime.
apart from getting solder points away from each other
the best advice i can give in this situation is be sure to solder deep into those holes on the motherboard (not just superficially). it's important to get fresh solder to flow through those points.

Tks everyone
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
i've done it. now it works everytime.
apart from getting solder points away from each other
the best advice i can give in this situation is be sure to solder deep into those holes on the motherboard (not just superficially). it's important to get fresh solder to flow through those points.

Tks everyone
You're welcome - it was nothing to do with the 'depth' of the solder, as it's metallic and conductive. The problem, as with 95% of the issues we see is is the soldering was not sufficiently done to complete the job.
 
  • Like
Reactions: nofeloniesyet