Using lflash to flash XBReboot??

[Pacote-san]

Awesome work, thanks so much for helping things along with this trancy!

I just tried it on a BB 512 and had it lockup hard while writing XBR3 to the nand.

It made it through dumping the first 64 meg and verifying fine.

I was able to reflash xell to the first 1.5 meg with my LPT (nandpro recognized the flash config and wrote without issue) and am booting gentoo now to try again.

Trying a different USB memory stick.

Pretty darn fast!

Copy your xbr.bin to DESKTOP first, then flash it there (cd /home/gentoo/Desktop)

[Counti]

Very nice work!

But i have a question: Are this lflash dumps 100% correct or should we dump at least 2 times and compare it with an hex editor? If so, maybe u can add such a function to your script?

greetz

[crimpshrine]

Awesome work, thanks so much for helping things along with this trancy!

I just tried it on a BB 512 and had it lockup hard while writing XBR3 to the nand.

It made it through dumping the first 64 meg and verifying fine.

I was able to reflash xell to the first 1.5 meg with my LPT (nandpro recognized the flash config and wrote without issue) and am booting gentoo now to try again.

Trying a different USB memory stick.

Pretty darn fast!

Copy your xbr.bin to DESKTOP first, then flash it there (cd /home/gentoo/Desktop)

Going to try that this time.. I did it a second time and it hung again during flashing.. Made it to 0X13D of 0X200 though.  (Further then the 1st time)

Reflashed XELL again and booting now

[iLLNESS]

Very nice work!

But i have a question: Are this lflash dumps 100% correct or should we dump at least 2 times and compare it with an hex editor? If so, maybe u can add such a function to your script?

greetz

we've proven that the reading part is correct so it is working.
the dump is verified again against the nand itself so if the dump was bad, it would fail. there should be no need to dump more then once but if this is your first time using xell on the 360 i'd suggest dumping more then once and verifying the read.

this is likely something that happens with bad block nands.

[crimpshrine]

Code:

XBR-Flash for Linux v0.1.1 beta by trancy
Thanks goes to tmbinc and Redline99

Nandsize: 64 MB

Dumping to back.bin...
0x200 block's to dump...
Bad block found (index: 0x16)                
Reading block: 0x200 of 0x200
Reading done in 41.00 sec.
Speed: 1.56 MB/s

Verifying flash with back.bin...
0x200 block's to verify...
Bad block found (index: 0x16)                
Ignoring bad block at 0x16
Verifying block: 0x200 of 0x200
Verify done in 40.00 sec.
Speed: 1.60 MB/s
Verify ok.

Flashing from xbr.bin...
0x200 block's to write...
Detected RAW nand file, flashing in raw mode.
Unexpected erase at block 0x16 with status 0x202
Writing block: 0x200 of 0x200
Write done in 32.00 sec.
Speed: 2.00 MB/s

Verifying flash with xbr.bin...
0x200 block's to verify...
Detected RAW nand file, verifying in raw mode.
Bad block found (index: 0x16)                
Ignoring bad block at 0x16
Verifying block: 0x200 of 0x200
Verify done in 41.00 sec.
Speed: 1.56 MB/s
Verified 67108864 bytes ok :)

Worked great after copying xbr.bin to system memory before running.

Still won't boot XBR though, just a solid green light

Everytime I would try to flash this particular 360 nandpro would error on block B0, I trust this more since it said it had an issue on 0x16 during read, verify, then write and verify of write.

Don't get why nandpro says b0, and this says 0x16

Could someone please PM me what block I would move where with nandpro as a follow up to just flashing with this?

Thanks

[Counti]

I already got a working JTAG box.

I just asked because i got another one (which i bought for a friend of mine) and its a 512mb jasper (same as mine). I will read the dumps 2 times to be sure. if they are identical (as they were on my first 3 dumps from my box) i will do future jtags without multiple dumps.

Thanks for the quick answer.

[iLLNESS]

Worked great after copying xbr.bin to system memory before running.

Still won't boot XBR though, just a solid green light

Everytime I would try to flash this particular 360 nandpro would error on block B0, I trust this more since it said it had an issue on 0x16 during read, verify, then write and verify of write.

Don't get why nandpro says b0, and this says 0x16

Could someone please PM me what block I would move where with nandpro as a follow up to just flashing with this?

Thanks

at this stage, i'd trust nandpro over lflash when it comes to bad blocks.
if remapping b0 worked before, why change to 16?

[crimpshrine]

Worked great after copying xbr.bin to system memory before running.

Still won't boot XBR though, just a solid green light

Everytime I would try to flash this particular 360 nandpro would error on block B0, I trust this more since it said it had an issue on 0x16 during read, verify, then write and verify of write.

Don't get why nandpro says b0, and this says 0x16

Could someone please PM me what block I would move where with nandpro as a follow up to just flashing with this?

Thanks

at this stage, i'd trust nandpro over lflash when it comes to bad blocks.
if remapping b0 worked before, why change to 16?

Remapping b0 before did not work.

That is why I rushed to try this because I was hoping to see if the results were the same when flashing.

With nandpro it always gets an error when writing B0, no other errors.

If I read 0xB0 from XBR#3 for big block nands there is only FF's there.

