So I just picked up this s3, it will turn on but shuts off halfway through galaxy splash screen. Boots into recovery and Odin mode just fine, prior to purchasing we plugged it in, got it to boot and did a factory reset, to clear privious owners data, and it went fine, did it reboot and took me to setup. Satisfied with its performance I went ahead and made the purchase, upon unplugging it shut off, as I expected if battery was indeed shot. What gets me is I let it charge, unplugged, booted, shut off at splash screen, plug back in and says its still fully charged. Boot into recovery and indeed, 100% battery. I haven't gotten around to flashing twrp or rooting, was wondering if anyone has experienced this?
Sent from my HTC Desire HD using XDA Free mobile app
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Phone was already on 4.4 when I got it, I downloaded and flashed stock firmware (ne1) via odin, I got the whole way to the end of setup and as soon as it started loading the homescreen it cut off and went to the green battery charge icon when phones off. Everytime I try and boot it, she'll go through all the splash screens and ill catch a very short glimpse of the homescreen and it shuts off. Also it HAS to be plugged in still, or else it just shuts off halfway through initial "galaxy s3" splash.. I don't understand...
Have you tried a new battery? Even if it's plugged in it won't run if the battery is completely shot.
Also if you indeed have a Verizon S3 on NE1 firmware you will not be able to install TWRP as the bootloader is locked. You will be able to root, however.
Muhff said:
Anyone got any ideas? Just got home, am able to boot past the splash screens as long as its plugged in but once I try to start using it (going through setup/tutorial) it ends up rebooting, computer can read phone in odin/recovery modes but don't see a point reflashing stock firmware if this phone was never touched, completely stock unrooted, just a factory reset upon purchasing. I've read somewhere about a stuck power button, is that common among the Verizon s3? If so ill pop it open and check it out.
Click to expand...
Click to collapse
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
XdrummerXboy said:
The stuck power button seems to affect users IN recovery mode too, it seems like phone randomly reboots in recovery.
You can pick up a new battery from amazon for like $7 I think, its been a while, but might be worth it.
It could also maybe be some issue in transferring charge from the battery to the main board, meaning maybe bad connections/contacts.
Is it plugged in when it reboots, because that may indicate poor contacts, since the charger alone isn't able to power the device (ex I used to be able to take out my LG Ally battery when plugged in and it functioned fine).
Good luck!
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Muhff said:
Turns out it was the battery all along, found a battery that the contacts matched on (even though it was only 1650 mAh) wedged it in with paper and it booted just fine. Found a battery on craigslist that night and has worked great ever since, unfortunately PO had already updated to 4.4.2 so im stuck with that Thanks for the response, I just found it odd that the battery held a charge just didn't work.. maybe I should check the contacts on that and clean them.
Click to expand...
Click to collapse
I'm glad you fixed the problem!
Sent from my SCH-I535 using XDA Free mobile app
Related
Need a little help here. The other day I turned on our old D2 BC I need aa replacement phone and its given me hell. First boot it went into the Liberty boot animation and wouldn't stop looping. My girl rebooted into recovery and flashed Liberty again and apparently it was working fine which I did not know. When she did this she didn't tell me so I was under the impression I needed to do what she did. I went to recovery, wiped and flashed Liberty, I believe its 2.0. Now I can't get it to even go into recovery. The only thing that happens is sometimes when I plug it in to a power source it will go straight to a liberty screen and just sit there. Not even an animation. Any ideas? I'm fixing my Ubuntu right now so maybe I can access ADB commands from there. It won't detect on Windows.
Sent from my Nexus S 4G using xda premium
update: I finally got this phone to do something and idk how? I have tried to let it charge for a few days now and I'm thinking that 'somehow'(???) the battery got f'd up because just now when I plugged it in to finally try to connect through ADB, a black screen popped up. at top it Read: Bootloader > next line > D2.37 then at the bottom two lines that read Battery Low, Unable to Program. ....any thoughts? other than a new battery?
you need to get the battery charged with another phone or an external charger (stay away from homemade chargers as they can mess up stuff). What happened is the battery got too low to either start or finish sbf'ing so it went to bootloader and the phone won't charge without software so until you charge or buy a charged battery you are stuck. It's very fixable but you are stuck.
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
fire_fist_ace said:
Hi guys,
I just recently flashed my phone to the Romulus rom, and its been going great. There have been a few hiccups but nothing too big, except for 2 things:
1. Whenever the phone is plugged in, the lockscreen becomes unresponsive. When i try putting in my unlock pattern, it only allows about 2 dots max before it thinks i have lifted my finger of the screen. To fully enter the pattern i have to unplug it, enter the pattern then reconnect the charger. Anyone else had this, or know of a fix?
2. This is the major one. For some reason, when my phone turns off due to low battery, the phone just wont come on, no matter how much i charge it. It gets stuck in a bootloop at the moto logo. Its happened twice now, the first time i somehow got it working by using the charger to turn it on, then unplugging and pressing the power button immediately at the logo. However yesterday this isnt working. When i do that, at times it boots up, but then when it gets to the lock screen it tells me to connect the charger, then shuts down again. The battery icon is red with an X accros the symbol. Does this mean that its not detecting the battery? How would i fix this?
Cheers for your help
Click to expand...
Click to collapse
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
---------- Post added at 11:47 PM ---------- Previous post was at 11:38 PM ----------
Chichoman said:
I've experienced the screen lag as well.. I think it only comes out when u are charging...usually i just d/c the carger then unlock the device and then plug it again..Something is still lagged...I relly don't know why this happens, but one friend has a Vibrant..and have this problem as well..So we aren't the only one whit this problem.
Click to expand...
Click to collapse
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Chichoman said:
<snip>
Edit: Also i'm on SCV7 so it's nothing to do with the rom.
For your second Q...Try to clear battery stats on CWM?? Sometimes when u flash a new rom u need to clear those stats...So give it a shot and let us know what happened.
Click to expand...
Click to collapse
This won't do anything for the OP's inability to boot. That's why I said that likely his best bet is to see if he can boot into AP Fastboot, so that he may be able to FXZ back to stock...
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Apex_Strider said:
First off mate, all questions go in our Q&A Section, so just keep that in mind going forward.
Now, your 1st question regarding the touch screen's responsiveness while trying to unlock with password, I've experienced this myself, and while charging. Though I'm not really sure what causes this, to be truthful. I've found though, that sometimes locking and unlocking will get things to cooperate. I doubt it there's anything to cause concern with any hardware (digitizer) since you don't mention this as being an issue outside the unlocking of the device while charging. Mine was sporadic, and I eventually grew tiresome of the pattern unlock, and did away with it altogether. Perhaps someone else could chime in here with a better explanation as to why this happens. (?)
Now, to your more 'serious' issue. Seeing as how you have Clockworkmod Recovery (CWM) installed, you never want to allow your device to power down at the low battery state. You're lucky that you can at least -or at least have- been able to boot after a low power shut down. You may need to FXZ back to stock, if the phone will not boot at all. Can you get into AP Fastboot by pressing and holding AT THE SAME TIME the volume up +volume down + power buttons? If so, you can restore to stock and get yourself out of the soft brick. Here is a great thread with discussions by Fall of Enosis and jimbridgman, I suggest you read through this:
http://forum.xda-developers.com/showthread.php?t=1756048
[Q] Unable to charge while off?
Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
fire_fist_ace said:
Cheers for the heads up, its not exactly a question, but I've seen questions on this board before so i thought that was ok.
Thing is, its not that it wont boot, it boots after i charge it for a while, but it states that the charger is not connected each time it boots, then shuts down.
Why should we not allow it to go into a low battery state when on CWM? I also set CWM recovery to start at each boot, and i have backups of just before and after i flashed the phone. Cant i just restore a previous backup rather than flash to stock?
And with the battery reset, doesnt clear any user data yeah? I have alot of stuff i would hate to lose
Click to expand...
Click to collapse
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Apex_Strider said:
Okay, I thought from the thread title that at some point, the phone wouldn't boot after a low power shut down. If the phone is saying that it isn't recognizing the battery while charging, you might have some luck trying the methods I overview in THIS POST. The battery will NOT charge while in CWM Recovery, nor will it charge while in AP Fastboot. This is why it is imperative that you not allow the phone to get to such a low power stage, especially when attempting a flash. You can certainly restore via CWM either of the backups that you have, and see if the problem clears up. And with a battery stats reset, nothing is wiped except the battery statistics. All of your user data, applications, settings, etc. will remain in tact. Hope this helps...
Click to expand...
Click to collapse
The battery reset actually worked! I had to charge it for quite a while on the usb charger since it wouldnt charge on the mains charger. Once it was on i made a backup then cleared the battery stats, and now it detects the mains charger.
Cheers for your help guys i still dont get why it wouldnt charge on the mains charger when the battery was low, even though before it would charge before when the battery wasnt...
I have a 3 week old Note 10.1 with rooted ROM that will not power on. It was put on the charger overnight with battery depleted (should have charged it before it went completed out.)
In the morning I unplugged it and turned it off before putting it it a sleeve. When I went to turn it on in the afternoon, it doesn't do anything to indicate turning on or waking up. I have it on the charger again, but nothing shows to indicate that a connection to the charger is being made on the Note 10.1
I will need to return it to Bestbuy, but can't do it in it's current stage as it's rooted and has my personal data still intact. Can anyone please suggest any options, I tried few that I had read about (holding power button for 30 seconds and touching the screen, attempt to go into recovery) but none pans out.
Thanks
Dave
Try plugging it into the computer to see if it shows up. If it does, try erasing the cache on it to see if that fixes it.
Sent from my EVO using xda app-developers app
plegrand said:
Try plugging it into the computer to see if it shows up. If it does, try erasing the cache on it to see if that fixes it.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately have the same result. Its seems as dead as a nail
Even in odin?
Plug in an otg cable with something lightey (led) to see if the mainboard doing basic jobs.
Can you get into either download (power/vol down) or recovery (power/vol up)? If you can get into recovery, try dirty flashing your ROM. If you can get into download, you should be able to Odin back to stock, though you will lose whatever data you have on your device.
Thanks for all the suggestions, greatly appreciated! Last night I decided to put it back on the charger one more time just to make sure it had juice in the morning to attempt the "finger on the screen and power button" option. It kept just flashing "Samsung Note 10.1" text for few seconds without going any further. I then decided to try "power button" and "volume up" option, took me to the "downloading" screen as it seemed like it was waiting for Odin download. I then proceeded to turn off the tablet and rebooting, which then took me to normal boot up. System indicated charge of 96%, this must have been what I have been reading online (Screen of Death or deep sleep.) I then did a restart to recovery, to perform restore from an backup that was done prior to root. After going thru all the clearing cache etc... and the tablet started to perform the restore, system shut itself and now I have nothing again.
When I was doing the restore from backup, I did not have the tablet connected to any usb connection, maybe that 96% battery was false or something. I put the unit back on the on the power charger again (thinking the battery is depleted again.) Very frustrating, I just want to unroot this tablet and take it back now to Bestbuy.
reminds me on what happened with my note. But for me I thought: "naah, you aren't dead. You're my new babe."
I flashed it immediately after buying and so far... odin always helped. With stock kernel most roms work. Some overclock kernels freeze my note or it isn't bootable 'til stock flash.
edit: you should add a [Solved] into your threadtitle.
Sorry not yet fixed, as mentioned its back on the charger and dead as a nail again.
Sent from my Nexus 4 using xda app-developers app
Try plugging it in and using adb command to get the list of devices and see if it shows up.
Sent from my EVO using xda app-developers app
unodish said:
Thanks for all the suggestions, greatly appreciated! Last night I decided to put it back on the charger one more time just to make sure it had juice in the morning to attempt the "finger on the screen and power button" option. It kept just flashing "Samsung Note 10.1" text for few seconds without going any further. I then decided to try "power button" and "volume up" option, took me to the "downloading" screen as it seemed like it was waiting for Odin download. I then proceeded to turn off the tablet and rebooting, which then took me to normal boot up. System indicated charge of 96%, this must have been what I have been reading online (Screen of Death or deep sleep.) I then did a restart to recovery, to perform restore from an backup that was done prior to root. After going thru all the clearing cache etc... and the tablet started to perform the restore, system shut itself and now I have nothing again.
When I was doing the restore from backup, I did not have the tablet connected to any usb connection, maybe that 96% battery was false or something. I put the unit back on the on the power charger again (thinking the battery is depleted again.) Very frustrating, I just want to unroot this tablet and take it back now to Bestbuy.
Click to expand...
Click to collapse
didn't think Best Buy would take stuff back after 3 weeks. Thought u only had 15 days.
I believe premier members get 60 days for returns
plegrand said:
Try plugging it in and using adb command to get the list of devices and see if it shows up.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Attempted to check for devices using adb, nothing at all listed under attached devices after entering "./adb devices" command. I think the board might have gone bad, as the tablet will not boot at all now, even after 8 hours of overnight charging, it's dead. Is there anything I can attempt to revive so I can unroot it, to take it back for refund? Thanks in advance
I'd take it back to the store and see if the Geek Squad can get it to power up. If they can't then they'll never know you rooted it anyway and you can swap it for a new one. Assuming that it's still in the zone or return/swap of course.
jusliloleme said:
I'd take it back to the store and see if the Geek Squad can get it to power up. If they can't then they'll never know you rooted it anyway and you can swap it for a new one. Assuming that it's still in the zone or return/swap of course.
Click to expand...
Click to collapse
I was thinking of doing that, just was worried what the consequences might be if they would to find out it was rooted later down the line. It's still in the return/exchange window. I guess I'll be taking that chance with them, if they get it to boot, I'll be happy with that and re-store to stock.
So, I was just browsing on my phone, as usual, when all of a sudden it made a loud beep then shut off. It tried to restart itself, but after the LG logo popped up, gray lines came up all over screen, like an old TV that wasn't getting enough reception, and it shut off again: for good. It will not even attempt to come back on or even boot into recovery. It's just completely dead. Plugging it into a charger makes no difference and neither does removing and reinserting the battery. It is rooted and unlocked, but I did that around six months ago. It is still running the stock ROM. I have never put a custom ROM on it. I have not done anything unusual with it. I've just been using it normally. I tried to Google what happened, but couldn't find ANYTHING. I'm praying it's the battery, but will have to order one from Amazon and wait as there's nowhere to get one in my rural area. Has anyone ever heard of this?? A very loud beep an then completely dying?? Please, please help!!!
Celeste8157 said:
So, I was just browsing on my phone, as usual, when all of a sudden it made a loud beep then shut off. It tried to restart itself, but after the LG logo popped up, gray lines came up all over screen, like an old TV that wasn't getting enough reception, and it shut off again: for good. It will not even attempt to come back on or even boot into recovery. It's just completely dead. Plugging it into a charger makes no difference and neither does removing and reinserting the battery. It is rooted and unlocked, but I did that around six months ago. It is still running the stock ROM. I have never put a custom ROM on it. I have not done anything unusual with it. I've just been using it normally. I tried to Google what happened, but couldn't find ANYTHING. I'm praying it's the battery, but will have to order one from Amazon and wait as there's nowhere to get one in my rural area. Has anyone ever heard of this?? A very loud beep an then completely dying?? Please, please help!!!
Click to expand...
Click to collapse
It could be the battery. But sounds like your phone is dead.
Sent from my iPhone using Tapatalk
Celeste8157 said:
So, I was just browsing on my phone, as usual, when all of a sudden it made a loud beep then shut off. It tried to restart itself, but after the LG logo popped up, gray lines came up all over screen, like an old TV that wasn't getting enough reception, and it shut off again: for good. It will not even attempt to come back on or even boot into recovery. It's just completely dead. Plugging it into a charger makes no difference and neither does removing and reinserting the battery. It is rooted and unlocked, but I did that around six months ago. It is still running the stock ROM. I have never put a custom ROM on it. I have not done anything unusual with it. I've just been using it normally. I tried to Google what happened, but couldn't find ANYTHING. I'm praying it's the battery, but will have to order one from Amazon and wait as there's nowhere to get one in my rural area. Has anyone ever heard of this?? A very loud beep an then completely dying?? Please, please help!!!
Click to expand...
Click to collapse
Normally when battery goes on these things they just keep rebooting u nles plugged in and even when plugged in sometimes they stll reboot