Dump 512mb Jasper Nand In 10 Minutes, Very Noob Friendly Descriptions Options

[jean.dread]

all time error!

livecd lflash # sudo gcc lflash.c
lflash.c: In function 'ioremap':
lflash.c:57: warning: cast to pointer from integer of different size
/mnt/livecd/usr/powerpc-unknown-linux-gnu/gcc-bin/4.1.1/../../../lib/gcc/powerpc-unknown-linux-gnu/4.1.1/../../../../powerpc-unknown-linux-gnu/bin/ld: cannot open output file a.out: Read-only file system
collect2: ld returned 1 exit status

and now? what i do? nandpro method are slow so much!

[Zanzang]

I found a trick to help with the freezing when using a USB 2.0 drive.

I copied the program from /flash to /Desktop, so the dump ended up on the desktop instead of going straight to the usb drive. After it finishes I drag the dump to /flash.

This worked 3 times before it crashed on a 256MB dump. Whenever I tried to dump directly to the stick it crashed at some point part way through the process every time.

[Downcastnut]

so im guessing before you do this you need to at least dump your full nand or at least 70mb through lpt so that when you write xbr to it you wont accidently screw it up and be ****ed with no backup. am i correct?

another question. Can you use lflash to also write to the nand? if so where can i find that?

This post has been edited by Downcastnut: Dec 29 2009, 08:35 AM

[vintage_guitar]

so im guessing before you do this you need to at least dump your full nand or at least 70mb through lpt so that when you write xbr to it you wont accidently screw it up and be ****ed with no backup. am i correct?

another question. Can you use lflash to also write to the nand? if so where can i find that?

