Xell - RGH1.2 Problems.

Nandcat841

Junior Member
Mar 31, 2017
10
0
So,

I wrote the xell image to my xbox.. after that I cannot seem to read or write to the nand.. Soldering is fine any suggestions?
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Did you write the write xell, if the smc included is for another console that could cause this issue. Also check the STBY_CLK area. if this is damaged, then it could cause this problem also.
 

Nandcat841

Junior Member
Mar 31, 2017
10
0
Did you write the write Xell, if the smc included is for another console that could cause this issue. Also, check the STBY_CLK area. if this is damaged, then it could cause this problem also.

thank you for your response.

I took like 6 NAND dumps before attempting anything.

I created the ECC with the NAND dump wrote it.. xell booted I then put the xebuild image I created on a USB and plugged it into my Xbox.. that finished and asked me to reboot (So I did) and now it won't glitch it just keeps attempting and sometimes red rings. I have checked STBY_CLK and all seems fine.

I will post the log for what it says when I try to read/ write to the NAND when I am home.

but before that any ideas? It's really bugging me as you can probably imagine. Its a £20 console so not the end of the world but would like to fix this.
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
You didnt unplug the power from the console after writing the nand image. lol. Always unplug console after writing, or else you end up with issues like this. It probably wont help now, as it appears that you probably corrupted the smc. easiest way to fix this that I know of, is to short 2 or 3 of the resistors together next to the nand, while you plug in the console, for about 3 seconds after power has been plugged in. then remove the bridge(Flathead screw driver works great), then try rewriting the nand image.
 

Nandcat841

Junior Member
Mar 31, 2017
10
0
I don't unplug every time after I write and have never experienced this issue. I dont think your claim is totally accurate.

The most likely answer to what went wrong is in the soldering and handling of components while working.
N

Nothing wrong with my soldering mate.

It stopped working after no changes to the soldering.
 

Nandcat841

Junior Member
Mar 31, 2017
10
0
post pics of install and chip and jr logs
Nand Initialization Finished
Retail Selected
Jasper 512MB Manually Selected
Device Not Found.
Jasper 512MB Manually Selected
Version: 10
Flash Config: 0x00000000
Can not Continue
Jasper 512MB Manually Selected
Version: 10
Flash Config: 0x00000000
Can not Continue

RGH1.2 Coolrunner REV C
https://ibb.co/ea7Rak
https://ibb.co/kwJoo5
https://ibb.co/jMoA1Q
https://ibb.co/hRvevk
https://ibb.co/iMhg85
https://ibb.co/eVz6ak
PICS^^
 

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Actually the coolrunner is not relevant, at this point in the install, as he is asking for help with presumably a nand-x / jr-programmer, which are also TX products. That is like saying we wont help you with a JTAG, because you didnt buy our QSB kit. Reality is, no one ever says that to someone with the same problem that didnt buy the jtag QSB kit. On top of that, on that logic, this forum should be dead, as you can no longer get non clone chips of the coolrunner. Which leave the CR4, and I havnt seen alot of them floating around out there lately either. Most chip manufactures have stopped producing product, their support sites have gone down, and our policy is dont help them, as they didnt buy the proper equipment, as they cant seem to get it anymore. lol. That is laughable. I seriously doubt that the only chips you guys install are TX chips. And if you do, you must have a backlog of them sitting on a shelf, just in case you cant get a console to glitch. lol.
 

playingmax

Staff member
Troll Eating Dogs
Actually the coolrunner is not relevant, at this point in the install, as he is asking for help with presumably a nand-x / jr-programmer, which are also TX products. That is like saying we wont help you with a JTAG, because you didnt buy our QSB kit. Reality is, no one ever says that to someone with the same problem that didnt buy the jtag QSB kit. On top of that, on that logic, this forum should be dead, as you can no longer get non clone chips of the coolrunner. Which leave the CR4, and I havnt seen alot of them floating around out there lately either. Most chip manufactures have stopped producing product, their support sites have gone down, and our policy is dont help them, as they didnt buy the proper equipment, as they cant seem to get it anymore. lol. That is laughable. I seriously doubt that the only chips you guys install are TX chips. And if you do, you must have a backlog of them sitting on a shelf, just in case you cant get a console to glitch. lol.
I asked for a pic of the cr to see how its wired up :redface:
 

L2000

VIP Member
Mar 8, 2011
271
33
Cape Town
Is the console connected to a power source? Disconnect glitcher then try hitting up the nand read points bottom side of the board see if you get it to read , failing that I would try shorting pins on the nand to get a read , I've only ever had to do this once though and it was on the same trinity that wouldn't read nand from topside of the board. J-Runner auto remaps bad blocks (or at least that's what it does on my rig) , so bad blocks although not impossible are very uncommon to be written back to console when using this programme. Normally when I had bad blocks written to a fat console back when we used Nand Pro it would give me XMas lights and Jet engine fans if image wasn't built correctly and Nand wasn't fully erased before write. Your thick red wire looks like it's bridging 7-9 double check that or just retouch up the point.Hope this helps you.
 
Last edited:

gavin_darkglide

VIP Member
Dec 14, 2012
2,303
118
Is the console connected to a power source? Disconnect glitcher then try hitting up the nand read points bottom side of the board see if you get it to read , failing that I would try shorting pins on the nand to get a read , I've only ever had to do this once though and it was on the same trinity that wouldn't read nand from topside of the board. J-Runner auto remaps bad blocks (or at least that's what it does on my rig) , so bad blocks although not impossible are very uncommon to be written back to console when using this programme. Normally when I had bad blocks written to a fat console back when we used Nand Pro it would give me XMas lights and Jet engine fans if image wasn't built correctly and Nand wasn't fully erased before write. Your thick red wire looks like it's bridging 7-9 double check that or just retouch up the point.Hope this helps you.
Auto remapping doesnt always happen with ecc, as they are pre-compiled, and then have the KV injected into them. No remaping done there. Now the image that you create using your nand dump will be remapped.
 

L2000

VIP Member
Mar 8, 2011
271
33
Cape Town
I was referring to his written image after he booted xell , he said he wrote an Xebuild image to nand and after that he couldn't get it to read or write again. If nothing got damaged and his soldering is correct he should be able to re access his nand.
 

Nandcat841

Junior Member
Mar 31, 2017
10
0
Is the console connected to a power source? Disconnect glitcher then try hitting up the nand read points bottom side of the board see if you get it to read , failing that I would try shorting pins on the nand to get a read , I've only ever had to do this once though and it was on the same trinity that wouldn't read nand from topside of the board. J-Runner auto remaps bad blocks (or at least that's what it does on my rig) , so bad blocks although not impossible are very uncommon to be written back to console when using this programme. Normally when I had bad blocks written to a fat console back when we used Nand Pro it would give me XMas lights and Jet engine fans if image wasn't built correctly and Nand wasn't fully erased before write. Your thick red wire looks like it's bridging 7-9 double check that or just retouch up the point.Hope this helps you.

Thank you for your comment bro, I will detach the chip and then try it if not can you give me a link to the alternate NAND points? really appreciate your help without criticism.
 

L2000

VIP Member
Mar 8, 2011
271
33
Cape Town
The points are on exactly the same places on the bottom of the board , use a marker next to points just to be certain that you connecting the correct colour wire to the correct point , easy to confuse as locations are either in reverse or upside down when doing it this way. Take your time when doing the soldering and use lots of flux , and be sure to keep your wire ends short as possible and your soldering iron's tip clean.