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
Related
Hello.
After hours of struggling and Googling (and reading mostly from this forum) I managed to root my KFHD 7.4.6 using bin4ry method. I have two questions about where I'm at right now.
Question 1: While struggling to get adb to recognize my KF, I realized that the problem was quite simple: after installing the special adb drivers, I would plug the Kindle back in and Windows would recognize the device and install the Microsoft drivers - completely ignoring the driver I had just installed. The only way I managed to get around this was to quickly interrupt Windows 7's driver installation and tell it to NOT install drivers from Windows Update.
However, I'm sure there must have been a more elegant way of accomplishing this. What would have been the correct way to do this?
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Thanks! :good:
SpidaFly said:
Question 2: Now that adb finally recognizes the KF, and the KF shows up as "Android Composite ADB Interface" in device manager, I want to put Android 4.2.2 on the KF - so CM 10.1. I'm doing preparatory research so I can learn about what I need to do. The big concern for me now is that my KF version is 7.4.6. There seems to be relatively little information about this, and I've seen it explicitly indicated in a few places that only versions before 7.3.something have the exploit available. Does this mean I must first downgrade from 7.4.6? I've had trouble pinning resources down that would help me answer this question - so if anyone has any solid tips about this, I'd appreciate it! I'd really rather not brick it :silly:
Click to expand...
Click to collapse
I just found this:
http://forum.xda-developers.com/showthread.php?t=2271909
So the answer to my question appears to be "YES", correct? It appears that I need to flash back to 7.2.3?
Question 1 still remains unsolved.
Well you could downgrade it, I don't know if the latest update causes problems, but the thing that needs downgrading isn't the os, its the bootloader. I suggest the fireflash method in seokhuns tutorial, the one you linked. Just make sure to check the first box at the top in fire flash or you will have a red screen brick, which requires a fastboot cable to fix. Also I have never heard of windows update having drivers for the kindle, I mean I usually hit skip anyways, I believe the more elegant solution may have come with kindle fire first aid, not positive though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks!
I'm having another little inconsistency now.
I disconnect and power off my KF.
I run in cmd: fastboot -i 0x1949 getvar product
It says < waiting for device >
I then plug in my (powered off) KF, and it boots up NORMALLY, and fastboot doesn't return the expected tate-xxx.
Any ideas why?
My ADB is seeing the device. (ie. adb devices is returning one device).
Your fastboot drivers aren't working.
soupmagnet said:
Your fastboot drivers aren't working.
Click to expand...
Click to collapse
Indeed. Can this be solved by wiping existing drivers and reinstalling Amazon's USB drivers from sdk/extras/amazon ?
EDIT: I've attempted reinstall twice with no improvement. ADB works, fastboot won't.
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Um I thought that command only worked on a 8.9" kindle to get it into fastboot.try this instead:
Adb shell su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
SpidaFly said:
Interesting. I tested that. adb shell su -c "reboot bootloader" does indeed put my device in fastboot mode, and fastboot -i 0x1949 reboot takes it out.
Interesting. Seokhun's tutorial seems to indicate that fastboot -i 0x1949 getvar product should do it as well... so it seems that my fastboot drivers are... kinda half working? Or something?
Click to expand...
Click to collapse
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
soupmagnet said:
That option may have been removed in later versions of the bootloader. Some have had success with it while others apparently haven't. If the reboot command works, your drivers should be working properly.
Click to expand...
Click to collapse
Sounds good, thanks. I'm following that tutorial even though it's for 7.4.3, and I'm on 7.4.6. I hope that doesn't cause any issues - but 7.4.6 looks like it's pretty new, so I don't see other options.
Ok - I've followed the aforementioned tutorial precisely up to step 4. When I try to boot the kindle up, it shows orange logo, then blue logo, then looks like it's trying to boot normally, then sends me into TWRP.
Is this what is called "boot loop"?
At this point my PC doesn't see the sdcard so I can't get CM/Gapp copied over.
Would it be safe to push CM & Gapp to the sdcard using adb, then resume with TWRP?
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
SpidaFly said:
EDIT: Still can't boot into the system. Just sideloaded CM 10.1 ROM onto the sdcard. Safe to continue with Step 4, wipe stuff, and install the CM rom?
Click to expand...
Click to collapse
This ended up working.
However, now with CM 10.1, my PC isn't recognizing the device for MTP. It still does recognize it as an ADB device, but ADB doesn't see it.
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Odd that MTP isn't working, u can always switch to pptp mode if that helps, but everything goes to the dcim folder on the sdcard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Got it working. Basically just uninstalled the existing drivers and reinstalled standard drivers. Works like a charm. I love CM, this is great! Thanks all, for the help!
I'll worry about getting adb going again later.
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Try my tutorial, I have been seeing this a lot lately, it just has to do with with something amazon did to their os.
http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jonnyc1003 said:
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
I think in twerp, you can mount usb
sent fro my rooted kindle fire hd 7 with twerp and kinology rom installed
You need to flash a custom ROM to boot. I really think the development or Q&A section should have a sticky regarding this issue, or at least Hashcode make note of it in his how-to guide on 2nd bootloader and recovery.
Sent from my MB886 using xda app-developers app
Thanks all. Stunts513, I'm trying it now, I'll let you know.
So there is no device with an issue in my device manager, I see Kindle Fire and under that is Android ADB Interface. But, when I do "adb push ..." all I see is the same thing as if I just type "adb" and the file doesn't transfer. Sorry, I'm a noob.
When typing adb push, it displays the help text? Type adb devices and see if it lists it, also make sure your command prompt is being run as admin, I probably should mention that in the tutorial, because I use windows 7 with uac disabled so I don't have to worry about that kinda stuff.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jonnyc1003 said:
So I'm trying to flash CM 10.1 onto my KFHD 7, and I've installed TWRP. Now when I try to boot up so I can move the ROM onto the device storage, it won't fully boot. I get the regular Kindle fire logo, then the blue one, then the flashing one as normal, but then it flashes, goes back the the first, then the blue, and finally opens TWRP. In TWRP, I can't get the device to mount so I can see it on my computer, so I'm not sure how to get the ROM onto the device to flash. Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
My advice is to go to the Kindle Fire FirstAide thread on here. Run KFFA back to 7.2.3 and root from that simple script. Then use Hashcode's 7.2.3 bootimg and the TWRP he has on his thread. This way you have matching bootimg and you should not bootloop.
I would put the rom you're going to flash on the root of the SD card before flashing first as well. If you do bootloop, you can flash the rom anyway and save some hassle.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers app
So my device shows up as "0123456789abcdef recovery" or something along those lines. Is this right (the ordered numbers and letters look kind of funny)? Also, I am an admin, so that can't be the problem.
OK that's good that is how the device is supposed to show up. If it displayed the help text last time I'm guessing there was a typo in the adb push command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
If you get frustrated or simply can't get ADB Sideload or ADB push to work, you may have to go into "Advanced", then "Reboot Bootloader" in TWRP and use KF First Aide to flash to 7.2.3 stock. From there, repeat the process of installing TWRP and Second Bootloader but put a custom ROM on your SD card before the procedure. Your fastboot drivers might not work, I know Stunts513 has drivers you can install.
Sent from my MB886 using xda app-developers app
Ok so when I wrote that, it was showing up when I typed "adb device," but it wouldn't push. I tried again today, triple checking my typing, but now it doesn't show up on "adb device," just the help menu. I just uninstalled and reinstalled the drivers with no luck.
Ok so I finally figured out the issue, it's really kind of silly. In your tutorial Stunt513, you show the push command like this:
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
All I had to do was replace the forward slash between the file name and 'sdcard' with a space. Problem solved. Thanks again for helping out!
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!
Q&A for KFHD System.img Restore Tool- Updated links 5/15/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for KFHD System.img Restore Tool- Updated links 5/15/14. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
couldn't even get passed 1st step
onemeila said:
KINDLE FIRE HD ONLY!!! USE AT YOUR OWN RISK!!
I put together this tool for those that have tried to modify their system unsuccessfully and bricked their device. You must be able to get your device into fastboot for this to work. The easiest way is to purchase a factory cable or make your own(a $15 purchase or a little bit of your time is better than a bricked device).
The .img's in this tool were made from a rooted device w/ the su binary in place. There is no need to re-root your device, however if you choose to erase cache and user data(not necessary but may be a good idea) you will need to re-install Superuser.apk to gain root.
Instructions:
1.) Download the version you want to use from the link below and unzip.
2.) Enable fastboot mode. Turn off your device then plug into your pc using a factory cable. If the device is recognized by adb then you can use this command:
Code:
adb shell su -c "reboot bootloader"
3.) Run the SR Tool.bat and follow the instructions. If you wish to downgrade system versions see instructions at the bottom of the post.
Downloads:
KFHD_SRT_v1.3.5- 7.3.0 (seperate option for restoring factory recovery)
KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)
KFHD_SRT_v1.2.3- 7.2.3
KFHD_SRT_v1.2- 7.2.1
KFHD_SRT_v1.0- 7.1.5
I apologize for the size of this tool. The .img files used are rather large. If you want to use your own backup .img then download the lastest version of this tool from here. Just place your system.img inside images folder. It must be named system for option 1 or system2 for option 2
UPDATES:
4/20/13
-separate option to restore factory recovery and boot now on v1.3.0
4/17/13
-KFHD_SRT_v1.3.5
-flashing boot and recovery images now a separate option
3/21/13
-KFHD_SRT_v1.3.0
-boot and recovery images inlcuded
-SuperSU and GoogleServicesFramework now included as system apk's
12/22/12
-KFHD_SRT_v1.2.3
-System v7.2.3
-New option for installing Googleservicesframework.apk
12/17/12
-downgrade method instructions(confirmed)
12/1/12
-KFHD_SRT_v1.2
-new system partition backups for software v7.2.1
-vending.apk to phonesky.apk for newest version of play store
Instructions for downgrading to 7.2.1:
1.) Download boot and recovery imgs(these are backus from 7.2.1) from this LINK and place in the folder where you have access to fastboot or inside the KFHD_SRTool_v1.2 folder
2.) Use KFHD_SRTool_v1.2 to flash system.img.
3.) Erase userdata and cache
4.) Open a cmd prompt from the folder where you placed the previously downloaded .img's.
Use these cmds:
Code:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
5- Reboot.
Those who deserve our thanks:
kinfauns for the how to on backing up and restoring system software.
bazm60 for confirming the method above works.
hellocali626 for bringing to my attention the need to flash boot and recovery images for downgrade.
Click to expand...
Click to collapse
My kindle fire hd is just staying on the beginning fastboot screen. my computer doesn't recognize it or anything. i think i accidentally deleted almost everything on it including the whole OS by using TWRP, so if someone could help it would be greatly appreciated.
cheezer4998 said:
My kindle fire hd is just staying on the beginning fastboot screen. my computer doesn't recognize it or anything. i think i accidentally deleted almost everything on it including the whole OS by using TWRP, so if someone could help it would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you need to install the correct drivers. Download and install the driver from this link:
http://forum.xda-developers.com/showthread.php?t=1890413
If that still doesnt work follow the directions from this one:
http://android.stackexchange.com/questions/48023/fastboot-not-working-for-kindle-fire-hd
My Kindle lost root.. So I downloaded and installed a super user... not sure what version off hand...
But its still not rooted.
I originally chose the option for the factory restore with root, Google Play Store, and the launcher.. And it was rooted for a couple of days.. I'm not sure if it lost root during reboot or not.
On a side note, it also no longer allows me to access storage through my PC. So I've been having to download everything straight to the Kindle.. Not sure if that matters... But I can't back it up because I can't save the backup files to my PC..
Any suggestions? Do I need to clear cache and dalvik for superuser to work? I've been hesitant to go into recovery mode..
Did it auto update to 7.5.1? That would explain why you lost root.
Red_81 said:
Did it auto update to 7.5.1? That would explain why you lost root.
Click to expand...
Click to collapse
Yes! Can I downgrade? And how to stop the update?
Or better yet I'll poke around to see about rooting 7.5.1..
Its my son's, so while I've flashed my android devices a billion times, this Kindle is a whole other thing...sorry for the questions..
You can either downgrade and then block auto update (look for threads with otacerts) or root 7.5.1. I believe the binary method still works.
OK I was able to get it back to 7.3.0...and even flashed it twice and cleared cache and user data...
But now the wifi won't turn on. I tried to click on ...nothing..
Is there a wifi fix I'm unaware of?
Try pushing the recovery only to it.
Please help!
Help me.
I can't unzip any zip-files downloaded from google Drive as Links about.
As links about?
onemeila said:
Sounds like you need to install the correct drivers. Download and install the driver from this link:
http://forum.xda-developers.com/showthread.php?t=1890413
If that still doesnt work follow the directions from this one:
http://android.stackexchange.com/questions/48023/fastboot-not-working-for-kindle-fire-hd
Click to expand...
Click to collapse
What about if i'm using a fastboot cable, and when i type adb devices or fastboot devices it still doesn't show up? I have the drivers installed for the fastboot cable but it just never shows up. I've been trying to use your tool to fix my bricked kindle that is stuck in a boot loop and has no system.img.
Recover from bootloop
As I am stuck in a bootloop, will I recover my kindle if I only restore the boot image?
Excellent resource! I now have Beanstalk Lollipop on my Kindle. Thank you!
Sent from my LG-VS980
Kindle Fire HD 7" overhaul
I tried to post this as a reply to "how to downgrade kindle fire hd" thread but as I'm a newb here, I was redirected to this thread. So here it goes...
I have a 2012 Kindle Fire HD 7" serial starting with D025, running firmware 7.5.1. I successfully rooted the device with the bin4ry method thanks to all the helpful members here. I am interested in getting TWRP loaded as well as flashing maybe a Cyanogen ROM. I haven't looked into the ROM's too much as I'd like to get TWRP on first... baby steps haha... So I saw instructions for getting TWRP on devices with firmware up to 7.4.8 or somewhere around there but nothing higher. Next step is to downgrade the Kindle to an older firmware. I have ordered SkOrPn's Factory Cable, should be here in a day or 2.
So onto the questions:
1. In this thread: http://forum.xda-developers.com/showthread.php?t=1951254 I see a list of system.img files to downgrade to. Does it matter which one I choose if I am going to be flashing Cyanogen ROM?
2. My next steps are to follow the instructions on that thread by plugging in the cable, run the adb command, run the SR Tool, follow instructions, and then on the bottom of the original post in that thread, it gives instructions for downgrading to 7.2.1. I take it those directions apply for any of the versions downgrading to?
This is where I am kind of lost as to what I am supposed to do from here. I am not sure what the SR tool accomplishes or intends to accomplish and the Factory Cable seems to be most often used as an "unbricking" device. I am not bricked, just looking to downgrade so as to get TWRP and Cyanogen. If there is an easier way for me to get TWRP and Cyanogen running without the downgrade or all this hullabaloo then I would be delightfully surprised.
So any help would be much appreciated
stuck on Fastboot
Hello, I definitely have a Kindle Fire HD 7 2012 and I do NOT yet have a factory cable, but it seems like the tool is working with my regular cable. When I use 1. Restore-Factory Rooted with SuperSU.apk my cmd screen tells me sending 'system' (907264 KB). . . OKAY (317.060s) writing 'system' . . . OKAY (72.750s) finished. total time: 389.821s
Even though I have erased cache and userdata, Factory Recovery, and Reboot normally I still am stuck on the FastBoot screen..
any suggestions ?
got Factory Cable Today still stuck in fastboot
HappyTNMom said:
Hello, I definitely have a Kindle Fire HD 7 2012 and I do NOT yet have a factory cable, but it seems like the tool is working with my regular cable. When I use 1. Restore-Factory Rooted with SuperSU.apk my cmd screen tells me sending 'system' (907264 KB). . . OKAY (317.060s) writing 'system' . . . OKAY (72.750s) finished. total time: 389.821s
Even though I have erased cache and userdata, Factory Recovery, and Reboot normally I still am stuck on the FastBoot screen..
any suggestions ?
Click to expand...
Click to collapse
I got my factory cable today. I plugged it into my kindle and to my pc. I tried to run the tool to clear cache, factory rooted with SuperSU.apk, Factory Recovery, then reboot normally and my kindle is still stuck on FastBoot....
What am I doing wrong? What else can I try? Thanks in advance for any help, much appreciated...
KFHD 7'' is not a KFHD 7'' 2013 KFSOWI ... bootloop fixed
I got a bootlooped kindle from someone and thought it was a KFHD 7'' it took me forever and quite a few attempts to fix and fails to discover it is a KFHD 7'' 2013 KFSOWI which it totally different. notable markings are no camera and angled edges on the back. also if you get to the point of running fastboot you will know as "getvar product" will return "soho-pvt-prod-07" instead of "tate-xxx-xxxx-xx"
i wanted to thank Red_81 from http://forum.xda-developers.com/showthread.php?t=1951254&page=23 who pointed me to the Kindlesuite guys which led me to http://forum.xda-developers.com/showthread.php?t=2685090&page=4 and the fantastic Firerooter tool it is super easy to use and does everything for you even has great help in it about updating the adb drivers etc.
just make sure you really have a 2013 KFSOWI version. i previously had it bootlooping, then red screen (when i used the KFHD SRT many times), and finally after trying Firerooter a couple of times got the dang thing working again. I ended up installing the 11.4.x then 11.3.x and wiping user data. I about fell out of my chair when I finally got a screen. So dont give up. I also had to get a fastboot cable.
I have bricked my Kindle Fire HD 7" 2nd Gen. The device is stuck in what i would assume is a boot loop. I am wondering if someone can confirm if the KFHD SRT is compatible with my device and could possibly unbrick it. Any information or suggestions would be greatly appreciated, I could not tell what versions the kindle were supported from the original thread. KFHD SRT THREAD: http://forum.xda-developers.com/showthread.php?t=1951254&highlight=kindle+fire+hd+7
Hi everybody
I've been running a rooted kindle fire hd for about a year with cyanogenmod and no problems. Tonight I downloaded the latest nightly update installed it with TWRP and re booted fine.
I kept getting google play services errors so decided to factory reset and clean everything up. Now I cannot get past the teamwin boot logo.
I see the orange kindlefire, blue kindlefire, then the teamwin logo flashes every 5 seconds.
Any ideas on how to recover this?
I posted this in standalone thread about a week ago, I've since bought a fastboot cable, which doesnt have any effect. I see Kindle fire on my PCs device manager so thinking there must be some sort of communication between the 2. Stuck with where to go now though. I know of at least 2 other people that have posted the same problem.
Regards
KP
I was messing around with rooting 5.1.1 and now I'm stuck at the boot animation, the word 'fire' in orange with yellow moving across it. I have adb and root; it's not totally bricked. I suspect that my mistake was, while haplessly pasting commands from the 5.0.1 root batch file, pasting the command "fastboot boot boot.img". I can issue reboot commands and it will reboot but still get stuck at the boot animation.
So, how can I get myself out of this mess? Do I need a 5.1.1 boot image from a volunteer?
Come to think of it, would booting to (OEM) recovery and doing a factory reset do the job?
theholycow01 said:
Do I need a 5.1.1 boot image from a volunteer?
Click to expand...
Click to collapse
Amazon has finally posted 5.1.1 now, you can grab it straight from them.
Success! Thanks so much!
For anyone arriving here with the same question:
I found update-kindle-global-37.5.4.1_user_541112720.bin on Amazon and downloaded it. It was on the Amazon page that says
Amazon Device Support › Fire & Kindle Software Updates›
Fire (5th Generation) Software Updates
Download Fire (5th Generation) software updates
Click the link below to download the software update to your computer:
Download Software Update 5.1.1
Click to expand...
Click to collapse
I'd post a link but as a noob I'm not allowed to yet, but Google that text and you should find it.
Then, I found the thread titled "[HOWTO] How to restore frimware on your device + Amazon Frimware" by Awesomeslayerg, Senior Member on 2nd November 2015, 12:13 AM in the "Fire Original Android Development" sub-forum (and would you believe noobs can't even post links to other XDA-Developers threads?!), which says:
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.
Click to expand...
Click to collapse
I'll note that step 4 said something else, which I too forgot to record exactly what it said...something more like "Install update from ADB". As noted elsewhere, ADB won't see the Fire until you select that option in the menu. Also, don't be surprised if Windows decides that it's suddenly a new device at that point and prompts you to install the drivers; let that complete before you run the adb sideload firmwarefilename.bin command. It seemed to take forever, I should have timed it, but I ate my breakfast and did some other stuff while I waited, and eventually it was back to the recovery menu. I did not need to wipe everything, at that point I rebooted and SUCCESS!