Related
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
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!
Tablet had Fire OS 5.3.1 build installed.
Successfully rooted with Rootjunky supertool - after a lot of hassle with Kingroot (needed a newer version via an XDA link). Replaced Kingroot with SuperSU - and loaded Google Play - everything fine so far....
Magisk Manager app downloaded via Play store- starts to install but when tablet re-boots it's soft-bricked.
I've tried this twice now with same result.
Anyone had success with Magisk on Fire Tablet?
i'm having the exact same issue with a kindle fire hd 7". installed lineage unofficial 20170309 found on here, kept pushing me to install magisk, first time it wouldn't install, then it updated from market...installed successfully this morning and now when device is rebooting it just stays on kindle fire gold screen. volume button doesn't work to get into recovery and adb devices returns nothing. nothing in device manager to even indicate the computer is seeing the kindle fire.
bmckenna said:
i'm having the exact same issue with a kindle fire hd 7". installed lineage unofficial 20170309 found on here, kept pushing me to install magisk, first time it wouldn't install, then it updated from market...installed successfully this morning and now when device is rebooting it just stays on kindle fire gold screen. volume button doesn't work to get into recovery and adb devices returns nothing. nothing in device manager to even indicate the computer is seeing the kindle fire.
Click to expand...
Click to collapse
Hi, when I bricked mine I pressed 'on' & 'Vol -' simultaneously and after a few attempts got it into recovery. From there I selected 'update using ADB' and at this point my Windows PC recognized fire tablet and allowed me to sideload the official Amazon firmware .bin file via fastboot (hope this makes some sense as I'm a bit of a noob!).
As for Magisk - probably incompatible with Fire device as suggested on this thread:
https://forum.xda-developers.com/showpost.php?p=68958498&postcount=2
But the thread's gone cold - no-one's confirmed either way.
FYI, fixed this with the following:
fastboot cable - plug in while device is off to enter forced fastboot mode
managed to get fastboot command responding after installing the android adb driver in device manager to the yellow triangle "tate" device - validate with
"fastboot -i 0x1949 getvar product" will validate that fastboot is responding
then:
"fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img" - reflash bootloader
"fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.3.0-recovery.img" - reflash twrp
just as if you were manually installing twrp for the first time
i had some other issues with kindle fire first aide where, when attempting to restore to factory, it wiped my data and cache partitions, but the above at least let me get back into twrp where i was able to reformat data/cache, flash a new system image, and successfully boot into it.
Moving away from aicp for now since that was what was pushing magisk, giving lineage a try.
Glad you got it sorted. Think I might need to get one of these factory cables just in case future 'experiments' go awry!!
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Stone. Cold said:
It's exactly as the title mentions...
Basically I had this tablet for two years, and I love this tablet, we've been through a lot when it came to flashing ROMs and other stuff, the journey so far has been awesome and I don't want it to end here and I won't give up on this tablet!
So here goes... basically I have installed the Magisk Manager app and in the app I chose to install Magisk V14.0 (I chose the recommended option) and once it has finished downloading and installing I then decided to reboot it. Upon rebooting i noticed that the kindle kept rebooting every 3 seconds, so I knew at that point I seriously screwed up!
I'm on the resurrection remix (marshmallow) and when it was installing the Magisk file it said it was updating the boot.img, I think that's the reason why my kindle is acting up. I don't know really know how to fix this issue as I've tried to go into recovery but it simply will not allow me to because it keeps rebooting and doesn't even give me a chance (which is giving me a headache). I looked on similar posts and users have said that a fastboot cable is needed, but I don't have one and I was wondering if using a normal USB cable would do the trick with ADB commands... if possible. If this requires me to purchase (or make) a fastboot cable then I will gladly order (or make) one.
And if ADB method does work, please tell me specific commands to use, and so. Also I have tried getting my laptop (windows 10) to recognise my device, but even when attached and the tablet is on my device isn't showing in device manger, I have downloaded the SDK tools (not manager) and even then I can't use ADB commands in CMD. I typed "ADB shell" (without commas) and even then it won't allow me to access ADB (so please guide me on this area as well).
If you're a user who is interested in helping others and likes to face a challenge, then please step right up and help me as I need all the help at this point! Thank you!
Click to expand...
Click to collapse
Yes, you are going to need a fastboot cable. You can pick one up on Amazon for cheap or you can make your own by using some tutorial online. After you get the fastboot cable, use the Kindle Fire restore tool that I will link down below. Download it (it will take a while) and run it. Please read the directions because I didn't at first and I boot looped my Kindle by installing older recovery and boot image. After this is complete your Kindle will work again. I wouldn't recommend installing Magisk again because it modifies the boot loader. Sorry.
KFHD Restore tool (that tool that I mentioned): https://forum.xda-developers.com/showthread.php?t=1951254
Thank you for this, will. I will follow your instructions once I have received my fastboot cable
Again, thank you. I have left my tablet on my shelf for quite some time now and didn't really have time to fix it due to college work, and so. But I will definitely let you know the results :fingers-crossed:
I made pretty mutch the same error like you and flashed Magisk 12. I used the fastboot cable, entered fastboot and used the recovery tool to restore recovery and stock Rom with supersu and apex launcher. After following exectly the steps in 2. Bootloader and twrp. The problem I am facing is the same I faced before. After flashing linearOS 14 with twrp. I reboot from recovery. At first it showes the orange logo and the the blue. And it stays at blue logo for hours.
I don't know what to do. The strange thing is. I can boot in the recovered Amazonfire OS. But I can't flash any costum Rom.
I have no idea what I made wrong during the process. I followed all steps and repeated the procedure 3 times.
Always ending in blue logo.
Even without flashing any rom. Only following the steps to flash twrp with all the other stuff I am stuck on blue screen.
Please I need advice. Help me
Hi, I tried to install Cyanogenmod 10.1 on my KFHD8.9, but bricked it in the process. When I turn it on it shows the normal orange kindle fire logo, and then the screen swipes to a red screen, then swipes to fastboot. I can't boot into TWRP, or FireOS anymore. I couldn't find any threads to resolve my problem, so I decided to make one.
Here's what let up to this, step by step:
First, it's running 8.5.1
So I rooted it using the KingRoot windows application (not the .apk)
Then I downloaded TWRP recovery 2.6.0.0 (as per this thread: https://forum.xda-developers.com/kindle-fire-hd/8-9-development/root-install-twrp-android-fire-os-8-5-1-t3278286 )
I downloaded all the other files that said were needed.
I used the FireFlash11.apk, and followed the instructions exactly.
It booted into FireOS the first time, so I reflashed TWRP with FireFlash, and successfully booted into TWRP
I then realized I didn't actually have any ROMs ready to install, so I booted back into FireOS
I downloaded the files, and tried to boot back into TWRP (This is where things went wrong)
I held down the volume up button, just like you normally would, and waited three seconds. The screen flickered, said 'badi: boot image' and for some reason booted into fastboot...?
I looked online, and found that I should factory reset it, so I tried. It seemed to be going fine, until when it shut down. After I powered it back on, my current symptoms appeared (Red screen then fastboot).
I now cannot do anything besides that, so any and all help would be appreciated. Keep in mind that I'm kinda bad at this, and have only correctly flashed a rom using TWRP once, and that was by following a different guide on a different firmware kindle word-for-word, so I'm not quite sure what everything means.
Thanks in advance!
Paradoxiality1 said:
Hi, I tried to install Cyanogenmod 10.1 on my KFHD8.9, but bricked it in the process. When I turn it on it shows the normal orange kindle fire logo, and then the screen swipes to a red screen, then swipes to fastboot. I can't boot into TWRP, or FireOS anymore.
Click to expand...
Click to collapse
If you can boot into fastboot you should be ok.
Read this guide. It's old and file names may change but, the steps remain the same.
https://web.archive.org/web/20161224194648/https://wiki.cyanogenmod.org/w/Install_CM_for_jem
If you are already in fastboot then start with Step 3.
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash recovery kfhd8-twrp-3.0.2-2-recovery.img
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot oem recovery
That should boot you into TWRP recovery.
Just incase you need some files.
Bootloader Download
Custom Recovery Download
Boot Image Download
CM-12.1-NIGHTLY 20161016-jem Download
Newer unofficial lineageOS from this thread. XDA-Link
Edit.
Corrected links.