Print

[bennybullfrog]

QUOTE(kipper2k @ Dec 18 2009, 11:09 AM)

Today is a good day, a real good day.  
thanks for the info

Worst day for me. I bought a 16mb Jasper when I could've got a 256mb arcade for much cheaper 3 hours before they released the new xbr!

I'd been debating all week whether to get one and finally took the plunge

I hope it doesn't turn out that having the 256mb nand is much better.

[Xx The 0ne xX]

QUOTE(Roamin64 @ Dec 17 2009, 08:41 PM)

Its different because it saves you a lot more time than simply dumping the entire 256/512 nand using lpt.  That method must not be used to flash , but to read only. Writing xbr will be a bit faster then reflashing your original nand , as it is 67 mb.

So if I do this route, then I do NOT have a backup of my original NAND, correct?

[infidelity]

you want to have backups of your original NAND incase anything happens. If you flash your NAND with xbr, and something messes up, and you don't have your original NAND backed up, then you've just given yourself a very expensive paperweight.

Make 2 backups, and compare the both of them using "HexCMP"

[Xx The 0ne xX]

QUOTE(infidelity @ Dec 17 2009, 10:32 PM)

you want to have backups of your original NAND incase anything happens. If you flash your NAND with xbr, and something messes up, and you don't have your original NAND backed up, then you've just given yourself a very expensive paperweight.

Make 2 backups, and compare the both of them using "HexCMP"

Thats what I thought. Its about half way through the first dump. Any way I can have it continue dumping after this one is done? I will most likeley be at work or asleep when this dump is done and I don't want it just sitting idle when it could be dumping another image

[infidelity]

Can anyone post the exact things to type into nandpro? specificly for the 512mb. This is what I'd like to know

What to type to obtain...

kv.bin
rawconfig.bin

and, how to write them into xbr

Many Thanks

-infidelity

oh, and if anyone knows of how to flash the xbr with gentoo, that would be great info too

[kipper2k]

for those who have a 256MB Jasper here is a batch file you can run to help in the reading process,

 it reads the Nand in small chunks, and then rereads using a different name so you can compare sections



_____________________________________________________________________________


cls
@echo off

@echo.    
echo  This will read your 256MB Nand file in 16 parts, then reread it again in 16 parts
echo  The first read is contained in Nand1.001,002,003 etc
echo  The second read is contained in Nand2.001,002.003 etc
echo  it is split into 16 parts to try to reduce the read time in the event of a
echo  crash/bad read etc which is especially useful when using lpt to read the Nand
echo
echo   config should read 008A3020
@echo.
@echo.
Pause
@echo.
 
@echo on

nandpro lpt: -r256 nand1.001 0 400

nandpro lpt: -r256 nand1.002 400 400

nandpro lpt: -r256 nand1.003 800 400

nandpro lpt: -r256 nand1.004 c00 400

nandpro lpt: -r256 nand1.005 1000 400

nandpro lpt: -r256 nand1.006 1400 400

nandpro lpt: -r256 nand1.007 1800 400

nandpro lpt: -r256 nand1.008 1c00 400

nandpro lpt: -r256 nand1.009 2000 400

nandpro lpt: -r256 nand1.010 2400 400

nandpro lpt: -r256 nand1.011 2800 400

nandpro lpt: -r256 nand1.012 2c00 400

nandpro lpt: -r256 nand1.013 3000 400

nandpro lpt: -r256 nand1.014 3400 400

nandpro lpt: -r256 nand1.015 3800 400

nandpro lpt: -r256 nand1.016 3c00 400


@echo off

@echo.

echo  First read completed - Press a key to begin second read
@echo.

pause


@echo.

@echo on

nandpro lpt: -r256 nand2.001 0 400

nandpro lpt: -r256 nand2.002 400 400

nandpro lpt: -r256 nand2.003 800 400

nandpro lpt: -r256 nand2.004 c00 400

nandpro lpt: -r256 nand2.005 1000 400

nandpro lpt: -r256 nand2.006 1400 400

nandpro lpt: -r256 nand2.007 1800 400

nandpro lpt: -r256 nand2.008 1c00 400

nandpro lpt: -r256 nand2.009 2000 400

nandpro lpt: -r256 nand2.010 2400 400

