As the title says, I'm fed up with the Google News Application. But the thing is., It is installed as a system app and I don't want that- Disable is the only option that exists for me. I've been disabling it everyday. Even I've disabled Auto-Update for that but still it ENABLES by itself and even UPDATES BY ITSELF.
I've even seeked the help of customer care but they told me to visit SERVICE CENTRE and I even did the same. When I visited the service centre, they just Hard resetted my device and I told them that I've done it more than 6 times at home. They started arguing with me thereby accusing me with bad words...
My phone is still under warranty and I don't want to lose it by installing TWRP and rooting it...
Any kind SUGGESTIONS are HEARTLY WELCOME.
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Okay. Thank you. But it gets only HIDDEN not completely uninstalled. As of I know, I can't uninstall permanently without root access.
SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..
PiXinCreate said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..
Click to expand...
Click to collapse
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.
SnapDrag910 said:
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.
Click to expand...
Click to collapse
Honestly speaking, in New to using ADB... But knew sp flash tool and I had thought that both are similar but not.
Are Nokia drivers are same as Google drivers?
Can you share me the step by step procedure is you enough time now, sir?
I just downloaded latest usb driver from developer.android.com
Hey Guys let me tell you I do get automatic installation (via Google Play) for the Google News app (yes frustrating ) but what I did is uninstalled updates emptied it's data and forced stop / disabled it.
As of this comment I do get automatic installation request via Google Play but Google News doesn't updates. This worked for me.
Related
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable
When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2
download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium
i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium
You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.
Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.
bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.
I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?
Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC
Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app
I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app
Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse
rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.
This guide is for people that have always problems with drivers, ADB or fastboot problems, with this guide you will clear all.
Tested and working with windows 8.1 (it will work with all other versions of windows, probably not with Windows 10 preview).
*0) Unplug of course the phone from the PC
1) Download USBDeview (32bit version here http://www.nirsoft.net/utils/usbdeview.zip - 64bit version here http://www.nirsoft.net/utils/usbdeview-x64.zip) to erase every driver on the pc (look under "Description" tab and uninstall all Asus things, MOOREFIELD, delete also your previous phones drivers or unused devices)
2) Reboot
3) If you are on windows 8 or 8.1 disable driver signature verification and than install
1- Intel Drivers https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
2- ADB Installer http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 (don't change installation path)
4) Reboot
5) Go in C:/adb, hold shift on keyboard, right click in the folder and "Open command prompt here"
6) Go to recovery with the phone plugged in
7) Tap apply update from ADB Sideload
7) Type in the previous cmd window: adb devices
If you can see your device, congratulations!
Thanks to @cangcan to this other tip:
If you installed bluestack on your pc, adb will show 'device emulator' something like that and you need to turn off the bluestack service..
1. Go to start and type services.msc
2. Look for Bluestack android service
3. Stop or disable the service
Its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled Bluestack services..
Thanks to- Everyone in this section
Snoop05 for "15 seconds ADB Installer"
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
cangcan said:
another thing i found for adb device not recognised for example in my case before..
if you installed bluestack on your pc or laptop, adb will show 'device emulator' something like that..
you need to turn off the bluestack service..
1. go to start and type services.msc
2. look for bluestack android service
3. stop or disable the service
its messing up my adb connection in windows 7 and now the zf2 device is recognised on adb after disabled bluestack services..
type adb devices to confirm it.
Click to expand...
Click to collapse
I will add this to first post, thanks
Hello, I badly need someones assistance. I accidentally installed the OTA update on my rooted zenfone 2 causing it to be bricked. I have spent the last 3 hours uninstalling and then reinstalling the drivers per the above directions. My PC recognized when I connect the phone via USB, and it is showing up as a working device in the device manager screen. It shows the drivers are installed properly and everything but I just cannot view it. I tried disabling the bluestack (it actually was not turned on but I made sure to disable it in case) and that did not work as well. I now have a zenfone 2 that is currently a paperweight and I cannot for the life of me figure out what to do next. Any help would be greatly appreciated.
Thank you for this
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Did you get permissions on your phone when popup appears?
No. The phone doesn't pop up the permission question. But I don't know why.
Don't know but as long as you don't give permission you can't sideload
Euclid's Brother said:
Been trying to get an adb connection to this phone. I'm on the latest Sprint available OTA (NMJ32F). Have not side loaded the later version. Never rooted.
When connecting the phone to PC, device manager shows "Essential Phone ADB" is working properly. I also tried the Google generic ADB driver. The phone also shows a notification "ADB debugging is connected. Tap to disable".
"adb devices” always returns empty. I am able to adb other devices.
I think the problem is the phone is not asking me to authorize the ADB connection as my other phones and tablets normally do.
Any idea?
Click to expand...
Click to collapse
Try the usb driver and SDK platform tools directly from Essential website:
https://www.essential.com/developer/current-builds
I am using the drivers from Essential website. However, I was using the lastest Unified Android Toolkit for the adb command. Looks like it may be outdated, as the adb.exe and it's dll's in the link from Essential website is newer. I will try the platform tools from there and see if there is a difference.
Thanks!
Is USB debugging enabled in Developer settings?
Are you in Fastboot? Did you try "fastboot devices"?
ADB devices returns your device is offline?
The popup to allow USB debugging from my computer doesn't popup when I connect my Oneplus 5 to my computer, and thus ADB devices comes back empty. This is only happening for my PC on stock Rom. When I tried installing another Rom, the popup to allow USB debug option comes and the phone is getting detected in my PC. Even on stock Rom, in another PC popup to allow usb debug option comes, only in my PC stock Rom it is not getting detected. Not sure whats and wheres the issue(PC or Phone)?!
I I've rooted my phone before and it was working fine previously and it stopped being detect after OB10 . I looked online too and tried options like restarting, turning debugging off and on, revoke USB authorization etc...... nothing works Please HELP!!!!
swapnilshah said:
The popup to allow USB debugging from my computer doesn't popup when I connect my Oneplus 5 to my computer, and thus ADB devices comes back empty. This is only happening for my PC on stock Rom. When I tried installing another Rom, the popup to allow USB debug option comes and the phone is getting detected in my PC. Even on stock Rom, in another PC popup to allow usb debug option comes, only in my PC stock Rom it is not getting detected. Not sure whats and wheres the issue(PC or Phone)?!
I I've rooted my phone before and it was working fine previously and it stopped being detect after OB10 . I looked online too and tried options like restarting, turning debugging off and on, revoke USB authorization etc...... nothing works Please HELP!!!!
Click to expand...
Click to collapse
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Dirk said:
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Click to expand...
Click to collapse
Thanks will try that and update you...
Dirk said:
If you have a folder named '.android' in your User Directory, delete it and then try again. If this doesn't work uninstall your current ADB software and reinstall the Platform Tools package:
https://developer.android.com/studio/releases/platform-tools
I've had this once or twice and that always did the job.
Click to expand...
Click to collapse
I tried deleting .android folder in user directory and also reinstalled the platform tools package.... but still it is not showing the device in adb devices command.
swapnilshah said:
I tried deleting .android folder in user directory and also reinstalled the platform tools package.... but still it is not showing the device in adb devices command.
Click to expand...
Click to collapse
On the Stock ROM, where you are having the trouble, does your PC see the phone when you connect it. i.e does it show up as a device in Explorer and Device Manager? When you enable MTP can you transfer files?
As it's only a problem on the OOS ROM, i wonder if it's a Driver issue. When you installed the Platform Tools, did you install the Google USB Drivers?
Also have a look here. There may be some useful information:
https://stackoverflow.com/search?q=adb+doesn't+see+my+device+on+pc
try to use a different cable. it works for me
i had a same problem like you
had the same problem on my phone (manually added the adb public key to get access), only got fixed by factory reset. the popup just didnt show no matter what, even though adb worked.