TRINITY Cannot boot into Xell / JRP2 = CR4XL v4

[tacxboxflash]

HIGHER RESOLUTION IMAGES AT:

http://1drv.ms/1Izw1ST

• Console Type: TRINITY
• Programmer Used: JRP v2.0
• NAND Size: 16MB
• Dashboard version: 13599
• CB Version: 9188
• Screenshot of NAND details from J-Runner: Click on above link
• J-Runner log:

===================================================
Friday, January 09, 2015 4:42:41 PM

J-Runner v0.3 Beta (7) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
Comparing...
Nands are the same
Version: 10
Flash Config: 0x00023010
Writing Nand
nanddump1.bin
Done!
in 3:43 min:sec

Comparing...
Nands are the same
Version: 10
Flash Config: 0x00023010
00023010
Trinity, Jasper 16MB
CB Version: 9188
Trinity
Reading Nand to C:\Users\Pins\Desktop\RGH\JR\J-Runner v3 (5) Core Pack\output\nanddump1.bin
Reading Nand
Done!
in 3:28 min:sec

Reading Nand to C:\Users\Pins\Desktop\RGH\JR\J-Runner v3 (5) Core Pack\output\nanddump2.bin
Initializing nanddump1.bin..
Trinity
Nand Initialization Finished
Reading Nand
Done!
in 3:28 min:sec

