new freeboot released runs unsigned xex's!!

[dtrmad2004]

how can you tell if you have a bad block(s)?  I absolutely can't get xbr to boot, I just get flashing red and green lights.

Nandpro tells you about bad blocks when you dump your flash.

Are you using Nandpro20 a? use Nandpro20 b. I was getting GRod flashing with a, used b and it worked.

[GffMaC]

Yeh how do you know which are free?

Ive got two bad blocks DF and F3 so I could do one like you said Arakon but what could I use for the other?

And sorry Arakon I PM'd you then saw your sig   I want to keep my balls please.

[Arakon]

Use 3FF and 3FE then. The last few blocks are free.


I noticed an odd issue.. if there's an USB HDD connected at boot, the console also gives E71.. if I plug it in later, it's fine.

[Hoax]

now I flashed the falcon _1 with own kv and config and the box does nothing.. aofter powerup the middle led is on, the ring of light does nothing.
when holding X on boot, xell is starting and works fine.. I dont get any tv/tft output (hdmi, compos., compon.)

any idea ?

[joeyddr]

so i followed the directions
1) Extract KV and Config blocks from orig.bin
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
2) Inject those blocks into XBR.bin
nandpro XBR.bin: -w16 rawkv.bin 1 1
nandpro XBR.bin: -w16 rawconfig.bin 3de 2
3) Flash result
nandpro lpt: -w16 XBR.bin

and i get 0022  now when i boot up....

if i flash back the older release with the _0 and just my kv and redline's xell patch patched to it... works fine.

[irishwhip]

i had the same problem, i just patched the kv, didn't bother with the rawconfig, and it worked.

[Crazziee]

Use 3FF and 3FE then. The last few blocks are free.


I noticed an odd issue.. if there's an USB HDD connected at boot, the console also gives E71.. if I plug it in later, it's fine.

Thanks for the help with the Bad blocks I can now boot XBR 

[sandungas]

so i followed the directions
1) Extract KV and Config blocks from orig.bin
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
2) Inject those blocks into XBR.bin
nandpro XBR.bin: -w16 rawkv.bin 1 1
nandpro XBR.bin: -w16 rawconfig.bin 3de 2
3) Flash result
nandpro lpt: -w16 XBR.bin

and i get 0022  now when i boot up....

if i flash back the older release with the _0 and just my kv and redline's xell patch patched to it... works fine.

This is not the way you must do it

First, you need to extract the same block (the damaged one) in both files (your nand dump & the new nand dump)
The one extracted from your nand dump has a "mark" that idenfity it like a "bad block"

After this... you need to write this bad block (that is marked bad) to the same position in the new file (this prevents the console to use it, because this block is really damaged in your nand, and cant be repaired nor used, and must be marked as bad)

The last step is to relocate the block extracted from the new dump to the "block repair area"

[joeyddr]

so i followed the directions
1) Extract KV and Config blocks from orig.bin
nandpro orig.bin: -r16 rawkv.bin 1 1
nandpro orig.bin: -r16 rawconfig.bin 3de 2
2) Inject those blocks into XBR.bin
nandpro XBR.bin: -w16 rawkv.bin 1 1
nandpro XBR.bin: -w16 rawconfig.bin 3de 2
3) Flash result
nandpro lpt: -w16 XBR.bin

and i get 0022  now when i boot up....

if i flash back the older release with the _0 and just my kv and redline's xell patch patched to it... works fine.

This is not the way you must do it

First, you need to extract the same block (the damaged one) in both files (your nand dump & the new nand dump)
The one extracted from your nand dump has a "mark" that idenfity it like a "bad block"

After this... you need to write this bad block (that is marked bad) to the same position in the new file (this prevents the console to use it, because is really damaged, and cant be repaired nor used)

The last step is to relocate the block extracted from the new dump to the "block repair area"

but i dont have any bad blocks from this nand? the first version worked fine XBR_Xenon_8955_0.bin when i patched my kv and redlines xell patch it boots up right away.. with XBR_Xenon_8955_1.bin i patch my kv and my config like the instructions say and i get 0022.

[sandungas]

Ops, then my mistake, i thought that you had bad blocks

[joeyddr]

i am going to try the new one now with just patching my kv into it instead of conf and kv because the first one worked with just kv patched.

[ddxcb]

Joey u prob have a 1921 CB because XBR0 is 1921 and XBR1 is 1920 =< only

[cory1492]

I noticed an odd issue.. if there's an USB HDD connected at boot, the console also gives E71.. if I plug it in later, it's fine.

Did you by chance have a default.xex in the root of the drive?

[stuntpenguin007]

I checked my original nand dump and the dump I got after flashing xbr and reading it back.  Both had 31 bad pages and 12 bad blocks.  my read back xbr had 1305 empty pages, and my original dump had approx. 1800 empty pages.

Is this fixable?  I have my cpu key if that counts for anything.  I know bad blocks can be written towards the end... but 12?  and what about the pages?

[NotMe]

I have a bad block at 0x1.  Degraded said it was mapped to 0x3FF.  I grabbed my kv from 0x3FF and put it in xbr at 0x3FF and did everything else like normal and it worked for me.

Thank you.  I had a bad block at 0128, tried flashing my falcon with the new XBR_1 for Falcons.  E71.  Opened the original.bin in a hex editor and changed 2007 to 2005.  Ran degraded on my original.bin and it said:

Note: Bad Block @ 0x128
Note: Block 0x128 found at 0x3FF

So I did the following commands and now have a booting falcon with XBR:

Code:

nandpro XBR.bin: -r16 X128.bin 128 1
nandpro usb: -w16 X128.bin 3FF 1

Thanks again and cheers mate.

[joeyddr]

ok so just writing my kv to the _01 file worked fine. 

[rkkman]

@domina

Check this out here - While this doesn't show the loader it will help you get the idea on what you will have to do to make one.  His other video does show the loader in action.

1. http://www.youtube.com/watch?v=I0wHm9jNdbs

2. http://www.youtube.com/watch?v=30_-t6BLSSw

I just did it with Mame and it worked.  The only thing I cant figure out is how to edit the ini to read the roms location.  Can anyone help?

Thanks

[Arakon]

I noticed an odd issue.. if there's an USB HDD connected at boot, the console also gives E71.. if I plug it in later, it's fine.

Did you by chance have a default.xex in the root of the drive?

yep.

[jester]

There are tons of people complaining/asking about XBR here, and although the patches are the same, freeBOOT and XBR are obviously not related. Maybe this topic should be split up so we can keep track of who's having problems with what?

[Hoax]

Here's my problem again but with additional information. I try to explain every step I did. Maybe someone can help.

I flashed the XBR 8955_1 to my falcon box with my own config and kv:

(nandpro 2.0b)
nandpro nanddump.bin: -r16 rawkw.bin 1 1
nandpro nanddump.bin: -r16 rawconf.bin 3de 2
nandpro xbr.bin: -w16 rawkv.bin 1 1
nandpro xbr.bin: -w16 rawconf.bin 3de 2
nandpro lpt: -w16 xbr.bin

When powering on I only get the middle led to work. The ring of light isn't doing anything. No videooutput, just black screen
When holding "X" on bootup, XeLL is booting fine.

Did a power cycle after flash and tried with every videomode (hdmi, composite, component, vga)...

CB: 5761, K: 7371, PAL Box, No Bad Blocks, Dump also runs fine.


So is here anyone who can help please? Thank you!