Related
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
whitesalt said:
hello people,
about this guide http://forum.xda-developers.com/showthread.php?t=2128175
steps 3 and 4 do not work.
Where should I put the files that I download?
Click to expand...
Click to collapse
correct the question
fastboot does not respond.
the command adb devices yes
why???
whitesalt said:
correct the question
fastboot does not respond.
the command adb devices yes
why???
Click to expand...
Click to collapse
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
humpster said:
The device has to be in fastboot mode to show up via fastboot.exe
Regarding your issues flashing the bootloader/TWRP, try using FireFlash, an apk that automates the process of flashing the exploitable bootloader and TWRP, using the freedom boot.img and TWRP files from the thread you mentioned in your post They can be anywhere on the device storage.
Stick the FireFlash apk on the device storage, install it with ES File Manager, plug in the freedom boot.img into the boot slot and the TWRP img into the recovery slot, check the box to flash 8.1.4 bootloader if you aren't already using it (red letters will warn you if you aren't) and check apply stack override. also check disable auto recovery update. execute the flash, and you're done.You can also use FireFlash to easily update TWRP later on if you like.
Click to expand...
Click to collapse
found within the forum
I open Fireflash and find the inscription: warning: current bootloader not kfhd8-u-boot-prod-8.1.4.bin.
Can I switch back?
FlashBoot I click to go into the "flash install script" or "reboot into recovery"?
I can also directly follow the program? reliable?
thanks
is stuck to the initial written "kindle fire" orange. help!
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Hashcode said:
If you are not seeing the blue logo, then the 2nd-bootloader / freedom boot / twrp img is not installed correctly.
I will post a small set of instructions in a few mins. But they require you have a working fastboot connection.
Sent from my XT926 using Tapatalk 2
Click to expand...
Click to collapse
apparently neither do fastboot adb recognizes the device!
how can I check better?
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
whitesalt said:
I remember that already fastboot did not work before, so I installed Fireflash and finally brick
Click to expand...
Click to collapse
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Hashcode said:
Have you tried using KFFA found here:
http://forum.xda-developers.com/showthread.php?t=2096888
It has MANY options for fixing USB drivers, installing 2nd-bootloader, etc.
Click to expand...
Click to collapse
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
whitesalt said:
nothing happens! the program fails to work because it waits for the device that does not find! I ask amazon replacement?
Click to expand...
Click to collapse
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
GenghisKhan67 said:
What operating system are you using on your computer?
If using Windows 7 or 8: are your Kindle HD 8.9 drivers up to date? Check this thread out to uninstall and reinstall the proper drivers: http://forum.xda-developers.com/showthread.php?t=2069117 (it references another thread that helps uninstall "phantom" device drivers: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361)
We need a bit more information in order to help you out.
Click to expand...
Click to collapse
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
whitesalt said:
hello,
I use windows xp and windows 7, the guide can not use it because the kindle is blocked! the day after tomorrow comes the new kindle you help me not to make mistakes? I listed exactly what is right to do? remember that the error was born from the fastboot that did not work! thanks
Click to expand...
Click to collapse
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
GenghisKhan67 said:
My point is that it is crucial to have proper drivers present and working BEFORE you even get into fastboot mode.
I would recommend you go back and re-read Hashcode's thread. Back up your system files before modifying anything, so you can go back if anything goes wrong.
Click to expand...
Click to collapse
but if something goes wrong, without the fastboot mode you can not recover anything the same right?
Surely my mistake was not to test the fastboot. Why can not I work in the device?? for drivers?
I think my kindle volume button is broken. Every time I reboot the device it always enter safe mode.
I reflash the device to stock but the problem still appear, now I want to back to custom rom but I cannot get in to TWRP (the volume up button not working) so I stuck at blue logo.
Fastboot and ADB still working.
Is there any way to install CM10.1 using fastboot/adb only without TWRP?
You can still get into twrp without using volume button, you just need to run adb on your PC with your kindle connected and adb enabled as follows:
adb reboot recovery
Or try
adb shell "su -c 'reboot recovery'"
If it is the second one u can run it from a mobile terminal app on the kindle, just take off the adb shell part.
Once you have cm installed I know for a fact you can reboot into recovery from the shutdown menu, but u have to enabled developer stuff on cm after u flash it. You can tell I'm half asleep when I can't remember the proper term and say "stuff"... Anyways if you want feel free to try what I suggested or search around for what I suggested. I am going to bed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
TWRP problem
Hello people
First of all thanks Hashcode for putting so much effort into it
I ran into a little bit of problem
First off regarding the BLUE LOGO
I first get ORANGE then BLUE n then ORANGE again with the animation
Second regarding TWRP
I can't seem to get into recovery while pressing the volume up button
It gives me a bad boot kinda error n then takes me to Fastboot mode
I hope you guys can help me out with this
Thanks
EDIT
Thanks to the above post i was able to enter recovery
Now it gives me two options
1 reboot kindle
2 reset to factory defaults
Question : How do i install CM 10.1 from there
You apparently didn't follow the instructions in the 2nd bootloader thread very well because you seem to have skipped a step.
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
To further explain what soupmagnet means, you didn't flash twrp to your recovery, that's the stock amazon recovery and is completely useless.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I entered every command perfectly
Do i need to re flash TWRP????
If so , HOW???
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
rocketfans14 said:
Just putting this out, this is my first time rooting and 'trying to get android' on a device. I recently got a kindle fire 2nd generation but hated the UI and other stuff. My friend suggested me to try rooting it and turn it into an android tablet instead. Following the rooting guide in the forum, I have successfully rooted the device. The next step was installing the 2nd bootloader and TWRP. I followed Hashcode's guide
HTML:
http://forum.xda-developers.com/showthread.php?t=2100963
but got stuck at step 4, flashing the bootloader. I have searched the thread but have not seen anyone solving the issue I'm having. Using cmd, I got the device to boot into fastboot mode and tried to type in 'fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin'. However, it returned an error: cannot load 'otter2-u-boot-prod-10.2.4.bin' : No error. Can someone help me? Your help is much appreciated.
Extra Info:
Amazon Kindle Fire 2 on 10.4.8 (rooted and has SuperSU)
using Windows 7 as workstation
installed KFFirstAide (yes, I have tried option 40 but stuck on <waiting for device>)
Also, I have put the 'otter2-u-boot-prod-10.2.4.bin', 'otter2-twrp-2.6.3.0-recovery.img', and 'otter2-freedom-boot-10.4.6.img' files in the C:\KFFirstAide folder. (I was thinking this might be the reason why it is not working but cannot be sure)
Click to expand...
Click to collapse
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
stunts513 said:
Yea you are kinda right, its because you are running the command from the system32 folder, you need to be cd'd into the folder that the files are in to run that command so "cd c:\kffaide" or w/e first and then run that command. Make sure you check the md5sum of that file before you flash it so you don't end up with a hard brick.
Click to expand...
Click to collapse
I have checked the md5sum of the files using a program I found here on xda. I'll try to do the cd from file right now and I'll let you know how that went. Thank you for the quick reply.
Ok, I got it up to the TWRP recovery screen. But how do I continue to flash the stock in step 4 after installing cm10.2 and gapps? Also, I do not have a factory fastboot cable.
EDIT
After installing CM10.2 and gapps, I hit reboot on TWRP and has 'unfortunately, com.android.phone has stop working' message popped up on the screen. Is it because I haven't continue to the section "Flashing back to stock" in step 4?
EDIT2 (I don't think this is related to the bootloader problem but I would like some assistance)
I rebooted again and didn't get the 'unfortunately' messages again. However, when I plug it into my computer, the device doesn't charge when it is active but charges when I put it into sleep mode. Is there any way to fix this issue?
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
stunts513 said:
That's because a pc doesn't put out as much amperage as a charger so it doesn't charge unless it is idle. Btw I recommend flashing cm 11, it is more up to date and has has improvements made to it that I think aren't added to cm 10.2.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I see. Where can I find CM11 and how do I flash it? Is it just:
1.put the file into /sdcard
2.reboot into TWRP recovery
3.uh, wipe memory?
4.install CM11
5.reboot
correct me if I'm wrong. I wasn't sure if these are the correct steps because there are a lot of different guides and most of them don't have the same steps.
P.S. Since the kindle only has 8gb, is there a way to free up more memory on the device other than the needed memory space for the os?
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
stunts513 said:
You have to factory reset to goto it. Download latest gapps as well. It should be in the development section for kf2 here on xda. Lemme find a link.
Link found!
http://forum.xda-developers.com/showthread.php?t=2388569
As to freeing up space all I can say is delete stuff you don't need. I don't tend to get low on my hd but the again I have a 16 gb model.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
"Factory reset to go to?" Also, I should put CM11 zip and gapp in sdcard right?
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes, what I meant was you have to factory reset before flashing cm 11. Kinda like how Amazon os caused a few problems if you didn't factory reset first, same applies when going to cm 11 from a previous cm os.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I'm sorry if this sounds stupid but how do I factory reset my device? I've been working on rooting to installing bootloaders and finally at the point of getting android os on it non stop. Brain cells are dying rapidly...
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
stunts513 said:
In twrp hit wipe and choose factory reset.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Thank you so much for all the help. Everything went smoothly after your advises.
Update: It was running well for a while until when it ran out of battery and I recharged it, it won't boot into CM anymore. It just boots into TWRP recovery even if I pressed the option to reboot system and normal boot... What should I do?
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Hmm could be a few things, try reflashing then ROM and gapps again, I suspect something with the boot IMG or system image is messed up. If it were the boot IMG I would think it would kick into fastboot though. Feel free to do a wipe of system, cache, and dalvik cache before you flash anything(under wipe>advanced).
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I wiped what you said and tried to flash the rom and gapp but when booting, it will still boot into TWRP.
I'll briefly explain what I did prior to the issue.
After everything was all set up, I went to see if there were any updates which there was, the nightlies for CM 11 0518. I hit download and after download was complete, I hit the option "install and reboot". After the orange kindle fire logo came up and briefly after, the blue one, it boot into TWRP. I tried to reboot again but still no changes. So I went ahead and did a factory reset and flashed the two zip files again. The devices still boots into TWRP... I have no idea what to do afterwards and here I am requesting assistance from someone who knows things like these better.
Have you tried wiping internal storage? That's a last resort, maybe somehow your selinux xattribs got messed up. A internal storage wipe would clear them. But it will wipe your sdcard area so backup anything you want to keep over adb first.
Sent from my Amazon Tate using Tapatalk
I haven't tried wiping the internal storage yet. How do I backup over adb? Also,since you said this might be a last resort method, if it fails, is there no other way to fix it? Not even restoring back to its out of the box state and start all over again with rooting and installing bootloaders etc?
PS. I don't know if it is related to what you are talking about at all but when I plug it into my computer, it doesn't recognize my kindle fire.
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
It should be recognized as an adb device when plugged in while in recovery, in which case your could run
Code:
adb pull /sdcard/ sdcard/
And it should pull it, though that syntax may have been a little off, seems like the syntax when pulling a entire directory isn't quite the same as when pushing one if I remember right but I might be wrong.
You could technically try to restore it with kffa by reflashing to stock, but I don't advise doing that just yet because fastboot is rather limited in comparison to twrp recovery. Twrp gives you access to Linux shell commands over adb whereas fastboot does not and gives you simpler commands.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
So in short, to backup, I can just use a adb pull command?
After that, I am lost. I don't really understand what you are saying...
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes just type
Code:
adb pull /sdcard/
and it will pull everything into the directory you are in, which gb be messy if you execute from something like kffa because vBulletin I don't believe it will create a folder called Edward and put the rules there, it will just put all the files right there so it's recommended to specify an empty directory at the end if that command. The rest of the other post was about the comparison if fastboot versus and access. Kindle fire first aid could try to restore it but if something screws up along the way you won't be able to have as much flexibility as you do with twrp to try and fix it. This is hard to explain from my phone...
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
So the steps are something like:
Backup with adb
Wipe internal storage
Flash the rom and gapp?
Alternative solution:
Restore the whole device
Repeat the root process
Installing the 2nd bootloader again
Flash rom and gapp
And the rest is if I were to restore the device, it is more flexible to use kindle fire first aide than to use TWRP?
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
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?
I'm not an expert by any means at customizing my android devices, so please bear with me.
I have a Kindle HD 8.9. I successfully rooted and installed a CyanogenMod on the Kindle, but my whole reason for trying to mod the Kindle was to get to a version of Android that the Sonos App would run on, and unfortunately the CyanogenMod I chose was too old (I was Android 4.3 and I needed 4.4 or later). I found later builds of mods for the Kindle but none of them would flash successfully, giving me errors where research indicated that my version of TWRP was too old and needed updating. This is where things went very, very wrong.
I downloaded the TWRP app and tried to update using that. No luck. I couldn't figure out how to update TWRP so I got desperate and started doing stupid things. I downloaded a zip file with the latest versions of the img files from TWRP and having no idea what I was doing, in fastboot mode, started flashing IMG files. The last thing I remember doing was flashing the boot.img to the device.
I'm in a situation now where the device will only boot into fastboot mode (when powering on + volume up button). I can see the device in Windows 1 0 device manager and I have the ADB device driver installed properly, but I just can't communicate with the device via ADB. "adb devices" command shows no devices, fastboot devices shows nothing. It seems like a driver issue but I've tried everything I can think of there. So windows can see it, but ADB cannot and at this point I'm totally stuck. I understand that I may have destroyed the tablet at this point but it seems like if Windows can see it, there should be *something* I can do to fix this.
If anyone has any suggestions, I'll try anything and appreciate any attempts to help me out of this mess.
Resolution
I've been struggling with this issue for weeks and no sooner did I post the question here did I find the solution. So, in case anyone else ever has the same issue as me...
When I originally rooted and modified the tablet I was following instructions from a website that had me modify the adb_usb.ini file in my .android directory to include the following: 0x1949. I honestly don't know what that is, some sort of memory address or hardware ID or something... something specific to the Kindle HD 8.9 device I think.
After spending the afternoon browsing the web for solutions I ran into something somewhere that talked about the vendor specific information in the adb_usb.ini file. This made me investigate that part further and I discovered that something I did along the way changed whatever that number is from 0x1949 to 0x1950. I found that out by right clicking on the device in device manager and selecting "properties" then selecting the "Details" tab and selecting "HardwareIds" from the dropdown. The number that showed up there had a 1950 in it and even though I had no idea what I was doing, I figured what the heck, try modifying the adb_usb.ini file to 0x1950 instead.
That change allowed me to see my device when typing "adb devices" at the command prompt and from there I was able to figure out how to update TWRP and finally load a more current ROM. And it *was* an outdated version of TWRP that was preventing me from installing the later versions of the ROM. Once I updated that, then the ROMs flashed without error (as soon as I figured out I needed to be VERY PATIENT because the ROMs took a long time to flash and went to a blank screen several times).
I am now happily running cm-13.0-20160807-UNOFFICIAL-jem on my Kindle HD 8.9 and have successfully installed Sonos app and am operating our Sonos system from this device.
I hope this info helps someone. I wish I was more technical and understood what I did to break things and what I actually did to fix them, but it worked so I guess I won't complain.
Kfhd 8.9 bricked?
I know this post is old but I need advice/help.
Have a Kindle fire he 8.9 tried to do a full conversation but after trying to flash room I can now only get the white/orangeish logo or I can get in to fastboot via "fastboot -i 0x1949 getvar product" I can also flash files ie recovery.img boot.img system.img ect but can't get back in to recovery or os. The restore tool seems to work but don't. At the end if my Whit's any help would be appreciated