New version of XBReboot !

[neonpolaris]

It sounds to me like the new version of XBReboot obsoletes freeboot.  Is there any advantage that freeboot has now?

[wickwack]

hmm nope freeboot as of today is inferior to xbr in everyway... aparently they dont even have a more dedicated development team...

if ur still unbanned then im not sure if having a cygnos + freeboot might allow you to stay unbanned doing the obvious... but not likely

[Eiji]

What is the common manufactured date of Jaspers with the new southbridge?

[Rogero]

What is the common manufactured date of Jaspers with the new southbridge?

beginning from June 2009 up are all with new Southbridge, before June 2009 i'll have to check for more Jaspers and report back

[terzi]

Hi,

I have Jasper 16M version and dated on 2009/02/04.

I have all following conditions true:
- original.bin: 0x71=01
- kv.bin: 0x200 = 00 01 00
- Flash tool 0.90 shows file list incorrectly
- Bad block remover shows bad block at 0x7D00 instead of correct one 0x27D

Bad block remover shows log below. Is that correct with new SB?

== Analyzed successfully ===========================
Erasing 0x20 Spare Blocks at offset 0x00FFC000
Reading Block ID 0x027D at offset 0x00A43A00
Copying Block ID 0x027D at offset 0x0107BE00
Zeroing Block ID 0x027D at offset 0x00A43A00
== Remapped successfully ===========================

I had no luck with any released xbreboot so far. Used infectus to flash nand. Xell works fine with XBR_Jasper_16_8955, but dashboard gives only E79. All dumps are done by injecting with nandpro20b.

For test I created new dumbs with following settings:
nandpro orig.bin: -r16 rkv.bin 1 1
nandpro xbr.bin: -w16 rkv.bin 1 1

as xbr_nanpro.bin

and with BinCrypt2 Build 28:
extraction:
  raw Flash bin - > extract - (operation: nothing) - > key vault (from orig.bin to kv.bin)

and replace:
  raw Flash bin -> replace - (operation: nothing)  -> key vault (from kv.bin to xbrbin)
as  xbr_bincrypt.bin

Then used NandComparer v1.2 to compare those dumps. And result is here:
1 non-matching block(s) found 1

So my next step is use that xbr_bincrypt.bin with lpt. Has anyone had similar problems or is there something iam doing wrong? I read somewhere that bincrypt solved problems.

[Shaun]

for a start your missing the config blocks

[terzi]

for a start your missing the config blocks

Thanks for your reply.

I forgot to mention that i had used both ways. With and without config.

[ulron]

[...]
For test I created new dumbs with following settings:
nandpro orig.bin: -r16 rkv.bin 1 1
nandpro xbr.bin: -w16 rkv.bin 1 1
[...]

if you really use the command as you typed above you just dump and write ONE (!) sector - might that be the problem?

[viericrespo]

I can confirm that the Geremia version of XBR for 16MB Jasper (3a), it's working flawlessly.

Just flashed it with lflash and 0 problems.

Very thanks to him

Regards

[Rogero]

for a start your missing the config blocks

Thanks for your reply.

I forgot to mention that i had used both ways. With and without config.

