Apparent Bricked SGS2!

[tone_la]

I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.

First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".

I searched for hours to find a solution, but one solution lead to another problem, and so on...

Currently:

- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.
- Tried Kies and the phone was not recognized in either DL mode or boot loop. Was hopeful Kies could reinstate the firmware.

I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...

 

[dandrumheller]

I've just spent many hours trying to revive my AT&T I777 phone that was running CM9 until I tried to flash it back to bone stock GB, then ICS.

First, I used ODIN to flash the standard default UCKH7 Gingerbread ROM from Sammy via One-Click "I777_UCKH7_OCD_No_BL.7z". After performing the ODIN, the phone flashed successfully and rebooted into a boot loop "Rethink Possible".

I searched for hours to find a solution, but one solution lead to another problem, and so on...

Currently:

- I cannot get into recovery mode, but it boots reliably into download mode. Tried the 3 button tango in EVERY way, but it will only go into DL mode.
- I've tried many different ODIN flashable images per recommendation in this forum, even the one that contains all of the extra files (recommended by creepyncrawly). All flashed fine, but none fixed the boot loop issue.
- Most recommendations say to "wipe/factory reset" to fix the bootloop issue, but I can't do that since I can't get into recovery.
- Tried to do ADB REBOOT RECOVERY, but can't get the driver to connect and list the device. The install guide says to enter "debug mode", but I can't even boot the phone.

I have a physically PERFECT SGS2 I want to sell, and unless I can fix this boot issue, it's nothing but a brick now. Any advice is much appreciated! Pulling my hair out so far...

From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...

Sent from my SGH-I777 using Tapatalk 2

 

[tone_la]

From powered off, how long are you holding power and vol+ and vol- to get into recovery? On both mine and my wife's phones, I have to hold all three down until the second time the Sammy logo flashes up on the screen. Most people seem to get it after the first time, but I've heard of a few others like mine...

Sent from my SGH-I777 using Tapatalk 2

When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.

 

[Pirateghost]

When I hold down the 3 buttons, it never actually shows the Sammy logo. It takes about 8-12 seconds and shows the Download prompt that says "press volume up" to continue to enter DL mode; "press volume down" to cancel/restart. Both of these work fine. If I ignore the prompt and continue holding the 3 buttons, it never does anything else. Thanks for your post.

Unplug the USB when you do that

Sent from my Galaxy Nexus

 

[122ninjas]

Stop using brick. It turns on it is not a brick

Sent from my GS4 running CM11 Kandy Kane

 

[tone_la]

Unplug the USB when you do that

It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...

This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.

Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?

 

[Phalanx7621]

It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...

This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.

Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?

A simple Google search is the best remedy. This is one of the most asked questions on this forum.

 

[dandrumheller]

It does the same thing whether the USB cable is plugged in or not. However, you gave me an idea...

This phone has been sitting in the drawer for a few months since I got my GNex. When I charged it up, after unplugging the charger the icon stayed with a "plug" symbol on the notify bar as if it was still connected to the charger.

Is it possible the phone is stuck thinking there's a cable plugged in and that's why I can't 3-button boot to recovery? Seems like I've read about other people having connector issues. Does this sound plausible? And if so, what's the best remedy?

Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.

Sent from my SGH-I777 using Tapatalk 2

 

[tone_la]

A simple Google search is the best remedy. This is one of the most asked questions on this forum.

I've tried very hard to not "waste" anyone's time by doing my research, searching, and thinking; BEFORE posting. My question above is not so much "how" to clean the port, but "does this symptom I'm experiencing sound like a 'bad port' issue?". Believe me, I've done tons of searching to try to solve this problem before posting so that I can be worthy of receiving assistance.

And to the guy who says, "don't use the term brick". Sorry I said "Apparent brick"; just looking for some neighborly help to get my phone working again. At any rate, I very much appreciate any advice to help me get this fixed.

Trying hard to keep the forum clean and think for myself when possible!

 

[tone_la]

Could be...Sounds like a symptom of bad or dirty usb port. Try cleaning gently with tooth brush and rubbing alcohol. Dry with canned air if you have some.

Sent from my SGH-I777 using Tapatalk 2

