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
Related
Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
anyone?
I'm no expert on this but it seems about all you can do is to NVflash some other ROM since that will wipe your internal memory and repartition it. Then go back to HC again. If you have anything important on your device, back it up somehow as all data will be erased. There are lots of Guides and How To's here, some are good but some aren't! You'll have to read, read and reread till you go blind.
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
Though you are running Dell's official rom, I'm not sure which rom it is. Anyway, I suggest you follow the instructions here and update it to the newest 514 rom. This will wipe your ds7 and give you a clean start.
http://streakblog.blogspot.com/2012/01/new-patch-to-fix-docking-bug.html
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
cdzo72 said:
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
Click to expand...
Click to collapse
I am running stock 514 rom and found it to be less prone to the reboot. Before this update my ds7 would reboot at least 2-3 times a week. Now it would be 2-3 times a month. I noticed that some apps do trigger the reboot, specially poor written apps and non-honeycomb apps. So don't go installling every apps under the sun.
But back to the OP problem, you seem to have an excessive amount of reboot. I would update to the 514 rom first because it is simple and easily done before you nvflash to other roms.
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
TheManii said:
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
Click to expand...
Click to collapse
I wish I had your luck... On all HC roms... Stock or Steven's I had reboots so bad that my 7 was almost unusable... Not much without root but after root it got real bad... I even quit using it for a while... But mine is the 4G version so that may have had something to do with the instability
SGS II I9100 from TapaTalk
ok, this sucks
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
domenicostorino said:
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
Click to expand...
Click to collapse
Our friend TheManii wrote a thread on how to take apart the ds7. Link below.
http://forum.xda-developers.com/showthread.php?t=1441139
Oh wow this sucks... I mean cool guide but it is so extremely difficult to take it apart without damaging it! It is basically being held together with glue :S
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
metal man007 said:
Hi guys.
First post, apologies if it is in the wrong place.
I was given a Motorola XT925 3 days ago, running what I can only assume is the most recent version of android (i tried updating it, and it claimed it was up to date). No SIM card in, no SD card.
All was well, until I noticed an app, "media" sucking 50% of the battery. It was killing me, so I did some extremely brief Googl-ing and arrived at the conclusion that a factory reset would be a sensible thing to do to nip the problem in the bud.
Unfortunately, my battery ran out half way through the reset (derrrrrrpppp), leaving my new phone semi-hard-bricked.
The loading icon will come on sometimes if it's put on to charge after some time off charge, and sometimes the stupid little robot even pops up, with a loading bar underneath him, and a tangled blue web protruding from his abdomen. He freezes a short time later.
The power and volume buttons are unresponsive, and the whole semi-booting pattern is erratic, but things seem to happen if I leave it off/on the charger all day.
I have a suspicion that my phone in it's current state has half the operating system un-installed, and will therefore not boot correctly.
Anyway I was hoping to get some recommendations for the most appropriate next step. I will be taking it to a nearby shop tomorrow, and see-ing if the people who sold it to the person that gave it to me can help...
I have read about "flashing" devices etc, and if the shop-people can't work it out, I'm probably going to give it a try. I am running a mac as well, so many flashing programs will probably be incompatible.
Thanks for the help
tl;dr: Motorola XT925 hard-bricked following complete battery depletion during factory reset. Wat do?
Click to expand...
Click to collapse
Hi,
Unfortunately, we cannot help you with your XT925 on the Moto X forum.
You can post your request here: http://forum.xda-developers.com/droid-razr-hd/help
Someone in the Razr HD Forum will be better suited to help you with this.
Good Luck.
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
ScrewedImei said:
I have the feeling I'm going to get repetitive here guys, but I've been reading the troubleshooting threads for over an hour and couldn't find an answer to help me.
Last saturday I was to lazy to move from the couch, so I watched as my S3 Mini ran out of battery. I got the "phone is turning off" screen as usual. Later I went to bed, but as I needed my alarm to go off in the morning I tried turning it on again, and nothing* happened. Plugged it on the wall, nothing*. Replaced the battery, nothing*. Gave it a good half hour plugged, and as you can guess, nothing*.
* when I say nothing, I mean it won't light up, won't vibrate, won't wink for me, won't load any kind of error, it's actually just like if you were trying to turn on a phone without any battery connected, no grasp of life comes from its poor soul.
The only moment I could see some action on the device is when I tried connecting it on the PC a few hours ago, as it installed drivers to Windows. Right after installing the drivers however, it won't show in the file explorer. I've tried to detect it with a few development tools such as ORT and Odin and there was no sucess either. Download or Recover mode will not work as well.
One thing I think worth mentioning, is that ever since I rooted it a couple of years ago, whenever I tried to recharge it while it was off, the standard "green charging battery" would never appear. What would appear on the screen was a freezed loading icon (the one that keeps roling again and again, but frozen). This particular issue never came off, even reseting it or installing new ROMs.
I always used Maclaw's, some of the latest 4.x, because I tought the 5.x was to heavy for the s3 minis.
I've read some about USB JIGs and stuff, but what makes me very curious is what the heck?! The phone was working just fine, the battery runs out and I have a brick? Is this possible? Can anyone tell me any work around?
I apologize for possible grammar mistakes.
Click to expand...
Click to collapse
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
bejunk said:
try to plug in the phone into charger & leave it there like 20 mins or more. battery loads then.
then try access samsung download mode, if you cant the phone is probably useless (brick for ever) because itslike mthe last standing thing.
& sorry i say that but thats typically samsung behaviuor. there allways this kind of threads in the samsung forums of xda... other manufacturer can mostly be restored or atleast you know what make it dead.
Click to expand...
Click to collapse
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
CrashOverride93 said:
Exactly the same problems happening to me.
This is my thread:
http://forum.xda-developers.com/galaxy-s3-mini/help/sgs3-mini-dead-t3085031
Can you try to follow what appears on this link? (I can't by now because my PC is broken)
I think won't do nothing because you won't be able to access to the recovery mode on android, as me, but to try...
http://forum.xda-developers.com/showthread.php?t=1840030
Click to expand...
Click to collapse
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
ScrewedImei said:
Hi there,
Thank you for your interest but I have passed this point already. Tried a brand new battery I had laying down in the drawer (which was fully charged with an universal charger) and there is no answer to any attempt of turning it on. Via recovery, download or normal boot.
Hello there,
I'm sorry to hear I'm not the only one affected by this bug (lets call it a bug). This shows there is a lack of concern from Samsung on dealing with this issues, and thus we see that old programmed obsolescence.
I will try that later on the weekend, and I come back here with an report.
Cheers
Click to expand...
Click to collapse
this guide useless for you. how u want flash things with odin if u cant enter download mode at all??
im really sorry for you that this phone is dead. just can give you 1 advice, dont buy samsung in future.
I have been repaired my phone successfully!!!
I just needed to change two capacitors on its motherboard, and that's it.
Here the video where I have found the info and how to do that. It's in Spanish but easy to understand for you I think. But if you need some help, send me a PM.
can you take a picture from the location of the 2 capasitors and the types of it
Hi everyone.
I have some news. It took me a while but I followed CrashOverride93's advice on that video. It actually solved one issue, as I now can turn it on, but now I have a second problem, I'm stuck on a boot loop, with acess to Download mode ONLY. No recovery.
Considering where my issue started, and where I am now, I have tried the following:
- Flashed via Odin stock ROM, kernel;
- flashed Wipe;
- flashed PARAM;
- three button combo.
So far I couldn't get it pass the boot loop. Any thoughts?
So, my Amazon subsidized R1 HD is rooted with systemless Xposed installed. I did take the OTA update last week. It had been working fine for two days. I powered the phone off and placed on the charger, at which point it keeps continuously attempting to boot, just flashing the White Blu screen every 4-5 seconds. No combination of button presses, or holding of power seems to be able to stop it, so can't power the phone down, or get into TWRP. Ideas? It does not have a SIM in it at the moment, or when this occurred if that might matter.
While I have rebooted the phone many times, this may have been the first time that I have completely powered it down since rooting and installing TWRP this weekend. I had not made any changes to anything for a day or so, and it had survived many reboots. The only thing I can think of is that I did freeze the Amazon Offers App in TiBu to see what would happen, however, not sure that is in anyway related since it is not even getting to a point in the startup where it would check.
Disregard the issue, after rebooting every 3 seconds for 7 hours, the battery died and the phone then properly booted on the first attempt. Not sure what happened, but all seems to work.
i dont think your the only one to have this happen to.
http://forum.xda-developers.com/member.php?u=2645880
that one got fixed same way. just letting it die. unfortunately that may take some time on full change.
edited.
oh i didnt realize that was both you.
This is the second reported instance with this behavior: http://forum.xda-developers.com/showpost.php?p=68027804&postcount=926
Wondering if we should start a thread for reports and the circumstances under which it occurs? In my case it occurred when using a 1st Gen Nexus base and a 3rd Party cable...... wondering if the behavior is charger related? Would be interested to hear if it happens to anyone else when using a BLU supplied charger and cable.