Discussion in 'Xbox 360 Guides' started by InsaneNutter, Nov 12, 2010.
this method bricked my console into 3 RROD error "0022"
1)If you soldered anything to the mainboard before it occured, whatever you are powering from this point is drawing too much power so get rid of it.Also get rid of everything that you can see that might bridge anything near the GPU.
2) X-Clamp replacement
3) Reflow GPU and HANA chip
4) If it\'s not the GPU/ANA, it might in rare cases be the CPU and can be fixed by reflowing the CPU.
5) if you flash with xell on JTAG-fixed xbox360 this will appear, flash back to original.
6) also can be caused by a broken trace (see link below).
This error is caused by a bridged/shorting solder joint under the GPU, ANA-chip or in between.It can also be power related though, for example if you are drawing power from one of the regulators that power the GPU and HANA-chip.Can also be a component that is missing or damaged so look for missing parts near the GPU and the HANA chip. In extremely rare cases it might also be related to the lines that lead from HANA to the CPU.
The chances are however higher that it is the GPU than the HANA chip so you should always first concentrate on the GPU.
Another cause could be due to a broken trace under the board near one of the ram blocks, check the picture in the reference section. Thank you arvydas for reporting this solution!
All info from Xbox-experts.com - Error code 3 RLOD E10 / 0022
I saw that link.
It was working 100% fine before doing this flash, only thing I can think of is I *did* solder some connections together to not allow the efuse to get blown via updates.
And I did connect a potentiometer to 2 fans (oem fan + 60mm over GPU) to run off that. But what's the difference in the update that changes requirements?
It could just be the things that you soldered drawing more power and that can cause it
Or you could have broke a trace when doing it
ok I used jtag tool and flashed my 360 with my original nand + freeboot, and it boots into dash now with dash 12625. I followed this guide, why am I on 12625 instead of 12611?
You flashed the wrong update perhaps?
Either way you are on the latest dash, there is no real difference between 12625 and 12611, update to the latest DashLaunch and enjoy: https://digiex.net/downloads/downlo...-launch-2-21-freeboot-9199-12611-12625-a.html
I followed your tutorial to a T, don't know the answer why I'm on a different version. I flashed the dashlaunch update and everything went smooth. Thanks
know where I can find the 12625 update so I can get avatars working?
Something must have got mixed up somewhere as I have never linked to the 12625 files in this tutorial.
The avatars for 12625 can be downloaded here: https://digiex.net/downloads/downlo...oard-update-2-0-12625-0-avatars-download.html
8955 to 12611
Hi InsaneNutter..i followed ur guide and it works!! Thanks thanks loooootsss!!!
Just in case anyone wanna know my specs:
It's Jasper 16mb going from 8955 to 12611 (i wrote 'jasper' when using the fbbuild)
The console has a dvd.
I think i don't have the original nand, coz i used the one from backing up my nand using flash360.
The size of smc_config, SMC & KV.bin are 16kb, 12kb & 16kb respectively.
At first i hesitated coz in my understanding this guide wont work for the 'aud-clamp fix' jtag (??)
Pls correct me if i'm wrong.
Coz i dunno how to find out if my jtag is clamp fixed/not, or is there a way to know that without opening the xbox casing?
Anw i gave it a go to see how it turned out..and luckily it worked! Fiuhh..^^
Well thanks again InsaneNutter..appreciate ur hard work to put all the details..
Just wondering, what exactly that's causing an efuse to blow?
I mean can it be when we load certain games, the efuse can just be blown..or ??
Well, i'm a newbie in this kind of thing..could u pls shed some light InsaneNutter..thanks hips!!
System updates case it, basically when an efuse has blown the Xbox 360 can no longer boot a lower kernel.
As the exploit that allows the Jtag hack to work is patched in later updates that means your jtag is no more
So do not accept official system updates and you will be fine, games can include updates however the new Dash Launch ignores the version check and stops you decadently installing system updates. Even without DashLaunch you will be asked to update, say no and all is good.
not technically true taken from c4eva
Slim Lite-On RELEASED 2011-04-08 v1.0 9504
what would actually happen if every efuse blew
At the time I posted it was not released yet so then it was true and with the new dashboard/disc format it don't really matter if its flashed or not because the dashboard flashes to new stock firmware and might require a chip installed to make the system think that it has stock firmware, also taken from c4eva site
I was on there site yesterday looking around for a friend that has a slim and also for a third system with a Samsung drive (unmodded right now)
Thank uu for the explanation..btw how abt the updates for the missing avatar (by Hoxygen92)?
It's an official update, but it's recommended to restore the avatar after upgrading to 12611.
Can it blow an efuse too?
And one more thing, how do we know that we've blown an efuse? Maybe the box shuts down, or..(??) ^^ Thanks..=)
You have to restore the avatars using the official update for the version of FreeBoot you are running.
E.g. if you are on 12611 you need the official 12611 update, that will only restore your avatars and not update your console as the console is already on 12611.
If you are on 12611 and run the official 12625 update, that will update your console and it will no longer be a Jtag unless you took precautions to stop the efuse from blowing.
Just wanted to say thanks a million to InsaneNutter!! I actually signed up just so I could give you the props you deserve for creating such a brilliantly simple guide. I'm a complete and utter noob when it comes to JTAG and I found this guide concise and easy to follow. Also, I was able to do it without having my original NAND by just simply dumping the current one with flash 360. So if anyone else out there is in the same position that I was, (stumbled across quite a few poor souls while looking for helpful info) just follow this guide step by step and you'll be set! Thanks again!!
I'm glad it worked for you with no problems Morbo, it is nice to see the occasional post where someone doesn't have a problem and has updated successfully!
Thanks man for the guide! Unfortunately, things went well up until the end, haha. Anyways, I updated from XBR 8955 to FB 12611 on a xenon. All was good until I went to boot the new dash. It looked good when I saw the new opening sequence, but it jumped to an E71 right after. The console boots fine into xellous though when I hold the eject button on the drive.
- xenon 360
- I didn't do anything precautionary with regards to dash updates (removing resistor, bridging circuit)
- I left the original jtag wiring from the XBR install in place
- I followed the tutorial to the T using a dump of the working XBR 8955 dump taken with flash 360 right before following the tutorial
- my nand did have a few bad blocks (2 during dump, 1 during flash)
- I have an extra intake fan soldered in, 12V'ed. rear fans also 12V'ed
I'm not so sure if the bad blocks had anything to do with it, as flash360 relocated the blocks accordingly during the 12611 flash, but it may be the issue since an E71 is specifically a dashboard error.
Anyways, how would I go about the recovery process right now? Do I have to redo the LPT wiring again? Because I don't have a usb nand reader =(
Thanks in advance!
Separate names with a comma.