Database Develop

Unable to root Kindle Fire HD

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:

[Q] Problems After Firmware Upgrade 7.4.6

Hi,
Yesterday, I carried out Firmware Update 7.4.6 to my 7" Kindle HD Fire and since then it has been behaving very strangely. Some of the symptoms of this strange behaviour are:-
1. when I open the current book I'm reading, after about 5 minutes of reading the book prematurely closes down and I'm returned to the Home Page Carousel.
2. When I open the book again I am not returned to the page I was on when it closed it self down, which means I have to scroll forwards to find the page I was reading when it closed down.
3. This premature close down happens on every occasion I open my book since the Firmware Upgrade.
4. On occasions, when it prematurely closes down and I re-open it, as well as not being on the page I was reading, but I also lose all my settings e.g. Font Size, Line Spacing and Margins.
I have tried Rebooting the Kindle e.g. holding the On/Off button down for 30 seconds and waiting for a reboot, but it doesn't automatically reboot, so I have to press on the On/Off button for the Kindle to start up again.
When it does restart, my books aren't visible on the Home Screen Carousel. I've connected my Kindle to my PC via the supplied USB cable and when I open Windows Explorer the Kindle is showing and all my books are in the Documents folder, then, after about 60 seconds of being connected to the PC, the books reappear on the Home Page Carousel of the Kindle
I open my book, start reading and the book prematurely closes down and the cycle begins again. I didn't have this problem before the Firmware Upgrade and an now wishing I hadn't bothered.
I am loathed to take all my books off and do a factory reset as that will take time, but if I have to I will.
Any advice on how to resolve this problem would be gratefully accepted.
Kind regards,

Eh I doubt a factory reset will help, I don't know if this will help you solve your problem, but if you are rooted I would look into reflashing the system image with kindle fire first aid, maybe clearing the cache and dalvik cache while your at it. From what I understand they don't have an image of the latest os, so it would be a downgrade, but I believe they left ota's active, so it should reupdate again on its own. If it happens to solve your problem on a previous os, and then when it updates again the bug comes back, then I would suggest just disabling ota's and sticking with an older os. I believe the kindle reader is a system app that they make changes to occasionally so it could just be a bug or something.
Note: this method should prevent u from losing any data, as it doesn't touch the data partition, though you may have to reregister the kindle again.
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

[Q] Kindle Fire 7" HD is stuck on the reboot

Good evening scholars, I am at a end with my Kindle Fire. Below is an
exact account of what I was doing and thus the end state of what is now my Kindle.
I have a rooted kindle. Basic root, nothing significant like CynMod. The boot-loader is stock and all. The only thing I really
installed that is not stock is a different Launcher since Amazon's Launcher is just horrid in my opinion.
I was in Rom Toolbox Pro uninstalling Chameleon Launcher because I wanted to run
Apex Launcher instead. So I uninstalled it. At this point there is no launcher running.
I'm using Rom Toolbox as a console so-to-speak. Simply going from one program to the next without actually ever hitting
the home button. So I go to install Apex Launcher and it says installing. However, it didn't do anything at all.
The status bar never moved; simply stayed at 0%. SO! No biggie, I've seen this before. So to make sure it is not Apex or something
I go to the stock Amazon Launcher. I had a backup and tried to install it through Rom Toolbox. Same thing happens,
No response, idle status bar, etc, etc. So at this point I assume it is Rom Toolbox. So I hit the home key on the slide menu.
Well, I have no launcher currently installed so it did nothing. Go figure. So I decide to do a hard reset. So I hold down the power button.The Kindle shuts off and then my troubles started. I hit the power button and it doesn't pass the Kindle is upgrading notice.
So I do another Hard reset adding insult to injury...but, the same thing again. Turn it off again, plug it in to my computer and attempt a fastboot with the stock cable, same results occurred.
So now my kindle shows the standard Kindle Fire Logo at the beginning of the boot cycle and then stops at the Kinde is upgrading...Starting Applications... prompt. Like the link to the photo below.
h ttp://i61.tinypic.com/2s0eeer.jp g
I try rectifying this, reading several articles.
I tried utilizing the Kindle Fire First Aid, the KFHD SRT, even looking into the android SDK a little. But they either - A. Don't recognize the device or, B. Prompts for superuser. Seeing as how my Kindle barely boots how can I check for a superuser prompt?
I go went into my device manager and looked to see if windows registers the Kindle and it does. The device manager displays Hardware ID's indicating something is there.
USB\VID_1949&PID_0007&MI_00
USB\VID_1949&PID_0007&REV_0216&MI_00
I have my hunches on what the problems could be. But I've been working this for a couple days now and have become agitated.
I have never had to many problems with this type of stuff. I won't say I'm a noob at this kind of work however, I feel like it at this point.
Worst comes to worst I would crack her open. But that is risky business. I rarely touch the inside of my devices.
Any words of wisdom are most appreciated.

