Develop Bugs

[Q] Can't get ADB to work, have tried everything

Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies

expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.

Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.

Have you added the environment variable for the sdk directory? It won't work if you don't.

Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try

I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.

vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.

bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.

If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App

It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.

Windows 8.1 Fastboot

I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?

kinglime said:
I'm on a fresh install of Windows 8.1
Here's what I did.
1. Installed HTC Sync Manager
2. Installed Minimal ADB and Fastboot
3. ADB works fine, boot into bootloader.
4. Windows shows Unknown USB Device (Device Failed Enumeration) in Device Manager
Running fastboot devices returns nothing
I can connect my phone to view files, I can ADB on my phone, the only thing I cannot do is fastboot. Why is this happening and how can I fix it?
Click to expand...
Click to collapse
I just experienced the exact same issue following the same steps on my laptop also running 8.1

Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app

gzbrambila said:
Fastboot doesn't work w 8.1. No workaround. You need another OS.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.

megaorange1 said:
Uh no. I have it working perfectly fine on my Surface Pro. It has both USB 3.0 and Windows 8.1. I'm not sure exactly how I got it to work but its possible.
Click to expand...
Click to collapse
From all of my research, you're the first person I've heard of having it working. Any specific drivers used? I'm very curious (currently, I have to use a backup machine to push TWRP updates to my VZW One)

Same thing here. 8.1 broke fastboot. Is this a Microsoft problem specifically because if it is I seriously doubt they will be in a hurry to patch it.
Sent from my HTC One using Tapatalk

I have found out something based on the VMware experience. Can somebody try it out and report back???
I feel that the fastboot problem in windows 8.1 is related to the USB port.
For those people that having problem, are you guys using USB 2.0??? If yes do you have USB 3.0 port in your computer??? The real problem maybe is that fastboot only works with USB 3.0 but not USB 2.0 in windows 8.1...

I tried both USB types, and half a dozen drivers and workarounds, and nothing.
I don't believe the dude above got it working. He is probably thinking Win 8, not 8.1. I have it working on 8.

Flash Image GUI will probably do everything you need to do in fastboot without the need for a computer. I just threw 8.1 on one of my extra PC's, I'll see if I can get the drivers going. I feel like this was answered in another thread though, I think it is in the rumrunner thread...

Just another reason why 8 is bad

cgskook said:
Just another reason why 8 is bad
Click to expand...
Click to collapse
fastboot was working on windows 8 and adb !!!
so the update win 8.1 have change sometihng but the question is what
and i try different drivers (from google,intelandroiddrv) and noting work
why have micro change something with drivers pffffff

kaverorzi said:
yep,definitely not working on Win8.1x64
Rooted a couple weeks ago on Win8x64, no issues.
Only noticed this issue today after I couldn't flash a different splash screen for my NuSenseOne.
Click to expand...
Click to collapse
I don't have the link on hand but there is a driver update to support 8.1 I have it working fine.
Sent from my HTC6500LVW using Tapatalk

i just used http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ and fastboot works on a 3.0 port on 8.1

I've just had this problem last week, and now got a solution...
Hi guys,
For anyone interested, due to something DreamerTKM said - I tried both USB 2 & USB 3 sockets on my Dell L701X laptop and both failed:
ERROR: Unknown USB Device (Device Failed Enumeration)
I did a clean install of Win 8.1 Pro and it still failed...
Anyway, I was using Windows 8.1 Pro default drivers for my system when this issue came up last week - default as in Microsoft's own out of the box drivers (drivers on the install DVD and Windows Updates) for my CPU chipset, USB chipset, etc... - my entire system (except for my nVidia graphic card!)
My laptop is now a few years old and my official "Dell" CPU chipset drivers are not compatible with Win 8.1, so I need to rely on Microsoft for these, but my USB 3 originally had Dell supplied "Renesas USB 3" drivers which I hadn't installed or even thought about installing as my USB 3 socket worked - and worked well...
...anyway, after installing the original Renesas USB 3 drivers the fastboot commands work once plugged into a USB 3 socket! USB 2 still wouldn't work though, but now my Win 8.1 laptop can do fastboot commands through a USB 3 socket.
I understand not everyone will have a Dell L701X laptop but the moral here is before blaming Microsoft and their Windows 8.1 O/S (which is truly awesome), try installing the correct drivers first!
DreamerTKM - thank you for putting me on the correct path with this!
Hopefully this post may help some of you!

