4 Step Guide To Flashing Xbreboot, Lets Get that Homebrew Working for You Options

[hazed69]

i was wondering if i extract my nand and lets say i didnt check it make sure it was correct
follwed the instruction on here and i get e79 does that mean the board is screwed
wonderin because i re flashed it with the nand i dump and it booted up fine but i checked my nand with
xbox360 flash tool i get 000000000000000000000000 for my cpu key!
does that mean
1 it will still boot up even if my cpu is all 0000
2 xbox360 flash tool is just wrong and theres another way to get that key!

[Grim187]

thats not your cpu key, thats where you put your cpu key.

[Roamin64]

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.

[hazed69]

thats not your cpu key, thats where you put your cpu key.

ooooh
why is that when i do flash nand
i get an error of e79
ive done both xbr that i can get
my CB is 1920
i flash kv.bin 1 1 that i get from the org.bin
then flash config.bin 3de 2
then flash xbr.bin
then add kv and then config
unplug add vga and start it up and e79
if i flash it with the org.bin
it works fine .........?
maybe im doing something wrong?

[Grim187]

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.

theres soo much wrong with what you just said im not even gonna bother, sorry.

maybe im doing something wrong?

but most likely your using the wrong xbr? (use 1921)

This post has been edited by Grim187: Dec 29 2009, 02:50 PM

[hazed69]

in my last poosti said ive used both xbr
with both results of e79

[Roamin64]

theres soo much wrong with what you just said im not even gonna bother, sorry.

What is wrong with what i said? All i'm saying is that on 16mb nands, the bad blocks are located at the complete end of the nand, and i was asking where, are they remapped on large nands?


Do you sincerely think that only backing up the first 70 megs of the nand is safe? I do understand that a lot of space in the nand is used for storage, i'm just wondering where are the bad blocks on a large nand..

[Tj1zzle]

What is wrong with what i said? All i'm saying is that on 16mb nands, the bad blocks are located at the complete end of the nand, and i was asking where, are they remapped on large nands?
Do you sincerely think that only backing up the first 70 megs of the nand is safe? I do understand that a lot of space in the nand is used for storage, i'm just wondering where are the bad blocks on a large nand..

Are you seriously questioning this mans logic? if you knew just how many boxes he has successfully completed this hack on you would stop badgering him with your retardo "speculations"

follow the tut word for word, you fail try again, you fail again, buy one off him.

[halikus]

fairly obvious, but know you can make an easy batch script. Just copy this into a text file, rename it "whatever".bat, copy it to the nandpro directory, and run it. %~dp0 means the root of the directory you are in. Im using Xenon as an emaple, make a directory in nandpro directory named "Xenon" and your dumps will go in there. If you have another mobo, rename all the xenon references to falcon or whatever. This way it will run for a few hours unattended and you can take your wife and dog for a walk before you submerse yourself in homebrew.

to dump...
------------------------------------


set buildir=%~dp0%

rem Put "rem" infront of the bottom 2 entries to not have it make c1.bin
ECHO Backing up XENON C1 XENONc1.bin to Nandpro Dir 10 minutes and then XENONnand3.bin ...
%~dp0nandpro.exe lpt: -r3 %~dp0Xenon\XENONc1.bin


ECHO Backing up XENON Nand XENONnand1.bin to Xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand1.bin


ECHO Backing up XENON Nand XENONnand2.bin to Xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand2.bin


ECHO Comparing XENON Nand XENONnand1.bin and XENONnand2.bin in xenon Dir...
%~dp0fc %~dp0Xenon\XENONnand1.bin %~dp0Xenon\XENONnand2.bin /b


ECHO Backing up XENON Nand XENONnand3.bin to xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand3.bin


echo Done
echo You should have XENONnand1.bin, XENONnand2.bin, and XENONnand3.bin in xenon dir.
pause

--------------------------------

[hazed69]

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

[halikus]

i couldnt find the edit post button lol, heres a cleaned up more elaborate script, at least for dumping. Bear in mind bigger than 16 meg flashs are different.


---------------------

set buildir=%~dp0%

echo=oFF


ECHO Backing up XENON C1 XENON_c1.bin to xenon Dir 10 minutes...
%~dp0nandpro.exe lpt: -r3 %~dp0Xenon\XENON_c1.bin


ECHO Backing up XENON Nand XENONnand1.bin to Xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand1.bin


ECHO Backing up XENON Nand XENONnand2.bin to Xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand2.bin


ECHO Backing up XENON Nand XENONnand3.bin to xenon Dir 40 minutes...
%~dp0nandpro.exe lpt: -r16 %~dp0Xenon\XENONnand3.bin


echo Done
echo You should have XENONnand1.bin, XENONnand2.bin, and XENONnand3.bin in xenon dir.
echo Now for file Compare. Press a key...
pause

ECHO Comparing xenon Nand XENONnand1.bin and XENONnand2.bin in xenon Dir...
fc %~dp0xenon\XENONnand1.bin %~dp0xenon\XENONnand2.bin /b
pause

ECHO Comparing xenon Nand XENONnand1.bin and XENONnand3.bin in xenon Dir...
fc %~dp0xenon\XENONnand1.bin %~dp0xenon\XENONnand3.bin /b
pause

ECHO Comparing xenon Nand XENONnand2.bin and XENONnand3.bin in xenon Dir...
fc %~dp0xenon\XENONnand2.bin %~dp0xenon\XENONnand3.bin /b

echo Done.
pause

exit

---------------------------------------

[halikus]

heres one for flashing. Just rename the files for your nand and xbr. This is very micky mouse scripting but still good for automation as it takes awhile. Use this (flashing) script at your own risk. If you dont have the proper backups you are screwed. Thanks for the tutorial too grim, very easy to follow. It should be stickied.



for flashing : (make this a .bat in nandpro dir)
Delete the pauses if you trust the script and yourself.
----------------------------


::begin
@ECHO OFF
set buildir=%~dp0%

rem Your Original Nand Dump (named 1.bin)

echo Have xbreboot named xbr.bin and your nand as orig.bin in nandpro folder.
echo Flashing XBR, are you sure?
pause

echo Flashing XBR, this will take 40 minutes...
nandpro lpt: -w16 xbr.bin

echo Get keyvault from orig.bin?
pause

echo Getting KV.bin...
nandpro orig.bin: -r16 kv.bin 1 1

echo Get Config from orig.bin?
pause

echo Getting config.bin...
nandpro orig.bin: -r16 config.bin 3de 2

echo Now you should have config.bin and kv.bin in the nandpro folder


echo Flash KV.bin?
pause

echo Flashing kv.bin...
nandpro lpt: -w16 kv.bin 1 1


echo Flash Config.bin?
Pause

Echo Flashing Config.bin...
nandpro lpt: -w16 config.bin 3de 2

echo Done. Enjoy motherhumpers.
pause
exit

---------------------------

This and my other scripts arent for anything bigger than a 16 meg nand too, but its easy enough to fix.

[Grim187]

the one i use for big block

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.

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.

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.

if you knew just how many boxes he has successfully completed this hack on

about 150.

[XBoxgeek]

I think what Roamin64 was trying to ask was that if you only back up the first 70MB there could be a chance that some crucial data (KV) may be remapped outside of the 70MB that you backed up due to bad blocks in the first 70MB.

Then again I could be wrong

[uzi]

im tryin to dump my nand ... and i get no flash controller