New version of XBReboot !

[littlestevie360]

doesnt loook like its been mentioned yet, but title updates DO work as is from usb/internal hdd. no more patching xex needed either all confirmed.

this is great! i was gonna post a thread about it but wasn't sure why it wasnt already posted so i never bothered heh

I forget if it's media check then region check but jap game doesn't play on aus console here due to region restrictions, so it's not total patching, thus some patching is still required :p

[Tony_Amigozs]

thank freeboot for the fix lol

XBReboot obviously is much better now then Freeboot.

[Geremia]

I arranged the xbr jasper16 image for my own elite, which has the new southbridge and 16MB, difference is just first 3bytes in each spare, rotated right 1byte and ecc recalculated, and address 0x71=01

http://rapidshare.de/files/48928634/XBR_Jasper16newSB_8955_3.zip.html

it's for jasper16 with flashconfig=00023010

I have 2 Jasper16 with flashconfig=00023010 consoles which had the XBR_8955_1 version , so i downloaded the new XBR_Japser_8955_3 from xbins and flashed it using lflash and gentoo ( i had to edit lflash.c and change the flashconfig to 00023010 ) and they are working great.
My question is what's the difference between the official Japser16 XBR3 release and your Version !! any issues in the official XBR3 for Jasper16 ??

the difference is into the first 3 bytes of the spare bytes, and address 0x71=01. These are the difference i saw from my elite dump (mid june 2009, southbridge without the metal circle) and an old elite dump i got times ago, so i just arranged the xbr image to match my new elite style.
Don't know, probably the flashconfig value is not the point, but official XBR does not work, or better, it works when it does nand reading (xell boots fine), if i insert my kv with +w (so porting my KVraw.bin blockID position to "oldstyle") xell decrypts the kv correctly.
What goes wrong, is when the console has to write to nand FS, and it happens at veryfirst (re)boot to dash: it has to write a new extended.bin but the new writing is done in the "new style" (first 3 bytes of spare rotated), so the FS is messed up and console hangs on first frames of bootanim, sometime it display E79 (probably because of unable to write the extended.bin?!??)

In your jasper dumps, do you see 0x71=01 and blockID into nand spare bytes at position 1-2 instead of oldstyle position 0-1?

[jelle2503]

In your jasper dumps, do you see 0x71=01 and blockID into nand spare bytes at position 1-2 instead of oldstyle position 0-1?

i think I have new SB jasper (0x71=01) .. but how to check blockID's? forgive my noobness

ill maybe have a go with this XBR image you uploaded will report back if i do..

[Geremia]

i think I have new SB jasper (0x71=01) .. but how to check blockID's? forgive my noobness

flash tool v0.90 reports crap instead of file listing
hexedit your raw KV.bin extracted with nandpro, at address 0x200 you see 00 01 00  instead of oldstyle 01 00 00

[jao123]

I arranged the xbr jasper16 image for my own elite, which has the new southbridge and 16MB, difference is just first 3bytes in each spare, rotated right 1byte and ecc recalculated, and address 0x71=01

http://rapidshare.de/files/48928634/XBR_Jasper16newSB_8955_3.zip.html

it's for jasper16 with flashconfig=00023010

Thanks Geremia, but my Jasper 16M RE5 ver is not working with your XBR fix. But is much better because I've got E71 instead black screen.

[maximilian0017]

Reflashed all my Xenons (usb Pic flasher) and they are all working perfectly.

Great work guys!!!!

[][e]

Reflashed my Zephyr back to 8955_1 and booting as normal (still same freeze problems with games etc). Patiently waiting for 8955_3c or later to arrive. These are the challenges you face when modding on the bleeding edge

[jelle2503]

flash tool v0.90 reports crap instead of file listing
hexedit your raw KV.bin extracted with nandpro, at address 0x200 you see 00 01 00  instead of oldstyle 01 00 00

0x200=00 01 00 in my KV.
but flash tool 0.91 is listing files fine

[xboxbman]

Just a little problem... I had the old version of XBReboot and had updated Xell for 1024 x 768 (xenon_1921_hack-20090911). Now, the new XBReboot overwrote Xell to it´s lower resolution (previous) form, and it´s all black in the VGA monitor, although when booting the Dash everything works perfect.

I tried to inject again the same file (xenon_1921_hack-20090911) in the New XBReboot, but It seems it ovewrites the bootloader and Xell...

Now I can only boot in Xell with 1024x768, but can´t boot the 8955 Dash.... Is there any way to overwrite only the updated Xell without the bootloader that comes in this file?

Thanks

If you broke the bootloader... probably you have injected xell to a wrong block
Take a look at this

