I got verygreen's CM10 to build finally, however after running all of the adb commands (I'm at the first fastboot command) my device is stuck in "Kindle Fire System Recovery". I tried unplugging it and powering it off, but running fastboot -i 0x1949 getvar product and plugging the device in will not boot into fastboot mode, just goes back into recovery. Factory reset gets about 1/5 done and then reboots back into recovery. ADB does not work either. Anyone know how to fix this?
I am running cm 10.2.
I tried to update twrp via the twrp app, my kindle shut down and loaded in to fastboot. Now every time i turn on the kindle it is stuck on fastboot please could someone help me
Interesting, never heard of that happening from a bad twrp flash, only bad kernel flashes. I would just try restoring the os with kffa and see if it will get past the initial kindle logo instead of going into fastboot, if it still doesn't I would try reflashing the boot loader. If it gets to the point you need to try reflashing the bootloader, i cant stress enough to check the md5sum of the bootloader file beforehand so you don't end up with a hard brick. You could also try two simple things first one is "fastboot -i 0x1949 reboot", the other is "fastboot oem idme bootmode 1” might be 2 not positive, followed by the previous command if it doesn't auto reboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try
fastboot -i 0x1949 oem idme bootmode 4000
Thanks
KFFirst Aide sorted it out, thanks for the advice.
Hello guys, need your help. Today i tried to update my TWRP Recovery to new version. Unfortunately i downloaded not what i needed (i downloaded openrecovery-twrp-2.7.0.1-blaze.img) and installed it via flashify app, then rebooted to check out my new Recovery but there was a bootloop with words "Fastboot Kindle Fire" on it, then i was trying to get it out from there by typing fastboot commands
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
but first one failed with FAILED<remote failure>, i started to panic and i flashed my old recovery .img via fastboot ( don't know why, don't ask :| ), then rebooted via fastboot reboot command, then same thing but even worse, now the fastboot logo lasts only 0.5 sec on the screen then black screen and PC can't recognize my KFHD7.
Please help don't know what to do :crying::crying::crying:
Got to FASTBOOT
Looped BAT with command 4002 and got my KF to fastboot mode again, what to do next?
SOLVED
RMetal said:
Looped BAT with command 4002 and got my KF to fastboot mode again, what to do next?
Click to expand...
Click to collapse
made it
I bricked my kindle fire 2nd generation after performing the steps called out here per cyanogenmod wiki for rooting kindle fire:
I was able to perform the following steps:
1. fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
2. fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.1-recovery.img
3. fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
4. (if using a fastboot USB cable swap to a normal USB cable before entering the next command)
5. fastboot -i 0x1949 oem recovery
after pressing enter on the "fastboot -i 0x1949 oem recovery" step, the screen went blank.
I have the factory cable, adb, fastboot, everything at my disposal, but the tablet won't turn on at all (it was fully charged before i started process, should have at least 80% left).
Please point me in the right direction. Thanks
My Kindle Fire HD is in a TEMAMWIN ecovery loop. The fastboot cable wont recognize the device for me to reflash the recovey img. What should I do?
jackjohns said:
My Kindle Fire HD is in a TEMAMWIN ecovery loop. The fastboot cable wont recognize the device for me to reflash the recovey img. What should I do?
Click to expand...
Click to collapse
If you're running Windows, install the Kindle drivers from this post. Also run the 15 second ADB installer found here, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle when you see <waiting for device>. If you get a string beginning with "jem" or "tate", then fastboot is recognized. At this point, you should reflash the recovery image. Also type fastboot -i 0x1949 erase system and fastboot -i 0x1949 erase cache. Once those complete, type fastboot -i 0x1949 reboot and try booting into recovery.
monster1612 said:
If you're running Windows, install the Kindle drivers from this post. Also run the 15 second ADB installer found here, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle when you see <waiting for device>. If you get a string beginning with "jem" or "tate", then fastboot is recognized. At this point, you should reflash the recovery image. Also type fastboot -i 0x1949 erase system and fastboot -i 0x1949 erase cache. Once those complete, type fastboot -i 0x1949 reboot and try booting into recovery.
Click to expand...
Click to collapse
Thanks! It worked. Only problem is... It isn't flashing the firmware... And it bricked into a normal over and over "kindle fire" logo. ?
jackjohns said:
Thanks! It worked. Only problem is... It isn't flashing the firmware... And it bricked into a normal over and over "kindle fire" logo. ?
Click to expand...
Click to collapse
Try flashing the second bootloader, freedom-boot, and TWRP images again in fastboot. You should have fastboot access at some point, even if you have to completely turn it off, run fastboot -i 0x1949 getvar product, and plug in the kindle when you see <waiting for device> to get it to boot into the bootloader.
Sent from my Amazon Jem using XDA Labs
It won't flash the boot images, just <waiting for device>
I have no OS, should I flash one and see if it helps?
jackjohns said:
It won't flash the boot images, just <waiting for device>
I have no OS, should I flash one and see if it helps?
Click to expand...
Click to collapse
Sure, but make sure you flash the 2nd bootloader via fastboot immediately after, or you may end up with a bricked device.
Sent from my Amazon Jem using XDA Labs
@monster1612 it is not flashing anything ? what should I do
jackjohns said:
@monster1612 it is not flashing anything ? what should I do
Click to expand...
Click to collapse
First off, you need to disable driver signature enforcement in order to install the Kindle drivers on Windows 10. Here's a tutorial to do just that. After you reboot, install the kindle drivers again, and perform another reboot when prompted.
Also, you can't flash .zip files via fastboot - that would be part of the reason as to why it's stuck. I suggest flashing TWRP, the second bootloader, and the freedom-boot image via fastboot first. Once those are complete, type fastboot -i 0x1949 oem recovery to reboot into TWRP, and then flash the CM ROM zip within TWRP.
Finally, make sure you include the -i 0x1949 parameter in all of your fastboot commands. This will ensure fastboot knows what device you're flashing.
Sent from my Amazon Jem using XDA Labs
@monster1612 thank you I will try that
@monster1612 also, the 7.2.3 uboot is a .bin. Will that work with fastboot? Or will I need it?
jackjohns said:
@monster1612 also, the 7.2.3 uboot is a .bin. Will that work with fastboot? Or will I need it?
Click to expand...
Click to collapse
Yes, it should work with fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yes, it should work with fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Now this
jackjohns said:
Now this
Click to expand...
Click to collapse
It looks like the fastboot flashing process isn't working because it's not being told where to flash each image. Go ahead and flash each of those files again as directed by Hashcode in this thread, under step 5. The flashing process should now succeed.
@monster1612 it flashed the uboot, freedomboot, and twrp ok, but the device is still in a bootloop. I even did it twice. What should I do?
@monster1612 now it wont even turn on. I tried fastboot 0x1949 erase system because i was just erasing everything and now it wont even turn on. Maybe it is just out of battery because Ive been at this for a couple of months....
jackjohns said:
@monster1612 now it wont even turn on. I tried fastboot 0x1949 erase system because i was just erasing everything and now it wont even turn on. Maybe it is just out of battery because Ive been at this for a couple of months....
Click to expand...
Click to collapse
I'd let it charge overnight. After that, try fastboot -i 0x1949 idme bootmode 4000 and then fastboot -i 0x1949 reboot. Does that quell the bootloop issue?
@monster1612 it has been plugged in for 45 minutes and isnt turning on. Could it be hard bricked?
jackjohns said:
@monster1612 it has been plugged in for 45 minutes and isnt turning on. Could it be hard bricked?
Click to expand...
Click to collapse
That's odd - try holding the power button down for 10 seconds, then turn it on and see if it boots.
Sent from my Amazon Jem using XDA Labs