solution
guyz if u r working on win8.1 just plug it in ur usb 3.0 then it will wrk...if u put in usb 2.0 it wont!

No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.

wex28 said:
No changes. I have read a few topics that it barely works with Win 8.1, so I will have to try it somewhere esle with Windows 7, then I'll be coming back to tell what's up.
Click to expand...
Click to collapse
Full fastboot and ADB support is available in windows 8.
Watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585

I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.

morrowa2 said:
I have been using fastboot and adb with no problems on Windows 8.1 since January. But the issue is much more than simply using a different USB port. Here is the tutorial I used. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/ Certain security features of 8.1 need to be bypassed to install the modified drivers. Also see this guide: http://forums.team-nocturnal.com/index.php/topic/1362-how-to-adb-fastboot-in-windows-xp-7-81/ I used this just for ADB, but it looks like he's updated his guide for fastboot as well. Hope this information helps.
Click to expand...
Click to collapse
Also, there is this: http://forum.xda-developers.com/showthread.php?t=2703585

[Q] Cannot Unlock Bootloader on Windows 8.1

Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.

killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.

I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.

ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?

ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8

xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.

Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app

It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.

I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.

OnePlus 3 fastboot driver issue

I had previously rooted my OP3, but accidentally updated it with the OTA open beta update, losing twrp recovery. I'm finding it incredibly difficult to flash twrp again to reroot.
The bootloader is still unlocked, and USB debugging is on with OEM unlocked, but I keep getting FAILED messages when I attempt to flash. "fastboot devices" shows the device (as a series of numbers).
I've tried using the OnePlus3&[email protected]_radaideh, but when attempting to flash it shows the below and then fails:
error: no devices/emulators found
I couldn't get it to work on my computer at home (win10) and read about problems with the OP3 drivers being unsigned (even with driver enforcement off). I'm also struggling on win7 - for some reason, the driver is listed in the Device Manager under the hardware group TP-LINK Android Phone and I can't get it to work using the OnePlus Android Bootloader Interface (under OnePlus, Inc.) or the Android Bootloader Interface (under Google, Inc.).
Could anyone suggest anything I should try?

Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.

emuandco said:
Win10, Update & Security, Recovery, extended Start, there disable driver signing and then do your thing. Don't reboot or signing is active again.
Click to expand...
Click to collapse
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above

justmast said:
Thanks for the reply! I tried that and couldn't get past the issues people complained about in a thread on Reddit about Kedacom drivers (can't link).
I'm at work on win7 which I believe should be easier, but still struggling with the problem as described in the post above
Click to expand...
Click to collapse
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.

emuandco said:
Did you use the drivers coming with the phone on a emulated CD drive? These worked very well for me in the past.
EDIT: Yes, Kedacom problem is nice. But changing the driver to the unsigned one manually worked for me in the past.
Click to expand...
Click to collapse
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though

justmast said:
Yes, I have tried those drivers (the OnePlus, Inc. ones). They worked for me when I rooted originally, I'm having trouble now though
Click to expand...
Click to collapse
Yep I was here aswell. Boot into driver signature mode and install the proper drivers. If you connect your device you can change the drivers. I don't have a PC next to me so I can't give you exact steps. The unbrick tool has the proper drivers, just follow the first few steps of that instruction to get it to show up as Qualcomm or something else as long as it isn't Kedacom.

Unable to use ADB with my Pixel XL

How do I enable using ADB with my Pixel XL? When I try to do ADB commands, they come back blank. ADB devices returns nothing for example. I read some stuff that seemed to indicate I didn't have the right drivers. I tried to download a new set of drivers from Google's website, but those don't work either. Windows 10 keeps insisting that the drivers installed are better.
Can someone point me in the right direction please?
Thanks!
Eric

