Jump to content


Photo

Complete Guide To Installing Xbreboot For Noobs


  • Please log in to reply
307 replies to this topic

#1 Roamin64

Roamin64

    X-S Member

  • Members
  • Pip
  • 89 posts

Posted 06 December 2009 - 02:06 AM

**UPDATE : XBReboot is now supported on 256 / 512 mb nands!

The very first thing you need to check, is your xbox kernel. At the time of writing, the most recent kernel is : 2.0.8955.0
  • Turn on your xbox and go to console settings.
  • Go to system info, the kernel version is on top right.
IPB Image

As of 5/12/09 (December 5th 2009) If you have kernel 2.0.8495.0 or HIGHER, YOU CANNOT INSTALL XBReboot.

If you have kernel 2.0.7371.0 or lower, there is one more check to do, which requires you to read the nand chip with a homemade lpt nand reader. USB Version

** There is no other 100% way of knowing your CB version without reading the nand.

Follow this thread to build a cable, Simple Db-25/cat5 Lpt Nand Dump/flash Cable Tut



Use this site to determine which motherboard type you have : Xbox 360 revisions OR check this picture.

Once the cable is ready and double checked, grab nandpro20b from Xbins (Make sure its version 2.0b)

Follow these steps to read your nand :
  • Make sure port95nt.exe is installed, if it's not, install it (from nandpro20b folder) you might need to reboot.
  • Plug your 360, but don't power it on.
  • Plug the lpt cable
  • Go to the nandpro20b folder and type :
  • nandpro lpt: -r16 orig.bin
  • MAKE SURE THAT THE FLASH CONFIG SAYS : FlashConfig:01198010 , if it doesn't , refer to troubleshooting at end of guide.
  • Wait patiently...
  • If there are errors, refer to trouble shooting at end of guide.
  • If there are no errors, read the nand again :
  • nandpro lpt: -r16 orig2.bin
  • Reading it a 3rd time is not a bad idea.
  • Don't power on the console in between reads , especially not without dvd drive connected , or your dumps will mostlikely not match.
Once you have a good dump , at any point you can restore it to your 360. Follow instructions at end of guide.

How to make sure you have a good dump :
  • First , compare the dumps together using a hex editor or other tool, they should match 100%
  • Grab Degraded 1.1b from Xbins. *** You can also use 360 Flash tool to verify CB.
  • Run Degraded and click settings, enter key you found using google "Degraded 1BL key" should pop right up.
  • After you set the key click Valid next to it and set the File System Start to 39. Click ok.
  • Open orig.bin
  • If you get, cannot read file , you must edit the orig.bin file. Make a copy of it, origcopy.bin and open it up in your hex editor. At offset 0x0012 , you will see 2004 - 2007 Microsoft Corporation...
  • Change it to : 2004 - 2005 Microsoft Corporation and it will open with Degraded :
IPB Image
(This picture shows an unexploitable CB version)

If Degraded shows you some bad blocks, refer to the bad blocks section at the end of the guide.

Check which version of CB you have.

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

More info here :
Xbox 360 Kernel

If you have an exploitable CB , then you are in luck , if you dont, then for now , there is nothing you can do but find another xbox 360.

So you have a 7371 or ealier kernel , and an exploitable CB you can install the JTAG HACK Refer to the picture for your motherboard under the Required Soldering topic. Once you wired your 360 this way, you install XBR to your nand.


Flashing XBR to your nand :
  • Grab the XBR_8955 matching your board from Xbins
  • Go to your nandpro20b folder
  • nandpro orig.bin: -r16 rawkv.bin 1 1
  • nandpro orig.bin: -r16 rawconfig.bin 3de 2
  • Now that you have extracted your keyvault and config blocks from your orig.bin, inject them in the xbr_8955.bin of your motherboard version :
  • Rename the xbr_8955.bin of your board to xbr.bin to simplify things.
  • nandpro xbr.bin: -w16 rawkv.bin 1 1
  • nandpro xbr.bin: -w16 rawconfig.bin 3de 2
  • Now that you've injected your keyvault and config into xbr.bin all you need to do is flash it back to your nand.
  • nandpro lpt: -w16 xbr.bin
  • Once done , unplug lpt cable from pc.
  • Users mentionned leaving the console unplugged, and powered off for 30 seconds in order to clear the SMC from memory.
  • Turn on xbox and enjoy XBR.
  • Problems? Refer to troubleshooting and end of guide.
