Hi
I'm trying to unlock my Bootloader and install a new ROM. (I've checked and the Bootloader is unlockable.)
adb works fine and I can see my device after running
Code:
adb devices
but when I put the phone in fastboot mode and run
Code:
fastboot devices
it returns blank
Of course I tried to install the fastboot drivers in the device manager but windows doesn't install them so I added them as legacy hardware but still it doesn't work.
also when I tried to install flashtool drivers the " Google Inc (WinUsb) " driver failed which I guess is the same fastboot driver that I tried to install earlier from android sdk.
also there isn't any driver for xperia mini pro in the flashtool drivers, so what's up with that?
I would really appreciate some help.
Did you try installing the Xperia Pro drivers? It's been a long time, but I think those are the ones I used.
If you're running Windows 8: http://www.flashtool.net/win8drivers.php
Related
I've been trying to work this our for quiet some time now.
Phone - Live with Walkman
PC - Windows 8 - 64 bit
What I did till now:
- Installed the Android SDK on my machine (for fastboot.exe)
- Acquired the unlock key from sony website (and verified that my bootloader can be unlocked *#*#7978423*#*#)
- Also, went to the Windows 8 PC settings and disabled the driver signature enforcement to false
- Downloaded the driver file from sony website and copied it in usb_drivers
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Running 'fastboot.exe -i 0x0fce getvar version' gives nothing.
In device manager, I can see a S1Fastboot Loader device but with no drivers. When I tried to manually install drivers, it didn't do anything.
Finally - I installed ADB driver instead.
Now, the command 'fastboot.exe -i 0x0fce getvar version' gicves '0.3' :laugh::laugh::laugh::laugh:
BUT -
fastboot.exe -i 0x0fce oem unlock 0x[my_key] is failing.
What should I do now???????
Seems like some issues with windows 8?????
arpitghiya said:
I've been trying to work this our for quiet some time now.
Phone - Live with Walkman
PC - Windows 8 - 64 bit
What I did till now:
- Installed the Android SDK on my machine (for fastboot.exe)
- Acquired the unlock key from sony website (and verified that my bootloader can be unlocked *#*#7978423*#*#)
- Also, went to the Windows 8 PC settings and disabled the driver signature enforcement to false
- Downloaded the driver file from sony website and copied it in usb_drivers
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Running 'fastboot.exe -i 0x0fce getvar version' gives nothing.
In device manager, I can see a S1Fastboot Loader device but with no drivers. When I tried to manually install drivers, it didn't do anything.
Finally - I installed ADB driver instead.
Now, the command 'fastboot.exe -i 0x0fce getvar version' gicves '0.3' :laugh::laugh::laugh::laugh:
BUT -
fastboot.exe -i 0x0fce oem unlock 0x[my_key] is failing.
What should I do now???????
Seems like some issues with windows 8?????
Click to expand...
Click to collapse
You Just Need Unlock it 1 time.so u can use a windows 7 pc for one time.no need to discuss.
.
.
anyway u can use flashtool.
I have a problem to install ADB drivers too, on windows 8, BUT I sloved it with this tutorial: http://forum.xda-developers.com/showthread.php?t=2044804
And now I have unlocked my Xperia mini pro bootloader
So it's posible to unlock bootloader on win 8 after installing ADB drivers.
How about IMEI did you enter first 14 corectly without last one?
I think that you have wrong unlock code.
arpitghiya said:
Now,
When I switch off my phone and put it into fastboot mode (Power up and USB cable), nothing happens in PC ... didn't asked for any drivers.
Click to expand...
Click to collapse
Volume up button, not power.
Hello everyone, I'm using Redmi Note 3 and I have tried rooting it several times.
I have unlocked the bootloader. I have also installed the adb drivers.
When I connect phone in fastboot mode and write 'fastboot devices' in cmd it doesn't return anything. But when I connect when its on, adb devices returns the device code.
Please help.
Same, happens to mine too. Used to work with a previous install of windows, but now, nope.
Had this issue too.
Try going to Device Manager and check to see if Kedacom USB Device shows up. Under which, Android Bootloader Interface should be present. Install minimalist ADB and fastboot and right click Android Bootloader Interface. Click Update Driver Software, browse computer, and then click the option to list driver files already present on your drive. It should pull up a fastboot driver that's an older version than the one you currently have. Install that and fastboot will work again.
Doesn't work
Can you please link the files for download when we're updating the driver software.
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!
There are 2 fastboots, fastboot and mfastboot (i guess this one is motorola fastboot)
Try with mfastboot
mfastboot
GuikBretas said:
There are 2 fastboots, fastboot and mfastboot (i guess this one is motorola fastboot)
Try with mfastboot
Click to expand...
Click to collapse
Where can I find the mfastboot? This is same with the Motorola driver?
Thank you.
Hello,
I have just bought a oneplus 7t Pro
I would like to root it but first I need to unlock it.
But impossible to get it detected in fastboot while it works with adb (it finds my device).
I have installed the driver from the attached "cd" repertory, nevertheless the devices manager shows an "android" device which is not correctly installed.
I tried to install the driver manually by slecting it in the oneplus folder in program files, but it says that the driver "OnePlus android bootloader interface" cannot be installed as the hash file is missing.
anyone can help?
Thanks
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
DeeZZ_NuuZZ said:
get the fastboot driver from google. easy to find, then unzip it and select it when installing drivers for oneplus fastboot in device manager.
so yea get either the google fastboot driver or the OEM drivers found there too
Click to expand...
Click to collapse
Hello,
This what I tried and it worked! Using generic driver instead of ... weird. Anyway now everything is fine.
Thanks.
I have the following devices installed ( I enabled show hidden devices ) .
Although my phone still wont be recognized after a qualcomm crash dump
I've been trying to unlock the bootloader in my phone (OnePlus7T Pro).
I can't see my phone when booted into fasboot mode or recovery mode (I can see the phone while normally working).
The command: fastboot devices shows no device. The same with adb devices command.
I think I need a proper driver for the device. I've already tried UniversalAdbDriverSetup.msi, but with no success.
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
kamien8 said:
I use PC with Ryzen processor and Win10.
Could you suggest a solution, please?
Click to expand...
Click to collapse
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Thanks for information.
I can see the device when it is up and running. Still nothing when it is in FB mode, however I can see the Widnows sound of a connected device.
jwoegerbauer said:
The UniversalAdbDriverSetup you referred to is not of any use. You instead have to install the Android USB Driver suitable to your phone:
Download OnePlus USB Driver for Windows (Latest Driver)
Download the latest and original OnePlus USB Driver to connect your OnePlus Smartphone to the Windows Computer quickly and easily.
androidmtk.com
Click to expand...
Click to collapse
I uninstalled the previous drivers and installed the right one from the link. I also have used your version of adb and fastboot.
CXZa said:
This might help...
[FIX] Fastboot issues on Ryzen based PCs
AMD has been known for it's notorious fastboot issues in the custom ROM community, especially with Xiaomi devices. I was trying to unlock the bootloader of my Redmi Note 5 Pro the other day and I encountered with an issue where Mi Unlock Tool...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes, I've heard about the fix. Run it, but still nothing happened.
Maybe I have to find somebody with Intel processor.
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
jwoegerbauer said:
Because your phone's Android is version 10 try this
Code:
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
....
Click to expand...
Click to collapse
Hi, I'm half way.
I checked on Intel proc, and I can see bootloaded phone in fastboot. ADB still can't see the device.
I was trying to re-install drivers, but no changes.
Unfortunately I need working ADB as I have to sideload an image.
I've since years a laptop powered by AMD Ryzen 5 in use: Fastboot always works like a hell. Hence I'm pretty sure that it doesn't matter whether Fastboot is run on an Intel or AMD powered computer.
If ADB isn't working as expected my guess is that "USB debugging" didn't get enabled on phone and phone didn't get re-booted afterwards.
USB debugging is enabled. When the phone is started normally, ADB works fine (for example I can use adb reboot bootloader command)
I thought, maybe there is a mess with the drivers in the device. Can it cause the issue?
So to confirm, this is the only one drivers package I need to run OnePlus (7T Pro) in bootloader and use fastboot and adb commands?
OnePlus 7T Pro USB Driver for Windows
Download the latest OnePlus 7T Pro Driver for Windows Computer. You can use the latest OnePlus Driver to connect OnePlus Device to the Computer.
oneplusdriver.com
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
jwoegerbauer said:
Command
Code:
adb reboot bootloader
since Android 10 is incorrect: I've already told you this in a previous post.
Click to expand...
Click to collapse
Yes, you're right.
adb reboot bootloader command works. Once I am in bootloader I still can connect phone via adb but fastboot doesn't work. That was my question, if the highlightet drivers are the only one I need.
Is it possible, that there is something wrong with the phone?
If ADB successfully connects to phone then your phone isn't booted into its bootloader, but into Android OS.