1. Up to you but my lpt backup and lflash backup were identical.
2. No. Do NOT use this modified lflash.c to write large block jasper, or any NAND for that matter. It will only erase your entire nand. If you have small block, grab the regular version of lflash.c and it will work to flash (supposedly, I haven't tried it).

This post has been edited by vintage_guitar: Dec 29 2009, 11:54 AM

[crimpshrine]

I have done 2, 256 meg Jaspers in this manner so far.

What I used after opening my xterm session:

The USB drive in /dev/sda1 contained just the lflash.c file

sudo su -
cd /home/gentoo/Desktop
makedir flash
mount -t vfat /dev/sda1 /home/gentoo/Desktop/flash
cd flash
gcc lflash.c
chmod +x a.out
./a.out backup01.bin
./a.out backup02.bin

As far as my results, I found out of like 3 flash drives I tried (all 2 gig drives) Only 1 would never lockup when dumping the nand. The other 2 were totally hit or miss, sometimes they would lockup 2 or 3 times and I would have to reboot and start all over again.

Even the one flash drive that would never lockup on dumping would then lockup on the verify part.

Every time I got a successful dump and it locked up on verify I would just power off then transfer the backup *.bin.

Out of all the times I dumped the nand on both of my 360's never once did they not compare identically.

I did get some block errors in the high address range on both 360's, I am guessing I will need to sort that out later if I want to use more of the nand.

I also had a close call on my second Jasper.

When I went to dump the 2 meg from my nand, at the time I did not realize I was only dumping 1 meg (I did a previous test dump of 1 meg and then when I was scrolling back through my commands I accidentally chose 1 meg instead of 2 meg) I did not realize this until AFTER I had already written the 1.5 meg Xell over the beginning of the nand and already had my backups of the entire nand.

I flashed back the one meg of the original nand to the beginning of the nand before continuing because I wanted to see if it would still boot. It did and it still played games so I assume the 512Kilobytes that I lost was not needed, and I then extracted the necessary details from my nand dump with the 1 meg file inplace and injected XBR.bin and flashed and it seems to work fine also. I noticed after testing that one I had a savegame on the MU that was listed as corrupted, maybe that 512K I lost was part of that.

This post has been edited by crimpshrine: Dec 30 2009, 09:38 PM

[ketty_yijun]

I found a trick to help with the freezing when using a USB 2.0 drive.

I copied the program from /flash to /Desktop, so the dump ended up on the desktop instead of going straight to the usb drive. After it finishes I drag the dump to /flash.

This worked 3 times before it crashed on a 256MB dump. Whenever I tried to dump directly to the stick it crashed at some point part way through the process every time.

this is a good trick. but i run out of space because i have 512m nand. what can i do with 512m nand using this trick. how to let lflash partially read my nand?

[modslave]

Hopefully someone can answer a couple of questions for me as I really want to try this on my 256, LTP to uncripple my banned box was painful:
1. When saving the nand to the desktop is this storage on an hdd connected by the standard sata cable?
2. Once you have the Nand do you use Hex Workshop etc to copy and paste the 1st 2Mb infront of it. I mean do you literally put the cursor to the start of the large dump hit paste and save - done?
3. What version of Xell should be installed and does this matter? The reason I ask is the new version moving from rear USB to the eject button.

Thanks

[vintage_guitar]

Hopefully someone can answer a couple of questions for me as I really want to try this on my 256, LTP to uncripple my banned box was painful:
1. When saving the nand to the desktop is this storage on an hdd connected by the standard sata cable?
2. Once you have the Nand do you use Hex Workshop etc to copy and paste the 1st 2Mb infront of it. I mean do you literally put the cursor to the start of the large dump hit paste and save - done?
3. What version of Xell should be installed and does this matter? The reason I ask is the new version moving from rear USB to the eject button.

Thanks

1. No
2. No, You have to overwrite the exact same amount of data as you are overwriting the first 2MB, not adding it.
3. jasper_6723_hack_256MB_512MB.rar

This post has been edited by vintage_guitar: Jan 4 2010, 04:03 AM

[modslave]

Cheers vintage_guitar for the version and my mistake is now obvious for not overwriting.
Although im still curious where the backup will be stored when dumped to the desktop, before being copied to the usb?
Or have I misunderstood a previous post entirely and the only option is dumping straight to the usb.

As soon as the big block XBR update comes out im gonna get stuck into this

[vintage_guitar]

Cheers vintage_guitar for the version and my mistake is now obvious for not overwriting.
Although im still curious where the backup will be stored when dumped to the desktop, before being copied to the usb?
Or have I misunderstood a previous post entirely and the only option is dumping straight to the usb.

As soon as the big block XBR update comes out im gonna get stuck into this

If you followed this guide, you will have mounted the USB to a folder on the desktop. This folder is actually a "shortcut" to the usb device itself for lack of a better term. The files here are actually on the usb stick, but showed on the desktop because that's where you mounted them to (if you followed the guide). If you wish, you could dump via ssh to a pc as well. Or, you could mount an external hard drive in linux preferrably with fat32 (not ntfs, fatx (which is the default xbox hard drive file system)) instead of usb.

This post has been edited by vintage_guitar: Jan 4 2010, 06:22 PM

[44serkan44]

thanks for tutorial

my xbox jasper 512 dasboard version : 2.0.8955
this method works 8955 ?

download gentoo live cd 2

burning cloncd with verbatime cdr 6x
xbox error : mixed media disk ?

This post has been edited by 44serkan44: Jan 5 2010, 11:44 AM

[ConteZero76]

thanks for tutorial

my xbox jasper 512 dasboard version : 2.0.8955
this method works 8955 ?

download gentoo live cd 2

burning cloncd with verbatime cdr 6x
xbox error : mixed media disk ?

facepalm.jpg

This works with ALREADY MODIFIED XBoxes, and, AFAIK, 8955 isn't exploitable.

[modslave]

@ infidelity & vintage_guitar - I get to mounting the flash folder part but get error "can only be done from the root"

@ crimpshrine - using your commands my 1 st dump crashed but 2nd & 3rd went through then crashed on verify where it states "ignoring bad sector" a lot. The only dump I get of correct size 270,336 was the 1st, after that they all come up random and short

This is well better than ltp. After uncrippling a banned 256 Jasper by that method previously im far too impatient 2nd time round to get XBR goin
THANKS for these tuts you guys are great!

This post has been edited by modslave: Jan 6 2010, 12:45 AM

[modslave]

After no luck with lpt I finally got 2 matching dumps using Gentoo

Used a slower and smaller usb pen (thanks Zanzang) and the following commands;

sudo su -
cd /home/gentoo/Desktop
mkdir flash
dmesg | grep -i "SCSI device"
mount /dev/sda1 /home/gentoo/Desktop/flash
cd /home/gentoo/Desktop/flash
gcc lflash.c -o lflash
./lflash 1.bin

Then removed pen transferred backup to PC and put pen back in 360 without rebooting Gentoo and typed:

mount /dev/sda1 /home/gentoo/Desktop/flash
cd /home/gentoo/Desktop/flash
gcc lflash.c -o lflash
./lflash 2.bin

Using a slower pen drive it always restarted after pauses during read and verify.

So to add my original 2mb backup taken before flashing Xell (called orig.bin) to the beginning of the Gentoo dump can't I use;

NandPro 1.bin: -w2 orig.bin

Or do I need the two numbers afterwards to tell Nandpro where to write and by how many blocks?

Thanks in advance to any answers and now onto flashing XBR - wish I knew how to code lflash for that

This post has been edited by modslave: Jan 6 2010, 10:43 PM

[bulle48]

So to add my original 2mb backup taken before flashing Xell (called orig.bin) to the beginning of the Gentoo dump can't I use;

NandPro 1.bin: -w2 orig.bin

Or do I need the two numbers afterwards to tell Nandpro where to write and by how many blocks?

Thanks in advance to any answers and now onto flashing XBR - wish I knew how to code lflash for that

The command "NandPro 1.bin: -w2 orig.bin" should give you your original unmodified NAND backup assuming you used "NandPro lpt: -r2 orig.bin" to read the first 2megs. You don't need to put where to start writing and how many blocks since it starts at 0, and the -w2 tells it to write the first 2mb. You can double check if the original backup is good by loading it in to degraded.

And lflash can write also but it currently only supports 16MB NAND... Do not try to use it to write on Big NANDs! The quickest solution is to build the USB PIC18 SPI flasher posted on XboxHacker, but if you are only doing 1 console, than LPT might be faster than spending a couple days building the USB flasher.

This post has been edited by bulle48: Jan 6 2010, 11:04 PM