Unable to root Kindle Fire HD - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie

Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.

soupmagnet said:
Sounds like you received a defective device. Send it back.
Maybe the "German Edition" versions were those that didn't make the first round of quality control checks.
Click to expand...
Click to collapse
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.

noskill123 said:
I only mentioned it because my firmware version isn't 7.21 (sorry my fault) but 7.20. Never heard of it, maybe the eu version somehow differs from the us version.
Click to expand...
Click to collapse
7.20 is on the 32GB that I just received today.

soupmagnet said:
Sounds like you received a defective device. Send it back..
Click to expand...
Click to collapse
yup, it's the right advice. don't try to force any root, send the device back instead and have a new try with the next one.

The root will work for both 7.2.0 and 7.2.1, barring any anomalies with your specific device. I would use the automated root found on this forum when you try rooting next time, since it'll eliminate any possible mistakes (not saying you made any). Either way, everyone else is definitely right in saying you got a defective device. Luckily, Amazon's pretty good about replacements when you're under warranty. My own device's CPU was running so hot, it smelled like things were melting. Got it replaced with no fuss, and no extra charges.

noskill123 said:
Hi!
I got my kindle fire hd today (german edition) and tried to root my device. So i watched the guide on *** and read several articles and forum threads to be prepared rooting the kindle fire. Ok first of all: i might have damaged the screen, although i have no clue how this happened. One of the corner led doesn't work properly anymore. The effect is like heavy clouding on led tvs.
I followed exactly the tutorial on ****. After the first step, the processor starts to heat up and the tablet slows a bit down. After the second reboot the tablet gets really hot and significantly slows down. The screen starts to flicker and the tablet needs about 10 seconds to execute a command. After a reset to factory defaults everything works like charm except the clouding. I changed the usb port, reinstalled the android sdk and even used qemuroot. Nothing works. I am going to send my kindle back and buy another one, but i wont try to root it without solving this problem. Does anyone have an idea??
/edit as a new member i can't post any urls. The first *** is reverendkyle.c*m and the second is an article on redmondpie
Click to expand...
Click to collapse
That’s exactly what happen to me about 10 days ago my KFHD
Get hot and speed is unbelievable slow down but I do manage to reset to factory setting
http://forum.xda-developers.com/showthread.php?p=32866304#post32866304
But finally I manage to root my KFHD and switch off upgrade option because I don’t want
The same problem occurs to me again.
My mistake at the first time is I mix up the method using manually method by reverendkjr
And on half way using script giving by sparkym3, so on the second attempt I only use
manually method by reverendkjr doing exactly what he is done and I get my KFHD rooted
I hope this will help you
NB
Even I uncheck automatic update they still updated my KFHD now I am with 7.21
and became unroot yes will start allover again.:fingers-crossed:

Related

Help please with soft unbrick, details in post

