Related
Hi all, posting here because my other thread hasn't been seen.
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
Update: I have found that at the least I should be able to see my phone in the Other Devices list in the Device Manager but I've got nothing, just ADB Interface
Alright I see. I am assuming you are using stock COS. So when you enable developer options and enabled android debugging your computer did not want to pick it up. Unplug device and Try revoking USB Authoriztions in developer options. plug swift back in and look at the device. It should ask you for Authroization
Thanks Yasteellutch. Still not seen by adb devices. I think I'll just clear the phone back to factory and try again...
B
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 stock recovery. And now, adb works! Also, this has fixed a few problems with themes. Now I can use helium! I hope this helps,
Jev
I cound manage the get a workung adb connection, buy switching adb debugging off and on again on the device while the device was connected to the pc via USB. Then I opened the device manager in windows and klicked on update driver vor the unrecogniced device. After that the device prompted a dialog, I had to accept the connection. Now the device was visible in the adb device list. (@jevtheboss: So you do not have to reinstall the cm to make it work)
Hey fellow members,
Since a few days my ADB is not working with my phone. Every time I try to connect it as an ADB device I get an error (See attachment) that my device is unauthorized.
I've read a dozen threads about this problem and I think it is the RSA Fingerprint. I don't get that pop-up anymore, when connecting my device to authorize the PC.
Here's what I've tried already
1.
Code:
adb kill-server
Code:
adb start-server
2. disable and enable USB-Debugging-Mode
3. Copy the adb key from C://user/me/.android. to the phone's directory /data/misc/adb
4. reinstall drivers on PC
5. Reboot PC and Phone
None of that worked. None. I'm desperate. Been looking for 6 hours yesterday and couldn't fix it.
If anybody has had these kinda problems I would be totally grateful for an answer.
I have the intl version of H815, bootloader unlocked, TWRP and SuperUser working fine. I'm currently on V20C (6.0 Marshmallow)
Any help would be extremely nice.
Best regards
Hi,
Did you solves this as I am having the same problem after doing a factory reset?
Cheers
Follow_and_Feel said:
Hey fellow members,
Since a few days my ADB is not working with my phone. Every time I try to connect it as an ADB device I get an error (See attachment) that my device is unauthorized.
I've read a dozen threads about this problem and I think it is the RSA Fingerprint. I don't get that pop-up anymore, when connecting my device to authorize the PC.
Here's what I've tried already
1.
Code:
adb kill-server
Code:
adb start-server
2. disable and enable USB-Debugging-Mode
3. Copy the adb key from C://user/me/.android. to the phone's directory /data/misc/adb
4. reinstall drivers on PC
5. Reboot PC and Phone
None of that worked. None. I'm desperate. Been looking for 6 hours yesterday and couldn't fix it.
If anybody has had these kinda problems I would be totally grateful for an answer.
I have the intl version of H815, bootloader unlocked, TWRP and SuperUser working fine. I'm currently on V20C (6.0 Marshmallow)
Any help would be extremely nice.
Best regards
Click to expand...
Click to collapse
pinn___________ said:
Hi,
Did you solves this as I am having the same problem after doing a factory reset?
Cheers
Click to expand...
Click to collapse
Unfortunately no. I've really tried everything. I even flashed a complete new kdz (at least upgraded to one), to no avail.
And this thread doesn't get enough recognition or any advice from a pro, so I'm heading dead ends.
I'll let you know, when I found a possible solution and post it in this thread.
Cheers
Hi,not a solution as such but I wanted adb to get into the bootloader. Instead I installed a terminal emu and got into it that way. Not sure what you are trying to achieve but this may be of some help.
Same problem for me... Device unauthorized, no rsa prompt... Tried it factory fresh, no success.
pinn___________ said:
Hi,not a solution as such but I wanted adb to get into the bootloader. Instead I installed a terminal emu and got into it that way. Not sure what you are trying to achieve but this may be of some help.
Click to expand...
Click to collapse
I want to access my device via ADB, e.g. pushing files to my phone, installing, wiping, etc.
Which I can't, since my computer, or my device is unauthorized to do so.
I just can't enter ADB commands, which is pretty annoying, since I often use it to push files to my phone or print out a logcat.
Well nothing's working so I gotta be patient until anybody comes up with a solution :good:
The strange thing is, i do also own an oneplus 2. It doesn't get authorized too, but is asking for fingerprint. Do you have win10, like me?
Trinaaa said:
The strange thing is, i do also own an oneplus 2. It doesn't get authorized too, but is asking for fingerprint. Do you have win10, like me?
Click to expand...
Click to collapse
Yes I have win 10. You're one step further than me. I don't even get an RSA prompt. Don't know why yet
Follow_and_Feel said:
Yes I have win 10. You're one step further than me. I don't even get an RSA prompt. Don't know why yet
Click to expand...
Click to collapse
Refer the below thread, hope this helps
http://stackoverflow.com/questions/23081263/adb-android-device-unauthorized/25546300#25546300
EXPERT FROM THE ABOVE LINK:-
I was not getting the RSA fingerprint pop up on my phone.
I had to go into the C:\Users\.android\adbkey and adbkey.pub
files, delete those and then do kill and restart of adb server. I had to stop and restart the debugger and connecting as USB in PTP mode.
Because the RSA authorisation key was getting stored in this path, killing and restarting the adb server didn't help.
Just wanted to reiterate the person above me as it helped me with my problem. So in case anyone out there on the internets runs into the same issues try these instructions.
1. boot your phone into recovery
2. now try doing adb devices in your command prompt - it should show up as LGH815xxxxxx recovery
3. type adb shell
4. type cd /data/misc/adb
5. type rm adb_keys -- this will delete any existing adb key from your device **
6. type exit to leave the shell and then reboot your device as normal
7. in windows find C:\Users\<your username>\.android
8. delete the existing adbkey.pub file
now you can proceed as normal with running adb devices, and you phone will prompt you to confirm.
** note you can also delete the adb key from android from within your android OS. go to settings > developer options > revoke USB debugging authorizations. i guess you can do it from recovery just to make sure.
TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?
Desert.pro.riders said:
TLDR: p2xl won't adb or fastboot on my mac
Lets see if you guys can help, or if my phone is stuck here.
I updated to December 2017 update
Used adb to root with magisk and twrp 3.1.1 beta 2 I believe
I noticed twrp wouldn't work when I would boot into it using the hardware buttons
Did some research and discovered that if you flash a custom kernel it would solve that issue.
When I went to push twrp img to my phone & I noticed my phone's adb stopped connecting to my Mac. I wouldn't get any response from the Mac. It was if I had just plugged my phone into a wall USB to charge. I tried the usb configurations, toggling USB debugging, toggling developer mode, restarting both devices & nothing (I tried on my 2 macs & tried 2 different cables & a micro USB to USB c adapter.)
I let about 4 months pass by and yesterday I decided I would try to fix this issue again.
I selected factory reset & when the phone rebooted into twrp to reset, it asked for a password and twrp started working again. I did a normal reboot & thought the issue was fixed. I booted into twrp again and did the factory reset & flashed flash kernel and twrp was working again.
I decided I would update the phone to the newest update. So I turned on USB debugging and plugged in my phone to my Mac to adb the newest update & still nothing.
So I decided to try to take the ota but it didn't work because of the custom kernel I flashed.
I read somewhere on here that you can flash the boot.img of your current version thru twrp. It would put me back at the stock recovery & kernel. I extracted the boot.img from the zip and flashed it with twrp. And it said it flashed fine. I booted up and checked the kernel and it's was still on the flash kernel. Went back to recovery and now I get the broken Android with the red triangle & I can't get into stock recovery from there by pressing the volume up + power or any other combo.
So now I'm here with a phone that won't adb or fastboot. Doesn't have a working recovery. & Can't take an ota.
Thanks for reading ^_^
What do you think I should do next?
Click to expand...
Click to collapse
The first thing I would do is take a drink!! Wow! Seems you have quite the mess on your hands. Seriously though, you really can't do much until you get fastboot working. Question, when you unlocked the bootloader, did you run BOTH unlocking commands??? Also, is OEM unlocking and USB debugging still enabled from the developer options menu??
Do you have the latest SDK/platform-tools on your pc? Have you tried different USB cables and ports??
Here's a recovery thread you may want to look at to help you along and get you back up and running :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot
View attachment 4492382
Desert.pro.riders said:
I believe I only used the unlock critical, but I unlocked the bootloader before I did the December update. Not sure that has anything to do with it?
Oem unlocking is enabled, but it is greyed out in the on position. I'll attach picture. And USB debugging is enabled as well
I updated to the latest platform tools yesterday, I tried on my two macs & swapped ports and tried my two different cables that I had on hand, maybe today I'll see if I can get anything with my buddy's pc. Windows 7 I believe.
And okay I'll look getting the recovery going again
Thanks a lot ?
Click to expand...
Click to collapse
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
Yes! At least the phone os on the phone works fine
Yeah you're right about the macs. They are pretty cool because it works with removable devices without having to mess with drivers. But it sucks when something goes bad because there are really any device managers or drivers to mess with.
Blessing/curse.
I'm usually a pc dude too, but my ex took my PC ?
Well once I get home from school I'll get to trying to fix this once again
Badger50 said:
Well at least you can still get into your OS apparently, which is good. I'm not a Mac guy, so I can't help much in that regard, just seems a bit more quirky when using fastboot. Be interested to know how it goes on the Windows 7 machine. That's what I use without issues at all :good:
Click to expand...
Click to collapse
So the windows PC does detect that something gets plugged in But this the only thing that happens
This sucks
Edit:
I was able to get into stock recovery now. But I don't think you can do much from there.
Adb & fastboot continue to be unresponsive
..
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
I never had problems connecting my Pixel to mac, even to other hackintosh...
I have Android File transfer installed and no SDK platform tools.
Usually I just download the package from Google and place it somewhere. Than opening Terminal, going into that folder, which btw contains adb and fastboot...
For example: when typing the " ./ adb devices" for the first time, the message about not running / starting Daemon service pops up. This is normal.
I presume that you are using the "./" before every command in Terminal.... This is obligatory on Mac.
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here
,,
Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
The way I do it is
1. Open terminal
2.write "cd "
3. Drag the platform tools folder from the desktop to the terminal window
4. Check adb devices , "./adb devices"
I will try to reinstall adb again your way, as I am out of options so anything helps, thanks
Desert.pro.riders said:
Yes so I've gotten adb, fastboot, and the Android file transfer working before on both of my Macs, so I know they are set up right. The problem was when I updated my pixel to the December version via adb. Adb stopped completely working.
I can have my phone booted up and in usb debugging mode and run the "./adb devices" and it'll show the list of devices empty.
Same thing if I put the phone in fastboot and try running "./fastboot devices" it hangs for about a second then it shows up with an empty device list.
I was able to wipe the phone clean with the stock recovery & got my stock kernel back I think.( I'll attach a picture) but I'm still not able to ota to the April patch, I'm thinking because I used twrp right?
Either way I still cant get fastboot & adb working, I've tried my two Macs one in high Sierra & the other on El capitan. And a Windows 10 pc and a combination of about 6 different us cables.
Has anyone ever seen this happen? I think I might have hit a wall here
Click to expand...
Click to collapse
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
Ericarthurc said:
Well couple things about Mac, you don't need any usb drivers for it. To view the file contents of the /sdcard you need Android File Transfer --> https://www.android.com/filetransfer/ plug in your phone then make sure you change it to MTP on the phone. As for adb and fastboot in terminal, download the latest platform tools for mac --> https://developer.android.com/studio/releases/platform-tools You will get a folder called "platform-tools" put that folder some where you like on your mac. I put mine at /Users/"my username"/platform-tools So to get it working correctly you need to open terminal and run "cd ~/" [no quotes on these commands btw] then run "sudo nano ~/.bash_profile" when nano opens it should be blank, type on the first line export PATH="$PATH:your/path/to/platform-tools" [with the quotes on that one]. In my case mine is export PATH="$PATH:~/platform-tools" or export PATH="$PATH:Users/ericarthurc/platform-tools"
Just make sure you get the right file path and that its writing correctly; then type ctrl + x and then y for yes to save. Then in terminal type source ~/.bash_profile
Quite terminal and relaunch, run the command "adb version" you should now see the correct file path and no errors; run adb device now and it will start the adb server
Click to expand...
Click to collapse
Badger50 said:
Just outa curiosity, since it appears your stock everything again, do you get any response from Google when you go into....settings/system/system update??
Click to expand...
Click to collapse
This, stops before it goes into step 2
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Still nothing I tried this a few times & did the path install too
IDK what else there is trouble try I'm pretty much open to anything
Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
Desert.pro.riders said:
Do you guys think I can do anything thru stock recovery?
I tried adb sideload with no success and I tried the apply update thru sd card and I gave me a error unable to mount message?
Click to expand...
Click to collapse
You can adb side load from stock recovery as well.
uicnren said:
disconnect your phone from the mac.
reboot the mac
open developer options on the pixel
disable USB debugging
tap on 'revoke USB debugging authorizations'
enable USB debugging
reboot your phone
plug your phone into the mac again
If all goes well, you will need to authorize it on the phone, and adb/fastboot should work correctly
if you wish to easily install adb/fastboot into your PATH, see here.
That will properly install it, as well as the latest version(s) of each.
Click to expand...
Click to collapse
Badger50 said:
You can adb side load from stock recovery as well.
Click to expand...
Click to collapse
If I'm on adb sideload mode & I type adb devices into the terminal, should the serial number show up in the terminal? Because it's not. I'll try messing with it a lil more once I get home from work
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
Phone is detected by "adb devices" but not detected by "fastboot devices"
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
ruhrohs said:
I purchased a used P3a XL from Swappa. I would like to install a custom ROM. As we all know, in order for me to do that I need to unlock the bootloader. I think the phone is a Google Edition (checked SKU on box against what is sold in stores).
I have done quite a bit of research before posting here and think I have the process correct. I have enabled developer mode and toggled the OEM unlock option. I am able to "adb devices" and see the phone on my computer terminal. I "adb reboot bootloader" and the phone reboots in to "Fastboot Mode". When I do "fastboot devices" nothing shows. When I boot in to fastbootd (via stock recovery) and execute "fastboot devices" I can see the phone. I execute "fastboot flashing unlock" and it fails with "fastboot flashing unlock failed remote: unrecognized command flashing unlock".
I have tried this on my PixelBook with Linux installed and on my Ubuntu lab machine. Both of those machines give me the same results. I tried with my Windows 10 laptop, but the phone isn't detected by any of my USB-C to USB-A cables.
I have factory wiped the phone a few times and attempted the steps above, but it results in the same thing. Phone is not detected in fastboot. Interestingly, I am able to sideload the latest OTA (QQ3A.200605.001, Jun 2020) without any errors. After sideloading the latest OTA, I am still unable to unlock the bootloader.
I suspect one of two things:
1. The phone is a VZW/Sprint/T-Mo edition. Even so, VZW edition can be unlocked. I tried that method (found an XDA thread to do that).
2. Something is wonky with the phone (bootloader software)
Unfortunately, since I bought it second hand, I do not think Google would honor the hardware warranty to issue me an RMA.
What do you folks think may be an issue?
Click to expand...
Click to collapse
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Tulsadiver said:
Sideloading is an adb function, not fastboot. Make sure you have the lastest Android platform tools. This doesn't mean you can unlock the bootloader but to get fastboot working.
Click to expand...
Click to collapse
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
41rw4lk said:
Also make sure you have the oem cable or at least a decent cable, and use a 2.0 port if possible. I've seen other a/b devices refuse to work or give half commands with 3.0+ ports. What does it says underneath oem unlocking in dev settings? I've attached the latest adb/fastboot files just in case you might need them.
Click to expand...
Click to collapse
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
ruhrohs said:
I just updated my Ubuntu machine with the lastest SDK, so both ADB and Fastboot were updated. The phone can be seen with "adb devices". It can be seen with "fastboot devices", but only if the phone is in fastbootd mode. Wouldn't this confirm that fastboot works on the laptop?
I am using a PixelBook with the original USB-C to USB-C cable that came with the phone. My Windows laptop doesn't see the phone at all
OEM unlock option is enabled.
Click to expand...
Click to collapse
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Tulsadiver said:
As far as your window laptop, you might try installing usb drivers.
https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
Yup, tried that as well. I even went as far as wiping one of my lab machines, installed Windows 7, copied and installed the command line tools only from here: https://developer.android.com/studio#downloads, but no dice. For Windows, I think it's a cable issue. I'm getting new USB-C to USB-A cables delivered tomorrow. Once I get them, I will try on my Windows laptop.
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
ruhrohs said:
Update to my issue...
Bought a 3 pack of Anker cables. Plugged each of them to my phone and to each of my Win 7 and Win 10 laptops. Both laptops are able to charge the phone, however the don't detect the phone for data transfer/USB debugging. I checked device manager, deleted/uninstalled all Android devices that were listed (including my first generation Pixel XL), rebooted my laptops and tried again. No dice... At this point, I'm chalking it up to the Pixel 3a XL phone itself and an issue with the hardware.
Note to self... Buy a brand new phone for an extra $100 and I would have saved myself over 4 days of troubleshooting an issue.
Click to expand...
Click to collapse
You do realise that you've got to change the USB settings for it to do data transfer right???
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
No worries dude even when you change default usb settings it still stays in charging mode
thatsupnow said:
You do realise that you've got to change the USB settings for it to do data transfer right???
Click to expand...
Click to collapse
Yup, I know that I need to change it to data transfer, however the phone isn't detected by either of my Windows laptops. The phone is only detected via ADB on my Chromebook. I can do an "adb reboot bootloader" and it'll accept the command, but "fastboot devices" or "lsusb" shows no devices.
kevinchristopherson said:
my problem more than once, ashamed to say. after updating drivers and cords. then forgot to pull my notifications down for that last little line. it's a learning process though. (so they say).
Click to expand...
Click to collapse
Yup, my first gen Pixel XL will notify me when I pull down the notifications, but the Pixel 3a doesn't.
I ended up setting up the phone and used it for a fewdays. It works fine, however I'm used to running AdAway, AFWall, EX Kernel Manager, Greenify, High Brightness Mode, NapTime, Titanium Backup and Viper4Android. There are workarounds to enable Greenify and NapTime via ADB, but it's a moot point without the other root dependent apps.
Updating this thread to close this out.
Bought a brand new Pixel 3a XL from the Google store. I was able to root without any issues on my Windows 10 laptop. I attempted the same exact process with the same USB port and USB cable for the Pixel 3a XL that I bought from Swappa, but it didn't work. This confirms my educated guess that it's a hardware issue on the phone.
The secondary market may soon be flooded with Pixel 3a XLs once the Pixel 4a is released. Before you get burned on a non-rootable phone, ask the seller how long they have owned the device and check the warranty on it. As of this post, you can check the IMEI Here: hxxps://store.google.com/repair (replace the hxxps with https).
Good luck!
You need to download the google usb driver and update the Pixel 3 driver in Device manager with the usb driver. Then the computer will recognize the phone as a fastboot device while it's in bootloader.
For me what solved this was I wasn't adding the "platform-tools" folder to my path.
I was using "fastboot.exe flashing unlock"
But once I added to path and did "fastboot flashing unlock" it worked like a charm
On Linux, did you try sudo fastboot flashing unlock? This is the only thing that works for me. Sudo before all fastboot commands.
In my case on Ubuntu 20.04, it was a USB 3.0 port problem. It was detect device with fastboot devices but other commands does not has a response. My laptop hasn't got a USB 2.0 port. Then I disabled internal USB 3.0 support in my BIOS and now fastboot is working normally. But all USB 3.0 support is stopped. It seems USB 2.0 hub is the better option. I will set back the BIOS setting later.
Yesterday i bought the G020B version, and the same happened to me while unlocking bootloader, fastboot keeps on <waiting for device> like if the phone was not even connected
I searched for a driver that could work and found this (For windows)
Basically, my system can't detect properly the phone because the driver was not 'updated'. (Even when i can use fastboot on other devices)
Hope it works for you or everyone here.