RGH Jasper wont boot glitched dash

[NeOCzx]

Hi and good day...

can someone help with my problem here?

recently doing RGH on 1 unit of jasper. the unit can boot to xell just fine, but cannot boot to the glitched dash. i made my glitched image and ecc using xnandhealer 0.78
the flasher shows its a jasper 512, but the box indicates its a 256mb model (arcade) since i cannot boot to dash due to failed update i dont know the exact model of it.

i got the unit without a dvd drive. the console originally failed the update process on 13146 dash (i dont know the ori dash version). the owner tried to recover the dvd key and end up frying the drive.

it is any way that i can fully wipe the update? i got the old nand dump, just in case.

already checked the LDV value, seems like no issues of it.

i have questions on RGH. hope all the gurus can help me :3

1. can the dash boot w/o dvd drive? currently i have no dvd drive can someone confirm it for me?

2. i flashed the ecc using xnandhealer. it flashes the ecc using the command -w16 and cant be changed. *i read somewhere that for 256/512 uses -w64 command)
but it can boot xell just fine. would that be the cause that i cant boot to dash?

3. it is possible to a 256 model xbox360 with 512mb nand chip?

thx for reading n have a nice day :3

 

[BL4K3Y]

You do not need a DVD-ROM connected.

It doesn't matter with big block consoles, you should only be reading 64MB, anything after that is allocated to internal storage.

Try building a modified image with J-Runner and post back here with your results.

 

[NeOCzx]

Hi.. thx for the reply n sorry for the late reply :3
Tried 14699, 14717 and 14719 glitched image with no luck.. the green light still blinking non stop.. ._.
any other suggestions?

 

[Statecowboy]

If you have the cpu key, original nand, and are using J-Runner there is no reason you should not be able to build a bootable hacked image.

Do those things and provide your J-Runner output log.

When you say green light keeps blinking, are you refering to your console's lights or the coolrunner?

 

[NeOCzx]

hmm.. what i mean the console light is blinking... not the coolrunner..

here is the log for reference.
somehow i cannot upload the txt files to the forum.. dont know y.


http://pastebin.com/AKWUCsMd

 

[BL4K3Y]

I can't see anything wrong with that image, write it back to your console's NAND with NandPro or use J-Runner.

Did you verify the LDV in that log (7) against what you see in XeLL?

The centre LED on the ROL is blinking because there isn't a DVD-ROM drive attached.

 

[NeOCzx]

Thx for the reply. yeah.. im already make sure of that. this is my fuseset from xell
fuseset 07: fffffff000000000
fuseset 08: 0000000000000000
fuseset 09: 0000000000000000
fuseset 10: 0000000000000000
fuseset 11: 0000000000000000

the ROL also not spinning that indicates the glitch working. only the center ROL led blinks.
im flashing the glitch dash using xell via usb.

if that any way that the failed updates interfere with the glitched dash?
it is possible to delete whole nand and only flash the first 64mb of the nand in xell?
it is any possible tool for editing the xenon.elf for erasing and flashing the nand in 1 reboot.?
or i can build a full 512mb nand with first 64mb of glitched dash? any tools that i can do that? to wipe off the memory data.

 

[Statecowboy]

Maybe I'm just missing it, but you said you do have the original nand right? Do you have a nand-x?

Flash your original nand back, and then flash the hacked image created from J-Runner and your cpu key. Then you can assure yourself you have the proper image flashed.

 

[NeOCzx]

i think the problem lies on the looped failed update.
i tried to extract the nand using 360 dump tools and it indicated that
Extracting Patch 0 HV & Kernel
ApplyKernelPatch: Failed to apply Patch V13146, it appears to be corrupt. (the nand dump itself is ok, the kernel messed up when updating)

so i decided to build a nand using a donor nand.
i have my cpu key, decrepted kv.bin, config.bin, smc and other generic files..
but the problem is when i tried to inject all of that into the donor nand it would mess up the smc config.. and it seems like when i injecting the config.bin this happen.

i dont know if its a bug from 360 flash dump tool or is my own mistake. can we inject all the bin directly using nandpro? any references of the block and files that i need to inject? :3
can i build the nand only injecting the kv only? or i need to manually edit the smc config identical to original nand? quite confused over here.. any suggestion are welcome.