RGH J-Runner didn't save nanddumps/no boot to xell

[aydota]

Hi,
yesterday I've installed a coolrunner to a trinity board with qsb. After programming the coolrunner I've connected the qsb to my nand-x and began reading nand 2 times with J-Runner.
After that created and wrote ecc. Power cycled and start to xell. Went well. Took a photo of my keys and fusesets and entered my cpu key in j-runner.
Created an image and because I had no bad blocks while reading nand, I decided to wirte nandflash with j-runner instead of installing via usb stick and xell.
Made several boots after power cycling again and tried different post length! Have the post qsb installed. While trying to find the sweet spot of this box, had a bunch of boots to nxe. All went well! After achieved boot times about 15 seconds I put the slim back together.
Now I had the problem that when I tried to boot to nxe the box stucked at the boot logo.
I thought it'll help to create an new image and write it through xell. Entered the J-Runner folder of this box and had to find out, that the original nanddumps weren't saved :sly:
But there were still the nandflash.bin and the xenon.elf file. I put them into the root of an usb stick and flashed the image through xell. Went with no problems.
But after power cycling again, my box won't boot to xell nor to nxe. The coolrunner tries to glitch (green led flashes and fan speed regulate itself every 5 secs)!
The installation and soldering were done really properly, took my time and made everything tidyli! Was my seventh box, never had an problem before.
I'm on my way to college now, will post pics of installation on afternoon if needed.
My question is, what can I do now?
Thx in advance
Edit: the stock nand was on dash 13599 for the image i chose 14719. J-Runner should have handle that i suppose! Fyi only!

 

[BraveH43]

at the point of creating the image file all your files from the "Output" folder are saved into the folder named as your console serial number! your dumps should be labelled nanddump1.bin and nanddump2.bin. unless you restarted J-Runner during the process. then some residual files maybe in the Output folder still. (only way they would be deleted is if you do more reads but a warning box appears to tell you that you are about to overwrite the files.)

do a search for nanddump1.bin on your pc! unless you allowed an overwrite your files should still be there!

 

[aydota]

So, I`m now at home again.
Had searched the whole computer for nanddump but the only ones, which were found are the ones, belonging to the other xboxes I`ve RGHed.
I`ve also looked into the J-Runner output folder and in the folder with the serial number of the trinity, my problem is about.
In that folder there are those files:

CB_A.bin
CB_B.bin
cpukey.txt
image_00000000.exx
KV_Info.txt
nandflash.bin
nandflash.bin.log
SMC.bin
xenon.elf

And I`ve not startet another Nand reading during the procedure. Would have recognized the warning, that the Nands will be overwritten...

I would write the image_00000000.ecc again on my nand. Can I proceed with J-Runner?

 

[XL3THAL VIP3RX]

just get yourself a doner nand and inject your relevent KV and SMC files,so you can build a fresh retail nand.just make sure it 13599

 

[Martin C]

Without seeing your J-Runner log or knowing exactly what you did (you may have deviated from what you said you did - it happens), it's hard to say where the issue is.

 

[aydota]

Ok I downloaded Multibuilder where the 13604 Dash was able to be chosen. I build an glitch image increased the LDV and there you go...
No more freezes.
Thank you anyway!


Update:
The problem was, that I`ve stored the nanddumps into my external hdd because there were 2 folders with same 2 digits at the beginning and I didn`t wanted to confound them. So I`ve got my original nanddumps.

The nandflash.bin I`ve used at last were from another console.

So I`ve startet J-Runner and loaded the original nands created ecc, flashed it to my console. Managed to boot in Xell.

Then created hacked image with dash 14699 and after it did freeze in nxe with 14719.
That freezes also... :-(

Then I decided to go back on stock to check how it behaves there. And there the dash works great. Btw stock is on 13599 so my LDV is 1.
Then I`ve downloaded official 14699 dash update and installed via usb:
As I expected it freezed on that dash in the main menu after 3 to 7 secs.

I suppose that the xbox can`t handle updates further then 13599. Is there a way to creat an hacked image on that dash?

Pics of my solder:

 

[Martin C]

"I suppose that the xbox can`t handle updates further then 13599. Is there a way to creat an hacked image on that dash?"

that's a pretty daft assumption, based only on your own work.

Build a valid 14719 RETAIL image for your console. Ensure LDVs are correct.

Use this image as the base for an RGH image for 14719.

Do NOT attempt to manually edit ANYTHING in the NAND. You shouldn't need to.

 

[aydota]

I`ve loaded my nanddumps in J-Runner.
Choose 14719 and Retail. Changed the LDV to 2 and confirmed the change.
After that I clicked write image.
Then I loaded the created image into source and selected glitch mode with same dash and firstly created and wrote ecc. Went well, could load Xell after power cycling.
Then entered my CPU Key into J-runner and created an a glitch image on 14719. Wrote it via usb stick and power cycled.
After booting to NXE I still get freezes... Sometimes in the screen where I choose the profile, sometimes 10 seconds after starting NXE...
I had the box on 13604 before your advice and had no freezes...
I`ve read that there are xboxes which can`t handle the 14xxx updated. They freeze, get an rod or can`t read disks. Couldn`t it be the reason for this...
My original nanddumps have no bad blocks and I do get no errors while creating them images...

 

[Martin C]

"Choose 14719 and Retail. Changed the LDV to 2 and confirmed the change."

WHY are you changing the LDV?

 

[aydota]

Don't worry I've read your sticky! Because after the nanddump I've flashed back stock nand and installed the original microsoft update dash 14699 to try how the box behaves on stock 14699 it also freezed. So my fusesets have changed from 1 to 2.