Database Develop

[Q] 7.4.6 - two questions

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.

[Q] [KHDF] always booting TWRP

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

[Q] fastboot will not work, no other thread helped yet

wanted to convert my HD7 into full android and got red screen in process. have read dozens of threads so far no help.
have fastboot cable, and I can get my kindle screen to say fastboot kindle fire - but I cannot seem to get the proper driver installed on my Win8 so that I can use fastboot. I've downloaded and installed numerous drivers. So far my kindle will not communicate with my computer, thus I cannot move forward in any way. I have installed ADB and SDK on my computer. I have scoured internet for ideas, helps. I am STUCK. Any help greatly appreciated!

Try the driver on my signature, but take note you are on windows 8, you can't install the driver by default because windows 8 won't allow unsigned drivers, you have to boot windows 8 up with driver signature enforcement disabled. Google disabling that and I think it may be the root of your problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I think it worked
stunts513 said:
Try the driver on my signature, but take note you are on windows 8, you can't install the driver by default because windows 8 won't allow unsigned drivers, you have to boot windows 8 up with driver signature enforcement disabled. Google disabling that and I think it may be the root of your problems.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks! I think it worked. I still can only see my kindle in device manager, but I ran the SR Tool.bat option to check fastboot and it said it finished. of course my kindle won't reboot or anything because the bootloader is messed up. so now I am on a quest looking for steps to flash something with fastboot so that my kindle will actually reboot and then I can take steps toward a completely new ROM. obviously I'm learning as I go. I'll start reading more threads, feel free to point me in the right direction if you want. thanks again!

Got this thread: http://forum.xda-developers.com/showthread.php?t=2128848
Do the part at step after where it says added 04/02, and please make sure you check the md5sum of the file before flashing, if it doesn't match up you will have a hard brick. Just Google "md5sum windows" if you don't know how to calculate a md5sum on windows. There's freeware available to do it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

blurry eyed now
stunts513 said:
Got this thread: http://forum.xda-developers.com/showthread.php?t=2128848
Do the part at step after where it says added 04/02, and please make sure you check the md5sum of the file before flashing, if it doesn't match up you will have a hard brick. Just Google "md5sum windows" if you don't know how to calculate a md5sum on windows. There's freeware available to do it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I've read threads and answers to the point now that I'm going in circles. No one seems to address my problem. I am in fastboot. It appears I can flash things onto my kindle. I got the "kfhd7-u-boot-prod-7.2.3.bin" file on my kindle and got rid of the red screen. but I cannot get a recovery screen on my kindle. it just says kindle fire (fire is in orange). I press the power and volume up button and nothing. I go back to the beginning, read more threads. argh! it doesn't seem to be bricked. I just can't get a new bootloader to run so that I can flash a new rom. argh help!

You can't get into twrp anymore be cause we had to restore the stock boot loader, now u just need to reflash the system image and it should boot up, might need the boot image as well, but I think that kfsrt restores both of those, just put it in fastboot again and start the process.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

got it
stunts513 said:
You can't get into twrp anymore be cause we had to restore the stock boot loader, now u just need to reflash the system image and it should boot up, might need the boot image as well, but I think that kfsrt restores both of those, just put it in fastboot again and start the process.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It was a long haul but finally got out of the loop. thanks for your help! the final step that got me out of the ditch was to download and use the KFHD_SRT_v1.3.5- 7.3.0, then I ran #3 restore-factory recovery. I learned a lot through the process about fastboot and flashing files. For now I'm rooted with factory launcher and some other options too. I still think I want to wipe it and make it totally android.
Thoughts or recommendations? and thanks!!!!!!!!!!!

Well there are a fair amount of ROMs out, I use a tablet ui cm ROM that jester originally made, but when he went straight to cm 10.2 I wasn't ready so I made my own patch for cm 10.1 latest update with tablet ui, if your interested check the link in my signature out, though u need to put twrp back on again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Bricked KFHD7: Boots then reboots again to Recovery Mode

So after rooting and installing a rom on my khhd7, I reboot, i see the fire logo, then the blue fire logo, then the fire logo again, then its shuts off. Then i see the fire logo again, then the blue again, and then i end up in recovery mode. I want to fix this and have my kindle back to normal. I have tried several ways of unbricking my kindle fire but all have failed. Can anyone tell me how to get out of this, hell, how to just get everything back to normal?

Wrong thread I will ask to move it
Sent from my Amazon Kindle Fire using xda app-developers app

