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.
Related
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
Hello everyone. I want to install CyanogenMod to my Sony Xperia SP 12.1.A.1.205.
I already unlocked the bootloader, I already rooted it, and even my PC (using Linux) detects it, but I just can't get fastboot to recognize the device. If I type in the command line
Code:
adb devices
CB51240CAW device
But if I try to do fastboot flash boot boot.img to install CyanogenMod I always get "Waiting for device". If I type fastboot devices I get no response (of course I restart my phone holding volume up to fastboot).
Is it even possible that my PC recognize my device using adb but not using fastboot?
Thank you in advance.
Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979
bbabel said:
Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
U can install the fastboot drivers on windows 8 or 8.1 by signing off of the drivers in advance reboot of the PC.:good:
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.
Developer option shows bootloader as locked but after reboot bootloader shows as unlocked . twrp working but Fastboot not working so I'm afraid I might brick my device as I can't flash fastboot rom. Please help.
I wanna know what you mean by 'Fastboot not working'. Does it mean you can't boot into fastboot mode, or does it mean you can't access fastboot commands on your pc?
Also i wanna know, while unlocking Bootloader. Did you used commands
Code:
fastboot oem unlock
and
Code:
fastboot oem unlock_critical
?
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
pythonner said:
The device does boot into fastboot but doesnt respond to any fastboot command
It doesn't even show up on typing fastboot device
I unlocked the bootloader using miunlocktool
But the device doesnt even show up in the tool
Click to expand...
Click to collapse
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
It's same for me.
You can ignore that safely.
eleven.co said:
If it's not responding to fastboot commands I worry that if correct drivers are installed on your pc.
Plug-in ur device while in fastboot mode to your pc.
Open Mi Unlock tool(this works very first time, you don't even have to install this tool). There's a setting icon on top right corner.
A dialogue box will appear, displaying to install drivers.
Install 'em. It will ask you to remove and plug-in your device again.
Now, download the platform tools file.
Open cmd in the platform tools folder.
Now try using fastboot commands.
Click to expand...
Click to collapse
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
Actually when I type fastboot devices in platform tools the device is not even detected. So I'm afraid that if I flash custom rom and brick it I will be unable to flash even the official fastboot rom.
pythonner said:
I updated the usb driver but unlock tool can't even detect the devices and when I type fastboot devices in platform tools the device is also not detected
I'm afraid of installing custom roms because if I brick it I will not be able to even flash the official fastboot rom
Click to expand...
Click to collapse
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
eleven.co said:
Boot your phone, connect through USB to PC. Now check in Windows File Explorer. Is your device visible there?
If not, open Device Manager and you'll find something with the name adb (You can go through this guide). In my case it was under Acer. Just update those drivers manually and see if your device is visible now.
Click to expand...
Click to collapse
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
pythonner said:
the devices shows up in file explorer and device manger when its turned on but after putting in fastboot mode the platform tools cant detect the device
Click to expand...
Click to collapse
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
Now developer options is showing as unlocked and adb is also working good
but fastboot is still not working when I type fastboot devices It returns nothing
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
What could be possible explanation to adb working but fastboot not working. The usb cable is tight and bootloader is unlocked even in developer options
eleven.co said:
This is sad. Try fiddling around. I am unable to identify what could be the possible reason behind non-detection of device over platform tools as there are many. Maybe go through this article. It has various methods to fix non - detection of device.
Click to expand...
Click to collapse
I just realised that I flashed twrp using the root app flashify. Could that be the reason for root not working
VD171 said:
It's same for me.
You can ignore that safely.
Click to expand...
Click to collapse
If you're rooted and have magisk hide enabled, it's normal, Magisk spoofs locked bootloader to pass safetynet in MIUI
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!