Ewto16 said:
How do I enable using ADB with my Pixel XL? When I try to do ADB commands, they come back blank. ADB devices returns nothing for example. I read some stuff that seemed to indicate I didn't have the right drivers. I tried to download a new set of drivers from Google's website, but those don't work either. Windows 10 keeps insisting that the drivers installed are better.
Can someone point me in the right direction please?
Thanks!
Eric
Click to expand...
Click to collapse
SDK Platform-tools r29.0.5?
If you booted into fastboot mode/bootloader
ADB doesn't work, use fastboot devices

Homeboy76 said:
SDK Platform-tools r29.0.5?
If you booted into fastboot mode/bootloader
ADB doesn't work, use fastboot devices
Click to expand...
Click to collapse
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!

Ewto16 said:
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!
Click to expand...
Click to collapse
What are you trying to do with adb? Adb is used in either recovery mode or once the phone had booted into the system, provided you have enabled USB debugging. Is it this that you want to know more about?

Ewto16 said:
Those are the platform tools I have.
On my phone, I hold down power and volume down until the little android guy comes up. From there I hook it to my PC, via a USB cable. Next I go into the platform tools folder and start running commands from there. If I run ADB devices, nothing comes back. If I run, fastboot devices, I get my model number back.
Is that not correct? How would I run ADB commands then?
Thanks!
Click to expand...
Click to collapse
When you power off phone, press and hold the power and volume down buttons you should see Start.
You are booting the bootloader/fastboot mode.
Then you open a Command prompt in the Platform-tools folder and type: fastboot devices
It should return the phones serial number.
Take a look at one of these guides: Android 9 (Pie) Guide or Android 10 (Q) Guide.

NZedPred said:
What are you trying to do with adb? Adb is used in either recovery mode or once the phone had booted into the system, provided you have enabled USB debugging. Is it this that you want to know more about?
Click to expand...
Click to collapse
Hi, thanks for the response. I was trying to run and do the following series of commands.
Install Magisk module: Busybox for Android NDK
Install Magisk module: MagiskHide Props Config
Reboot
adb shell
settings put global tether_dun_required 0
su props
On the last command above you may need to authorize the shell via Magisk SU.
You'll now be in an interactive script, do the following:
Enter 5, Add/edit custom props
Enter n, New custom prop
Enter net.tethering.noprovisioning
Enter true
Enter 2, post-fs-data
Enter y
Enter y to reboot
I couldn't figure out how to get adb to work. (I don't know what the heck BusyBox does either for that matter.) It sounds like I may not have had my phone in the right mode to use adb. Based on the other post, I think I was in bootloader mode. (power down and volume down). It sounds like adb doesn't work in that mode, which I didn't understand. Does any of this make any sense?

Homeboy76 said:
When you power off phone, press and hold the power and volume down buttons you should see Start.
You are booting the bootloader/fastboot mode.
Then you open a Command prompt in the Platform-tools folder and type: fastboot devices
It should return the phones serial number.
Take a look at one of these guides: Android 9 (Pie) Guide or Android 10 (Q) Guide.
Click to expand...
Click to collapse
You are correct. Doing that does return my phone's serial number. However, adb doesn't appear to work for me in that mode. Are you saying that in bootloader/fastboot mode adb doesn't work?
Thanks for the link to those guides. They are REALLY good and well written for someone who is a bit of a noob like myself. I really appreciate them. I've used them to install Magisk on my Pixel XL when it was on Android 9 quite a few times. This time, I used it to install Magisk on my Pixel XL with Android 10, but ran into issues when I couldn't edit the build.prop file to enable tethering. The adb commands I was trying to run were supposed to help with the build.prop problem.

