|
raidenxtribe
|
 |
« on: February 28, 2011, 10:52:59 AM » |
|
I received 2 already "JTAGGED" xbox, 1 falcon and 1 jasper, backup and writing, according to the sender, were made using pic182455, on first check diodes were soldered nicely, not a farmer job, no damages on MB ... First thing I did was flashing back original dump on the falcon with my dear OLIMEX but RRODding continued to show up, decided to unsolder the NAND and swapping with another one and flashing it again with original dump... RROD 0022 shows up again, i'm short of ideas, i would like to know better the boot process of the Xbox itself to seek the right component to rescue, i presume the boot process starts with the cpu, it checks the NAND than what ?
|
|
|
|
« Last Edit: February 28, 2011, 10:55:33 AM by raidenxtribe »
|
Logged
|
|
|
|
|
jelle2503
|
|
« Reply #1 on: February 28, 2011, 12:14:19 PM » |
|
you wouldn't think these 360's have the RROD as in the RROD? the gpu related error that can be fixed by reflowing or reballing?
also I don't see how swapping NANDs would solve RROD, or have you read some random tutorial online to fix RROD? Doesn't make any sense to me
|
|
|
|
« Last Edit: February 28, 2011, 12:16:29 PM by jelle2503 »
|
Logged
|
*
|
|
|
|
k0mpresd
|
|
« Reply #2 on: February 28, 2011, 01:04:39 PM » |
|
i had a console with 0022. i did a reflow on the gpu and cpu and neither fixed the console.
xboxscene lists 0022: "E10: Unconfirmed: CPU error, generally caused by a poor connection to the mainboard (cold solder joints/bridged solder joints). This can also be triggered by an error with the TSOP."
|
|
|
|
|
Logged
|
|
|
|
|
raidenxtribe
|
|
« Reply #3 on: February 28, 2011, 04:52:08 PM » |
|
you wouldn't think these 360's have the RROD as in the RROD? the gpu related error that can be fixed by reflowing or reballing?
also I don't see how swapping NANDs would solve RROD, or have you read some random tutorial online to fix RROD? Doesn't make any sense to me
And that's why ... E0022 This can also be triggered by an error with the TSOP To be sure the NAND was not damaged during flash with the PIC18F i just swapped it, no big deal to give it a try, 10 minutes more or less... I' m sure there are no damage to solder balls, the 2 consoles had the same problem just after the owner tried to jtag them ... not a coincidence especially on a jasper (i do reballs and i did not see 1 jasper since today with GPU related problems). Back to boot sequence... First CPU, than NAND, than what ? |
|
|
|
|
Logged
|
|
|
|
|
RAMBO
|
|
« Reply #4 on: March 03, 2011, 05:30:33 AM » |
|
i'm a noob here i know, but there is a new version of freestyle dash out. I had someone who bought a jtag from me try to use the dashboard. When they clicked the xex the jtag froze and the on boot gave RROD and showed e79 on the screen. He was able to fix the issue by holding sync in while booting up. He then attempted to use the freestyle xex again and got the same result, RRod, but now he can't clear it with the sync option and is sending it back to me so I can take a look at it.
|
|
|
|
|
Logged
|
JTAG hobbiest
|
|
|
|
Gazcoigne
|
|
« Reply #5 on: March 03, 2011, 07:32:08 AM » |
|
i'm a noob here i know, but there is a new version of freestyle dash out. I had someone who bought a jtag from me try to use the dashboard. When they clicked the xex the jtag froze and the on boot gave RROD and showed e79 on the screen. He was able to fix the issue by holding sync in while booting up. He then attempted to use the freestyle xex again and got the same result, RRod, but now he can't clear it with the sync option and is sending it back to me so I can take a look at it.
I have a XENON JTAG with a similar story was updated to latest FB 0.4, and ran new FSD dash, running fine with console stripped out of case rebuilt case and got RROD 0022 reflowed the GPU several times, no change. starting to suspect the NAND has been corrupted by FSD rather than a normal RROD coz ive fixed tons of them with reflow. am going to reflash the NAND and report back.. |
|
|
|
|
Logged
|
|
|
|
|
RAMBO
|
|
« Reply #6 on: March 03, 2011, 11:02:15 AM » |
|
I would be interested to know if FSD is the cause, since the JTAG in question for me is also a Xenon. I myself have a Xenon too and it runs FSD fine except for it failing to boot up sometimes.
|
|
|
|
|
Logged
|
JTAG hobbiest
|
|
|
|
raidenxtribe
|
|
« Reply #7 on: April 08, 2011, 11:05:26 AM » |
|
Swapping the southbridge would be of any use ?
|
|
|
|
|
Logged
|
|
|
|
|
bugess
|
|
« Reply #8 on: April 10, 2011, 01:51:25 AM » |
|
???boot in 0022 after about 30s = corruption nand content,  refussion the gpu is a 0020 Rod tries with just a xell in nand |
|
|
|
|
Logged
|
|
|
|
|
l_oliveira
|
|
« Reply #9 on: April 10, 2011, 11:41:12 AM » |
|
The proper way to test the consoles is:
1- backup the current flash with SPI connection (LPT or USB flasher).
2- flash small XELL image that matches the board in test.
3- test if it launches.
If you get them to boot with the procedure outlined above there's no hardware damage and it's a matter of corrupted flash image. Proceed to salvage contents of the flash (KV, SMC and smc_config) to create a new flash image.
If you get 0022 still, check if EFUSES blowing was blocked. If it was not blocked and the consoles attempted to update, then efuses were blown.
If this is the case, they're good for the trash bin.
|
|
|
|
|
Logged
|
 It's a Rough World |