I had whatever, that updated to 7.3 as soon as I turned it on. Rooted fine with KF First Aide. Installed ES File Explorer, Google Play, etc. All was well. Then I read a post here how hard it was to copy/paste with ES File Explorer. I was joking about it with my husband and showing him how easy it was and copied random file... literally just randomly long pressed a file to show him the options, picked copy, and then went to another directory and *meant* to point to but touched paste instead... it was one of the Google Play files.
Kindle fire hd 7" immediately started freaking out. A mac address type error flashing so quick I couldn't do anything else. It was the same low letters and numbers you'd get with a mac address but said error and just an OK button which did nothing when you manage to tap in while flashing. Restarted, thinking if I was lucky Google Play just would't work... got the red triangle and neither option helped. So I ordered one of SkOrPn's cables which works flawlessly and boots right into fastboot. Yay for SkOrPn! Not so ya for me... (not their fault!).
It shows up as "Tate-PVT-08". I've tried every variation of driver I can find. Uninstalling all old things I can find, complete with the command line command to show ghost hubs/devices and what not and removing them and shut down/start up fresh too... no joy. Also removing and restarting between each driver try... neither of the Amazon drivers work for fastboot for me. I've tried so many things at this point my brain is fried.
So I'm hoping someone can help direct me how to fix this. . I won it in an online giveaway, so I'm not out anything, but it'd sure be nice to use it! As messed up as the Kindle crap is I'd be pissed if I bought it... but I'm majorly spoiled on Sony (Ericsson) and their "ya, play with it, screw it up, we don't care, here's how to fix it online just plug it in"... even before they had the online thing they'd let you send it back (and paid shipping both ways for it!) would reflash firmware and send it back with paper ticket that said "No problems found" lol... even on a device you actually bricked (wouldn't turn on... not the cute "brick"="I screwed it up but it's fixable" that people use now).
Any help or advice would be greatly appreciated. Especially if you could steer me to drivers that work for 2nd generation HD 7 inch in fastboot on Windows 8. Thanks for reading if nothing else!
Try The SoupKit found here.
This is a Kinology HD using XDA Premium
Swap cables. Boot with the factory cable then switch to a normal one.
Thanks for the reply, but I've been doing that. Great advice for anyone who doesn't know though!
You couldn't have damaged anything by just copying a file unless either:
You cut the file
OR
You overwrote a system file
OR
You filled up your system partition.
If you still need help, I might be able to do some researching.
Sent From my Kindle Fire HD running CM10.1
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Same Problem
I'm having the same problem! If you fixed it please let me know!
FIXED!!
It's fixed! You have to use KindleFireAide. Just follow all of the directions and it's perfect.:laugh::laugh::laugh::good::good::good:
Shawnsch said:
I'd say your fast boot driver didn't install right mine showed up like that and I had to keep playing with drivers to get it to work
Sent from my Amazon Kindle Fire HD running CM 10.1
Click to expand...
Click to collapse
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Deviantelf said:
Thanks, I was hoping there was a better answer than just keep uninstalling/reinstalling various drivers in various ways til it works lol.
I've got a pc I haven't plugged it in to I'll try this weekend, if that doesn't work I'll do the Linux Soup Kit.
Click to expand...
Click to collapse
Use Kindle Fire Aide. It comes with all of the drivers.
Geckodudes said:
Use Kindle Fire Aide. It comes with all of the drivers.
Click to expand...
Click to collapse
That was my first thing to try. Unfortunately one of them says stopped by user (preferred one) and the alternate won't install, gets to the end of installing and says didn't install, do manually... which has the same results. I'm getting the same results on another pc. Fun times lol.
Edit... I give up, it's Linux time. Will report back later.
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
I'll fix it for you...
Deviantelf said:
My husband did the Soup kit (correct version, followed directions, etc.) with it for me while I was at work today on an pc he put Linux on (so nothing phone/tablet/adb/driver has ever touched it for anything). He's more savvy with Linux, I haven't used it much since the 90s while he regularly has it as a dual boot on his main pc. He used Ubuntu, followed the Soupkit directions and still no Linux love either.
I'm pretty much down to just sending it back, worst case they send it back and tell me I'm screwed. Both of us are so spoiled on Sony (me) and Google/Nexus (him)... that this some things only works sometimes and just keep bashing your head into the wall and something you already tried three times will work thing is out of our frame of reference (which is what it took to get it rooted lol). I've already spent more time trying to fix the stupid thing for something that shouldn't have even caused an issue than I've spent on both my Sonys combined... even though I've borked both more than once... crazy.
My only advice ... buy a real tablet lol. Luckily I won this so I'm not out anything if Amazon won't swap it... but I really like the 7" size for book reading.
Click to expand...
Click to collapse
If you're gonna send it anywhere, if you pay for shipping I could try to fix it. No guarantees, of course.
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
KindleFireGuy said:
If you are on Windows 8 to install kfhd drivers you must advanced boot with unsigned drivers install mode active
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Ya did all that fun stuff, repeatedly with various drivers with all the 20 steps in between to remove others, lol.
Husband spent quite some time with Linux and SoupKit to no avail also. He could get his phone to work (making sure he had all the rules and steps correct), but it never would do anything with the tablet.
I gave up and called Amazon late Monday. They had me turn it on and verify the red triangle screen then sent me a new one that arrived today. Take the new one out of the box and put the old one in they said. They paid shipping both ways. If they complain I'll tell them send me the old and I'll send the new one back lol (at my expense). If they want to make the thing such a mess to deal with what do they expect? They know there's a whole group of people that won't live with the crappy launcher mess they have .

[Q] Odd shutoff issue...what to do?

Every so often my Kindle Fire 7 hd will shut off. Not reboot. It will completely turn itself off. It is very random. Sometimes it works for a while and the boom it happens. Doesn't seem to matter what I'm doing at the time. Sometimes it is when I unlock the screen...sometimes when the screen rotates...other times when I'm opening an app, or using an app.
There were times that after it would shut off I would turn it back on and it would almost be finished started up, but then turn itself off. I would have to plug it in in order for it to completely boot up.
One thing I've noticed is I don't seem to have any issues when the unit is plugged in. Could be just a coincidence though. The battery is 50%+ when this happens.
It started this about a week ago or so. At that point I had used KFFirstAide to put 7.2.3 on and was running Nova as my launcher. I thought it might be a ROM issue so I installed TWRP and put Kinology on it. Well, it is still happening.
So, it seems like I might have to make a call to Amazon (although I bought it Oct. 2012, so I doubt it is under warranty). I assume I will need to get the whole thing back to stock...unless someone here has a different suggestion).
Thanks for any insights/help you might be able to provide!
Dave.
I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app
@galearned is dealing with a similar issue regarding a KFHD7. I think the three of you should get together to try and find a common denominator.
Slangster said:
I have a similar issue where my Kindle now wants to shut down as I open the case????? This is a new problem and I've also noticed that the battery life is getting worse. Anyone else having these problems and got any ideas on how to fix?
Steve
Sent from my KFHD7 using xda app-developers app
Click to expand...
Click to collapse
Galearned here: I am running CM10.1 on my KFHD7 and do not have any shut down issues as far as I know but, regarding battery life, the unit is pretty bad compared to the KFHD8 also running cm10.1.
I traveled to Cleveland this last weekend and took my KFHD8 with me.
I used the KFHD8 the entire trip on the plane (several hours of fooling around and shopping on Ebay (free ebay on the plane).
I also used the KFHD8 both Saturday and Sunday extensively and Sunday evening, I checked the battery and it was down to 20%.
Until then, I did not plug in to any power supply.
I know for sure the KFHD7 would never had gotten that far.
One thing I have not checked is how quickly the battery drains on both units while doing the same tasks.
Most of the comparisons including the one I posted, indicate that while asleep, the KFHD continues to drain loosing several points over night.
If you leave the KFHD7 asleep for several days, the battery will be down to the 20% level or lower.
The KFHD8 will not loose more than a single point after several days setting asleep.
_________________________________
Update : CM 10.1 Deepsleep release 07/26/2013
Loaded this 07/26/2013 version last night on KFHD7 and configured wifi to be off while asleep as usual.
Tablet was fully charged at 11M and at 7AM still showed battery at %100%.
Very Very nice. Looks like Hashcode came through again............
So, you're saying the shutdown issue ceased after installing CM?
I have the same problem, running CM 10.1
I just flashed CM 10.1 a few days ago and just started to have these random shut offs... usually when the battery is around 60%. I thought it was the ROM, but seeing you guys have the same problem, I´m thinking there is something else involved. I never had those shut offs on stock.
Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved
Elgari said:
Well, exactly same problem with no apparent solution. I think the problem started when upgraded to 7.3.1. After that I disabled OTA, tried to uninstall all applications added by me, disabled all notifications, etc.. but the problem is not solved
Click to expand...
Click to collapse
Are you on Stock OS? If so, have you changed the Kindle's DPI? When I was on stock, I changed my DPI to 213 (same as Nexus 7) and started having random rebooting issues. Changing the DPI back to default (240) fixed the problem.
Just my two cents
Ph0enix_216;47286524 you on Stock OS? If so said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse
Elgari said:
Thank you for your post. I m on stock OS, but I dont know how to change DPI!!
Click to expand...
Click to collapse
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240
Ph0enix_216 said:
If you don't know, then I'm guessing that you never changed it, which means that it's probably not the problem. However, if you want to check, download ES File explorer from the Play Store, and navigate to "/system." There should be a file there called "build.prop." Open it, and look for this line (the value should be set at 240).
Code:
ro.sf.lcd_density=240
Click to expand...
Click to collapse
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!
Elgari said:
Thank you! I did what you said but, exactly as you anticipated, it was properly configured.
But the problem persists and I can not find any solution anywhere!
Click to expand...
Click to collapse
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.
Ph0enix_216 said:
You could reflash the entire system image. Download Kindle Fire First Aide (it's in the "General" section of this subforum) and follow the steps there. Once it's set up, select the option 3 (assuming that you have a KFHD), which will let you choose to restore to either the 7.2.3 or 7.2.1 OS. It says "fastboot," but I don't think you need a fastboot cable for it.
OR, if you have TWRP enabled, you can go here and download Amazon OS 7.4.6, but comes pre-rooted and has OTA updates disabled. Put this on your SD card, reboot into recovery, and wipe your current ROM and install this.
Click to expand...
Click to collapse
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!
Elgari said:
I already did the first option you mention, but did not solve the problem.
I will try with the second option. I do not know if I am able to make it!!
And yes, I have KFHD (and I make a factory cable).
Thanks again!
Click to expand...
Click to collapse
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.
Ph0enix_216 said:
If you tried the first option, and you're still experiencing the problem, then it might be something you're doing, such as installing a specific app or mod or something.
Click to expand...
Click to collapse
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.
Elgari said:
Yes, I think that too! In last month I uninstall all my apps one by one but I do not find the problem either!!
Did you think to have OTA disabled can cause the problem?
I hope tomorrow read To learn about TWRP and try with that.
Click to expand...
Click to collapse
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is
Ph0enix_216 said:
OTA shouldn't be the cause. Lots of people have had OTA disabled without any problems. Honestly, I have no clue what the problem is
Click to expand...
Click to collapse
Well, the problem the problem has worsened which led me to decide install TWRP.
I read about TWRP and second bootloader and try three times with Hashcode´s method but I cant do it. I´m very frustrated for my inability!!!
Thanks anyway for your help.
Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD
Krsmqn said:
Have any of you tried calibrating your battery?
Sent from my JellyBeer Fire HD
Click to expand...
Click to collapse
I tried to install TWRP but after three attempts I could not do it and bricked my KF. So I install everything new with KFFA. The bad news is that the problem continued. I'm starting to believe it's a battery problem and not a problem of the apps. Yesterday its worked all day (with tunein radio) without problem and just spent 20% of battery. But today when I wanted to put to work again made the same problem.
How can I calibrating the battery as you suggest? I think the problem is for this side.

[Q] Just asking for general advice after rooting

Dear members of XDA Forums:
So, a few days ago I decided to purchase an e-reader, because there are a lot of books in their original language that are almost impossible to get here in Argentina in physical format. I looked in a few stores, and the Kindle Fire HD 7 seemed fine. It had android, wifi, and some cool random stuff. Well, I purchased it, and was really glad after realizing that what I had in my hands could be turned into a fully functional (and pretty powerful) tablet, not just a reader. So I rooted it, installed a custom launcher, that kind of stuff, and everything went well.
I've been trying to investigate even further, but there are a few particular points to which I found no answer on the forums:
- Currently I'm using the latest version of the firmware (I think it was 7.4.1), and it seems pretty obvious after a quick look at the forums that no wallpaper can be set in that version because Amazon disabled them with a switch in the framework or something like that, and it can only be accesed by decompiling or using the custom script created by mr. stunts513; both of which seem too dangerous for me at this moment (I have absolutely no way of getting a factory cable if something goes wrong, and this thing was worth 2/5 of my monthly salary...)
Was there any update regarding this, or it remains in the same situation?
- At some point before rooting, I'm sure I updated my Kindle. But I've only had it for a few days, so a data wipe doesn't scare me yet. What will happen if I do a total factory restore? I mean, without using any app, just hitting the button in the settings menu. I guess it will unroot and all my apps and personal stuff will be erased, but what about the firmware? Will it remain in the latest I had before restoring (7.4.1) or will it go back to the one it had when I took it from the box?
- I've read several ways to block OTA updates, but there seem to be mixed sollutions for the K7 and the K8'9 in the same threads. Regarding my 7, I only changed the name of the .zip file that controls it (can't remember it's name now, it was in system/etc/security, I think). Will that be enough for a 7?
Thanks in advance, and best regards!
P.S.
Mr. stunts513, please do not take my commentary as a way to despise your work; quite the contrary, I'm grateful and would try it without a doubt if I was sure I could unbrick my Kindle if something goes wrong. But there is no way to be 100% sure, so for now I'd rather wait with a black desktop.
Ah No problem I completely understand, if you feel safe trying to install 2nd boot loader and twrp you won't need a fastboot cable if it bricks, but that has some risks of its own. Factory reset I think pretty much just wipes the data folder, maybe some of the system folder, so it doesn't restore the is to a previous version, least as far as I have ever heard. I can't really speak for everyone but I think renaming the ota certs zip file does the trick but I have heard mixed reviews on whether it does as of late or not, I'd wait for someone else to confirm that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[Q] Impossible to fix auto turn off

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

5.6 update bricked my Fire Tablet 7 5th Gen

Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.
CaptainPatterson said:
Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.
Click to expand...
Click to collapse
Yes - I have (indirectly) seen this on numerous unrooted Amazon Fire devices from several generations following a major OTA update. In most cases the device is NOT recoverable unless the bootloader is unlocked (not possible on 5th-7th gen devices). Boils down to a borked update which is not totally unexpected given the manner in which they are engineered and administered by Amazon. Clearly a very high percentage work without issue. Still sucks if you're a member of the substantial minority...regardless of size. You can try giving Amazon support a call...they might throw you a coupon that can be used against a future purchase (including deeply discounted Amazon/Fire devices during "Black Friday" week).
Just an update on this...
After a few days of not being able to use it I powered it on for the umpteenth time and it properly went through factory reset mode. I was able to manually download the 5.6 update again and it is finally back to normal. Funny thing is I now have even less internal storage than before but at least it is working now. That was a huge inconvenience and I still have no clue what happened.

Categories

Resources