Hi,
I am really hoping someone can help. My first attempt at upgrading my Fire HD using flashfire has red bricked it before it even got as far as installing twrp.
I bought a fastboot/factory cable and a few times it has showed the fastboot screen but adb does not list the device and so the tools just say waiting for device.
I have tried multiple versions of the adb usb drivers but none have worked so far when using the fastboot cable. I am using Windows 10 laptop but I also tried win7 desktop with the same lack of results.
I am stuck.
There seems to be as many ways to fix this as there are users who have bricked their kindle.
adb doesn't work in fastboot mode. Try fastboot devices. If you want out of fastboot try, fastboot reboot. Remove the cable before it reboots.
While in fastboot you could flash TWRP. Make sure the img file is in the directory you are in. Type fastboot flash recovery twrp(whatever filename).img
You can get into recovery by holding down the power button and volume up. Let go when the blue fire shows up.
The volume button is broken so it does limit my options.
I just found that to get into Fastboot I have to plugin to the laptop with the fastboot cable and then switch on the KFHD immediately.
> fastboot devices
returns nothing.
> fastboot reboot
says <waiting for device>
Same with the fastboot flash recovery command using either cable.
Then using the normal usb cable I opened Win Device Manager and under the Android Device entry I changed the driver to Android Bootloader Interface. This seems to have helped.
>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: -0.000s
>fastboot -i 0x1949 erase boot
erasing 'boot'...
OKAY [ 0.703s]
finished. total time: 0.703s
So I am currently using ULTIMATE KINDLE FIRE HD UNBRICK TOOL to erase everything and hopefully I can install something afterwards.
I will report back if I succeed.
Many thanks for helping.
It took 2 attempts but it has just finished wiping and installing the os (version 7.3.0 which is lower than the one I had before I think) and has successfully rebooted. Phew!
Thanks again for pointing out my newbie errors.
I now need to work out how to do this properly and which version I can safely update to without bricking the device. The LineageOS website is a bit contradictory. Maybe CM will be better ?
I'm running a cm12 nightly build. Anything more and you lose the camera and HDMI output.
Which bootloader driver did you install? By that, I am referring to the hardware I'd.
ps68060 said:
The volume button is broken so it does limit my options.
I just found that to get into Fastboot I have to plugin to the laptop with the fastboot cable and then switch on the KFHD immediately.
> fastboot devices
returns nothing.
> fastboot reboot
says <waiting for device>
Same with the fastboot flash recovery command using either cable.
Then using the normal usb cable I opened Win Device Manager and under the Android Device entry I changed the driver to Android Bootloader Interface. This seems to have helped.
>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: -0.000s
>fastboot -i 0x1949 erase boot
erasing 'boot'...
OKAY [ 0.703s]
finished. total time: 0.703s
So I am currently using ULTIMATE KINDLE FIRE HD UNBRICK TOOL to erase everything and hopefully I can install something afterwards.
I will report back if I succeed.
Many thanks for helping.
Click to expand...
Click to collapse
you have to put -i 0x1949 in front of ALL your commands. Its a vendor ID for amazon and its the only way to fastboot to the device. (example: fastboot -i 0x1949 reboot, fastboot -i ox1949 flash recovery yeeee.img, etc.)
just trial and error it.
Also to use TWRP (temoporarily) run "fastboot -i 0x1949 boot [path to recovery image]"
On latest platform tools the -i option is gone so where can we get the older fastboot executables?
Related
does anyone know where to get help with fastboot in ubuntu? i have tried flashing a recovery image to my Dell Streak 7, but it keeps failing. fastboot is working, and when i send the command "fastboot reboot" it works fine. however, "fastboot devices" returns "????????????". when i try to flash the recovery, i get
"sending 'recovery' (3654 KB)...
FAILED (command write failed (No such device))
finished. total time: 0.000s"
"fastboot getvar version" returns version: LG7 0.4
so i know fastboot is working, and that it has at least some communication with the tablet, but something is not quite working. any ideas?
SOLVED
i'm not sure what happened differently, but i plugged the tablet into a different USB port, and then i got a max-download-size error when flashing the recovery. i came across another post that said to use "fastboot -S 0 flash..." to resolve that error, and it worked. everything seems to be good now
The original question was posted here.
I decided to move it over here.
Hashcode said:
Can you try "fastboot -i 0x1949 oem recovery"?
Click to expand...
Click to collapse
When device is disconnected, I type in terminal:
Code:
fastboot.exe -i 0x1949 oem recovery
<waiting for device >
Then I connect kindle and see this:
Code:
....
OKAY [ 0.003s]
finished. total time: 0.011s
But after restarting the device I get the same white & orange logo and device reboots infinitely.
Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....
Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.
i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:
Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.
Wipe cache through fastboot and try again. It van help
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!
Kindle Fire HD 7" 2nd Gen - Kindle logo boot loop - unable to erase cache / userdata
Hello,
I've been googling and found a few tips to help me deal with a Kindle Fire HD 7" 2nd generation that is stuck in a Kindle Fire Logo loop. It's a friend's and they never tried to hack or root it from what I understand.
I have a fastboot cable and it comes into fastboot mode when connected. Fastboot sees the device (the adb command does not seem to - is that normal w/ the fastboot cable? The Macbook does NOT see the device with a standard USB cable).
I do "fastboot -i 0x1949 getvar product" and get
product: Tate-PVT-08
finished. total time: 0.000s
But when I do "Fastboot -i 0x1949 erase cache" or "erase userdata", it seems to "hang" (and it seemed to hang the macbook, too)... after hardbooting the macbook, the Kindle was back in boot loop, and the recovered Terminal showed:
Rick's MacBook Airlatform-tools rick$ ./fastboot devices
2C66000200000001 fastboot
Rick's MacBook Airlatform-tools rick$ ./fastboot -i 0x1949 erase userdata
ERROR: usb_read failed with status e00002ed
erasing 'userdata'...
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 0.002s
(it certainly didn't return in 2 thousands of a second!)
The window with Erase Cache (which I started first) never returned anything.
I then tried to execute the fastboot command prior to connecting the KFHD2; this is what happened then:
Rick's MacBook Airlatform-tools rick$ ./fastboot -i 0x1949 erase cache
< waiting for any device >
erasing 'cache'...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (Operation timed out))
finished. total time: 11.393s
Rick's MacBook Airlatform-tools rick$
Oddly, after this happens, the keyboard and pointer on the Mac stop responding! I have to hardboot the computer.
I just want to return this device to standard factory settings so my friend's kids can use it.
Any help is appreciated - I am an Android/Fire novice.
Thank you!
elwynor said:
Hello,
...
Thank you!
Click to expand...
Click to collapse
Try fastboot -i 0x1949 oem recovery. the Kindle should boot into recovery, from which point you can factory reset.
Sent from my Amazon Jem using XDA Labs
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
I've managed to resolve it for anyone else that might read this....
Follow the guide here https://forum.xda-developers.com/tr...f701t-nvflash-unbrick-solutiontested-t3742848 and use the NvFlash TF701T Unbrick tool, you need to do a bit of prep but it worked for me
Big thanks to Mr.Bin for this fix.
Cheers and good luck
Martin
martinnut said:
I've just purchased an Asus Transformer TF701T from a friend at work. It was working perfectly and I was able to restore all my apps as I previously used a Nexus 2013. The pad was running with an older version of Android 4.4.2 so I decided Id like to flash the device to get a newer version but I was unable to unlock it via the Asus unlock tool as I when I ran it, I was getting an "unknown error occurred which may be a network connection issue. Please wait and try again later" message. I tried all the usual fixes, removing my Google account, unlocking the 2 factor authentication etc, but the same error persisted. I then read a few posts and hit upon the idea to flash the firmware via the Bootloader and followed the various guides and got things setup this evening. I am using the Minimal ADB and Fastboot drivers.
So I can get the tablet to the bootloader screen without issue, with the 3 icons RCK, Android and Wipe Data and it responds fine to fastboot commands, even reboot works. So I entered the following after getting the UL-K00C-WW-11.4.1.30-user.zip firmware 11.4.1.30 from the Asus website (it used to have WW 11.4.1.17) and unpacked to my ADB folder. These are the commands I used which are all successful:-
fastboot erase system, fastboot erase recovery, fastboot erase userdata, fastboot erase boot, fastboot erase misc, fastboot erase cache. So far so good!
However, the penultimate command fastboot -i 0x0B05 system blob results in the error in the subject (exact copy of the output below)
Now the tablet just comes up with the Asus logo and in red "Unrecoverable bootloader error (0x00000000)." and only changes if I force it into the bootloader again. I can move between the 3 options ok.
Is there any way of recovering from this? is the problem that the tablet is still locked? I'd really appreciate some help if possible, thanks in advance Martin
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -i 0x0B05 flash system blob
target reported max download size of 643825664 bytes
erasing 'system'...
OKAY [ 1.021s]
sending 'system' (1781 KB)...
OKAY [ 0.266s]
writing 'system'...
FAILED (remote: Unsupport Flash Unsparse System Image.)
finished. total time: 1.323s
Click to expand...
Click to collapse