Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
enjoyingsilence said:
Last night I attempted to root my Fire 8.9 2nd gen.. I used a video on youtube to follow the procedure (not sure if I can link it here? if so, let me know). I managed to get twrp installed, but when it rebooted it got stuck on the kindle fire logo. The color of the text "Fire" changes from Orange to Blue on boot and stays that way. I can turn it off and then back on, and hold volume up to get into twrp. Problem is, when I say to mount storage, or connect it to the computer, nothing happens, so I'm in this limbo where I can't recover back to stock or install a ROM.
Maybe I'm not doing something right when trying to mount the internal storage? I've tried on Windows 7, OS X "El Capitan" and an Ubuntu variant.
I don't have a factory cable, just the cable that came with it.
Thanks for any help!!
Click to expand...
Click to collapse
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
monster1612 said:
Does adb recognize your kindle when it's in TWRP? If it does, then enable sideloading in TWRP (under the advanced menu) and try adb sideload /path/to/ROM.zip to flash a ROM.
Click to expand...
Click to collapse
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
enjoyingsilence said:
Thanks for the reply. Sort of.. If I boot it to fastload or fastboot, w/e it's called, I can open adb shell, but the prompt is odd. If I try to su , it won't work. If I boot into twrp then do adb sideload, it just doesn't work at all.
The computer sees the device though, fortunately.
Click to expand...
Click to collapse
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
monster1612 said:
Try booting into Ubuntu. Are you able to access the kindle's internal storage from within TWRP?
Click to expand...
Click to collapse
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
enjoyingsilence said:
Will I need adb drivers for Ubuntu? If so, where can I get them?
I can see the internal storage from twrp, yes.. when I try to format the sd card (the internal one, there's no removable option) or partition, It seems to give errors.
Click to expand...
Click to collapse
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
monster1612 said:
No adb drivers are needed for Ubuntu - you just need to make sure the android-tools-adb and android-tools-fastboot packages are installed (you'll need the 'universe' component enabled in the "Software and updates" settings to install them via apt-get). The kindle doesn't have an external sdcard, so you wouldn't be able to use a removable one. If you're trying to wipe/format the internal sdcard and other partitions, use the Wipe -> advanced wipe menu in TWRP.
Click to expand...
Click to collapse
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
enjoyingsilence said:
Got # prompt on ubuntu terminal. What steps are next to restore?
Edit: Su does not work, there's no root here. If it makes any difference in what to do next.
Click to expand...
Click to collapse
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
monster1612 said:
If you have the # instead of the $ in the terminal, that means you're probably authenticated with root already. In that case, do apt-add-repository universe && apt-get update && apt-get install android-tools-adb android-tools-fastboot - this will automatically enable the universe repo, update the list of available packages, and install the adb and fastboot packages if they aren't already installed.
Click to expand...
Click to collapse
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
enjoyingsilence said:
Sorry, I should've been more clear. I've added in the universe repository, and installed android-adb-tools as well as android-tools-fastboot. When I said I have # at prompt, that was after typing adb shell. It seems to let me browse through the tablet, a good indicator it's connected and working. My apologies!
Now that I have connectivity from my linux box to the tablet over usb, what are the next steps to recover it? If I type adb shell <enter> whoami, it says root. So we have root access to the tablet. Yay!
Click to expand...
Click to collapse
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
monster1612 said:
Exit adb shell if you're in it already. Now in the linux terminal, type adb push /path/to/ROM.zip /sdcard, where the /path/to/ROM.zip is where your CM/other ROM zip is located on your PC. Repeat this process for any other zips you desire to flash, like xposed, gapps, etc. This should hopefully put the files in the internal storage, from where TWRP can find and flash them. Good luck!
(Side note: assuming you can boot into TWRP, you should be able to view & manipulate the kindle's internal storage from Ubuntu with nautilus or another GUI-based file manager.)
Click to expand...
Click to collapse
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
edit: Found the latest CM ROM and Gapps files. Just need options for full recovery back to FireOS if needed in the end.
enjoyingsilence said:
I'm not sure I have a good working rom at this point. Where might I find the latest one? Also, if I wanted to flash this back to the original FireOS... what would be the steps to do that? Thanks for your help!
Click to expand...
Click to collapse
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
monster1612 said:
CyanogenMod has somewhat stable CM12.1 nightlies available for download here, although I think they're starting to slow down now. If you wanted to flash back to the stock OS, Hashcode created a ROM zip for Amazon OS 8.4.1 (the 8.4.3 version was hosted on the now-defunct goo.im), and you may find the link in this thread. That particular version is a bit outdated, but it shouldn't be too hard to manually upgrade.
Click to expand...
Click to collapse
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
enjoyingsilence said:
Would a nightly build be wise? I'd be worried about it being unstable....
Thanks for the factory reset link.
Click to expand...
Click to collapse
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
enjoyingsilence said:
My 1st and 2nd attempt to flash resulted in a failure. Not sure why...
Click to expand...
Click to collapse
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
monster1612 said:
Try updating your TWRP. Here's Hashcode's thread that links to a download for the latest version (2.8.7.0 as of the time of writing). It's a .zip, so you can flash it in TWRP.
Click to expand...
Click to collapse
Thanks. I was able to update twrp and get the 23rd of Dec's nightly CM12 build installed. It didn't seem to work properly though, and gapps wouldn't install. So I've resigned to the fact that I need to put the original OS back on it. After updating twrp, this doesn't seem possible. When I connect it to the computer, all I'm getting is error: device offline when typing adb shell. This is in linux and windows.
I tried connecting it and mounting the usb storage, then dragging over the fireos images, but after installation it went into this reboot loop due to a corrupt something or other... Now, I can't get cm or the original os back on it.
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
enjoyingsilence said:
So, some updates... it's still dead.. but here goes:
I tried to copy the original os as found in the link you gave above to the fire via the usb storage mode, but after install and reboot it keeps failing as I mentioned due to corrupt data (the amazon os is throwing that error). so I tried adbsideload... it kept telling me that i needed 1.0.32 or newer of adb. After obtaining that, I was able to sideload the original OS image to no avail.
So I tried the recovery tool: KFHD System.img Recovery Tool but I used the wrong one (the one that isn't for 8.9 inch fire hd tablets)... and now it's stuck at the fire logo (orange/yellow in color). Turning off on again and holding volume up to get to twrp no longer works as it's been de rooted, I believe.
Any suggestions?
Click to expand...
Click to collapse
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
monster1612 said:
The volume up to enter TWRP no longer works because the bootloader's been returned to stock. Regardless, you should be able to boot into fastboot. First, make sure the kindle's turned off completely and not plugged into your PC. Then type fastboot -i 0x1949 getvar product. When you see <waiting for device>, plug the kindle in. The kindle should now show a fastboot screen, and the terminal will have outputted a string looking like "Jem-PVT-Prod-04". At this point, if both of those are true, then you should either locate your backups of the stock software or download it for your device. If you haven't made backups, then you can try this tool to attempt to restore. If that tool doesn't work, I have a backup that I'd be willing to share if necessary. In any case, once you have the stock system images, you should flash them as instructed by Hashcode here (skip to the "Flashing back to stock" section). Good luck!
Click to expand...
Click to collapse
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
enjoyingsilence said:
Thanks for the reply. Surely I must be overlooking something.
I downloaded the kindle fire HD recovery tool from the link you provided (the post by onemeila) - KFHD_SRTv2.1-8.14. Opened the SR Tool file, and used option 2 to restore su and such. When it rebooted, nothing happened... stayed stuck on the orange kindle fire screen.
Next, I obtained the boot and recovery img files from the KFHD System.img Recovery thread by onemeila, and put them in the root of the KFHD_SRT_v2.1 folder. I also copied the system.img that comes with the KFHD_SRT_v2.1 file to the root of it, instead of the folder I was in. Then I issued the kindle the following commands from an administrative command prompt... there weren't any errors:
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img # This one will take a few minutes
fastboot -i 0x1949 reboot
It rebooted, but has remained stuck on the orange kindle fire screen.
Click to expand...
Click to collapse
Do you have adb installed system-wide? If you do, try cd'ing to the directory where you placed the boot, recovery, and system images and then running those commands again. If you don't, then move the files to the folder where the adb and fastboot executables are located and run the commands in that folder.
Related
Hi everyone, I have two kindle fire, I messed with both of them.
I've root them the first one has the problem with the yellow triangle logo stucked. And the other one I've tried to reset it to the factory settings and everything was cool until I hit the TWRP utility and I think I erased everything.
I've see tons of posts regarding rooting and troubleshooting related to rooting and i'm pretty sick of rooting, I think that 3 months is sufficient time, please DON'T POST anything related to rooting.
I'm here asking if anyone knows how to flash all the data ofthe kindle from the pc and been able to install the factory software, firmware (I don't know) from scratch from my pc. Anyone, please?
The first one is probably stuck in fastboot. Try giving it a go with "fastboot oem idme bootmode 4000 && fastboot reboot".
For the second one, "I think I erased everything" is as descriptive as not wanting people to post about your procedure is helpful. What exactly is going on with it? For future reference: http://forum.xda-developers.com/showthread.php?t=1644970
You should also update both FFF and TWRP on both devices once they are working normally.
If i may suggest flashing modaco first after a good wipe everything except your sdcard I believe this will make a smoother transition if you desire to return to stock before returning to stock always do a good wioe to remove remnants of previous roms download the latest stock bin and rename it to update.zip do not place it in any folder just at the root of your sdcard flash in twrp this will also wipe out twrp and fff I really dont recommend doing this lots of people fail at doing the procedure correcty modaco is stock with only the market added try this approach first then you can retain fff and twrp for custom backups.
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
I really, don't want to try the adb commands (I've tried them before), nor follow any tutorial about root troubleshooting.
I'm really sick of them and of all that mal-functioning software that you have to download(Eg. Not-responding superOneClick, kindleFireUnbrickUtility saying in one line <No device found> <Processing something> <Congrats, your kindle is good to go! (When it's not)>, Eternal loading Android Commander)
With all due respect I DON'T want any more of those, as I said, 3 months is sufficient time, I feel so frustrated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
jRam90 said:
Ok, so, I've been investigating and what I'm really looking is to erase ABSOLUTELY everything from the kindle sdcard, system, etc, everything. And I'm looking for a method to sideload from the pc the orginal stock ROM of Kindle Fire. Any clues, directions? Any fully functional software?
Click to expand...
Click to collapse
To restore back to full factory
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
8. Let it bootloop about 3 times or so...
If you want FFF and TWRP then flash Stock 6.3.1 Basic from TWRP. This has no root or gapps.
Dasanko said:
http://forum.xda-developers.com/showpost.php?p=25730666&postcount=2
Read from "Reverting to stock software". You can manually rename the file and then copy it into the KF instead of using ADB for it, just make sure the extension is .zip and not .zip.bin (Windows hides extensions per default settings).
Click to expand...
Click to collapse
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
jRam90 said:
When trying to execute the adb shell commands all I get is:
- exec 'system/bin/sh' failed: No such file or directory (2) -
I've also tried, fastboot update | flash | boot | flash:raw
This is with one kindle, with the other one, I can't even get the PC to recognized it as a USB
Is there any tool, that really erases everything and take the stock ROM to be installed again? Software, script?
Click to expand...
Click to collapse
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Dasanko said:
Ahh, that's a bother. It's a pretty annoying error. Could be something messed with your TWRP (I'm assuming you tried the commands from there).
There isn't one, but there's really no need for it... you just rename the ROM to update.zip, wipe cache, dalvik-cache and factory reset, and install update.zip. If you just want to flash stock because you like it better for whatever reason, you could also just look at the MoDaCo custom ROM instead, as it is stock based.
As for the other KF... you can't get it recognized, from where? The ROM? TWRP? Fastboot?
Click to expand...
Click to collapse
Both of the kindles, are damaged. I can't access them. I just can access one by USB.
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Dasanko said:
For future reference:
This user's issues have been partially dealt with.
The first KF will require a factory cable to be fixed.
The second KF was soft bricked (there were a few corrupt partitions) after a bad flash attempt of the stock ROM. Luckily, FFF was still installed, but the Windows fastboot drivers weren't. Reinstalled FFF+TWRP from Firekit, and then fixed the partitions, wiped and flashed the stock ROM.
Click to expand...
Click to collapse
Thanks a LOT, Dasanko !!!!
jRam90 said:
Thanks a LOT, Dasanko !!!!
Click to expand...
Click to collapse
Ok, So, I have the factory cable. How can I test its Ok?
I have another question, the kindle is pratically empty no system, no sdcard memory, probably corrupted ¿How do I use the factory cable, to format the Kindle and install the Stock ROM again?
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Dasanko said:
With the KF off and unplugged, type "fastboot getvar product" on a shell (KFU/tools).
Then plug in the KF using the factory cable. If you get anything listed or returned, it should be working fine. Otherwise, if you wait a few seconds and still nothing, you'll have to check the drivers to make sure the correct fastboot ones are installed.
To check the partitions, you can just "fastboot boot twrp.img" to load a TWRP into memory, and then "adb shell parted /dev/block/mmcblk0 p" to print all partitions' information.
Click to expand...
Click to collapse
Well, I'm at my job now. So I will try this at home, but the shell is not working since system/sh (shell) it's not in the Kindle. I was trying to boot it yesterday with "fastboot boot twrp.img" and nothing. I also tried: "fastboot getvar product" and nothing but I only used the console. Anyway, let's see what happens...
Quick question, I've read that the factory cable puts the Kindle straight into bootmode, ¿So the color of the power button, has something to do with it? ¿I mean how do I know the kindle has entered factory mode? ¿The orange light is an indicator? (With a standard USB Cable I only get the green light with the power button, with the factory cable I first get green light, then orange light)
I've also read that if I can see the Kindle fire logo, the bootloader is Ok. Hence my Kindle is OK, but I can't enter fastboot mode. ¿Can anyone confirm this?
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Dasanko said:
It'll get stuck in the bootloader screen, and fastboot commands should work as well, provided the drivers are properly installed and working.
Click to expand...
Click to collapse
OK, I've finally made myself a working factory cable. And in the device manger I can see the kindle listed as "Android phone" and in that root it says "Android ADB Interface". Look like drivers are not working. Where can I download them?
Those are the proper drivers for fastboot you should be able to use kfu to send twrp and fff to the device if that doesn't work you will need to fastboot flash them
All I get is < waiting for device>. Looks like the drivers are not installed.
Simply hold the power button down while connected when it says waiting then power it back on and it should send also try unplug replug when it says waiting
---------- Post added at 03:49 PM ---------- Previous post was at 03:44 PM ----------
If you would like some help I have some time before work but you must finish your thread for the benefit of others
Oh dear, am a noob, please forgive me!!
I have a Kindle Fire HD 8.9, rooted it OK, then followed "Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial" to install TWRP.
Everything seemed ok, then got stuck on blue/white logo, so got into TWRP hoping somehow I could move a rom on there to flash it. Now I'm in TWRP , the Kindle won't show up on My Computer, so how do I do this? I did try pressing "mount" but nothing happened.
I've searched forums but am just getting more confused!!
Maybe the drivers are wrong, but I don't know how to fix that.
Tried looking at "[HOW-TO] ADB Push a ROM to your phone"http://forum.xda-developers.com/showthread.php?t=1667929, it tells me to find where my ADB is on my PC's hard drive, but I can't find anything that says AndroidSDK on my c:drive.
Oh God!! Am I doomed???
Please can someone kind help me??
Thanks guys
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
http://forum.xda-developers.com/showthread.php?t=2277105
mfg
German JPL
Thank you German JPL,
I did try to follow this trobleshooting bit at the end, but I'm kinda stumped by the fact I don't know where this "ADB binary is (usually inside platform-tools folder in Android SDK directory)"
I'm on Windows 7 and there's no such thing on my c:drive. Under User, there is an ".android" folder, but I don't think that's it.
Hi pixie67,
sorry for my bad english, I'm a German speaking English writer.
in what way do you have adb drivers and fastboot drivers installed?
when did you proceed to the manual, you would still have a folder with android sdk?
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing". This is only for the 7 version of the device, the 8.9 version does not require the factory cable.
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
Click to expand...
Click to collapse
I have windows 7 and when I enter in the search window windows sdk, I find the folder.
mfg
GermanJPL
Hello,
I installed KindleADB.exe for the drivers. That seemed successful. I managed to root it ok,
My Kindle, in TWRP shows up in device manager as Android Phone/Android ADB interface.
I can boot into fastboot from the options in TWRP.
I've updated the android SDK package and rebooted my computer.
I can't use ADB sideload, it just sticks on "starting ADB sideload feature...."
If I reboot to system, I just end up on the white/blue logo.
I don't know what to do next
I do not understand ... have you thought you were the instructions?
you've got installed 2nd Boot Loader & TRWP after manual with ADB and fastboot .... ? why are you not looking adb.exe, then you have your folder
or you install you Andrid sdk subsequently follow the instructions, then you've got everything you need.
German JPL
I don't really understand your answer German, I've followed the instructions, but I'm still stuck on the boot screen, or in TWRP with no way to flash a ROM as there is no ROM on the device and I can't transfer a rom onto the device because mounting doesn't work and Adb sideload doesn't work.
So I'm stuck.
Help!
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
GermanJPL said:
You have written the sideload does not work because the can not find the sdk folder. Did you find it now and sideload does not work?
Before you experiment still around for hours, start your Kindle in fastboot and play the 3 img a backup folder.
After that you start from scratch and copy before the Rome and gapps on the Kindle.
German JPL
Click to expand...
Click to collapse
I can't find a SDK folder anywhere, I've searched, I've enabled hidden folders. I don't know if this is why the ADB sideload option doesn't work, but it doesn't, it just hangs there.
I can start the Kindle in fastboot, there is a message saying "installing device driver software", then another, confirming the ADB driver software has been successfully installed. In device manager I now see
Kindle Fire listed with android adb interface.
I don't know what "play the 3 img a backup folder." means. I'm sorry. While I'm in fastboot mode, I'm not sure what to do. Can you tell me?
And I don't know how to start from scratch as I can't copy anything anywhere. Although I can see the Kindle in device manager, I can't get to it in windows explorer.
The problem is, I didn't copy the ROM and GAPPS onto the Kindle before installing TWRP and now I can't.
Oh dear, I'm sorry to be so frustrating!! Thank you for trying to help though xx
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 8.9. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD8Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode. Place the folder and the files in it back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD8Backup
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
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Click to expand...
Click to collapse
German JPL
Thank you for helping me.
I can't transfer the 2 files as I can't access the sdcard, but I did do this initially.
Also, do I use the command prompt just from the desktop and will it work while I'm in fastboot mode as I can only get into fastboot or recovery. I can't boot normally.
I will give it a go anyway, I really am very grateful for your help
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
HELP
pixie67 said:
Well, I've done it!!
I made sure ADB was properly installed, following the video link German helped with. Had to make my own android-sdk folder on the C:\ drive. Put KFFirstAide100 and KFHD_SRT_v2.1 downloaded from here in the "platform-tools" folder, ran KFHD_SRT_v2.1 tool to get into fastboot (turn Kindle off first, press option 1, then n, then connect kindle to computer via cable. It will go into fastboot.
Then Go to Firstaide in fastboot mode and restore kindle via one of the options on there.
Now I'm up and running again. Yey!!
Thank you German for all your help!!:highfive:
Click to expand...
Click to collapse
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
OhhRey said:
I dont get how you fixed it i am a noob can you please send me everything i need to download and how to do it? I really need to get my kindle back so i can put my cm rom on it please!
Click to expand...
Click to collapse
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
HELP
stunts513 said:
This should do the trick(assuming you just want to push a rom onto your device), drivers are always in my signature, adb is in the zip on the tutorial i wrote a while back. Here ya go!
Click to expand...
Click to collapse
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
OhhRey said:
Good news and bad news, i installed the gapps and cm but it is stuck on the cyanogenmod screen and keeps looping. Please help! I thought i was done so close to a new android device! HELP!
Click to expand...
Click to collapse
Do a factory reset from twrp and see if it fixes the problem.
hi all
I have a problem on getting TWRP to work properly.
I initially used BreakDroid to install TWRP, everything worked fine.
I tried to install the cm-11-20140512.1655-SKANKY-otter.zip OS but I first got the "error 7", fixed that, and then it was stuck at "updating package" (or similar)....
then I saw an updated version of TWRP, without realizing that it was for an asys TF101 tablet (http://forum.xda-developers.com/showthread.php?t=2434422)...I installed that and now twrp doesn't work because the screen is the wrong size and I can't get to various buttons including flash/wipe etc..
I can still mount it tho so I thought about using adb/flashboot...but I can't seem to override that version of TWRP.
...best part...i cannot restore the original amazon OS since I didn't do a backup (...i know...:angel
does anyone have any idea about how I can fix that and install a kitkat rom?
I have nandroid backup of stock in my list.
sd_shadow's collection of links for: Kindle Fire 1
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
I have nandroid backup of stock in my list.
Click to expand...
Click to collapse
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
SbDROID2012 said:
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
Click to expand...
Click to collapse
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
sd_shadow said:
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
Click to expand...
Click to collapse
I did try to do that but
1)
adb shell
Click to expand...
Click to collapse
--> doesn't work and I get "error: device not found"
i did the "./android update adb" with "adb kill-server" and "adb start-server" but nothing changed..
2) I installed the img file anyway through
fastboot flash recovery
Click to expand...
Click to collapse
the img file but i still cannot get the twrp with the view for kindle...see attached image. i have NO ACCESS to some of the buttons, therefore I can't do much with it.
I would REALLY like to be able to install a CWM...i tried the one here http://forum.xda-developers.com/showthread.php?t=1454241 using
fastboot flash recovery cwm-file-here.img
Click to expand...
Click to collapse
but it gets to the boot page, I select "recovery" and then it's stuck with the kindle logo and the small "booting..." at the bottom of the screen...so I re-installed twrp even tho i still have that damn "build for Asus TF101 Series Tablets" (see attachment) warning on top!!
any help would be HUGELY appreciated!!
also, using "adb devices" I still can't see it.
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Duchman said:
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Click to expand...
Click to collapse
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
SbDROID2012 said:
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
Click to expand...
Click to collapse
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
sd_shadow said:
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
Click to expand...
Click to collapse
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
SbDROID2012 said:
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
Click to expand...
Click to collapse
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Duchman said:
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Click to expand...
Click to collapse
so..the problem with that is that I could not access the sdcard since adb doesn't work...however...as of now I've been able to fix the layout problem by using
fastboot -w
fastboot flash recovery twrp.2.7.0.1.img
fastboot reboot
Click to expand...
Click to collapse
once rebooting I had to re-wipe (advance wipe) sdcard/cache/data since when I tried to mount them I could not check the boxes.
now i STILL cannot mount it and adb does not recognize it.
I'm using mac and I tried
android update adb
Click to expand...
Click to collapse
but still adb can't see the kindle and I can't mount it through twrp
...however, I'm still able to reboot in bootloader and use fastboot
I don't think I can flash a .zip rom from fastboot tho...and I'm not sure how to transfer files on the kindle to flash them from twrp...any idea?
thanks a ton!!
-- edit --
i already modified the ~/.android/adb_usb.ini file adding 0×1949 and then running
adb kill-server
adb devices
but what I get is just
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
and nothing to it...the "adb shell" still gives me "device not found"!!
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
sd_shadow said:
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
Click to expand...
Click to collapse
SCORE !!!
dunno why twrp was the problem! the new recovery that you linked worked like magic, adb worked perfectly, I already flashed a rom and it works!!
so...why wouldn't twrp allow me to use adb or mount disks through usb?!
thanks so much for the help!!
Guessing it doesn't use the twrp theme, that was causing trouble.
Sent from my Amazon OtterX using Tapatalk
I'm sorry if this is not the right place to put this.
Before you go on:
This is not a guarantee that this will unbrick your device. This is how I fixed my kindle and I want to share how I did it since there is no tutorial on how to. As long as your device can boot, this method should work. Also, unless you have a kindle fire hd 8.9 rom, you will lose the stock os. THIS IS FOR THE KINDLE FIRE HD 8.9 (If you do not know what your's is, use a ruler)
Cause of brick:
Mine:
Installed Wrong Recovery On Device
(If you do this method and it works, please tell me so I can add it to the list)
Things You Need:
Windows OS (I don't know how to do this on linux)
Custom Rom (Cyanogenmod 11 or 12)
Android SDK
USB
Also twrp, uboot, and freedom boot that I got from this website
Tutorial:
Step 0:
Install Android SDK
Download all files given in "Things you need" (Put all in one place)
Step 1:
Put Kindle Fire HD 8.9 in fastboot mode.
Code:
fastboot -i 0x1949 getvar product
Step 2:
If you have not already, move the cmd to the directory with your files. (using the cd command)
Enter All These Commands In Order:
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Code:
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
Step 3:
Reboot into recovery
Code:
fastboot -i 0x1949 oem recovery
Step 4:
Push OS To Kindle Fire Hd 8.9
adb push filename.zip /sdcard/.
Step 5:
Wipe System
Step 6:
Install Your OS
And You Are Done!
Please Reply If You Have Any Questions
help please
when i type in fastboot -i 0x1949 getvar product then i hit enter it says waiting for device once i plug in my kindle hd 8.9 it just goes into the bootloop and doesnt go into fastboot mode what could be the problem? any idea of what it could be please tell me. i have the adb drivers installed.
albertferrari_1995 said:
when i type in fastboot -i 0x1949 getvar product then i hit enter it says waiting for device once i plug in my kindle hd 8.9 it just goes into the bootloop and doesnt go into fastboot mode what could be the problem? any idea of what it could be please tell me. i have the adb drivers installed.
Click to expand...
Click to collapse
I am currently looking for a solution. Sorry for the late reply, I don't come here often.
GoldenBullet72 said:
I am currently looking for a solution. Sorry for the late reply, I don't come here often.
Click to expand...
Click to collapse
So I ended up fixing my kindle with this works like a charm thanks a lot you are the best helped a lot there hahahaha.
Wanted to see if my problem was similar to the one that you had. I got my kindle rooted and to the point where TWRP is installed. I get the blue kindle logo but it never boots into the software again. I can hit the up arrow key during boot and get to the TWRP software.
My problem, is that when I plug my kindle into the computer, my computer sees the Kindle but I don't think that the "“Allow installation of Applications" and "enable ADB" are checked on anymore (or at least that's what it seems. The computer see's the device but I can't transfer my CM ROM to the device. If my ROM would have been on the device already, I can see the file folders on there and could select it from TWRP but the instructions that I was following had you move the ROM over to the Kindle AFTER rooting and installing TWRP..
I accessed the fastboot and followed the instructions. Perfect way to get the ROM onto the sdcard and that appears to work great. But as soon as try to flash the OS on on the device, I get the following.
Updating partition details...
Running boot script...
Finishing running boot script
Installing 'sdcard/cm121.zip'...
Checking for MD5 file...
Skipping MD5 check: No MD5 file found
Warning: No file_contents
detected filesystem ext14 for /dev/block/platform/omap/omap_hsmmc.1/by-name/system
detected filesystem ext14 for /dev/block/platform/omap/omap_hsmmc.1/by-name/system
ApplyParsedPerms: lsetfilecon of /system/bin/showlease to u: object_r:system_file:s0 failed: Operation not supported by transport endpoint
ApplyParsedPerms: removedattr of /system/bin/showlease to 0 failed: Operation not supported by transport endpoint
set_metdata_recursive: some changes failed
E: Error executing updater binary zip 'sdcard/cm121.zip'
Error flashing zip 'sdcard/cm121.zip'
Updating partition details...
Failed
Is this a a problem with moving over the file to the device? or is this a ROM problem? I tried using 2 different CyanogenMod 12.1 nightly downloads and got the same error message both times.
Any help would be appreaciated!
Update: Found my problem. was using TWRP 2.6. After I adb pushed TWRP 2.8.7 to the tablet and installed, I was able to install all varieties.
cweatherford7 said:
Update: Found my problem. was using TWRP 2.6. After I adb pushed TWRP 2.8.7 to the tablet and installed, I was able to install all varieties.
Click to expand...
Click to collapse
Hi cweatherford7.
I also have version 2.6.0.0 and the same problem you had.
I know how to push zip files and install them, but img files cannot be installed that way using TWRP.
Where can I get a TWRP.zip to install? Can you tell how you did it?
Thanks
flacogal said:
Hi cweatherford7.
I also have version 2.6.0.0 and the same problem you had.
I know how to push zip files and install them, but img files cannot be installed that way using TWRP.
Where can I get a TWRP.zip to install? Can you tell how you did it?
Thanks
Click to expand...
Click to collapse
I honestly do not remember the site that I got it from. I remember thinking the the download location was kinda sketchy.. i.e. Worried I was going to get a virus but everything turned out OK.
I do not have the tablet with me right now. It's at home. I don't remember how large of a file it was but if its small enough to email or something I could try to get it to you (if I still have it on my tablet)
The site for those files is gone.
Anyway, I can get into twrp just fine and even move files to it.
Can also flash CM- 11, 12 or 13 to it.
What I can't do, is get a complete boot up, after app optimization, it just never comes off boot screen and eventually returns to optimize screen again, and back to moving boot logo.
It's on 5.1.1 and was previously rooted.
UPDATE: I can install CM 13 and get full boot, but keep getting a bluetooth share message and play services message.
tia
GoldenBullet72 said:
I'm sorry if this is not the right place to put this.
Before you go on:
This is not a guarantee that this will unbrick your device. This is how I fixed my kindle and I want to share how I did it since there is no tutorial on how to. As long as your device can boot, this method should work. Also, unless you have a kindle fire hd 8.9 rom, you will lose the stock os. THIS IS FOR THE KINDLE FIRE HD 8.9 (If you do not know what your's is, use a ruler)
Cause of brick:
Mine:
Installed Wrong Recovery On Device
(If you do this method and it works, please tell me so I can add it to the list)
Things You Need:
Windows OS (I don't know how to do this on linux)
Custom Rom (Cyanogenmod 11 or 12)
Android SDK
USB
Also twrp, uboot, and freedom boot that I got from this website
Tutorial:
Step 0:
Install Android SDK
Download all files given in "Things you need" (Put all in one place)
Step 1:
Put Kindle Fire HD 8.9 in fastboot mode.
Code:
fastboot -i 0x1949 getvar product
Step 2:
If you have not already, move the cmd to the directory with your files. (using the cd command)
Enter All These Commands In Order:
Code:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
Code:
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.7.0.0-recovery.img
Code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
Step 3:
Reboot into recovery
Code:
fastboot -i 0x1949 oem recovery
Step 4:
Push OS To Kindle Fire Hd 8.9
adb push filename.zip /sdcard/.
Step 5:
Wipe System
Step 6:
Install Your OS
And You Are Done!
Please Reply If You Have Any Questions
Click to expand...
Click to collapse
@ant17 That seems like a Google play services problem. Make sure the gapps are for the right Android version and processor. You can also try a different rom like ressurection remix to see if the Bluetooth problem is fixed.
GoldenBullet72 said:
@ant17 That seems like a Google play services problem. Make sure the gapps are for the right Android version and processor. You can also try a different rom like ressurection remix to see if the Bluetooth problem is fixed.
Click to expand...
Click to collapse
I'm thinking maybe its not, as for bluetooth, I never use bluetooth. EVER
ant17 said:
I'm thinking maybe its not, as for bluetooth, I never use bluetooth. EVER
Click to expand...
Click to collapse
Is your jem an LTE version?
ong14 said:
Is your jem an LTE version?
Click to expand...
Click to collapse
YES!
ant17 said:
YES!
Click to expand...
Click to collapse
It's a common problem on LTE version.
ong14 said:
It's a common problem on LTE version.
Click to expand...
Click to collapse
Never had it before. Maybe I'll try 14.0 LO
I have two tablets, both lte versions, which were running fine for months. Now, both of them simultaneously are behaving like @ant17 describes. Tablet boots fine, but as soon as you swipe away from the boot screen it reboots.
I'd guess that google updated something, since I tried reflashing and things were fine until I installed gapps (the same one that I had been using forever).
I guess I'll try CM13.
kgoroway said:
I have two tablets, both lte versions, which were running fine for months. Now, both of them simultaneously are behaving like @ant17 describes. Tablet boots fine, but as soon as you swipe away from the boot screen it reboots.
I'd guess that google updated something, since I tried reflashing and things were fine until I installed gapps (the same one that I had been using forever).
I guess I'll try CM13.
Click to expand...
Click to collapse
The gapps became my problem and installing the correct gapps for your OS version IS NOT THE THING that ultimately worked. That's bad information.
There's an easy gapps thats only 55MB that finally worked. All the guidance that says which gapp to use in totally INCORRECT!
Called "working marshmallow gapps" (this works)
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
joes6789 said:
Have read a ton on XDA and elsewhere, to the point that I have too much information, and I think it's likely someone with more experience could point me to the right area to focus on. Any help is much appreciated! Thanks!
Where I started:
Was a total noob, had never tried to flash anything or use command line
One day my stock Kindle Fire HD 8.9 just stopped working on its own. Not sure why -- I never tried to root it or hack into it. I had left it plugged in for a week and it felt a little warm.
Powering on would get to the orange/white Kindle Fire screen, and then the screen would go blank and stay that way until powering off.
I just wanted to get the Kindle running again, preferably with stock OS or something that still allowed me to use Amazon Instant Video.
What I've accomplished so far:
Successfully got fastboot running! Originally through First Aide and now through command line too.
Successfully got TWRP 2.8.7 running! Downloaded the TWRP image and used fastboot to flash recovery.
Also flashed kfhd8-freedom-boot-8.4.6.img and kfhd8-u-boot-prod-8.1.4.bin from the instructions on XDA's 2nd bootloader page.
Tried using both First Aide and the SR Tool to restore system back to stock, but neither seemed to do anything. Even flashed the system.img included with the SR Tool manually using fastboot, but Kindle still won't successfully launch. Also tried the "Restore 2 Stock" program, which says it cannot find a device in TWRP mode (likely related to my ADB issue cited below).
Where I'm at now:
Now when powering on (in normal mode), Kindle stays at orange/white Kindle Fire boot screen forever. Screen no longer goes blank afterwards.
Can get to TWRP, but only by using "fastboot oem recovery -i 0x1949"
Strangely, ADB NOT working. While in TWRP mode, I use command line "adb devices" and it returns "B0C91004245614ME Offline". I'm pretty sure I have the correct ADB drivers (while in TWRP mode, device manager shows two entries: "Kindle ADB Mode" and "Recovery ADB Mode").
Obviously I have no backups of original system/boot images because the Kindle broke on its own and I've never seemed to have ADB access.
Questions:
Is there something big I'm missing in order to restore to stock? Intuitively, it seems like I should be able to just flash a working system image from fastboot. If I can't restore to stock, I'm fine installing another OS -- would just like to get the device working again.
I doubt I would have enabled ADB access before the Kindle broke. Is that the reason that the "adb devices" command returns "Offline"?
Have not tried gaining root access. Is that a prereq for using ADB and/or restoring to stock?
-Joe
Click to expand...
Click to collapse
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Regarding your questions:
1) Hashcode created a TWRP-flashable ROM zip for Amazon's stock OS., which you can find in this thread. You should download the 8.4.1 version from the d-h.st link in the thread, as the goo.im links no longer work because Goo.im (a former file hosting service for Android developers) shut down. However, beware the d-h.st (Dev-Host) links, as they are notorious for causing unwanted downloads and popups. Do NOT download anything executable (the file we want is a .zip, not anything else), as it can cause unwanted software or even malware to be inadvertently installed onto your PC (and in some cases, your android device).
2) Yes, that is why the command returns "offline" when you run it with the kindle in recovery mode.
3) No, root is not a prerequisite for either of those commands. (In fact, you'd have to have adb enabled before rooting the stock OS in most cases.) However, should you need root, the stock ROM that Hashcode built as a flashable TWRP .zip is rooted, and as long as you don't update the OS, your root should remain intact.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
joes6789 said:
Thanks for the answers and explanations Monster. I downloaded Hashcode's 8.4.1 ROM zip, but I cannot figure out how to copy the zip file onto my Kindle, given that I don't have ADB access.
I did some research and it seems that one workaround is to use the Mount USB Storage feature within TWRP, but I can't get that to work. When I try to Mount USB Storage, no new storage drive shows on my computer (nor in Disk Management), and the TWRP error log says "Unable to mount storage. Unable to mount '/data'. Unable to mount '/cache'. Unable to find storage partition to mount to USB." Furthermore, the mount menu in TWRP says "Storage: Internal Storage (0 MB)" -- that doesn't seem good.
Do you have any other suggestions, either on how to get the zip file on my Kindle, or another alternative method to get my Kindle functional? Perhaps flashing something else directly from fastboot? Again, appreciate the help!
Click to expand...
Click to collapse
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Boot into TWRP, then when you're in, choose Advanced -> ADB Sideload. Check the boxes that say "Wipe cache" and "wipe dalvik cache." Swipe where indicated to sideload, and hook up your kindle to your PC if it's not already connected. Type "adb devices" into a terminal/command prompt, and you should see a device that registers itself as in "sideload" in the list. If you do, then type "adb sideload path/to/file.zip", where path/to/file.zip is the location of the downloaded 8.4.1 ROM zip. The ROM should automatically copy and flash; keep the kindle plugged in until the flashing process is complete. Any luck?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
joes6789 said:
Yes, the adb sideload worked!!! (just had to update my adb version to 1.0.32) Kindle seems to be fully functional. Thank you so much Monster!
Last thing, do I need to worry about OTA updates or anything in the future that might create a conflict with the bootloader or ROM I'm using?
Click to expand...
Click to collapse
I believe that the OS is properly patched in Hashcode's stock ROM, so you shouldn't need to worry about OTAs or a conflicting bootloader. Glad to see it works again!
Sent from my Amazon Jem using XDA Labs
How were you able to get into fastboot with kf first aide? Which drivers and which options?
Gesendet von meinem Nexus 6P mit Tapatalk