I'm trying to unlock the bootloader, but once the phone goes into fastboot mode, the phone is not being detected(adb is detected)
I have tried updating the device driver in My Computer>device manager, but the device is not switching to adb device from other device with the yellow warning icon
Anyone know what I'm doing wrong?
Related
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc. Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Make sure minimal adb and fastboot are installed in your pc. After that, enable usb debugging from developer options and connect with your pc and let it there for a while to install drivers on your pc.
Click to expand...
Click to collapse
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
SilverMarcs said:
Then go to twrp and your phone should no longer reboot after your connect usb. Flash twrp here.
Click to expand...
Click to collapse
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
FrozenPie1 said:
ADB and FASTBOOT installed -> checked!
USB-Debugging enabled -> checked!
Windows installing drivers automaticly -> unsure. Windows didn't installed anything it just notified me that there is a new USB-Device (Device is also showen as ADB-Device and appears in the list of connected adb devices)
To that: TWRP is not installed on the phone anymore. I just have the standard xiaomi recovery where i'm not able to flash a .zip or something. I can just wipe all my data there
The reboot behaviour also appears if i switch to fastboot via "adb reboot bootloader" command while spamming "fastboot devices" to check if it appears before it reboots.
The standard recovery is usable as it should be without any reboots only the fastboot mode seems brocken.
Click to expand...
Click to collapse
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Sent from my Xiaomi Mi5 using Tapatalk
SilverMarcs said:
Weird. Everytime this sorta problem happens to me, its because windows didnt have the drivers installed after you connect your pc with debugging enabled. So thats the only troubleshooting i did to fix things. And yeah it did show me drivers installed correctly after i connected phone with debugging enabled. Maybe for some reasonn those drivers arent being installed to windows. Give it more time maybe? [emoji23]
Click to expand...
Click to collapse
It's not working on both Windows 10 Machines i have. I'll try to install Windows 7 on my Laptop (or in a VM) and look if that works when i'm home again
Edit: Well, now i'm totally confused... For some reason fastboot started working again this morning so i was able to flash TWRP again. Anyway thanks for the help
FrozenPie1 said:
Hey guys,
I have a problem while trying to flash TWRP on my Xiaomi Mi5. TWRP was installed earlier and worked completly fine with flashing custom ROMs, flashing OpenGAPs or rooting the device but now for some reason TWRP got lost and the standard Xiaomi recovery is on the device again. Installed was MIUI 8 in the Dev-Version (weekly patches) for the last half year and was the last ROM flashed with TWRP.
And now comes the problem when i try to install/flash the twrp image via fastboot: If i reboot the device in fastboot mode it shows the following behaviour:
1. It show the fastboot logo on the screen for about 10-30 seconds before it reboots automaticly (doesn't matter if i connect it via USB before or while it shows the fastboot logo)
2. While it shows the logo on the screen and it is connected via USB it's not showing up in the console when i list the all connected fastboot devices
I can still use the devices standard recovery and the installed OS, just the fastboot part seems to be brocken. Am i missing a driver on my computer or something?
Has somebody else an idea how i can solve this automatic reboot in fastboot mode?
Edit: If this Thread belongs into another catagory, i apologize
Click to expand...
Click to collapse
I too have the same problem..****
Install MiFlash on your PC and try again, the device will show up correctly on fastbook devices command. It was a USB drivers issue in my case.
I'm trying to unlock the bootloader so I can install a custom firmware. I installed the adb and fastboot tools and have to reboot the phone in fastboot mode. I tried holding down volume and plugged the USB cable in as well the 'adb reboot bootloader' command , the LED get blue and in the windows device manager I see something like an unknown device called S1Boot Fastboot for a few seconds and then it disappears. If I try to verify the fastboot mode with 'fastboot devices' and don't get any device, so something is wrong. I know if have to use fastboot drivers and I think the problem should be there. First there are some google fastboot drivers,'I installed then but no succes. Then there is some sony fastboot driver, you need the overwrite some .inf file over the google fastboot drivers but then I get an error some checksum is not correct. And at last there are some universal fastboot drivers on github, I tried to install those but windows say they are not correct.
After this I tried to use the flashtool and unlock the bootloader with the falshtool tool. Here I get the same problem of needing a driver. I installed all drivers that come with the flashtool, but the problem persists. I also try to manually install the drivers from the flashtool drivers(copied them during installation) and here it again says the the driver could not be installed due to some hash not correct in the catalog or something.
What can I do?
I have Windows 10 fall creators update and run everything with administrator privileges.
hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
reinstalling windows solved my problem
Ibtisaam said:
hi fellows im fascing a problem,
Im unable to get my phone in adb or fastboot mode
when i plug my phone in and hit ADB Devices after allowing "Using USB to transfer files" it shows no device,
but if i dont allow it shows my devices.
again if i hit "Adb reboot-bootloader"
i restarts in bootloader but again here fastboot shows nothing.
any knid guy also let me know how to unlock bootloader on august patch after resolving this issue.
Click to expand...
Click to collapse
reinstalling windows solved my problem
Hi, Im kinda new to this bootloader thingy. What happen is, i updated the razer phone 2 to Pie, but notice wifi and sim card cant be detect. Even factory reset fails. So i thought of flashing new image on it. KINDA easy on my oneplus, but im not sure where I gone wrong on this razer phone 2, i accidentally unlock the bootloader. NOW the problem is HOW to relock it back? i been follow all youtube and guides all over the place but still fails.
The state of device atm, cannot be boot into Download Mode. Everytime I plug in usb c from Windows, it will boot into unlock bootloader warning page, and continue boot into the homescreen. testing the adbtools, fastboot also to no avail. Can anyone help and guide me how to relocking it back? Maybe i type wrongly on cmd or maybe other android steps not similar to razer one etc....:crying:help much appreciated.
Hold volume down while turning on. Then fastboot flashing lock.
the stock usb doesnt send things correctly in BL mode, https://www.amazon.com/Blackweb-3-Foot-Charge-Cable-Connector/dp/B07SG7P3KZ/ worked for me. with the correct usb cable you should be able to perform the lock commands correctly. can you give us more detail of what you tried on this phone so we know if we need to provide you additional information?
https://developer.razer.com/razer-phone-dev-tools/general-instructions/
"Locking the Bootloader
Locking the bootloader is recommended for security reasons. Some applications will not work with an unlocked bootloader.
Start the Phone in Download Mode with one of the following methods:
Using the adb tool: With the Phone powered on, execute: adb reboot bootloader Enter Download Mode:
Plug in a USB cable to connect your Razer Phone to your computer, Power Off the Phone, then turn it on and immediately press and hold the Volume Down button until “Download Mode” appears on screen.
Lock the critical partitions of the Bootloader first by running this command: fastboot flashing lock_critical
Your Razer Phone will show you a confirmation screen. Use the Volume Up/Volume Down buttons for navigation, and press the Power button to select. Your Phone will reboot."
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
The_Vinlander said:
I can't seem to enter download mode. All I have is fastboot mode and the option to either reboot, close the phone or enter recovery mode. I would really like to lock the bootloader, but I can't seem to be able to detect my phone on my PC even though I installed the fastboot driver.
Click to expand...
Click to collapse
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Reznor7 said:
You must use a USB 2.0 port. The RP2 isn't detected by fastboot when connected to a 3/3.1 port.
Click to expand...
Click to collapse
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
The_Vinlander said:
I tried this, but to no avail. I tried with 2 cables I had and it keeps telling me < waiting for device > when I enter this command; fastboot flashing lock_critical
Click to expand...
Click to collapse
You need to go into your device manager and select [ android bootloader interface ] while in fastboot
Hi I have a problem where my pc does not detect my unlocked device in fastboot. This is a problem because I tried to update from global V10.3.3.0 to miui 11 but that did not work probably because there is not the right recovery on the device. So I can not get into the recovery and I can not get into the system this would of course be no problem because I can get into fastboot but my computer wont detect my device. How can I get my 9t pro to be detected in fastboot?
My device is unlocked. I did all that some time ago and it says so when I try to boot into system or recovery.
USB debugging is on. Idk if that is still there because I did try to update the system to miui11 but it was not detecting my phone in fastboot even before I did that update.
When I connected my phone to my computer when the system still worked I could use "adb devices" and that worked
I could also transfer files and stuff when my phone was connected to my laptop
So only when in fastboot my unlocked device is not detected if it was I could get back up there.
I really hope that this is some driver problem or something. Please help
Edit:
So at this point magically the system worked again! But I still can not use fastboot
I seem to have this problem:
https://forum.xda-developers.com/k20-pro/help/broken-fastboot-t3972697