whatever TWRP version I tried to flash recovery on my MiPad (newly bought from aliexpress), I'm getting errors. (and show 'press any key to shutdown)
when it boot, it's showing "Unlocked" below
Code:
$ fastboot devices
8XXXXXX3 fastboot
$ fastboot getvar all
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:VQ[.......]QhBhu
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4371
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:vendor:ext4
(bootloader) partition-size:vendor: 0x80000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xCAD753E00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno: 8XXXXXX3
(bootloader) product:clover
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.109s
Code:
$ fastboot boot twrp_clover-3.3.1-recommand.img
Sending 'boot.img' (34680 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Code:
$ fastboot flash recovery recovery-33.img
Sending 'recovery' (64644 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
Code:
$ fastboot flash recovery recovery-33.img
Sending 'recovery' (64644 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
Code:
$ fastboot --version
fastboot version 29.0.1-5644136
can anyone help me?
Yes, just get a USB 2.0 HUB.
Fastboot does NOT work with USB 3.0 with this device. That's it.
I just used an old notebook that is USB2 only.
Same problem.
*Le sigh*
Can 100% confirm this is the problem and solution. Used an ancient laptop I had lying around just to flash TWRP. Rest is gravy.
I just flahsed & rooted my MI PAD 4 bought from China a while ago yesterday for the very first time and I concurred, using an older USB port (2.0) is the right way to deal with this problem, otherwise you will see "press any key to shut down" message no matter what you do, and you can't go beyond this page.
Maybe it's late, but for the best result, try windows 7 too. I plug the tab into the usb 2.0 port on my win 10 pc and the dreaded "press any key to shutdown" button still appear.
Related
LG-D415 stuck in fastboot No operating system installed. ( I think)
To make long story short was stuck in recovery (due to 14.1 issue) tried the twrp3.2.1-0mako.img solution but somewhere (hard to nail down) hit reboot before I had installed a rom. Now stuck in fastboot. Have tried many different ways to get system but none work. Need help with fastboot and partitions getvar:slot . Here is what I can get from the phone as info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.im
downloading 'boot.img'...
OKAY [ 0.438s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.444s
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot getvar all
(bootloader) display-panel:
(bootloader) charger-screen-enabled: 0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x38400000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x102180400
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) unlocked: yes
(bootloader) secure-boot: yes
(bootloader) version-hardware: rev_10
(bootloader) variant: w7_tmo_us Samsung 8GB
(bootloader) serialno: LGD415e09994e6
(bootloader) kernel: lk
(bootloader) product: W7_TMO_US
all:
finished. total time: 0.050s
all commands except this one and list devices have failed
I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)
betam4x said:
I unlocked bootloader long ago, however, it was with an older method I believe. The device appears to be unlocked (see below), but attempting to flash anything just freezes into eternity:
Any thoughts?
Code:
C:\platform-tools>adb devices
List of devices attached
LGUS9980af4c546 device
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot getvar all
(bootloader) eio_count:0
(bootloader) dm_count:0
(bootloader) lock_count:0
(bootloader) unlock_count:1
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4308
(bootloader) version-baseband:┼φ≈Qa⌡6C`⌡ⁿƒ
(bootloader) version-bootloader:
(bootloader) variant:MSM UFS
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x81800000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC92474000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x19F400000
(bootloader) secure:yes
(bootloader) serialno:LGUS9980af4c546
(bootloader) product:QC_Reference_Phone
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.047s
C:\platform-tools>fastboot flash recovery TWRP.img
Sending 'recovery' (30860 KB)
Click to expand...
Click to collapse
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.
HueyT said:
Download both TWRP.zip on phone and TWRP.img to adb folder of PC. U then have to "fastboot boot TWRP.img" and once temp TWRP boots up, then use TWRP to install TWRP. ZIP as v30 does NOT have recovery partition.
Click to expand...
Click to collapse
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.
betam4x said:
No luck so far, it just freezes on sending. Does the same thing if i try to re-unlock it as well.
Click to expand...
Click to collapse
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot
HueyT said:
Try another fresh laptop, cable, USB port, LG, Qualcomm drivers, latest minimal adb and fastboot
Click to expand...
Click to collapse
tried 3 different cables, multiple versions of the ports (1.1, 3.0, 3.1) and no dice on my main desktop, going to try another desktop in just a moment. Thanks!
It was my desktop. again. Managed to get TWRP on there, now just trying to get LineageOS to boot (right now it's showing the startup screen. Hoping it just takes a while on first boot). Thanks for your help! I should know better by now.
hello, my first name is jonathan, i'm french.
I have an amazfit stratos 3 watch, Chinese version.
I have a problem unlocking the bootloader.
----------------------------------------------------------------
Microsoft Windows [version 10.0.18363.592]
(c) 2019 Microsoft Corporation. Tous droits réservés.
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.016s
C:\adb>adb devices
List of devices attached
11ee2611 device
C:\adb>adb shell reboot bootloader
C:\adb>fastboot oem unlock d144d5a285c0b53aeb2ee359bb7a2ee9
< waiting for device >
...
OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot getvar unlocked
unlocked: no
finished. total time: 0.016s
---------------------------------------
the code is good but the bootloader does not want to unlock
C:\adb>adb shell reboot bootloader
C:\adb>fastboot getvar all
(bootloader) version-bootloader: U-Boot 2013.07-g43d9f8c
(bootloader) version-baseband: N/A
(bootloader) version-hardware: V1.1 20130322
(bootloader) version-cdma: N/A
(bootloader) variant: watch
(bootloader) serialno: 19281943******
(bootloader) product: watch
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: NO
(bootloader) partition-size:bootloader: 0x0000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x1000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x2000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x3000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x4000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x5000
(bootloader) partition-type:userdata: ext4
(bootloader) max-download-size: 0x4000000
all:
finished. total time: 0.156s
C:\adb>
Try this:
In the case of ROM China the code must be inserted with a slash after the first 5 numbers (for example 12345 / 12345678);
How to unlock the bootloader on Amazfit Pace, Stratos and Verge
In this guide we explain how to unlock the bootloader on Amazfit devices, so you can install custom ROM.
en.gizchina.it
Commande d'erreur CMD.
$ Démarrage rapide oem_unlock_get_data
Failed (commend unlock cmd)
Mod translation:
CMD error command.
$ Quickstart oem_unlock_get_data
Failed (commend unlock cmd)
Le commande est:
Code:
fastboot oem get_unlock_data
Please stick to English. You've taxed my French capability inordinately.
enael said:
Mod translation:
CMD error command.
Click to expand...
Click to collapse
Greetings. As a friendly reminder, we ask all members to please post in English as stipulated by XDA Rule #4:
Spoiler: XDA Rule #4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
Thank you for your cooperation, and have a pleasant day.
-Regards: Badger50
that's what I did but I got errors yet I have the tool, SDK. the Motorola and Google usb oem driver.
enael said:
... I got errors ...
Click to expand...
Click to collapse
Code:
fastboot oem help
fastboot oem get_unlock_data
Code:
adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem get_unlock_data
...
FAILED (remote: unknown cmd.)
finished. total time: 0.016s
PS C:\Users\Enael\Desktop\adb+fastboot>
enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
How old is this device? What is it?
the device is released in 2022
And fastboot oem help
A quick Google shows:
Thanks for providing this. Upon checking, the device is not supported by this bootloader program.
Regards,
Jess
Motorola Support
Click to expand...
Click to collapse
PS C:\Users\Enael\Desktop\adb+fastboot> fastboot oem help
...
FAILED (remote: unknown cmd.)
finished. total time: 0.031s
PS C:\Users\Enael\Desktop\adb+fastboot>
enael said:
FAILED (remote: unknown cmd.)
Click to expand...
Click to collapse
I guess that Motorola screwed you.
This is my Moto G Power (2021), not that much more pricey a Motorola.
Code:
C:\>fastboot oem help
(bootloader) config...
(bootloader) hw...
(bootloader) partition...
(bootloader) blankflash
(bootloader) fb_mode_set
(bootloader) fb_mode_clear
(bootloader) bp-tools-on
(bootloader) bp-tools-off
(bootloader) qcom-on
(bootloader) qcom-off
(bootloader) unlock
(bootloader) lock
(bootloader) get_unlock_data
(bootloader) cid_prov_req
(bootloader) off-mode-charge
(bootloader) read_sv
(bootloader) show_screen
OKAY [ 0.016s]
Finished. Total time: 0.016s
It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?
enael said:
It does not work I think the adb and fastboot drivers are obsolete.
Will you have up-to-date drivers?
Click to expand...
Click to collapse
https://developer.android.com/studio/releases/platform-tools
It's good to update, but I don't think it will make a difference.
Fastboot does some filtering locally so that fastboot self-destruct doesn't go anywhere.
OTOH, fastboot oem self-destruct should be passed to a device (but probably won't do anything).
Spoiler
Code:
fastboot getvar all
(bootloader) frp-state: Protection
(bootloader) serialno: ZY32FTTJFM
(bootloader) secure: true
(bootloader) socidp2: d311d921e088b588bda2f11f7e42ce46
(bootloader) socidp1: e2f7cb94c69577917f8bf8468753667c
(bootloader) tokenp1: 5a5933324654544a464d000000000000
(bootloader) lcs: 5
(bootloader) max-download-size: 0x36000000
(bootloader) is-userspace: no
(bootloader) version: 1.0
(bootloader) battery-voltage: 3825
(bootloader) battid: SB18D34202
(bootloader) cpu: T606 AB
(bootloader) radio: EMEA
(bootloader) hwrev: PVT
(bootloader) ram: 4GB SAMSUNG LP4X M5-M8=01 08 00 12
(bootloader) ufs_sn: 0036003300370061003000390031003100380066003200380000
(bootloader) ufs: 64GB SAMSUNG KM5P9001DM-B424 FV=0300
(bootloader) storage-type: UFS
(bootloader) ufs_ffu.change_count: 0
(bootloader) ufs_ffu.vice_flash_retry_count: 0
(bootloader) ufs_ffu.vice_flash_fail_count: 0
(bootloader) ufs_ffu.vice_flash_count: 0
(bootloader) ufs_ffu.flash_retry_count: 0
(bootloader) ufs_ffu.flash_fail_count: 0
(bootloader) ufs_ffu.flash_count: 0
(bootloader) unlock_raw_data: c19012e8c1849b5bcd7088a7364fd182
(bootloader) sku: XT2227-2
(bootloader) build_type: user
(bootloader) product_model: Hawaii
(bootloader) product_name: hawaii
(bootloader) ro.build.version.incremental: 9fe5d
(bootloader) ro.carrier: reteu
(bootloader) imei2: 000000000000000
(bootloader) imei: 000000000000000
(bootloader) persist.radio.multisim.config: dsds
(bootloader) fingerprint(3):: s
(bootloader) fingerprint(2):: S31.335-20-2/9fe5d:user/release-key
(bootloader) fingerprint(1):: motorola/hawaii_reteu/hawaii:11/ROR
all: Done!!
Finished. Total time: 0.084s
Hello everyone, I finally managed to get the info from my phone but I see that the FRP protection is active, is that a problem?
Hi,
I bricked the Mi 8 Lite (platina)
I had Rom Lineage 20 and TRWP 3.7.0_12 uploaded.
I wanted to flash back the MIUI ROM so I did a wipe in recovery and flash new rom. After reboot the system booted but there was no recovery. Fastboot only. I wanted to upload a new recovery (fastboot flash recovery recovery.img) but I get the error:
FAILED (Write to device failed (Invalid argument))
---------------------------------------------------------------------------------
When trying to:
fastboot devices
4fa7e5b9 fastboot
-------------------------------------------------------------------------------
When trying to:
fastboot getvar all
---------------------------------------------------------------------------------
<waiting for any device>
(bootloader) DP:0x0
(bootloader) token:VQEBIQEQnmryIh8fcJ8Ox+x507NtFwMHcGxhdGluYQIE+x0CYg==
(bootloader) crc:1
(bootloader) cpuid:0xfb1d0262
(bootloader) board_version:2.19.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4326
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC7F7FBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno:4fa7e5b9
(bootloader) productlatina
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
all:
Finished. Total time: 0.003s
----------------------------------------------------------------------
The MIUI system booted normally, but I did factory reset, because I thought it would enter recovery and now only fastboot
I tested fastboot on Windows 11 and Fedora. The same all the time.
EDIT:
-------------------------------------------------------------------------------------------------
When i try "fastboot continue"
Resuming boot FAILED (Status read failed (No such device))
------------------------------------------------------------------------------------------------
But system MIUI booted.
sudo adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
4fa7e5b9 device
Question: Howto flash recovery ? Or fix that ?