Troubleshooting

I've gathered this from reading other people's posts, as i have not experienced any problems at all, except read errors above 0x200 while making first dump of my nand.

Nandpro / LPT notes : You should try to keep your cable as short as possible to avoid errors.

Nandpro FATAL ERROR :
  • nandpro only works with certain USB adapters, and real LPT ports, not pci to lpt cards.
  • Check wiring, check pc BIOS settings for parallel port mode SPP (Normal) but users report nandpro working fine on most lpt settings.
  • Is port95nt.exe installed? Run port95nt.exe again
  • Try a different pc
Nandpro Flashconfig: 01198010 / reading errors :
  • Are you using the diode as explained in the cable making tutorial? The diode is a hit and miss, if you receive config 01198010 then its not needed. The diode goes with the black line towards the board , and pin 11 of lpt port connected to the other leg.
  • Shorten your wires
  • Are you using the 5 resistors? Some boards require you to solder directly, without using the resistors. This will fix reading errors above 0x200 that some experience.
  • Check solder joints, make sure they are clean and they are not touching each other.
Nandpro Error 250:
  • Error 250: This , in my experience means that the block is full of 0's, and is not an error you should be concerned about if you come across it once or twice. Of course if you keep getting Error 250, there might be an error elsewhere , or maybe you've flashed 0's all over your nand.
RRoD / Blackscreen / Error 79 :
  • Do you have an exploitable CB? People seem to only look at their dash board and see it's 7371 or lower and think they can install XBR without verifying their CB to see if JTAG hack will work.
  • Did you inject the rawkv.bin into xbr.bin ? (nandpro xbr.bin: -w16 rawkv.bin 1 1)
  • Did you inject the rawconfig.bin into xbr.bin ? (nandpro xbr.bin: -w16 rawconfig.bin 3de 2)
  • Did you have Bad Blocks in your orig.bin ? Did you follow the Bad Block Installation notes?
Restoring your original nand.
  • Make sure port95nt.exe is installed, if it's not, install it (from nandpro20b folder) you might need to reboot.
  • Plug your 360, but don't power it on.
  • Plug the lpt cable
  • Go to the nandpro20b folder and type :
  • nandpro lpt: -w16 orig.bin
  • Your nand is back to its original state.
Bad Blocks in the nand

If Degraded shows you some bad blocks, you will have to move the blocks from your xbr.bin to where they are remapped.
IPB Image

You can use this tool : Bad Block Remapper

If you want to do it manually, you have to do this:
  • Take the picture above as example.
  • It says: Note : Block 0x2CE found at 0x3F8
  • This is where the bad block 0x2CE was remapped.
  • nandpro xbr.bin: -r16 block2ce.bin 2ce 1 (Reads block 0x02CE and saves as block2ce.bin)
  • nandpro xbr.bin: -w16 block2ce.bin 3f8 1 (Write block2ce.bin to 0x3f8 where block is remapped)
  • You will have to do this for each block.
  • Here is the "formula":
  • nandpro xbr.bin -r16 blockXXX.bin XXX 1 (Where XXX is the bad block number)
  • nandpro xbr.bin -w16 blockXXX.bin YYY 1 (Where YYY is the address where block is found in degraded)
Tips on finding a xbox with an exploitable CB version
  • According to this post most boards manufactured after june 2009 should come with an unexploitable CB version so seek something earlier.
  • Obviously, must be be pre summer 09' update (kernel 7371 and lower)
  • Find your serial number inside your xbox by going to console settings , system info. This is the real serial number, if you bought the 360 second hand , nothing guarantees the information on the back being accurate.
  • There is one trick to find the manufactured date with the serial number, this site shows how. The last 5 digits of your serial number determines the date YWWFF 74902 would be 2007 week 49 (december) factory code : Mexico
  • Even if it was manufactured before june 2009, if its a second hand console , maybe it was sent to microsoft at some point and it could have been update then.
