Stuck on apple logo... tried almost everything to restore... help?

[xxCARLOSxx]

Alright so I jailbroke and unlocked an iphone 3g 8gb to firmware 4.2.1 bb 6.15.00. I put it in my drawer for a few days because it is not my personal phone, I just wanted to sell it. I checked on it before yesterday and it is stuck on the apple logo, it doesn't turn off or anything, just stays on the apple forever. First i tried charging it, then putting it in dfu mde and taking it out of dfu mode, redsn0w restore, pwnage tool restore, ireb with custom firmware, sn0wbreeze restore, and even tinyumbrella with an official firmware... and nothing... I haven't found anything that has been able to fix it. The farthest i have gotten to re-jailbreaking it was with redsn0w but when all the commands are running on the screen it stop when it says "reason: image not found". It doesnt get past that screen

Any suggestions??? thanks

[Orby]

Alright so I jailbroke and unlocked an iphone 3g 8gb to firmware 4.2.1 bb 6.15.00. I put it in my drawer for a few days because it is not my personal phone, I just wanted to sell it. I checked on it before yesterday and it is stuck on the apple logo, it doesn't turn off or anything, just stays on the apple forever. First i tried charging it, then putting it in dfu mde and taking it out of dfu mode, redsn0w restore, pwnage tool restore, ireb with custom firmware, sn0wbreeze restore, and even tinyumbrella with an official firmware... and nothing... I haven't found anything that has been able to fix it. The farthest i have gotten to re-jailbreaking it was with redsn0w but when all the commands are running on the screen it stop when it says "reason: image not found". It doesnt get past that screen

Any suggestions??? thanks

I'd try letting the battery drain fully (or opening the phone up and removing the battery from the board for a minute--strongly discouraged unless you know what you're doing), and then try restoring it to a custom firmware without a baseband upgrade (from Pwned DFU).

[Simon]

So what happens when you try restoring to a custom firmware?

[xxCARLOSxx]

I'd try letting the battery drain fully (or opening the phone up and removing the battery from the board for a minute--strongly discouraged unless you know what you're doing), and then try restoring it to a custom firmware without a baseband upgrade (from Pwned DFU).

It'll take forever to drain it so i'm just gonna swap the whole back housing with a second working 3g that I have for now. What version of redsn0w should I use to put it in dfu mode? and what's best for creating custom firmware 4.2.1, pwnage tool or sn0wbreeze?(what version)

So what happens when you try restoring to a custom firmware?

It gives me an error (error 1600 i think) and i tried it with ireb too since its supposed to bypass the 1600 but nothing... it just gives me another error

[Simon]

Use the latest redsnow 0.9.6rc16 to enter pwned dfu, then try restoring to the custom firmware.

[xxCARLOSxx]

ok so i swapped the motherboards and now the working one is stuck on the apple so it must be the battery... i finished putting together then non working one and its in recovery mode. Im gonna try the custom restore and ill let you guys know!

Edit: It just finished restoring the one that wasn't working!!! Now I just have to change the battery on the working one and i'm set, thanks guys this forum pwns!

[Simon]

Glad to hear it

[xxCARLOSxx]

Glad to hear it

I guess I celebrated victory to early...
When I move the "working" battery and either of the motherboards to the "non working" housing, neither of the boards boot.
When I use the "working" battery and either of the motherboards on the "working" housing, both boards boot.

Now I'm thinking that it wasn't the battery but maybe another component, would a malfunction in the headphone flex, antenna flex, or dock connector flex affect the booting of the board?

Edit: I placed the "Non-working" battery and put it in the "working" housing and it did boot -.- so it wasn't the batteries after all!
I also swapped the dock connectors from the "working" housing to the "non working" housing and it still didnt boot... and the working one did so idk what else it could be!
please help...

Edit #2: Ok I think i found the problem which is really trippy... I swapped the screens and the non-working one boot up! now my question is, is it the lcd or the digitizer?

Edit #3: Well i swapped lcds and the broken one was still broken so that could only mean that the digitizer is broken! I had changed a broken digitizer for this one. I guess it came faulty from ebay... I will change it and report my findings!

Edit #4: So I changed the digitizer to a brand new one and it still didnt work... The last thing that it could be was the proximity sensor... so i changed that and it worked!!! It took me about 3 more hours to solve it but finally got it done... good night lol