Plz help me out guyz.
I have HTC Desire 816G dual sim with MTK6582 chipset. The problem I'm facing is that when I connect my phone in ON state to my PC and run the command "adb devices" it shows my device, but when I get into fastboot mode and connect my phone to pc and run the same command my device is not shown, and also when I enter the command "fastboot oem get_identifier_token" (as I am trying to unlock my bootloader) it says
FAILED: (remote : unknown command)
Finisher. time taken 0.005s
Don't know what's the problem.
Someone please help me .
I'll be very gratefull.
I have unlock Xiaomi Mi 6, And I can use the windows flash tools to flash new rom in fastboot mode.
But got no response even I type "fastboot reboot".
Did I miss some steps?
I use the lastest develop version.
$ lsusb.py
2-4 18d1:d00d 00 2.10 480MBit/s 160mA 1IF (Google Android e276dec5)
I have tried "-i 0x18d1"
And I have installed android-udev
$ fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (Success))
finished. total time: 0.000s
yangtsesu said:
$ fastboot reboot-bootloader
< waiting for any device >
rebooting into bootloader...
FAILED (command write failed (Success))
finished. total time: 0.000s
Click to expand...
Click to collapse
does fastboot recognize your device?
type "fastboot devices", terminal should give you a sort of string of numbers and letters
Pendragon2000 said:
does fastboot recognize your device?
type "fastboot devices", terminal should give you a sort of string of numbers and letters
Click to expand...
Click to collapse
$ fastboot devices -l
e276dec5 fastboot usb:2-4
yangtsesu said:
$ fastboot devices -l
e276dec5 fastboot usb:2-4
Click to expand...
Click to collapse
fastboot recognizes your device. Mhmmm do you use root privilege?
Pendragon2000 said:
fastboot recognizes your device. Mhmmm do you use root privilege?
Click to expand...
Click to collapse
I have tried root and adbusers.
None of these works.
adb is 2717:ff48
fastboot is 18d1:d00d
I have wrote a 51-android.rules myself.
It do not works too.
OEM lock in Developer Options is grey,And I can not change it.
yangtsesu said:
adb is 2717:ff48
fastboot is 18d1:d00d
I have wrote a 51-android.rules myself.
It do not works too.
OEM lock in Developer Options is grey,And I can not change it.
Click to expand...
Click to collapse
Do you have the chance to test fastboot with another computer/ windows?
It could be a driver issue.
If the OEM unlock option is grey then the unlock should be fine.
Dobsgw said:
Do you have the chance to test fastboot with another computer/ windows?
It could be a driver issue.
If the OEM unlock option is grey then the unlock should be fine.
Click to expand...
Click to collapse
I have test on Windows,But with the fastboot.exe compiled by Xiaomi. It works fine.
I do not have chance to test with the origin one.
I use Archlinux latest.
Maybe the issues is fastboot/adb binaries being too old. Remove fastboot/adb and use this script https://drive.google.com/open?id=1lh-nOrpeeJrEeLrBO6i9-aLgWfSVD05b
Try using sudo while using fastboot also.
icrunchbanger said:
Maybe the issues is fastboot/adb binaries being too old. Remove fastboot/adb and use this script https://drive.google.com/open?id=1lh-nOrpeeJrEeLrBO6i9-aLgWfSVD05b
Try using sudo while using fastboot also.
Click to expand...
Click to collapse
Not this issue.
Both not work.
Thank you the same.
Same problem
I'm trying to convert from Windows to Linux and I'm doing great, as I'm using the former only for gaming and Adobe Suite. But I'm still having this problem, and I hate rebooting my computer only to flash a recovery. Everything works fine with windows + powershell + fastboot, but here in linux I'm having the same weird behaviour of fastboot as you.
MEGA BUMP
neflux said:
I'm trying to convert from Windows to Linux and I'm doing great, as I'm using the former only for gaming and Adobe Suite. But I'm still having this problem, and I hate rebooting my computer only to flash a recovery. Everything works fine with windows + powershell + fastboot, but here in linux I'm having the same weird behaviour of fastboot as you.
MEGA BUMP
Click to expand...
Click to collapse
Try this
https://wiki.archlinux.org/index.php/Android_Debug_Bridge#Adding_udev_Rules
Any update I have a xiaomi mi 6 and I have problem connect it to ArchLinux.
The phone connect looks connecting at the beginning but the it keep disconnecting
( I suspect the cause it is the cable so I gonna buy a new one and check )
dmeg shows these lines:
Code:
[ 344.485964] usb 1-1: new full-speed USB device number 12 using xhci_hcd
[ 344.609329] usb 1-1: device descriptor read/64, error -71
[ 344.839332] usb 1-1: device descriptor read/64, error -71
[ 345.069295] usb 1-1: new full-speed USB device number 13 using xhci_hcd
[ 345.192664] usb 1-1: device descriptor read/64, error -71
[ 345.422651] usb 1-1: device descriptor read/64, error -71
[ 345.529405] usb usb1-port1: attempt power cycle
[ 346.172634] usb 1-1: new full-speed USB device number 14 using xhci_hcd
[ 346.172860] usb 1-1: Device not responding to setup address.
[ 346.379531] usb 1-1: Device not responding to setup address.
[ 346.585957] usb 1-1: device not accepting address 14, error -71
[ 346.709323] usb 1-1: new full-speed USB device number 15 using xhci_hcd
[ 346.709569] usb 1-1: Device not responding to setup address.
[ 346.916181] usb 1-1: Device not responding to setup address.
[ 347.122647] usb 1-1: device not accepting address 15, error -71
[ 347.122763] usb usb1-port1: unable to enumerate USB device
Do you have solution? I suspect that Xiaomi's build of fastboot is customized.
For fastboot on linux, the only thing that fixed the inconsistent behavior when trying to send commands was to move the phone onto a usb hub. Im not sure why it never worked for me without a hub, maybe it needs a usb controller all to itself. Hope this helps
8andage said:
For fastboot on linux, the only thing that fixed the inconsistent behavior when trying to send commands was to move the phone onto a usb hub. Im not sure why it never worked for me without a hub, maybe it needs a usb controller all to itself. Hope this helps
Click to expand...
Click to collapse
Crazy. I know this topic is old but this last post helped to fix my issue. I've faced the same situation with a Xiaomi Redmi Note 10. I've tried everything found on the web to connect my phone to Ubuntu on a old Lenovo T430. By everything I mean... everything!
But THIS did the trick. Status were still < waiting for any device > in response to the fastboot flash recovery twrp.img command when I've just unplugged the phone from direct connection to computer to plug it to my ORICO 15 ports USB hub. After plugging I could see in terminal that job was done instantly.
Bash:
$ sudo fastboot devices
45ac2951 fastboot
$ sudo fastboot flash recovery twrp-3.6.1_11-0-sweet.img
< waiting for any device >
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 7.805s]
writing 'recovery'...
OKAY [ 0.481s]
finished. total time: 8.286s
$ fastboot reboot
Thanks a lot for the advice 8andage. I could have searched a long time before understanding this workaround.
In my case on Ubuntu 20.04, it was a USB 3.0 port problem. It was detect device with fastboot devices but other commands does not has a response. My laptop hasn't got a USB 2.0 port. Then I disabled internal USB 3.0 support in my BIOS and now fastboot is working normally. But all USB 3.0 support is stopped. It seems USB 2.0 hub is the better option. I will set back the BIOS setting later.
My m9 is rebooting when I plugged charge . I'm trying to flashing but I just enter fastboot . Can't get download mode and recovery mode. I used adb.
adb reboot bootloader
error: device '(null)' not found
----
fastboot devices
HT59FSV01842 fastboot
Please help!
If you cannot get to download mode the device is dead.
-----------------------------------------------------------------------------------------
Start up Failed:
Your device didnt't start up successfully.
Use the software repair assistant on computer
to repair your device.
connect your device to your computer to get
the software repair assistant
ap fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validaton, backup to fastboot
fastboot reason: Fall-through from charger boot mode
-----------------------------------------------------------------------------------------
Is there any way to backup data before flashing ?
* bootloader not unlocked (haven't done anything to phone)
* usb debugging enabled
* adb not detecting
* only fastboot command can be executed through usb
I'm trying to unbrick my 11 LE, but whenever I try to do anything with it, it gives me an error like:
FAILED (Write to device failed (Too many links))
FAILED (remote: 'Token Verify Failed, Reboot the device
')
FAILED (Write to device failed (no link))
All drivers are installed, don't know what to do...
Already tried to use USB 2.0 port, 2 different PC's (all Intel) and 2 different USB cables from Xiaomi.
Bootloader is unlocked, I use Windows 11 x64.
Closed! Fixed with using rear USB 2.0 port of my PC.