I think I'm going to write a tutorial somewhere tomorrow for this problem, because I have been seeing too many of this problem lately. Basically you need to push a ROM onto the sdcard and flash it. Put the ROM in the same folder as a adb command, boot your kindle into twrp and open a command prompt and type "adb push romname.zip /sdcard/" once it finishes just flash the ROM on the sdcard. If the adb command fails to see your device update your drivers to the ones in my signature while in twrp. Reason for the boot loop is Amazon's os detected a older boot loader if I remember right, and so it refuses to boot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
I think I'm going to write a tutorial somewhere tomorrow for this problem, because I have been seeing too many of this problem lately. Basically you need to push a ROM onto the sdcard and flash it. Put the ROM in the same folder as a adb command, boot your kindle into twrp and open a command prompt and type "adb push romname.zip /sdcard/" once it finishes just flash the ROM on the sdcard. If the adb command fails to see your device update your drivers to the ones in my signature while in twrp. Reason for the boot loop is Amazon's os detected a older boot loader if I remember right, and so it refuses to boot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Hey if you make a tutorial, post the link to this thread. I'm still not sure exactly what you mean by that (I'm kind of a noob at rooting) so if you could outline it step by step that would be awesome.

stunts513 said:
I think I'm going to write a tutorial somewhere tomorrow for this problem, because I have been seeing too many of this problem lately. Basically you need to push a ROM onto the sdcard and flash it. Put the ROM in the same folder as a adb command, boot your kindle into twrp and open a command prompt and type "adb push romname.zip /sdcard/" once it finishes just flash the ROM on the sdcard. If the adb command fails to see your device update your drivers to the ones in my signature while in twrp. Reason for the boot loop is Amazon's os detected a older boot loader if I remember right, and so it refuses to boot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The issue seems to be the newer firmwares not playing nice when flashing an older firmware at the same time as flashing the 2nd bootloader/twrp. After 4 bootloops I found that going back to 7.2.3 then rooting with KFFA, then using Hashcode's 7.2.3 bootimg and the recent twrp he lists and flashing with Fire flash worked like a charm.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers app

Ok tutorial is up, here's the link!

[Q] twrp bootloop with a factoryboot cable on hand

Hello.
I rooted my kfhd 7 10.4.6 successfully and naturally proceeded to twrp where it got stuck on a bootloop. Now that I have made a factoryboot I was wondering what rout I should follow to flash the rom?
Browsing the topics I see these options:
* continue the process installing the twrp...
* download a toolkit that allows backup
* install ADB
* get fff
Now I'm wondering if someone has just made a restore utility, is there a utility to just restore to the state of having a rom installed?
Also, since I don't care for restoring backups, is there an easier way to flash?
I really appreciate your advice.
Deano

Firefirefire is not for this device 1st off, you don't have a kfhd 2nd off. Kfhd is v7.x.x. You have a kf2. Kf2's are 10.x.x.
Sent from my Kindle Fire HD 7 using XDA Premium 4 mobile app

if your logo turns blue at this point, turn the device off and when you turn it back on hold volume up while the logo is orange and keep holding it even after it turns blue, it should then say twrp and go into twrp, from there you could push a rom and flash it. If the logo does not turn blue then i would put it in fastboot and use kindle fire first aid to restore it, and try again.

which rout should I go? restore or twrp?
wire55 said:
Firefirefire is not for this device 1st off, you don't have a kfhd 2nd off. Kfhd is v7.x.x. You have a kf2. Kf2's are 10.x.x.
Click to expand...
Click to collapse
stunts513 said:
if your logo turns blue at this point, turn the device off and when you turn it back on hold volume up while the logo is orange and keep holding it even after it turns blue, it should then say twrp and go into twrp, from there you could push a rom and flash it. If the logo does not turn blue then i would put it in fastboot and use kindle fire first aid to restore it, and try again.
Click to expand...
Click to collapse
It's been a while since I bricked. Perhaps it was 10.4.6 I can no longer access the settings the verify. But now that I have a factoryboot cable. I would just flash cyanogenmod. Now when I connect factoryboot it reads (in a fancy 3d text) "Fastboot" with a small "kindle fire" on the right side of it.
I originally followed a youtube video that had links for freedom boots, twrp, etc... to this forum, but then again I must have downloaded incorrect versions.. I'm not concerned with the date. So I'm wondering if it's easier to restore or continue with twrp.
Here are some links I was looking at:
(do I need to go the adb rout)
http://forum.xda-developers.com/showthread.php?t=2459498
Do I need to have adb tools use command: fastboot -i 0x1949 getvar product
http://forum.xda-developers.com/showthread.php?p=33156486
http://forum.xda-developers.com/showthread.php?t=2685090
http://forum.xda-developers.com/showthread.php?t=2271909
http://forum.xda-developers.com/showthread.php?t=2685090
There are too many guides, here ... which is really great. But the process of download, verification, transfer (to a pc).
If I cant brick this device any harder than it is, I will follow each guide...
stunts513, the fire logo does not turn blue. In fact I was taking a video when it was loading ... (it's a funny video about
a guy who bricked his device)

