CORONA Installed CR4 XL, read nand 2x perfectly, now cant connect with J-RP V2 and J-runner

Mode-B

Full Member
Dec 27, 2014
41
0
Hardware and software used:

-Windows 7 (64bit)
-J-Runner V0.3 beta 5 (then updated it to V0.3 beta 7)
-J-R Programmer V2
-CR4 XL
-Corona QSB V3
-Corona Postfix adapter V2
-XBOX 360E 250 GB (Corona V5)




So, I installed the CR4 XL on my Corona V5(Xbox 360E 250gb) and was able to read my nand twice and compare it with jungle runner. I created the ECC, then wrote the ecc. Then my xbox only gives me a red light on the power button. It's not powering on at all. So, I thought it may be that the postfix adapter v2 was not contacting the resistive wall on the gpu. I tried to uninstall the postfix adapter v2 and broke the dang spring loaded contact point. I ordered a new postfix adapter v2 and installed and I'm positive it is installed correctly this time as it sat fine and did not push back as it did when I installed the first one. Hooked it up to my computer and was able to read the nand again although it was the one with the ecc i wrote to it in the first place. I only read the nand again to make sure it would recognize the xbox in j-runner. I have my stock nand reads safe and backed up in multiple locations so I wouldn't overwrite the stock nand reads on accident. After I determined i could get a connection to the nand again after replacing the postfix adapter i tried writing the stock nand back to the xbox with no luck. I'm not sure what the hell is going on. I have a pretty good soldering skills i think and really don't think this is my problem.When i tried to write the stock nand back to the box i got errors on every block. Now all i get when the box is connected in j-runner is:

Version: 10
Flash Config: 0x00000000
Can not Continue


