What's new

Unsolved No boot after glitching

  • Thread starter laz_no
  • Start date
  • Views 178
L

laz_no

Newbie
Messages
31
Reaction score
1
Hello guys .

I have this xbox 360 corona MB rgh ... It was working well , and today i turn it on and no display on the screen ..

So i open it and i see that the glitch chip glitching normal and stop after 2-glitch cycle wich means the console booted up , so i change the glitch chip to X360 run and still the same result ..

What could be the problem ?

I think the problem is the southbridge maybe ? ..

Thanks
 
A

afterjo

Enthusiast
Messages
775
Reaction score
115
do you get constant green light blinking?
 
L

laz_no

Newbie
Messages
31
Reaction score
1
best way to diagnose a problem would be to write stock nand and start from there. Because RGH won't give error codes.

i don't have the OG files for this console ... so i should create a nand from scratch and see if it will solve the problem ! what do u think ?
Post automatically merged:

Haha what's going on with this console , i can it's a corona from the positioning of the nand header , but jrunner telling me it's a trinity and auto select a trinity mother board ??? what i'm i supose to do
Post automatically merged:

Haha what's going on with this console , i can it's a corona from the positioning of the nand header , but jrunner telling me it's a trinity and auto select a trinity mother board ??? what i'm i supose to do
 
Last edited:
C

Cryptic7s

Enthusiast
Messages
384
Reaction score
48
i don't have the OG files for this console ... so i should create a nand from scratch and see if it will solve the problem ! what do u think ?
Post automatically merged:

Haha what's going on with this console , i can it's a corona from the positioning of the nand header , but jrunner telling me it's a trinity and auto select a trinity mother board ??? what i'm i supose to do
Post automatically merged:

