Post by: PleXo on January 26, 2010, 11:17:00 AM
CODE
XBR Flasher By Plexo
Features
Automatic CB Detection
Automatic dumping (2 times)
Automatic checksum compare
Automatic Keyvault and config extraction and injection
Automatic XBR.bin selection
Keeps backups in tidy folders
Supports 16mb and 256/512mb nands
XBRFlasher will now dump 1 sector from the NAND and run cbcheck.exe
to determine the CB Version, it will then (based on your board revision
you picked) decide if the xbox is exploitable or not, it will continue
if exploitable and go back to start with an error if your xbox has an
unexploitable CB version
Looking further into GUI idea... have a rough draft layed out still
deciding on alot of things...
**PLEASE NOTE ** i recommend that when XBRFlasher tells you to press any key
to continue flashing, you run 1 of the backup files through Degraded or similar
to check for badblocks!
simple batch file for flashing/restoring your xbox 360 nand chips,
compatible with all revisions to date. nand backups along with kv
and config seperate and log files from nandpro all kept in /backups/
restoring will come next havent done that yet...
installation:
1. make a folder called firmwares
2. Install PortIO Install.exe
3. put the following files into the firmwares folder:
XBR_Xenon_8955_3.bin
XBR_Zephyr_8955_3b.bin
XBR_Falcon_8955_3a.bin
XBR_Jasper16_8955_3.bin
XBR_JasperBB_8955_3.bin
4. Run XBRFlash.bat
todo
hhd uncripple support - should be easy enough when i have time...
Bad Block support - unsure how to do this.. need to know how to determine "bad blocks"
Automatic Board detection - so it will auto detect if you have a falcon etc...
lots of error detection/handling (will be leaving this for GUI ??)
changelog
v0.2 26/01/10 - Added Automatic CB Checking, cleaned up some of batch script
fixed some misc errors coming up
v0.1 22/01/10 - inital release
DISCLAIMER
Please note, this program is in very early stages and may have some bugs, i cannot
be held responsible for any damage whatsoever done by this program, use it at your
own risk!
v0.2 http://www.sendspace.com/file/yl5hi6
v0.1 http://www.sendspace.com/file/i03haz
Post by: belenos on January 28, 2010, 11:25:00 AM
Post by: Luqq on January 28, 2010, 11:27:00 AM
This post has been edited by Luqq: Jan 28 2010, 07:28 PM
Post by: Sunblood on January 28, 2010, 11:32:00 AM
QUOTE(Luqq @ Jan 28 2010, 12:27 PM) 
Err, this is a different tool than the linux one? Because what use is a CB checker for a linux flasher- i mean, if you got that far, your box is exploitable..
This is a PC tool. You run this from your desktop, not the 360 running Linux.
Post by: Luqq on January 28, 2010, 11:32:00 AM
QUOTE(Sunblood @ Jan 28 2010, 07:32 PM)
This is a PC tool. You run this from your desktop, not the 360 running Linux.
Yeah i know, just wanted to make this clear. Is this working better/faster than nandpro?
Post by: docentore on January 28, 2010, 12:02:00 PM
QUOTE(Luqq @ Jan 28 2010, 06:32 PM)
Yeah i know, just wanted to make this clear. Is this working better/faster than nandpro?
its a batch which uses nandpro, so the answer to your question is no.
Thanks for the update, very happy with 0.1 need to try 0.2
Post by: evans05 on January 28, 2010, 12:06:00 PM
Post by: GOTitCUZiMODDED on January 28, 2010, 01:20:00 PM
Post by: Ranger72 on January 28, 2010, 03:17:00 PM
Exploitable CB versions:
1888, 1902, 1903, 1920,1921: exploitable xenon
4558: exploitable Zephyr
5761, 5766, 5770: exploitable falcon
6712, 6723: exploitable jasper
These CB versions are patched so the JTAG/SMC Hack is no longer working: (CD = 8453 for all of them)
Xenon: 1922, 1923, 1940
Zephyr: 4571, 4572, 4578, 4579
Falcon/Opus: 5771
Jasper: 6750
Other than that looking good.
This post has been edited by Ranger72: Jan 28 2010, 11:17 PM
Post by: Mat03111984 on January 28, 2010, 03:28:00 PM
Post by: arielzadi on January 28, 2010, 03:56:00 PM
all we need now is a gui
some unbanning features
and an option to read and compare first 50 blocks and then write Xellous(not regular xell)
Post by: k2xtrEm on January 28, 2010, 04:25:00 PM
any progress on the non-exploitable boxes?
Post by: PleXo on January 28, 2010, 04:43:00 PM
QUOTE(Ranger72 @ Jan 28 2010, 10:17 PM)
Got a bug to report. When using this app to dump a big block Jasper I get (error: CB version (6723) is incompatible for jtag). NOT true.
Exploitable CB versions:
1888, 1902, 1903, 1920,1921: exploitable xenon
4558: exploitable Zephyr
5761, 5766, 5770: exploitable falcon
6712, 6723: exploitable jasper
These CB versions are patched so the JTAG/SMC Hack is no longer working: (CD = 8453 for all of them)
Xenon: 1922, 1923, 1940
Zephyr: 4571, 4572, 4578, 4579
Falcon/Opus: 5771
Jasper: 6750
Other than that looking good.
hey there, please pm me your nand dump!!
Post by: Ranger72 on January 28, 2010, 05:14:00 PM
QUOTE(PleXo @ Jan 28 2010, 06:43 PM)
hey there, please pm me your nand dump!!
Yes it was my bad. I was typing capital J instead of lower case j.
Will test it again when it gets done dumping the traditional way.
Post by: Frogman7 on January 28, 2010, 06:52:00 PM
To everyone asking is there any progress on non-exploitable boxes? Well I don't know the answer to that not being part of the "scene" but I can pretty much guarantee its going to be a long time before we see another exploit like the jtag if ever. The security of the 360 is pretty intense watch the google talks video on it sometime if your curious. So I'd start looking in unlikely places for an exploitable 360 and cross your fingers I found two at a local video store. I wouldn't plan on another exploit coming around as there might not even be one.
Post by: KCO on January 29, 2010, 08:27:00 AM
Post by: Ranger72 on January 29, 2010, 11:57:00 AM
Post by: Spegs12 on January 29, 2010, 05:20:00 PM
This post has been edited by Spegs12: Jan 30 2010, 01:21 AM
Post by: MadDog70 on January 30, 2010, 01:44:00 PM
Post by: DrexeL_UK on January 30, 2010, 04:45:00 PM
QUOTE(MadDog70 @ Jan 30 2010, 08:44 PM)
Can anyone tell me if I can flash my banned falcon XBox 360 updated with the 8955 dashboard ?
No. This question gets asked a thousand times a day. Use the search.
Post by: aerofx on January 30, 2010, 06:26:00 PM
Post by: Larzon on January 31, 2010, 04:10:00 AM
I've got this error:
ERROR: cb.bin was not created.. please check SPI cable wiring and try again!
when I use nandpro manually it works but I have one bad block, can I remap it after xbr flasher is done? well, if i'll get xbr flasher to work in the first place.. =)
This post has been edited by Larzon: Jan 31 2010, 12:59 PM
Post by: cardboardbox on January 31, 2010, 03:56:00 PM
This post has been edited by cardboardbox: Jan 31 2010, 11:57 PM
Post by: eppo on February 01, 2010, 06:53:00 AM
- The first one is that the comparing from the 2 dumps also works on non-English windows.
- The second change is that you choose for LPT or USB with the L or U (Use (L)PT of (U)SB). That because when you use USB instead of usb, nandpro will not work.
You can download the .bat file from:
http://www.eppo-ombo...ash_changed.bat (right click -> save as..)
Post by: Larzon on February 01, 2010, 12:08:00 PM
QUOTE(cardboardbox @ Jan 31 2010, 11:56 PM) 
I get "application failed to initialize" right after it starts to read.
Do you have dotNET installed? standard error message if you don't...
Someone knows why I get this error?
ERROR: cb.bin was not created.. please check SPI cable wiring and try again!
This post has been edited by Larzon: Feb 1 2010, 08:18 PM
Post by: PleXo on February 04, 2010, 08:49:00 PM
QUOTE(cardboardbox @ Jan 31 2010, 10:56 PM)
I get "application failed to initialize" right after it starts to read.
as larzon says you need .net installed for cbcheck.exe to work!!
QUOTE(Larzon @ Feb 1 2010, 07:08 PM)
Do you have dotNET installed? standard error message if you don't...
Someone knows why I get this error?
ERROR: cb.bin was not created.. please check SPI cable wiring and try again!
i guess it means that cb.bin was not created, thats why your getting it, does it dump normally with nandpro?
this error usually means that nandpro couldnt detect your xbox, hence cb.bin wasnt dumped and cbcheck.exe cant find it so it brings you that error, thats why it says check your wiring ??
ANYWAYS......
hi guys ... have been away for a few days hehe...
here is an updated pic of the latest progress of MagicFlasher...
i seemed to of hit a brick wall with nandpro and getting it to output properly into my application, i have resorted to a simple animation that will run while its read/writing the nand, no progress bar so to speak, no output until its complete, sorry guys but its the only way
anyway, when i have the basic, dump, inject to xbr, flash functions completed il be releasing the first beta release.. at the moment it isnt really releasable as it stands as doesnt do much!
Post by: thesonandheir on February 06, 2010, 03:24:00 PM
QUOTE(Larzon @ Feb 1 2010, 07:08 PM)
Do you have dotNET installed? standard error message if you don't...
Someone knows why I get this error?
ERROR: cb.bin was not created.. please check SPI cable wiring and try again!
I get this error too, nandpro sees my USB SPI and works correctly but XBR Flasher does not. I have used this app when I just had LPT and it worked like a dream, just wish I could get it working with my USB.
Anyways, keep up the good work Plexo.
Post by: thesmj on February 06, 2010, 04:32:00 PM
Is there any reason the batch is set to write/modify using 256MB address space on 16MB Xenon boards? Shouldn't the %size% variable be used in the modify and write processes?
The flash ROM on my Xenon board is only 128MB in total size...
Post by: PleXo on February 07, 2010, 08:11:00 AM
it just saves using the var
Post by: arielzadi on February 08, 2010, 11:57:00 PM
so if you can manage to make the software to read the log every few second or maybe evry second then maybe just maybe we can hve some sort of progress bar with bad block output
cheers
Post by: HooGLaNDeR on February 21, 2010, 09:08:00 AM
QUOTE(thesmj @ Feb 7 2010, 12:32 AM)
Hey Plexo!
Is there any reason the batch is set to write/modify using 256MB address space on 16MB Xenon boards? Shouldn't the %size% variable be used in the modify and write processes?
The flash ROM on my Xenon board is only 128MB in total size...
Original line :
nandpro\nandpro %usblpt%: -r256 cb.bin 2 1 won't work on my Xenon (16 MB ) mobo.
Altering it to :
nandpro\nandpro %usblpt%: -r%size% cb.bin 2 1 will work though. I've tested this on 2 different Xenons. Both work with this change.
//HooGLaNDeR
This post has been edited by HooGLaNDeR: Feb 21 2010, 05:09 PM
Post by: firasgt on March 03, 2010, 04:50:00 PM
looking for magic flasher release.
Post by: PleXo on March 05, 2010, 12:43:00 AM
QUOTE(HooGLaNDeR @ Feb 21 2010, 04:08 PM)
Original line :
nandpro\nandpro %usblpt%: -r256 cb.bin 2 1 won't work on my Xenon (16 MB ) mobo.
Altering it to :
nandpro\nandpro %usblpt%: -r%size% cb.bin 2 1 will work though. I've tested this on 2 different Xenons. Both work with this change.
//HooGLaNDeR
what error are you receiving??
as nandpro shouldnt have any issue with this the way it currently is..
nandpro outputs the txt file at the end it isnt updated every second or so, that wouldnt work...
maybe future holds some goodness
