Wont boot, probably softbricked

mcj108

Member
Oct 2, 2010
36
1
0
Fresno, CA
I had a S2 i777, then I got a S3 so I gave the S2 to my mother. I just installed fresh ShoStock because I thought that would work well. It worked ok, but after about a month I came home and she said it wasnt working.

It appeared to be bootlooping at the ShoStock logo. I downloaded a new rom for it on my phone the put the SD card in her phone, booted into clockwork and tried flashing it. Trying to wipe or flash at all results in hanging for a few minutes then rebooting and getting stuck at the Samsung S2 logo now. Since then I've tried various odin methods for flashing to unbrick around xda. Every time I try to flash with odin, it either says error or it just hangs until I manually stop it after 30+ minutes. I've even got as desperate as to have Kies revert it to stock, it also hangs at 2%.

At this moment, you can see the screen its stuck it in the attached screenshot, its probably worth noting its been at this screen ever since the first Odin flash failed.

I do have a microUSB jig so I can kick it into download mode if I have to. Anyone got any ideas :f
 

Attachments

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
Try the following procedure exactly as written. In case the problem is nand read/write corruption, this should clear it and get the phone working again.

1) Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA without ticking Re-Partitioning.

2) Successful? Nice. Next, flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.

3) If that is successful you are done. If it is not, then:

4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.

5) Flash the Kernel, as in step 1.

6) Flash the full stock Gingerbread distribution, as in step 2.
 

mcj108

Member
Oct 2, 2010
36
1
0
Fresno, CA
When I try and flash Siyah in Odin for step 1, it just hangs.

<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> NAND Write Start!!
The box at the top says kernel and the progress bar goes all the way across, it will never get past this.
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
Since it won't flash the kernel, the next thing to suspect and try to find out if the cable is faulty. Or anything in the path from the computer to the phone. So...

Try a different cable, or as many different cables as you can put your hands on.

Try different ports on the computer, and use the ones attached directly to the motherboard if it is a desktop.

Try a different computer.

In some cases where there is a connection problem, just flashing repeatedly may eventually result in a pass, as some have reported.
 

mcj108

Member
Oct 2, 2010
36
1
0
Fresno, CA
Tried it on two different laptops, with three different microUSB cables on each, no dice.

I tried flashing the kernel from step one you gave, I also tried the I777UCKH7-CL503881 FULL Odin3 One-click from the Download Repository and it hangs at:

<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> sbl.bin
<ID:0/003> param.lfs
<ID:0/003> cache.img
 

creepyncrawly

Senior Member
Sep 3, 2010
2,770
3,276
0
I don't have any additional suggestions for trying to fix it yourself. The problem could be one of several things. It doesn't seem like a simple soft brick. Maybe it could be damaged memory or some other hardware failure. Or maybe not.

If you are close to an AT&T service center, maybe you could take it by and ask them to flash it back to stock for you. If that fails, then at least you are pretty sure the problem is in the phone, not the connection. I realize it is not under warranty any longer, but they should at least try that for you.

You could send it to Samsung repair center to be worked on. They would probably fix it, but it won't be free, and it will also take two to three weeks. If it were me, I would call them first and discuss the issue with them.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone