New version of XBReboot !

[JFSAINTS]

I've been all day with the XBR  .... to see if someone gives me a clue what is wrong or what to do ...

Have a Xenon, the normal method of prepare the XBR with the config and kV give me the Christmas lights .... the only way to get the XBR is using byncript to inject  KV and config, then  flashing with  nandpro without  errors ..... all good, until I put the hard drive.

The hard drive when I do not corrupt the profile error during the process .... and of course lets not save any games, neither detected anything in content and forget about creating a new profile that goes in a loop. In another console works well and lets me format and other .... but with the XBR nothing. Probe to restore the original nand and the hard drive its perfect .... the problem is with the XBR.

Has anyone had the same thing? Any idea which is the cause ?..... now no longer think of anything. help... Thanks

[ReverseAffect]

1 error reading 3 copy's (same error all 3)didn't do anything with the block error (e:250 b:2b5).
just flashed with it...

falcon 3a works great from a fresh nand(first time read console)
eject also works into xell..

[Rogero]

Guys just to let u know, there another XBR release for Jasper with new SB, file called "XBR_Jasper16_8955_3a.rar"
is this from TeamXBR or the same version released by Geremia !!

 

[Geremia]

there is sort of confusion, me included   

- i didn't do anything about XBR, i don't know anything about rebooting, credits to TeamXBR, i just bought an elite and arranged the official XBRjasper16 image to have the same "page spare bytes layout", cause using the official XBR caused the told problems.
- don't know how many different jaspers16 are out here, could be that jasper16 with 0x71=00 and blockID on sparebyte 0-1 does not work with this new layout.

What is interesting, is that someone has the official XBR working on the same kind of jasper than mine

[Rogero]

there is sort of confusion, me included   

- i didn't do anything about XBR, i don't know anything about rebooting, credits to TeamXBR, i just bought an elite and arranged the official XBRjasper16 image to have the same "page spare bytes layout", cause using the official XBR caused the told problems.
- don't know how many different jaspers16 are out here, could be that jasper16 with 0x71=00 and blockID on sparebyte 0-1 does not work with this new layout.

What is interesting, is that someone has the official XBR working on the same kind of jasper than mine

  yup, that's me with the same Jasper working fine with official XBR3_Jasper flashed using Lflash/Gentoo ( nandpro = error E71 )

 Geremia, please check the PM i sent you so u can check and we can clear out this confusion !!

[preaching]

There are news for nand 256/512?

[SanPedro_]

There are news for nand 256/512?

Another one waiting here for some kind of news

[Arakon]

If there were, they would be mentioned here.

[xboxbman]

Can anyone help me figure out how to update Xell to Redline's version on the new XBR for falcon?  Trying to flash it with

Code:

nandpro lpt: -W16 xell.bin 30

, as I did when only xell seems to replace the boot, as the updated Xell will boot from either the power button or the eject button.  I've tried to update just by renaming the new xell to updxell.bin, and placing it on a usb, but again, it replaces the boot and the 360 will only boot to Xell.

[jelle2503]

thats because xell @ 30 is a backup xell if you would've bothered reading the XBR readme


the xell payload you are using probably is bigger then 0x30-0x3F

[MastaG]

I've been having some issues with that too on my Zephyr using 3b.
nandpro.exe xbr.bin: -W16 xell-1f.bin 30 F
The xell-1f.bin is from redline which is posted here in the Software section.
It won't boot with the eject button.

[Shaun]

Can anyone help me figure out how to update Xell to Redline's version on the new XBR for falcon?  Trying to flash it with

erm it already has it, at least the 3a ver i got does.
boot with eject and you see your cpukey and dvd key in glorious white on blue text

[Geremia]

Thanks Rogero for the tests and the dumps.
Basically the old XBRjasper16 worked by some miracle only if you flashed without relocating blocks.
If you relocated a block, the nand controllers searches it at end and can't find a correct one, in my case for example for block 23B it searches in latest block spares for 00 3B 02 and finds an oldstyle 3B 02 00 and gives up.
For filesystem writing, the console writes the new blocks in the new format, but cause of some lucky stuff, it can work anyway.

[viericrespo]

Thanks Rogero for the tests and the dumps.
Basically the old XBRjasper16 worked by some miracle only if you flashed without relocating blocks.
If you relocated a block, the nand controllers searches it at end and can't find a correct one, in my case for example for block 23B it searches in latest block spares for 00 3B 02 and finds an oldstyle 3B 02 00 and gives up.
For filesystem writing, the console writes the new blocks in the new format, but cause of some lucky stuff, it can work anyway.

Hi,

forgive me for doing this intrusion but I'm another one with that kind of Jasper, and I got the official version of XBR to work.

The KV and Config blocks writing with Nandpro gave me E79, so I used Bincrypt instead for inserting them.

Then flashed the XBR image and got no problems at all.

Regards  

P.S. I have no bad blocks in my nand

[ulron]

Basically the old XBRjasper16 worked by some miracle only if you flashed without relocating blocks.

sorry, all this info actually is here already - just want to make sure i get it right:
the only difference is in the spare blocks which are used to make up for defective ones, so if i don't have any bad blocks until now and i already flashed _3 everythings ok since when writing to the spare blocks the "errors" will be corrected?

if of interest: my jasper ( kv reads 00 01 00 and flashtool0.90 only reports garbage) is working flawless, flashed via lpt.

[Rogero]

Basically the old XBRjasper16 worked by some miracle only if you flashed without relocating blocks.

sorry, all this info actually is here already - just want to make sure i get it right:
the only difference is in the spare blocks which are used to make up for defective ones, so if i don't have any bad blocks until now and i already flashed _3 everythings ok since when writing to the spare blocks the "errors" will be corrected?

if of interest: my jasper ( kv reads 00 01 00 and flashtool0.90 only reports garbage) is working flawless, flashed via lpt.

I had also flashed 2 Jaspers16 new SB revision with the initial XBR3_Jasper and i had them both working great without any single error ( i didn't remap any bad block before flashing ) but after Geremia addressed the difference between the 2 nand revisions ( old Southbridge Jasper and the newer Southbridge Jasper ) it became clear now that to have a correctly working flash ( if you have the newer style Jasper/SB ) you must use the new style XBR which is released under name "XBR_Jasper16_8955_3a.bin" or the one released by Geremia too ( Geremia: seems like you have triggered the error for TeamXBR to correct it and release the revised version    )

I just finished re-flashing both consoles with XBR 3a  and got them both working from first time too. ( knowing now that i have a correctly flashed nand eventhough before i had the consoles working fine too ).

[JQE]

So i have Xell working on my xbox. Boots up fine, but i can't get the xbox to boot the Gentoo live CD. is there something that needs to be done to get it to boot the live CD?

I had to burn it to a DVD as i ran out of blank CD's, would this work?

[Eiji]

BTW, is it necessary to update a new out-of-the-box Xbox which has kernel 6xxx to 7371 before dumping NAND and then flashing XBReboot v3 or is there no reason to update and blow fuses to update to 7371?

[iLLNESS]

BTW, is it necessary to update a new out-of-the-box Xbox which has kernel 6xxx to 7371 before dumping NAND and then flashing XBReboot v3 or is there no reason to update and blow fuses to update to 7371?

the update is to prep your box for avatars/etc.

from what i understand people get it to run no issue, but why not just make things easier for yourself and update to 7371. not like your losing anything.

[Arakon]

For XBReboot, there's no need to update first. That's only for freeboot, as the freeboot creation process expects 7xxx files.