Related
Sometimes when I leave my Nook alone for awhile and then come back I am unable to wake it up by pressing one of the hardware keys. I have to plug it in and it boots up(rather than just waking up) has anyone else had a similar problem?
THis is seemingly random. It was on sleep all night and I woke it up to read this morning(after about 8+ hours of being in sleep mode). Just now however I tried to wake it up and it would not(after less than 45 min of being in sleep mode).
I'm having a similar problem. I've found that I can also make it come on by holding the power button long enough for it to do a shutdown (30 seconds I think) and then turning it back on. After I did a factory reset it worked correctly for a week and is now doing the same thing. I've had the issue on the stock software and with root applied. I'm going to return it today.
I know it's not helpful, but at least you aren't the only one with the problem.
How does the return process work? Can I just box it up and take it back to the store?
You might try a full factory reset before returning it. Do the 8X reboot and then the 3 button data reset. See if this helps as it may be a software issue and this may help/eliminate the problem.
Yes, I have seen this before. Are you running SetCPU on it? I removed it from a friends device and it resolved the problem in that particular case. He was going to return it as well. He probably would have had the same issue with the next one since he would have potentially installed the same apps (with the same settings) on it from backup. SetCPU may not be completely at fault since it may have been setup wrong. All I know is that, it stopped happening after it was removed.
I was using CPUtuner up until a few days ago. I was however using Settings Profile Lite so I don't know if that may have had something to do with it.
I've had a similar issue ... occasionally it won't turn on, and I need to hold the button down for 20 seconds or so to get it to reboot.
However, I've found that if I use the N button to bring it out of standby, that it happens so infrequently that I haven't taken the time to troubleshoot if this behavior persists in an un-rooted state.
Sounds like exactly the same issue I have with a SetCPU for Windows Mobile. Locks up the device on wakeup and needs a soft reset to get it back up and running. Almost made me late for work as my phone is my alarm.
I believe it also had the same effect on the EVO I had for a bit but configuring to a more strict setting and keeping it from throttling up and down seemed to help. (OnDemand setting over conservative I believe)
About the return, yes just box it up with the cord and take it back. I told them the issue and they exchanged it for a new one with no problem. I did the full factory reset before I took it back so that I could unroot the device and it still displayed the same behavior. So far on the new one I have no problems. I do notice that the power button click action is better on the new one. Perhaps that was a problem with the one I had.
Hmmm. Okay. I just attempted to wake up my nook with no luck after doing the factory resets last night. I will probably be boxing it up and exchanging it tomorrow.
Sent from my NOOKcolor using the xda app
I used to have the same problem and found that all I had to do was uninstall and reinstall auto-nooter and problem solved. Im not sure if you're rooted or not.
I get that once in a while... haven't looked much into it but if I plug it in it'll reboot or if I hold the power button for a while it'll also reboot. No biggie... I'm a WM user for a very long time. I've learned to live with the little annoyances
I got mine exchanged, the lady just wanted to update my softwre because she was sure that would fix it, then of all things the screen crapped out and wouldn't respond to her touches anymore so I got a new one.
I haven't rooted this one yet.
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
The same problem, HELP US
Elgari said:
Brief history: I bought my Kindle Fire HD in November 20012. It was the first android device I had, so I did not know anything about it. My first search was for rooting, thing that I could make with the help of this forum. From that moment I started reading the forum because everything was new to me and interesting. Meanwhile my rooted kindle worked fine until at some point began to turn off alone. With help of some people of this forum, I was noticed that the problem were gmail notifications. I disabled the notification and the problem was fixed for several months . . . but after that she started doing it again.
There began -also with the help of people on the forum- an odyssey of endless tests, install and uninstall apps, upgrades, downgrades, battery calibrations, etc. until I decided to install TWRP and flash CM 10.2. Of course I learned a lot in this process and I am very happy with CM 10.2.
But what which leaves me sad, very sad and frustrated, is that remain turning off arbitrarily and randomly!!!!!
It can spend two whole days working fine until battery is low, but it can also happen that its turns off every 10 minutes. It is totally independent of the battery charge, although it tends to do more when it is around 50%!
After that, sometimes I can turn-it on normally, but sometimes I have to try 10 or 20 times because she turn off again while charging system.
If I plug-it (to wall or PC) she normally turns on and does not auto turn off again (while plugged).
My latest finding is that if when she turns off itself I shake-it vigorously I can then turning on normally. It's like there's a loose connection or something like that.
As I'm outside the U.S. have no chance of sending it to Amazon.
I really appreciate if someone have some idea about this problem.
I want to thank again all those who given me very good suggestions. It is thanks to them that I learned a lot.
I edit to coment another thing. When I use Corpse Finder from SD Maid, it detect 3 files: .adobe-digital-editions; kindle and Digital Editions ( the three placed in: /storage/emulated/0). No matter how many times I clean it, they always are found in a new corpse search. I don´t know if that its relevant, but is strange to me.
Click to expand...
Click to collapse
I HAVE THE SAME PROBLEM, I DON´T KNOW WHAT´S HAPPEN. Can you fix it?
i have heard occasionally around on the forums of peoples power buttons and such doing this after a while, if that is the case you might be able to test for it but its kinda complicated. Is it sleeping or shutting off? If it's shutting off it would be interesting to see why but you'd have to have either a logcat running on the pc the entire time, a cat of the kmsg, or something of that nature running and turn off while its doing that, then you can find the root of the problem. If it won't do it while plugged in, cm has a way to wirelessly do adb commands. I think hashcode said in his sources theres a test binary for the buttons to see if they are doing anything, but i'd have to figure out how to cross compile it by itself if thats the case, unless its precompiled.
Yes, cassualy I fix it last week. I open the Kindle, looking the wires and conectors and close again. And voila . . . fixed!
Enviado desde mi Amazon Kindle Fire HD mediante Tapatalk
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.
Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
quaxer said:
Ok, so I bought a brand new in box Moto X from an acquaintance. After a month or two it started randomly rebooting, and after a couple of weeks of rebooting once or more per day, it died. Wouldn't power on (not even recovery). I sent it in for repair>got it back>3 days and it died again>sent it in again>got it back>1 day and it died again>sent it in again>got replacement>2-3 months later the new phone is starting the cycle again. Every time I pull it out of my pocket, the lock button doesn't work, and it's locked up on Active Display. I hold the power button and reboot it, only to have it happen again in an hour. I am doing a factory reset now--does anyone have any idea what the problem may be? what i should avoid when setting it up again?
This phone is 100% untampered with. No root, no nothing.
Please help me out. Thanks!
Click to expand...
Click to collapse
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
bothgoodandbad said:
That sounds like a headache.
When were both phones manufactured? What version of KK were you running? Did you upgrade software OTA, if so what did it upgrade to?
Are you saying you never downloaded any apps? never installed anything on the phone? What services did you use? (apps.. anything, what were they?) Were there any other things you noticed out of the ordinary? What were Motorola's responses the first time they replaced the phone? What are their responses now that you are having the same issues with this replacement device?
Otherwise I'd advise you let us know what modifications (apps installed, anything) you had done and continue to do, that will give a variable context to the issue, at least. Other wise we a have an issue with no variables on the actual phone. The more information you give the higher quality the responses you can receive
Click to expand...
Click to collapse
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
Thanks, hopefully your info helps someone help you better or hopefully it can help/spark someone truly seasoned in android/moto x etc to chime in
To check your manufacture date boot into your fastboot menu, check image to verify you're there.
Then choose BP Tools and then once that menu loads choose the option for UPC/Manufacture date read out, check for the date when it appears on the screen, maybe you are on a batch that has specific issues.
I've never heard of this issue, yuk sounds terrible. Goodluck! If you do end up finding answers somewhere else can you please come back here and post the resolution?
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
maybe static electricity?
or do you use any cases?
maybe wrong charger?
Multiple devices, different Android versions, Sounds like an app issue to me.
If it happens frequently, then that is good in a way... You could factory reset and don't install a single app. If it doesn't act up for a couple days ..... Install about 5 apps. Go a couple days.... Install 5 more, etc... Etc. When it starts to act up, you know it's an app you recently installed, so it'll be easier to narrow down.
A logcat could help too. Search on that for how. It would likely show what happened at the time of the reboot /shutdown.
quaxer said:
1) I don't know when the phones were manufactured. Can you advise me how to tell?
2) I had a number of apps on it including WhatsApp, BBM, Toggl, SwiftKey, The Weather Network, ES File Explorer, BBC, The Economist, Espresso, Google Now Launcher, Dictionary.com, TimmyMe, MyBackup Pro, eBay, Amazon, Kayak and a few others. It's still doing the same thing after a data wipe.
3) The first three times I had trouble they had me send in the phone with no quibbles. The first two times they tried to repair it (the documentation just said "replaced component, and reflashed software"), and after two failed attempts, they simply replaced it. Now they want to start the cycle over again... asking me to send it in for repair.
When they sent me the replacement it arrived with 4.4.4. The previous phone had issues with 4.4.2 and 4.4.3 both. I am still running stock 4.4.4.
Thanks for your help
Click to expand...
Click to collapse
quaxer said:
When I hit BP Tools it just reboots the phone... I don't know what's wrong???
Click to expand...
Click to collapse
use the volume +up button (once BP Tools is highlighted) and not the power button to select BP Tools I'm assuming that's what's happening, hmm
I would send it back to Motorola again. If the issues continue, tell them you want it replaced with something else like the 2014 Moto X.
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
quaxer said:
Ok -- so the issues stopped completely over Christmas vacation, but I went back to work this morning (I work in a dusty woodworking plant) with my phone in my pocket, and bang, they were back. Every time I pulled my phone out of my pocket it had powered off, and finally it didn't want to power back on. I called Moto, and this time actually got a competent rep on the line. He blamed the issues on static electricity, and I second his opinion, because the machinery I work with tends to create some static, and the dust in my pocket may exacerbate the problem (?)
Anyway, he recommended that I plug the phone in and hold the power button for 2 minutes to drain the static. Voila! It seems to have worked.
Solved for the time being. Thanks everyone for your input.
Click to expand...
Click to collapse
This thread is awesome.
Also, I recommend leaving your phone on your desk/home/car when you work
Or maybe a full-body armor case or something.
Statics & electronics = bad idea. Even if you can drain it and it works, it's still hurting the components inside.
So, it's been a bit, but I just came back to this phone. I never did send it in to Moto, though it seemed to have died completely. It sat in the drawer for a couple of weeks, and now on a whim I plugged it into my computer, and it started up! I had never tried plugging it into a computer, just chargers...
BUT,
In the last 10 minutes it's been sitting here rebooting itself every 2 minutes... I guess I'll try wiping it again (It didn't do the trick last time), but this phone has serious problems.
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
pantera1989 said:
This is a very strange problem. I never saw anything similar in my life and I searched for someone with a similar problem but I cannot find anything. So I am posting this thread, maybe someone here knows what I should do.
This tablet has been riddled with problems, but this one makes it close to useless. I had several problems since I got the tablet where it won't wake up after sleeping and you had to reboot the thing, where the dock is not available after sleeping and you have to undock and redock it, where the battery drains while sleeping etc etc. Annoyances but I can live with them. I know there is a fix for the dock and you have to send it to Asus, but shipping is expensive so I'll learn to live with it.
This problem though.. this is a big one. So just to clarify, the tablet is rooted with the original 4.4.2 ROM. I did not make any changes in the past week. Yesterday morning, I woke up and used it normally. Later that morning I unplugged it from the charger and that's when I noticed this problem. So while it is connected to the charger the tablet will function normally. After I unplug it the tablet will freeze after a few seconds, reboot on its own and then it will boot until the icons start coming up. Usually after this you get the lockscreen, but instead the screen will black out. After a few seconds the icons start coming back and the the screen will black out again and so on. This loop will continue forever unless you plug the charger in. When you plug in the charger, the icons will come up and after you get the lock screen (instead of the black screen), and you can use it normally. If you unplug it again, the boot loop starts again. This behavior is the same whether using the dock or not.
I don't want to do a factory reset just yet if I can. Last time I did a factory reset, the tablet would not boot and I had to send it back for a replacement. When I get to the fastboot screen, trying RCK I get the dead Android with the red exclamation, and cold booting does nothing.
Any suggestions please? Any kind of log I can get to help? I can post a video if the problem is not clear.
Thanks.
Click to expand...
Click to collapse
Hi, to start this reply, I'll let you know that I am no professional at any of this stuff. I am a regular person that has had experience with flashing ROMs and whatnot. In my opinion, this seems like a software (maybe hardware) related problem. So there are a couple of options you have here.
1. Are you still under your warranty period? You could return it and get another one (easy fix)
2. You could try to factory reset, and if it doesn't turn on, rma the tablet (which it sounds like it may be cheaper to just buy a new one anyways)
3. You could try unlocking the bootloader. Then install a custom ROM (kind of risky, but might be less risky than #2)
Overall, you are not in an amazing spot with your tablet. It saddens me to see all the problems with asus's tablets. I have been with them since the transformer prime because of their laptop like tablet makes it easy to use in school, but its always been a struggle staying with their lineup. I have returned their tablets multiple times. Please update when you can
Sent from my SCH-I545 using Tapatalk 2
If you have a microSD in the tablet take it out and try to boot it. I have seen the weirdest problems because of a card on the fritz....
Second possibility: Hardware. The behavior (working fine when connected to power) seems to indicate it doesn't get the charge it needs from the battery. Could be that it is going kaputt. It's not totally fried but enough that the tablet does not get a reliable charge from the battery.
Third option would be to reflash the firmware. That would eliminate a software problem. You will loose root if you do that...
Since you're still on the original firmware, I assume you did not unlock the bootloader and rooted with Towelroot - correct?
Whatever you do, backup everything you care about off the tablet now....
Thanks for your replies/suggestions. I could not use towelroot as it was on 4.4.2 (I think I read it is not possible). The bootloader is unlocked. This is my second tablet as I had returned the original one. I tried putting Cromi-X on it, and when I got to the step to factory reset it (using fastboot), the thing just was stuck in an endless loop. I could not even get to fastboot and my PC wouldn't recognize it. All it did was boot to the ASUS logo (and the message that the bootloader was unlocked) and reboot.
So this is the replacement unit and the charging issue was the problem. I say was because believe me or not the tablet is now smashed to bits. Since it must always be connected with a charger to work, I was carrying it around docked as I usually do and forgot that it was plugged in. I have resorted to an extra long extension cord with the charger plugged in to walk around. Anyway I forgot it was plugged in, the extension cord reached its limit and the charger cord yanked the tablet out of my hands and onto its side - screen facing away. I sweared, feared the worst and went to pick it up. The good news is that it still boots. The bad news is that the screen is completely smashed. The back cover is bent at one corner and the glass is smashed at that corner with cracks running to the other side. The touchscreen is not working anymore either. To add insult to the injury the tablet still only boots up with the charger plugged in..so there's that.
I don't know what to do now. I have contacted ASUS for a possible RMA but got no response yet. The thing is I don't feel like spending more money on it given the problems experienced. A screen with digitizer on ebay is about €75..so not exactly cheap.
I guess we can close this thread as it is now pointless. I hope no one has to go through my experience and that maybe it was a one off thing.
Thanks again to whoever replied. I appreciate it.