Hi guys,
I've screwed up royally...
I got my Kindle Fire 2 (not HD) today and... tried to root it. Unsuccessfully.
It's now got a flickering Kindle Fire logo and it's responding with a 30 second to 1 minute lag (so unusable).
My Vista laptop still recognises it as an ADB device but I don't know what to do now
Can anyone help me please?
Many thanks.
EDIT: I've held the power button for 20+ seconds and it still does this...
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
433Mhz said:
Same thing happened to me today on my fire 2. Do a reset to factory settings in the device options. It'll takes some time to get there but it is no problem. Someone should warn people with recently purchased KFs about rooting. Doesn't seem to work anymore!
Click to expand...
Click to collapse
Thanks I'll try that and report back
It's beyond laggy though, so it's gonna be a pain
UPDATE: I love you 433Mhz It's worked, I wish I could give you a million thanks. I really hope Amazon reverse their stance on the locked bootloader with an OTA update, because that was all I wanted to start with haha.
Thanks again mate
Think I'm bricked
The root process went perfectly clean and it rebooted fine. Then I couldn't find instructions to install the Play Store. I finally found some that said to copy GoogleServicesFramework.apk to the Kindle and install, I did that cleanly. Then to copy vending.apk to /system/app/ and I did that and was able to change permissions to 664. I then rebooted the Kindle. It goes straight to the triangle. If you push the power button 5 times it reboots to the same thing. I did not try to flash TWRP to it because I saw some having problems with it. I have 10.2.1 on it. I have the proper drivers installed and each time the Kindle rebooted during boot the computer beeped that it recognized it. Since the triangle the PC no longer recognizes it, it does not show up in Device manager and it does not show up in explorer as connected. I think it is hard bricked but wanted to run it by everyone.
Sparkym3's root process went flawlessly on my Fire2, It only took a couple minutes to root and be booted to a working Kindle. I just screwed up the market process somehow.
Let me know your thoughts. Being that everything went so clean with rooting I have a hard time thinking it can be the drivers, cable, usb port.
I've rooted a phone and 2 tablets multiple times but never had this happen. Any help is greatly appreciated.
This is an exact description of the problem:
I get the Kindle Fire logo, sits there several seconds, reboots and the power light goes out and back on, then the logo comes up again, it flashes a couple of times then I get an orange triangle with an exclamation point inside Below that is a message stating "Your Kindle device cannot boot".
Below that is You can reset device to Factory defaults to fix this issue (all data will be deleted from the device"
<Menu options>
To reboot your device, press and hold the power button for 4 seconds and release.
To reset to Factory Defaults, press the power button 5 times in succession.
Well the 4 second thing does not work at all, more like 20 seconds. The pressing 5 times just reboots to the same problem and warning triangle. I tried fastboot commands but nothing.and my laptop no longer recognizes the Kindle and nothing is in Device Manager about the Kindle now. The fastboot command just says waiting for device. As I said above the root process went flawlessly and the Fire reboot 3-4 times and the laptop beeped each time that it saw it.
Any help is greatly appreciated
So, I'm totally lost. Maybe a frisbee at this point.
http://forum.xda-developers.com/showthread.php?p=33156486
Trys this
Sent from my SAMSUNG-SGH-T989 using xda premium
---------- Post added at 08:02 PM ---------- Previous post was at 07:58 PM ----------
Ops wrong link srry tthast for the hd :banghead:
Sent from my SAMSUNG-SGH-T989 using xda premium
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
That kindle is hard bricked, there's a slight chance of fixing if it is flashing fastboot mode for a few seconds, but I give it a 10% chance of fixing. We can't fix omap4440 bricks because while we have the means to interface with that device, we need a signed xloader for the kindle to let us flash the other partitions. We can't get the signed xloader (believe its called xloader, might be called something else) unless someone at amazon or TI were nice enough to leak it and probably get fired in the process.
On another note is that android adb composite device staying there the entire time the kindle is plugged in? If it does then you may be able to fix the kindle, I haven't heard of omap4440 and the adb composite being there at the same before. I would guess that adb is the fastboot interface but usually it says Tate when drivers aren't installed and in this case it doesn't but still has an exclamation. I'm curious....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I wouldn't say 100% out of hope...
http://forum.xda-developers.com/showthread.php?t=2391047
Or you could try using "fastboot boot" to boot the bootloader. This takes barely less time so if the fastboot flash fails, try this.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Same exact problem, did anyone find a fix?
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Steveohookem said:
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Click to expand...
Click to collapse
When you remove your OS off any device without one to install, its like giving someone a car with no steering wheel. You now need to push a ROM thru TWRP using ADB. Try using the solution that helped me, which I provided to another user in this thread:
http://forum.xda-developers.com/showthread.php?p=45188927#post45188927
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 06:10 AM ---------- Previous post was at 05:56 AM ----------
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
Creepy never seen that happen on either of my two KFHD7s. Have you tried uninstalling that driver completely? Or uninstalling those drivers thru "Device Manager" AND all others installed for /example the ones provided by Hashcode, then reinstalling them WITH the device still connected? Many times I've realized that these Kindle Fires love to have drivers juggled around. The fastboot cable I made at home using a Samsung USB does FBmode instantly. Try holding the power button for about 20 seconds while unplugged, make sure when you let go it doesn't power back on. If alls well, have the fastboot cable plugged in already to your computer, then attach it to the KF. See if that helps. If not, then believe it or not it might be a hardware failure if the screen goes black as you mentioned...
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
My bad the picture must have not loaded up last time, or I wouldn't have said that much. But more than likely he has a hard brick. Slim chance of fixing it though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
hi guys from Italy, i have the same very problem...now is the end of Settember....any good news about?????????
Not very much, unless you wanna try hooking up your emmc to a USB card reader like kurohyou did and trying to flash the stock partitions from Linux, no there really isn't any new news. That's basically the only way we have to recover from a hard brick, and it still isntna perfected process, he got his kf2 to a soft brick state after un-hardbricking it, but he couldn't un-softbrick it yet, so he is currently working on that part last I heard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Juls69 said:
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Click to expand...
Click to collapse
i think someone finished mapping the rest of the points out on the motherboard but i'm not positive, I'll have to find the thread but the only fix is to solder the kindles motherboard contact point for the emmc to a sdcard reader and hook it up to a pc running linux and flash the bootloader partition with the dd command. Keep in mind I'm referring to the hd 7 2012 model, i don't believe anyone has mapped the points for the 2013 model yet.
edit: foudn the thread: http://forum.xda-developers.com/showthread.php?t=2674737&page=3
use the tutorial for the kf2 or kfhd8.9" but use the contact points mentioned there, might take some researching to know what each of those corresponds to on the sdcard reader. Not everybody is up to soldering on their kindle to fix a hard brick.
Hello,
i found these Thread, because i have the same problems.During the boot the kindle shows the kindle logo then the fastboot logo and the screen goes black. But if use a fastboot-code at the right time, the kindle stay in the fastboot-mode. So i tried to flash the Bootloader and so from Hashwell. The output of fastboot says everythings ok, no errors, but my kindle doesn't leave the bootloop. What i done wrong? I read about the Kindle Fire First Aide-Kit, but i cant find an downloadlink, that still work.
Maybe someone of you can help with this problem.
Hi this is my problem nephew got kindle fire hd 7 for xmas stupid idea hes only 11 anyway he has put a pin in to the tablet and now has forgotten it when you boot it up all it does is ask for a pin there is no way of getting in to it,how can I get in to this tablet I have some idea of what im doing rooted tablets before so I know how to use adb,now adb see the device gives me a number but I tried to use KFFirstAide to restore the kindle but the programme isn't working as its telling me adb is not working ive looked in to hacking the pin to get into it but from what I have read and watched online its saying you need to have adb working but yet I don't think its enabled on the tablet does anyone know of a back door like on android when you holed the volume down you get the dead droid then you can go to option of restore or is there another way to get into this tablet its brand new never been played with just pin put into it and now cant get into it anyone guide me or help me please proper head scratching happening at the momement thanks in advance
I thought if you typed the pin in wrong enough times it would give you the option to restore factory defaults. If adb wasn't on then I don't see you turning it on externally. If it doesn't present you with a way to format it then I suggest getting a fastboot cable and using fastboot mode to clear the userdata, that would probably do the trick.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
ok will look into this cable thx,and still look to see if there is a way to get this sorted in the mean time thx
I have a friend that wants me to fix their Kindle Fire 7 HD, it is NOT the tate model that would easily allow me to unlock bootloader and "fix" it. The tablet automatically reboots a few seconds or minutes (it varies) after it initially powers on. I try to factory reset with no change to anything, I don't think it's actually resetting it.
That model is the kfowsi. Google for that. I think there is a tool that loads a stock system image.
tjustice86 said:
I have a friend that wants me to fix their Kindle Fire 7 HD, it is NOT the tate model that would easily allow me to unlock bootloader and "fix" it. The tablet automatically reboots a few seconds or minutes (it varies) after it initially powers on. I try to factory reset with no change to anything, I don't think it's actually resetting it.
Click to expand...
Click to collapse
see [Help Thread][Kindle Fire HD] 3rd Gen/2013 Ask Any Question, Noob Friendly
http://forum.xda-developers.com/kin...p/help-thread-question-noob-friendly-t3206681
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
navtis123 said:
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
Click to expand...
Click to collapse
I would not spend time trying to debug the WiFi issue. Given you have root + ADB access recover whatever personal files you need and then reload FireOS (preferably 5.1.2; 5.3.1 will also work) from the stock recovery menu. Fixing radio issues is akin to tossing sawdust in the transmission. It will likely come back to bite you later.
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
navtis123 said:
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Click to expand...
Click to collapse
navtis123 said:
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
Click to expand...
Click to collapse
Rolling back to stock eliminated many possibilities and suggests the likely root case is hardware based assuming you (or Amazon) did not install/update any apps after restoring 5.1.2. Possible one of the chips is overheating triggering a boot loop. If the device is still in warranty Amazon will exchange it. If not you can attempt to load FireOS 5.3.1 (latest rootable version). Given the symptoms that should not make a difference but you have nothing to loose. Just don't go lower than 5.1.2 as device will brick.
Also try moving to a different location (friends house, coffee shop, etc) to see if the AP makes a difference. Not common but certain multi-band APs have been known to trigger device instability.