Develop Bugs

SOLVED Stick mount...?

Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
I am current and up to date with the sdk and drivers. I have fastboot installed. I know how to use it, please skip the referrals/how-to because that isn't the issue.
Spawn The Dark Ages

JediNinjafication said:
Ok long story short. I restored. Now no recovery. No super user. Fastboot doesn't see phone but does when in regular mode. Think somehow or another during the restore my internal was mounted/un mounted or however that goes because I'm seeing files/folders within my phone that aren't there and won't let me remove because "a device is missing from the network". A folder named windows and one named edited appear when I'm connected to computer but not when i disconnect. How do i m mount/unmount so phone is read correctly? Adb works fine.
Spawn The Dark Ages
Click to expand...
Click to collapse
As for fastboot, sounds like you need to get the proper driver. It's a different interface than adb. Try the naked driver efrant links to in his 101 FAQ post.
As for the other issue, I'm not sure I follow. Using a file manager on the device, you see files/folder that "aren't there" and via adb shell you don't see them? Please elaborate.

Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed. since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Spawn The Dark Ages

I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages

JediNinjafication said:
Ok. When i attach phone to computer, my devices lists mtp device (galaxy) under portable devices and Android debug interface under Samsung phones. the window that asks what would you like to do pops up and i choose view files. There were "windows" and "edited" folders that i don't know where they came from. If i click the windows, it will list some of the pics i have on my external drive. If i dismount my external..those folders will say device not attached to network. If i plug phone in without external at all..those folders do not show up in my phones sdcard.
Click to expand...
Click to collapse
What do you mean by external? The gnex doesn't have an external SD. Forget browsing the /sdcard with Window explorer at this moment, let's try more robust ways first. What do you see using a file manager on your device? What do you see using adb shell? (type ls -l)
When i open adb from sdk/platform tools that has the fastboot driver while phone is in this strange interface and adb reboot-bootloader my phone reboots but fastboot doesn't see it and both of the adb interface and mtp device disappear and are replaced with Android 1.0 with best driver installed.
Click to expand...
Click to collapse
Yes, the adb interface device and mtp device are gone because when you are booted in bootloader the phone uses another interface (fasboot). I'm sure it says best driver installed, but if 'fastboot devices' doesn't list your device I beg to differ that's true. Manually update the driver using the naked driver version 0.7: http://forum.xda-developers.com/showthread.php?t=1379875
since it said Android debug while on, i rebooted, did adb devices then for kicks fastboot devices and got the message fastboot does not work with production devices...meaning basically because the Android system is running. So, i.think something had been mounted/dismounted and that's why my drivers are installing backwards
Click to expand...
Click to collapse
Fastboot won't work if you're booted into Android OS. Again, it's an interface of the bootloader.

Oh..i just remembered..when i did have root, i had a program that would tell me system info and it listed internal memory and sdmemory. This was just before i restored.
Spawn The Dark Ages

My external harddrive for my computer. I know all this you just said hence i posted the thread
Spawn The Dark Ages

JediNinjafication said:
I saw a thread on gto (?) And stick mount and it seems that my phone is mounting as if i had those programs. Which i don't and never had.
Spawn The Dark Ages
Click to expand...
Click to collapse
Afaik, stick mount is an app that allows you to mount USB thumb drives with your gnex. If you don't have one of those attached and you never used this program, I doubt it's the cause or your problem.

This is not my first Android. each time i post everyone immediately refers me to a toolkit or how to on the sdk. Let's skip all that, assume I'm current and up to date and know how to use it. Now, read the post and continue from there. Not trying to be *****y, but this check drivers and fastboot banter will continue three pages.
Spawn The Dark Ages

And that's why I'm asking because that's how my phone is mounting.
Spawn The Dark Ages

I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.

Petrovski80 said:
I didn't refer to a toolkit or sdk. And from your post, I doubt you understand the difference between fastboot and adb, otherwise you would know trying 'fastboot devices' while Android is booted doesn't make any sense.
Either way, I don't respond well to commands when I'm just trying to help. Good luck solving this, but it will be without me.
Click to expand...
Click to collapse
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages

