Related
I have a conglomeration of issues with my Kindle Fire HD 7. I'm currently in the process of ordering a factory cable from SkOrPn, but wanted to make sure there are no other avenues for me to attempt.
I'm very noob here, so bear with me. I've searched around, and attempted all the fixes that I've found, but for some reason, none are working.
My KFHD7 is currently stuck at the boot logo, non-animated. It came back to my company this way, so I'm not sure exactly what the person that had it before me was attempting to do with it. If I plug it into my PC, with Windows 8 Pro, I do NOT hear anything that tells me that the computer recognizes that the device is connected. I also do NOT see the device in the Device Manager. I attempt to install the drivers from the KFU, but for some reason, those fail every time.
I've installed Ubuntu, to attempt Soupkit, and Firekit. It isn't detected there, either.
Do I have any other options, or is a factory cable the way to go? Also, if/when I order the factory cable, will my computer then be able to detect the KFHD7?
I'm sorry if this question has been answered a hundred times already, but after searching for 3 days, and attempting everything I saw, I've reached the end of my rope.
Boot into the Ubuntu that you have SoupKit installed (will eliminate Windows driver problems), open a terminal and enter the following:
Code:
fastboot -i 0x1949 getvar product
Then reboot (hold power button for 10 seconds) when you see "waiting for device". That will get you into fastboot. From there you can flash a system.img and restore your device. Onemelia has a system.img restore tool in the HD7 dev forum that has a system image included so check it out.
[Edit:] Considering you don't know exactly what was done to the device, you should probably restore the stock recovery and boot partitions too. I've had situations where I've installed Hashcode's stack override, along with the custom boot and recovery images and my device acted the same way. Since the stack is on the system partition, overwriting it with a new system partition and leaving the custom boot and recovery partitions in place would presumably put the device in a hard bricked state, from which there is no recovery.
Will it be a problem that I have Ubuntu 12.10 installed, rather than 12.04 that you reference? Maybe that was half of my issue there.
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
honberiz said:
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
Click to expand...
Click to collapse
Get the cable. It's worth way more then the price. After you get it, check out the first aide link in my signature. Good Luck!
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
honberiz said:
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
Click to expand...
Click to collapse
Onemelia's system.img restore tool in the development section has a system image...I'm not sure about the boot and recovery images though. If not, PM me and I'll send you copies.
As far as which version of Ubuntu, it shouldn't matter. The key packages are 'dpkg' which comes with all Debian based distros that I know of, and 'apt-get' which comes standard on all Ubuntu based distros I believe, so you should be fine either way. If you're using a 64bit install, I'd suggest you switch to a 32bit install. And make sure you aren't using a USB 3.0 port. As a matter of fact, you should probably switch to a dedicated usb port rather than a hub. A good way to check to see if Linux can even see your device is with the 'lsusb' command...you should see a device called "Lab 126".
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Well, if you can get into recovery, that's a good thing.
I had this problem a couple of days ago. I had tried to revert from Chameleon OS back to the stock OS by flashing Haschode's stock OS zip, which resulted in the issue you described. I fixed it by restoring from a back up of ChaOS o had made, and it got me out of TWRP.
You could try re-flashing Hashcode's stock OS (it comes pre-rooted). It can be found here: http://forum.xda-developers.com/showthread.php?t=2218475
To move it on to your SD card, go to "Advanced" in TWRP and select "ADB Sideload," or something to that effect. Then from your PC, use a command window and enter "adb sideload name\of\zip.zip"
I don't remember if you have to wipe anything or not before you flash it
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Aaron Belle said:
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Click to expand...
Click to collapse
Lol same thing happened to me when I flashed TWRP and 2nd BL. So basically, your in a boot loop. Don't worry you didn't do anything wrong, its just that the stock Kindle OS now hates us because we modified something. So here's what's gonna need to be done. You have TWRP, your all set to flash anything you want! But, you have no custom rom in there correct? My same mistake. Those are all easy fixes, the problem is playing with the KFHD7 drivers on your computer to detect your device 100% while its connected and on TWRP. I can't remember how I got mine to detect it, if I'm not mistaking I unisntalled ALL associated drivers, then reinstalled the ones provided for the rooting process WITH THE DEVICE STILL CONNECTED, then manually updating the driver to those installed drivers in C:/Program Files/Amazon/Kindle Fire. Once its installed, you would need to check by opening a command prompt with ADB, then check for devices by typing "ADB getdevices" if I'm not mistaking and see if some serial numbers show up. Then push the files thru ADB. If you wanna cheat your way thru ADB cause you don't know how to use it properly, do what I used to do. Download the Nexus 7 toolkit, install it, go to the folder where installed and create a shortcut for "tkmain.exe" to your desktop. Then open that and a green text command looking menu is in your view. If serials appear on the top, device is detected thru TWRP. If not keep playing with installing the drivers while in TWRP and refresh the green menu by using option 27 (type 27, then hit enter). Once those serials show up, download the custom ROM you want your mom to have. I recommend CM10.1 as its a small file, stabler than CM10.2, and its basically jellybean. Remember the folder where the Nexus 7 Toolkit was installed, where I first mentioned to make a shortcut for tkmain? Go back to that folder and look for a folder called "put files to push here". Throw the ROM there. Rename the ROM something short and with few or no symbols. When that's done, your ready to push it. Go to the wonderful green menu thingy, type 13 and hit enter. Then it will have two options. Type 2, hit enter. It will ask if your using an insecure bla bla bla. Type yes, hit enter. Then it should show the name of the ROM you threw in the folder, type it out exactly as spelled, hit enter. Push to /sdcard/. Some crap will appear and say "remount failed: Success" ignore that, don't panic, that's good. For a while nothing will show, but afterwards words should appear confirming the push, and Two last questions your gonna type no to. Now your ready to bring moms new device back to life! If you know how to flash a rom, do it. If not, swipe to wipe dalvik cache in Wipe menu, go back, Install > search SD card for your file and flash. Tada! You should see CM logo after the blue Kindle Fire logo and wait til the screen dims more or less, that means your a few seconds away from getting to touch. Remember to start it up, then flash GAPPS so mom can have Google Play, I'm sure she's gonna love Candy Crush Saga as mine does.
Sent from my Amazon Kindle Fire HD using xda app-developers app
May uestnl
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jeanphi506 said:
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
Click to expand...
Click to collapse
Try the solution I mentioned above you. I'm no rocket scientist, or an android expert, just picked up a thing or two from experience. If I can do it you can as well. That's why I mentioned the toolkit I used. It may be for the Nexus 7 but it does the same adb commands used for all androids for you. That way if your not an adb expert you can use that. As I said, your first goal is to get your computer to properly detect the device while in TWRP, your stock kindle OS is just doing what it does best when simple modifications are done.
Lost access to stock amazon
stunts513 said:
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
jeanphi506 said:
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
Click to expand...
Click to collapse
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
How to get to the original OS after installing TWRP.
Crossvxm said:
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
Click to expand...
Click to collapse
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
jeanphi506 said:
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
Click to expand...
Click to collapse
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Reinstalling stock OS
Crossvxm said:
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Click to expand...
Click to collapse
Coming back to give you some news.
I was not able to use the following link, as it was not on my Kindle and I was not able to have the kindle recognized by the computer.
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason."
I decided to use he backup I made and I used the following command, with the factory cable:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
It worked and I have a working device, but without TWRP, 2nd boot loader.
I suppose I could have flashed directly the Amazon OS System mentionned earlier, but I was not exactly sure which command to use.
So, I will to try again to install TWRP, 2nd bootloader.
Thank you very much for your help. I will read again your answers to try to use them in the future.
Jeanphi
Completely fixed! Thanks!!
Download the Nexus 7 toolkit said:
I cant tell you how much of a life saver this was....this works 100% !! Just follow his instructions to a tee and this will save a lot of time and effort trying to get our TWRP loop!
Click to expand...
Click to collapse
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Nikaroo said:
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Click to expand...
Click to collapse
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
soupmagnet said:
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
Click to expand...
Click to collapse
Thanks for the pointer - I think it got me a tiny bit further. After finding the package and 'fixing' drivers - woo-hoo - my computer is saying that the device is working properly now, I can see it as 'Kindle Fire' in my device manager. However, it still is showing up as 'Tate-PVT-08' under Devices and Printers, and it cannot be found (isn't communicating) with ADB. I feel like I'm missing something so small to be able to move forward and reflash this thing - it's so incredibly frustrating to not be able to find it. :/
I also have tried editing the adb usb file to include the 0x1949, having gone through the adb kill/start-server commands several times, which hasn't changed anything. Is there anything I am missing to get windows and adb to communicate with it? Or is my only option at this point trying 'non-Windows based options'?
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Click to expand...
Click to collapse
Sooo, I feel even stupider now. I do have KFFA, so I tried to reflash the system image. It went through and gave me a success, although it did have an issue with erasing user data and cache. It said to disconnect from the computer/usb and power down, then restart. I did that and was super hopeful - it went through the boot screen a few more times than normal... but then BAM. Right back to the Kindle Fire System Recovery screen that it can't get past. Ugh. I must have really screwed something up on it.
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here. Going through that, I checked my hardware IDs, and one of the numbers are off, which according to the guide means that my Kindle isn't in fastboot mode (and this is while using the fastboot cable). If I use a regular USB cable, it doesn't show up at all anywhere. The more I research, the more confused I get. Everything seems geared towards fixing your device if it is stuck in a bootloop (mine goes through that and sticks at the recovery screen) or being able to get it into fastboot, which I cannot seem to do even with the cable. I guess I'm going to try to uninstall and reinstall the drivers for it again, but I'm starting to believe that whatever value I changed while in super user mode before my problems began are going to make it impossible to fix...
The hardware I'd should be 0x1949, and at this point I'm guessing maybe something is wrong with something in the data partition or you have a bad kernel. I don't know how to wipe the data partition from fastboot though. I don't know if kffa reflashes the boot partition, but you could always try that since a system reflash didn't work, or you could try reflashing the system image again, there's another tool in the android development section called kindle fire system restore tool, maybe it will work better for you. Here's the other tool: http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part about that adb command, that's only for of your kindle can actually boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Nikaroo said:
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here.
Click to expand...
Click to collapse
Be very careful of what guides you use around here. Some of them (fastboot guide in particular) are made with the original Kindle Fires in mind, and can lead you to do irreversible damage.
I'll try that in the morning... I spent most of my day at this and need a break! Thank you so much for trying to help me out. I really appreciate any and all pointers.
Dear members of XDA,
first of all, sorry if this question already has been asked, but for some reason the search tool wouldn't work for me tonight.
Yesterday I succesfully installed CyanogenMod on a friend's 1st gen Kindle, and it was pretty easy - make sure that the drivers are ok, install TWRP, copy rom, wipe, install, done.
My Kindle 7' HD is rooted, and very modified, but I didn't want to try to mess with roms because I didn't had a factory cable. Well, I got one now, so the time has come.
I've checked Hashtag's post about the 2nd bootloader, and altought it is very helpful, I'm not sure if I'm ready to do all that stuff manually.
So, my question is this:
The KFFA has an option to install the 2nd bootloader + TWRP (option 39), and it itself states that it's the same process that can be found on Hashtag's post. Let's say I run that option, and all that is installed - what next? I just copy the rom and gapps to my device, use TWRP to wipe the stock rom, and install the new one? Just like that?
Any help will be much appreciated.
Thanks in advance, and best regards -
I suggest putting the ROM onto the kindle ahead of time along with its corresponding gapps, the latest is tends to boot loop into twrp after you flash second boot loader and twrp. You can still push them to the device even if that happens, but it tends to be more inconvenient.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I managed to install TWRP without breaking anything (altought not with KFFA but with FireFlash). I copied the CM rom and gapps, and wiped the stock OS... Only to find that I copied the wrong rom (I used the otter2 project, not the one modified by Hashcode).
No big deal, I tought, let's just copy the other rom and install it. The fact is that there is no way to make my computer recognize my kindle now. I have the latest version of ADB installed, I can get to TWRP screen without problems, but it always has a yellow marker on the device manager, and when I tipe "adb devices", nothing is listed.
Any tips?
Reinstalled some drivers, now the Kindle appears when I input "adb devices", even if it appears as an "android phone" on the device manager (without any yellow markers).
I can access TWRP and fastboot via the factory cable, but don't know how to continue from there. I want to copy Hashcode's ROM in order to flash it, but cannot find a way. I've read somewhere that it has to be sideloaded, I tried that before reinstalling the drivers, and it didn't work. Now I cannot find that procedure again.
In a 1st gen kindle I remember I could just transfer files via normal folders on windows, as long as I mount it using TWRP. Here on mine, even if I use TWRP's option to mount, nothing happens.
Solved!
Used this guide:
http://forum.xda-developers.com/showthread.php?t=2459498
Thanks once again, mr. Stunts!
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.