ANSWERED Jasper 256 aud_clamp blackscreen

[WalangAlam]

I have a Jasper 256. 13599 freebot image works but 14699 does not work. Center light green but won't boot.

I used my original untouched nand in creating freebot image with j-runner. Tried also multibuilder still no joy.

Tried following this guide
http://team-xecuter.com/forums/showthread.php?t=58111

Tried with and without dash patches. aud_clamp checked. Tried nandx, rawflash and even flash360 but no joy.

If i reflashed the 13699 freebot, all work fine. LDV is 2, cb is 6723.

i could give the link of my working and non-working nand if needed.

Please help.

360 Flash Dump Tool says XBR/Freebot Jasper(v4.1) when I load my orig nand. Is this already a patched nand?

 

[manwithoutname]

PM a link to your 13699 freeboot image & CPU key. What board is it and what wiring method did you use (db1f1 or audio_clamp & open_tray)?

 

[WalangAlam]

PM a link to your 13699 freeboot image & CPU key. What board is it and what wiring method did you use (db1f1 or audio_clamp & open_tray)?

pm sent. jasper 256mb with audio_clamp & opentray

I opened again my untouched nandbin and 360 Flash Dump Tool says XBR/Freebot Jasper(v4.1) when I load my orig nand. Is this already a patched nand?

 

[Martin C]

Yes, it means it's an XBR/Freeboot image.

Have you tried building a new image with J-Runner?

 

[WalangAlam]

Yes, it means it's an XBR/Freeboot image.

Have you tried building a new image with J-Runner?

I see. I can't seems to find my untouched nand.bin
I tried rebuilding new Freebot image with j-runner with that xbr/freebot image... I can't create freebot image from a previous freebot image right?

 

[AteOeight]

You can, I think all you have to do is increase LDV... confirmation, anyone?

 

[WalangAlam]

I have a working 13599 freebot image and the cpu key...

 

[manwithoutname]

You can and you don't need to increase the LDV.

 

[WalangAlam]

so where to proceed from here?

 

[manwithoutname]

Give me 5 mins . . .

 

[WalangAlam]

k thanks

 

[Martin C]

can you post your log from j-runner?

How are you flashing it back? Have you tried nandpro for instance?

 

[WalangAlam]

i tried reflashing with nand-x, rawflash and flash360. I didn't try writing using nandpro yet...

jr log
Initializing Nand..
Key already Exists
Load Files Initiliazation Finished
Initializing Nand..
Key already Exists
Started Creation of the xebuild image
KV Info saved to file
---------------------------------------------------------------
xeBuild v1.01.421
---------------------------------------------------------------
building jtag image
---------------------------------------------------------------
E:\Users\Taka\Downloads\preloader\J-Runner v01 Beta (256)\064549790907\nandflash.bin image built, info:
---------------------------------------------------------------
Console : Jasper (big block)
NAND size: 64MiB (system only)
Build : JTAG
Xell : power on console with console eject button
CPU Key : 675D2358C****1E6A0CE2
1BL Key : DD8********9E7B56794FB68563EFA
DVD Key : 35C905CD0*****2808226E09287
CF LDV : 2
KV type : type2 (hashed)
---------------------------------------------------------------
xeBuild Finished. Have a nice day.
---------------------------------------------------------------

press <enter> to quit...

Saved to E:\Users\Taka\Downloads\preloader\J-Runner v01 Beta (256)\064549790907
Image is Ready
INFO: You can write the resulting image to the nand using this app's Write Nand button
However if you wish, you may copy the "Nandflash.bin" and "Xenon.elf" to a USB stick.
Place that in console and boot the console using the eject button.
(this will use rawflash and overcome any bad blocks you may have on your nand)

 

[WalangAlam]

Pmd manwithoutname with my working 13599 freebot image and he PMd me back a freebot 14699 image. Flashed it with j-runner and worked like a charm. Thanks much manwithoutname. Care to share what you did so I will know what I did wrong?

 

[manwithoutname]

I just used XeBuild GUI

 

[WalangAlam]

I just used XeBuild GUI

will try that Thanks much:smile:

 

[WalangAlam]

ah so j-runner doesn't support open_tray yet so i had this problem. note to self.

 

[socalbill]

you can also use a great little program called smc-comparison-tool-v0.3 to compare the smc of your working freeboot and the new image, and change it if it doesn't match.