In the TWRP thread some people confirmed that their Moto Z Play also turns USB debugging off on reboot. Like mine.
Does anyone know the reason? Is it related to the problem that /data is formatted using f2fs which is having a broken loopback device until fixed, which already prevents systemless rooting and usage of Magisk? How to keep it enabled?
Related
So i just updated my Zenfone 2 ze551ml and wanted to root the phone. But everytime I enable the USB debugging, it gets enabled for 5 seconds and gets disabled immediately. Doesn't matter if I am connected via USB or not, just keeps getting disabled for no reason.
Twice it has rebooted while enabling the USB debugging, so something is amiss.
Any suggestions on what should be done? I cannot root my phone/install custom rom/recovery without it. This problem started with the last major update, and the new 24mb update did not solve it.
I've got an LG G Pad 8.3 and I deleted all my files with recovery (stock) by accident. And I didn't made a save from them. I want to recover my files, but I can't do this because it can connect to PC only by MTP and If I wanted to root it via adb, adb said my device is offline. Can anyone help me in this problem?
rektilian said:
I've got an LG G Pad 8.3 and I deleted all my files with recovery (stock) by accident. And I didn't made a save from them. I want to recover my files, but I can't do this because it can connect to PC only by MTP and If I wanted to root it via adb, adb said my device is offline. Can anyone help me in this problem?
Click to expand...
Click to collapse
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Thank you
roirraW "edor" ehT said:
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Click to expand...
Click to collapse
Thank you. If i have time i will try it.
Doesn't works
roirraW "edor" ehT said:
You mean you Factory Reset so that your internal storage were wiped, right?
There's probably some Android apps available to undelete files, but I have no experience doing so. You have USB Debugging enabled? Also, some LG devices have a solvable "bug" (at least after rooting) that after every reboot, USB Debugging is turned back off. If yours has that problem, the way to fix it is to turn USB Debugging on, hook the device up to the PC, change it to PTP mode, then back to MTP, then disconnect. From now on it should be good again until certain circumstances cause it to start happening such as after flashing a KDZ or TOT and then re-rooting.
Once USB Debugging and you try to access the device via ADB, you'll have to confirm the ADB authorization dialog on the device. Select the checkbox to remember the authorization.
Click to expand...
Click to collapse
It doesn't works. adb still sais offline.
rektilian said:
It doesn't works. adb still sais offline.
Click to expand...
Click to collapse
No idea what else to suggest. I'd probably have to be there and fool with it myself to get any ideas.
Did you look for any undelete apps in the Play Store?
Hi,
i have rooted my Pixel 3 XL without problems.
TWRP & MAgisk is installed.
Now i wanted to disable the new gestures as described here:
https://www.xda-developers.com/disable-android-pie-gestures-google-pixel-3/
unfortunately, the USB Debugging does not stay on.
Also titanium backup always complains about this.
When i enable USB Debugging, i see for a few seconds some "le Mobile android device", but disappeared immediately after.
USB drivers are installed.
Any idea?
Thanks
Btw: adb devices shows me my device in recovery when in TWRP. So cable seems to be ok. (anyway, i installed everything with this cable).
Termi11 said:
Hi,
i have rooted my Pixel 3 XL without problems.
TWRP & MAgisk is installed.
Now i wanted to disable the new gestures as described here:
https://www.xda-developers.com/disable-android-pie-gestures-google-pixel-3/
unfortunately, the USB Debugging does not stay on.
Also titanium backup always complains about this.
When i enable USB Debugging, i see for a few seconds some "le Mobile android device", but disappeared immediately after.
USB drivers are installed. Any idea?
Thanks Btw: adb devices shows me my device in recovery when in TWRP. So cable seems to be ok. (anyway, i installed everything with this cable).
Click to expand...
Click to collapse
Assuming you have enabled USB debugging in Dev settings. You've somehow got the wrong drivers installed. Use a program called USBDeview To remove all the Google related drivers on your PC/Laptop and reinstall the Google USB drivers. There are tutorials out there for step by step, but for some reason your drivers are wrong.
I confirm, Dev options are enabled, so also USB debugging.
Unfortunately when i enable USB debugging (WITHOUT CABLE), go back, and enter again in the Dev options menu, the USB debugging is disabled again..
But nevertheless i reinstalled the drivers as you wrote -> same problem.
I think the problem is the Pixel, not windows, as everything went fine while rooting the device. (usb debugging was active).
Solved!
My fault, enabled by mistake in Cerberus App the "prevent USB Debugging" option!
Should work now
Hello.
After almost 3 great years my Moto bit the dust. I was wondering if it's possible to recover data from it.
Its display is broken, but i know it works, because I can still unlock it with fingerprint. It's rooted so obviously USB debugging is enabled, but it doesn't show up on device manager nor on adb devices list.
Any ideas?
-N
If you boot it to TWRP, where MTP is enabled by default, so you can copy files to your PC
As the title says, I'm stuck in a bootloop with USB Debugging disabled. I know close to nothing about coding and stuff (sorry if I use the wrong terminology), but I started the first steps to fix my phone without losing my data (hopefully). My only barrier now is that I can't use ADB to reset my phone because of the USB Debugging part. Any advice on how to enable it?