Database Develop

[Q] Fastboot problem on Windows XP

I wanna unlock bootloader on my XSP but every time I connect it in fastboot mode, my pc tries to reinstall ADB drivers. I can put in download mode, I can push files in both sdcard0 and sdcard1. What can I do?

natroid said:
I wanna unlock bootloader on my XSP but every time I connect it in fastboot mode, my pc tries to reinstall ADB drivers. I can put in download mode, I can push files in both sdcard0 and sdcard1. What can I do?
Click to expand...
Click to collapse
This is coz u didnt install the drivers correctly. U can find them here: HERE. Anyway for make it work u will need this too: HERE

Joku1981 said:
This is coz u didnt install the drivers correctly. U can find them here: HERE. Anyway for make it work u will need this too: HERE
EDIT: All process for unlock your bootloader: HERE
Click to expand...
Click to collapse
Thanks, but, where shall I put fastboot_with_Android(etc)? I already installed flashtool drivers...

natroid said:
Thanks, but, where shall I put fastboot_with_Android(etc)?
Click to expand...
Click to collapse
Did u read the tuto of Doomlord again?? . I give u a trick:
7. Extract fastboot_with_Android_USB_file.rar and open fastboot folder
8. Hold SHIFT and right click on the background of the folder
9. Select 'Open command window here'
10. Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above]
11. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
12. If a value is returned (it will return 0.5), it means the phone is correctly connected
13. Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
14. You're device should now be bootloader unlocked
EDIT: I hope it helped ya :highfive:

Joku1981 said:
Did u read the tuto of Doomlord again?? . I give u a trick:
7. Extract fastboot_with_Android_USB_file.rar and open fastboot folder
8. Hold SHIFT and right click on the background of the folder
9. Select 'Open command window here'
10. Connect your phone in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above]
11. In the cmd windows type in fastboot.exe -i 0x0fce getvar version
12. If a value is returned (it will return 0.5), it means the phone is correctly connected
13. Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
14. You're device should now be bootloader unlocked
EDIT: This process is delicate. If u dont know what u are doing, is better u dont do it for prevent one beaty BRICK :highfive:
Click to expand...
Click to collapse
Yes, I read it, but if I can't go in fastboot mode, I can't do this procedure. I installed flashtool drivers, but I still have this problem...

natroid said:
Yes, I read it, but if I can't go in fastboot mode, I can't do this procedure. I installed flashtool drivers, but I still have this problem...
Click to expand...
Click to collapse
Windows 7 or 8?

Joku1981 said:
Windows 7 or 8?
Click to expand...
Click to collapse
XP. But I unlocked bootloader also on Xperia U, I don't know why I have this problem... I remember I had problems with fastboot drivers, but I resolved in a few minutes...

natroid said:
XP. But I unlocked bootloader also on Xperia U, I don't know why I have this problem... I remember I had problems with fastboot drivers, but I resolved in a few minutes...
Click to expand...
Click to collapse
Try this lil tuto:
1. Open the Windows Device Manager
2. Connect to phone in Fastboot mode (phone off -> Volume + key pressed -> connecting cable)
3. Connect your phone and ignore Windows messages. Quickly go to Device Manager and look for that just appeared "S1Boot Fastboot". Right click and click "Update Driver Software", once done you can relax, you can release the Volume + key and disconnect the phone. [NOTE: If Windows is trying to install the driver, you will not see "Update Driver Software" until it stops, so hurry].
4. Click "Search for driver software on your computer"
5. Click "Choose from a list of device drivers on my computer"
6. Select "Show all devices" (or something, I can not see the exact text)
7. Click "Use Disk ..."
8. Click "Browse ..."
9. Select the android_winusb.inf (in the folder with Fastboot usb_driver the USB drivers) and open
10. Click "OK"
11. If you get a list of 3 devices, choose "Android Bootloader Interface"
12. BEFORE pressing "Next" you need to reconnect the phone in fastboot mode, here you have to be fast again. Unplug the phone if you had not done before. Plug it back into fastboot mode. Once you do click "Next" on the computer.
13. If you followed the instructions correctly have the drivers installed before the phone was disconnected again.
14. Now you have the drivers installed, the phone will not slip out of Fastboot mode and everything should work properly.

