Jump to content


Photo

Need Help With Slim Trinity And Rgh


  • Please log in to reply
8 replies to this topic

#1 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 06 March 2012 - 03:34 AM

Ok so I got the Xbox360 Slim (Trinity) installed the QSB and the CoolRunner-II connected it to the Nand-X v3 and read my nand several times.

Each time I read it i get :


Trinity
Reading Nand to F:\16gb usb\111-JTAG TOOLS\111-J-Runner v01 (259) Core Pack\J-Runner\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00023010
Reading Nand
Error: 250 reading block 178
Done!


its always the same block 178, I tried a few other programs and same block again.. I have re-soldered everything aswell.

but my big problem is when I select my nand files and that when I go to create the ECC file.. this is what I get

Initializing Nand..
*found flash image, unpacking...
ECC'ed - will unecc.
UnECC'ed
*found decrypted CD
*found XeLL binary, must be linked to 0x1c000000
*we found the following parts:
SMC: 3.1
CB_A: 9230
CB_C: 9230
CD (image): 9230
CD (decrypted): 8453
*this image will be valid *only* for: trinity (slim)
*patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3

* XOR HACK NEEDED FOR CB 9230
* patching CB_9188..

(*** and then the J-Runner program crashes ***)


Im not sure whats going on...

any one got any suggestions

Thanks

Edited by FrankDux, 06 March 2012 - 03:48 AM.


#2 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 06 March 2012 - 03:48 AM

I have a small update...

now when I do a fresh nand read with J-Runner and select Create ECC it seems to work with out crashing.. here is the logs


===================================================
Monday, March 05, 2012 8:38:38 PM



No Updates Found


Checking Files
Finished Checking Files
Can not continue
Trinity
Reading Nand to F:\16gb usb\111-JTAG TOOLS\111-J-Runner v01 (259) Core Pack\J-Runner\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00023010
Reading Nand
Error: 250 reading block 178
Done!

Initializing Nand..
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9230
CB_B: 9230
CD (image): 9230
CD (decrypted): 8453
* this image will be valid *only* for: trinity (slim)
* patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3

* XOR HACK NEEDED FOR CB 9230
* patching CB_B 9188...
patchset for 9188 found, 4 patch(es)
* Applying XOR Hack to CB_B 9230
*** Re-encrypting CB_B with xor keystream
*** Fixing entrypoint

* constructing new image...
* base size: 70000
* Replacing CB_A 9230 with 9188
* encrypting CB...
* 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 9230
0x9AC0..0x114EF (0x7A30 bytes) CB_B 9188
0x114F0..0x174EF (0x6000 bytes) CD 8453
0x174F0..0xBFFFF (0xA8B10 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...

100%
------------- Written into output\image_00000000.ecc


why is this working this way, but if I open J-Runner and select my nand files then click on Create ECC it crashes ????


#3 stanleycup

stanleycup

    X-S Enthusiast

  • Members
  • 28 posts

Posted 06 March 2012 - 06:31 AM

QUOTE(FrankDux @ Mar 5 2012, 09:48 PM) View Post

I have a small update...

now when I do a fresh nand read with J-Runner and select Create ECC it seems to work with out crashing.. here is the logs
===================================================
Monday, March 05, 2012 8:38:38 PM
No Updates Found
Checking Files
Finished Checking Files
Can not continue
Trinity
Reading Nand to F:\16gb usb\111-JTAG TOOLS\111-J-Runner v01 (259) Core Pack\J-Runner\output\nanddump1.bin
Arm Version: 3
Flash Config: 0x00023010
Reading Nand
Error: 250 reading block 178
Done!

Initializing Nand..
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 3.1
CB_A: 9230
CB_B: 9230
CD (image): 9230
CD (decrypted): 8453
* this image will be valid *only* for: trinity (slim)
* patching SMC...
Patching Trinity version 3.1 SMC at offset 0x13B3

* XOR HACK NEEDED FOR CB 9230
* patching CB_B 9188...
patchset for 9188 found, 4 patch(es)
* Applying XOR Hack to CB_B 9230
*** Re-encrypting CB_B with xor keystream
*** Fixing entrypoint

* constructing new image...
* base size: 70000
* Replacing CB_A 9230 with 9188
* encrypting CB...
* 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 9230
0x9AC0..0x114EF (0x7A30 bytes) CB_B 9188
0x114F0..0x174EF (0x6000 bytes) CD 8453
0x174F0..0xBFFFF (0xA8B10 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...

100%
------------- Written into output\image_00000000.ecc
why is this working this way, but if I open J-Runner and select my nand files then click on Create ECC it crashes ????

how can you make the coolrunner glitch without new JED/SXVF files????

#4 Dark Mod

Dark Mod

    X-S X-perience

  • Members
  • PipPip
  • 489 posts
  • Location:Trinidad and Tobago W.I
  • Interests:Electronic services and upgrades
  • Xbox Version:v1.6b
  • 360 version:v5.0 (360S - trinity)

Posted 06 March 2012 - 07:01 AM

Use multibuilder 0.8 or 0.7....that never let me down.

#5 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 06 March 2012 - 07:19 PM

Ok so I took a gamble on the ECC it made and booted it up my slim, I got the CPU Key and created the image and clicked write nand.

it now works, but the timing is horrible, takes 2 mins to boot, some times it takes 10secs, I tried moving the blue wire around and different methods seen online.. nothing is really helping..


This timing thing is killing me.

#6 boflc

boflc

    X-S X-perience

  • Members
  • PipPip
  • 389 posts
  • Xbox Version:none
  • 360 version:v4.0 (jasper)

Posted 06 March 2012 - 07:27 PM

QUOTE(FrankDux @ Mar 6 2012, 02:19 PM) View Post

Ok so I took a gamble on the ECC it made and booted it up my slim, I got the CPU Key and created the image and clicked write nand.

it now works, but the timing is horrible, takes 2 mins to boot, some times it takes 10secs, I tried moving the blue wire around and different methods seen online.. nothing is really helping..
This timing thing is killing me.


how long is your cpu-rst wire?
a) try 28cm, 35cm and 50cm lengths. each console is different.
cool.gif make sure you stay away from coils when routing the wire.


#7 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 06 March 2012 - 07:45 PM

I have not altered the original length of the wire that came with the CoolRunner 2, I will try cutting it down little by little..

I wish people with successful timings would post some pics for ideas, no one ever does..

#8 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 06 March 2012 - 08:26 PM

Is there any one selling Xecuter POST QSB For Xbox 360 Slim but with out $10 shipping. its kinda expensive shipping on most sites or a $3 tiny item.

#9 FrankDux

FrankDux

    X-S Senior Member

  • Members
  • PipPip
  • 274 posts

Posted 07 March 2012 - 05:57 AM

Ok so I tried using all kinds of different lengths for the CPU RST wire, and tried even wrapping it around the fan shroud like someone suggested..

at 50cm wrapped around the fan shroud it actually booted 5 times in a row in 2-3secs but after that never booted again.

so i moved it around some more.. im back to having it coiled next to the xclamp like the diagram from TX show and its back to booting but takes a minute and doesnt always boot.


i also tried joining to wires together and the alternate points too. I redid all my solder points again, cleaned them all up.. doesnt change anything.

why is this so hard to get working. will a TRIM POT work instead of a long length of wire, if you run a small 8cm wire from CR-II glitch board to a small TRIM POT (which in effect is a section of wire that you can shorten the distance travelled by rotating the centre point) and then a small 2 or 4cm wire from trim pot to solder point on mobo.

????????

Thanks




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users