First - sorry for my English. Last monday i received my KF2 and when I could not find the instructions on this forum for version 10.4.3 - i decided to try it myself.
Introducing: Kindle Fire 2 (v10.4.3 & v10.4.6 already tested) installing CyanogenMod
** YOU SHOULD HAVE A WORKING NORMAL (NOT FASTBOOT) CABLE + ADB DRIVERS/ACCESS ON YOUR PC. **
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
INITIAL SETUP INSTRUCTIONS
STEP 1. Install ADB Drivers for Kindle HD and enable ADB on tablet Settings->Security->Enable ADB->On
Check ADB:
Code:
C:\> adb devices
List of devices attached
0123456789ABCDEF device
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for ADB on your PC before proceeding.
STEP 2. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # This will take a few minutes
Take those files and put them somewhere safe.
STEP 3. Getting root
Just follow this threat http://forum.xda-developers.com/showthread.php?t=2075959 -> everything working fine
STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check this before using fastboot -- downloads CAN be corrupted)
Open cmd and promt:
Code:
adb shell su -c "reboot bootloader"
Your Kindle should reboot in fastboot mode, and now flash bootloader:
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 reboot
STEP 5. Install TWRP
First, download CM and GAPPS and copy it to SDCARD:
CM-10.1 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the top rom CM10.1 version)
1. Copy com.powerpoint45.FMKilo-2.apk to the tablet (you can get this apk from here http://d-h.st/n7L)
2. Enable on Kindle: Device -> Allow Installation of Applications
3. Use file browser (i recomended to use ES Explorer) to install apk.
4. Run Tweezermod Installer and answer on all question about Super User -> "Allow"
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
In this time your kindle can not boot, u'll see BLUE logo, then ORANGE and then device restarted again. Don't worry - it's ok
STEP 6. Install CyanogenMod
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
Dont forget to do FULL WIPE - cache, dalvik cache, factory reset, system.
Enjoy
Tested on my Kindle Fire 2 v10.4.3 & v10.4.6
7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.
pythonjosh said:
7" KF HD 2, 10.4.6
This tutorial worked perfectly, up until the end, step 6.
I'm new to Kindle, but not Android. I got into TWRP prior to downloading CM10.2 and Gapps. And when i try to mount as USB, and this line shows in the log:
"Unable to locate volume information for USB storage mode"
Googling didn't help much with investigating that error. ADB sideload doesn't seem to work.
I don't know what to do from here.
Click to expand...
Click to collapse
Check STEP 1 to check ADB. If it not working check this manual https:// developer.amazon.com/sdk/fire/connect-adb.html
When ADB start working - copy CM and GAPPS to kindle:
Promt in CMD:
Code:
adb push /path/to/filename /sdcard/download/filename
I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.
I found instructions via terminal emulator to get it rebooted into fastboot, in hopes of flashing CM 10.2 via fastboot.
Looking up the fastboot syntax for flashing a new rom, I've always used recovery on my other devices, but i don't have that option now.
pythonjosh said:
I'm also on Win7 x64.
When it is on ADB Sideload, I see in my Device manager Amazon Kindle Fire2, but it appears to not be loading the drivers correctly.
ADB Devices are not showing any attached devices. Ideas?
---------- Post added at 09:37 AM ---------- Previous post was at 09:29 AM ----------
Also in my Device Manager, Portable Devices, it shows F: but there's no F: in my windows explorer.
Click to expand...
Click to collapse
ADB Sideload - good idea. Try this manual:
1. Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
2. From the command line on PC, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
My mistake in manual. Better way - copy rom file to sdcard before STEP 5.
I'm still unable to use adb sideload, reports "device not found". I have the usb drivers installed, your tutorial is the only one I have used, I can't use TWRP at all.
It works, but USB drive mounting doesn't work, ADB sideload doesn't seem to work. No errors in the log, but ADB reports device not found.
I don't know what to do from here. It's nothing like 4EXT or CWM.
Ok so I have got it in fastboot by going to Advanced->Terminal, idme bootmode 4
Once in fastboot , fastboot -i 0x1949 devices returned a device number
I flashed CM10.2 using "fastboot -i 0x1949 flash system CM102.zip
Then I ran fastboot -i 0x1949 oem idme bootmode 1
Then rebooted, doesn't load ROM, got back into TWRP, changed bootmode back to 1, reboot, says I have no OS.
That's my current status. Seems others have been at this point before, still workin on this.
Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.
pythonjosh said:
Ok you can give up on thinking now, I've bricked it. No signs of life.
I flashed the 7.23 bootloader and TWRP 2.6 from: http://forum.xda-developers.com/showthread.php?t=2128848
via fastboot, and now it's done for.
Found a rooted one on craigslist for $120 to replace this one for my father in law.
I've rooted a good few other Android devices, but never a tablet, first try on a KFHD2.
I give up on Kindle's.
Click to expand...
Click to collapse
Don't trash the old one after u get the new one, we have a viable method now to unbrick a hard bricked kindle. The person behind the fix is working on a more user friendly version of the device that doesn't require soldering. Check it out: http://forum.xda-developers.com/showthread.php?t=2391047
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
kindle fire 2 completely dead
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:
jeffrey00345 said:
:crying: after
Code:
fastboot -i 0x1949 reboot
, my kindle fire just shutted off and never response again, who can help me? :crying:
Click to expand...
Click to collapse
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
thanks for your reponse I would try to get a replacement from Amazon.
---------- Post added at 03:29 PM ---------- Previous post was at 02:59 PM ----------
kurohyou said:
Assuming you have a Kindle Fire 2nd Generation, it's "hard-bricked."
Read the FAQ if you haven't already, specifically Q14 (although, read them all). Then, I would see if you can get Amazon to send you a replacement.
If they won't do that, take a look at this thread and this thread by me. As of now, I've succeeded in returning a hard-bricked KF2 to soft-bricked, but working out some bugs in order to return it to fully functional after that.
Click to expand...
Click to collapse
I have contacted Amazon and they said that they would send a replacement to me but now I'm worried because I didn't tell them that it was my fault, I just told them the Kindle is not working.Is this ok?
Trying to make it work
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?
"STEP 4. Downgrade your bootloader
Download the older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/o...rod-10.2.4.bin"
On 2nd gen Kindle Fire Non-HD. ver 10.4.6 rooted , can this step be completed without a fastboot cable?
I have the original usb cable. Maybe with Kindle Aide?
or tweezermod?
http://forum.xda-developers.com/showthread.php?t=2106463
Hello, I also I have the 10.4.6 rooted.
I have the same question that adaweawe, I can install bootloader / recovery with the original cable?
thanks
movesandpepper said:
I've followed the linked guide to installing the sdk and driver (windows 7 64 bit) and I still cannot get the adb devices to list the kf2. What am I doing wrong?
Click to expand...
Click to collapse
try other USB ports. one of my usb ports did not recognize. try install both driver exe from the zip.
Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
What I'm doing with the standard USB cable.
edit
After trying on a USB, now the error is this:
target reported max download size of 486539264 bytes
error: cannot load otter2-u-boot-prod-10.2.4.bin
galaxyn84 said:
Hello again.
I try, but I have a problem at this point:
fastboot-i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
Once put the kindle in fastboot mode, write the code in CMD and gets stuck saying <waiting for device>
Click to expand...
Click to collapse
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
" *Note: After several conference calls with the Amazon Development Team we found Amazon applied a patch to the Bootloader in an effort to lock down the Bootloader, this patch rarely causes the Bootloader to stick or Bootloop, please use the above link to release the Bootloader. We have removed this patch from the boot-prod.img eliminating future issues with recovered HD 8.9" users. "
http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
and
+Note: As of Amazon OS update 7.3.x+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2271909
applies to 2nd gen nonHD too i think
also hesitant to try tweezermod due to some bricks:
http://forum.xda-developers.com/showthread.php?t=2106463&page=4
I'm rooted and downgraded to bootloader version 10.2.3 and it still causes the red screen? I used the computer method and the terminal doesn't have any errors but recovery is not there. My Kindle Fire 2 is disconnected from wifi so it won't be updated to 10.4.1 Any idea why?
Click to expand...
Click to collapse
i really want to install cyanogenmod 10.1 on my rooted 10.4.6 without fastboot cable, but i think amazon updated bootloader to make it impossible without fastboot cable.
i disabled OTA updates and hope someone figures out 10.4.6 -> CM 10.1 without fastboot cable
adaweawe said:
how you get into fastboot mode? did u try Kindle First Aide?
i'm hesitant to try install new bootloader + TWRP on my kf2 without fastboot cable:
Click to expand...
Click to collapse
HI
I enter fastboot mode as shown in the tutorial
"" "" Adb shell su-c "reboot bootloader" "" "" "
I ask for superuser permissions, accept and restart in fastboot mode
Appear a black screen with fastboot logo in red, and a traffic light with flashing green light.
But I can not move from there ....
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
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Background/How I 'Bricked' It: I have a Kindle Fire 2 and was able to successfully unroot/flash Cyanogenmod 10 onto it. Worked perfectly for about 6 months, when I decided that it would be a good idea to flash back to stock so that I could give it to a relative. I have TWRP 2.3.3.0, so I used a guide on xda to do the following:
I used a guide from xda and followed these instructions
-Download latest KF2 stock software from amazon. Re-name the file to update.zip
-Moved it to the root of the SD card
-Booted in to TWRP
-Factory Wipe/Restore
-Wiped Cache
-Wiped Dalvik Cache
-Wiped System
-Installed the "update.zip"
-Wiped cache/dalvik again
-Rebooted
Unfortunately, wiping the system seems to have wiped the CM10 OS (ROM) that I had installed, and there was a failure in installing the amazon stock:
Installing '/sdcard/download/update.zip...
assert failed: is_substring ("Otter2 , file_getstring("/proc/product_name"))
E: Error in /sdcard/download/update.zip
(Status 7)
Error flashing zip '/sdcard/download/update.zip'
Updating partition details...
Trying to reboot the system from TWRP results in a message that states: "No OS installed! Are you sure you wish to reboot?"
Investigating using ADB: So it looks like I have no OS on the Kindle Fire 2. This seems to be a problem because without an OS, I am unable to use adb (from what I've read, no OS = no way to accept/authenticate the computer RSA fingerprint to whitelist the kindle and allow adb to function). Trying to use KFU, KFFirstAide, or the Kindle UnBrick Utility results in Error: Device offline or Error: Device not found types of messages (I am assuming due to the fact that I can't "turn" adb on by accepting the RSA fingerprint prompt)
What does Device Manager tell me? My computer can 'see' the Kindle Fire in device manager [as I stated earlier: My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles] but going to My Computer and looking under mass storage devices, the computer doesn't seem to recognize the device as a USB storage device, which is a problem because I can't drag/drop or push/pull files to the SD card so I can't try to flash anything *other* than the original file that failed.
Fastboot Mode...? From what I can tell (http://forum.xda-developers.com/showthread.php?t=1668159), my device is in fastboot mode. My Kindle screen hangs on the blue/white Kindle Fire logo screen, which from what I understand is hashcode's bootloader/fastboot screen. However, when I look at the Hardware IDs in the device manager, it tells me that my hardware IDs are:
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
So...my kindle seems to be stuck on the blue/white fastboot screen, but register on my computer as the stock kindle fastboot? I'm not really sure what's going on there, and couldn't find too many people with the same discrepancy that I have...
I tried plugging in my cord (making sure to use a USB 2.0 port), going into Command Prompt and using some fastboot commands. (ie: fastboot flash bootloader \path\update.zip) but all I get is a <waiting for device> for a LONG time. As in, a few hours. Some basic googling/investigation seems to indicate that I don't have fastboot drivers installed, OR that I wasn't running fastboot in an 'elevated mode' but I haven't been able to find too many details about how to fix those, IF that is the problem.
TWRP 2.3.3.0: I can get into TWRP recovery just fine, although I can't seem to figure out how to get files onto my device. So I've tried re-installing the original update.zip file that failed the first time several times, with no success. trying to 'Mount' the device doesn't seem to do anything (at least, my computer doesn't see the device as USB storage regardless of whether it's mounted or not) I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the adb sideload <filename> command just gets me an Error: Device not Found message. I thought maybe I could try Advanced --> Terminal Command, but have no idea how to do that or what it does, and most sites are very vague about the step-by-step details, so I didn't really touch it.
Not sure if this is relevant or not, but when my KF2 is plugged into (attached) to my computer with the cord and is in TWRP, device manager shows the device under 'Other Devices' --> Amazon Kindle Fire2, and there is a yellow triangle on it. Not sure why...going back to 'fastboot' mode gets rid of yellow triangles and is recognized as a Kindle Fire again.
At this point - I'm pretty much stumped and have (hopefully) demonstrated that I've done my best to do my own research/read through threads/done due diligence. Is there anyone out there that might have any suggestions? Or do I now have a very large paperweight?
ANY input/suggestions/encouragement is welcome! I absolutely and sincerely appreciate your time in reading through this thread and trying to help noobs like me!
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
...tried those, but maybe am doing them incorrectly?
mindmajick said:
Use fast boot mode to recover to stock: http://forum.xda-developers.com/showthread.php?t=2096888
Or
If you have access to twrp. Use the ADb sideload feature to push CyanogenMod or another ROM over.
One thing though- if you can boot into TWRP you didn't wipe the system partition. Twrp for kf2 requires a file named stack to be there.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Trying to use the ADB sideload feature to push CM or another ROM over doesn't seem to be working for me (unless I'm doing it wrong?)
I tried using Advanced --> ADB Sideload, but trying to send the file in Command Prompt using the "adb sideload C:\users\Name\update.zip command just gets me an Error: Device not Found message". Could I be using the command incorrectly?
Trying to use any fastboot command in Windows Command Prompt results in <waiting for device> to hang for hours, with no changes to command prompt and no changes to the kindle (still sits at the blue/white boot logo).
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Fastboot Drivers
mindmajick said:
Ah. Sorry. Missed that in the OP.
Sounds like you probably need the drivers installed.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Are there difference drivers for fastboot and adb? I don't get a 'yellow triangle' and my device manager identifies the device as a Kindle Fire [Android ADB Interface], so I thought I was okay.
Should I be looking for fastboot drivers?
And btw, thanks so much for your willingness to help and input!
ME TOO
Just purchased a KF from someone...thay had rooted it...I tried to unroot...got stuck...now mine is doing the same as yours. I hope someone has a fix for you as I too have a large paperweight.
Follow Up
tessa33 said:
I've read through hundreds of similar threads and haven't been able to find a solution - I'll gladly give up my firstborn (and/or make a paypal donation) to anyone who is able to help solve my issue!!
From my research, I seem to have no OS installed on the Kindle, and as far as I can tell, I'm booting into fastboot mode (screen hangs on the blue/white Kindle Fire logo, screen does not ever dim). I AM able to access TWRP Recovery, but don't have any backup to load from, am unable to successfully flash the ROM that I have saved to my SD card. My device manager recognizes the Kindle as a Kindle Fire (Android ADB Interface), no yellow triangles. Typing ADB Devices into Command Prompt gets me: [device number ] offline. Typing fastboot devices into Command Prompt gets me nothing (blank line).
Click to expand...
Click to collapse
tessa33,
I just sent you a response. Call me at 707-774-5923 when you have a moment.
Solution?
I figured I could post in this thread before staring my own because I am having a very similar issue trying to revert my Kindle Fire 2 back to stock from cyanogen so I can sell it. I downloaded the official software from Amazon but every time I try to flash it through TWRP I get the exact same error you were getting. Did anyone ever figure out how to resolve the issue for you?
Had the same problem, so I chatted with an Amazon associate, told him I turned it on one day and it showed the grey triangle and he sent me a new Kindle Fire 2nd Gen for free. Try that...
Sent from my iPhone using Tapatalk
Hello
I have rooted KF2 and I did factory reset I lost TWRP&Os I can see the device as ADB device, Howeverm when the device in fastboot the pc not recognize it.
issuing fastboot devices command return nothing.
I used ubuntu and windows still the same issue. any idea?
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)
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.