HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Well, if you can get into recovery, that's a good thing.
I had this problem a couple of days ago. I had tried to revert from Chameleon OS back to the stock OS by flashing Haschode's stock OS zip, which resulted in the issue you described. I fixed it by restoring from a back up of ChaOS o had made, and it got me out of TWRP.
You could try re-flashing Hashcode's stock OS (it comes pre-rooted). It can be found here: http://forum.xda-developers.com/showthread.php?t=2218475
To move it on to your SD card, go to "Advanced" in TWRP and select "ADB Sideload," or something to that effect. Then from your PC, use a command window and enter "adb sideload name\of\zip.zip"
I don't remember if you have to wipe anything or not before you flash it
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... Or maybe it's a rooted Kindle Fire HD running ChameleonOS
Aaron Belle said:
HI,
I am sorry to bother the xdadevelopers community but I have tried to root the KIndle Fire HD 7" I offered to my mom for her birthday a week ago and i can't work around a problem :'(
I successfully installed Team Win Recovery Project. But anytime I boot i get into recovey (even when not pressing any button).
I hace searched the web for the last 3 days but any of the solutions have worked so far:
- I have tried to use adb shell "idme bootmode 4000" buti get /sbin/sh: idme not found
- I have tried adb shell nbmode but with the same result
- The rest of the solutions were for linux users.
So the question is ... what to do from here ?
Thank you very very much for any sugestion
Greetings from Bordeaux, France
Aaron Belle
Click to expand...
Click to collapse
Lol same thing happened to me when I flashed TWRP and 2nd BL. So basically, your in a boot loop. Don't worry you didn't do anything wrong, its just that the stock Kindle OS now hates us because we modified something. So here's what's gonna need to be done. You have TWRP, your all set to flash anything you want! But, you have no custom rom in there correct? My same mistake. Those are all easy fixes, the problem is playing with the KFHD7 drivers on your computer to detect your device 100% while its connected and on TWRP. I can't remember how I got mine to detect it, if I'm not mistaking I unisntalled ALL associated drivers, then reinstalled the ones provided for the rooting process WITH THE DEVICE STILL CONNECTED, then manually updating the driver to those installed drivers in C:/Program Files/Amazon/Kindle Fire. Once its installed, you would need to check by opening a command prompt with ADB, then check for devices by typing "ADB getdevices" if I'm not mistaking and see if some serial numbers show up. Then push the files thru ADB. If you wanna cheat your way thru ADB cause you don't know how to use it properly, do what I used to do. Download the Nexus 7 toolkit, install it, go to the folder where installed and create a shortcut for "tkmain.exe" to your desktop. Then open that and a green text command looking menu is in your view. If serials appear on the top, device is detected thru TWRP. If not keep playing with installing the drivers while in TWRP and refresh the green menu by using option 27 (type 27, then hit enter). Once those serials show up, download the custom ROM you want your mom to have. I recommend CM10.1 as its a small file, stabler than CM10.2, and its basically jellybean. Remember the folder where the Nexus 7 Toolkit was installed, where I first mentioned to make a shortcut for tkmain? Go back to that folder and look for a folder called "put files to push here". Throw the ROM there. Rename the ROM something short and with few or no symbols. When that's done, your ready to push it. Go to the wonderful green menu thingy, type 13 and hit enter. Then it will have two options. Type 2, hit enter. It will ask if your using an insecure bla bla bla. Type yes, hit enter. Then it should show the name of the ROM you threw in the folder, type it out exactly as spelled, hit enter. Push to /sdcard/. Some crap will appear and say "remount failed: Success" ignore that, don't panic, that's good. For a while nothing will show, but afterwards words should appear confirming the push, and Two last questions your gonna type no to. Now your ready to bring moms new device back to life! If you know how to flash a rom, do it. If not, swipe to wipe dalvik cache in Wipe menu, go back, Install > search SD card for your file and flash. Tada! You should see CM logo after the blue Kindle Fire logo and wait til the screen dims more or less, that means your a few seconds away from getting to touch. Remember to start it up, then flash GAPPS so mom can have Google Play, I'm sure she's gonna love Candy Crush Saga as mine does.
Sent from my Amazon Kindle Fire HD using xda app-developers app
May uestnl
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
jeanphi506 said:
Hi,
I have the same problem as AAron Belle, I think:
I followed the
"[REF] Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial" till step 3.
I wanted to stop at step3 after installing 2nd bootloader and TWRP, without installing any custom ROMS.
I succeeded in the sense I don't have any red screen and the Kindle Fire HD 7 boots in TWRP (Screen Kindle fire in orange, then in blue, then TWRP).
But I can't find a way to boot anymore in the stock system (amazon).
I try to use a factory cable, but without success.
I would like to keep the 2nd bootloader and TWRP that I just installed, and as a first step use them in the amazon environnment.
Is there something I can do (not too complicated, I'm a noob!) ?
Thank you in advance,
Jeanphi
Click to expand...
Click to collapse
Try the solution I mentioned above you. I'm no rocket scientist, or an android expert, just picked up a thing or two from experience. If I can do it you can as well. That's why I mentioned the toolkit I used. It may be for the Nexus 7 but it does the same adb commands used for all androids for you. That way if your not an adb expert you can use that. As I said, your first goal is to get your computer to properly detect the device while in TWRP, your stock kindle OS is just doing what it does best when simple modifications are done.
Lost access to stock amazon
stunts513 said:
You can use "adb sideload" or "adb push" from a command prompt while plugged into your kindle in twrp and put a new ROM on it, like stock amazon, kinology, cm 10.1 or 10.2, etc.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
jeanphi506 said:
Thank you for the answer.
If I put a new ROM containing stock amazon, will I have still on the Kindle the 2nd bootloader and TWRP ?
Will my Kindle still be rooted ?
Jeanphi
Click to expand...
Click to collapse
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
How to get to the original OS after installing TWRP.
Crossvxm said:
Depends on if the stock ROM is rooted, although usually, the answer is yes since messing around with things like overclocking and so on is always one of the reasons people seek to achieve root. If your going to flash this stock ROM, obviously only possible thru TWRP so yes you'll still have TWRP + 2nd BL. If your going to do the headachey fastboot restore, (not recommended at this point) then no. I've never gotten ADB sideload working, but either way I prefer pushing a rom to the internal SD and just installing.
Click to expand...
Click to collapse
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
jeanphi506 said:
Thank you for answers. I think I will my first attempt to flash a Rom, through TWRP.
I will use this following link from Hashcode
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason.
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac"
Nevertheless, before doing that I might try to understand and use your first answer, as my Amazon 7.4.6 must still be on the system and this is just a question of access to it.
Jeanphi
Click to expand...
Click to collapse
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Reinstalling stock OS
Crossvxm said:
Once you flash any, there is no recovering the last stock you had, in this case, 7.4.6. This is lost for all of us. Now I haven't yet researched if there is a way to completely revert back to stock (as in removing the TWRP, 2nd boot loader and any other mods), but if there were, that's the way to go back to 7.4.6. However, no matter what ROM you toss on your device, any objects you may have had saved to your SD are still found as long as you don't delete em thru twrp. Remember before tossing in a rom, in the Wipe section, just swipe to factory reset, then go back and Install the zip from your storage.
Click to expand...
Click to collapse
Coming back to give you some news.
I was not able to use the following link, as it was not on my Kindle and I was not able to have the kindle recognized by the computer.
"This flash .zip file contains the Amazon OS 7.4.3 update + root/Superuser.apk and should have OTAs disabled. You can use this to revert back to the Amazon OS should you need to for any reason."
I decided to use he backup I made and I used the following command, with the factory cable:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
It worked and I have a working device, but without TWRP, 2nd boot loader.
I suppose I could have flashed directly the Amazon OS System mentionned earlier, but I was not exactly sure which command to use.
So, I will to try again to install TWRP, 2nd bootloader.
Thank you very much for your help. I will read again your answers to try to use them in the future.
Jeanphi
Completely fixed! Thanks!!
Download the Nexus 7 toolkit said:
I cant tell you how much of a life saver this was....this works 100% !! Just follow his instructions to a tee and this will save a lot of time and effort trying to get our TWRP loop!
Click to expand...
Click to collapse
I recently rooted my kindle fire hd 7 running 7.4.6 and i had it working fine, I could use the adp connection, the drivers were working, and I could access the ad card. I then decided to flash twrp so that I could then install CM 10.1 and get jelly bean 4.2.2. I was able to install twrp by using fire flash and made sure to select the option to flash a 2nd boot loader but when I rebooted, the device gets stuck in a boot loop and always loads twrp, whether or not I wanted to. Apparently this problem can be fixed with an adp command, but I have not been able to attempt this fix because I no longer can get an adp connection with the kindle, and none of the drivers that worked prior to installing twrp were working. I can't access the sd card files to flash the CM 10.1 files, or anything else for that matter, and my PV (running windows 7) can't identify the device or install drivers. I have not tried to use a factory cable and flash a new os in fast boot mode, and I'm not entirely sure how to do this properly so I would like to avoid resorting to this. If there is a way to get the adp connection and drivers to work, get the kindle to boot up normally instead of alway getting stuck in twrp, and install the CM 10.1 software I wanted, please let me know, and if there's no way to do this, how can I revert back to the amazon os with a factory cable. Thanks in advance.
Yep, probably again a noob that bricked his phone.
As there was no info on my phone that wasn't on google servers or something I was so stupid to start installing the latest official CM12 built on my XT1068 without any decent backups.
- I think the moto/google service for lost devices encrypted my phone without me really noticing it. :crying:
- I was on Lollipop, the latest update I got here from in Benelux/Europe.
- I unlocked my device, worked fine. device also tells in bootloader
"Device is UNLOCKED. Status Code: 3"
- when than having installed TWRP 2.8.0.1, os started but gave problems installing superSU.
(no prob I thought, I go immediately forward with CM12 installation, so don't have to bother with the old ROM) :silly:
- wiping everything for clean install I already saw some messages coming up. on hindsight; Difficulties with opening /data folder etc...
- tried to install CM, and several other more stock roms, but never get through the message. All bad installs.
- maximum I got is CM12 booting up, preparing some apps and than a message describing the encryption problem, asking to reboot.
TRIED:
- install from usb drive (with OTG cable)
- erase and reinstall from TWRP 2.8.0.1 and other recoveries.
- fastboot flash a standard recovery again, to wipe data from there,
(from this standard recovery installers never got through even the verification to install, so tried than installing from other recoveries, same problem.)
Can still try but hesistant:
Unlock my mothers phone (same month, same model, same place, probably same encrypted) to try backup there in TWRP, recover this on my phone, and this way flash standard rom again. From there I could probably get rid of encryption. (as found already in several places)
I would afterward immediately try to lock my mothers phone again, don't know so much of how to get recovery to standard one again though. Can I backup this before. When I try now "adb backup - all" on my phone from my mac, I get "unable to connect for backup" message though. Even when phone is saying "phone connected".
Anyone an idea of how to get out this trouble?
Greetings
Otto
[email protected]: try "fastboot erase userdata"
have the feeling I'm getting there. Gapps still don't work but rom boots. Recovery has to be standard one to make encryption to work. Thats the key.
I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.
Hi, I rooted and installed aosp nexus rom on my kindle fire. was working fine until somehow it factory reset and screwed up. (play store wont work, or play services, cant use any google apps, no recovery) I cannot seem to get into any type of recovery. Nothing happens when i try to boot into fastboot, or recovery. I want to revert back to the fire OS.
MikeHenry said:
Hi, I rooted and installed aosp nexus rom on my kindle fire. was working fine until somehow it factory reset and screwed up. (play store wont work, or play services, cant use any google apps, no recovery) I cannot seem to get into any type of recovery. Nothing happens when i try to boot into fastboot, or recovery. I want to revert back to the fire OS.
Click to expand...
Click to collapse
- untether device (no charger or USB connection)
- long press power until device shuts off
- press <power>+<vol-up> to access stock recovery
- if device does not enter recovery release buttons and try again
If the above sequence is unsuccessful after a few attempts there is little you can do to recover the device. If you are one of the lucky few with an older 5.0.x bootloader you can try to access Fastboot via <power>+<vol-down> and then boot into twrp.
Note: <volume-up> is the button closest to the headphone jack.
Thanks for the reply. I already knew the key combo to boot into recovery. What I'm saying is, nothing happens when I try.
MikeHenry said:
Thanks for the reply. I already knew the key combo to boot into recovery. What I'm saying is, nothing happens when I try.
Click to expand...
Click to collapse
Right - as noted there is little you can do if stock recovery is inaccessible (no other magic commands). If within warranty Amazon will exchange no questions asked.
If fastboot is accessible it's worth shelving as there's an outside possibility some future vulnerability will be uncovered that permits booting recovery or some other 'repair' tool.
Edit: Assuming Nexus doesn't boot either. If it does there's a bit of hope as FlashFire can be sideloaded which opens a few possibilities including reflashing Nexus or another custom rom which will likely restore functionality even if stock recovery is borked. Don't try to restore FireOS with FlashFire - not compatible.
Once again thanks for the reply. Gotcha. I can get into fastboot with some help (doing a fastboot check with supertool boots it into fastboot) I rooted and installed flashfire with RootJunkys supertool originally. I used flashfire to install the current rom. Worked flawlessly. I was going to attempt to flash slimrom or some other rom when the current one malfunctioned but I cannot seem to get flashfire to work. It will immediately force close after I try to open the app.
MikeHenry said:
Once again thanks for the reply. Gotcha. I can get into fastboot with some help (doing a fastboot check with supertool boots it into fastboot) I rooted and installed flashfire with RootJunkys supertool originally. I used flashfire to install the current rom. Worked flawlessly. I was going to attempt to flash slimrom or some other rom when the current one malfunctioned but I cannot seem to get flashfire to work. It will immediately force close after I try to open the app.
Click to expand...
Click to collapse
If you used FlashFire to install your current ROM (Nexus?) then it is unlikely you have an older bootloader that permits booting twrp from fastboot. So FlashFire is the only option in the absence of a working recovery. Thoughts:
- Is your device still rooted? Fire up SuperSU to check.
- Have you tried side loading the latest FlashFire build from here