RGH Jasper problem, 360 multi builder does not make nandflash.bin

[LINSONCHAN]

I already got the image_00000..... ecc file and got to the XELL to get my key,

I already had the nanddump.bin and cpukey.txt,

When making nandflash.bin, whenever I press 2 (jasper 16) and 1 build image, it just goes directly to the finish instruction without making the nandflash.bin

I also open the nanddump.bin I extracted to 360flashtool, and it open up the file, but on the other side, the is a "NO FS ROOT"

please help.

 

[WestCoastConsoles]

Try another program Jtag tool and see results. Did you verify you had good dumps in 360 flash dump tool.

 

[LINSONCHAN]

what other jtag tools can I use?

 

[WestCoastConsoles]

Coolshrimps jtag tool.

 

[LINSONCHAN]

thanks

 

[x360ccm]

did you name your nand like so nanddump.bin and cpukey.txt

or did you just name them nanddump and cpukey.

 

[LINSONCHAN]

exactly with extentions.

downloading jtag tool coolshirmp

 

[x360ccm]

just have it named nanddump and cpukey.it should work fine then.

 

[WestCoastConsoles]

What version are you using of 360 flash dump tool I remember I used an outdated version and got no fs root on a bb jasper. New version fixed it. Is this a big block jasper or 16mb

 

[LINSONCHAN]

im using .90 and since .97 crashes when it loads the dump.bin

RGHtool coolshrimp still does not work. also uses 360_Multi_Builder_v0.5

I already got to Xell and got my key, now im stuck.

Any ideas?

Jasper has no memory, so its 16mb right?

 

[WestCoastConsoles]

How many dumps did you get try .96 .90 is the version I had issues with.

---------- Post added at 01:55 ---------- Previous post was at 01:50 ----------

Sent a pm your way phone spazzed out and sent you 3 my apologies

 

[LINSONCHAN]

got 2 dump, mistakenly forgot to rename after using c:\nandpro usb -r16 nanddump.bin

but im sure i always gets a good dump. i never had a problem, since I have rgh about 5 units already.

Is it possible to just revert back to the old nand

only writting to 004F

 

[WestCoastConsoles]

that nand dump is corrupt write the old nand back and see if it boots. Then redump you can never be too certain just assuming the dump is good you need to check always open in 360 flash dump tool to verify its a good clean nand dump.

Next step is building you you an image with a donor nand if the first method doesn't work

 

[x360ccm]

dose your jasper have internal memory like 256 or 512 by any chance.

the only thing i could get it to load in was

 

[LINSONCHAN]

no it does not have any internal memory

 

[WestCoastConsoles]

hook up your 360 to nand pro and get us a flash config

 

[LINSONCHAN]

what's the command to write upto 004F only, the one the ecc wrote, so that I do not have to risk flashing up 3FF

 

[WestCoastConsoles]

Scratch it Im not 100 % so Id rather you not try it

 

[LINSONCHAN]

Im planning to restore writting the original nand up to 004F, where the image.ecc wrote.

Whats the exact command?

 

[LINSONCHAN]

Restored, and boots absolutely fine.

Dash, 13599