Nor was there any command issued. It was a request to skip the usual fastboot/adb and get down to the issue...saving each one if us typing and time.
The time spent explaining i am current and up to date with everything is horrible. Only reason i did the fastboot is because i have never seen it say Android debug interface while my phone is powered on...only when it's in fastboot. Nor have i ever had it sharing files with my external hard drive...like it were stick mounted.
Spawn The Dark Ages

Spawn The Dark Ages

JediNinjafication said:
If you read what i posted...you would see that i said "for kicks" i tried fadtboot and it didn't work obviously because Android was running.
Spawn The Dark Ages
Click to expand...
Click to collapse
You obviously think you understand what you are doing, but it us clear to everyone but you that you do not. I'm not trying to be mean here, but you are not listen to everyone who has tried to help you. I have tried in your other thread, petrovski80 tried in this one, and others in your other threads that you keep creating. One: you do not have the fastboot driver installed. Period. Two: to answer your question in your other thread, once you do install the fastboot driver, you can follow any one of the multiple guides on how to get root. Three: do not trust what you see in mtp on windows - it is not refreshed properly often. Four: no matter how many android devices you have had and have rooted and no matter how many drivers you have installed in the past, you still have not done the things you need for the GNex.
Sent from my Galaxy Nexus using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=30778314#post30778314

JediNinjafication said:
http://forum.xda-developers.com/showthread.php?p=30778314#post30778314
Click to expand...
Click to collapse
Funny, because no one suggested you use the driver that came with the SDK. If you look up to post #5, you would have seen that the driver that was linked to was the one that you should have used, and you would not have had to make any changes to any setup.inf files, and your issue would have been solved a while ago.

Funny because I had multiple different ones put in my dropboxthat didn't work either. Point being the drivers were there.
And I learned something new. Win/win

ADB Drivers

I don't see any other threads, so is it just me struggling to install working ADB drivers?
The zip file I found in another thread made out like it was installed, but apparently not...
Any tips?

Windows 7/8? The drivers that I posted in the dev thread should work.
If you're on Windows 8 though, you'll have to reboot in that insecure driver installation mode thing.
Sent from my HTCONE using Tapatalk

Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.

AndyCr15 said:
Win 7 64 bit. I think I'm using the right ones, don't quite understand why it can't be seen
It shows up in Device Manager in which ever of the 3 ones I try, but when I try 'adb devices' nothing shows.
Click to expand...
Click to collapse
You try "ADB Composite Device" or something along those lines? When you run that one it should be good.
When you download the zip, you should just extract the whole thing. Then after that I find the driver manually instead of having it search the folders. Are you selecting the android_winusb.inf for the driver?
I'm on the same OS for my main desktop and I do a lot of my work with the N1 on there using those drivers. Are you using normal command prompt in the platform-tools folder? I don't use anything other than command prompt for adb, so I'm not sure about those picking it up.
Sorry if that isn't any help, but I'm not sure what would stop it from picking it up after you use those drivers.

the other threads zip file works fine with my win 64. Are you going through a usb hub? That can mess it up
Sent from my N1 using XDA Premium 4 mobile app

No, no hub. Yep, doing all as I should. I'll try a different cable and different port though.

Linux
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.

mybrotherischad said:
ADB not working on Ubuntu 13.10. No issue with fastboot. When I do ADB devices, it doesn't return anything at all aside from "List of devices attached" with a blank space underneath.
Curiously, even after enabling USB debugging I am never given the RSA popup asking me to confirm access. I'm guessing the two are related but even after revoking previous confirmations via the Developer Menu, I still can't get it to pop up.
Click to expand...
Click to collapse
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.

ChodTheWacko said:
I recently got this going on Ubuntu 12 on VIrtualBox.
I have to start the adb server as root to get it working, i.e sudo adb start-server,
before I do 'adb devices'.
Also if you use VIrtualBox don't forget to add the usb filter for adb mode too.
Click to expand...
Click to collapse
Running natively. No luck doing it as root.

ADB can't see my Swift

Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B