If you happen to have adb access I'm guessing there's a system app that needs to be chmodd'ed to the right permissions, or if you want you could run "adb reboot bootloader" (and do what I mention next after it's in fastboot mode), however if you have no adb access then you will need to get a fastboot cable and restore with kfhd SRT or kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

As I said before the Kindle does not respond when I use KFHD SRT or the Aid Kit.

That's because for those tools to work you need to already be in fastboot mode with the fastboot drivers installed. Have you managed to get into fastboot mode?
Sent from my Amazon Kindle Fire HD using Tapatalk

As of now what you see is what you get. All I get is a never ending boot screen. I see you made a comment about fast-boot drivers. I might be missing something in the equation. I'm going to retrace my steps and start from scratch. Hopefully I will be able to get this thing working.

Well, I cannot get my Kindle to boot into fastboot. Tried reinstalling ADB drivers and everything. Even tried using the First Aid with no luck. I think the boot loader might be damaged. I keep the kindle off, plug it in, try to initiate a fastboot through the KFFA, it dims and continues normal boot operations. Stopping with the Kindle is upgrading notification.

Those commands aren't going to work unless adb was ever active in the first place, you are going to need a fastboot cable to fix it, the bootloader is behaving just as it should BTW, so it is fine, once you get a fastboot cable it will tell the device to enter fastboot when it powers on, from there kffa should work just fine outside of probably having to install Tue drivers because of how finicky it is. The ones in my signature will surface when the time comes.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

nook keeps waking up, killing battery

I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...

THRiLL KiLL said:
I am now on my second nook hd (upgraded from a 7" to a 10")
booth nooks have had the same issue, where i turn the screen off (sleep mode) and then for whatever reason the screen wakes up, (and the lock screen is shown) but it never goes back asleep and eventually kills the battery.
this behavior is random. and doesn't happen all the time.
Once i find the nook turned on, i can make it go back to "sleep" and it will mostly do that.
The nooks are on stock firmware, have most recent frimware and are not rooted.
the case that is used, is not a smart case.
the nook only has 2 applications installed. Astro file manager and bsplayer. using nova launcher
it is kept 99% in airplane mode.
this has been my only android device that doesnt turn off the screen when the lock screen is displayed. (on a side note this is also my only android device that is running stock firmware)
any ideas?
google hasnt been much help...
Click to expand...
Click to collapse
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.

sandsofmyst said:
When I had a problem with my original nook hd+, verygreen reminded me of trying the bn rom again.
Since your on the bn rom and its fully updated, I'm going to say for you to backup, then do a factory wipe and restore. After that, leave it as-is (no apps, as little setting changes as possible) and see what happens - no nova launcher either - basic and plain untouched. While your at it take away the case too. Perhaps its adding pressure or something else in some crazy way.
If that works then its a start.
If it doesn't then try cm on sdcard and see if it still happens. That way the bn rom could be ruled out.
Click to expand...
Click to collapse
thanks for the suggestions.
i finally had time to wipe and do what you suggested
figured out the case is what was waking it up, but i still had the issue of it never going back to sleep.
i installed go locker. and now its working as expected no more dead batteries.. i am happy!