Hey so like i have a problem. It\s seems to be to simply impossible to get any drivers to work, i tried everything google drivers, sdk ,drivers that come on phone and drivers from some random websites. Nothing works, tried both w10 and linux ubuntu. On my older pc i had 0 issueas other than simply doing something dumb.
Im out of ideas, help? Also tried with sony z5 premium instead of my nokia 7 plus but same thing -_-
Sidenote:fastboot device from phone drivers kinda works(?) But still im not able to do anything because im stuck on waitig on devices when i want to flash
To manage an Android phone from PC you at least need
1. ADB - provided by Google
2. FastBoot - provided by Google
3. Android-USB-driver provided by OEM/Carrier matching your phone
and nothing else.
Have all of those and im stuck on waiting on devices after i reboot to bootloader. Seriously annoying maybe i will try on other pc and see what happens but its not really a solution
If your phone supports Fastboot - take note that not all phones do - then when Fastboot returns "Waiting for device" it's a driver problem: Install correct driver.
True but as i wrote official drivers don't work it's on the phone after all. Rest doesn't work too then . Heh
Related
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
For me, it was a wiring problem. I hadn't got the original wire plugged, but a second one bought in ebay. Then I used the original one, and problem solved. I hope it is your problem.
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Try using the Universal Naked Drivers instead.
http://forum.xda-developers.com/showthread.php?t=2139767
Tajmoti said:
It is showing my device in "adb devices" when it is turned on, but it is not there when it is in fastboot mode, i cant flash any img, it stucks, i have done everything, unlocked bootloader, everything. But fastboot doesnt see my device, i have done a bit of research and i realised that it is showing SAMSUNG drivers under my ASUS device tab in that device manager, i have seen this problem in another topic and they said they have uninstalled those samsung drivers trough control panel and it worked for them, but i tried that and installed google drivers from google SDK, ASUS drivers that came with aus sync, both at once, then 1 of them and neither worked and i have tried like 95581546 things, reinstalling, uninstalling,restarting pc, disabling antivirus, and i cant get adb to see my device in fastboot. And in hdwwiz, when i am installing drivers manually it shows me Samsung drivers in Asus group and i dont know how to remove them from there. Or any ideas how i can get it to work?
Thanks
(sorry for grammar nazi and for this topic in wrong section, but i cant make new threads under "Development" because this is my first post)
Click to expand...
Click to collapse
Have you tried a different USB port on your PC? I know when I first started customizing my tablet I had problems using the front ports on my PC. It wouldn't recognize my tablet in fastboot, but when I plugged into one of the back ports directly on the motherboard it worked great.
Ehh
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Solved
Tajmoti said:
I have reinstalled drivers few times and plugged it to back of the PC and it works! It is still not showing my tablet in adb devices (now i am not sure if it should show it there in fastboot) but the img transfer has finished and everything is fine, thanks for all help!
Click to expand...
Click to collapse
@Tajmoti can you add solved to the thread name...
lj50036 said:
@Tajmoti can you add solved to the thread name...
Click to expand...
Click to collapse
I dont know how LOL
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead (Edit: For a strange reason, it didn't update to the latest version available.)
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Almogpas said:
Heya. First things first:
My Google Nexus 5 is quite... Well bricked.
I've updated CarbonROM a couple of hours ago and since then the phone's been stuck on the Google Logo, as well as starting automatically after shutting it down.
Here's some specifications:
Recovery: ClockworkMod Recovery v6.0.4.5
ROM: Carbon. The version I updated to was CARBON-KK-NIGHTLY-20140706-0428-hammerhead
I've tried performing:
Reinstall of the same Rom
Factory reset
Following the many unbricking tutorials that require the computer to actually recognize the phone yet no "Nexus 5" appears... Actually nothing appears in devices other than my regular devices.
Phone has been already rooted (obviously) using tutorials here on XDA.
Please help :3
Click to expand...
Click to collapse
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
bitdomo said:
if no new devices appear in your device manager we cant yet do much for you. Get the phone recognised in fastboot or in recovery on any pc then restore stock rom or sideload new rom
Click to expand...
Click to collapse
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
hmmm... try lg flashtool. Link in my signature.
Almogpas said:
Do you think I should get a new phone or maybe take it to a professional? I just can't get the pc to recognize it even though I have the drivers installed. (Although even if the drivers weren't installed it would still recognize it...)
Click to expand...
Click to collapse
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
http://developer.android.com/sdk/win-usb.html
doctor_droid said:
Adb drivers are different when compared to mtp drivers (windows reconizes it as mtp when swtiched on) ... U need adb drivers for pc to recognize it in fastboot mode...will fetch u the link wait
Click to expand...
Click to collapse
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Almogpas said:
The main problem in all these solutions is that the phone isn't even recognized by the computer. I'm pretty sure it's the computer's problem but you may never know. Tomorrow I'm retrieving my main rig and I'll post if that rig discovers my phone. If it does, it will make me happier than Columbus discovering America. It not, it will make my wallet really sad as I will be obliged to buy a new one.
Click to expand...
Click to collapse
Yup if the pc is not detecting the phone best is to try wid another usb cable and a different pc... let us knw tomorrow
Did you install those libraries properly?
Freshly baked from my Nexus 5
This universal ADB driver + this ADB and Fastboot pack always does the trick for me.
When you get either ADB or Fastboot working we can help you recover the device.
Hi! So I'm new in this forum and I'm trying to flash Xperia xa2 Ultra H3223 but had two problems, first I try flashing with Flashtool but no matter what it said "no partition delivery" or something "yes to continue", found some forum and said something about copying file 50.2.fsc and manually sync but again, clicked and nothing happened. Then I installed Emma but the only firmware was from the US (I'm from Mexico) and was a custom old version 50.1 with no other option. Finally, I just installed Newflasher, follow the instructions and nothing, just this:
"ERROR: TIMEOUT: failed with error code 997 as follows:
Se estß ejecutando la operaci¾n de E/S superpuesta.
- Error write! Need nBytes: 0x18 but done: 0x0
nBytes[0x0]:
- Error writing command getvar:max-download-size!
End. You can disconnect your device when you close newflasher.exe"
I've done everything, followed every tutorial and nothing seems to work.
By the way, I'm trying to flash firmware 50.2A.3.22, last year my phone bricked and the only thing I found was firmware Commercial and Journalists wich worked well but now I want to try other version and then LineageOs but guess I'll have to wait.
Don't know what I'm doing wrong, if I turn on my phone works perfect and nothing been erased.
My device is bootloader unlocked and no root.
Please let me know if you need to know something else, I'm not desperate but was kind of excited to try Lineage
Thanks!
I had the same problem with my H3113.
While I had installed flashtool and the drivers that come with it, it seems like they are too old for the XA2. They are from 2014.
What I had to do was get flashtool from the Sony website and open up the .exe with 7-Zip:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
Inside of that is the file Sony_Mobile_Software_Update_Drivers_x64_Setup.exe - this one installs a driver from 2017.
After a reboot, flashing with Newflasher worked. What a damn pain!
I had the same problem and can confirm it works. I wish I saw this comment earlier.
If you flash with flashtool will it relock bootloader?
I am running Windows 10 Pro v. 21H1 and also have a Sony H3223.
I am trying to install the latest plain LineageOS on the phone for which is still supported. The H3223 is unlocked so there are a variety of guides for different flashing projects.
LineageOS wiki suggests installing a universal ADB driver which sadly does not apply for this phone. So I then took a peek at SailfishOS and their flashing guide... incidentally, they specify the use of Sony's Xperia X driver. This forum has a thread suggesting the use of Sony's Xperia XZ2 driver.
SailfishOS was specifying the XZ2 driver as well until they updated their guide for Windows 21H1.
I have tried to install both drivers in alteration—both times I uninstalled everything Android via safe mode—and both drivers will not properly install. I get the icon with the yellow triangle badge in my Device Manager list for 5 seconds but then it changes immediately to the questions mark badge and is only visible after showing hidden devices. This is true even while the phone is plugged in.
The phone is being connected via the included USB cable and is being plugged into a USB 2.0 port on my PC.
The phone when connected does get picked up by Windows and I get listings in other places under Device Manager. ADB sees my phone when I run any adb commands but booting into fastboot mode makes the above happen every time.
In other words, when I connect the phone to my PC, Windows installs some driver from who knows where. At this point, adb commands work but fastboot commands don't work. After this, I uninstall the stuff Windows sets up and I boot the phone into fastboot mode only. When this happens, Windows only shows an Android listing under Device Manager for hidden devices. This is the same device that is designated for the driver update in any guide I find... so at this point I have tried updating this object with the Xperia X and Xperia XZ2 drivers. The Sony object that's supposed to get added to the device tree is never added an instead it's as if nothing happened.
I have followed both the LineageOS guide and SailfishOS guide and I have no clue why Windows will not update the driver. There is nothing complicated about either guides... as I said, adb commands work but that is without me installing any driver and Windows does stuff. The only time I see what I'm supposed to see is when all drivers are uninstalled and I connect the phone to my PC while it's going into fastboot mode. However, Windows will not properly see the phone in fastboot mode due to the driver not being applied.
I previously unlocked my bootloader, installed oxygen 11 (am on beta 4) . I want to install PA but I can't get fastboot on my machine. Shouldnt it be as simple as instilling adb and fastboot as well as the oneplus drivers? I've done everything I can think of and the majority of times ,I ended with an exclamation point in device manager and couldn't get the correct driver installed. I tried SDK etc.. more so... Android composite adb isn't showing in device manager. I might just use my laptop.
Any quick ideas on how to fix though? Thanks
There are lots of guides and links to the minimal adb/fastboot packages here on XDA. I will say it's a heck of a lot easier on Linux or even Mac, but typically the issue is that you want to have your device drivers installed first, then connect your phone (switch it between charging, file transfer, and MTP modes and let it install each of them fully to the device manager while it's plugged in), then install adb, enable debugging, plug in, run "adb devices" and trust the RSA fingerprint, and let it install that side of things to device manager as well.
I'd start by uninstalling all of the instances of the device in your system first to start over. You might even try plugging it in with no drivers installed first to see if it loads working generic drivers.
Man, I do not miss Windows.
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Make sure you have the latest Android Platform Tools installed...
https://developer.android.com/studio/releases/platform-tools
satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Try revoking all adb authorizations and then try to plug it in and run "adb devices" to regenerate an authorization maybe? Is the problem only with fastboot or is adb also broken? You are running fastboot commands in the bootloader instead of adb commands, right?
satva49721 said:
I've done all that, and now I tried my laptop and it's the same issue. Adb works fine, mtp works, just fastboot says "waiting for device" so frustrated.
I'd switch to linux if gaming was better... You think most games can run in linux? I am used to use it in the last before I started pc gaming and I really liked how capable it was. Creating bash scripts for simple tasks was great.. Windows really does suck. Getting fastboot working shouldn't be this much of a hassle and it never has been so I don't know what's wrong. I've uninstalled drivers multiple times now and still can't get anything. I'm Wondering if it's this latest release of Windows...
Click to expand...
Click to collapse
Any luck? I'm having the same issue. Just managed to get my phone unlocked from tmo, and for the life of me can't get windows to recognize my device in fastboot. After an uninstall of the device in device manager, and plugging it back in fastboot. It appears under other devices as simply android with a question mark icon top left, and a yellow triangle bottom right. Manually pointing to either the drivers from 15 sec minimal adb & fastboot google drivers, or selecting all devices>have disk>and pointing too the inf of the driver downloaded straight from google results in the yellow triangle going away, but the question mark still remains, and it's still listed under other>Android. So I suspect for some reason or another the drivers aren't installing properly. Usually (having to have to do this with other devices) has worked in the past. I've had win 10 mess up loads of things most notably my dl speed once. Some bug had it capped at like 24 kb/sec (shudders). Just for comparison what Windows version are you on?
Tried dl ubuntu to boot from usb and try that. Then I ran into issues dl the iso. Couldn't catch a break yesterday I guess. I'll try again after work today, and report back. Don't like the idea of having to boot linux just for fastboot. Might a vm, but I'm not sure that would work considering windows doesn't recognize the device to pass it through, but we shall see. I will say this just about over win10.
Also Idk if it matters, but I had Android studio installed before this as well. Might be time for a fresh install it's been a while.
Sent from my OnePlus8TMO using XDA Labs
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
tarek._.n said:
I am trying to unlock my bootloader (first time doing so) on my one plus 7 pro to get pixel experience 12 working. adb commands work well but once i'm in fastboot/recovery mode, my phone isn't recognized in the fastboot devices list, i assumed this was a driver issue since I have yet to find a working driver (my phone doesnt show up properly in the device manager) but the issue might come from some other source, here are the things i did and tried :
I am using a Windows 11 intel pc, plugged into both usb 2 and 3 ports since i have seen that people found different results with usb 2, i tried installing the drivers from android sdk platform tools from where I manually installed different drivers in the device manager since there wasn't a One plus specific driver(adb composite, android adb), none of which managed to be successfully installed. All of the instances of people finding drivers online either led me to expired links or a shady looking exe., i also tried using the all in one tool but installing drivers from there only returned "unable to install drivers", and unlocking the bootloader through it had the same result as when i tried manually, that is "waiting for device" after entering fastboot oem unlock.Any idea where i can find a driver for my phone?
Click to expand...
Click to collapse
Update : I used another pc, an amd laptop and used the tool all in one made by @mauronofrio and it worked perfectly, saving me from hours of trying things, so thank you for that!
I usually avoid this drama by disabling driver signature before installing OnePlus drivers on windows 11. Always works.