Bump - anyone? Bueller? Bueller?
B

finnfather said:
Bump - anyone? Bueller? Bueller?
B
Click to expand...
Click to collapse
If you're trying to root then see the method I added to the end of the ROOT thread (can't post link, new account).
In short, you can get directly into the flashed recovery without it going back to normal and getting over written first without needing to use ADB to send it back to recovery mode.
Just take the back off, then once you have flashed the crackling recovery: pull the battery.
Plug it back in with the volume down held and power the device on, holding volume down.
You'll get into the recovery and can install superSU.
Hope that helps.

finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
I had the same problem on my Windows 10 that was upgraded from 8.1.
To fix it, I removed completely Android SDK and reinstalled it. For some reason this was the solution for me.
I tried the same things as you before that (except factory restore as it is a pain) and got the same results - no device listed.
As for Linux and OSX, the Swift got recognized without a problem.

finnfather said:
Hi all,
I bought a WileyFox Swift on grey thursday and have edited my adb_usb.ini to include 0x2970, but ADB doesn't see the phone. I have rebooted the PC, run adb kill-server and adb start-server, but all the time when I run adb devices it gives the line "List of devices attached" but nothing.
I've even tried using the USB cable it comes with rather than my normal one. The problem is I'd like to run Locale More, to switch between locales (have you ever tried using the GPS in English when you are in France? Painful on the ears ), but the batch file it comes with doesn't work because it can't find the Swift either.
And yes, I've turned on developer options, etc.
I think I'd like to root as well, but that might prove difficult if ADB can't see the thing in the first place...
B
Click to expand...
Click to collapse
Hi everyone,
@finnfather I think I have solved the issue. Today, I decided to manualy install (cm-12.1-YOG7DAS2FI) the latest cyanogen update as my phone didn't recive it as an OTA. I downloaded the zip package here and installed it through the atock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev

Hi
Windows 10, android sdk installed and google drivers.
Fastboot shows 8bce440 fastboot when fastboot devices is tried in cmd (admin priv) and "waiting for any devices"
ADB list devices is also empty.
Any help appreciated.

Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?

Pak0St said:
Have you installed the SDK after getting Windows 10 on the machine? For me removing and re-installing the SDK helped as it was placed there when I still had Windows 8.1 on my desktop PC. I know it is a pain but it helped me remove a lot of old stuff that just wasted space as well.
What do you get from Device Manager? It is also worth it to try different USB port.
Are you using COS or CM?
Click to expand...
Click to collapse
Hi Cheers for replying.
I have now tried it on Win 10 (clean install) win 8.1 (clean install) and windows 7 (clean install)
Reinstalled sdk on 8.1 and 10 twice but no joy. I cant see anything under device manager for it (in fastboot)
Under devices and printers it shows Android
Any help appreciated.
---------- Post added at 06:31 PM ---------- Previous post was at 06:25 PM ----------
adb_usb.ini could this help? I have tried creating a file manually. But no joy

In fastboot mode, it should come up as Marshall London Bootloader Interface under Device Manager. From Devices and Printers you can check what driver is currently installed when it's displaying "Android".
Windows 8/10 is very insistent on using verified drivers. You could try to uninstall the current driver and re-connect the device so that Windows can try to find the verified ones.
For me it automatically installed the fastboot drivers, although it wasn't fast enough and the Swift rebooted before the drivers were finished with installation.

Question Is anybody able to connect fastboot to the Pixel on chromeOS running crostini?

I have the latest version of both adb and fastboot. I'm able to connect with adb with the pixel and run commands but as soon as I have it in bootloader mode, fastboot doesn't see it. The chromeOS sees it because linux is asking for permisions. I tried about 3 or 4 different cables, different ports, rebooting linux and also the computer but just can't get it to work.
I'm able to connect adb and fastboot with other devices on chromeos running the linux container, don't know why fastboot isn't working with the Pixel 6. I tried on a windows PC and it worked like it supposed to

Can confirm same problem here. Really not sure what's wrong

Its really strange, I thought it should be easier on a chromeOS device, but then again, Crostini isn't full linux so maybe theres something missing that the Pixel 6 specifically needs