Joku1981 said:
It tells u installing drivers but cant install nothing... uh?
Click to expand...
Click to collapse
Yes, every time I put in fastboot mode, XP opens a window with "Sony ADB Interface" and tries to install it. But at the end it do nothing and ADB is always a problem.

natroid said:
Yes, every time I put in fastboot mode, XP opens a window with "Sony ADB Interface" and tries to install it. But at the end it do nothing and ADB is always a problem.
Click to expand...
Click to collapse
I hope it works for ya how it worked for me :highfive:

Joku1981 said:
I hope it works for ya how it worked for me :highfive:
Click to expand...
Click to collapse
DONE!
But, I was trying to unlock bootloader. Where I can see if it worked? Now I see that my sdcard0 has formatted with internal data. But I'm trying to install CWM with a kernel.elf (autoroot & CWM) using Flashtool. But... Flashtool says that I must be rooted before doing this. WUT?
Edit: I also see that I lost DRM keys, but I've got a backup to restore them. So... bootloader is unlocked!
Edit: RESOLVED! I restored DRM keys before flash kernel.elf, and it was wrong. So I repeated the procedure without DRM keys and... beautiful CWM with root now I think I can restore my DRM keys. Heheh

Request Driver for ADB Detection CMD for NOKIA 8

I have a problem after updating to latest June Security patch for Nokia 8 TA-1004. I had installed driver long time ago when I wanted to obtain root and there I did it. However, after updating to latest patch which also causes to lose root, I couldn't get my phone to detect adb in cmd. I tried reinstalling driver but still not working. USB Debugging is also on. What could this be the problem? I need help. I want to obtain root back. Thank you very much in advance.

Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.

Get that fork of ADB and Fastboot and use it straight out of cmd :
https://developer.android.com/studio/releases/platform-tools

Rakaloah said:
Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.
Click to expand...
Click to collapse
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !

webvan said:
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !
Click to expand...
Click to collapse
Have a look at my post: https://forum.xda-developers.com/showpost.php?p=78074773&postcount=67

Thanks.

Fastboot Devices comes up empty

im on w10 and im having trouble using fastboot commands through cmd (in a folder with the files)
my device is not showing up when i type "fastboot devices" when i go into fastboot mode or flash mode
when i open cmd and type in "fastboot boot twrp.img" or "fastboot flash recovery twrp.img", it gets stuck saying "< waiting for device >"
but when i use flashtool, it recognizes that im in fastboot mode or flash mode
i have installed:
adb drivers
fastboot drivers
flashtool
platform tools
android sdk
google usb driver
i have tried uninstalling the drivers and reinstalling them through device manager
my device shows up as "S1Boot Fastboot"
my main objective is to get twrp in order to flash oreo carbon rom with magisk

Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.

LaRazón said:
Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.
Click to expand...
Click to collapse
sucha simple fix lol
thanks

Can't connect in fastboot, driver issue?

After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.

LuminousOne said:
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
Click to expand...
Click to collapse
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'

Didgesteve said:
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Click to expand...
Click to collapse
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?

LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I'm not sure what you're trying to do. If you want to flash a rom, you want flashmode, volume down (-) then plug in the USB. If you want fastboot it's volume up (+) then plug in the USB..
MTP driver is wrong, you need to uninstall it and re-install the sony driver. Windows chooses the wrong driver by default and you have to manually add it yourself to make it work.
Having said that you mentioned that you are getting ADB commands to work, so I'm confused, perhaps the google driver is in place, but the Sony one is not.
You need both, when the phone is in fastboot it's presented as a different device than when connected via ADB.
Hope that helps explain a bit.
But if you're having issues with the drivers, should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.

LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I had this problem before. My fault before was install drivers in usb-debugging mode, then a change to fastbook/flash, and then the phone is not recognized or connection properly - despite me thinking I had correctly installed the drivers.
Took me months to figure it out. Boot into windows, then connect your phone in all modes, flash mode, fastbook mode, standard, and usb debugging - and for each mode - install the Sony driver again.
The result will be, that for every mode - when you go to device manager - you won't see an exclamation mark. If you ever see an exclamation mark again - install the driver. You get the idea.
Regards,

I finally found the f**kin problem the invalid driver was hiding under "other devices" only when the phone was in fastboot mode. Basically I followed the instructions of user2021355 from here.
Start Windows in test mode (instructions)
download driver from https://developer.sony.com/develop/drivers/
in admin command prompt run adb reboot bootloader
if the above step failed, you have a problem with adb and the solution is something different
open device manager and carefully search for any errors. I found mine hidden under "other devices"
right click on the errored driver and choose update
choose browse my computer
select the driver you downloaded from step 2
verify if working by running fastboot devices and you should get a serial number

Didgesteve said:
should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
Click to expand...
Click to collapse
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?

LuminousOne said:
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
Click to expand...
Click to collapse
Some banking and games apps don't like rooted phones.
Not sure about android pay.

Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
same is when pointing to the drivers from here: https://developer.android.com/studio/run/win-usb
I ve the G8441

sheedy1900 said:
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
I ve the G8441
Click to expand...
Click to collapse
Add the driver manually.

Didgesteve said:
Add the driver manually.
Click to expand...
Click to collapse
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.

OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement

LuminousOne said:
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
Click to expand...
Click to collapse
I think we have different ideas of what adding the driver manually is

sheedy1900 said:
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
Click to expand...
Click to collapse
i have the problem as you and I'm also on win10. can you share how you installed the fastboot driver?
the adb and mtp drivers work fine for me, just fastboot is not working

unsigned driver under W10
try this one
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Gesendet von meinem viennalte mit Tapatalk

I have the same problem with my Sony XZ1 Compact G8441.
'adb devices' shows my phone, after 'adb reboot bootloader' phone goes into fastboot mode (I think), the one with blue LED, but 'fastboot devices' does not show any connected devices. Same when pressing Volume Up or Volume Down while plugging the phone in.
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Tried installing through device manager, right-click on faulty 'Android' under 'Other Devices', update driver, browse to download location.
With 'Sony XZ1 Compact driver' it found no installable drivers.
With 'Sony Fastboot Driver' it found an installable driver but had an error. Error said something like 'Did not find "Android ADB Interface", installation failed'.
I tried figuring out what you guys meant by 'installing driver manually' but I don't understand. Is it what I tried above, or something else?
My goal is to be able to install TWRP, which needs an unlocked Bootloader first. I followed the instructions on the official Sony Website for that.

Sorry. Delete this.

Gnorv said:
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Click to expand...
Click to collapse
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.

Didgesteve said:
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Click to expand...
Click to collapse
No, that did not help. The same problem remains. Phone is recognized when powered on by 'adb devices' but not recognized after typing 'adb reboot bootloader' and 'fastboot devices'.
Thanks for your suggestion though.

I got the problem that no matter what i do i can't install the driver.
Booting windows 10 with driver check disabled does not solve my problem.
Once i selected the driver to install i end up with a questionmark in the device manager above the android device. Taking a closer look reveals that there seems to be no driver installed.....
Any advice?
I tried:
1. Booting with driver signature check disabled
2. Switching windows 10 into test Mode
I booted ubuntu from a live usb stick and went from there. That works like a charm without the need of installing any drivers
Both solutions do not work....

Can't unlock bootloader - fastboot issue

Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!

TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Hii. you go to device manager. find your phone in unknown device. Update the driver using i have a disk option. Then try again. it will work.

Disable windows 10 Driver signature and install Fastboot USB drivers again.