Ewto16 said:
You are correct. Doing that does return my phone's serial number. However, adb doesn't appear to work for me in that mode. Are you saying that in bootloader/fastboot mode adb doesn't work?
Thanks for the link to those guides. They are REALLY good and well written for someone who is a bit of a noob like myself. I really appreciate them. I've used them to install Magisk on my Pixel XL when it was on Android 9 quite a few times. This time, I used it to install Magisk on my Pixel XL with Android 10, but ran into issues when I couldn't edit the build.prop file to enable tethering. The adb commands I was trying to run were supposed to help with the build.prop problem.
Click to expand...
Click to collapse
Yes!

adb does not work in bootloader you spastic, boot into your system or twrp to use it

Homeboy76 said:
Yes!
Click to expand...
Click to collapse
Ah, I see. OK. Thanks for clearing that up for me. I'll have to hook my phone up and try adb again. I'll probably just wait until I need to upgrade again. I have everything working at the moment so I kinda don't want to mess with it.
Thanks for the help!

Ewto16 said:
Ah, I see. OK. Thanks for clearing that up for me. I'll have to hook my phone up and try adb again. I'll probably just wait until I need to upgrade again. I have everything working at the moment so I kinda don't want to mess with it.
Thanks for the help!
Click to expand...
Click to collapse
Also do yourself a HUGE favor and use dual boot on your computer and install Linux Ubuntu. Then adb and fastboot and anything you want as far as Android (and all types of other things) will work without issues. I am somewhat new to Linux Ubuntu but ever since the first installation I did I fell in love with it and haven't had an issue since. If you google search Linux Ubuntu you can find their site and read all about it and dual boot if you want or wipe windows and install Linux only. I grantee you'd love Linux OS. There are MANY to choose from too, not just Ubuntu but Ubuntu is bad ass IMO. I use 18.04 LTS and I love it. Check it out some time. Its 100% free too.
Linux site: https://ubuntu.com/download

flash713 said:
Also do yourself a HUGE favor and use dual boot on your computer and install Linux Ubuntu. Then adb and fastboot and anything you want as far as Android (and all types of other things) will work without issues. I am somewhat new to Linux Ubuntu but ever since the first installation I did I fell in love with it and haven't had an issue since. If you google search Linux Ubuntu you can find their site and read all about it and dual boot if you want or wipe windows and install Linux only. I grantee you'd love Linux OS. There are MANY to choose from too, not just Ubuntu but Ubuntu is bad ass IMO. I use 18.04 LTS and I love it. Check it out some time. Its 100% free too.
Linux site: https://ubuntu.com/download
Click to expand...
Click to collapse
ubuntu is trash.
also adb/fastboot work fine on any os i dont see why there is any difference. i use macos myself and its working just fine and it works on my windows install too.

sudoxd said:
ubuntu is trash.
also adb/fastboot work fine on any os i dont see why there is any difference. i use macos myself and its working just fine and it works on my windows install too.
Click to expand...
Click to collapse
I always had some driver issue on Windows seemed like. And everything was installed perfect. Since I left windows and switched I have NOT had any issue with anything far as my phone and PC go. I may check out Mint and or some other distros soon. I've only been onboard 6-8 months now so I'm noobin it still. ;p You should see my setup. LMAO! It's not the nicest looking laptop (a few keys missing on my keyboard...) [emoji23][emoji849] But hey, it does the job I need it to,, for now anyway. LOL! I would never return to windows unless I was using Photoshop. Sure there's Gimp but I always kinda liked Photoshop better.
Sent from my [device_name] using XDA-Developers Legacy app

flash713 said:
I always had some driver issue on Windows seemed like. And everything was installed perfect. Since I left windows and switched I have NOT had any issue with anything far as my phone and PC go. I may check out Mint and or some other distros soon. I've only been onboard 6-8 months now so I'm noobin it still. ;p You should see my setup. LMAO! It's not the nicest looking laptop (a few keys missing on my keyboard...) [emoji23][emoji849] But hey, it does the job I need it to,, for now anyway. LOL! I would never return to windows unless I was using Photoshop. Sure there's Gimp but I always kinda liked Photoshop better.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
how have you been using linux for 6-8 months and you still think ****-tier distros like ubuntu and mint are still acceptable