Verizon SGS3. This is my first Samsung, so I have no doubt that it was something I did - been running my OG Droid since it came out and I'm not very familiar with the Samsung setup.
I followed this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The forum won't let me post my question there, due to my low post count, so I put it here...
I used Odin to flash the image in the PDA field. Right after that, without checking to see if the phone was working properly, I used ADB to put CWM on there. The phone was turned on (not in Odin mode) when I pushed the recovery. Now I can't get the phone to turn even turn on, much less get into Odin mode to reflash....(yes, I've pulled the battery).
My computer recognizes when I plug my phone in (it give the "you plugged something in" tone), but it doesn't register in Windows explorer.
Any ideas...?
Not sure if this will be any help but..
I was flashing the same rom as you and my computer randomly blue screened in the middle of it and my phone wouldn't boot. I tried just flashing it again with odin right over it, but same problem.
I had to do a factory reset, flash the Samsung stock rom (which unrooted), I think I did another factory reset, and finally re flashed the root 66 rom. I also booted up the phone and did the initial setup before pushing recovery over with adb, but I'm not sure if that makes a difference.
Good Luck!
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
letinsh said:
I can't even get into Odin, though. Nothing happens when I try to power on....so no getting into Odin or Recovery....very frustrating.
Click to expand...
Click to collapse
Was your battery full/plenty of charge when you first flashed through ODIN? What happens when you try to turn it on? No luck with download mode? Are you getting any feedback whatsoever from holding the power button?
Which recovery did you download and flash? I ask because I did this same thing last night and had the same issue. I used the touch recovery (TWRP 2.2.0) from HERE but the direct download link is bad. It gets you the wrong recovery if you download it directly to push via ADB or terminal. You need this one HERE
I hope im wrong but it sounds like a brick. If you can get into download mode your fine.
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
letinsh said:
Battery was 100% (charged it overnight).
Nothing happens when I try to power it on....no lights, no vibration, no noise. Screen doesn't come on, no backlight...nothing.
No feedback whatsoever.
That's interesting. I pulled the battery and plugged in my USB to computer (I'm at work and don't have a regular charger) and the red "charging" LED just came on, but still unresponsive to any button push.
Click to expand...
Click to collapse
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
adb doesn't see the device, even though windows registers something as plugged in (tone thru speakers when plugged/unplugged)
mustbepbs said:
Have you battery pulled already besides just now? If you pull the battery hold the power button after you pull for a few seconds, put it back in and then try to power on.
Click to expand...
Click to collapse
Tried this just now. No joy.
....can a mod please verify my account so I can post more often than every 5 minutes...it's very frustrating.
bump
letinsh said:
bump
Click to expand...
Click to collapse
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
mustbepbs said:
That's really odd that you're getting no life out of it after pushing CWM. What version did you push? When did you push it? You did it via the command prompt or on the actual device?
Click to expand...
Click to collapse
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
letinsh said:
I worked off of this thread:
http://forum.xda-developers.com/showthread.php?t=1756885
and followed it's directions to a "t"
Click to expand...
Click to collapse
Sorry, that's not entirely true. I followed those instructions but used the root66 image from this thread
http://forum.xda-developers.com/showthread.php?t=1762204
The CWM file i used was from the [ROOT] [RECOVERY] SCH-i535 thread
After some searching, this same sort of brick seems to be happening when dudes are flashing roms coded for other carriers....but I've got an i535 and have only used i535 files....hmm.
Shot in the dark
This is really just a shot in the dark, but have you tried power,home and volume button?
-SmithTech- said:
This is really just a shot in the dark, but have you tried power,home and volume button?
Click to expand...
Click to collapse
Yes, both vol up and vol down. I've tried every iteration I can think of. I'm waiting to hear back from Josh @ MobileTechVideos to get me an address. I'll be driving out there to have him give it a crack at unbricking...
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
nosympathy said:
i am not sure about fixing it, but a good rule of thumb is verify your MD5 on your files always!
I downloaded the same root66 because it was a torrent verifed md5 before I even attempted flashing it.
Click to expand...
Click to collapse
+1. Always make sure to verify MD5's before flashing anything, especially in our case. Hopefully you can get that fixed, OP. That's really bizarre.
Possible Fix
Curious.... when you you type ./adb devices does it list any devices there? (Windows its just adb device)
I have seen this happen on Samsung Vibrants and it sounds like your device has forgotten what the hardware keys actually do. If adb works, you can reboot to download it it doesn't a resistor can be built with a Micro usb end to trick the device into download mode. Some were made for the Vibrants and should be able to find them on the forums over there. I believe Team Whiskey built them
Related
In anticipation of flashing Eugene's MacNut with GPS working, I managed to somehow got to the point where the phone will now not even boot up. I did a factory reset, "Linda" said "complete", then when I rebooted it did so but then shut off. I was able to get to Odin via reboot download, I flashed back to stock, but when it rebooted it shut off again. Now I cannot get the phone to boot up, either normally or in to recovery. Anyone ever have this experience, and is there any way out? TIA.
New issue...
Good to see that nobody else had this problem. Fortunately I found out how to get into download mode. I may have successfully (maybe?) reflashed stock through Odin. However, when I reboot the screen goes black and the phone turns off. I've spent hours trying to find the exact type of potential issue I have, and none of them get me past where I'm at now. The most promising I found was this one
http://forum.xda-developers.com/showthread.php?t=811820
but I am not exactly sure of the sequence: constant "adb push update.zip /sdcard" that I should be doing. Like, how many times do I do this? When I push the power button while in recovery it (obviously) just reboots, which is what it is supposed to do. Am I trying the wrong thing/ in th wrong thread? TIA.
This worked for me, but it re-partitions, so you'll lose your data.
http://forum.xda-developers.com/showthread.php?t=803492
I was also trying to find the instructions where you odin "froyo that doesn't brick" and then odin the original, but I don't see it now.
if you need to get into download mode, use Eugene's method:
pull battery and leave it out
plug in the usb to the phone and the computer
hold volume +/- key
insert battery while holding the volume key
burgon said:
This worked for me, but it re-partitions, so you'll lose your data.
http://forum.xda-developers.com/showthread.php?t=803492
I was also trying to find the instructions where you odin "froyo that doesn't brick" and then odin the original, but I don't see it now.
if you need to get into download mode, use Eugene's method:
pull battery and leave it out
plug in the usb to the phone and the computer
hold volume +/- key
insert battery while holding the volume key
Click to expand...
Click to collapse
Hey, thanks for the reply. I am able to get in to download. I'm uploading the file now, it's a big one. We'll see when it's done. Thanks again.
wbexpress said:
Hey, thanks for the reply. I am able to get in to download. I'm uploading the file now, it's a big one. We'll see when it's done. Thanks again.
Click to expand...
Click to collapse
Oh well, so much for the theoretical impossibility of bricking a Vibrant. I did the whole YouNeek fix, no go. It still does the same thing as it has since I screwed it up, it turns on, reboots and then goes black. Oh well, I think I've about had it with Samsung. The screen is awesome, but the OS is just not user friendly. The irony is that when I bricked this thing I took the SIM out and threw it back into my G1, which I have NEVER had an issue with. HTC...
I had the same issue you had, boots, screen goes black but buttons still light up. I posted the fix in a few different threads, one of which I started myself. If you search for threads I've started your fix will be there. You have to flash eugene's "froyo that will not brick" through odin and then flash the stock rom again through odin. Check my thread for a link to the exact instructions. I fix my phone in about 5 minutes once the roms were downloaded and happily shipped my replacement back so I won't have to pay the $20 in shipping
OK, here the story. My SGS2 started acting up a few days ago, it thinks it's charging all the time now. I searched and found that this seems to be a common problem with the port, so I cleaned the contacts on the microUSB connector, but it's not helping. I decided today that I'll just take it in since it's still under warranty, and I'd like to do it after work today since I live almost an hour away from the AT&T Store near the hospital. Problem was, I'm running AOKP on it and I don't have access to a computer with Odin on it where I can restore it to stock. Then I find the thread that details how I can download the .tar file and flash on the phone with Mobile Odin. Seems to work great, but it goes into a bootloop afterwards. One member posted that he had the same problem, but it was solved by booting into recovery and doing a full wipe. Here's where I have a problem now.
I can only boot into Odin mode, and it gives me the choice where it's asking me if I'm sure I want to load a custom binary or cancel and reboot. When I click that I want to load the binary, I get to the Odin mode screen; it reads
Custom Binary Download: No
Current Binary: Samsung Official
Downloading...
Do not turn off target!!
That's it. If I reboot normal, it goes into bootloop. Otherwise, it sits there with the battery logo showing, whether it's plugged in or not.
I'm pretty sure when I get home tonight, I can plug it in and get something going on my desktop, but I'd like to hit up the store before I head home. Anyone got any ideas or suggestions?
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
Yup, and that's what comes up. I'm thinking it has something to do with the fact that the phone thinks it's plugged in. I guess I'll just have to plug it in my desktop when I get home and work on it from there. Worst case scenario is that I just take it to AT&T tomorrow as it is, tell them about the false charging problem, and when I tried to do factory reset to see if it would fix things, this is where it's stuck.
I can't believe I spent the first 30 years of my life without a cell phone and now I don't feel right if it won't work for a day or two.
creepyncrawly said:
If you can't boot into recovery using the three button method, I'm not aware of any way to put it into recovery mode without a computer. You didn't say, but I assume you used vol+, vol-, & pwr?
Click to expand...
Click to collapse
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
drjim said:
I'm having the same problem after trying to install S-Voice. You indicate that there is a way to get into recover using a computer. Can you explain?
Thanks.
Click to expand...
Click to collapse
need adb.
adb reboot recovery
Google
Update:
I actually managed to catch it when it didn't think it was plugged in and do full wipe. It worked after that, sorta. It didn't think it was plugged in all the time, but it was still real funky; like the power usage curve started high, had a sudden big drop, then went up from there. Plus, when it was off, it would flash between a grey battery with a circle and a green on, back and forth. And I couldn't power it on unless it was plugged in. Once I showed them that, AT&T gave me a new SGS2. It's rocking Shostock2 now, so problem solved.
My samsung vibrant running 4.0.4 ICS zenwich 1.8.4 randomly shut off today, not even able to turn on, it was the Sleep of Death I have got before, so i pulled battery and reboot, still nothing.
The phone now boots, but their is no display
The phone will literally turn on, have the 4 buttons light up on the bottom, have the screen be responsive to touches, but the physical display is off
I can unlock my phone by swiping, hear the volume up sound, even dial calls by blind touching. It is the same idea as a PC that is plugged in, just so VGA cable to the monitor.
I have tried rebooting to recovery, download mode and tried to heimdall, but it never finds my device, i tried to sdk in and reboot to download mode via cmd prompt but no luck finding device too
I am all out of ideas and nothing is seems to be working
Any advice on resolving this issue would be appreciated
wafflebroski said:
My samsung vibrant running 4.0.4 ICS zenwich 1.8.4 randomly shut off today, not even able to turn on, it was the Sleep of Death I have got before, so i pulled battery and reboot, still nothing.
The phone now boots, but their is no display
The phone will literally turn on, have the 4 buttons light up on the bottom, have the screen be responsive to touches, but the physical display is off
I can unlock my phone by swiping, hear the volume up sound, even dial calls by blind touching. It is the same idea as a PC that is plugged in, just so VGA cable to the monitor.
I have tried rebooting to recovery, download mode and tried to heimdall, but it never finds my device, i tried to sdk in and reboot to download mode via cmd prompt but no luck finding device too
I am all out of ideas and nothing is seems to be working
Any advice on resolving this issue would be appreciated
Click to expand...
Click to collapse
Device Manager show anything is plugged in?
FaultException said:
Device Manager show anything is plugged in?
Click to expand...
Click to collapse
Yes, It shows up as the linusb winusb t-959 but neither heimdall or android sdk find the device.
wafflebroski said:
Yes, It shows up as the linusb winusb t-959 but neither heimdall or android sdk find the device.
Click to expand...
Click to collapse
So were you able to get into Download Mode at all? And if so was the display on then?
FaultException said:
So were you able to get into Download Mode at all? And if so was the display on then?
Click to expand...
Click to collapse
i think it did because it wasnt at a lock screen, and when i touched the soft buttons they would light up, but the phone wasnt in an OS.
the screen was still off though, I can't get anything to make it turn on
wafflebroski said:
i think it did because it wasnt at a lock screen, and when i touched the soft buttons they would light up, but the phone wasnt in an OS.
the screen was still off though, I can't get anything to make it turn on
Click to expand...
Click to collapse
What method did you use to get into Download Mode?
FaultException said:
What method did you use to get into Download Mode?
Click to expand...
Click to collapse
take battery out, hold vol + and - and power button, put battery in while usb connected
wafflebroski said:
take battery out, hold vol + and - and power button, put battery in while usb connected
Click to expand...
Click to collapse
You may've gotten into recovery, I can't really get into download mode like that. Try this:
Unplug USB & remove battery
Insert battery but do not power on.
Hold VOL-UP + VOL-DOWN
Insert USB and wait a few seconds, while still holding them
FaultException said:
You may've gotten into recovery, I can't really get into download mode like that. Try this:
Unplug USB & remove battery
Insert battery but do not power on.
Hold VOL-UP + VOL-DOWN
Insert USB and wait a few seconds, while still holding them
Click to expand...
Click to collapse
Ok that works, I'm defineatly in download mode, the device shows up in ODIN, but not heimdall. I am not familiar with ODIN, how would I go about flashing the ICS zen rom? I found a tutorial to flash back to stock ROM and wipe all data, but I would like to be able to just reflash the ICS rom
wafflebroski said:
Ok that works, I'm defineatly in download mode, the device shows up in ODIN, but not heimdall. I am not familiar with ODIN, how would I go about flashing the ICS zen rom? I found a tutorial to flash back to stock ROM and wipe all data, but I would like to be able to just reflash the ICS rom
Click to expand...
Click to collapse
Ok, so it shows the download mode on the screen of the phone?
If so, that's good news and means your screen is not shot.
Try to get Heimdall to work. Are you in windows? Then you'll need to uninstall the samsung drivers and do this (from CM update guide):
CM update guide said:
1. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
2. From the menu, choose Options ยป List All Devices.
3. From the drop down, select Samsung USB Composite Device or Gadget Serial.
4. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
5. Heimdall can now be used safely on the Windows computer.
Click to expand...
Click to collapse
Once heimdall is running, try grabbing the boot.img out of the zen zip and do this:
Code:
heimdall flash --kernel boot.img
See if anything comes of that.
The screen never turned on.. it just went into download mode and i was able to see from ODIN that it was recognized. So i ODIN'd back to stock rom, i heard the phone reboot, but still no display.
Like before the phone's screen is 100% responsive, i can unlock the phone, hear the usb plugging in noise, just no display. It just blows my mind because the screen works but its not on.. I am very confused
wafflebroski said:
The screen never turned on.. it just went into download mode and i was able to see from ODIN that it was recognized. So i ODIN'd back to stock rom, i heard the phone reboot, but still no display.
Like before the phone's screen is 100% responsive, i can unlock the phone, hear the usb plugging in noise, just no display. It just blows my mind because the screen works but its not on.. I am very confused
Click to expand...
Click to collapse
That's not good. Your phone might be done for then. I once repartitioned with no partition files and still download mode worked on a fresh battery pull.
Maybe try leaving the battery out for a while and see if it fixes itself, since it seems to be an electronics problem, maybe something needs time to reset or something.
Sent from my SGH-T959 using xda premium
Yea I've had the battery out for over 30 mins and nothing. I even opened up my phone last night to check all the ribbon wires and connections, everything looked fine and i removed the motherboard & replugged everything in.. still no luck
it's a good thing my contract is up I think I am going to get the samsung galaxy s 3..
RIP vibrant best phone i ever had, I'm surprised it lasted this long with all the mods I had done to it haha
my xt890 lcd screen and digitizer were broken so i changed them and the phone was working fine for a week, i then wanted to update to kitkat through oem update; everytime i tried it would give me error . i then read that since i unlocked bootloader and rooted my phone and installed cwm recovery i couldnt do an oem update and i had to do a factory reset in order to update through oem, so i did just that ; after the phone finished factory reset and booted i proceeded with oem update while the phone was charging, everything was going fine the file was downloading, i went to the bathroom and came back the display was black, but touch screen was working fine...through more searching i read that this could be from the update, and i should do another reset... since i couldnt see anything even recovery menu. i downloaded moborobo so i can see my screen on pc and proceeded to factory reset ... now i cant even see through moborobo and im stuck. i think im stuck in recovery screen, but no way to be sure , hence i cant get usb debug.Please help.
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...
tone_la said:
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...
Click to expand...
Click to collapse
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
dandrumheller said:
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
Click to expand...
Click to collapse
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.
tone_la said:
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.
Click to expand...
Click to collapse
Unplug the USB when you do that
Sent from my Galaxy Nexus
Stop using brick. It turns on it is not a brick
Sent from my GS4 running CM11 Kandy Kane
Pirateghost said:
Unplug the USB when you do that
Click to expand...
Click to collapse
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?
tone_la said:
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?
Click to expand...
Click to collapse
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
tone_la said:
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?
Click to expand...
Click to collapse
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
Phalanx7621 said:
A simple Google search is the best remedy. This is one of the most asked questions on this forum.
Click to expand...
Click to collapse
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!
dandrumheller said:
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
Click to expand...
Click to collapse
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
tone_la said:
Thanks so much for this post, I will do this and post again with the results. Much appreciated!
Click to expand...
Click to collapse
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.
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
Red_81 said:
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
Click to expand...
Click to collapse
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!
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.
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
tone_la said:
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
Click to expand...
Click to collapse
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??
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
dandrumheller said:
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??
Click to expand...
Click to collapse
Why would it work better in Linux? I'm willing to try this, but fairly unfamiliar with Linux.
Phalanx7621 said:
Tried these? http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-II-i777-USB-Driver-for-AT-T.shtml
Click to expand...
Click to collapse
I used the Samsung drivers. Kinda leary of these drivers from softpedia. They download as SETUP.EXE and seem like inauthentic/spyware.
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.
So yesterday morning I went to turn on my phone, but nothing happened. It was on the charger all night so it should have been a full battery.
Here are my symptoms:
1) AC plugged in without battery - Phone's screen turns on for a second, turns off, and then repeats.
2) AC plugged in with battery - Phone will start to charge (has the loading symbol in the battery), but then turns off immediately. It cannot boot into recovery. It CAN boot into download mode, but my computer will not recognize it to restore the phone with odin.
Any ideas?
I don't have an official upgrade until October, but I'm going to call customer service to try and get them to bump the date up so I can get a new phone.
First possibility to suspect is a failed battery. If you know someone else with an s2, ask to borrow their battery temporarily to see if your phone will boot. Or perhaps go to an AT&T store to see if you can borrow a battery.
If it's not the battery, then the next step to try is to boot into download mode with the battery out of the phone to see if Odin will recognize the phone with the battery out. With the battery out of the phone and the USB cable plugged into the computer, hold down the vol down button while plugging the USB cable into the phone. The computer will supply the power. This assumes that you have the proper "Samsung USB driver for mobile phones" installed on your PC.
That's a start.
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
sfb14 said:
I am having the same issue with my s2. i had shostock installed on it a few weeks back and it was working fine. then it just stopped working. i tried rebooting but it keeps on going on bootloops. I tried using odin to flash back to stock but no go, just bootloops. kies just dont work for me. i know it isnt the battery cuz i have the charging cradle to charge the battery and the phone goes to odin mode without the battery. Any help is appreciated.
Click to expand...
Click to collapse
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
creepyncrawly said:
It sounds like you got a successful flash of stock. Boot into recovery and perform a wipe data/factory reset.
Click to expand...
Click to collapse
I just did. Still no boot.
sfb14 said:
I just did. Still no boot.
Click to expand...
Click to collapse
OK. Did the flash to stock succeed? In other words, you got a pass in odin?
Which version of SHOstock was installed, the latest? And which version of stock did you flash?
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
sfb14 said:
i flashed SHOstock v3 before all of this happened. i flashed ucle5 stock rooted. battery icon flashes capacitive keys blink over and over again. if i unplug it nothing happens. i may have to try UCKH7 once im done downloading it.
** after flashing KH7, i go to recovery to wipe/factory reset... there is a message saying
Installing Multi-CSC...
"can't access to '/system/csc/ATT/system/'
Successfully applied multi-CSC
Click to expand...
Click to collapse
This is sounding a bit like nand read/write corruption, which is fixable. Try this:
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 and boots normally 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.
Will try that later. Thanks for your help!
Sent from my SAMSUNG-SGH-I337 using xda premium
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
sfb14 said:
still no luck.. i did everything odin says "PASS" but it just wont boot. i'm going to try and get a different battery and see if that works.
thanks for your help sir. :good:
Click to expand...
Click to collapse
Going through the exact same issue with my kids phone with the same results. Tried creepy's 6 steps, but still no luck.
I think it was caused by my kid killing the battery.
update: got it to boot into custom recovery, then reflashed ROM. It stills acts weird though. Very laggy.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-at-t-usb-port-repair/
Sent from my SGH-I777 using xda app-developers app
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
jvick920 said:
Having a very similar issue here.. Battery icon flashes then black screen. Boot to download mode.. Push up arrow, black screen. Computer does not register device connected.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
creepyncrawly said:
It's hard to give any suggestions with this little information. More information would be useful. A lot more information would be more helpful.
Click to expand...
Click to collapse
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
jvick920 said:
When I plug then phone in (automatically turns on when plugged in, power button is broken), the battery logo and hardware buttons flash erratically for up to a minute then nothing at all. I've tried different batteries and different cords. The only thing that seems to bring it back to life is letting the phone and battery sit unplugged for 2 weeks up to a month and trying again, but it's very hit or miss. This only seems to happen when the battery completely drains.
Click to expand...
Click to collapse
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
creepyncrawly said:
What phone do you have... the AT&T SGH-I777 does not have hardware buttons, but maybe you mean the capacitive buttons which are part of the display? Your previous post was sent from an Infuse? If it's not an I777 then you need a different forum.
If the phone that has the problem is an SGH-I777, then... what firmware is/was it running? Is it rooted? Is USB debugging turned on? Have you been able to boot into download mode since your first post? How long was the power button broken before this problem first manifested?
I think you need to get into download mode and flash stock firmware.
You also may need to see if you can do something about the broken power button, since that may be involved in the problem. That would mean either taking the phone apart and trying to mechanically clean the button or move/press/activate it a lot to get the dirt out so that the problem clears itself, or it may mean getting it replaced.
Click to expand...
Click to collapse
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
jvick920 said:
It is the I777, capacitive buttons is what I meant.. I apologize, I'm still fairly new with terminology.. Yes, I have an Infuse also, it's my backup phone because I can't get the s2 to charge. It is rooted and flashed, running 4.2.2 (Avatar ROM)
The problem is, it isn't holding enough of a charge to do anything. Aside from the previously stated issue, it will go into download mode, but the screen will only stay on for maybe 5 seconds max. The power button has been broken about 6 months before this issue arose. This only started happening about a month ago when I let the battery discharge completely. To test my theory that it's a battery/charging issue, I got a backup battery (which allowed the phone to work again) and I allowed that one to discharge completely. Now I'm having the same issue with both batteries. I was able to get the phone to power on once after letting the phone and battery sit disconnected for about 2 weeks.
Click to expand...
Click to collapse
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
creepyncrawly said:
What firmware is/was it running?
Is it rooted?
Is USB debugging turned on?
Did it charge the second battery fully more than once?
How long did it operate with the second battery?
Click to expand...
Click to collapse
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
jvick920 said:
Firmware is CM 10.1, it is rooted, running AvatarROM. USB debugging and mock locations were turned on. It had no issue charging while it was working, it was after I allowed the batteries to die that I started having issues. Even on the second battery, it would continue operating as long as I kept it charged.
Click to expand...
Click to collapse
I have never used Cyanogen Mod or any of the other AOSP firmware, and I don't know how the firmware would affect this issue, if at all. But I suspect there may be some link.
I think what you need to do is to flash back to stock firmware, or perhaps use one of the stock plus root packages, and then a custom kernel, and then reload CM 10.1. So try this:
Pull the battery and leave it out. Open Odin3 on the desktop and then while holding down the volume buttons, plug in the usb cable. See if the phone will boot into download mode this way, and if Odin will recognize it. If so, then go ahead and flash the stock of your choosing. I think if it were me, I would flash 4.0.4 UCLL6 plus root.