XeLLous OK, unable to install FreeBoot

[arken]

I have installed JTAG on Falcon CB5770 using boxxdr wiring with transistors and AUD_CLAMP.
Everything went well, dumped the NAND 3 times, no differences, only 2 bad blocks remapped.
After that I flashed Xellous (SMC patched for AUD_CLAMP).
The box is booting in Xellous, I am able to get CPU key.
Then the problems begin:
After installing a freebot the box just going to blank screen, the console is booting normal - no red lights or errors, it just shows blank screen.

Tried the following:

1. Building with BestPig Freebot Toolmaker, Jtag tool, Easy Freebot GUI and manually
2. Patching the smc.bin manually with smc_io
3. Flashing with Xellous and with NAND interface
4. Remapping the bad blocks on original image and the new one
5. Using 12611 and 9199 dashboard files (remapped or not)
6. composite or HDMI cable

I am running out of ideas.
Can someone help, please. And sorry for my english.

 

[manwithoutname]

Have you got a freeboot 9199 dash working on the console?

 

[arken]

Have you got a freeboot 9199 dash working on the console?

No. I builded 9199 dash with JTAG tool 1.74, patched the SMC manually, and remmaped bad blocks in the new image before flashing - didnt work.
Its a pity - the box is actualy hacked, but cannot load the dash

 

[manwithoutname]

You done it in the wrong order.

Download the files in my signature, replace the SMC files in Jtag tool 1.74 with those you downloaded (12kb each) and ensure that jtag tool isn't running when you do this. Compile freeboot using your obtained CPU key, remap the bad blocks and flash. Report back and then will take it from there.

 

[arken]

Sorry, followed the instructions exactly, and still no go.

 

[manwithoutname]

Post a screen dump of 360 flash tool or degrader showing the bad blocks. And state exactly with it how you remapped the bad blocks in freeboot image after you created it.

 

[arken]

[FONT=Arial][SIZE=3]nandpro[/SIZE][/FONT][FONT=Arial][SIZE=3] updflash.bin: -r16 badblock06A.bin 06A 1[/SIZE][/FONT][FONT=Arial]
[/FONT][FONT=Arial][SIZE=3]nandpro [/SIZE][/FONT][FONT=Arial][SIZE=3]updflash.bin[/SIZE][/FONT][FONT=Arial][SIZE=3]: -w16 [/SIZE][/FONT][FONT=Arial][SIZE=3]badblock06A.bin [/SIZE][/FONT][FONT=Arial][SIZE=3]3FF 1[/SIZE][/FONT][FONT=Arial]
[/FONT][FONT=Arial][SIZE=3]nandpro[/SIZE][/FONT][FONT=Arial][SIZE=3] updflash.bin: -r16 badblock101.bin 101 1[/SIZE][/FONT][FONT=Arial][SIZE=3]
nandpro [/SIZE][/FONT][FONT=Arial][SIZE=3]updflash.bin[/SIZE][/FONT][FONT=Arial][SIZE=3]: -w16 [/SIZE][/FONT][FONT=Arial][SIZE=3]badblock101.bin [/SIZE][/FONT][FONT=Arial][SIZE=3]3FE 1[/SIZE][/FONT]

Thank you for you time

 

[manwithoutname]

Looks right to me. There must be something gone wrong somewhere. I take it that you created freeboot from your original non modified dump?

You got 2 options, I can either create one for you on your computer remotely via Team Viewer or you could send me your files and I'll make one for you.

 

[arken]

OK. Thank you. Please check you PM or contact information.

 

[arken]

After rewiring the JTAG - using TRAY_OPEN instead of DB1F1 for TDI connection, and AUD_CLAMP for TMS, and building XeLLOus with smc.io patched for that kind of wiring the box again is booting fine into XeLLous, but shows black screen when freeboot is installed. Also Free360 linux can't boot too, the box freezes at "Please wait a moment while kernel loads..."
manwithoutname (many thanks) helped me a lot and finally suggested that changing the transistors with diodes maybe will solve the problem. But isn't the JTAG hack used to inject code at the boot stage, and since xellous is booting the freeboot should boot too?
Any advice will be highly appreciated.

 

[big_ted]

if xellous is working ok,
try this, make your image don't move the bad blocks to the spare area, rename it to flashdmp.bin (make sure it dosn't end up flashdmp.bin.bin easy mistake) put it on the root of a usb stick and boot up xellous, this will flash your image and auto remap the blocks. It's not a wiring issue if xell is working its a bad block issue.

Ted

 

[arken]

Thank you for answering.
The Xellous does not search for flashdmp.bin at startup. Only these:

updslot0.bin 
updslot1.bin
updpatch.bin
updflash.bin

Using updflash.bin without remapping, produced the following result:
(please see image attached). The console boots to black screen after flash, no red lights, no green lights flashing, just black screen. I am still able to boot into XeLLous with eject button.

Removed the JTAG wiring, flashed back original nand - black screen again. Rewired with diodes, flashed xellous again, console boots into xellous, but no freeboot or Linux

 

[big_ted]

my bad should have read updflash.bin sorry.
try it this way,
dump the orig nand,
remap the parts from the spare area back to the correct places,
make you fb image
rename it updflash put on usb and boot up xellous.

Ted

 

[arken]

I remapped my original nand dump that way:

nandpro fullnand_orig.bin: -r16 badblock3FF.bin 3FF 1
nandpro fullnand_orig.bin: -w16 badblock3FF.bin 06A 1
nandpro fullnand_orig.bin: -r16 badblock3FE.bin 3FE 1
nandpro fullnand_orig.bin: -w16 badblock3FE.bin 101 1

Builded the image from remapped dump, flashed - nothing changes. Black screen only.

 

[arken]

Anyone? Xellous is booting OK, I have a triple checked nand, all keys. I dont want to throw away the box.

 

[arken]

To revive an old thread
I had time last few days and tried again to setup my box.
I readed again the NAND from xellous web interface and the interesting thing is that 360 flash tool does not show bad blocks in the new (reflashed) image.
I had 2 bad blocks in the original NAND image.
Does this mean that my NAND is completely erased including the information where bad blocks are remapped? (something like MBR/FAT table in hard disks). Is there a way to initialize the NAND and restore bad sectors table?
Thank you.

 

[M AzeeM K]

^ No. The thing is that when you make freeBOOT image, the bad blocks just disappear. And if you read the NAND once that image is written, ofcourse you won't find any bad blocks.

Anyways, what you should do is to make a new freeBOOT image using an unremapped original NAND image. Then once created, the bad blocks won't be present in the freeBOOT image. Now, remap the freeBOOT image as if it had bad blocks at exactly the same place as the original NAND image. Once done, write this image to the console. Do a power cycle. Hopefully you'll be greeted with the Welcome screen.