nandpro lpt: -r256 nand2.011 2800 400

nandpro lpt: -r256 nand2.012 2c00 400

nandpro lpt: -r256 nand2.013 3000 400

nandpro lpt: -r256 nand2.014 3400 400

nandpro lpt: -r256 nand2.015 3800 400

nandpro lpt: -r256 nand2.016 3c00 400

@echo off

@echo.
echo  Assuming there were no errors you can now compare each section with each other
echo  If there are no errors then you can rejoin them

_____________________________________________________________________________

That basically splits all the files into smaller chunks in case you get bad reads then you can just copy and paste as you need to to continue from a new start point. So if you get just one suspect part you will only need to reread that area instead of the whole Nand

[vintage_guitar]

CODE

nandpro lpt: -w512 xbr.bin

3. Extract your keyvault (KV) from your dump (Call your original dump orig.bin)

CODE

nandpro orig.bin: -r512 rawkv.bin 1 1

4. Inject this KV you just extracted into your NAND

CODE

nandpro lpt: -w512 rawkv.bin 1 1

5. Unplug the power supply and LPT cable to/from the xbox 360 and wait 5 minutes for a guaranteed power cycle
6. Boot to XBR (or xell, your choice)
(Note, it shouldn't matter which order you use for injecting the keyvault, either flashing it to NAND directly AFTER flashing XBR, or injecting into XBR BEFORE flashing.)

[Roamin64]

QUOTE(vintage_guitar @ Dec 17 2009, 11:24 PM)

Not sure if XBR does this for other consoles, but It was working perfect at first, but began shooting E71 at me when i tried booting with my USB stick plugged in. I unplugged it and it booted perfectly next try. If you get E71, just try booting without any USB plugged in before taking your box apart.

Does your usb drive contain a default.xex file at root? or perhaps even elsewhere on the drive? For sure if there is one at root , you will get e71.

[vintage_guitar]

I'm gonna try to install xexloader directly on NAND and get it to run that way by transferring the files from inside xexloader. Has anybody attempted this yet?

[dakaku]

As i dont have a wired controller nor a remote or a akku-pack, is there another way to boot into xell ?

For those who need a usb flasher, check my signature.

[magnus__hydra]

QUOTE(vintage_guitar @ Dec 18 2009, 01:11 AM)

Well, here is the process I used for getting XBR to work on 512 jasper.
1. Download the file in the first post. (extract and rename the file to xbr.bin)
2. Flash it to the NAND with this command

CODE

nandpro lpt: -w512 xbr.bin

3. Extract your keyvault (KV) from your dump (Call your original dump orig.bin)

CODE

nandpro orig.bin: -r512 rawkv.bin 1 1

4. Inject this KV you just extracted into your NAND

CODE

nandpro lpt: -w512 rawkv.bin 1 1

5. Unplug the power supply and LPT cable to/from the xbox 360 and wait 5 minutes for a guaranteed power cycle
6. Boot to XBR (or xell, your choice)
(Note, it shouldn't matter which order you use for injecting the keyvault, either flashing it to NAND directly AFTER flashing XBR, or injecting into XBR BEFORE flashing.)

no need for the rawconfig.bin?

[kipper2k]

QUOTE(vintage_guitar @ Dec 18 2009, 07:40 AM)

I'm gonna try to install xexloader directly on NAND and get it to run that way by transferring the files from inside xexloader. Has anybody attempted this yet?

i dont think its really worth it, you would stil need to read your nand for the sake of restoration purposes and the xbr file is not that big anyway so you may as well save yourself the extra headache

[zeroprobe]

QUOTE(segaton @ Dec 18 2009, 01:28 PM)

?

I'm a bit confused, does that mean we can mod 360's with 8955 dashboards too?

Please read, even if its just a little before posting.

8955 means it reboots exploited xboxes into this latest dashboard.

[under420dog]

QUOTE(Br0k3R @ Dec 17 2009, 05:25 PM)

my 7363 16mb jasper is NOT exploitable.....

some ain't, some are. it depends on the date and the CB lock down.....most are locked now...

[supes]

I have a Jasper from 0ctober.26th, 2008 is that forsure exploitable, because if not I do not want ot open it too check, because than I cannot return it.

ON a secondary note does ne one have a link to a tut about how to build and solder a usb spi?