Related
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
UPDATE 12/23/2013:
1. I was able to get into Recovery by quickly pressing reboot and reboot into recovery. From here I could get into Download Mode.
2. I first cleared my Dalvik & Cache and reflashed JellyBeans v19, then cleared Dalvik & Cache again. This did no solve any problems.
3. Next I flashed the Stock VRBMF1 Firmware through Odin, which also did not solve any problems.
4. Now I am downloading Root66 and following Hero's guide to unbricking a soft-bricked device.
usatf1290 said:
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
Click to expand...
Click to collapse
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the response!
I would try to flash stock packages through Odin, but i cant get to download mode. Usb debugging is enabled.
Ill probably send it Verizon when i get back to the states, but I was wondering if i could do anything in the mean time.
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Sad for you, mine opinion is it might related to hardware issues. Hope some pros may come up and help you here.
Flash stock firmware from fastboot
ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Follow this guide and everything will be good
Tried flashing but nothing happens
I have tried flashing it too. When it fastboot mode, I see that all the processes are running as intended and once the flash is complete and my phone starts with Moto G, guess what - I see the same old wallpaper and lock screen. It means phone is not flashed .
amolgosavi said:
Flash stock firmware from fastboot
Click to expand...
Click to collapse
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Will trying flashing after 2 weeks of phone phones processes has stopped
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
robm123 said:
I suppose that either means you flashed incorrectly, the phone is still wet inside or the phone is damaged.
Try drying it on a warm, dry place for another day or two.
Good luck!
Click to expand...
Click to collapse
Tried flashing and nothing happens again.
This is crazy!
I do not rely service centers anymore and I can flash myself.
Techies - please help.
ashu388866 said:
I will flash it today again.
Which is the best process to flash the Moto G phone. I have followed couple of methods and they haven't worked for me.
It could also because of the battery issue. I read it on another forum that Factory cable might help.
Can you or anyone else point me to Factoty cable. Searched all over ebay and all I could see is Factory cable for Moto Razr.
Let me know guys.
Thanks.
Click to expand...
Click to collapse
I'm similar situation. Only my daughter's Moto G (android 4.4.4) was not physically damaged.
After sreen unlocking the phone shows errors "Unfortanately [everything] has stopped working".
I flashed stock recovery many times but it does't help.
And one more thing: if the phone is connected to the PC it is possible to run fastboot commands, but the phone filesystem is not accesible.
Is this a hardware problem?
P.s. Sorry for my english
ashu388866 said:
Dear XDA mates,
I am facing this different kind of issue currently. None of the process on my phone are working. Here is what has happened and what is happening:
What happened:
1. I dropped my phone in water. It soaked in water literally.
2. I dried it off but saw that phone was starting and shutting down automatically. I kept it the way it is so that it can dry off further.
3. Couple of hours after I started the device and it was all working but I wanted to make sure it is working fine so switched it off and kept it to dry off till next morning.
4. Next morning phone was not switching on.
5. I put in on charge and after a while try to switch it on. The phone started but was giving me zero battery alert and switching off. I thought it is a usual battery going dead issue and left the phone the way it is.
6. After one day I kept it on charge again but nothing happened so I finally decided to take the device to service center.
7. Stupid service center technician told me, phone is dead completely and motherboard has to be changed. I decided to not do anything with the phone and brought it back home.
8. I kept it on charge and guess what, phone was full charged next morning and it started again.
What is happening:
1. The phone started but now as soon as I unlock the phone, I start seeing errors. (Unfortunately, Google Play Newsstand has stopped, Unfortunately, com.google.process.gapps has stopped, Unfortunately, Weather has stopped etc etc, the error never ends).
2. Now it thought of doing a factory reset, went to Fastboot mode, selected the Factory option, phone goes to Moto logo and I see the same old lockscreen. Phone is not resetting.
3. I thought of flashing the phone with stock firmware, went on fastboot mode again, tried to go on Recovery option. Phone returns to fastboot mode with error (in yellow font) "Boot up failed".
Now I am stuck, I see some serious problem has happened for sure.
I need some super expert help and need to understand what might have happened to my phone.
Click to expand...
Click to collapse
Flash the stock rom via fastboot dat could fix the problem:good:
My tablet is unrooted, untouched, unmolested, etc. Running 5.0.1 from the ota update.
My tablet's battery died while I was using it a few hours ago. I put it on the charger and wait a bit before turning it on. It boots up normally but I'm immediately greeted with the "power off" message box as soon as android loads. I've done fastboot and did the recovery boot (whatever that means in this case) and nothing I have tried has helped.
I'm afraid of tampering with it to install custom roms, because if that doesn't work the warranty would be void.
Anyone experience this problem before?
Sounds unusual but my only recommendation is to leave it on the charger overnight to get it fully powered up.
If not, you might have to boot into the stock recovery and perform a factory reset. At that point if it still doesn't work, if your tablet is completely unrooted with a locked bootloader, just send it to Nvidia.
Yeah it sounds like it's gonna get rma'd. It was charging the whole time, in the 4 or so seconds it was on the lockscreen before turning off it would show the battery percentage at something like 60%+, so it was definitely charging.
After enough tries it just wouldn't even give me the nvidia start up splash screen. I managed to do a factory reset (which seemed to take a really long time). The factory reset let it get back to the lockscreen but it immediately turned off again.
Other things for people who might have this problem as well:
It started after I put in a 32gb micro SD card I bought for it. I think the SD card is fine because it works in my phone.
Also this tablet was only about 4 days old when it broke.
The tablet is completely stock. I'm lucky it broke so soon as I was about to root it.
http://forum.xda-developers.com/shield-tablet/help/tablet-shutdown-boot-t3035492
Hey all,
First of all, forgive me if this has already been covered, but I couldn't find any threads that had a solution to this specific problem that worked for me.
That said, I have a Droid RAZR MAXX HD that I rooted and flashed to page plus just about two years ago. I have since unrooted the phone. It was running on jellybean 4.1.2 if I recall correctly. The phone has been great and I've been very happy with it till today. I shut it down, nothing out of the ordinary, just decided to turn it all the way off. When I later went to turn it on, it got stuck in the middle of the little boot animation where the robotic iris opens to reveal the red eye. It froze there for 3-5 seconds and then rebooted only to do it again. Funny thing is, it freezes at a different point every time. Some times the red eye is completely visible and sometimes the iris hasn't even started to open. I tried booting without the sd card and when that didn't work I tried all the other typical stuff: simulated battery removal, cache wipe, factory reset-wipe-format. I also tried a stock system data wipe as well as a stock recovery, both with mattlgroff's Doid RAZR utility from AP Fastboot mode. Still nothing.
At this point I'm at a loss. I bought this phone for $300 back when it was the phone to have and it's been a great phone, I don't want to lose it if I don't have to. Any help would be greatly appreciated.
Just a quick update.
I decided to take my phone apart and see if there were any loose connections that might be causing issues with booting. I didn't find any loose connections so I put it back together, and decided to try booting it on a whim. To my surprise, it booted perfectly. A few weeks ago I installed ancleaner, and app that claims to clean your cache, yada yada. I'm guessing that somewhere along the line, it managed to corrupt a deep system file or the cache or something. Regardless of what really happened, my phone is alive again, and I think that it was probably due to physically disconnecting the battery. So moral of the story is, don't trust the simulated battery pull, and physically disconnect it for a time instead.