Falcon R-JTAG Install Issue, Please Help! (0x00000000 + 0010)

[jsheradin]

Before I do the reflow, I just wanted to make absolutely sure that it is necessary. I did a little more digging and found that a bad SMC causes every one of the symptoms that I have had occurring (NAND R/W fail, no power, bad point readings). It explains everything but the 0010 error. Is there any way to test if the SMC is corrupt? I don't know if it means anything, but when building Xell even though I selected Falcon it builds it with the Jasper 2.3 SMC. Is that normal? I have a copy of the NANDs that I got earlier (which is what is currently on the console, still dead as a door nail). Should I unhook the Demon and try the bad flash recovery/short technique (link below)? That way I can at least see if the JRP will write to it, hopefully confirming the bad SMC theory. Is there any way I can download a ready made falcon Xell? Please share your opinions! Even just a simple "yeah I guess" will reassure me!

My NANDs: https://www.dropbox.com/s/jt0iigqd4mwj25d/Nands.zip

Flash Controller bypass: http://team-xecuter.com/forums/showthread.php/52213-Bad-Flash-To-Nand-How-To-Recover-!

 

[jsheradin]

Ok, so I flashed a freshly generated xell file to the NAND via Demon ToolKit, desoldered the Demon, put a new Nand-X QSB on (found one in a drawer, from another kit I think) soldered that up, and re-installed the glitch chip (and moved the green wire to the correct point). I plugged in the PSU, attached my JRP, loaded up the Rater feature of J-Runner, and hit boot. The console gives no response, the green light on the glitch chip doesn't blink (red is lit, as is the green one on the JRP), but Rater gives me this:

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 04
Post 04
TIMEOUT or SMC CORRUPTED Shutting Down
Shutdown
Power Up
Waiting for POST to change

Thats all it has so far, but I am letting it run as I type.

So it looks almost certain that the SMC is corrupt, is this fixable? Can you point me in the right direction on how to rebuild it? Thanks in advance!

 

[jsheradin]

Ok, so I just wen tout to check on the Xbox and there was still nothing, just a bunch of timeouts. I retried it with an older 203W power supply and got a TON of errors, but when I switched back to the 175W it just did the timeouts. I think tomorrow I will reflow the SouthBridge and see if I get any better results. If that doesn't work, I think I'll just cut my losses and find another Xbox at a yard sale or something to use the kit on. Situation seems pretty hopeless to me.

Rater Results: http://pastebin.com/DYt9RgTD

 

[gavin_darkglide]

your southbridge is fine. the system turns on...... the problem is that you need your cpu key to create a nand from a donor nand....... which means your best bet is to flash ecc, and jtag smc to console, and try to get the cpu key from it..... if that works, then i would try to pull the keyvault from the corrupted nand image. without that the console is basically a brick....... i guess you may be able to swap the keyvault from a donor nand, but the system will never run stock again.

 

[jsheradin]

I am fine with the console never running stock again, phats are basically worthless unless modded. Are you saying that I need to make the xell reloaded .ecc and then stitch in a donor SMC from a falcon JTAG? If that is then flashed to the console should it work? Once I have the CPU key I then use that to build a NAND from scratch? Could you please make a step list and include what software and files are needed to pull this off? I have plenty of banned KV's (both type A and B) from when I used to host lobbies, could I just use those instead (and yes I know that it would change the serial number)? Thanks a lot for the help!

 

[jsheradin]

So, I found a tutorial on how to build a NAND from scratch, but I am still unclear on how I am supposed to build Xell with the "JTAG SMC". Could you please elaborate on that process? Thanks in advance!

Create NAND from scratch: http://www.xpgamesaves.com/topic/16...-nand-with-just-a-cpu-key-with-a-donar-nand/#

 

[gavin_darkglide]

On this i dont know, but i would assume the standard jtag ecc would have the modified smc built in to enable the jtag hack to boot xell.

 

[jsheradin]

On this i dont know, but i would assume the standard jtag ecc would have the modified smc built in to enable the jtag hack to boot xell.

Can anybody confirm that this would work? Since this R-JTAG is apparently based on the original SMC/JTAG hack it sounds feasible. If it were that simple why does the xell ecc need to be created from the NAND in the first place? If this were to be possible, would I just fill in the J-Runner settings as if it were a normal JTAG with the AUD_CLAMP option?

 

[gavin_darkglide]

the ecc isnt created from your nand anymore..... they are pre-compiled. Some one leaked the unlocked bootloader, so now when you say create ecc, j-runner pulls up the correct file based upon how you chose to set it up.

 

[mrdrifta]

It sounds like your problem is writing to your nand, so trying to get xell to boot is making a bigger problem for yourself.

If i were you, i would use your demon to write the original nand back to the console. It loads in J-Runner so it seems to be okay.

Desolder all rjtag quick solder boards so only the demon is installed. Try booting your xbox nand that way. You may want to try writing back the original nand through demon, power cycling the xbox(removing power for two minutes) and then writing the original nand via demon again. Power cycle the xbox again and then try reading the xbox nand through demon.

If all is well you should get an identical nand to one of your two original nands.

Once your console boots your original nand, then proceed to flash rjtag to your demon nand( Load original nand in J-Runner, select RJtag and Aud_Clamp if your using that method and click Create Xell-Reloaded. Then select Advanced > Write Demon.)
Make sure you power cycle the console after each time you write to the nand.

 

[jsheradin]

I'm going to go die in a hole: http://team-xecuter.com/forums/show...-JTAG-Install-NAND-Error-NO-BOOT!-PLEASE-HELP!!!

 