If I read block 0x16 from XBR there is valid data there..  So that makes me think maybe lflash64 is right

I have never gotten this particular 360 to boot XBR, I have gotten 4 others booting it first time, but none of those had any lower bad blocks.

[trancy]

@crimpshrine

0xB0 from nandpro is the same Block as 0x16 from XBR-Flash. Because NandPro uses Blocksize: 16KB and XBR-Flash uses 128KB.

I made some progress with a sulution for Bad Blocks (all Nadnsizes). Wait for the next XBR-Flash update!

[Bydox]

Don't get why nandpro says b0, and this says 0x16

nandpro always uses small block number convention.  This is why for example, it will show total of 0x3FFF blocks on a 256Mb nand. lflash uses big block numbering which means total of 0x800 blocks on the same nand.  So in your example, 0xb0 / 8 = 0x16.  Same block is being reported in both programs (they just use different block sizes).  Hope this makes sense.

Edit.. I see trancy already answered your question too.

[crimpshrine]

Thanks, yeah someone pointed out to me in another thread that  lflash is 0x2100 bytes per block and NandPro's is 0x4200 bytes

I should have realized when looking at the 0x16 that 0b is half of that..

[crimpshrine]

@crimpshrine

0xB0 from nandpro is the same Block as 0x16 from XBR-Flash. Because NandPro uses Blocksize: 16KB and XBR-Flash uses 128KB.

I made some progress with a sulution for Bad Blocks (all Nadnsizes). Wait for the next XBR-Flash update!

That is awesome..

Thanks trancy for your time and modifications, you are cumulatively saving people weeks if not months worth of flash time.

I have this problem unit here and I don't mind if it's unstable I have LPT still soldered to put xell back on if you need me to test anything.

[crimpshrine]

I just flashed 2 - xbox 360's (256 Meg Nand) that were still on XBR#1. (I had pulled the LPT connector in hopes that there would be a linux based flash tool one day)  

I just wound up using FTP to get the files to the Xboxes, I kept having lockups just copying the xbr.bin to the desktop from USB no matter which USB memory drive I used.  With FTP it copied over every time without any lockups.

Copied to the desktop the lflash binary and the xbr with keyvault and config already injected and both units updated without a hitch.

[Rogero]

Seems like a problem with Grub being unable to find or access the boot partition. Bad burn maybe?

2 burns now: 1 on a CD-R medium, 1 on a DVD-R medium. Going to try a DVD+R DL (verbatim). The second burn seemed to make it through more steps during the boot up cycle but still failed as soon as it got to:

Loading modules
Activating mdev
Making tmpfs for /newroot
No bootable medium found. Waiting for new devices...\

And then the errors I already described follow. Strange...

A DVD+R DL would be a waste, by the way the Gentoo ISO is meant to be burned to a CD, you can't just burn it to a DVD and expect it to work. I would try to burn again on a CD.

Burned 3 cds, was simply trying to eliminate possibilities. No luck, looks like I am going to have to LPT flash. I would like to say thank you though to the people putting time and effort into making this possible. People like you all keep the scene going.

when it gives you the error : "Can't find boot device" and stops, just try to open the dvd drive then close again, it worked for me.

[benwolf]

when i try to flash xbr8955v3 on my 512mb jasper nand i always get "verify error at block: 0x0200 Verify failed"
whats wrong? nand reading works great, got 1 bad block at 0xaa

anyone an idea?

[elderdrake]

For anyone that saw my post about problems w/Gentoo loading I finally figured it out and wanted to share it in case someone else has this problem. My Jasper 256 running Xell on XBR_1 would not see Gentoo livecd Beta 2. I tried multiple mediums, burning apps, etc until on a whim i tired the earlier Gentoo Livecd image...booted with no errors. My only concern is will my botting with the previous Gentoo Livecd make this work around flash dangerous or not possible? Sorry to post on this problem here, should be reserved for straight coders but my problem does relate and threads on this are few and far between.

[Badxil]

Great work 
I know that my question is not really lflash related but I think it's the best place to find someone with the knowledge to help me.
I try to use the infectus 2 modchip to dump the 512Mb Samsung K9F4G08U0B nand chip on my jasper, so I decided to use Infectus NAND Flasher 1.03 (made by NDT) but I need some info about this chip.
Since I don't find the datasheet for the K9F4G08U0B, I can't get it working (I get bad dump full of 02020202....)

Here is the good settings for the 256 Mb chip

#### 360 Nand ####
flash_id = 0xECDA
flash_name = Samsung K9F2G08U0A 256Mbyte [ECDA]
subpage_size = 0x2c0
page_size = 2048
spare_size = 64
num_blocks = 2048
pages_per_block = 64
address_cycles = 4
nr_of_flashes = 1

Regards

[crimpshrine]

I flashed another 360 with a 512 nand today without issue.

I don't even use USB memory anymore, just another local PC running an FTP daemon with the a.out binary and whatever XBR I am going to flash.

Connect through FPT with Gentoo off the dekstop, transfer the files to desktop and open a terminal and do it.

[crimpshrine]

New versions of lflash now has its own thread I see:

http://www.xboxhacker.org/index.php?topic=13656.0