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.
Related
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s
antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .
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
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?
Hello,
I am trying to update from the old cyanogen recovery to the TWRP recovery in this post: https://forum.xda-developers.com/showthread.php?t=3557606
I have enable to write the cyanogen recovery in the developer options.
I have rebooted into flashboot and executed:
----
[email protected]:/tmp/xperia/TWRP# adb reboot bootloader
[email protected]:/tmp/xperia/TWRP# fastboot flash recovery twrp-3.1.1-0-z3c_V02.img
target didn't report max-download-size
sending 'recovery' (14296 KB)...
OKAY [ 0.572s]
writing 'recovery'...
OKAY [ 0.930s]
finished. total time: 1.502s
[email protected]:/tmp/xperia/TWRP# fastboot reboot
rebooting...
----
Unfortunately the system boots in the cyanogen recovery anyhow.
does anyone knows what am I doing wrong ?
Many thanks in advance
There's an app called NDR Utils that lets you choose which recovery to boot to, but I don't know of a clean link where you can get it.
I got it with Nut's Dual Recovery:
http://nut.xperia-files.com/path/XZDualRecovery/XZDualRecovery_2.8.26
I mean you have to unlock your bootloader with:
Code:
fastboot -i 0x0fce oem unlock 0xhex_unlock_key
(see here)
also you have to erase the old recovery with:
Code:
fastboot erase recovery
(claimed in this guide here)
Edit: I forgot you used a CyanogenMod Recovery, which is stored in FOTAkernel,
so you have to use also :
Code:
fastboot erase boot
fastboot erase FOTAKernel
I did read it here
Hope that does help you
Thanks a lot !
imascara said:
Thanks a lot !
Click to expand...
Click to collapse
I updated my last posting
Got my bootloader unlocked, but when trying to flash or unlock critical I get an error and it goes to a screen with the razer logo, "powered by android" at the bottom, and super small text in the upper left "press any key to shutdown"
and shows this in the cmd window:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing unlock_critical
< waiting for any device >
...
FAILED (command write failed (No error))
finished. total time: 0.027s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a arter97-kernel-r9-20190607.img
< waiting for any device >
target didn't report max-download-size
sending 'boot_a' (30140 KB)...
FAILED (command write failed (No error))
finished. total time: 0.011s
I do have the full sdk package and used android studios sdk manager to get the latest google usb driver.
HTML:
EDIT: Also I'm on a global version (bought it on razer's website)
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
blackknightavalon said:
Download any version of the firmware available on the Razer developer portal then run the flash-all script. Once that's done, flash boot and system images separately on both partitions just to be on the safe side. Your phone should be able to boot normally after that. Just run setup, flash arter97's kernel, boot into TWRP and try to enter your lock code (odds are this'll fail), then reboot into TWRP, this time your password/lock code should work, then flash Magisk
Click to expand...
Click to collapse
Running the flash_all script just throws it into that shutdowns again and keeps going into it anytime I go back into fastboot mode.
also gives me this
Code:
C:\Users\zacha\Desktop\platform-tools>fastboot devices
my S/N fastboot
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed.
or is just sits there likes this:
Code:
C:\Users\zacha\Desktop\platform-tools>adb reboot bootloader
C:\Users\zacha\Desktop\platform-tools>flash_all
C:\Users\zacha\Desktop\platform-tools>set fastboot_cmd=fastboot
C:\Users\zacha\Desktop\platform-tools>fastboot flash partition:0 gpt_both0.bin
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
blackknightavalon said:
In that case, fastboot flash each part individually under both partitions (where applicable) and you should be back to stock
Click to expand...
Click to collapse
Just does the exact same thing.
Cyclo_sarin said:
Just does the exact same thing.
Click to expand...
Click to collapse
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Razer recommends you use a USB 3 Type-A to Type-C spec-compliant cable for any device flashing.
Click to expand...
Click to collapse
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
xCROv said:
I'm having the exact same issue. I'm unable to get any flash to work. Tried multiple different machines. Keep getting the same errors. Did you find a solution?
Code:
c:\adb>fastboot flash partition:0 gpt_both0.bin
Sending 'partition:0' (44 KB) FAILED (Write to device failed (Invalid argument))
Finished. Total time: 0.005s
Then my RP2 will go to the "Powered by Android" screen with the Razer logo and say "Press any key to shutdown"
I can use "fastboot devices" and get my devices serial number back along with rebooting the bootloader so I don't think it's a driver issue. Out of options and could use some help. At this point I can't even get the factory images to flash.
RP2 - ATT
Click to expand...
Click to collapse
BeardKing said:
Incorrect cord?
https://developer.razer.com/razer-phone-dev-tools/factory-images/
Or old ADB/Fastboot: https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Have ya'll tried using this tool?? It works I'm telling you it'll solve any issues you have with ADB and or FASTBOOT period....
https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445