[jsheradin]

It sounds like your problem is writing to your nand, so trying to get xell to boot is making a bigger problem for yourself.

If i were you, i would use your demon to write the original nand back to the console. It loads in J-Runner so it seems to be okay.

Desolder all rjtag quick solder boards so only the demon is installed. Try booting your xbox nand that way. You may want to try writing back the original nand through demon, power cycling the xbox(removing power for two minutes) and then writing the original nand via demon again. Power cycle the xbox again and then try reading the xbox nand through demon.

If all is well you should get an identical nand to one of your two original nands.

Once your console boots your original nand, then proceed to flash rjtag to your demon nand( Load original nand in J-Runner, select RJtag and Aud_Clamp if your using that method and click Create Xell-Reloaded. Then select Advanced > Write Demon.)
Make sure you power cycle the console after each time you write to the nand.

It all sounds right, but at the moment my Demon is kind of caught up in what could be one of the worst decisions ever.

My idiot mistake: http://team-xecuter.com/forums/show...-JTAG-Install-NAND-Error-NO-BOOT!-PLEASE-HELP

 

[mrdrifta]

Try updating the demon firmware before doing anything else, also make sure you copy your jasper nand dump to a safe place. J-Runner sometimes moves nand dumps to strange places if you read more than one consoles nand before getting its CPU_KEY

 

[jsheradin]

RESOLVED!!!
http://team-xecuter.com/forums/show...-JTAG-Install-NAND-Error-NO-BOOT!-PLEASE-HELP
Now I can focus on the Falcon again! Hooray for lost causes!

 

[Antalpromille]

RESOLVED!!!
http://team-xecuter.com/forums/show...-JTAG-Install-NAND-Error-NO-BOOT!-PLEASE-HELP
Now I can focus on the Falcon again! Hooray for lost causes!

why are you posting information about your other thread in this one?

 

[jsheradin]

why are you posting information about your other thread in this one?

I mentioned it because these posts are directly related; this one was held up due to a glitch with the other install. Now that that one has been sorted, the Demon is able to be used to help with this install (given that the computer didn't fry it somehow).

 

[Krafter]

I also just realized that the SB having a cold joint would also explain the 0010 error! Any advice before I break out the skillet?

Use a little garlic salt along with pinch of oregano.

What do you mean by "break out the skillet"? If you indeed have a cold solder joint that needs reflowed then you should send it off to a pro.



Tapatalk misspelled it. Knot me.

 

[mrdrifta]

I mentioned it because these posts are directly related; this one was held up due to a glitch with the other install. Now that that one has been sorted, the Demon is able to be used to help with this install (given that the computer didn't fry it somehow).

So try getting a nand dump from this console. If you fail to get a flash config you may need solder the demon to the console and try flashing via demon. Although you can't be sure your demon isn't faulty, theres not much else to try at this stage before sending it to someone else to fix

The SB errors are likely to be caused by a failed write that has corrupted the smc.

 

[jsheradin]

Use a little garlic salt along with pinch of oregano.

What do you mean by "break out the skillet"? If you indeed have a cold solder joint that needs reflowed then you should send it off to a pro.



Tapatalk misspelled it. Knot me.

I have an Aoyue 968 rework station that I use to reflow/reball consoles. I only have a GPU stencil, otherwise I would reball the South Bridge myself. I have a cheap-o electric frying pan thing that I got at a yard sale for like $5 that I use to hold and pre-heat the boards so the shock of the heat wand won't cause any pulled pads on the processors, etc. I have an Arduino controlled regulator system utilizing an H-Bridge style current regulator combined with an infrared temp gun thing to precisely control the temperature of the pan. The pan itself has several bolts, washers, and nuts affixed in specific places that hold the board about 1cm above the surface. I have plenty of experience reflowing consoles and as I said before, I have only had one that I couldn't fix (TV fell on it). As far as the reball, I have only done four consoles to date and they all went smoothly (had to do the first one twice to get it right). I read that the 0010 code can be remedied by a CPU reball as well, so that is why I wanted to get a pro to do that along with the South Bridge to avoid any chance of error in the future (I can only do the GPU). My setup is basically the same as a professional setup, just a bit more DIY. I figured I could do the same process that I would do to reflow the GPU/CPU only on the SB, and at a little lower temperature considering that there are more caps and things to worry about in that area.

 

[jsheradin]

So try getting a nand dump from this console. If you fail to get a flash config you may need solder the demon to the console and try flashing via demon. Although you can't be sure your demon isn't faulty, theres not much else to try at this stage before sending it to someone else to fix

The SB errors are likely to be caused by a failed write that has corrupted the smc.

My profit margin on this console is shrinking by the second... Who, where, and how much would somebody who has the necessary skills be able to fix it for? If for whatever reason the NAND dump is corrupt on the console and is preventing me from loading onto it, I have plenty of experience swapping SMD chipsets, as I work with dev platforms all the time (and am even working on my own in EAGLE currently). If the 5v mod doesn't yield a successful dump/write, could I maybe swap the NAND chip for that of an equivalent console? I understand that the NAND on it would be completely useless (E79 and such thanks to a bad CPU key, not to mention the DVD key), but if the SMC is good, could that let me at least use the JRP to write the original back to the console (with a stitched SMC if possible) if the Demon were to be dead after all? At this point I am less worried about saving the console, as I really just don't want to keep throwing money at it. Last time the Demon wrote just fine, but the console was still bricked. The again, the Demon also bricked my Jasper (which fixed itself miraculously when the Demon was removed), could that have been at fault at some point along the line on this console?