Today i tried to install a custom ROM update which caused a softbrick and now my device is stuck at the logo. I naturally decided to flash a stock rom in order to solve this. I went ahead and downloaded a MIUI 11 global stable one, next was rebooting into fastboot and connect it to my PC...
...When i rebooted my phone into fastboot, my PC didn't recognize the device at all. Device Manager says "USB Unknown Device (Device Descriptor Request Failed)". I verified the USB port and cable works properly with another phone, i installed USB drivers and ADB/fastboot ones, still nothing.
Is there anything I'm missing? I'm not very adept at these topics, I previously flashed mine into a PE custom ROM purely by following tutorials mindlessly.
Try the app "Xiaomi ADB/Fastboot Tools", this has the option to flash stock ROMs. The USB drivers that I have installed on my computer are "minimal ADB Fastboot 1.4.3".
You could also solve the problem with the tool "MiFlash Pro".
Related
Dear people of xda,
Recenlty ive receive a FOTA update to my device which runs 4.2.2. Being stupid, i did the update although i had cwm recovery installed on my devices. Now my device keeps bootlooping into cwm without being able to do anything.
Ive read tons of threads talking about this issue but i still cant get my to boot normally.
Yingy in this thread http://forum.xda-developers.com/showthread.php?t=2563527 had the same problem but the only diffrence is my pc cant recognize my device in order to do the adb fix by thecubed.
Im plugging my G2 for the first time in this computer and that is why i think my pc is failing to install drivers. I downloaded and instellad latest driver although windows device manger shows error devices not detected and the end of the process.
In order to fix my phone i just need to make me pc recognize my phone in adb although phone was never plugged before to this pc so i think my G2 wont let it access. I tried installing universal driver such as Pdanet as offered in threat but still when i write adb devices in cmd i get device offline!
Download latest adb drviers, lates lg g2 driver, lg user support tool does not recognize plugged device as well. All me sdk manger tools are patched to latest version.
PLEASE ive tried anything possible. spend like 9 hours and still nothing. i would really appriciate your help.
Thanks.
Edit: here my problem with pdanet drivers, it asks me to allow pc usb debbuging as shown in screenshot below but icant do it since im stuck at cwm recovery!
Solved!
BOOM!! after 12 hours i FINALLY manged to solved this problem. Really simple actually lol.
If anyone come across the issue please do the following:
1. Go to clockwork recovery as always, go to install zip from sdcard, choose install zip from sideload.
2. Plug your phone to pc.
3. Run adb with lastest drivers and sdk tools.
4. At the adb folder press shift+right click and start cmd.
5. write adb devices it should show your device id like this (xxxxxxxxx sideload).
6.Download latest twrp recovery from here http://teamw.in/project/twrp2/197 and if you have open europe version G2 like me download latest version from here: http://techerrata.com/browse/twrp2/g2d802
7.put the zip file in the adb folder, do not unzip it.
8. write in cmd console adb sideload xxxx.zip (xxxx is the name of twrp file).
9. cwm will flash twrp recovery over cwm.
10. reboot in recovery in advanced options.
11. now you have twrp recovery.
12. follow this guide : http://forum.xda-developers.com/showthread.php?t=2451696&nocache=1
13. THATS IT!!!
finally after going through this mess, im never using cwm recovery again. twrp is the best
good luck everyone!
Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10
I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.
Can't anybody help us?
Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Excuse me for my bad English. I am new on this Forum. Please help me, I have a big problem!
I can’t use Fastboot command, because ewery time I got the „Waiting for devices” error message
1) I have a Motorola Moto G4 phone (XT 1622, athene)
2) This mobile are not rooted.
3) I want to unlock my bootloader, after this I want to install TWRP, and after this I van root my mobile, for install the custom Lineage OS.
4) On my phone I activated at the Developper Otions the USB debugging, and OEM Unlocking.
5) I connected my phone to my PC, I used first time Windows 10. On this system my Moto G4 are identified: Motorola ADB interface. No problem with identification, no any yelow exclamation matrk, no unidentified device!
6) I have installed the correct ADB and Fastboot driver v.1.4.3 (link is made from this site)
7) I have installed the Motorola driver from the official Motorola site.
8) All ADB command work fine, for example adb devices, adb reboot bootloader, etc.
9) But no fastboot command work, when I tested the fastboot devices, I got the „Waiting for devices”. Of corse befor this, I rebooted my phone in fastboot mode! If I use any fastboot command, I got this error message.
10) I try to use the excellent tools (thank you for this): Universal Fastboot & ADB tool, latest version, but the situation in this case is the same, „Waiting for devices”.
11) Of corse I rebooted the PC after instalation of the drivers, the fastboot.exe is in the right paths, etc.
12) I have installed the Universal USB Driver with the Universal Fastboot & ADB tool, Install drivers button, PC rebooted after this.
13) I used Windows 10, Windows XP, and Ubuntu, and in all cases I got the „Waiting for devices”
14) Under Ubuntu I got this message, despite that on Ubuntu the ADB and Fastboot driver installations are cleare.
15) I tested all on many other PC.
16) Every time I connected my phone to the PC only on USB 2.0 port, I changed the USB port, and I changed the USB cable too.
17) I read hundred ot tutorilas on youtube, on differant Forums, but none of them helped.
18) I uninstalled or reinstalled a many timet he ADB and fastboot drivers (I tested a lot of drives from the net), and I installet a many times the official Motorola driver, and the Google universal USB driver, but nothing
Please tell me what can I do for solve this devil situation, Please help me! Thank you again!
I hope someone in here can help me with the following problem:
I had an old Android version on my X720, which I wanted to update/install LineAge custom ROM with Android 10 on. Since the old Android was acting weird and USB debugging couldnt be enabled for some reason, I decided to wipe the System/Cache on it using TWRP recovery BECAUSE the device wasnt found on Windows 7 when plugging in via USB. Previously I installed ADB drivers and everything needed, but still Windows couldnt find the device and I was unable to move the Lineage ROM (plus GApps) to the device to be able to install it via TWRP. Anyway, now there is no OS installed and I can only boot into TWRP. I tried to ADB sideload the Lineage ROM via TWRP (via connected USB to my Notebook), but after typing "adb devices" and "adb sideload path...." etc. in Windows Terminal as Admin I always get "no devices found". So, when connecting the device to my Notebook, nothing is shown and the device doesnt appear under "Device Manager" and I think that's the main problem.
Does anyone have any solution or idea? Thanks a lot in advance!
try reading this useful thread:
https://forum.xda-developers.com/le-pro3/how-to/unbrick-leeco-phones-leeco-variants-t3847220
good luck!
I have a Mi 9T Global 6/128GB running stock MIUI 12.0.7 Global with bootloader already unlocked. However the USB port has gone bad and only works for charging.
Is there a way for me to install TWRP without a USB connection?
Everything I've done and observed:
USB debugging enabled
USB tethering option greyed out - no USB connection detected
Default USB action set to MTP does not help
It charges but no prompt for USB mode when connected
Phone does not show up on PC
No new device detected in device manager
No problematic device detected in device manager in any mode
No device detected through ADB in any mode
No device detected through fastboot in fastboot mode
No device detected in miflash tool regardles of phone in system or fastboot
No device detected in miunlock tool regardless of phone in system or fastboot
No detected USB device on which I can attempt a driver update
USB drivers verified updated
Tried on my desktop and laptop, with multiple cables and ports
OTG with another Android device does not work
I was using RR Android Q when I realized this issue. At that time I was using TWRP and even in recovery with everything mounted and MTP enabled, the phone was still not detected on PC. I flashed the latest stable MIUI zip hoping it would be fixed bit no bueno.
I want to get TWRP back to install a custom rom because I refuse to use MIUI.
Any help will be greatly appreciated.