I Never used the config blocks, just inject the kv.bin WITH NandPro on all XBR releases, and on different console models ( i've done Xenon, Zephyr, Falcon and Jasper16 )
the config blocks will never cause a problem running XBR if u dont inject them, u just have to go through the console initial setup at first boot and that's it, then the 360 writes back your new config blocks to the nand.
Errors like E71 (sometimes E79) are always related to Flashing problems and mostly to Bad Blocks and remapping them correctly.
E79 is mostly a sign that u have something wrong in the Jtag wiring ( diodes, etc... ),
always try to get Xell loading to verify ur Jtag wiring, even if u had to Flash a standalone Xell image.

[terzi]

Xell is working perfectly. I managed to get CPU key. So it can't be about bad jtag hack. Is that bad block mover working corretly with new version of jasper dump?[color=][/color][color=][/color]

[Shaun]

the config blocks are much more todo with continuity rather than the initial setup.
There are many config blocks, the one used for xbr is very much needed as it stores console specific info such as mac address and cpu and gpu thermal calibration values.
There is also a smc config block, both of these are static config blocks.  You are thinking of are settings ones which are not static and take up the next free space (not a full block) and store info on filesystem and settings.

[MastaG]

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

Thanks br.
My 3b for zephyr also features redline's xell:P
3 wasted hours trying to manually inject xell-1f.bin using winhex lol

[nik138]

Hi guys

i have 3 xbox 360s all are ntscj i want to turn one of them to PAL all are Xenon motherboards . the software dash is the latest i believe updated from the COD MW-2 disc.

How do i do it i have an infectus chip as well .

can i do a nand dump and post it here can them some one convert it to pal for me.

thanks
Nik

[Arakon]

If you updated, you can do nothing. Also, this isn't related to xbreboot at all.

[Tiros]

My 3b for zephyr also features redline's xell:P
3 wasted hours trying to manually inject xell-1f.bin using winhex lol

3 Hours?

nandpro zephyrwithredlinexell.bin: -r16 redlinexell.bin 30 10
nandpro lpt: -w16 redlinexell.bin 30

[Rogero]

the config blocks are much more todo with continuity rather than the initial setup.
There are many config blocks, the one used for xbr is very much needed as it stores console specific info such as mac address and cpu and gpu thermal calibration values.
There is also a smc config block, both of these are static config blocks.  You are thinking of are settings ones which are not static and take up the next free space (not a full block) and store info on filesystem and settings.

Excuse my ignorance about the config blocks full roles, but i repeat that i already have done more then 15 consoles,all running different versions of XBR and not even one of them have the config blocks flashed, just the kv.bin, and all running flawlessly, playing games from hdd , running emulators, everything seems fine till now.

[Tiros]

Excuse my ignorance about the config blocks full roles, but i repeat that i already have done more then 15 consoles,all running different versions of XBR and not even one of them have the config blocks flashed, just the kv.bin, and all running flawlessly, playing games from hdd , running emulators, everything seems fine till now.

So what are you saying? Since you have done 15 that work, we should all abandon the instructions and follow you?
There is console specific information there. If you want to run without it, thats ok by me

[littlestevie360]

the config blocks are much more todo with continuity rather than the initial setup.
There are many config blocks, the one used for xbr is very much needed as it stores console specific info such as mac address and cpu and gpu thermal calibration values.
There is also a smc config block, both of these are static config blocks.  You are thinking of are settings ones which are not static and take up the next free space (not a full block) and store info on filesystem and settings.

Excuse my ignorance about the config blocks full roles, but i repeat that i already have done more then 15 consoles,all running different versions of XBR and not even one of them have the config blocks flashed, just the kv.bin, and all running flawlessly, playing games from hdd , running emulators, everything seems fine till now.

you mean everything is fine, until you go to play a system link game between them, or even have 2+ in the same network turned on at the same time

[Rogero]

Xell is working perfectly. I managed to get CPU key. So it can't be about bad jtag hack. Is that bad block mover working corretly with new version of jasper dump?[color=][/color][color=][/color]

BadBlockMover current version does not even support Jasper models, Redline99 will release a new version that supports all Jasper models (16/256/512)  check here : http://www.xboxhacker.org/index.php?topic=13051.20

Good you have your Jtag setup working, now you have different tests to do :
1- start with a clean XBR image, insert kv.bin with nandpro, dont do any bad block remapping,
    just give it a shot and flash it.
    If you got error E71, just flash it again because sometimes it doesn't work from first flash.

2- If still it doesn't boot into XBR and you still have Xell loading fine, then you must try to flash it
    with Lflash/Gentoo which saved me many times after un-successful attempts with nandpro.
    Use this Lflash for Jasper, it have the right flashconfig, the original lflash won't work with Jasper :
    http://www.mediafire.com/file/kmyqtxilmod/lflash-All-jaspers-only.c

N.B:  Step 1 & 2 both considering no Bad blocks remapping involved.

3- In case didn't work with Lflash too, now you must try to relocate your bad blocks manually with
     nandPro ( or wait for Redline99's new BadBlockMover release )
    Also you must Flash it at least twice with NandPro, then try with LFlash with gives me better
    chances for a working XBR.

Good Luck...