Hello xda'ers
I have the Xiaomi Redmi Note 8, however I want to use the scrcpy github . com / Genymobile / scrcpy utility it says it cannot detect the phone.
ADB Setup and its drivers have been correctly installed.
USB debugging has been enabled in the phone.
But the ADB cannot detect the phone.
It still is not working, so I went into the phone, developer options and go to USB Debugging, Security settings, and toggle that on, but it asks for a Mi Account?, which I do not have.
Please help.
Might as well sign up for that Mi account, because you need the (security settings) toggle turned on if you want to control the device via scrcpy. What does it tell you when you enter the command adb devices ? Did you get the popup asking for confirmation on whether you want to allow the PC to access debugging when you connected the phone via USB? Also make sure MTP/PTP/whatever else isn't turned on.
It's odd, executing adb devices gave an unauthorized message on the computer console, but the security confirmation never appeared on the phone up until some hours ago. I authorized the connection and voila I can now see the phone's screen on desktop PC via scrcpy, however.....
The screen just freezes, I mean, I cannot interact with it on the computer. If I unblock the phone manually and interact with it, the screen refreshes properly on the desktop, alas this is an issue with scrcpy not with the phone or ADB. Maybe I should file a bug or search their site?
Again, you have to enable the (security settings) toggle in your developer options if you want to control your device from the computer. This is mentioned on the Readme on scrcpy GitHub already.
Found solution:
1. Enable USB debugging
2. Run any terminal as root
3. setprop persist.security.adbinput 1
. That's all, nothing else is required
Related
Has anyone gotten their computer find their G4 through cmd (adb devices). I cant get the adb message on my phone to allow access to my computer. I turned on and off usb debugging several times but i still don't see the message on my phone to allow access. I let me computer download the drivers when plugging up my G4 as well as allowing the install of PC drivers.
yes, working great for me. Do u have updated and right drivers? u find tread here with right drivers..
Sent from my unlocked and rooted LG-H815
I was having the same problem..
You need to install the LG Drivers and then your phone will connect via adb..you will be asked on your phone to allow the port connection after installing the proper LG drivers. Verify and you will be good to go..
I used these ones below in the attatchment or you can grab them from.....
http://www.theandroidsoul.com/download-lg-g4-driver-for-windows-and-mac-mtp-adb-download-mode-77723/
I think I found the issue. I had Note 3, 4, Nexus 6, S6 edge, and G4 all still on my computer in the device manager. I uninstalled all of them plus I uninstalled the adb driver in device manager. Plugged my G4 back in and ran the PC driver update via G4 and it worked. I can now see my G4. Don't know if I had to do all that to get it working but hey it worked for me.
I was having issues with this myself and didn't find a solution. I found out that I was having better luck switching it to Camera PTP from the notification dropdown. Sometimes I have to toggle to MTP back to PTP, The dev notifcation should appear when it is actually connected.
1. PTP
(1a. switch to MTP back to PTP if it doesn't work)
2. 'adb kill-server'
3. 'adb devices'
-If you see your device, you can try to 'adb connect **IP**' but it will most likely say it was unable to connect
4. give it your adb commands you want
It's the only way I've been able to get adb, hope this helps!
I was having this issue also. After install win10 then adb connection to my LG G4 (h818) was not detected. Back to android.com, it said that if general USB driver doesn't work then we must find OEM driver to the producer web. LG ADB Driver was about 17MB. After installed the driver then it was immediately detected. Thank God, finally.
I have silly problem. I bought used G4 LG from someone found in online forum. Checked all series on phone (sticker), on software "about phone" all showing LG H815 software version H81510H, but by adb ( linux machine ) showed H812xxxxxx .... set on developer option debugging the command "adb reboot bootloader" just send device into android boot ( device boot ). I wish to unlock the bootloader and put CM. Hard button option > pushing vol up + power button simultaneously did nothing, vol up + power button then > connect to PC via usb, did nothing ( just send phone to device boot ) ..... I have no windows machine
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
FinnSanity7 said:
Hello, my Oneplus 3 finally met its maker when it slid off my knee as I was doing a poo. This phone had served me well for a long time and was used for the last year without a functioning power button.
Today I was trying to extract my data from the phone using adb. However, I have a few issues.
The screen is fully black and shattered and digitizer appears to also be broken.
I can use the fingerprint sensor, but not much else. If I try to apply pressure to the screen, the device disconnects from the computer then reconnects.
My phone will not show in 'My PC' and just shows as 'android' under 'USB devices' in Device Manager, I try to update the driver through this and I am just assigning it to be an 'ADB device' or 'Oneplus Android ADB Interface' which does not help.
I have downloaded the Oneplus USB drivers and installed them which did not help or allow me to select those as driver updates in 'device manager'. Even after turning off signed driver checks in boot options.
I believe I have USB debugging on, as I turned it on not long ago due to the power button failing. But when I attempt to use ADB I either get 'unauthorised' or 'offline' beside my devices serial number.
I have tried unlocking my device with my fingerprint and it has the response vibration but does not allow me to access it.
Ideally I would like it to work with '[email protected]' and 'android control' but I would settle for just being able to pull everything off the device. I have been reading threads and trying fixes all day to no avail. Please help me.
Desktop Info that may have an effect
Windows 10 version 1803
USB 3.0 ports
Related programs installed
ADB Minimal and Fastboot
Android Studio (not sure how to use)
[email protected]
Android Control
Thankyou
Click to expand...
Click to collapse
If you had used adb before and the phone was recognised earlier, then there shouldn't be an issue. If not, then when issuing adb commands, there will be a popup on the phone asking you to enable authorisation and to make it permanent. In your current scenario, you will not be able to grant authorisation. Your drivers might be installed properly but because of this "authorisation" issue, the phone might not be recognised properly.
Search for methods to pull data from the phone. I had read about a couple of methods where you can mirror your screen on the PC which will solve the problem for you. Unfortunately I am not able to recollect where I read that.
EDIT: Enter fastboot mode on your phone and connect it to the PC. Then using 'fastboot boot twrp.img' you can boot into TWRP on the phone and access the files and copy them using adb commands. This requires the TWRP in the same folder as your adb tools or vice versa and renaming the file as TWRP. I don't know whether this also requires 'authorisation' but try it any way.
Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated
Elixir_ said:
Hey guys,
I'm trying to root my Huawei watch 1 since a week but with no success. The problem is that I'm not even able to unlock the bootloader.
As stated in the title the watch is not recognized at all by the PC, when I plug it in nothing happens not even a sound. I tried with at least 5 different computers running Windows 10 and one computer running Linux (Ubuntu) and I also tried different cables. In Windows Device Manager there is no sign of the watch and in Ubuntu using "lsusb" all the usb ports are shown as empty.
The watch is working perfectly btw with the latest Wear Os update (2.23.0.238044309) and Android 7.1.1
Is there anything I can do to make the PC recognize the watch ? Or are there any workaround to root the watch / unlock the bootloader ?
Any help would be appreciated
Click to expand...
Click to collapse
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.
JimSmith94 said:
Have you enabled Developer Options and ADB debugging on your watch? If not, here's how to do it:
Open the Settings menu on the watch.
Scroll to the bottom of the menu. If no Developer Options item is provided, tap About.
Tap the build number 7 times.
From the Settings menu, tap the Developer Options item.
Enable ADB debugging.
Click to expand...
Click to collapse
Thank you for the suggestion ! I already did it before and unfortunately it didn't change anything to the fact that the watch isn't recognized by the pc.
Hi Team,
Using a one plus 3 device. Want to recover/access data from phone.
Issue with phone:
1. Black screen
2. Volume and power buttons not working
3. No root access/ USB debugging Disabled
Any possible solution to access data from my phone using ADB tool, or any other software or through command line( Android SDK)
Searched for software but most of them works with Samsung phone or USB debugging needs to be enabled.
Now I think only possible solution is via command line if any one having a knowledge of accessing file system via SDK.
Please reply to the thread.
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
adb shell pm enable --user 0 com.samsung.android.kgclient
Click to expand...
Click to collapse
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
Came here just to thank you for explaining this procedure: it allowed me to recover a debloat activity gone wrong. Thanks!
enquil said:
While debloating Samsung Galaxy A70 (rooted) I've disabled something I shouldn't have, and now my phone is locked with a message "Your phone is locked because Payment Services was uninstalled without authorization". I don't have a Samsung Account, so remote unlocking is a no-go.
I need to somehow:
A) Backup my data from internal storage and do a factory reset. (Can't access storage without unlocking the device though...)
B) Unfreeze or reinstall the Payment Services / Samsung Pay app. (I found a guide for another device on how to do it via adb, but my device isn't detected via adb).
C) Re-flash stock firmware with all the stock apps using Odin, without wiping user and app data. (Is this even possible?)
EDIT: SOLVED via method B:
I managed to establish an adb connection. I was trying to do it with the portable version of "minimal adb and fastboot", but it didn't work. "cmd-here.exe" wouldn't show any devices. I tried using non-portable version of "minimal adb and fastboot", and used "cmd" to send commands to adb.exe. It still wasn't detecting the device. I found a fix though:
After unlocking the lock screen, you have a few seconds before the phone will re-lock itself. Use those few seconds to enable developer options (if you haven't already). After the phone locks itself again - reboot, unlock the lock screen, and quickly enable USB debugging before the phone re-locks. Reboot again, unlock the lock screen, request an adb connection (I used "adb devices" command) and click "allow" on the pop-up that appears when your device receives an adb connection. As long as you allow the connection before the device re-locks - it'll stay connected via adb.
Now you can send the adb command to re-enable Samsung Pay. The command in the guide I linked above was incomplete, so it didn't work for me and it took me some searching to figure out why. The full command is
If you did everything correctly, you should see the message in cmd showing that the package has been enabled.
Hope this helps for anyone with the same problem.
Click to expand...
Click to collapse
I wish I could by you a beer Bro. I thought I was gonna have to factory reset my S22 Ultra with over 200GBs used. I had to disable then re-enable USB debugging to get it to work. Minmall ADB didn't work for me so I had to Powershell.