Playing content from a hdd that wasn't signed to this console

I paid for a lot of microsoft xbla games, and i believe it is my right to play on both my xbox as i please, so here i will give the gross method of playing your 360 xbla games and dlc on this XBR kernel.
  • Unscrew your hard drive case until you have just the hard drive and plug it in a SATA port of your pc.
  • Grab xplorer360 from xbins and execute it.
  • Open Hard drive
  • Go to partition 3
  • Your games are in Content\0000000000000
  • Extract the content you want.
  • Most xbla should be contained in a single file
  • To see the title of the content, hex edit one of the content file the title of the xbla or the dlc is usually at 0x412
  • Grab Yaris-Swap from xbins
  • Open content file and patch it
  • Inject back into hdd using xplorer360
  • xplorer360 is drag and drop, use it
  • xplorer360 needs a modification in order to see 120gb drives properly, follow this link.
Thanks to the authors of all the tools mentioned in this post, and to all the hard work that everyone did involving them.

Feel free to let me know if anything needs to change, if anything was out of line (rules wise) or if the topic is even in the right section smile.gif

Edited by No_Remorse_666, 09 March 2010 - 03:07 AM.


#2 tonybologna

tonybologna

    X-S Member

  • Members
  • Pip
  • 143 posts
  • Location:USA-Tennessee
  • Interests:sports,hunting,fishing,video games,etc.
  • Xbox Version:none
  • 360 version:v3.0 (falcon)

Posted 06 December 2009 - 06:21 AM

Thanks for this. I also posted this over at 360iso & gave you credit for it. I took no credit but just posted it because so many people are struggling with this hack. Good job! wink.gif

Edited by tonybologna, 06 December 2009 - 06:27 AM.


#3 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 07 December 2009 - 11:00 PM

I like to think of myself as being a little more than a newb when it comes to soldering and fallowing directions to the letter. But for the life of me I cant seem to get this to work.

I have created the cable just like the tutorial suggests. Fallowed everything perfectly. Tested every connection with an ohm meter from the pins to the motherboard and everything matches just as it should. I have tried 5 different PC's and 3 different 360 revisions and not for the life of me can I get lptpro to detect anything.

All I get is testing LPT device address:0378 ect for all 3 addresses and then (could not detect a flash controller)

Same result no matter what PC or 360 I use. When creating the cable I used the 100 ohm resisters and diode on pin 11. I even tried it without the diode just for kicks. And of course I installed the Port95nt driver.

Anyone have a clue as to what I may be doing wrong here?

Edited by Ranger72, 07 December 2009 - 11:06 PM.


#4 thwack

thwack

    X-S Freak

  • Last Chance
  • PipPipPipPipPip
  • 1,334 posts
  • Location:Yorkshire at heart.....
  • Xbox Version:unk
  • 360 version:unknown

Posted 07 December 2009 - 11:05 PM

QUOTE(Ranger72 @ Dec 7 2009, 10:00 PM)  

I like to think of myself as being a little more than a newb when it comes to soldering and fallowing directions to the letter. But for the life of me I cant seem to get this to work.

I have created the cable just like the tutorial suggests. Fallowed everything perfectly. Tested every connection with an ohm meter from the pins to the motherboard and everything matches just as it should. I have tried 5 different PC's and 3 different 360 revisions and not for the life of me can I get lptpro to detect anything.

All I get is testing LPT device address:0378 ect for all 3 addresses and then (could not detect a flash controller)

Same result no matter what PC or 360 I use. When creating the cable I used the 100 ohm resisters and diode on pin 11. I even tried it without the diode just for kicks.

Anyone have a clue as to what I may be doing wrong here?


Have you tried it without the resistors?

#5 dstruktiv