|
|
|
bugess
|
|
« Reply #10 on: April 11, 2011, 05:38:39 AM » |
|
If you get 0022 still, check if EFUSES blowing was blocked. If it was not blocked and the consoles attempted to update, then efuses were blown.
how you doing  , you could explain the method |
|
|
|
|
Logged
|
|
|
|
|
xboxbreaker
|
|
« Reply #11 on: April 11, 2011, 06:56:23 AM » |
|
He means if the console was updated (or even a failed update) without the R6T3 resistor removed (or with the bridge discussed at link below) then the Efuses will be blown and the xbox can no longer launch a vulnerable kernal. http://www.xboxhacker.org/index.php?topic=13658.msg102753#msg102753Your original Nand dumps would also not boot if this was the case. |
|
|
|
|
Logged
|
|
|
|
|
l_oliveira
|
|
« Reply #12 on: April 11, 2011, 07:05:57 PM » |
|
If he kept a copy of his CPU KEY from when it was JTAG, it's possible to make an 9199 image with ibuild, which obviously will work.
Of course the console will be then back to old boring normal non JTAG XBOX360 but would work instead of being a paper weight.
Also an console repaired that way is by no means XBL safe, even if you repair the DVD drive to be original.
|
|
|
|
|
Logged
|
It's a Rough World |
|
|
|
raidenxtribe
|
|
« Reply #13 on: April 12, 2011, 04:37:34 PM » |
|
Thank you for all those advice, will test and report results !
|
|
|
|
|
Logged
|
|
|
|
|
raidenxtribe
|
|
« Reply #14 on: April 12, 2011, 05:28:19 PM » |
|
jasper rrod 0022, r6t3 was removed ... i'm going to try "xell only" now ...
|
|
|
|
« Last Edit: April 12, 2011, 05:32:16 PM by raidenxtribe »
|
Logged
|
|
|
|
|
raidenxtribe
|
|
« Reply #15 on: April 26, 2011, 07:27:36 AM » |
|
Failed again with xell only, 0022 still there ... any suggestion ?
|
|
|
|
|
Logged
|
|
|
|
|
l_oliveira
|
|
« Reply #16 on: April 26, 2011, 08:19:08 AM » |
|
Well, you know the CPUKEY ? The only suggestion I have for you is you attempt to build an proper 9199 dash image with ibuild and flash then see if it boots. If it boots you're out of luck because it has been updated and R6T3 was removed after $#!t happened.
If it does not boot you're out of luck because it has a hardware problem...
Either way you're out of luck. 0022 means the CPU timed out (did not reply SMC that it's alive) and usually means there's something wrong with the software. It does not explain why the CPU failed to start.
|
|
|
|
|
Logged
|
It's a Rough World |
|
|
|
Dilber MC Theme by HarzeM