I had the same issue... I forgot to remove a script before flashing twrp. Maybe it is the same for you. Did you followed carefully the tuto ?
In my situation, I managed to go into fastboot (with fasboot cable), flashed stock ROM, and did the flashing process from the beginning..
Hope it may help
"Envoyé depuis mon Amazon Kindle Fire HD avec Tapatalk"

If you only have fastboot access right now i suggest restoring with srt or kindle fire first aid. Afterwards you can start the twrp process over again, we can't simply flash cm from fastboot, if everything else isnt in place like the stack file or the bootimg and a old version of the bootloader then it wouldn't work. Fastboot should be in utilities like kffa and srt

stunts513 said:
If you only have fastboot access right now i suggest restoring with srt or kindle fire first aid. Afterwards you can start the twrp process over again, we can't simply flash cm from fastboot, if everything else isnt in place like the stack file or the bootimg and a old version of the bootloader then it wouldn't work. Fastboot should be in utilities like kffa and srt
Click to expand...
Click to collapse
There are so many options it seems, but I think I know what to do now (please let me know if it's not a incorrect course):
First, download and Kindle fire first aid from here, to restore back to and then follow the instruction here in order to start twrp and flashing.
wire55 said:
Firefirefire is not for this device 1st off, you don't have a kfhd 2nd off. Kfhd is v7.x.x. You have a kf2. Kf2's are 10.x.x.
Click to expand...
Click to collapse
I think the versions are according to kf2 (10.4.6) this time.
Thanks you so much everyone.

unbrick attempt 3
I have download and installed many sdks and drivers and checked md5.. while at it. kffirstaid does not really seem to connect with the device. And some messing around with the drivers did occur, uninstalling/reinstalling through downloads and through kffirstaid. It now announces as tate-pv-08 though a triangle is showing next to Android ADB Interface in device manager.. I think something is missing.. Is java sdk necessary? because it doesn't install ..
yeah
If I didn't mess around with my Kindle I would be reading through Dante's levels of hell which is more pleasant than all this troubleshooting ..

testing
test

You should be able to update the drivers of the Tate device using the drivers in my signature and have then programs work with fastboot. Not sure why an adb device and a Tate device show at same time, the Tate device should be the one needing fastboot drivers for it to work.

I got
stunts513 said:
If you only have fastboot access right now i suggest restoring with srt or kindle fire first aid. Afterwards you can start the twrp process over again, we can't simply flash cm from fastboot, if everything else isnt in place like the stack file or the bootimg and a old version of the bootloader then it wouldn't work. Fastboot should be in utilities like kffa and srt
Click to expand...
Click to collapse
Hi. Someone yanked out the factory-boot cable and I quickly ordered the scorpion king cable. I downloaded kffirst aide again and there's been a massive update. Running a restore showed all signs of success. But then after restoring it to normal boot, I get kindle fire logo showing and then the boot loop continues.

If kffa fails then try SRT.

Kffirst aide is in order
stunts513 said:
You should be able to update the drivers of the Tate device using the drivers in my signature and have then programs work with fastboot. Not sure why an adb device and a Tate device show at same time, the Tate device should be the one needing fastboot drivers for it to work.
Click to expand...
Click to collapse
I have upgraded kffirst aide and in the middle of restore I do the following statements:
cannot load 'boot-prod.img No error
cannot load recovery-prod.img No error
cannot load system.imp: No error
However at the end there is the success message:
Success!!! The kindle Fire 2 7 has been restored to software version 10.2.3
and yet the bootloop continues to plague the brick..

That means the files it tried to flash didn't exist on your computer. Try srt, it includes those images.

I have a kf2
stunts513 said:
That means the files it tried to flash didn't exist on your computer. Try srt, it includes those images.
Click to expand...
Click to collapse
I'm not sure if this is compatible with my device. Perhaps replacing those files/folders would solve the problem?

Oh wait yea kf2 didn't have a SRT.... My bad. Yea in that case you will need the kf2 I ages, kffa is supposed to download them for you but it's possible the links went down for the files.