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
Related
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
Hello Everyone,
I'd be eternally grateful for any technical advice and wisdom anyone that can help with my issue! I have a previously rooted phone that I have to return for a warranty, but the bootloader is unlocked and I can't lock it again.
Here is the problem, my phone completely shuts off about 10 seconds after the screen turns off. It's a full shut down, not just the screen not turning back on.
Some other symptoms:
My phone won't power on while it's plugged into the wall outlet. I have to remove it from the charger for it to turn on. But it will charge while the phone is ON and I plug it into the wall outlet afterwards.
My phone will automatically shut off when I plug it into any USB cable connected to a computer that's on (however, it doesn't automatically shut off if I plug it into the wall charger while it's on)
When I press power and volume down for ODIN or volume up + volume down for the bootloader screen, both screens will only show up briefly, then the phone will immediately shut down. I can't access either menus.
I have tried swapping out my battery with my wife's, and it does the same thing. Her phone works perfectly fine with my battery, mine doesn't work with either. (We have the same phone).
I rooted my phone a little less than a year. It became unrooted quite a while back when I accidentally ran a stock update. I never messed with it since. I'm EXTREMELY rusty with rooting and custom firmware and flashing, etc., so I apologize in advance.
I'm terrified because I'm sending out my phone under that Samsung warranty because all of my tech sense tells me there's a hardware issue going on; it's not my fault. However, aren't they going to see the big "Unlock" icon under the google logo when they get my phone, and immediately say I have a voided warranty? The representative said they'd charge me $300 if they phone was "damaged".
I almost wish my phone were a complete brick and wouldn't turn on at all. But at this point without access to a bootloader menu and my phone being unrooted and not able to work with it on my computer, I'm not sure what I can do.
It's already restored completely to factory defaults through the android interface. But that "unlock" icon is still there when it boots.
Anyone have any advice for me at all? Again, if my terminology is off or I'm not being clear in some way, I apologize. Let me know and I'll clarify and/or give any more information required.
I have about three days to figure this out before the prepaid shipping box and my new phone gets here.
Thanks so much in advance.
Sincerely,
Darkencypher
Just for clarification, its the Samsung Galaxy Nexus SCH-I515.
Thanks
Darkencypher
Last chance
As I'm running short on time before my new phone gets here, I figured I'd give it another shot at seeing if anyone out there knows how to help me.
I'm nervous that the "unlock" logo that appears below the Google logo when I boot my samsung galaxy nexus means that my warranty is void. I was able to restore it back to factory defaults, but I can't remove that "unlocked" icon because the phone is so severely disabled in its current state do to some hardware problem that keeps it shutting off.
I'd settle for anyone even knowing how to turn my phone into a paperweight at this point. I'd rather it not turn on at all when they get it lest they see I've unlocked my phone and void my warranty even though I'm certain I have a hardware problem due to manufacturer defect.
Also, on a side note if anyone reads this and knows a little bit more about troubleshooting phones based on symptoms: I downloaded a program called Wake Lock and set it to keep the CPU running in the background even when the screen is off. It doesn't appear to shut off anymore when the screen turns off.
Thanks again,
Darkencypher
Hello, here is my problem. I posted it here as well, but maybe it's not the only place because it might be more than a CyanogenMod problem? (http://forum.xda-developers.com/showthread.php?p=57411392#post57411392)
The other day, my phone shut off. I thought maybe my battery (zerolemon standard size) was dead, so I tried charging it, but I realized that nothing was happening. In fact, my phone didn't even start up. I would see the Samsung Screen, then Cyd (sp?) the Android showed up, but it wouldn't boot. I could still get into my Recovery, so I tried reflashing CM11, but it still was broken. I had put in my OEM stock battery at this point. I even factory reset, but nohting.
I found that by flashing Bonestock, that my phone worked, however. So I grabbed whatever photos and files that I deemed important, and tried formatting data, then reflashing the newest cm11 nightly (12/6 i believe. ) STILL nothing. Wouldn't boot.
Finally, I used ODIN to go back to stock (4.1 or something), then rerooted my phone, and put the 12/6 nightly on.
It worked, for the time being. A few random restarts, but nothing weird.
However, Today, i noticed that the random restart happened again. I press the home button, cuz i think it's on, but it isn't. It vibrates, then starts to reset. I see the Samsung screen, then nothing! This is with my zero lemon. I can't get it to go to recovery or anything w/o shutting off.
I put in my stock battery, and it starts right up! However, after a few hours, it starts turning off and doesn't boot up.
I managed to get it into recovery long enough to reflash hyperdrive, because it seems like touchwiz roms work?
questions:
1. is this a CyanogenMod problem?
2. Is this a hardware problem?
3. Is this a battery problem?
4. What should I do? If I stay on this touchwiz rom, I can't use my Moto 360. You need 4.3 or 4.4 to use Android Wear.
5. I am thinking of unrooting and sending my phone back through warranty. (cuz it might be hardware problem). However, if they send me a refurb, would it be unlockable? Cuz it's like 4.2 or something? and then I'm stuck w/o my Moto 360. (what's the latest verizon update?) (also, is there a chance i'd get the phone like 4.1 and then i could still root and unlock bootloader?)
6. the other day, before this happened, it was raining and i used my phone. i don't think water got in... but could this be the result of that? I don't see how water would hate CM but like TW though.
Thanks, any ideas would be super helpful.
chances of getting a phone that is rootable and bootloader unlockable is very low, if there's any chance at all. if you wann try and replace the phone why not try swappa and look for one that is either bootloader unlocked or look for one that is capable of being unlocked. other then that, i dont see any way of getting another one that you can root and rom.
Thanks. I would get a replacement through my Verizon insurance. I guess it might be the end of an era for cm my galaxy s3. Sigh. Just looking forward to nexus 6 hopefully for Christmas.
Background: I had my completely stock Nexus 5 on the charger for around an hour. When it got near 100%, it locked up for about 5 seconds and powered off. It wouldn't charge or power on again until 2 days later where it would power up but not charge. It could go to the bootloader/recovery but it would still shut down. The charger used won't charge anything anymore, it may have been a power surge that messed it up.
I replaced the battery and the system is still unable to maintain power but recovery and the bootloader are stable (just formatted the cache and the phone did not power off, took around 15 minutes). Now it won't power up again.
Any idea what the issue could be? Could it be corrupted data?
First, try another cable and charger.
Also, make sure you have enough juice on the device first, reflash stock firmware with fastboot and see if the issue remains.
If you successfully flash your stock firmware and use another known working cable and charger and it's the same.... Then unfortunately it could be a hardware issue.
Thanks for the reply.
Unfortunately, that didn't bring my N5 back to life. I'm think a circuit may be fried on the motherboard but I don't have a real way of judging that at the moment.
Any chance you might be able to guess what the hardware issue could be? I'm mainly trying to save the data on my phone and I'm not against taking the phone apart to do that.
Update: I took the phone to a Sprint store and a technician looked at it. When the tech plugged it into the charger, the phone LED was flashing red with no charging screen. It eventually booted up and shut down. Later that day, I could see my notifications (Pushbullet is a wonderful app) and noticed the phone stayed on consistently. He said everything was fine and their formal report didn't mention any sort of damage to the phone that they could find. Later that same day, it died again. Today, I decided to completely wipe and load 5.1 to the phone. It stayed powered on through the whole flashing process (bootloader unlock and individual partition flashes) but shut off during "optimizing apps". Considering it powered off in the system, I'm thinking the issue is with the RAM or the CPU possibly being fried due to a power spike while on the charger. It seems like it only happens during heavy operations.
Something hardware it seems. Not sure what, but if a component on the mb is bad then it is a replacement.
I like the title though, doubt anyone has a device that stays charged while in system. Sorry about your phone, but made me chuckle. I really can't think of a better way to describe it, not trying to pick on you.
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.