Develop Bugs

Problem unlocking bootloader

Hello i have a problem unlocking the bootloader of my xperia sl. The problem is when i turn off my phone to blue led, suddenly it goes to orange then began charging? What do? I have checked my rooting status and the bootloader is allowed:yes .. Please help me, if there's a solution thanks more power

doodoot_09 said:
Hello i have a problem unlocking the bootloader of my xperia sl. The problem is when i turn off my phone to blue led, suddenly it goes to orange then began charging? What do? I have checked my rooting status and the bootloader is allowed:yes .. Please help me, if there's a solution thanks more power
Click to expand...
Click to collapse
Do just that :- Step By Step
- open device manager
- connect in fastboot mode and click the s1 boot fastboot right away
- disconnect the device , without closing the s1boot fastboot windows !
- click update drivers -> browse for drivers on my computer -> let me pick from a list of device drivers on my computer
-> have disk -> browse and locate the device drivers -> press ok
- reconnect the device in fastboot and click next on the computer right away of the blue led

hello bro it says it encountered an error, the android ADB something bro

white paranoia said:
Do just that :- Step By Step
- open device manager
- connect in fastboot mode and click the s1 boot fastboot right away
- disconnect the device , without closing the s1boot fastboot windows !
- click update drivers -> browse for drivers on my computer -> let me pick from a list of device drivers on my computer
-> have disk -> browse and locate the device drivers -> press ok
- reconnect the device in fastboot and click next on the computer right away of the blue led
Click to expand...
Click to collapse
doodoot_09 said:
hello bro it says it encountered an error, the android ADB something bro
Click to expand...
Click to collapse
I think you dont need to disconnect the phone...
Open Device Manager in your windows, standby at that....Turn off your phone, and after it turned off, push and hold the Volume Up button and at the same time connect the phone to the computer with a USB-cable. This will trigger FASTBOOT mode and windows will start driver search....
Once there is a popup in Device Manager with what word i cant remember, directly right click on it and point to the folder containing the driver...If the folder youre having, failed to give the driver required....Download driver below, my driver compilation...
http://www.mediafire.com/?dw77ineguikk7bo
Unzip the Xperia_Ion_Fastboot_USBDriver.rar and unzip both files that came out
that is fastboot_with_Android_USB_file.rar and drivers.zip
Point out the driver search to drivers.zip folder...Hope it helps

Google drivers not working on Nexus 5X/Marshmallow on Win7 - Is the phone too new?

I have my new Nexus 5X with Android 6 on it. I am trying to unlock and root.
I have enabled USB debugging and OEM unlock.
I have downloaded and installed the SDK package with Platform-Tools and drivers in the 'Extras' folder.
When first plugging in the phone I install the drivers with the 'Have Disk' and browse method.
Every time, installing the driver returns an Error 'Code 10 - device cannot start. 'Android ADB interface' shows up in device manager when I plug in the phone but with an exclamation point.
I have uninstalled, downloaded fresh drivers from other sources, reinstalled, tried plugging the phone in while in 'recovery' mode (starting by pressing all 3 hardware buttons).
I uninstall every time and reboot both the computer and the phone. The drivers simply won't work.
What is going on here? Is the phone/Android 6 still too new to unlock and root?
P.S. I should also say that I go into Developer options and change the Select USB Configuration between PTP and MTP (between which, I have not seen mention of the correct choice. Does it not matter?) - I cannot chose the others RNDIS, Audio Source, or MIDI; it seems to want to default to 'Charging' when I try to change to these choices.

Having the same issues on Windows 8.1. Can't get my 5x to connect to transfer files or to show up in adb.

Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok

bsinc1962 said:
Just need the right drivers. Download the driver files from here: https://www.dropbox.com/sh/e43knzpxvr9hzqi/AAC7Yiz8EShMpFiMkClPpkC5a?dl=0
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.

ahunter said:
I've got the same problems & the driver did not fix it. My computer won't use the android_winusb file gives me an error that it is not a 64 bit system fle. Same with te official google file.
Click to expand...
Click to collapse
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.