Haha what's going on with this console , i can it's a corona from the positioning of the nand header , but jrunner telling me it's a trinity and auto select a trinity mother board ??? what i'm i supose to do
Thats definitely a Corona, it seems to have 4GB nand points to me, as well as the Alt layout for the pins. I posted a reply to someone else on here with a guide on how to rebuild a hacked nand from nothing, hopefully it helps you too.



  1. usb spi nand programmer(nand-x, jr-programmer, any will do(eMMC R/W kit for corona 4gb)
  2. J-Runner the ultimate JTAG/RGH app DOWNLOAD
  3. Extracted nand files that match you motherboard model (download below)


[SIZE=x-large]Step 1; Recovery of cpu key and LDV's[/SIZE]


  • [SIZE=medium]Download one of the clean extracted donor nand files according to your motherboard model and extract the containing folder to the location of your choice;[/SIZE]
Don't use these files to unban your console, first you don't have the original cpu key and second they are all coming from banned consoles. You have been warned!


Extracted Nand Files Download


UnHidden Content:
[SIZE=medium]XENON[/SIZE]
[SIZE=medium]ZEPHYR[/SIZE]
[SIZE=medium]OPUS/FALCON[/SIZE]
[SIZE=medium]JASPER SB[/SIZE]
[SIZE=medium]JASPER BB[/SIZE]
[SIZE=medium]TRINITY[/SIZE]
TRINITY No FCRT
[SIZE=medium]CORONA[/SIZE]
[SIZE=medium]CORONA 4gb[/SIZE]





  • [SIZE=medium]Next you need to solder/plug in your nand programmer wires onto the motherboard [/SIZE]
  • [SIZE=medium]Open J-Runner app an click on "show working folder" button located at the bottom right[/SIZE]




  • [SIZE=medium]Open the folder name "data" located inside /J-Runner/xeBuild/ folders[/SIZE]

  • [SIZE=medium]Open your extracted nand files folder and copy and paste KV.bin, SMC.bin, smc_config.bin and fcrt.bin(if required) to data folder. It should look like this.[/SIZE]

[SIZE=x-large][/SIZE]


  • In J-Runner, copy and paste this cpu key F37C0CD50B928F4E67614ACD548A4E49 in the cpu key section.

  • Choose dashboard version according your hack type (for JTAG choose 7371 - for phat rgh1 choose 14699 - for R-JTAG choose 15574 - for phat RGH2 choose 14719 - for slim choose anything above 14719)

  • Select your motherboard nand type.

  • Select retail as your image type.

  • It should look like this.




  • In J-Runner under the Advanced tab click on Create an image without nanddump.bin





  • Then you will be ask to enter LDV just enter any number between 1 and 80 and click ok.






  • At this point the dummy image should be successfully created and automatically loaded in the "Load Source" section.

  • Now with your nand programmer properly connected to both you pc and motherboard click on "Write Nand".

  • Wait until J-Runner is finish writing the nand and select your "hack type" then click on "Create ECC" for rgh machine or "Create Xell-Reloaded" for JTAG/R-JTAG machine.

  • Now click on "Write ECC" or "Write Xell-Reloaded" depending on your hack type[SIZE=11pt].[/SIZE]








  • You are now ready to boot xell and recover your cpu key.

  • Disconnect the nand wires from the nand programmer and Power ON your console and wait for xell to boot.
  • .
  • Once xell as booted write down your cpu key, fuseset 02 and fuseset 07/08.






Understanding and calculating LDV's
  • Calculating CF/CG ldv is fairly simple. Just count the number of "F" in fuseset 07 to fuseset 11. So in the example above we have a cf/cg lock down value of 2.

  • Calculating CB LDV can be a little bit more trickier. You have to take the right-most "F" and calculate how many character it is from the left. In the example above the right-most "F" is 5 characters from the left so we have a cb lock down value of 5.

  • [SIZE=11pt]Understanding CB LDV; Quote from Martin C @ TX [/SIZE]

  • [SIZE=11pt]This value is NOT updated every dashboard version and is not directly reflected in any apps. However, the value can be translated to a CB/dashboard version. You cannot 'edit' your image to use a different CB for a retail NAND. It MUST match the entry as found in XeLL, otherwise it'll fail to boot.[/SIZE]

  • The example above is from a Jasper with a cb ldv cseq of 5, remember that this value can be translated to a dashboard version. So by looking at the chart below we can determine that dashboard 7371 would be the highest compatible version for this particular console.





[SIZE=x-large]Step 2; Building the fake OG nand image[/SIZE]


  • Now back in J-Runner, enter your cpu key in the cpu key section.

  • Select your dashboard according to your CB LDV cseq

  • Select Retail as Image type.

  • Select Motherboard nand type.

  • Click on the "Advanced" tab and on "create an image without nanddump.bin"






  • You will be ask for LDV, this is the cf/cg LDV so you enter what you have in fuseset 07/08 and click "OK".





  • You have now created a fake original nand image. Even though you won't be able to boot your console with this image it would still be a good idea to keep it somewhere safe.

  • With your new image loaded in the "Load Source" section and your cpu key in the "Cpu Key" section click on the "kv info" tab. You will notice that the info in there are obviously not from your console. So now would be a good time, for those who can, to extract your dvd drive key and patch the key vault with the appropriate dvd key.

  • Click on the "XB Settings" tab, click on "Advanced XeBuild Options", paste your dvd key in the "dvdkey" section, click "OK" then click the "Use Edited Options" check box.

  • For DG16D5S and DLN10N owners; the easiest and cheapest way to make your dvd drive functional would be to install a TX LTU 2 pcb.




Final Part; Building/writing the hacked image



  • Back in J-Runner, with your new fake original nand image loaded in the "Load Source" section and cpu key in the "Cpu Key" section select hack image type(Jtag - rgh - rgh2 - r-jtag), select your desired dashboard(should be the latest which is 17150 at the moment), select motherboard nand type. You can also edit dashlaunch and xeBuild options at this point.

  • Click on create xeBuild image. You will see 3 or 4 warning messages poping up which will ask you if you want to delete kv.bin, smc.bin, fcrt.bin and smc_config.bin. Click yes on all of them.



  • With your nand programmer properly connected to both your console and pc click on "Write Nand"

  • Disconnect nand wires, Boot your console and have fun.


Guide taken from XPG, good luck
 
Top Bottom