XBReboot Block Layout:
Ox00 - 0x2F Xell Boot firmware
0x30 - 0x3F Backup Xell
0x40 - 0x4F freeboot.bin or freeboot-manual.bin (patch engine core)
0x50 - 0x61 Alternate CG
0x62 - 0x64 Spare blocks
0x65 - 0x65 Patch.bin, patches for bootloaders and kernel
0x66 - 0x8F Alternate CB/CD/CE
0x90 - 0x?? Flash file system

To update the backup xell use this command

nandpro XBR.bin: -W16 xell.bin 30

*W (in capital) adds ECC to a "file" without it (xell has not ECC because is the binary compliled, you need to add ECC when writing)

I have been trying this, and after applying redline's xell, xell will no longer boot, i just get a black screen. 

Anyone else getting this?

[fred444]

Will there be another Zephyr update ?

Something like Zephyr_3b ?

I brought mine back to life after the bad _3 flash, but dont want to flash the current _3a update becaus many people on xb-h and xb-s report that they only get their power led working 

[RimbaldoTeobaldo]

Just a little problem... I had the old version of XBReboot and had updated Xell for 1024 x 768 (xenon_1921_hack-20090911). Now, the new XBReboot overwrote Xell to it´s lower resolution (previous) form, and it´s all black in the VGA monitor, although when booting the Dash everything works perfect.

I tried to inject again the same file (xenon_1921_hack-20090911) in the New XBReboot, but It seems it ovewrites the bootloader and Xell...

Now I can only boot in Xell with 1024x768, but can´t boot the 8955 Dash.... Is there any way to overwrite only the updated Xell without the bootloader that comes in this file?

Thanks

If you broke the bootloader... probably you have injected xell to a wrong block
Take a look at this

XBReboot Block Layout:
Ox00 - 0x2F Xell Boot firmware
0x30 - 0x3F Backup Xell
0x40 - 0x4F freeboot.bin or freeboot-manual.bin (patch engine core)
0x50 - 0x61 Alternate CG
0x62 - 0x64 Spare blocks
0x65 - 0x65 Patch.bin, patches for bootloaders and kernel
0x66 - 0x8F Alternate CB/CD/CE
0x90 - 0x?? Flash file system

To update the backup xell use this command

nandpro XBR.bin: -W16 xell.bin 30

*W (in capital) adds ECC to a "file" without it (xell has not ECC because is the binary compliled, you need to add ECC when writing)

I have been trying this, and after applying redline's xell, xell will no longer boot, i just get a black screen. 

Anyone else getting this?

Well... I reflashed back my orig. 4532 kernel and the system booted normally. I then flashed back the XBR.bin normally, but only with the kv.bin... without the rawconfig.bin.... It still gets a blank screen when I try to include it.... Is there a solution for this? It never worked when I tried to include rawconfig....

I think that what happened with xell is that this version of XBR may have disabled the Boot-xell-through-the-remote-control option. If I try to boot Xell using the remote the 360 turns on, keeps turned on without any strange lights, but the screen is blank. If I turn it on normally (on button on the remote, or the on switch on the 360), it boots to the 8955 dash. If I turn on through the Eject button, Xell boots normally (in 1024x768) .... So Xell, in my case... is only bootable through the eject button. I didn´t try to update using Redline´s Xell... It´s working.... I´ll leave it this way... eheheh... 

[xboxbman]

It is booting fine via eject with the version of Xell that comes with it.  It is only when I try to update it to redline's xell that it craps out.

[selyb]

TEAM XBR r0X0rZ!
this is my belated christmas present

[X-QlusioN]

LOL, I'm having the weirdest problems ever...

So a Xenon with XBR_3

Xell boots perfectly every time using eject
When using the power button, 9/10 times it'l give the center green light but no screen, no error, no circling corners
The other 1/10 time it gives me a E79 error (1033)

Now if I insert a disc (used the Gentoo disc siince I just used it to flash) first boot is like the 9/10 time one (no error, just center green light), but the second boot iis to dash (aka working XBR)

Weird stuff

[fred444]

I flashed mine back to _1

But it doesn't boot... Xell works fine everytime, but with pressing power button i get E71 everytime 

The same image worked before trying to update to _3 !

[intealls]

But it doesn't boot... Xell works fine everytime, but with pressing power button i get E71 everytime 

I've got a Xenon, so this may not work on your Zephyr. I've had this problem twice, trying to power up the box after a flash would result in a freeze and then RROD. I resolved it both times by first erasing the flash (nandpro lpt: -e# (#= 16, 256, whatever)) and then flashing the nand again.

[Arakon]

I had E71 previously too, a reflash fixed it.

[fred444]

I reflashed it 2 times.

First with LPT, then with lflash . . .

Everything flashed without errors (except the usual lflash ones)

erasing nand does not make sense when writing the full 16mb flash, because every single bit is written new

[intealls]

erasing nand does not make sense when writing the full 16mb flash, because every single bit is written new

Probably not, but if you've tried everything else, why not give it a shot?