dstruktiv

    X-S Senior Member

  • Members
  • PipPip
  • 235 posts
  • Location:New Zealand
  • Xbox Version:none
  • 360 version:v3.0 (falcon)

Posted 07 December 2009 - 11:09 PM

QUOTE(Ranger72 @ Dec 8 2009, 10:00 AM)  

I like to think of myself as being a little more than a newb when it comes to soldering and fallowing directions to the letter. But for the life of me I cant seem to get this to work.

I have created the cable just like the tutorial suggests. Fallowed everything perfectly. Tested every connection with an ohm meter from the pins to the motherboard and everything matches just as it should. I have tried 5 different PC's and 3 different 360 revisions and not for the life of me can I get lptpro to detect anything.

All I get is testing LPT device address:0378 ect for all 3 addresses and then (could not detect a flash controller)

Same result no matter what PC or 360 I use. When creating the cable I used the 100 ohm resisters and diode on pin 11. I even tried it without the diode just for kicks.

Anyone have a clue as to what I may be doing wrong here?


I've just followed the instructions to the letter on a Falcon board and am now successfully dumping my nand pop.gif (12MB done so far without errors).

I used the 100ohm resisters and the 1N4148 diode. I've read in numerous places that you may or may not need the diode, you also may get away without using the resistors. Try shortening your cable and see if that helps (Although mine is roughly 1 metre long and works fine).

My wiring is 360 -> CAT6 Solid core network cable wires -> Female DB29 plug (With 5x resistors and 1x diode) -> Male to Male LPT cable -> Intel computer with 945G chipset -> Windows XP 32bit -> Nandpro

I can't remember exactly what parallel port mode I have set in my BIOS but will check after this dump completes.


#6 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 07 December 2009 - 11:30 PM

QUOTE(thwack @ Dec 7 2009, 05:05 PM)  

Have you tried it without the resistors?



No I have not tried it without the resisters. I am now making another cable and using a normal LPT printer cable cut about 2 feet long. I will try it once without the resisters and see what happens.

QUOTE(dstruktiv @ Dec 7 2009, 05:09 PM)  



I used the 100ohm resisters and the 1N4148 diode. I've read in numerous places that you may or may not need the diode, you also may get away without using the resistors. Try shortening your cable and see if that helps (Although mine is roughly 1 metre long and works fine).

I can't remember exactly what parallel port mode I have set in my BIOS but will check after this dump completes.


i tried it without the diode. The first cable i made was pretty short. Next cable I am making will be shorter yet.


#7 LiGhTfasT

LiGhTfasT

    X-S Senior Member

  • Members
  • PipPip
  • 205 posts
  • Xbox Version:v1.0
  • 360 version:v1 (xenon)

Posted 07 December 2009 - 11:39 PM

Ranger72: Make sure you have the power brick plugged in and switched on at mains... that got me the first time

then i have error 0 no matter what i did so i removed the cat5 socket and wired direct with diode on db25 and all resistors... so far had 3 dumps all the same biggrin.gif


#8 vintage_guitar

vintage_guitar

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,441 posts
  • Xbox Version:v1.4
  • 360 version:unknown

Posted 07 December 2009 - 11:48 PM

Remember to make the cable as short as possible, that is a big issue. Also try without resistors or lower ohm versions.

#9 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 07 December 2009 - 11:56 PM

QUOTE(LiGhTfasT @ Dec 7 2009, 05:39 PM)  

Ranger72: Make sure you have the power brick plugged in and switched on at mains... that got me the first time

then i have error 0 no matter what i did so i removed the cat5 socket and wired direct with diode on db25 and all resistors... so far had 3 dumps all the same biggrin.gif



I did try with the power brick connected. When the LPT cable is connected the console will not power on (pretty sure it is not supposed to be turned on anyway) but from some tutorials I read that at some point the power may come on anyway on its own and as stated with the cable connected to the PC even if I hit the power button on the console it does not power on.

I even tried to connect a direct ground wire from the console to the PC just to see if that would be an issue.

The cable I am making now will not have any resisters just so I can see if I can get some type of confirmation that it is at least detecting the flash chip.

