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.
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
Sometimes my I5500 won't turn on.
This has already happened 2 times (with two different firmwares I5500XWJPL and I5503TTLPJP9). The phone shows absolutely no signs of life - screen is black, no sounds, nothing.
I tried everything: pressing VolumeDown+Center+Power, VolumeDown+Home+Power, with or without battery/SIM/charger/SD. Tried removing battery for 30 minutes, charging battery in external charger.
Sometimes when charger is connected, it shows green battery on the screen, but still won't boot.
Last times I spent several hours fiddling with it until it finally turned on..
Can someone tell my if there is a fast way to revive the phone next time this happens?
Maybe your arm11boot is damaged, but still partly working. You need replace that partition. I saw arm11boot partition image in one Russian FW. I can't remember actual name. You can try that, but caution. You might brick your phone compleatly!
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Rigardi said:
sorry for reviving this thread.
but I got the same problem now. Tried to use ROM Manager to install CWM Recovery (following a blogpost explaining how to install a Custom ROM on the SG5). Might have accidentally clicked a different CWM Rec. version than I thought I did. However, ROM manager showed a message, telling me that CWMR was installed correctly.
So I wanted to boot into CWMR up to flash my device with the latest CyanogenMod 7 port from MADTeam. Used the "boot into recovery" option from ROM manager for that purpose. The next thing I know is my phone not reacting to anything.
Tried all methods mentioned afore (Vol- + Home + Power / Vol- + Center + Power, with/w.o. SD card and/or battery inserted). Screen keeps being off, no sign of life, phone wont even do anything when plugged to my PC or a charger.
The phone has been rooted properly before and was running Stock 2.1. Houston, we've got a problem.
Click to expand...
Click to collapse
Take your battery out, put it back in and turn your phone on, then it will boot up into recovery mode. I also have this problem from time to time, sometimes it boots into recovery, sometimes not and i have to remove/replace the battery.
I actually thought that this might be a useful feature for say - if you wanted to upgrade a friends phone to cyanogenmod in the pub, for example.
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Rigardi said:
did try that. now even had the battery removed for about an hour. put it back in. still no reaction on pressing the power button or one of the combinations that should put it into recovery or download mode. no sign of life when plugging the phone to my computer or the charger.
I do fear the worst, though I dont know how ROM manager was actually able to brick the phone that badly.
Click to expand...
Click to collapse
In that case then this also happened to me - While exploring the rom manager application after first ever flashing my phone i accidentally selected the wrong phone model from the 'flash clockworkmod recovery' option and my phone was gone forever. Perhaps your problem is similar.
(Luckily it was under warranty and they replaced it. The method worked so well in fact it happened 'accidentally' a second time i acquired a 3rd i5500 out of the box )
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Rigardi said:
bought mine already used, so no chance for a warranty replacement :/
gonna give it a shot with a usb jig now, maybe i can get the thing into d/l mode with that, so I can revive it with odin.
Click to expand...
Click to collapse
what about the Emergency DLoad Mode, which is not the Download Mode? Did you try it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
how do I access emergency d/l mode?
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
ops, sorry: I miss your previous message!!
Now I got it and read this last post.. let some time to think about it, I'll replay soon.. but, generally speaking, at this point there's not so much you can do..
If you can get it into Download or Recovery mode, then you should be fine.
Sent from my GT-I5500 using XDA App
Rigardi said:
UPDATE
I actually CAN get download mode (or what I assume it to be) running by pressing Vol- + Menu + Power (while Vol- + Home + Power wont do anything, nor does the USB jig that arrived today). Took me some time to discover this, as this doesnt seem to be the usual 3-button-combination used. BUT: while the phone is now recognized by my PC, it wont show anything on the screen.
Odin (tried 4.28 and 4.43 on both win7 x64 and x32 and everyting related to Kies shut down) does now detect my phone. However, it always gets stuck at "Setup Connection" when I try to flash the stock rom or CWMR. Tried different approaches (from starting DL-mode with the phone being connected to my PC to separately starting DL mode and then connecting, starting it up with the battery already being in place, starting it up with sliding the battery in place while holding the 3 buttons etc.), none of them gets me further so far.
Another hint I found was setting the Baud-rate of the Samsung mobile modem to 203400, but this, unfortunately, didnt change anything.
Anyone got a lead on how to get Odin finally started properly?
Click to expand...
Click to collapse
download mode is Vol - / Central Button / Power..
Im aware of that. However, Vol- + Menu + Power is the only key combination that the phone will react upon.
Anyway. Brought it to a mobile phone shop on friday, called them on monday and according to them, the phone should be fixed by tomorrow, wednesday. Seems like ROM manager has done damage that cant be undone without knowing how to handle a JTAG device. But at least its not completely broken. Learning that will cost me 25 Euros, though.
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Rigardi said:
One final update to this: Got the phone back today, they were indeed able to fix it.
Conclusion:
While installing a non-fitting CWM-Recovery through ROM Manager will make your Galaxy 5 unfixable via Odin, it still can be saved by making proper use of a JTAG.
Click to expand...
Click to collapse
... for only 25 €!!!
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
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
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.
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.