Does anyone know why PTP mode would not be retained across a reboot? It seems to revert to MTP when rebooting into either the bootloader menu or into regular user mode.
I am trying to unlock the bootloader on my Nexus 6 running the latest build N6F27C of 7.1.1 that was sideloaded over 7.0 using ADB from my Mac. Now I'd like to start again and perform a clean flash of the 7.1.1 using ADB.
In normal user mode I can enable USB debugging in Developer Options and when PTP USB mode is selected then ADB will list my device just fine, I can trigger a reboot, etc.
However, after rebooting into the bootloader menu ADB shows that it has lost connection with my device, even though the screen shows that USB is connected. The ADB device list is empty.
On subsequent reboot into user mode I can see that USB debugging mode is still on but PTP connection mode has reverted to MTP, which (at least on a Mac) can account for ADB's lost USB connection to the device.
ADB debugging in PTP mode has worked fine for me in the past, but the phone now has been through several factory resets and restores from Google's backups, plus it is on 7.1.1.
Related
In reply to PsychoAssassinX in the dev forum:
http://forum.xda-developers.com/showthread.php?t=936810
ADB does not recognize a stock NookColor because debug mode must be enabled on the device. To enable debug mode, you must have a rooted NC.
If you boot with NookieFroyo, you can activate debug mode by selecting from the notification menu in the upper left after connecting the NC via USB.
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Cheetohz said:
So, I went and skipped through the setup process without inserting my SIM, enabled developer options and turned on ADB access, and enabled OEM unlock while I was at it. I use eclipse frequently for other devices, so I ran an update in SDK manager. My device is not showign up as an external drive, or in ADB. However when I reboot into fastboot, I get a connection just fine. I am suspecting this is a software issue on the device itself. Any ideas?
Edit: switching from MTP to PTP was the only thing that worked
Click to expand...
Click to collapse
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
PaisanNYC said:
What showed up in Device Manager when connected as MTP? Did it perhaps say ACER Android Device or something similar to that?
Click to expand...
Click to collapse
I actually did nto check device manager. but I had the safely eject Nexus 6 show up in my task bar, so it was recognizing it as a nexus.
hello
dropped my N6 on to a marble floor, the screen is black and touch is not responding. the phone seems to be working otherwise. usb debugging is off, the phone is fully stock (stock recovery, bootloader is locked, encryption is the marshmellow default, phone is not rooted). There is no lockscreen pin or pattern, just the standard slide to unlock. photos are not auto-backed up online, so I need access to the phone itself.
when I plug the phone into my computer, I cannot file explore it because I need to enable a prompt on the phone to MTP instead of charge only. as USB debug if off I cannot use ADP PULL / SDCARD.
I have two ideas:
1) use Wug's nexus root toolkit and do something there like put TWRP on, and then use TWRP to avoid the USB debug being off. I'm not sure on the details of this though! Any guide on the steps here? the power and volume hardware keys work, so in theory I can get into recovery with the right steps.
2) get a micro-usb hub, and plug in a wired mouse as well as connect to my computer, then blindly click about hoping that I enable MTP or USB debugging. I can then either copy files off in windows explorer or use Vysor to control the phone over ADB and email files etc as needed. Would this work? I don't have a hub so would need to spend £5-10 buying one
Many thanks in advance for any help!
Option 1 won't work because the bootloader is locked. You'll have to try option 2.
Hello,
I want to talk about a problem that I have experienced for a long time on my Mi5 Pro (128GB) device.
Since I bought the device from my friend (knowing the problem), I don't know when USB last worked.
Problem:
* The device is only charging when I connect the device to the PC.
* There is no notification about USB connection.
* PC doesn't recognize the device.
* In bootloader mode, the PC can see the device as a fastboot device. I can do operations on fastboot such as flashing a rom.
So far I have:
* flashed different Marshmallow, Nougat, Oreo Global Stable Rom, Developer Rom, Custom Roms.
* flashed different original and custom kernels.
* tried 3 different PCs with 4 different data cables.
* done editing in the build.prop file related to adb connections etc.
* deleted and reinstalled adb / fastboot drivers on PC.
* tried using USB 2-3 ports, PC's direct motherboard usb ports etc.
* turned on and off USB Debugging on the developer options
* changed the setting of USB Mode to ptp,mtp etc. on developer options.
* locked and unlocked device etc.
My own solution to temporarily access ADB / Phone memory:
Step 1: I get into fastboot mode when device is not connected to PC.
Step 2: In Fastboot mode, connect the device to the PC. PC sees the device as a fastboot device.
Step 3: I reboot into Recovery manually when the device is connected to the PC.
Step 4: In TWRP (MTP Enabled) PC can detect the phone and I can access the files.
Step 5: I start the device normally with the function "Reboot to System" via TWRP when the device is connected to the PC.
Step 6: When the device is turned on, the USB connection notification is coming up and I can use it as an adb device and access the memory.
Step 7: After disconnecting the device from the PC, the PC never sees the device again when I reconnect the device.
I don't have access to the device memory/adb unless I repeat these steps.
PS: I wrote the steps individually because, for example; This method doesn't work if I open fastboot while the device is already connected to the PC (Step 1).
Hopefully, a solution proposal comes up. This is a really weird problem for me.
Thanks in advance for your suggestions.
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530
If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.