Here's the following information about the console before the description, pictures and logs:
I have a Falcon which does not want to boot to XeLL with either R-JTAG+ or RGH2+. I have followed the guides in this forum carefully, and it just won't boot. I have checked all my joints, and they are all nicely soldered onto the correct points. Each point has been tested with a multimeter, also to see if there were any shorts. Flux was also used, and I also tried resoldering.
I have made successful dumps of the NAND 3 times (all identical according to the hashes), and when I first did RGH2+, I chose RGH2 and checked CR4. This created the ECC. I wrote this ECC to the NAND. This is where I cannot boot XeLL. I then tried the FALCON_CR4.ECC file in the common file folder from J-Runner, but this did not work either. I even tried other ECC files as well after writing back stock NAND, but this did not work (Even unchecked CR4 just for the hell of it). The NAND does have a bad block in the first 50 blocks, but I can see in the J-Runner log that this gets fixed automatically, where the 0x39 block gets moved to 0x3FF. I even tried to fix this manually by following Martins tutorial, but this did not work either. I can easily write back the stock nand, disable CR4 by removing 5V point, and then the console works perfectly again.
I then proceeded to try the dip switch settings, as mentioned in the installation thread. None of the combinations I tried would work. The jumper to set either 10 ohm or 100 ohm did not work either. I even tried to choose slim just to try, but this of course did not work either.
After messing a few hours with this, I just didn't come any further. It was the exact same results in the rater console. Then I tried with R-JTAG+, and switched the dip switch settings and wires accordingly. I did not have a QSB, so I followed a tutorial on how to solder the diodes and wires without the QSB. The tutorial I used can be found here:
The diodes I used were 1N4148. After setting it all up, I then proceeded to write back stock NAND again and check everything worked, which it did. Then I activated the CR4 again and wrote the falcon aud_clamp.bin file, which generated after checking JTAG, then R-JTAG and then aud_clamp. This did not work sadly, so the console does pretty much the same as the RGH2+ setup.
I have afterwards set the whole CR4, nand, ECC and wires back to RGH2+. I then tried again, but it did not work sadly.
I have since then written back stock NAND. One thing I noticed however, was that I could boot stock NAND even with the CR4 Running. It also ran as usual when trying to boot. I had before added a cap and had some other settings, where it did not want to boot. Then I set back the default dip switches and removed the cap. This then made the CR4 glitch once or twice and then boot stock NAND. So could it be that the ECC files and perhaps the bad blocks are somehow the culprit???
I have a JR-Programmer V2, and I use it with the rater feature. The log does not seem to show any great progress. This is how the logs pretty much proceed when doing the RGH2+. The same text showed after trying 50-100 glitches:
This occurs when doing the R-JTAG, also about 50-100 glitches:
Here's pictures of some of the soldering from RGH2+:
https://www.dropbox.com/s/blu6t02u56obfvk/2015-08-01 18.06.53.jpg?dl=0
https://www.dropbox.com/s/ow9kyiav0nilskf/2015-08-01 18.00.49.jpg?dl=0
https://www.dropbox.com/s/tg118386n00bneh/2015-08-01 18.00.23.jpg?dl=0
This was a quick picture I took of the the soldering on the CR4 with R-JTAG wires:
https://www.dropbox.com/s/7kze5q1csvl9qcc/2015-08-01 17.45.04.jpg?dl=0
I am pretty much giving up on why it won't boot, but I am starting to suspect that the CR4 may be broken. If anyone has some ideas or suggestions, then I would really appreciate it. Thanks!
- Console Type: Falcon
- Programmer Used: JRP v2.0
- NAND Size: 16MB
- Dashboard version: 17349
- CB Version: 5774
- Screenshot of NAND details from J-Runner: Added to post
- J-Runner log
- Image of the CR4 XL: Added to post
- Images of close-up soldering to motherboard: Added to post
- Detailed Description of the Problem: Added to post
- Was the console working before you started: Yes
- Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Around 6-7 seconds.
- How long is the light on for each time: About half a second. Regular and stable debug blinks.
I have a Falcon which does not want to boot to XeLL with either R-JTAG+ or RGH2+. I have followed the guides in this forum carefully, and it just won't boot. I have checked all my joints, and they are all nicely soldered onto the correct points. Each point has been tested with a multimeter, also to see if there were any shorts. Flux was also used, and I also tried resoldering.
I have made successful dumps of the NAND 3 times (all identical according to the hashes), and when I first did RGH2+, I chose RGH2 and checked CR4. This created the ECC. I wrote this ECC to the NAND. This is where I cannot boot XeLL. I then tried the FALCON_CR4.ECC file in the common file folder from J-Runner, but this did not work either. I even tried other ECC files as well after writing back stock NAND, but this did not work (Even unchecked CR4 just for the hell of it). The NAND does have a bad block in the first 50 blocks, but I can see in the J-Runner log that this gets fixed automatically, where the 0x39 block gets moved to 0x3FF. I even tried to fix this manually by following Martins tutorial, but this did not work either. I can easily write back the stock nand, disable CR4 by removing 5V point, and then the console works perfectly again.
I then proceeded to try the dip switch settings, as mentioned in the installation thread. None of the combinations I tried would work. The jumper to set either 10 ohm or 100 ohm did not work either. I even tried to choose slim just to try, but this of course did not work either.
After messing a few hours with this, I just didn't come any further. It was the exact same results in the rater console. Then I tried with R-JTAG+, and switched the dip switch settings and wires accordingly. I did not have a QSB, so I followed a tutorial on how to solder the diodes and wires without the QSB. The tutorial I used can be found here:
Code:
http://forum.coolshrimpmodz.com/forum/xbox-360-discussion/team-xecuter-product-support/cr4-xl-support/136-r-jtag-install-diagrams-wire-onlyThe diodes I used were 1N4148. After setting it all up, I then proceeded to write back stock NAND again and check everything worked, which it did. Then I activated the CR4 again and wrote the falcon aud_clamp.bin file, which generated after checking JTAG, then R-JTAG and then aud_clamp. This did not work sadly, so the console does pretty much the same as the RGH2+ setup.
I have afterwards set the whole CR4, nand, ECC and wires back to RGH2+. I then tried again, but it did not work sadly.
I have since then written back stock NAND. One thing I noticed however, was that I could boot stock NAND even with the CR4 Running. It also ran as usual when trying to boot. I had before added a cap and had some other settings, where it did not want to boot. Then I set back the default dip switches and removed the cap. This then made the CR4 glitch once or twice and then boot stock NAND. So could it be that the ECC files and perhaps the bad blocks are somehow the culprit???
I have a JR-Programmer V2, and I use it with the rater feature. The log does not seem to show any great progress. This is how the logs pretty much proceed when doing the RGH2+. The same text showed after trying 50-100 glitches:
Code:
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Shutdown
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Post 7E
Post FD
Post F5
Post F4
Post F0
Post 70
Post 50
Post 10 - ......
Post 06 - ....
Post 01 - .
Post 03 - ...
Post 04 - BOOT SEQUENCE STARTING
Post 05 - ...
Post 06 - ....
Post 07 - .....
Post 08 - ......
Post 09 - .......
Post 0A - ........
Post 0B - .........
Post 0C - ..........
Post 0D - GLITCH CHECK COMMENCE
Post 03 - ...
Post 04 - BOOT SEQUENCE STARTING
Post 05 - ...
Post 06 - ....
Post 07 - .....
Post 08 - ......
Post 09 - .......
Post 0A - ........
Post 0B - .........
Post 0C - ..........
[B][B][B][B]Post 0D - GLITCH CHECK COMMENCE [/B][/B][/B][/B]This occurs when doing the R-JTAG, also about 50-100 glitches:
Code:
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Post 01 - .
Post 05 - ...
Post 06 - ....
Post 07 - .....
Post 08 - ......
Post 09 - .......
Post 0A - ........
Post 0B - .........
Post 0C - ..........
Post 0D - GLITCH CHECK COMMENCE
Post 01 - .
Post 0D - GLITCH CHECK COMMENCE
Post 15 - CONTINUING
Post 16 - .
Post 17 - ..
Post 18 - ...
Post 1A - .....
Post 1B - ......
Post 1C - .......
Post 1D - ........
Post 1E - .
Post 1F - ..
Post 20 - ...
Post 21 - ....
Post 22 - .
Post 23 - ..
Post 24 - Entrypoint reached
Post 25 - ...
Post 01 - .
Post 03 - ...
Post 04 - BOOT SEQUENCE STARTING
Post 05 - ...
Post 06 - ....
Post 07 - .....
Post 08 - ......
Post 09 - .......
Post 0A - ........
Post 0B - .........
Post 0C - ..........
Post 0D - GLITCH CHECK COMMENCE
Post 01 - .
Post 15 - CONTINUING
Post 16 - .
Post 17 - ..
Post 18 - ...
Post 19 - ....
Post 1A - .....
Post 1B - ......
Post 1C - .......
Post 1D - ........
Post 1E - .
Post 1F - ..
Post 20 - ...
Post 21 - ....
Post 22 - .
Post 23 - ..
Post 24 - Entrypoint reached
Post 25 - ...
[B][B][B][B]Post 01 - . [/B][/B][/B][/B]https://www.dropbox.com/s/blu6t02u56obfvk/2015-08-01 18.06.53.jpg?dl=0
https://www.dropbox.com/s/ow9kyiav0nilskf/2015-08-01 18.00.49.jpg?dl=0
https://www.dropbox.com/s/tg118386n00bneh/2015-08-01 18.00.23.jpg?dl=0
This was a quick picture I took of the the soldering on the CR4 with R-JTAG wires:
https://www.dropbox.com/s/7kze5q1csvl9qcc/2015-08-01 17.45.04.jpg?dl=0
I am pretty much giving up on why it won't boot, but I am starting to suspect that the CR4 may be broken. If anyone has some ideas or suggestions, then I would really appreciate it. Thanks!
Last edited:
