Sponsored Links

Sponsored Links

XBReboot v0.05 8955_1 for Zephyr, Falcon and Jasper-16 is out!


Sponsored Links
242w ago - As a follow-up to the previous release comes XBReboot v0.05 8955_1 for Zephyr, Falcon and Jasper-16 today.

They are all available with the latest 8955_1 patch revision now, so each 16mb motherboard can now run XBR v0.05 8955_1!

Only support for Jasper 256/512mb motherboards is still missing now. Don't forget to inject your own KeyVault and Config before flashing.

Download: XBR Zephyr 8955_1 / XBR Falcon 8955_1 / XBR Jasper 16 8955_1 / 360 Flash Tool v0.90 / FindSecData v0.61

XBReboot Block Layout:

Ox00 - 0x2F 4548 boot FW
0x30 - 0x3F Backup Xell
0x40 - 0x4F XBRfw.bin Rebooter core
0x50 - 0xBF Patch.bin Kernel and patches
0xC0 - 0x?? Flash file system

Version: XBRfw 0.5beta Initial
The fw version need not change for any given Patch.bin

Patch.bin is what needs to change for any new patch
The following are Patch.bin versions

8955_0: Initial
Don't need xextool:
automatically detect correct key for dev or retail xex.
Drag and drop any xex to cdr.
No specific secdata.bin or crl.bin requirements.

8955_1:
Add support for PIRS
Fixed Backup Xell

HowTo:

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

Notes:

There is no need to unpack and repack pirs files!
This is a limitation of freeboot. Not XBR.
Aside from that major difference, all functionality is the same.

Individual sections can be updated or extracted seperately using nandpro.

The image can be made to work for all 16M consoles.

The standard method of using build.py can be used to change the 4548 boot FW portion of the flash to the console type.

Generally:

Create the image as described above.
The command to rebuild it might look like this:

build.py XBR.bin CB CD update.bin xell-1f.bin XBRfw.bin smcp.bin

Then the .ecc file result from build.py would be "flashed" back into the XBR

nandpro XBR.bin: -w16 image_00000000.ecc



Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!

Comments 10 Comments - Go to Forum Thread »

• Please Register at PS3News.com or Login to make comments on Site News articles. Thanks!

PS3 News's Avatar
#5 - PS3 News - 238w ago
Here are some XBReboot v0.05 8955_3 and 8955_3a (for all 16mb Motherboards) updates attached below.
A new 'patch'-version of XBReboot has been released for all 16MB NAND motherboards solving the freezing/lagging issues and removing the need to patch XEX files (media check etc).

XBReboot is an image you can flash on your onboard NAND that will allow you to 'reboot' a JTAG-exploitable (~pre-mid-June MFR date, pre 8xxx kernel) 360 in a patched 8955 kernel which makes homebrew XDK (unsigned XEXs etc) possible.

*Update* There was an issue with the SMC code in the Zephyr and Falcon releases. 8955_3a has now been released for these 2 motherboard revisions with good SMC.

From readme/nfo:

* Who wrote this?
Talented members of XBH contributed in many ways. You know who they are. TeamXBR assembled the parts, coded the utilities, and glued it all together to make it work.

* How does it work?
Both XBR and Freeboot use a "patch engine" to apply patches to the bootloaders as the console reboots. For Freeboot, this is "freeboot.bin" or "freeboot-manual.bin"; For XBR, its "xbrfw.bin" Both of these binaries are based on xell type start up code, and are launched by the exploit. The code then applies patches contained at block 0x65+, and restarts the system.

* What went wrong?
Earlier versions of XBR used the same CB/CD pair to start the 8955 kernel as the exploit. Freeboot, using a dual nand setup, used the older bootloaders to start the exploit, than used the newer bootloaders on the alternate flash to start the kernel.

The problems were not related to the patches used by XBR, but rather the use of the older bootloaders. Please try to control yourselves if problems arise, they can always be fixed. Dont do anything crazy like start conspiracy theories, buy a cygnos, wire up a dual nand or xd card, rip out a big nand to swap in a smaller one etc, etc. Have a little patience, have a little faith :P

* So whats the fix?
1) Add a copy of the new bootloaders to flash.
2) Create patches to use the newer relocated bootloaders on reboot.

It was easier to re-use the freeboot.bin patch engine to accomplish this task.
The freeboot patches themselves are not used. XBR continues to use its own patches, however, the freeboot.bin patch engine will be used to apply them.
This also allows custom patches to be applied, in the format used by freeboot.

8955_3a:
- Zephyrs and Falcons now built with correct smc.

8955_3:
- Uses 6750 as the alternate CB to allow easy support for all hardware versions.
- No changes made to patches, exact same functionality as 8955_2.

8955_2:
- Add a copy of the new bootloaders to flash.
- Create patches to use the new relocated bootloaders on reboot.
- Translated existing XBR patches to use the freeboot.bin patch engine.
- Fixed build file to use CB/CD 1921 for all xenon.
- Eliminate media binding path checks, run xex from all media without patching.

* 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

* HowTo:
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

* Notes:
There is no need to unpack and repack pirs files!
This is a limitation of freeboot. Not XBR.
Aside from that major difference, all functionality is the same.
Individual sections can be updated or extracted seperately using nandpro.

JeffJ's Avatar
#4 - JeffJ - 240w ago
Yes it does. You can use any drive.

j c's Avatar
#3 - j c - 240w ago
Does XBR offer the same feature as freeboot where you can use any 2.5" SATA in the internal enclosure?

JeffJ's Avatar
#2 - JeffJ - 242w ago
There is a guide here on how to flash a linux kernel to a Xenon board with th16MB flash rom.. this is what you will want.

jabberosx's Avatar
#1 - jabberosx - 242w ago
I just got hold of an xbox with Hitchi drive. Its the one without HDMI. Now over to the FAQ/Help sections to figure out whats what!!

Thanks.

Sponsored Links

Sponsored Links
Sponsored Links

Sponsored Links







Affiliates - Contact Us - PS3 Downloads - Privacy Statement - Site Rules - Top - © 2014 PlayStation 3 News