Papote3 said:
Its really strange, I thought it should be easier on a chromeOS device, but then again, Crostini isn't full linux so maybe theres something missing that the Pixel 6 specifically needs
Click to expand...
Click to collapse
Best report this in Pixel Support settings, so the developers responsible can take a look into this.

Papote3 said:
I have the latest version of both adb and fastboot. I'm able to connect with adb with the pixel and run commands but as soon as I have it in bootloader mode, fastboot doesn't see it. The chromeOS sees it because linux is asking for permisions. I tried about 3 or 4 different cables, different ports, rebooting linux and also the computer but just can't get it to work.
I'm able to connect adb and fastboot with other devices on chromeos running the linux container, don't know why fastboot isn't working with the Pixel 6. I tried on a windows PC and it worked like it supposed to
Click to expand...
Click to collapse
AFAIK, it has not worked with previous Pixels. I have my PixelBook set to do dual boot with GalliumOS because of this. I believe it also works when you boot GalliumOS from USB, but it has been a while since I have done it.

dcarvil said:
AFAIK, it has not worked with previous Pixels. I have my PixelBook set to do dual boot with GalliumOS because of this. I believe it also works when you boot GalliumOS from USB, but it has been a while since I have done it.
Click to expand...
Click to collapse
well that is even stranger that it works with other phones and not with Google's own devices.
I did tried it in the past with an OG Pixel XL and it did work.
It's a shame because my chromebook is basically my main computer and the one that I can easily carry around to do my basic daily stuff

Papote3 said:
well that is even stranger that it works with other phones and not with Google's own devices.
I did tried it in the past with an OG Pixel XL and it did work.
It's a shame because my chromebook is basically my main computer and the one that I can easily carry around to do my basic daily stuff
Click to expand...
Click to collapse
It didn't work with my Pixel 3 a couple of years ago. I have not tried it since, so perhaps it would work with the P3 now. It appeared to be a timing issue with the phone reboot, so it may work sometimes and not others.

Usb drivers?..

This stuff is a few years old, and I don't use ChromeOS, so forgive me if this doesn't apply or is out of date, but here are several relevant Google search results:
https://github.com/nathanchance/chromeos-adb-fastboot
https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
(linked to from the above article) https://forum.xda-developers.com/t/...and-fastboot-on-an-x86_64-chromebook.3806428/
Hope you find your solution. It would suck not to be able to use Fastboot from Google's own OS.

cultofluna said:
Usb drivers?..
Click to expand...
Click to collapse
Only needed for windows OS, on ChromeOS you'd be using adb/fastboot on a Linux environment
roirraW edor ehT said:
This stuff is a few years old, and I don't use ChromeOS, so forgive me if this doesn't apply or is out of date, but here are several relevant Google search results:
https://github.com/nathanchance/chromeos-adb-fastboot
https://www.xda-developers.com/adb-fastboot-chromebook-chrome-os/
(linked to from the above article) https://forum.xda-developers.com/t/...and-fastboot-on-an-x86_64-chromebook.3806428/
Hope you find your solution. It would suck not to be able to use Fastboot from Google's own OS.
Click to expand...
Click to collapse
Thanks for the help. Those are somewhat old but I think the issue is with pixel 6 (or older) devices
adb and fastboot work great on other phones on chromeOS running crostini and the pixel 6 is able to run adb/fastboot commands from windows and Mac OS. So the issue has to be the combination of the Pixel 6 and chromeOS.
I still can try and put my Chromebook in developer mode and run adb/fastboot in Crosh, so maybe I'll try that some day

Just an update, My Acer Chromebook (Developer) ADB and Fastboot commands worked fine on the latest SDK (I ditched MS years ago). I've been doing this since the great Developer nathanchance set it up in 2018!

Question adb/fastboot wont recognize my device.

Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com

i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...

simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.

Try on Windows

ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.

limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...

simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.

limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.

limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.

TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...

simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.

limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.

Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.

Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.

TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.

limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.

Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.

TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!

Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com

der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.