You are viewing our Forum Archives. To view or take place in current topics click here.
How to Fix Jtag/Xbox Errors With and W/O Original Nand
Posted:

How to Fix Jtag/Xbox Errors With and W/O Original NandPosted:

Chronic_Modz
  • Prospect
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Do to the Mass Amount of Topics concerning RROD and "E" Errors on Modified or Stock
Xbox 360 Consoles, I have made this Tutorial to Reduce the Spam.



ALL Xbox 360/Jtag "E" Errors Number Error Solutions.

E45: Unknown (Most Likely Dashboard MisCoding, Very Rare)

E64: DVD Drive Error.... DVD Timeout, Wrong firmware, dvd is without f/w chip, etc.

E65: DVD Drive Error.... DVD Timeout, Wrong firmware, dvd is without f/w chip, etc. This can also be caused by the tray not being fully closed on boot.

E66: DVD Drive Error: DVD model, or version does not match that of the version expected by the dashboard. OR the firmware version on the drive is older then the firmware version expected by the dashboard. Make sure the DVD drive is of the same version originally included with the console and that it is using either the original firmware included with the console or newer.

E67: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it

E68: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it, This can also be caused by a Hard Drive Eprom Error. Some also believe this might be caused by a problem with the fans.

E69: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it

E71: possibly a dashboard update error, Check below in the "Console Reset Codes" for instructions. If that does not work there is no other solution and the console must be sent back to MS for repair.

E72: (Unknown, Possibly Motherboard Short or Dashboard Disable)

E73: General Hardware Error: Ethernet port... this error is caused by a problem with the Ethernet port.

E74: AV cable error... There is a problem with the AV cable, try using a different AV cable. If the cable is known to be working then there is a 90% chance it's a scaler chip problem (the "ANA" or "HANA" chip connected directly to the AV cable) in rare cases it is the GPU.

E76: (Unknown, Possibly Short in Motherboard)

E79: Hard Drive Error... It could be a problem with the Hard Drive itself or a problem with the internal connection to the hard drive, Try removing the hard drive and playing without it
0001 power supply problem
0002 Network Interface problem
0003 Power problem could be the PSU could be the GPU/CPU, somehow the console isn't getting clean power from the power supply.
0010 over heating
0011 over heating - If you are receiving this error after disassembling your console make sure to all 8 of the heatsync screws are tightened securely to the board/heatsink holes.
0012 over heating
0013 over heating
0020 (Not yet known, possibly overheating)
0021 DVD Drive Time out - Can be caused by problems with a firmware flash. This is also speculated to sometime be caused by a problem with the southbridge chipset on the motherboard.
0022 GPU Error / GPU Overheating
0023 (not yet known)
...
0101 (not yet known)
0102 unknown error
(Credits to Google for finding Info )


How To fix Jtag Bad Flash Christmas Lights/RROD Without Orig. NAND


Step 1:
Getting the CPU key.
Have a camera ready to take a picture of the Fuse Set's that pop up briefly on xell (you get to xell by turning you box on with the eject button)
Take a picture that includes fuse set 3,4,5,and 6. These contain your CPU key.
[ Register or Signin to view external links. ]
Take either 3 and 5 or 4 and 6 or 3 and 6 or 4 . This will make up your cpu key.

So for example.
I will take 3 and 5.
3= E42D681ED06A6D1C
5= 1FFD8E48C56A2058

So the CPU Key is - E42D681ED06A6D1C1FFD8E48C56A2058

This key is the one you also put into the drive of the xbox when modding it.

Adding any combonation of these will make your CPU key.


2.) Flash360

3.) RAR that contains freeBOOT v0.032, libeay32.dll, 9199 files, and donor files

4.) 1BL Key (just google for 1BL XBOX) It can't be posted because it is illegal.

5.) A Hex editor - Hex Workshop or HxD (Either one will work fine)

6.) The official MS Xbox Update $SystemUpdate_9199.zip (Optional and can be found on Xbox.com)

7.) A flash drive


How to build a FreeBOOT Image:

1.) Boot into Xellous(by pressing the eject button) and read out your CPU Key(fuse sets 3&5 combined)

2.) Start Flash360 and create a Full Nand Backup of your XBR3 (flashdmp.bin) Make sure to make a backup of this flashdmp.bin file just in case.

3.) Open flashdmp.bin with a Hex editor, at the top you should find CB0=####. Record that number

4.) Extract xbr to freeboot , the libeay32.dll should go into *\xbr to freeboot\

5.) Copy your XBR3 Backup (flashdmp.bin) to *\xbr to freeboot\bin

6.) open the Dos Command prompt (Start>Run> type 'cmd' )

7.) cd to the freeboot root directory ("cd *\xbr to freeboot") and paste:

8.) ibuild x -d data\ -b "1BL Key" -p "CPU Key" bin\flashdmp.bin
"1BL Key" replace it with the 1BL Key
"CPU Key" replace it with your CPU Key

9.) THERE WILL BE AN ERROR, but we don't care about it, because we only need 3 files from it

10.) Go to *\xbr to freeboot\data delete everything except only these 3 files should stay kv.bin, smc.bin and smc_config.bin

11.) Put all of the files in the 9199 folder into the *\xbr to freeboot\data folder

12.) Now open the Donor Files folder.

