According to this post
http://forum.xda-developers.com/showthread.php?p=45897011#post45897011
you can get ADB root without rooting your phone first. I want to install the modded wifi tethering app on my VZW G2 but don't want to root it if I don't have to (mainly just because of time constraints). I have searched how to do this, but all the instructions I find say you need to be rooted to use ADB Insecure/root. If it is possible to just get ADB root without rooting your phone, can someone point to detailed instructions?
Yes, look for the root thread and use the side load adb option. Next, buy that dev a beer.
Hello all,
Here is my situation:
- I have my brother's Nexus 4.
- The screen no longer responds to touch, though it still displays correctly when it is turned on.
- It has PIN security
- It is running stock KitKat 4.4.4.
- It is not rooted.
- USB Debugging (ADB) is not enabled.
- Stock recovery is installed.
- The bootloader is locked.
I would like to be able to back up the contents of the phone, but the state it is in renders that difficult. Here are the different options I've considered and discarded:
- Connect the phone via USB to copy the contents of the SD Card
# Impossible since the phone will not mount USB storage (might be a security feature since it has PIN enabled?)
- USB OTG mouse to bypass using the touchscreen
# OTG support is not available on stock kernels for the N4
- Bluetooth mouse
# No way to enable Bluetooth
- Use Android Control to control the phone via my PC
# No ADB; no way to enable ADB; unlocking bootloader to install a recovery with ADB enabled would wipe the phone.
The only option that might work that I have yet to attempt is to replace the screen. However, based on research I did while trying to troubleshoot my own Nexus 4, this could be a costly waste of time. The Nexus 4 has a history of having faulty touchscreens. Case in point, both my phone and my brother's phone suffered from this same flaw. This might be because the touchscreen controller is bad on the N4's motherboard. I junked my N4 specifically for this reason.
I'm beginning to think that there is no way for me to recover the data on this phone. Does anyone know of a way I could get the data off of it? Any way to enable ADB via Fastboot or Recovery? Any way to flash an ADB-enabled kernel via ADB sideload? Any way to unlock the bootloader without wiping all the data? Any way to run a backup of the whole phone?
Please help! Thank you in advance!
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, that's pretty much what I thought. I was hoping someone here could think of something I hadn't thought of yet. Basically, I think the only two avenues I have to send anything to the phone are via the Bootloader (Fastboot) or via ADB sideload in Recovery. I was hoping I could find something to save me there, but it is looking unlikely.
I am trying to use the ADBD Insecure app to enable adb root access by default. I have already flashed my Nexus to BETA-SuperSU 2.67, and that has worked and allowed me to use su in adb. However, I need to have adb root functionality by default, which is where your ADBD Insecure app has saved me many times.
For my Nexus 6P though, which is running Android M (6.0.1), I'm unable to use the app. Every time I enable insecure adbd, my computer no longer recognizes that there is a device plugged in (it disappears from the Devices and Printers window). Also, although Android OS is still showing that USB debugging is enabled, the app shows that it is disabled.
I've seen this issue a few places on the internet, but have come across no solutions. Does ADBD Insecure not work on Android M, or is there something I am missing?
As a side note, I have a Nexus 5, which was rooted with the same BETE-SuperSU, and the app works fine on there.
Thanks for the help.
Here's a screenshot showing the inconsistency between the app and Android.
i.imgur.com/6p2ZRxa.png
meesa said:
I am trying to use the ADBD Insecure app to enable adb root access by default. I have already flashed my Nexus to BETA-SuperSU 2.67, and that has worked and allowed me to use su in adb. However, I need to have adb root functionality by default, which is where your ADBD Insecure app has saved me many times.
For my Nexus 6P though, which is running Android M (6.0.1), I'm unable to use the app. Every time I enable insecure adbd, my computer no longer recognizes that there is a device plugged in (it disappears from the Devices and Printers window). Also, although Android OS is still showing that USB debugging is enabled, the app shows that it is disabled.
I've seen this issue a few places on the internet, but have come across no solutions. Does ADBD Insecure not work on Android M, or is there something I am missing?
As a side note, I have a Nexus 5, which was rooted with the same BETE-SuperSU, and the app works fine on there.
Thanks for the help.
Click to expand...
Click to collapse
I'm having the same issue on a HTC One M9 stock Marshmallow rooted with beta SuperSU 2.65. As soon as I enable ADB Insecure it reports USB Debugging not active and my computer no longer sees my phone. When I go to developer options USB Debugging is still checked @Chainfire any ideas?
Edit: After settling SELinux to permissive the computer now sees the phone. Going to ADB Insecure it still reports USB debugging not enabled, but after un-checking enable ADB insecure going to developer options and uncheck then RE-check USB debugging I can go back to ADB insecure it shows debugging enabled. I can then enable ADB insecure and all is good.
Using XDA to unleash the power of Android on my HTC One M9 and S6 Edge Plus
but after un-checking enable ADB insecure
Click to expand...
Click to collapse
Yes, ADB still works if ADB Insecure is not in use, but I need adb root functionality.
meesa said:
Yes, ADB still works if ADB Insecure is not in use, but I need adb root functionality.
Click to expand...
Click to collapse
I have root function after going back to ADB Insecure and re-enabling it.
Using XDA to unleash the power of Android
If anyone's post or work has helped you please, use the thanks button
Unfortunately that has not been what has happened for me. Re-enabling it just breaks it again.
Same issue using a Nexus 9 LTE, running Android 6.0.1.
@Chainfire , any idea what's going on with this? Did Android break your app?
Figured out the issue! I was using ElementX 4.06, which is the latest version. I noticed that one of my other devices had version 3.0 on it, so I downgraded and now ADBD Insecure is working as expected.
im also having this issue and i am not using element. my phone is complete stock except im using TWRP. any idea's as to why its not working?
---------- Post added at 11:00 AM ---------- Previous post was at 10:56 AM ----------
after looking i see this app hasn't been updated for two years. im gussing theres some system in place on android 6 thats blocking this.
Is this possible in any way? Will it be possible soon? Thanks.
The only way to root without a PC that I know of is an app like King Root. But you don't want King Root. It only works on certain phones and probably not this one because dual partitions make it much more difficult even if you have a computer. But King Root is pretty much malware. It loads adware onto your phone, sends unrestricted data to servers in China and refuses to give root access to any app that King Root considers a threat to any action that King Root wants to perform on your phone. The fact that anyone actually uses the app is unbelievable to me. There may be an auto root app that is less malicious but probably nothing that would work on this phone.
pementosequence said:
Is this possible in any way? Will it be possible soon? Thanks.
Click to expand...
Click to collapse
You need an unlocked bootloader.
You need a computer to unlock the bootloader.
You need a computer to flash the images.
There is no way to OEM unlock without a computer.
tech_head said:
You need an unlocked bootloader.
You need a computer to unlock the bootloader.
You need a computer to flash the images.
There is no way to OEM unlock without a computer.
Click to expand...
Click to collapse
King Root actually works on some phones where the bootloader can't be unlocked. That was the only reason I tried that garbage app but any benefits from rooting aren't worth the problems caused by the app. If the bootloader is locked but you are rooted you can run apps that require root access like Titanium Backup (as long as King Root doesn't block root access like it does with Adaway) but you can't flash a custom kernel or custom ROM.
I have tried kingoroot over and over and it will not root, is there another way? I have unlocked developer options and this did nothing. Is there any options to be able to boot into safe mode? Or see all of the files and folders available?
Can't get root on mine either, I can connect adb but can't force su access.
freshfitz said:
Can't get root on mine either, I can connect adb but can't force su access.
Click to expand...
Click to collapse
There is very little support on this forum on just about anything. If you figure anything out, please let me know