Related
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus. Not exactly obvious why, but I you select the second option "Camera (PTP)" the device is available for debugging. This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise
Click to expand...
Click to collapse
Basically, This is my problem. I need to change my Nexus usb configuration from MTP to PTP so that it'll show up on adb devices, but unfortunately I'm softbricked; I cannot get my Nexus to do anything because I can't get it pass the googlescreen.
So my question is; is there anyway to change it from MTP to PTP without having the option to enable it via the tablet?
Bump, can I configure usb through the nexus toolkit? Please help.
What do you mean?
EDIT: Saw the OP now. If you can get into bootloader mode, try flashing a factory image. If that's not the answer you were looking for, please specify your requirements and why you need them.
I don't know what you mean, and I don't understand why you recommended flashing a factory image but I'll try to elaborate.
At the moment, my Tablet doesn't allow for USB Debugging.
It is Soft Bricked, so I can't get into system to enable USB Debugging, as I have accidentally deleted my OS.
I cannot disable MTP either because I cannot access my tablet setting.
WHAT I NEED:
An alternative to accessing these such settings.
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Yeah since you dleted the OS itself, your only optioons are to either flash a ROM from recovery or flash the factory image.
ivn888 said:
To activate usb debug you have to go in "developer options".
To repair "softbrick" you have to flash factory image in "adb sideload" or adb in linux or windows pc.
Click to expand...
Click to collapse
Not necessarily correct, since it depends on having a working custom recovery that can start an ADB instance. Fastboot flashing is much more reliable.
You DO NOT need USB debugging in recovery or fastboot modes.
USB debugging ONLY applies to a booted OS.
Sent from my Galaxy Nexus
Stop trying to use ADB, use FASTBOOT. There is a sticky at the top of the forum How to flash a factory image using fastboot/return to stock. It has all the information you need to return to a working device. ADB is only useful if you have a working OS, which currently you do not.
As the title says, I can't connect my N6P to my computer while USB debugging is on. Also, for some reason, it DOES work when the phone is in recovery mode, but I don't want to reboot in recovery every time. Anyone know how to fix this?
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
If you do a manual factory reset , never gonna lose the root.
diver47591 said:
After following info on XDA and everything I could find elsewhere on the web to no avail, ADB still showed "error; device offline" . I believe I must install new rom in order to start over with computer/device recognition. After "Revoke USB Authorizations" in Settings>Developer Options>USB Debugging, believe that is a permanent revocation until computer is presented with a new system.img, (rom). But I am just noob, please correct me if I'm wrong. So if I'm correct I guess I'll Have to do Factory Reset, lose root, and go through the whole process again
Click to expand...
Click to collapse
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
alaneddy said:
When you "Revoke USB Authorizations" it just clears the current saved devices. Try this, unplug device, use a USB port on back of the computer (sometimes it matters), make sure Developer Options is enabled, USB Debugging enabled, Verify apps via USB unchecked, revoke USB authorizations, then start ADB, plug phone in and wait for it to be recognized by windows, then enter the command "adb devices". The phone should ask if you want to authorize this PC.
If that fails, try a different cable.
Click to expand...
Click to collapse
I was way off! I found a suggestion on another site that recommended updating sdk. Determined my sdk was version 1.0.29, updated to 1.0.30, and voila returned "device name device" good to go. Thanks so much for the help.
So, I followed the directions in the "[H918] recowvery, unlock your V20 root shell - now with TWRP!" thread by jcadduono to unlock the bootloader, however after rebooting out of the bootloader, I now find that I can't re-enable USB Debugging(it is greyed out and off) and I can't disable OEM Unlock(not that I'd want to, but it is on and greyed out). This is making it to where I can no longer allow ADB to access my phone via USB, and so I can't continue on with root. I've uninstalled and reinstalled all the V20 drivers on my computer just in case, but adb doesn't see any devices connected, which is really weird, since, as I said, I already unlocked the bootloader... Has anyone else had this issue? Am I missing something obvious?
Edit: So I figured this out. For anyone having a similar issue, this actually seems to be something with the phone, if you toggle off developer mode and then turn it back on you can change the USB Debugging option state, but you have to be quick, because it will lock the option after a second. After I obtained root this issue went away entirely and I can now toggle it on and off whenever... I'll chock it up to a weird bug, but I've updated this post with a solution.
Thank you. I Ran into this right now, worked perfectly.
Hi,
My touchscreen stopped working all of a sudden, in a very similar way as these users reported:
> https://forum.xda-developers.com/oneplus-5/help/oneplus-5-touch-screen-stop-t3757724
> https://forum.xda-developers.com/oneplus-5/help/touchscreen-responding-how-access-t3844693
The phone boots up to the "Enter pattern for all data and features" screen, and I'm not able to enter the pattern since my touchscreen doesn't respond. For what it's worth, my phone is rooted and has the latest TWRP installed. However, the phone is encrypted, USB debugging is disabled and I have an anti-theft app (Cerberus Anti-Theft) that can act on settings like "Prevent USB debugging" or "Disable Wi-Fi". I have three users on my phone, and I have been able to recover the data of the first user only so far (see below).
Idea 1: use an USB OTG mouse
I did try this solution, but nothing happens when I plug the USB mouse. The blue LED on the mouse doesn't turn on, and it seems that no power is output at all.
Idea 2: use an USB OTG mouse in recovery
I tried to boot into recovery and plug my USB-C mouse in... but nothing, no pointer, no power drawn from the mouse.
Idea 3: boot into recovery and use TWRP adb commands
The phone boots TWRP and prompts me to enter my pattern, but is not able to communicate with the PC. 'adb devices' shows nothing.
Idea 4: load a temporary TWRP from fastboot
The phone boots fastboot without any problem. I'm able to 'fasboot boot C:\twrp-cheeseburger.img', and TWRP boots just fine. I then try to plug my USB-C mouse, and it works! I can see the pointer, and the mouse's blue LED turns on. I can enter my pattern, decipher my Data partition and backup everyhting to my PC.
HOWEVER, I am not able to access other users' data, and I have a work profile that contains data I would really like to recover. Is there any way to decrypt data from secondary users without booting Android system?
On a side note, I was also able to permanently flash the TWRP I booted from, which means I'm able to use the mouse without having to 'fastboot boot'.
I now have full, untethered recovery access, with full mouse support. I'm still not able to swipe to confirm some adb commands though, as I have to disconnect the PC cable to plug the mouse.
Idea 5: enable USB debugging from temporary TWRP in order to use adb from Android system
I would gladly accept any help on that matter.
From what I've read, I have to edit two files, '/data/property/persist.sys.usb.config' &'/system/build.prop', and then push RSA keys on the device in the '/data/misc/adb/adb_keys' folder.
The pulling / editing / pushing part is OK, but the RSA part seems trickier. I've never connected my phone via adb to my computer (just recently bought it), but I do have the adbkey files in my home folder. I would try and give my results back here, but like I said, I have data that I would like to recover and I can't risk messing with the keys.
Idea 6: find what's causing the USB ports to be disabled
Easier said than done! What could possibly prevent the USB port to be completely disabled (except for charging)? Any ideas? I'm guessing Cerberus Anti-Theft might have to do something with it, but I couldn't find anything specific on that matter.
Idea 7: nandroid backup the phone, wait for quantum computers to become commercially available and bruteforce the private keys
Hmmm...
I'm really running out of ideas here.
EDIT: Solution
> The only way to get to secondary users' files is to boot Android system and enter the pattern.
> The only way to enter a pattern with a broken touchscreen is to use an USB mouse.
> USB OTG wasnt enabled on my phone for some reason, so I had to find a way to enable it from recovery. I booted in fastboot mode, then flashed the latest version of TWRP so I was able to use the mouse in TWRP (OTG mouse is enabled by default in TWRP).
> USB OTG was still disabled in Android system. Luckily, I had Magisk installed so I was able to flash the zip that Axelguitt suggested, which is a Magisk module that enables USB OTG at boot.
Here's a link to the module (by simonsmh): https://forum.xda-developers.com/apps/magisk/module-oxygenos-otg-enabler-t3735922. Simply install the provided zip from recovery.
> This permanently enabled USB OTG in Android system, so I was able to enter the pattern and backup data for all users.
Did you look in /storage/emulated/ in TWRP? There should be some numbered folders, 0 being the primary user. 999 for parallel apps and so on.
Lupus77 said:
Did you look in /storage/emulated/ in TWRP? There should be some numbered folders, 0 being the primary user. 999 for parallel apps and so on.
Click to expand...
Click to collapse
Hi,
On my device, /storage/ is empty (adb pull gives nothing and TWRP File Manager also shows that the folder is empty).
The primary user's files are in /data/media/0 (perfectly readable using TWRP File Manager)
The other users' files are in /data/media/10 & /data/media/11, but are encrypted. I'm looking for a way to decrypt these specific files
This is not really an answer or another idea but a reason, why your mouse doesn't work while in Android - the OTG switch is off.
I think there's a workaround to permanently enable OTG without needing to go to settings, but I think that's kernel based, you'd have to flash a custom kernel with that enabled. I think @nathanchance had it on his now discontinued Flash kernel, maybe he can help.
Is it possible to install a magisk module while you are in recovery?
If so I maybe have an idea :
Go in recovery and find a way to install this magisk module:
https://forum.xda-developers.com/apps/magisk/module-oxygenos-otg-enabler-t3735922
This module enables always on OTG in oxygenOS.
Then boot in system and you should be able to use an OTG mouse.
It is only a suggestion, I have no clue if what I'm suggesting will work.
Axelguitt said:
Is it possible to install a magisk module while you are in recovery?
If so I maybe have an idea :
Go in recovery and find a way to install this magisk module:
https://forum.xda-developers.com/apps/magisk/module-oxygenos-otg-enabler-t3735922
This module enables always on OTG in oxygenOS.
Then boot in system and you should be able to use an OTG mouse.
It is only a suggestion, I have no clue if what I'm suggesting will work.
Click to expand...
Click to collapse
That actually worked!
Many thanks
Bakuryu91 said:
That actually worked!
Many thanks
Click to expand...
Click to collapse
You're welcome!
Can you explain how to install a magisk module from recovery just in case someone with the same issue find this thread?
Axelguitt said:
You're welcome!
Can you explain how to install a magisk module from recovery just in case someone with the same issue find this thread?
Click to expand...
Click to collapse
In this case, the dev (simonsmh) provided a flashable zip of the module. This is usually the case for Magisk modules.
Bakuryu91 said:
In this case, the dev (simonsmh) provided a flashable zip of the module. This is usually the case for Magisk modules.
Click to expand...
Click to collapse
Cool thing to know, I'll remember it if I ever break my touchscreen!
my oneplus 5 keeps getting this issue the touch screen not working ive reset the phone twice now and it still happens. i read its something to do with a bug or hardware problem with the latest android i read this a few times online. is there a custom OS i can load on there that doesnt have this problem?
i already tried to load on an older version of the os and while it worked im still on android 9 when it should have loaded 8. so i know how to load it on but what should i use?
sick of this **** it works then it randomly decides not to work! a reboot works sometimes other times its a full reset