Has anyone had any success getting a factory cable to enable fastboot on the 8.9? I've had no luck. I'm thinking amazon locked out this method. It can still be accessed using adb but that doesn't help if you are in a boot-loop and can't get adb to recognize it.
What about using
fastboot -i 0x1949 getvar product
that works for the fire to put it into fastboot, even when ADB does not see it.
mdblaze said:
What about using
fastboot -i 0x1949 getvar product
that works for the fire to put it into fastboot, even when ADB does not see it.
Click to expand...
Click to collapse
Did you test?
It does put it into fastboot. I put it into fast boot and was able to take it back to normal boot.
Sent from my Kindroid Fire Bean
adb reboot bootloader will take you into fastboot mode on the KF HD7, probably work on the 8.9 too.
mdblaze said:
It does put it into fastboot. I put it into fast boot and was able to take it back to normal boot.
Sent from my Kindroid Fire Bean
Click to expand...
Click to collapse
Just to confirm, you had the power off to the device and plugged in a factory cable and the device booted into fastboot? Like I said I can get it to boot into fastboot through adb, but if the device ever gets into a loop i want to be able to get into fastboot via factory cable. Maybe my factory cable is not working properly, it was starting to act funny on the KFHD 7 but it would still work to get into fastboot.
mdblaze said:
What about using
fastboot -i 0x1949 getvar product
that works for the fire to put it into fastboot, even when ADB does not see it.
Click to expand...
Click to collapse
Just tried this. Suprisingly it works. I thought that command was just used to get the product info. I had the device powered off, typed the command(says- "waiting for device") , and plugged the device in- voila fastboot mode.
Thank you.
Edit: Any fastboot command entered before the device is turned on will enable fastboot mode as soon as it is powered on.
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?
Please help in big trouble.. my phone is stuck at Fastboot screen.. Nothing is working no volume keys nothing... What did i Do:
Unlocked bootloader...
and then I was trying to flash a custom recovery but after typing fastboot boot recovery.img.. it showed something like booting and then it finished.. Then in the tutorial it was written :
Perform a nandroid backup.
After nandroid backup is done, reboot the device in fastboot mode again.
In the Command Prompt type following command: fastboot flash recovery recovery.img
BUt i didn't performed a nandroid backup and straight after fastboot boot recovery.img was done I typed fastboot flash recovery recovery.img.... and now nothing is happening so I quit command prompt and unplugged usb but still I cant do anything and the phone is stuck at fastbood mode. When i am trying to connect usb it's saying usb not recognized... PLEASE HELP ME!
PC is not detecting my phone now.
anuragvivek93 said:
Please help in big trouble.. my phone is stuck at Fastboot screen.. Nothing is working no volume keys nothing... What did i Do:
Unlocked bootloader...
and then I was trying to flash a custom recovery but after typing fastboot boot recovery.img.. it showed something like booting and then it finished.. Then in the tutorial it was written :
Perform a nandroid backup.
After nandroid backup is done, reboot the device in fastboot mode again.
In the Command Prompt type following command: fastboot flash recovery <name of recovery>.img
BUt i didn't performed a nandroid backup and straight after fastboot boot recovery.img was done I typed fastboot flash recovery recovery.img.... and now nothing is happening so I quit command prompt and unplugged usb but still I cant do anything and the phone is stuck at fastbood mode. When i am trying to connect usb it's saying usb not recognized... PLEASE HELP ME!
PC is not detecting my phone now.
Click to expand...
Click to collapse
Not sure what thread you are following.. but steps don't sound correct.
Depending on the hboot you are on the fastboot boot recovery.img.. doesn't work.
to flash recovery you should have used fastboot flash recovery recovery.img
what happens if you hold down volume button and power for 10-20secs will it reboot to bootloader? If so from bootloader hit the power button to get to fastboot USB then select reboot option.
If nothing is working other option let phone go flat, then recharge and try again.
Is your device s-off?
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
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
gmoura5010 said:
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
Click to expand...
Click to collapse
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
rodrimx4 said:
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
Click to expand...
Click to collapse
Thanks, I was able to repair after unlocking the bootloader again and then unlocking the critical parts, so I flashed a stock rom from August 2018, however didn't block the bootloader again.