I have used 32bit and 64 bit operating systems with win7 and they both report the same things. My xbox sat for a week while i was waiting for the new postfix adapter(don't think this had anything to do with this problem). Also, I went over all my wire installs and shortened them as suggested but i still get the above errors. I just want my box back to stock to see if it even works still.

I have successfully j-tagged an old box but it was a piece of crap that had the RROD come on every once in a while so I have some idea as to what I'm doing. I really don't believe this xbox is bricked so any thoughts would be REALLY GREATLY APPRICIATED. And by the way this xbox was brand new and was working just fine. I ordered it off Amazon like maybe 4 or 5 months ago and used it a few times other than that it was sitting in the box waiting for this new CR4 XL chip. If I'm forgetting anything let me know...I don't see these templates that are mentioned on here so i did my best to include as much info as possible as well as pics of my install.


In the process of uploading my install photos and my j-runner logs...it's not letting me upload pics for some reason at the time of writing this.
 

Mode-B

Full Member
Dec 27, 2014
41
0
not sure why it's not letting me upload jpegs or my txt files this sucks lol
 

Mode-B

Full Member
Dec 27, 2014
41
0
Thanks guys i kinda figured it may have to do with the size cuz only one of many was ok originally. Anyways here are the pics and the log will be up in a few mins...

102_2694--2.jpg102_2699--2.jpg102_2700--2.jpg102_2702--2.jpg102_2705--2.jpg102_2707--2.jpg102_2708--2.jpg102_2713--2.jpg102_2715--2.jpg102_2717--2.jpg102_2718--2.jpg
 

Attachments

Mode-B

Full Member
Dec 27, 2014
41
0
log showing i have good nand dumps and then created the and wrote the ecc...

----------------------------------------------------------------------
Friday, December 26, 2014 8:22:31 PM


J-Runner v0.3 Beta (7) Started




Happy Holidays Everyone!
Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00043000
00043000
Corona
CB Version: 13182
Corona
Reading Nand to C:\Users\byrdson\Desktop\RGH2+ Files\J-Runner V 0.3 beta 5\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 3:29 min:sec


Reading Nand to C:\Users\byrdson\Desktop\RGH2+ Files\J-Runner V 0.3 beta 5\J-Runner v3 (5) Core Pack\J-Runner v3 (5) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Corona
Glitch2 Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:29 min:sec


Comparing...
Nands are the same
CR4 Selected
ECC created
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x00043000
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec

----------------------------------------------------------
 

jligg

VIP Member
Mar 16, 2011
1,062
88
Cincinnati Ohio
Remove 5v wire and try to write you stock nand again. Jrp2 can be touchy. After hooking it up and seing the jrp2 logo in jrunner, hold down the black reset button for 2 seconds on the jrp2 and then try and write again. Your soldering looks fine
 
Last edited:
  • Like
Reactions: Mode-B

jerky333

Full Member
Jan 5, 2014
72
0
Masshole (US)
To try to get it back to stock, can you try writing one your original nand dumps back to the box, then just disconnecting the 5v wire from the QSB, and see if stock nand boots?

Note: You shouldn't need to uninstall anything if all you soldering is ok, which it looks like it is, but you never know there could be a bridge under the QSB.
 
Last edited:

jligg

VIP Member
Mar 16, 2011
1,062
88
Cincinnati Ohio
To try to get it back to stock, can you try writing one your original nand dumps back to the box, then just disconnecting the 5v wire from the QSB, and see if stock nand boots?

Note: You shouldn't need to uninstall anything if all you soldering is ok, which it looks like it is, but you never know there could be a bridge under the QSB.
Look up..isnt that what I just asked him to do?
 
  • Like
Reactions: skillet34

Mode-B

Full Member
Dec 27, 2014
41
0
Remove 5v wire and try to write you stock nand again. Jrp2 can be touchy. After hooking it up and seing the jrp2 logo in jrunner, hold down the black reset button for 2 seconds on the jrp2 and then try and write again. Your soldering looks fine
Thanks for such quick responses guys. I will try this tonight when I get off and report back...had to go into work for a few hours.
 

Mode-B

Full Member
Dec 27, 2014
41
0
Well...not looking too good guys. I disconnected the 5V wire from the QSB. Then started jrunner and hooked up the J-R Programmer V2, then plugged in the power to the console and held the reset button for 2 secs as suggested. Loaded my stock nanddump into the source and tried to write the nand but i am still getting the same thing in jrunner

Version: 10
Flash Config: 0x00000000
Can not Continue


Maybe my JR Programmer V2 is garbage??? All the chips and programmer were purchased just recently and i haven't used any of the components on any other box but this one.. They are definitly genuine TX parts not knock offs. Anyone have any other ideas for a fix? I really don't understand it read the nand and wrote the ecc without a hitch it seemed. Now i cant even connect in j-runner to flash to stock.
 

ablegepu

VIP Member
Jan 3, 2014
925
0
Alabama U.S
first off post a good quality picture of the jr programmer, not saying it's not genuine... Just looking for a possible defect (longshot)... also if you have a multimeter check all of your solder points on the QSB against their corresponding point on the flip side of the board (continuity test).. Also check each point against any and all adjacent points surrounding each point. (so we can almost completely rule out the QSB as the culprit).

One more thing, and it may be stupid because your soldering looks damn near flawless but if you have any doubt about any of your solder bridges (R2C4, R2C6, R2C7, R2C10) or if you are just curious try and touch them up to make sure they are getting bridged properly, I believe they may cause this problem..
 
Last edited:
  • Like
Reactions: Mode-B

Mode-B

Full Member
Dec 27, 2014
41
0
Originally Posted by ablegepu
first off post a good quality picture of the jr programmer, not saying it's not genuine... Just looking for a possible defect (longshot)... also if you have a multimeter check all of your solder points on the QSB against their corresponding point on the flip side of the board (continuity test).. Also check each point against any and all adjacent points surrounding each point. (so we can almost completely rule out the QSB as the culprit).

One more thing, and it may be stupid because your soldering looks damn near flawless but if you have any doubt about any of your solder bridges (R2C4, R2C6, R2C7, R2C10) or if you are just curious try and touch them up to make sure they are getting bridged properly, I believe they may cause this problem...
Ya know, the bridge points are what I'm thinking it is now. I didn't just bridge with solder I used a strand of thin wire to bridge the points. It's definitely worth a try to retouch these points. This time I'm going to just bridge with solder. If this doesn't work I'll go ahead and break out my multimeter and start checking the solder points.