Related
Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959
Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.
beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.
I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks
yeah did my search to no avail. followed all the steps and even a few extra once i ran into this problem and a few solutions even on xda and i cannot seem to get this to work. all the drivers installed correctly but when i restart into bootloader it says it ran into a problem while trying to install driver but its installed but says device cannot start. dont know what im doing wrong guys any help would be great. windows 64 bit nexus 7 v2 newest update 16gb wifi only.
mixalot2008 said:
yeah did my search to no avail. followed all the steps and even a few extra once i ran into this problem and a few solutions even on xda and i cannot seem to get this to work. all the drivers installed correctly but when i restart into bootloader it says it ran into a problem while trying to install driver but its installed but says device cannot start. dont know what im doing wrong guys any help would be great. windows 64 bit nexus 7 v2 newest update 16gb wifi only.
Click to expand...
Click to collapse
Make sure USB debugging is enabled in developer options
Then do this: Setting's > Storage > Click the ellipsis top right of the screen the 3 dots) > Select Camera (PTP)
Now when you connect your phone to your laptop etc you should get an address id authentication prompt, tick the checkbox and click ok.
You may also need to install android sdk if you don't have correct drivers or whish to use cmd prompt adb
Wezi said:
Make sure USB debugging is enabled in developer options
Then do this: Setting's > Storage > Click the ellipsis top right of the screen the 3 dots) > Select Camera (PTP)
Now when you connect your phone to your laptop etc you should get an address id authentication prompt, tick the checkbox and click ok.
You may also need to install android sdk if you don't have correct drivers or whish to use cmd prompt adb
Click to expand...
Click to collapse
Cool debugging is enabled and SDK is installed but haven't tried the camera option. Will try after work and update. Forgot to add that adb work its only fastboot that isn't recognized.
mixalot2008 said:
Cool debugging is enabled and SDK is installed but haven't tried the camera option. Will try after work and update. Forgot to add that adb work its only fastboot that isn't recognized.
Click to expand...
Click to collapse
Fastboot only works in bootloader. To get to bootloader, power off, then hold power and volume-down. Does that work?
That's just it. Bootloader works just fine but its not working on my PC. It recognizes it as android boot loader interface but says device cannot start so I can't do crap with fast boot Lol that's why I'm confused I've never had this issue
Sent from my SGH-T959V using Tapatalk 4
How do you know that drivers installed correctly? Was there a popup?
mixalot2008 said:
That's just it. Bootloader works just fine but its not working on my PC. It recognizes it as android boot loader interface but says device cannot start so I can't do crap with fast boot Lol that's why I'm confused I've never had this issue
Click to expand...
Click to collapse
Either the drivers that got installed are the issue or you have cable/port issues.
I actually just gave up with me PC and switched to my wife's which I had done a ton of rooting before including my original nexus 7 and it went smooth without a hitch so Idk what the problem was
Sent from my SGH-T959V using Tapatalk 4
As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:
panha510 said:
As stated, I cant acess usb debugging.. I've already connect my phone to pc but it just only show charging.. I also cant copy file to my pc.. what is the problem here? :crying::crying::crying:
Click to expand...
Click to collapse
HTC manager also wont recognize my phone..
panha510 said:
HTC manager also wont recognize my phone..
Click to expand...
Click to collapse
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...
bratusm said:
It was written so many times on XDA Forums, that your question is quite a surprise:
Open Settings, then go to phone details (where u can see kernel, Android-version etc) then just tap your Build number enough times until you're developer! Then enable USB Debugging...
Click to expand...
Click to collapse
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.
panha510 said:
I've already know that, it is when I plugged my phone into the computer, the battery indicator is charging, but the USB connection never happens.
Click to expand...
Click to collapse
System? Win XXX, Linux...
HTC Drivers?
bratusm said:
System? Win XXX, Linux...
HTC Drivers?
Click to expand...
Click to collapse
windows 7, i already installed the htc driver..
If you can't access it, go into your settings app on your phone
Open Developer Options and click the checkbox that says
Code:
USB Debugging
If it still doesn't work, install HTC Sync Manager (if not installed already)
Restart your phone into the bootloader (by holding [Vol Down] + pressing [Power] for a second, still holding [Vol Down]
Select 'Fastboot' at the menu that shows up
Plug in your phone, ignore HTC Sync Manager, open a command prompt (admin) by hitting [WIN] + [X], then select
Code:
Command Prompt (Admin)
Once you have done that, cd to your directory of the adb and fastboot executables, like this:
Code:
cd "C:/[your directory]/"
Then
Code:
adb devices
If adb detects that the service isn't running, it'll start it then search for your device. If it finds it, you're set to use the fastboot commands for whatever you want
Good luck guys!
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** offline
Looks like MTP mode adb cannot connect to H811 at all.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
eruisi said:
I already enabled OEM Unlock and USB Debugging in Developer options.
then I connected my LG G4 H811 to PC and confirmed MTP.
adb devices just shows:
List of devices attached
If I select USB charge instead of MTP, the adb devices shows:
List of devices attached:
LGH811***** offline
Looks like MTP mode adb cannot connect to H811 at all.
Does anyone know the reason? Really need to unlock bootloader and then root my phone.
Thanks
Click to expand...
Click to collapse
its beacause your mobile's Debugging didnt alowed that usb connection. when u type 'adb device' there should be a popup on your device asking to connect to pc. choose Allow. it will be online hen.
Thanks for the reply!
But there is no popup on the phone when I type "adb devices". The only popup I see is when I connect PC and phone with USB, a popup on phone asks me "Allow this computer to access your phone data?" I choose "Yes"
Any help will be much appreciated.
eruisi said:
Thanks for the reply!
But there is no popup on the phone when I type "adb devices". The only popup I see is when I connect PC and phone with USB, a popup on phone asks me "Allow this computer to access your phone data?" I choose "Yes"
Any help will be much appreciated.
Click to expand...
Click to collapse
You need to enable USB debugging in developers options.
Sent from my LG-D801 using Tapatalk
bxlegend said:
You need to enable USB debugging in developers options.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I enabled OEM unlock and USB debugging both in Developer options.
eruisi said:
I enabled OEM unlock and USB debugging both in Developer options.
Click to expand...
Click to collapse
If all the checks boxes are ticked, try revoking USB debugging authorizations. Connect your device as MTP (try PTP as well) and try to adb devices again and see if you get the pop up on your phone. Last option would be to boot into recovery via button combo and reboot into the bootloader from there.
Sent from my LG-D801 using Tapatalk
I tried all of your suggestions, none of them work.
PTP/USB charging mode, adb devices shows:
List of devices attached:
LGH811***** offline
MTP shown no device attached...
I did get into download mode (bootloader mode I think) - screen says Firmware Update, do not unplug the USB connection until the process is complete
Then I tried to run fastboot oem unlock, it stucks at
< waiting for device >
and there is no change on phone screen.
Any other ideas? I really need to root my H811. Appreciate any suggestions!
Change to PTP mode.
Gesendet von meinem LG-H815 mit Tapatalk
It sounds like your usb drivers ars not properly installed. I would try uninstalling and then reinstall. Did you happen to install LG Bridge?
Sent from my LG-H811 using Tapatalk
eruisi said:
I tried all of your suggestions, none of them work.
PTP/USB charging mode, adb devices shows:
List of devices attached:
LGH811***** offline
MTP shown no device attached...
I did get into download mode (bootloader mode I think) - screen says Firmware Update, do not unplug the USB connection until the process is complete
Then I tried to run fastboot oem unlock, it stucks at
< waiting for device >
and there is no change on phone screen.
Any other ideas? I really need to root my H811. Appreciate any suggestions!
Click to expand...
Click to collapse
Download mode is not the recovery. If you have TWRP installed as your recovery, power your phone off completely and disconnect it from the computer. Then press and hold volume down and power. Keep holding and when you see the LG screen, release only the power button and press and hold it quickly again (you should still be holding volume down). This'll take you to the factory reset screen, select yes twice and you should be taken to twrp. REMEMBER, ONLY DO THIS IF YOU HAVE TWRP INSTALLED!
Sent from my LG-D801 using Tapatalk
I dont have TWRP installed
The phone is in initial state from factory and has been upgraded to MM 20O
eruisi said:
I dont have TWRP installed
The phone is in initial state from factory and has been upgraded to MM 20O
Click to expand...
Click to collapse
Ohh...follow the op in this thread.
Sent from my LG-D801 using Tapatalk
I followed all steps in the thread you list. I am stuck at "adb devices" where I didn't see my phone is listed if I connect with MTP mode. For USB charge or PTP, I see devices but it is offline.
With this problem, I cannot get my phone reboot into bootloader mode and run oem unlock/twrp.
eruisi said:
I followed all steps in the thread you list. I am stuck at "adb devices" where I didn't see my phone is listed if I connect with MTP mode. For USB charge or PTP, I see devices but it is offline.
With this problem, I cannot get my phone reboot into bootloader mode and run oem unlock/twrp.
Click to expand...
Click to collapse
Did you tried revoking the usb auth?
http://forum.xda-developers.com/g4/development/unlock-bootloader-h811-20o-t3459285/post68630578
Do you receive a popup afterwards when connecting the usb cable?
PTP or usb charge should be fine.
What OS are you running?
.
I am using Window10 on my PC.
I made a tiny progress: I installed LG Bridge software and it updated LG driver on my PC. Now when I connect phone to PC with USB (of course I choose "ALLOW" for popup USB Connection Allow this computer to accept your phone data?). Now I see devices under MTP mode but it is still offline so I cannot boot it into bootloader mode. There is no popup when I run adb devices.
I tried revoke USB auth a couple of time, no luck
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
eruisi said:
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
Click to expand...
Click to collapse
flash tt36 uss enterprise rom ots fast.
http://forum.xda-developers.com/tmobile-g4/development/t-mobile-lg-g4-h-811-mm-20o-tt10-uss-t3411769
I am having a different problem, i get to all these step but when I type fastboot oem unlock it gets stuck at waiting for device no matter how long i let it sit. I know there is no problem with adb because it shows the device with the serial number, I just can't unlock the boot loader
eruisi said:
Finally I made it work!
The reason is adb I was using is too old
I changed to 1.0.31 then it works w/o any issue.
Thanks for the help all the way! I really appreciate your patience.
Click to expand...
Click to collapse
OP @eruisi
Dont you know that this doesn't belong to the Android Development section?
Please be sensible and post in the right section and create threads only when it is actually required.
By using SEARCH and PM to other members...many things get solved with less and accurate results
Thread moved
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
jaw2floor said:
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
Click to expand...
Click to collapse
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
faby GT said:
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
Click to expand...
Click to collapse
Hi thanks for getting back to me,
I assume you meant the '15 second installer', which I just did just install successfully. I am still unable to see the device with 'fastboot devices' command.
Other info: I have factory reset the phone, made sure oem unlock is checked, tried the same process on another computer. I can get adb mode to work fine, but the command 'adb reboot fastboot' just reboots the phone as usual
jaw2floor said:
The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED.
Click to expand...
Click to collapse
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
schmatzler said:
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
Click to expand...
Click to collapse
If it won't work, after that just go to devices and printers and delete Xperia XA2. It will work.
Else, after installing 15 seconds, inside device manager, update the driver of your phone (or mtp device), select local, then Android device, then fastboot. Disconnect the phone and reconnect as before (volume down)
Fastboot is VOL. UP (on this device)! (Not vol. down)
So basically turn off the device, hold Vol. UP and simply connect to USB, hold Vol. UP until LED is steady blue and you are set.
Note: VOLUME UP activates fastboot and VOLUME DOWN enables flashmode and/or recovery mode
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Corias said:
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Click to expand...
Click to collapse
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
BoernMe said:
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
Click to expand...
Click to collapse
Did solve this by connecting to different PC. No cable/port/hub change did help. Looks like there was some trouble with drivers (though the same PC fastboots Z3 Tablet Compact perfectly).
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
that_random_guy said:
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
Click to expand...
Click to collapse
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
I had the same problems with my device XA2 H3113 and Win10.
My solution: Try it with Ubuntu. Just grab an 8GB usbstick, install Ubuntu via usb-installer, boot ubuntu and open a terminal
sudo apt update
sudo apt install adb fastboot
LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
Hey can you please provide me a link to the drivers? as I've been trying so many drivers and they don't work.
LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
works for me