This cable is about 2 feet long.

#10 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 08 December 2009 - 12:29 AM

Second cable I just made without any resisters or diode does the same thing as the other cable. Still does not detect any flash chip.

Normally with the lpt cable connected to the PC if I hit the power button on the console should it power on? When I hit the power button it does nothing.

I also tried every different variation of the lpt port from within the bios as well.

Edited by Ranger72, 08 December 2009 - 12:30 AM.


#11 vintage_guitar

vintage_guitar

    X-S Freak

  • Members
  • PipPipPipPipPip
  • 1,441 posts
  • Xbox Version:v1.4
  • 360 version:unknown

Posted 08 December 2009 - 12:59 AM

The xbox should not turn on when connected through LPT to PC, this is correct. However, it may turn on and off by itself while reading/flashing, which happens to some people and not others, and is not an issue. Try making your cable shorter. Also which settings did you use in BIOS? You should first try SPP. Then try ECP, etc. Just keep fiddling with it.
Ok I see you fiddled with BIOS settings. Hmm.. cable length is all i can think of. Mine wouldn't work unless it was about 10inches-1 foot long.

Edited by vintage_guitar, 08 December 2009 - 01:07 AM.


#12 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 08 December 2009 - 01:08 AM

QUOTE(vintage_guitar @ Dec 7 2009, 06:59 PM)  

The xbox should not turn on when connected through LPT to PC, this is correct. However, it may turn on and off by itself while reading/flashing, which happens to some people and not others, and is not an issue. Try making your cable shorter. Also which settings did you use in BIOS? You should first try SPP. Then try ECP, etc. Just keep fiddling with it.



I tried every bios variable option there is on each of the 5 PC's I have tried this on. My newest cable I just built is about 2 feet long. Any shorter and I will have a problem trying to find a place to sit the console any closer to the PC.

all 3 of the different 360 versions I have tried (zenon, falcon, and jasper) all have the older pre summer dashboard installed.

To be honest I am at wits end on this. I cant think of any single variable I have missed.

#13 popaman

popaman

    X-S Member

  • Members
  • Pip
  • 72 posts

Posted 08 December 2009 - 03:32 AM

my first pc it read the nand but all the dumps werent the same

the second pc did the same

the third pc read the nand and all dumps were exactly the same and everythin went ok smile.gif

so im sayin that your problem probably isnt a pc, if its doin the same thing between all five of them. I would triple check your connections on the lpt connector and make absolutely sure that you have pins 1,2,11,14,16,17,and 18.

All pc's I used had the lpt port on the motherboard. I believe pci lpt cards dont work or are ify.

#14 rage10

rage10

    X-S Enthusiast

  • Members
  • 2 posts

Posted 08 December 2009 - 05:00 AM

QUOTE(Ranger72 @ Dec 7 2009, 11:30 PM)  

No I have not tried it without the resisters. I am now making another cable and using a normal LPT printer cable cut about 2 feet long. I will try it once without the resisters and see what happens.
i tried it without the diode. The first cable i made was pretty short. Next cable I am making will be shorter yet.


Hi Ranger72.. i had the same issue. tried a few diffent pc etc.

then i found that i soldered the parallel port incorrectly. ensure your pin numbers are correct.

#15 Ranger72

Ranger72

    MOD GOD

  • Head Moderators
  • PipPipPipPipPipPipPipPipPipPipPip
  • 7,805 posts
  • Gender:Male
  • Location:Cumberland MD.
  • Xbox Version:v1.6
  • 360 version:v4.0 (jasper)

Posted 08 December 2009 - 05:05 AM

QUOTE(rage10 @ Dec 7 2009, 11:00 PM)  

Hi Ranger72.. i had the same issue. tried a few diffent pc etc.

then i found that i soldered the parallel port incorrectly. ensure your pin numbers are correct.


On both cables I verified every connection from the adapter that connects to the PC to the motherboard contacts using an ohm meter.

I will check them again tomorrow just to make sure.

Thanks for the help guys.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users