13 & 14) In the Donor Folder, open the folder for your Motherboard (Falcon, Jasper, Xenon). Then choose the folder that is the number of your CB0, found with the hex editor earlier.

15.) Copy the files (crl.bin, crl.bin.meta, extended.bin, extended.bin.meta, odd.bin, odd.bin.meta, secdata.bin, secdata.bin.meta) into *\xbr to freeboot\data

16.) Open the Dos Command prompt

17.) cd *\xbr to freeboot

18.) ibuild.exe c freeBOOT -c [Console] -d data\ -p [CPU Key] -b [1BL Key] bin\image.bin bin\fuses.bin

[Console] replace it with falcon, xenon, jasper, jasper256 or jasper512
[1BL Key] replace it with the 1BL Key
[CPU Key] replace it with your CPU Key

the Image creation needs to finish without errors!!!!

19.) You should find now an image.bin in your *\xbr to freeboot\bin folder, the size should be the same as your XBR Nand Backup(16 MB most likely unless you have a jasper 256 or 512).

20.) Rename now image.bin to updflash.bin and put it on the root of your USB Stick where you have flash360 on it

21.) Connect the Usb Stick to your console and open Flash360.xex

22.) Now flash your new image on with A B A, if there is a KV mismatch, then you did something wrong, wrong CPU Key...Make sure that Flash360 automatically shuts your console down, don't shut the console down manually by yourself.

23.) Now you should have the freeBOOT image installed, check it out in your Console Settings, it should tell you 2.0.9199.0
(If you get Christmas lights or you get a black screen then refer to the trouble shooting at the end of the tutorial. You shouldn't have a problem, but if you do then refer to the trouble shooting.)

OPTIONAL
24.) Now to make it complete we install also the official Systemupdate, to install the missing files.

25.) Extract the $SystemUpdate_9199.zip and burn a CD or put it on a flash drive with $SystemUpdate_9199 on it

26.) Now put the CD or flash drive into your Xbox, start something and it should tell you that there is a new update available, install it.

27.) after a reboot your are finally at 2.0.9199.0


Trouble Shooting:
Q: I get Christmas lights(flashing between red and green lights), black screen, fuzzy screen where I can't read anything, or some other problem that causes me to not be able to use my JTAG. What do I do?

A: Take your original unmodified flashdmp.bin file that you originally had from Flash360 and put it on the root of your flash drive. Then delete every other file on your flash drive besides that one. Then plug your flash drive into your Xbox 360 and boot into XeLL by pressing the eject button. XeLL should recognize the flash drive and begin writing the old image(flashdmp.bin) back your NAND. Give it a few(like 2ish) minutes to recognize it. If it doesn't recognize it, then make sure you don't have any controllers or devices connected to the console besides the flash drive.

Hope this Helped, Remember to say thanks

The following 1 user thanked Chronic_Modz for this useful post:

RedRings (11-22-2010)
#2. Posted:
TTGxM40SNIPES
  • TTG Warrior
Status: Offline
Joined: Oct 12, 200914Year Member
Posts: 9,687
Reputation Power: 451
Status: Offline
Joined: Oct 12, 200914Year Member
Posts: 9,687
Reputation Power: 451
wow post this in tutorials =)


good post
#3. Posted:
RedRings
  • TTG Senior
Status: Offline
Joined: Aug 02, 201013Year Member
Posts: 1,263
Reputation Power: 56
Status: Offline
Joined: Aug 02, 201013Year Member
Posts: 1,263
Reputation Power: 56
Sourced this article from a google search: [ Register or Signin to view external links. ]

Went into a bit of research, +thanks.
#4. Posted:
Chronic_Modz
  • Prospect
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
TTGxM40SNIPES wrote wow post this in tutorials =)


good post


Thanks, But i see topics in this section all the time asking for info on how to fix these problems :/
#5. Posted:
Chronic_Modz
  • Prospect
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
-RROD- wrote Sourced this article from a google search: [ Register or Signin to view external links. ]

Went into a bit of research, +thanks.


Yeah I see so many topics like "+Rep if you help me fix RROD or E79" etc..
#6. Posted:
TTG_iKYLE
  • TTG Addict
Status: Offline
Joined: May 12, 201013Year Member
Posts: 2,302
Reputation Power: 230
Status: Offline
Joined: May 12, 201013Year Member
Posts: 2,302
Reputation Power: 230
[ Register or Signin to view external links. ]

sorry want to use it
but posted befor i posted 1
#7. Posted:
Chronic_Modz
  • Prospect
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
youmadbro? troll the jtag section cuz you aint got one?
#8. Posted:
Chronic_Modz
  • Prospect
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
Status: Offline
Joined: Jun 30, 201013Year Member
Posts: 615
Reputation Power: 23
updated. hope this helps.
#9. Posted:
-VeteranHacker-
  • Prospect
Status: Offline
Joined: Oct 11, 201013Year Member
Posts: 688
Reputation Power: 26
Status: Offline
Joined: Oct 11, 201013Year Member
Posts: 688
Reputation Power: 26
Secondary error code: 0102 is the same as E18. It is a problem with the RAM chips and the GPU chips etc. But it is also sometime (especially on JTAGS) made by "Cold Solder".

A reflow would fix this for a while but a complete reball is recomended.
Jump to:
You are viewing our Forum Archives. To view or take place in current topics click here.