FALCON CR4XL Falcon Bad block @ 000B , can't boot xell

Bong420

Senior Member
Mar 23, 2005
147
0
Where you live?
I am having issues and I am sure its related to the bad block. The bad block is block B on the Falcon nand.

I have tried to use Martin's guide to bad block remapping and have no success with that.

Console worked fine and was on dash 14719 prior to starting working on it. Green debug light blinks every few seconds. Have tried using martins bad block remap guide and different settings on the chip with no luck. Every falcon I have done with CR4 yet boot on 3 and 7.

I also noticed that it only gave me an error on block B when reading but not writing.
Version: 03
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5773
Falcon/Opus
Reading Nand to C:\Users\user\Desktop\RGHSTUFF\J-Runner\output\nanddump1.bin
Reading Nand
Error: 250 reading block B
Done!
in 2:02 min:sec

Reading Nand to C:\Users\user\Desktop\RGHSTUFF\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Reading Nand
Falcon/Opus
Error: 250 reading block B
Glitch2 Selected
Nand Initialization Finished
Done!
in 2:02 min:sec

Comparing...
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Nands are the same
Jtag Selected
Glitch2 Selected
Jtag Selected
Aud_Clamp Selected
R-Jtag Selected
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully falcon_hack_aud_clamp.bin
Version: 03
Flash Config: 0x01198010
Writing Nand
falcon_hack_aud_clamp.bin
Done!
in 0:10 min:sec
IMAG0295.jpgIMAG0292.jpgIMAG0294.jpgIMAG0293.jpg
 
Last edited:

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
Try the demon/fusion function when writing the ECC, it's in the advanced menu I think.

So load the ECC and choose that option., and it should remap the bad block.
 
  • Like
Reactions: Bong420

Bong420

Senior Member
Mar 23, 2005
147
0
Where you live?
Try the demon/fusion function when writing the ECC, it's in the advanced menu I think.

So load the ECC and choose that option., and it should remap the bad block.

Tried it and didnt work.

Restored back to stock 14719 and then updated to the latest dashboard.

Reread the NAND again, then wrote it the way you said too and booted right to xell!

Thanks

I think it was the bootloader or something, because the versions changed when I updated to latest dash. Must have to be on a further dash than 14719 to use this chip perhaps?
 

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
The issue was not the bootloader but the efuses on the CPU.

As stated in the guide, RJTAG requires 15574 or higher.
Didn't even noticed that :p only that the bad block wasn't remapped.
 

nofeloniesyet

VIP Member
Jan 16, 2011
4,830
128
Nowhere
I am having issues and I am sure its related to the bad block. The bad block is block B on the Falcon nand.

I have tried to use Martin's guide to bad block remapping and have no success with that.

Console worked fine and was on dash 14719 prior to starting working on it. Green debug light blinks every few seconds. Have tried using martins bad block remap guide and different settings on the chip with no luck. Every falcon I have done with CR4 yet boot on 3 and 7.

I also noticed that it only gave me an error on block B when reading but not writing.
View attachment 31027View attachment 31024View attachment 31026View attachment 31025
Didn't even noticed that :p only that the bad block wasn't remapped.
Comparing...
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Nands are the same

bad block was remapped. :)
 

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
Comparing...
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Bad Block ID 000B Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 000B [Offset: 0x2D600]
Bad Blocks Remapped
Nands are the same

bad block was remapped. :)
Not when xell was written ;)
 

Bong420

Senior Member
Mar 23, 2005
147
0
Where you live?
The issue was not the bootloader but the efuses on the CPU.

As stated in the guide, RJTAG requires 15574 or higher.
All I seen in the sticky post for the phat guide was said you could be on the latest dashboard. Searched 15574 in the post and didnt see it anyways so I didnt misread. I figured it might be the problem that the dashboard was too low by myself but I appreciate everyone's help.