E79 16MB Jasper XBReboot

[HiTec]

Jasper (16MB) i´v been working with will boot to E79 when flashed with newest XBReboot Jasper 16MB image. Tried with config + kv and just the kv. Can´t get it work. It seems that there is a bad block in the nand.
I can boot XeLL just fine. And the retail 6xxx blade dashboard.

What can i do to make it work? Allready tried badblockmover app.

[POi]

E79 in my experience is problem with the JTAG wiring/soldering.

[HiTec]

I know. But i´m 100% sure that the wiring is ok.

[damox]

E79 in my experience is problem with the JTAG wiring/soldering.

Seeing as xell boots .

[HiTec]

Yeap. XeLL gave me the right CPU and DVD-key. Checked my NAND-dumps with flash dump tool 0.91.
Just for test, I rewired the whole JTAG-wiring. That clearly isn´t the problem. I think its´s the NAND-chip... I´v been in this situation before with the timing attack. I got it working when i changed the whole NAND-chip to another. But because this isn´t my Xbox, and this is brand new Jasper made in January 09, im not really too happy if i have to change the NAND....

If i flash the nand, and read it (wont turn xbox on before reading) the dumps wont match when doing md5 compare, so it´s bad block(s). What can i try? Thanks for answers 

Some info:

My wirings:

Infectus







CB 6712 should be good?

[maximilian0017]

If i flash the nand, and read it (wont turn xbox on before reading) the dumps wont match when doing md5 compare, so it´s bad block(s). What can i try? Thanks for answers 

Dont use md5 compare, use something like Hex workshop and check if the differences between written an read nand are in the Bad Block area, it is normal that a bad block can cause this.

[ReverseAffect]

you went as far as using and infectus..why not the add on for the attack???...and nice install on the infectus

[littlestevie360]

you went as far as using and infectus..why not the add on for the attack???...and nice install on the infectus

well one would assume because its a jasper which isnt vuln to the timing attack, and because you dont do the timing attack for running xell

[HiTec]

nice install on the infectus 

It´s just temporary installation but thanks

Dont use md5 compare, use something like Hex workshop and check if the differences between written an read nand are in the Bad Block area, it is normal that a bad block can cause this.

Okay, i will do that. Thanks.

[HiTec]

If i remap the bad blocks in the nand dump, i can get my xbox almost to boot:

Video:

http://dream.pic.fi/kuvat/Xbox+360/HiTec+XBReboot+0.05/almost_boot.mp4

XeLL boots just fine. Do i really have to change the whole NAND-chip to get it work? Is infectus so $#!tty device that it allways tries to write in that specific bad block...

[ReverseAffect]

ya but if your using 8955 don't you have to up the LDV to 1?

and you used XBR_Jasper_16_8955_1 ?

what dash was in it?

[Arakon]

infectus doesn't write bad blocks if you remap them. it's impossible for the infectus to know if a block is bad and should be remapped.

[HiTec]

Thanks for answer! Okay, so the problem is my remapping. (Sorry Infectus, my bad).

And to ReverseAffect, i dont think i have to change LDV cause XBR uses virtual fuses... I´v disabled R6T3 allready, and use XBR_Jasper_16_8955_1.bin
Orig dash is the last blade dash 2.0.6717.0.

Edit: Opened orig.bin with degraded, saw bad blocks, tried remapping manually, with these commands in nandpro20b, still the same $#!t:

    * nandpro xbr.bin: -r16 block7D00.bin 7D00 1 (Reads block 7D00 and saves as block7D00.bin)
    * nandpro xbr.bin: -w16 block7D00.bin 3ff 1 (Writeblock7D00.bin to 0x3ff where block is remapped)

[Geremia]

I've similar problem, jasper 16MB with a bad block, xell works but XBR hangs on bootanim.
Your block 027D block is bad, but, like the pros here told me, the blockID in mine (and your) dump is shifted 1byte left, that's why the badblockmover app thinks it's block 7D00 instead of 027D.
Since the jasper16MB XBR image out here has "old style" blockID position, when you insert your KV, you should use nandrpo +w command, which fix the ECC and blockID position.
For block reallocation, write manually the block number into the app, then press "reposition bad blocks" and browse the XBR image.
I'm still getting the bootanim hang, but sincerely i had not so much time to test.

[HiTec]

Aaa, i was thinking that why its saying 7D00 when degraded say its 027D. Never thought that it could be a shifted byte. Thanks for advice Geremia! I hope it works, now testing

Code:

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 ===========================

Now flashing.

Edit: Doesn´t work. The end result is same what is you see in the video. Should i also use +r when reading the kv from orig.bin? I think i´ve tried everything.

[HiTec]

Soldered R6T3 back, flashed orig.bin, booted pre nxe and then updated to 7xxx nxe. Then i started the whole thing from the scratch. Still it just wont boot to hacked 8955. XeLL and orig fine. wtf is this.

[l_oliveira]

Why not try to flash with LPT and nandpro ?

Drop that infectus a bit so you will be able to remap the bad blocks properly.

Refer to Arakon's post:

infectus doesn't write bad blocks if you remap them. it's impossible for the infectus to know if a block is bad and should be remapped.

With the SPI method you have chances of making it work.

[Arakon]

makes no difference really as long as you manually remap them in the file before you flash, or use the bad block mover.

[HiTec]

Okay. I get my new USB-based reader in next week and test with it. This is really strange xbox.

[HiTec]

YES! Geremia you are the man!

http://dream.pic.fi/kuvat/Xbox%20360/HiTec%20XBReboot%200.05/Xbox+360+New+SB.mp4

So, the main problem was the new southbridge that caused the E79 when using "original" XBR.
How i made it to work:

- Write orig bin 7xxx dash to NAND, boot.
- Read it back.
- Then injected kv and config to Geremia´s great SB-fixed XBR.
- Checked bad blocks with bb-mover showed 0x7D00.
- Manually changed it to 0x027D:ksi and then remapped it with bb-mover
- Then i repaired infectus (broked it again when moving Xbox mobo.)
- Flashed XBR, and instantly read it back ja compaired images with hex-editor, zero differences, then took power cable of the box, put it back and rebooted it to 8955 XBR.

Thank you Geremia!