Thanks so much for this post, I will do this and post again with the results. Much appreciated!

 

[dandrumheller]

Thanks so much for this post, I will do this and post again with the results. Much appreciated!

I should elaborate a little for safety's sake - probably a no brainer, but in case - TAKE YOUR BATTERY OUT BEFORE CLEANING THE PORT. Don't know if it matters or not, but I wouldn't want you to short stuff during cleaning - rubbing alcohol IS part water.

 

[Red_81]

Adb wait-for-device reboot recovery

Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.

This issues the reboot command if at any point in the boot process your phone is detected.

You might want to install the android sdk and ensure you have the nexus drivers installed.

Sent from my SGH-I777 using xda premium

 

[tone_la]

Adb wait-for-device reboot recovery

Plug in your phone and let it attempt to boot. If you need adb, use the link in my signature for adb portable. It includes batch files to reboot to download or recovery modes.

This issues the reboot command if at any point in the boot process your phone is detected.

You might want to install the android sdk and ensure you have the nexus drivers installed.

Sent from my SGH-I777 using xda premium

Well, I cleaned the heck out of the USB port with rubbing alcohol and a toothbrush, followed by a thorough drying with compressed air. Yes, battery removed during the process; thanks for that! Unfortunately, same exact symptom. Only goes into DL mode and boot loop.

I'll now try your portable adb suggestion and see if I can get a connection.

Does anyone else have any thoughts on what may have gone wrong and/or anything I can flash via ODIN to fix the issue? Many thanks!

 

[tone_la]

Installed your portable adb and followed your instructions. Ran the recovery_mode batch file and adb initialized (daemon not running, starting daemon...) followed by red text "Waiting for your device to be detected". I already installed the Android SDK yesterday and the following modules are installed: Android SDK Tools, Android SDK Platform-tools, and Google USB Driver

Powered on the phone and after a few seconds the "Rethink Possible" logo showed up and shortly thereafter, I heard the computer beep indicating it connected with the phone. Win7 device manager shows "SAMSUNG Mobile USB Modem" under the Modems category.

However, the portable ADB continues to show "Waiting for your device to be detected" and the boot loop continues. Did the same thing in DL mode, same result.

I reinstalled the Samsung I777 driver from Samsung's site. Going to reboot my PC now to see if that makes a difference.

 

[tone_la]

Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.

Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you

 

[dandrumheller]

Reboot did not help. Seems like the phone is not being identified as "Android Composite ADB Interface", and therefore ADB cannot see the phone. I've looked for other drivers, but no matter what I've tried, the SGS2 I777 shows as "SAMSUNG Mobile USB Modem" under the Modems category in Win7 Device Manger.

Any advice on ADB here? Doing the best I can, but keep running into stops. Thank you

Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??

 

[Phalanx7621]

Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml

 

[tone_la]

Try in Linux? Make yourself an ubuntu live CD and go from there? As long as you have the most current drivers, it should work in Win - unless the problem is a totally hosed USB port??

Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.

 

[tone_la]

Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml

I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.

 

[tone_la]

After many many hours of frustration and dead ends, I've finally recovered my phone! YAYYYYY!!!!!

Here's how I got it done...

- No matter what I flashed, I kept getting the boot loop. This was really throwing me for a "loop" when I thought I was flashing standard original Sammy full ROM with ODIN; yet that wasn't enough to recover the phone.

- Something was missing with the boot process, so I started looking for CWM that I could flash via ODIN. Most sites had the zip CWM file, but only a few had the TAR file. Finding a valid file proved more difficult than I thought with all the download sites that went offline for legal reasons. But I did find one!
http://www.mediafire.com/?bjhx33o4viz8tza

The above link is for file name: SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar

- Once I installed the above via ODIN, all of a sudden ADB recognized the phone and I was able to run: ADB REBOOT RECOVERY

It's very possible that the 3-button recovery may have worked too, but when I saw the device show up on ADB, I didn't want to take the chance.

- The device then rebooted and entered RECOVERY mode! FINALLY!!!!

- I then did a factory reset / wipe and rebooted the phone. It came up just fine, NO MORE BOOT LOOP!

Thanks to those who replied to this thread. The responses helped me think hard about what was going wrong and ultimately I dug up a solution.