Print

[garus]

I'm happy for you, but knowing that everything works for you doesn't help me at all...

[garus]

MY mistake, I actually receive 0022 error, NOT 0020.

[garus]

The problem is I don't have JTAG wires soldered to mainboard. I tried without them and error is still the same(flashed original backup to NAND).

And my mainboard is outside the metal case so I can't tighten down the screws. Should I put it back inside?

[ToBbErT]

QUOTE(carlitoB @ Mar 1 2010, 11:52 AM)

it could be a couple of things then if you have not got the 3 hack wires in place. 1st of all i'd try putting case back together with the screws in and the fans and air tunnel, your gpu could be overheating instantly (i think this is the normal reason for 0022 before jtagging came along) and see if that works.

the other thing is if you are using LPT you might not be getting a good write-to-nand. if a console doesnt have the nand hack done to it when you edit anything on the nand it gives rrod. i know you are flashing your original dump back to it but say if a couple of sectors are not being written propery then you would get rrod. i suggest you put the hack wires+diodes on. the jasper is alot easier to do than a falcon, you get a nice little blob of solder on the db1f1 hole on jaspers. i put a big blob of solder on the end of my wire, placed that over db1f1 then quickly pressed both together with soldering iron. also save this connection till last to avoid accidently knocking back off. get a glue gun too and cover all your connections with glue gun glue that turns to hard plastic.

good luck.

0022 aint a overheating problem. So dont put the motherboard back in the case, first eliminate the problem.........

[garus]

Thanks, will try that.

[ToBbErT]

Try what? Your 360 wont boot and its giving a 0022. What that guy is suggesting is all bullshit couse running a 360 without fans or windtunnel wont result in instant overheating. It will take some time to overheat specially with the jaspers (much longer then 30sec). He also suggested to add the jtag wires again wich doesnt make sence to me. Adding the wires wont help anything and soldering again wont do your motherboard any good.

What you should do is :

Flash nand back to stock.
Dump the nand.
Compare original dump with the dump you just made.

This will confirm if the nand has been writen properly but im pretty sure your dealing with a hardware issue here.

[garus]

QUOTE(ToBbErT @ Mar 1 2010, 11:58 AM)

0022 aint a overheating problem. So dont put the motherboard back in the case, first eliminate the problem.........

I didn't see this reply. I flashed first 64MB(is that enough?) from original dump and will read it to compare. I compared smaller parts(2-3mb and they matched).

[garus]

I read that everything after 1000 block(in hex) is MU storage. And ive seen commands like nandpro lpt: -e512 1001 to make partition unformated.
So I erased whole nand and just flashed original stock nand to 1000th block.That should result in the same, right?

[garus]

That's exactly what i did, along with unplugging after flashing.

Thanks for help

[garus]

I erased whole nand and flashed only Xell. I still have a 0022 error after 10 seconds, but now fans go full speed immediately from start.

[vb_encryption_vb]

QUOTE(carlitoB @ Mar 1 2010, 09:19 AM)

if (as you've said previously) you do not have the hack wires in place id recommend flashing your entire originalnand.bin to your nand.

i do not know if this is necessary but thats what i would do next. please correct me if i am wrong people.

id wait for another reply before doing this, it takes 16hours to do this via lpt.

Using the tutorial in my signature, I've dumped and flashed a 512 mb jasper in less then an hour...via LPT.

QUOTE(garus @ Mar 1 2010, 12:08 PM)

I erased whole nand and flashed only Xell. I still have a 0022 error after 10 seconds, but now fans go full speed immediately from start.

That box is just trashed, try and get a box that is jtaggble with no RROD history, it's not the jtag thats the problem it's the RROD that's causing all the problems. xclamp fix is straight garbage anyways.

[garus]

It has no RROD history, it's new. I bought it brand new and flashed it. Worked perfectly until it got corrupted by saving to internal memory unit. So why "thrashed"? How can it be thrashed by corrupting by MU?

[ToBbErT]

post 12*
Does anyone have any idea what might be wrong? I soldered JTAG wires many times, using alternate spots, the returning to default DB1F1, and still the same.

Using the internal MU isnt the cause of the problems. It started the horror fest yes but it wasnt the actual cause. I think you screwed it up with soldering or knocked off a critical part. Anyway i know its to late now but you should have updated xell to xellous so you could have recovered yourself. Post some high res pictures of the solderjoints.......

[garus]

That's the best I can do with my camera: http://showsdb.org/pictures.rar

I know LPT wirings look messy, but readings are perfect. Could they be the reason, even though they seem ok while reading/writing?

[vb_encryption_vb]

I didn't even see where you had your lpt wiring hooked up at. From what I can see is the jtag wires look like they are touching some things they shouldn't be. Also them are all alternate jtag points and I've been doing the standard points from day one now...

Like I said I didn't see any picture of your LPT wiring so I can determine if your reading/writing was wrong.