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
Related
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk
ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.
LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >
Im having some trouble with ADB / Fastboot commands. No matter if i try "fastboot devices" or "adb devices" they both show nothing / no device. I've tried the commands to the TWRP recovery, a booted os and the bootloader in fastboot mode. Nothing seems to be working. Im using the well known adb/fastboot 15 sec installer from here. I've tried two win10 computers and now a win7 computer although all 64 bit, which have not been a problem before.
In the bootloader on the phone with the cable plugged in, the red fastboot text doesn't show "FASTBOOT USB" unless i move the cursor (like it doesnt update before i move the cursor). Im running the command prompts with administrative rights. I've also tried different cables, but im beginning to think that its the phones micro usb connector that is faulty, although MPT is working fine in windows, and transfers files without problems. Its a HTC One S im trying to do this on. All i want is to update my recovery!
Is there something very obvious im missing?
I found a solution however a wierd one. I already had debugging enabled on the phone, but thought that i should try and disable it, and then re-enable it right after. This seemed to trigger something, as my computer now started to install some drivers, that it had been missing before. After this fastboot commands and adb commands ran without any trouble.
Da9L said:
I found a solution however a wierd one. I already had debugging enabled on the phone, but thought that i should try and disable it, and then re-enable it right after. This seemed to trigger something, as my computer now started to install some drivers, that it had been missing before. After this fastboot commands and adb commands ran without any trouble.
Click to expand...
Click to collapse
I just tried that and it absolutely worked for me too. Thanks. Very bright person you are.
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
triteshy said:
I feel like I have tried absolutely everything but my computer will not recognize my phone when I type fastboot devices, while in fastboot. When the phone is on though, adb devices shows the device.
I'm curious if anyone else has run into this issue and if so, how did you fix it?
Click to expand...
Click to collapse
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
niteStalker09 said:
Hey pal, I'm no expert but I'd say try download adb driver for your OS version whether it's Windows or Linux. and maybe phone driver as well. Worked for me
Click to expand...
Click to collapse
Thank you for the response. Did both of those things already.
triteshy said:
Thank you for the response. Did both of those things already.
Click to expand...
Click to collapse
Just making sure but you do have the latest platform-tools?
I've never actually experienced it not being detected in fastboot before so that's really the only solution I can think of.
So just for some one in the future trying to figure out what happened. I managed to get it fixed.
The problem I was running into was that my computer recognized the driver (the regular oneplus driver that you can install when you plug in your phone) only when my phone was using adb (or in other words, my phone was on, in a usable state, in the regular OS, not fastboot or anything).
However when I launched into fastboot, my computer would no longer recognize my phone as the same device.
To fix:
I had to open file explorer on my pc (running windows), then right click "my pc", then manage devices.
There was my phone, right there, but under "unknown device". I right clicked it, and installed a driver for it, however I didn't use the oneplus driver, I used the Samsung phone drivers. It then worked perfectly.
I know that's not good directions but it still may help someone in the future and save them from a horrible headache that I experienced, at least pointing them in the right direction.
GLHF.
I had this happen to me as well. Was driving me nuts. I had to use a different cable. The wrong cable solution usually never works, but for some reason, my older USB-C anker cable would work in ADB but not fastboot. Newer Anker cable worked. I'm sure the OEM cable would work too.
Hello everybody, I was trying to update my Magisk and that process failed. I thought nothing of it put it off. Tried to restart my phone a few days later and now it's stuck in a fastboot loop. Cannot even go into recovery. So I'm like okay, probably need to reinstall recovery and flash a clean rom again. Try the "fastboot boot recovery.img" command and it's giving me a "waiting for any device". Googling says it's a driver error, but that's strange because I have used my phone on this computer before with ADB and fastboot. Fastboot and ADB commands work fine on my Oneplus 3T.
A week ago I also had the problems after the Magisk update. But connecting to the PC worked normally for me. Once you've installed the drivers, there shouldn't be any problems. You could use a different cable.
Incidentally, Magisk only messed up the boot image. It is sufficient if you flash your boot.img, then the twrp.zip, reboot into recovery, then the magisk.zip.
That was completely enough for me. Cell phone works normally again, without data loss.
Good luck!
Yeah that's exactly what I am trying to do, I can't even flash the boot.img to get into recovery, my computer won't recognize the device for some reason now. Do you know where I can find the drivers? I could only find shady 3rd party sites. Thanks!
Tried installing drivers from here, no change.
Download Latest OnePlus USB Drivers for Windows and Mac
Download The Latest OnePlus USB Drivers For All OnePlus Android Smartphones. We Have Included USB drivers for Both Windows And Apple MAC OS Users. Download Links Given Below.
www.getdroidtips.com
This is installed and works with me
ghost323 said:
This is installed and works with me
Click to expand...
Click to collapse
No joy, looks like that's the same file as the one I downloaded. Thanks for your help anyways.
Now I can't even turn my phone off lol. It woke itself up this morning magically and now whenever I hit power off in fastboot it just boots up again into fastboot. Might have to send it in...the horror
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
ghost323 said:
Your phone is crying out for help. It doesn't like to die.
I think you will have tried everything possible. Have you already connected it to another computer with the right drivers? Tried other cables?
Click to expand...
Click to collapse
Haha yeah, it's like your kid who refuses to go to bed and is throwing a tantrum. Yeah two different computers that are known to have worked with this phone in the past (how I unlocked the bootloader in the first place). Different ports, different cables. It seems like I'm having the same issue that a lot of other people are having with the last Magisk update, except they're able to flash the recovery image in fastboot to get back running.
This is a ****ty situation! That was really a nasty magisk update. I wonder why its consequences are so different, even though it is the same cell phone.
fastboot cannot recognize device but adb can
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both. Oneplus 7 pro is running 10.3.0GM21AA >fastboot devices >adb devices List of devices attached 966c8016...
forum.xda-developers.com
Look at this. Maybe it will help you so that your computer recognizes the cell phone again.
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