rgerrans said:
I was running into the same issue. The problem is you need to install them first as an ADB Interface Device (not composite) with the phone on and plugged in. From Device Manager choose the Google | Android ADB Interface (not the composite one. I saw another reference to making sure it's in PTP mode which may force it to this one as well but I didn't test). Then when you get into FastBoot mode on your phone and plug it in you can go through the same Update Driver steps and choose the "Android ADB Interface" for it as well when it shows the Nexus 5 with the yellow triangle. Then you should be good to go.
Click to expand...
Click to collapse
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?

ahunter said:
My phone shows up as a portable device/Nexus 5x . Are you saying it should be in Device Manager choose the Google | Android ADB Interface?
Click to expand...
Click to collapse
Sorry. I should have been more specific. Part of it is I did so many different approaches they've bled together in my head and I was on my way out the door yesterday when I fired off the reply.
To try to break it down from memory (going to throw in a couple of different options since I can’t seem to fully uninstall / reinstall so please provide any corrections once you get it to work or let me know if anything doesn’t match what you find and I’ll try to remember from there):
Phase I (phone on and connected to computer):
Open Device Manager. My phone shows as Android Device | Android Composite ADB Interface or Android ADB Interface.
If it is the Composite version, I believe I had to update it to the straight “Android ADB Interface to get Phase II to work)
If you don’t see that, look to see if you have any uninstalled devices by scanning for new. If so, then right click on that device, and choose “Update Driver”
Choose “Browse my computer for driver software”
Choose the “Have disk” option and browse to your USB Driver folder
From there, choose “Google | Android ADB Interface”
Phase II (phone in recovery connected to computer)
On phone, choose “Update device from ADB”
Open Device Manager and you should see the Nexus 5 under Other Devices with the yellow triangle.
Right click on it and “Update Drivers”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list….”
Choose “Android Device”
Choose “Android ADB Interface”
Now you should be able to push the update over

Simple method: What I did was plug it in and wait for it to show up in device manager. Then I deleted the device (the one that shows adb) from device manager. Then I unplugged the device and plugged it back in... Then waited for drivers to install on it's own. Everything was good after that.

I have no trouble other than on Windows 10. Windows 10 doesn't even show the drivers from a list to install.
Sent from my Nexus 5X using Tapatalk

I followed this to get my Nexus 5X detected on my Windows 10: http://stackoverflow.com/questions/...ould-we-use-for-the-nexus-5/19839812#19839812

I have no trouble with Fastboot or adb. It only happens when I try and sideload. I end up have to use my Macbook Pro to sideload.
Sent from my Nexus 5X using Tapatalk

bsinc1962 said:
Just need the right drivers. Download the driver files from here:
1. Then with the phone plugged in and in PTP mode go into the device manager on your PC.
2. You'll probably have an Android device listed with an exclamation point showing. Right click on it.
3. Pick update driver.
4. Pick browse my computer for driver software.
5. Then pick "let me pick from a list of device drivers.
6. Then pick have disk.
7. Navigate to the folder you downloaded and select android_winusb
8. Let it install and you should be ok
Click to expand...
Click to collapse
I wish it were that easy. But, no, this does not work. Nor do I believe my issue is the same as you others here, as I have Windows 7 and not the 8.1 and 10 issues that you are having.
No, no matter what driver I use, including any from your kind link, bsinc1962, they return an error, code 10 when trying just to install the drivers. I cannot go further.
What is this Code 10 error preventing drivers from installing?

unable to unlock bootloader

Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.

I always use something called 15 Second ADB Installer when setting up ADB and Fastboot on a new computer. It installs all the correct drivers as well, so maybe that would solve your issue. Also, be sure to check Device Manager in Windows and see whether there are any devices showing with yellow caution symbols besides them.
If you find your phone displaying like this; right-click and choose 'Update driver', then 'Browse my computer for driver software' and 'Let me pick from a list of available devices on my computer'. Find Google Inc. and choose the one which says 'Android ADB Interface'. You have to do this AFTER running the 15 Second ADB Installer otherwise it won't work.

Definitely driver related, remove and reinstall etc but don't give up haha sometimes its a PITA to install the correct drivers...