Comparing...
Nands are the same
Initializing nanddump1.bin..
Trinity
Nand Initialization Finished
Comparing...
Nands are the same
CR4 Selected
* unpacking flash image, ....
Spare Data found, will remove.
Removed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9188
CB_B: 9188
CD (image): 9452
CD (decrypted): 8453
* this image will be valid *only* for: trinity (slim)
* patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3
* patching CB_B...
patchset for 9188 found, 4 patch(es)
* constructing new image...
* base size: 70000
* No separate recovery Xell available!
* Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x9ABF (0x1AC0 bytes) CB_A 9188
0x9AC0..0x112BF (0x7800 bytes) CB_B 9188
0x112C0..0x172BF (0x6000 bytes) CD 8453
0x172C0..0xBFFFF (0xA8D40 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...Done!
------------- Written into output\image_00000000.ecc

Trinity Manually Selected
Version: 10
Flash Config: 0x00023010
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec

• Detailed Description of the Problem: Successfully dumped NAND 2x, Created then Wrote ECC using standard method via JR and also manually selecting the TRINITY_CR4XL.ecc file. Tried to boot to XELL with the following: DIP 3&4 on, 3 on only, 4 on only, 1 on only, 2 on only. Soldered in 22 cap. Left console on for several minutes each time, will not boot to XELL. CR4 is getting power, red led on. Green led blinks for about a half second every 5 seconds or so. Able to flash back to stock NAND and console boots fine. Checked solder points with multimeter, posting here as last resort. Any help is greatly appreciated!

• Was the console working before you started: Y
• Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Y
• How long is the light on for each time: ~ 1 second

 

[BL4K3Y]

Load "TRINITY_CR4.ecc" from the "common\ECC" folder as the source in J-Runner and write it to your console's NAND.

Have you tried different POST_OUT resistance options?

If you know how to use RATER, get a POST output log (3 or 4 glitch cycles should be enough).

 

[tacxboxflash]

Hey Blackey,

Thanks for the quick reply, its true you never sleep huh?

I tried loading the TRINITY_CR4.ecc as source before writing the ECC to the nand and had the same behavior/result. The only post_out resistance option I tried was the 22 based on everyone have such great results with it on trinity consoles. I will start down that road next. I do not know how to use the RATER, I will look into that if I can't get something to give with the different post_out resistance levels.

When do you typically mail it in, after 5 min? 10, 20? I appreciate all of you guys here, thanks in advance for any other suggestions. I will post my results shortly.

Load "TRINITY_CR4.ecc" from the "common\ECC" folder as the source in J-Runner and write it to your console's NAND.

Have you tried different POST_OUT resistance options?

If you know how to use RATER, get a POST output log (3 or 4 glitch cycles should be enough).

 

[BL4K3Y]

Hey Blackey,

Thanks for the quick reply, its true you never sleep huh?

I tried loading the TRINITY_CR4.ecc as source before writing the ECC to the nand and had the same behavior/result. The only post_out resistance option I tried was the 22 based on everyone have such great results with it on trinity consoles. I will start down that road next. I do not know how to use the RATER, I will look into that if I can't get something to give with the different post_out resistance levels.

When do you typically mail it in, after 5 min? 10, 20? I appreciate all of you guys here, thanks in advance for any other suggestions. I will post my results shortly.

You need to make sure you write the Trinity CR4 ECC image to the console's NAND or it won't boot.

I was talking about the small jumper:

 

[jerky333]

When working it should boot in 10-20 cycles at most, once dialed-in usually boots under 5.

 

[tacxboxflash]

Sorry for the noob moment, Blackey. I wound up trying the same using 10 & 100 with the same result. I wonder if its something with my method of writing the TRINITY_C4R.ecc? I did the following:

1. Dumped NAND 2x (verified good, able to flash back to stock no prob)
2. Hit CREATE ECC
3. Loaded Source as TRINITY_C4R.ecc
4. Write ECC, at which point JR has me manually select Trinity.

I don't know it just feels like I am missing something or doing something incorrectly.

Does this make any sense?

Thanks man.

You need to make sure you write the Trinity CR4 ECC image to the console's NAND or it won't boot.

I was talking about the small jumper:

 

[Magics]

im also having this same problem been trying the same way you are

 

[ultimate360]

Nevermind, I'm nothing but a waste of server space on this forum

 

[nofeloniesyet]

Turn dip 3 off. Had one the other day that wouldn't boot until I did that

from op:

• Detailed Description of the Problem: Successfully dumped NAND 2x, Created then Wrote ECC using standard method via JR and also manually selecting the TRINITY_CR4XL.ecc file. Tried to boot to XELL with the following: DIP 3&4 on, 3 on only, 4 on only, 1 on only, 2 on only. Soldered in 22 cap. Left console on for several minutes each time, will not boot to XELL. CR4 is getting power, red led on. Green led blinks for about a half second every 5 seconds or so. Able to flash back to stock NAND and console boots fine. Checked solder points with multimeter, posting here as last resort. Any help is greatly appreciated!

• Was the console working before you started: Y
• Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: Y
• How long is the light on for each time: ~ 1 second

 

[WigOmatic]

Try updating your console to CB version 9231(15572+)
The first trinity I did with a cr4 wouldn't boot no matter what I tried on 9188. So since then I always make sure that the console is at least updated to 15574(CB 9231)
Maybe it's luck or it might not be related but it won't hurt to try.

 

[Magics]

i fixed mine this morning all i did was remove the 22 cap and booted so fast got my cpu key finally

 

[Antalpromille]

i fixed mine this morning all i did was remove the 22 cap and booted so fast got my cpu key finally

Why did you even solder a cap before you got the console booting? :facepalm:

 

[Magics]

i was doing another console and forgot lol i know i want give myself a slap on the forehead for that

 

[Antalpromille]

i was doing another console and forgot lol i know i want give myself a slap on the forehead for that

You don't forget stuff like that, and next time start your own topic.

 

[tacxboxflash]

Not at all, mate. Everything helps, believe me. Like the early days of the MRA hack. Only for the gents on this forum I'd have never mastered that. Thanks for trying.

Nevermind, I'm nothing but a waste of server space on this forum

 

[tacxboxflash]

Going to try that next, I will not give up. Thanks for all the suggestions guys! I got really knackered on Sat night, hungover all day today so tomorrow is the day stay tuned!

"Try updating your console to CB version 9231(15572+)
The first trinity I did with a cr4 wouldn't boot no matter what I tried on 9188. So since then I always make sure that the console is at least updated to 15574(CB 9231)
Maybe it's luck or it might not be related but it won't hurt to try."

 

[tacxboxflash]

Ok fellas, I updated to 17150 and below is my post out log. Tried the same method as before dip 3&4, 3 only, 4 only, 1 only, 2 only, 1&2 at 0, 10, & 100 and still can't get XELL to boot. Re-soldered G, B, & Y again, solid connections. Shortened each wire as well. Running out of ideas, hopefully the log below will shed some light on where I am coming up short. Thanks all....

EDIT: I am taking the TRINITY_CR4.ecc file from the \common and copying it to \output then renaming it image_00000000.ecc then hitting write ecc.

===================================================
Monday, January 12, 2015 1:03:56 PM

J-Runner v0.3 Beta (7) Started


WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button


Checking Files
Finished Checking Files
Initializing nanddump1.bin..
Trinity
Glitch2 Selected
Nand Initialization Finished
CR4 Selected
You need an .ecc image
ECC created
Version: FF
Wrong Version.
Version: 10
Flash Config: 0x00023010
Writing Nand
image_00000000.ecc
Done!
in 0:18 min:sec

Version: 10
Press Escape to exit
Waiting for POST to change
Post 10 - Payload/1BL started
Post 0C
Post 0D
Post 05
Post 06
Post 0A
Post 0C
Post 0D
Post 05
Post 06
Post 0A
Post 0C
Post 0D
Post 05
Post 06
Post 07
Post 0A
Post 0C
Post 0D
Post 05
Post 06
Post 07
Post 0A
Post 0C
Post 0D
Post 05
Post 06
Post 0A
Post 0B
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 07
Post 0A
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 0A
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 0A
Post 0C
Post 0D
Post 05
Post 06
Post 07
Post 0A
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 0A
Post 0B
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 0A
Post 0B
Post 0C
Post 0D
Post 05
Post 06
Post 0A
Post 0B
Post 0C
Post 0D
Post 04
Post 05
Post 06
Post 07
Post 0A
Post 0C
Post 0D
Done!

 

[Antalpromille]

The ECC you create for trinity won't work, and renaming the trinity_cr4.ecc won't make any difference. Flashing it to the nand will make your chances alot bigger though.

 

[tacxboxflash]

Ok dumb question, should I just take the TRINITY_CR4.ecc from \common and load to source and hit write NAND?

 

[Antalpromille]

Ok dumb question, should I just take the TRINITY_CR4.ecc from \common and load to source and hit write NAND?

Yes.