CODE
@ECHO OFF
ECHO.
:b
cls
color a
set choice=1
set /p choice=skip read?
if '%choice%'=='y' goto :f
b usb: -r70 j1.bin
ECHO.
set /p choice=Press Enter
b usb: -r70 j2.bin
ECHO.
fc j1.bin j2.bin /b
ECHO.
ECHO If No Differances Found
pause
echo.
echo.
:f
color c
set /p v=Version?
b usb: -w256 xbr%v%.bin
pause
:r
b j1.bin: -r256 jk.bin 1 1
sleep 1
b j1.bin: -r256 jcfg.bin ef7 2
sleep 1
b usb: -w256 jk.bin 1 1
sleep 3
b usb: -w256 jcfg.bin ef7 2
set choice=1
set choice=2
set /p choice=save file?
if '%choice%'=='y' set /p fn=Filename?
rename j1.bin %fn%.bin
if '%choice%'=='n' del j1.bin
del j2.bin
del jk.bin
ECHO.
CLS
EXIT
i found your more likely to get a croupt dump if you dont pause and manualy continue, if you just wanna leave your pc dumping for awhile then replace "set /p choice=Press Enter" with "sleep 3".
you will need sleep.exe in system32 its found in the
Windows Server 2003 Resource Kit Tools pack.
the ones i use for 16mb nands;
CODE
@ECHO OFF
ECHO.
:b
cls
color a
set choice=1
set /p choice=skip read?
if '%choice%'=='y' goto :f
nandpro usb: -r16 1.bin
ECHO.
set /p choice=Press Enter
nandpro usb: -r16 2.bin
ECHO.
fc 1.bin 2.bin /b
ECHO.
ECHO If No Differances Found
pause
echo.
echo.
:f
color c
set /p v=Version?
nandpro usb: -w16 xbr%v%.bin
set choice=1
set choice=2
pause
:r
b 1.bin: -r16 k.bin 1 1
sleep 1
nandpro usb: -w16 k.bin 1 1
sleep 3
nandpro usb: -w16 cfg.bin 3de 2
set choice=1
set choice=2
set /p choice=save file?
if '%choice%'=='y' set /p fn=Filename?
rename 1.bin %fn%.bin
if '%choice%'=='n' del 1.bin
del 2.bin
del k.bin
ECHO.
CLS
EXIT
xbr.bin is xenon (so you just press enter when it asks version?)
xbrz.bin is zephyr
xbrf.bin is falcon
xbrj.bin is jasper 16mb
if i get differances then i open up a cmd prompt and dump the 3rd and compare with 1 and 2.
QUOTE(hazed69 @ Dec 29 2009, 01:37 PM)
Thanks for the script
does anyone know how to check if the resistor are still good
I was thinking of using and ohms reader but just wanted to make sure I will be doing it right
ya you can use a multimeter and check them but i dont think ive ever seen a dead resistor in my 8+ years with computers/modding/etc.
QUOTE(Roamin64 @ Dec 29 2009, 02:31 AM)
At what address do the bad blocks in large nand jaspers start? Is it the end like the 16mb nands? because if so, backing up only the beginning of your nand , wouldn't you be leaving the bad blocks out , and if you ever want to reflash to original, then maybe the first 70 megs won't be enough , to cover the bad blocks? I'm guessing there's a table that says where each bad block was remapped, and without that table, when you format the nand using the console, wouldn't it erase the data from the remapped zone, if your new image doesn't have that table?
I don't have a large jasper , but i did find very important to have a 100% backup of my nand, in case.
This is just speculation on my part, but i thought i should bring it up.
bad blocks usaly occur in the nand, not outside of the nand.
there isent any one place where they frequent.
if you have a bad block you remap it to a ff space with badblock mover.
a bad block isent a dead block its just a spot in the nand that you cant read/write to (the 360 still can...iinm).
not haveing to read/write bad blocks (i.e. there in a part of that nand that dosent been to be flashed) is a good thing.
badblock mover analyzes your original nand and gives you a list of bad blocks; you will aways have this option as long as you have your original nand, even if you loose your nand the bad blocks will show up in nandpro when you try to read/write them, you will have to use badblock mover on every xbr update you do if you have bad blocks in your nand.
QUOTE(Tj1zzle @ Dec 29 2009, 10:22 AM)
if you knew just how many boxes he has successfully completed this hack on
about 150.