satya365 said:
Yesterday i got my zuk z2 plus 64gb. I installed adb driver on pc & enable usb debugging from zuk z2 plus. I connect my phone to pc, Grant the usb debugging permission, extract the adb setup, shift button & write click. Now the cmd is open. When i enter "adb devices", my device is not showing.
Click to expand...
Click to collapse
Download MIFLASH TOOL, it installs all the drivers needed for Z2

[HELP] MI a2 lite Fastboot Exits aAutomatically

I have a mi a2 lite and i want to unlock its bootloader, i have alrready enabled oem unlocking on developer options, when i boot my device in fastboot and connect to computer, command window says waiting for device and after 15-20 seconds of connecting my device to my pc, fastboot mode automatically exits and shows charging animation. Please anyone can help?
My device is in andoid pie (stable).

Check if you have installed drivers and run "fastboot devices" to see if device is recognised.

Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.

hossman said:
Agree something with your PC.
Phone will automatically exit fastboot if no connection in timely manner.
Check drivers are installed, reboot your PC.
Also be sure USB debugging is on in Dev option and trust PC.
For me, I generally boot Android normal. Then plug into PC and from command line, "adb reboot bootloader". That should verify adb, If that doesn't work, your PC not talking to device.
Click to expand...
Click to collapse
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.

I've tried restarting my pc as well as my phone and after 5-6 attempts it is now unlocked.
Thanks guys for supporting and giving response to my post
Love ya'll

CherryFarmer8 said:
I reinstalled the drivers and the command "adb reboot bootloader" works for me that means it boots to fastboot mode but when in fastboot mode, when i enter a command "fastboot devices" it does nothing and when i enter command "fastboot oem unlock" it again says waiting for any device.
i have attached a screenshot of it.
Click to expand...
Click to collapse
same problem boss, did you already solved this? please help me out

Andrew.kathy said:
same problem boss, did you already solved this? please help me out
Click to expand...
Click to collapse
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA

capajga said:
The solution for fastboot disconnecting after a few seconds are the windows drivers. There are different drivers for our phone, normal, bootloader and fastboot. Windows loads these drivers depending in which state the phone is.
If you still didn't find the correct drivers, you should try installing MiFlash, as it contains all the needed drivers for our phone
If you like to try the Linux way, there's a distro called FWUL linux here on XDA
Click to expand...
Click to collapse
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate

CherryFarmer8 said:
Yeah, just go to windows drivers, click update device driver, browse my computer, let me pick, choose android > next > and choose another version or try whatever you feel is appropriate
Click to expand...
Click to collapse
I also have this problem drivers are installed and fine but when I go to fastboot within like 15 sec it automatically turns off.

I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/

adb wont work in my realme 6 pro? Whyyyy. i cant root my phone or bootlock it.

help me please.

the same happens to me

crossf015 said:
help me please.
Click to expand...
Click to collapse
Explain

You need to have the correct drivers installed on you computer. Does you computer recognize your phone when you plug it into computers USB port ? If it does then install the latest ADB Fastboot software into a folder on C: drive not inside of other folders or libraries like shown in the 1st picture.
Then go to that folder and in the address bar show with arrow in 2nd picture 2) click mouse where the red arrow is to highlight like shown in 3rd picture then press delete key then type --> cmd ,like shown in 4th picture and press enter. Plug your phone into the computer with USB and type in the command terminal --> adb devices ,and you phone should be listed. From there you can reboot fastboot to see if you phone is still connected type --> fastboot devices , your phone should be listed.

My laptop only recognizes my phone when it is open and me enabling "file transfer" prompt/popup. I am om 6 pro and I can't open my phone because of the flicker issue. How can I at least access adb other than this?
oxbowlarry said:
You need to have the correct drivers installed on you computer. Does you computer recognize your phone when you plug it into computers USB port ? If it does then install the latest ADB Fastboot software into a folder on C: drive not inside of other folders or libraries like shown in the 1st picture.
Then go to that folder and in the address bar show with arrow in 2nd picture 2) click mouse where the red arrow is to highlight like shown in 3rd picture then press delete key then type --> cmd ,like shown in 4th picture and press enter. Plug your phone into the computer with USB and type in the command terminal --> adb devices ,and you phone should be listed. From there you can reboot fastboot to see if you phone is still connected type --> fastboot devices , your phone should be listed.
Click to expand...
Click to collapse