My LG Stylo 2 Sprint Version running on Android 7 Nougat has a locked bootloader. LG made sure that the bootloader can't be unlocked.  states that it's possible to root with a locked bootloader.  When the boot loader is locked, and the manufacturer doesn’t provide a legitimate method to unlock it, you usually need to find a flaw in the device that will serve as an entry point for rooting it. First you need to identify which type of boot loader lock you have; it can vary depending on the manufacturer, carrier, device variant, or software version within the same device. Sometimes, fastboot access is forbidden but you can still flash using the manufacturer’s proprietary flashing protocol, such as Motorola SBF or Samsung ODIN. Sometimes signature checks on the same device are enforced differently when using fastboot instead of the manufacturer’s proprietary download mode. Signature checking can happen at boot time, at flashing time, or both. Some locked boot loaders only enforce signature verification on selected partitions; a typical example is having locked boot and recovery partitions. In this case booting a custom kernel or a modified recovery image is not allowed, but you can still modify the system partition. In this scenario, you can perform rooting by editing the system partition of a stock image as described in the “Rooting with an Unlocked Boot Loader” section. On some devices, where the boot partition is locked and booting a custom kernel is forbidden, it is possible to flash a custom boot image in the recovery partition and boot the system with the custom kernel by booting in recovery mode when powering on the phone. In this case, it is possible to get root access through adb shell by modifying the default.prop file of the custom boot image initrd, as you’ll see in the “Abusing adbd to Get Root” section. On some devices, the stock recovery image allows applying updates signed with the default Android test key. This key is a generic key for packages that do not otherwise specify a key. It is included in the build/target/product/security directory in the AOSP source tree. You can root by applying a custom update package containing the su binary. It is unknown whether the manufacturer has left this on purpose or not, but this is known to work on some Samsung devices with Android 4.0 and stock recovery 3e. In the worst-case scenario, boot loader restrictions won’t allow you to boot with a partition that fails signature verification. In this case, you have to use other techniques to achieve root access.  This seems counterintuitive, but is it necessary to have an unlocked bootloader to root a device? Otherwise, do any of the methods mentioned in the article work?
107512
I've tried almost any method to root my ASUS ZenFone Live, but no one seems to work. Also I only need root, no unlocked bootloader (don't want to wipe data) or custom recovery (not essential ATM).
122790
I searched in lots of websites/forums but did not find a solution for this problem, and this site is last chance, this is problem: This problem have several other users too. my phone is Galaxy S7 Edge , exynos, Oreo 8.0 (Stock ROM), rooted with magisk latest version. root works well in other applications. In pentesting applications like csploit, Network Spoofer, WifiKill and others  root works well(grants permission)  but when start using options of app(for example, arp spoofing, network sniffer, MITM, etc) drops same error: [ERROR] Unable to retrieve local hardware address libnet ( ioctl: Permission denied ) what to do? Can this issue fixed? or exactly which permission is it?  Also one interesting thing, when I installed old version of WifiKill app it worked - killed wifi connection.
116282
I would like to recover message attachments from a Pixel 3 that died recently. (Yes, I should have had them saved and backed up, but I missed that option for message attachments.)  However, the phone is minimally functional. If the phone could turn on, I could sync those files and be done. It also appears that I need to turn the phone on to enable usb debugging for ADB. I can reach the fastboot menu by holding the power and volume down buttons, but if I try to go past that into "Start" or "Recovery Mode" or even "Rescue Mode," the phone powers off again.  While in the fastboot menu, I can see that a Pixel 3 device is connected by usb to my computer. I have installed Android Studio, Android SDK, and the Google USB drivers. The phone appeared as "LeMobile Android Device" at first, but after changing the driver to Google's it is now "Android Device"--"Android Bootloader Interface."  Running adb devices returns an empty list even while Device Manager shows it is attached (probably because I can't turn the phone on and enable usb debugging).  I'm out of ideas, and am looking for ADB tips to try. What can I try next? How can I get the phone to start or to get access to the phone without leaving the fastboot menu?  Thanks.
110939
Is there any way to disable autostart apps at boot time? I need to disable some of them (not all) like Facebook, etc to get quicker boot time. I'm asking how to do this on Android 9.0.
32245
How to disable system apps without root?  My phone model is vivo x5 max+ and android 4.4.4  I have tried Debloater but it failed to connect (I am sure I've allowed USB debugging).
14025
Or, how do I root my device without a rooter?  Rooting instructions for Android devices that I have seen are typically of the following form:   Download Gingerbreak.apk Run Gingerbreak, click “root device” Observe that Superuser.apk has been magically installed, possibly along with busybox and other things, and enjoy your rooty goodness.   What I am wanting to know is this: how does the rooting actually happen? What does Gingerbreak do?  I understand the end result of rooting:   su is present and working Superuser.apk is installed and controls access to su Various utilities are present, provided by BusyBox (optional?)   I also think I understand the basic idea of how Gingerbreak gets started — it exploits some local privilege escalation vulnerability and uses its new-found powers to deploy Superuser and whatever else is necessary.  So, unless I am wrong in some of the understanding I laid out above, the core of thing I want to know is what the root installer does to deploy and activate Superuser. It seems that just putting Superuser.apk in the right place wouldn't be enough — how does it get allowed root access? How does it get hooked up to moderate that access for other applications?  What does Gingerbreak do post-exploit to enable and secure root access?
84985
I want to do the following without a PC, just directly from an Android phone using a script / Android Terminal:     Reboot into bootloader, and then enter a few fastboot commands   Is this possible?
93133
When the device is set to use MTP, neither Windows, nor ADB will detect the device when connect via USB cable. I have tried multiple cables, in multiple USB ports. I have not tried other computers yet, as this is the only one that actually has the driver installed.  Disclaimer: I am running an Unofficial CyanogenMod 12 build of Android 5.0.2  Device : LG G3 (LG-D855) Android 5.0.2  Google USB Driver: Installed USB debugging: Enabled PC: Windows 8.1 Pro Update 1 No one, except me, has reported this as an issue in the .   I have been unable to get my PC to detect the device via USB since I first installed CM12, which was around 11/10/2014.      If i change to PTP, Windows will detect the device, as will ADB. But Windows will only let me access the internal storage, and Camera folders.
48352
Are there any technical or others reasons why Android is still a firmware and not an OS which can be just installed without a lot of hassle?  Why there is no universal image which could detect appropriate drivers (kernel modules), partition NAND in some standard way and configure boot loader to boot updated OS version?  What stops Google from making a real (less firmware-like) OS (an OS for small ARM, x86 etc. devices)?
113547
My YU YUPHORIA got bricked while I was working with it. I want to install custom ROM into it for that I am installing custom recovery and boot file but the file that is found on Internet was not working and that's why I am stuck with company logo. I can't go into recovery mod, neither it boot, and USB debugging mode is turned off. I tried to install fresh ROM from fastboot but after installing every driver properly command prompt is showing "waiting for the device". Please sugest some way to get rid of this problem.
70796
I see that some  say that rooting involves:   Download a SuperSU as a zip file that would be accessible to the phone (e.g. the sdcard). Unlock the phone's bootloader. Booting into a "custom" recovery mode. E.g. TWRP or CWM. Either temporarily booting using fastboot or flashing the custom recovery to the phone and then booting. Use the custom recovery mode to install the downloaded SuperSU zip file. Reboot the phone into normal mode and root access should be A) available and B) managed by the SuperSU program.   However, I also see that SuperSU is also on the . Installing from the Play Store does not promise any root access. (It actually assumes you already have it.)   So, my questions are:   What is different between these installation methods practically? What is are the technical differences in actions or restrictions?  And how can/does the custom recovery installation method provide root access whereas the Play Store method can not?
16691
How is the ability of a person who gained physical access to your computer to get root with those steps in any way secure?   When grub2 menu opens press  e  to edit the Linux start options Change:   "linux   /vmlinuz-2.6.35-23-generic root=UUID=e7f1e48d-0015-485f-be7d-836217a31312 ro   quiet splash"    to:  "linux   /vmlinuz-2.6.35-23-generic root=UUID=e7f1e48d-0015-485f-be7d-836217a31312 ro init=/bin/bash"  Now you have root access just do:   mount -o remount,rw / passwd user mount -o remount,ro /  sync  reboot the computer and you win.   My question is, how is being able to break into any Linux machine through grub2 secure? I don't understand that fact about Linux, thank you for your answers.
113424
I am having a really hard time finding anything about this on Google which is not from 2011. I have a Samsung Galaxy S10+. I have rooted it with Magisk without TWRP, i.e. no custom recovery or custom kernel. I want OTA updates without having to delete everything on my phone just to update, that is why I use Magisk without TWRP.   What I need is drivers for my WiFi adapter TP-Link TL-WN7220. I know that to be able to install a driver into the kernel, that means a custom kernel and then you would not be able to have OTA updates which defeats the above purpose.  My question is, is there a way to load a driver, even if it is temporary like loading a kernel module on Linux? On Linux this does not require a reboot, can this be done similarly on Android, so I will keep my stock kernel but still be able to run the WiFi adapter?
80029
I recently enabled encryption on my Nexus S running Android 4.1.1. I'm aware of all the benefits and drawbacks, and device encryption is definitely something I want. It's currently working fine.  However, one small caveat I overlooked is that encryption requires a password or PIN lock screen. I assumed (somewhat foolishly) that I'd be able to change back to the lock screen of my choice once the encryption process was complete. I like using a pattern lock, because I can set it to not display any visual cues, which makes shoulder-surfing a lot more difficult. It's also quick and easy to enter a relatively complex code.  The password I used to encrypt the device was intentionally long and complex, making it something I certainly don't want to be entering every time I want to check my messages. I don't want to change it to something shorter, because increased security was the whole point of doing this in the first place.  Is there a way I can go back to using a pattern lock screen? I understand that encryption is irreversible, and I don't really want to remove it. I just want my old lock screen back.  EDIT: I notice that changing the code for my lock screen also changes the key used to decrypt the device, which I assume is why you're not allowed to use a different type of lock screen. I very specifically do not want to be using the same code to encrypt the storage as I'm using to unlock the screen. That seems like a terrible idea, and I can't believe it's really the way Android does it.
49873
According to ,      /data ... Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.   What about /boot, /system, and /recovery, and /cache?    If Factory Reset wipes only /data, then I wish it were called something else, because if you've rooted your phone, it will still be left with whatever custom ROM you flashed even after a Factory Reset.    On the other hand, if Factory Reset does indeed wipe /boot, /system, and /recovery as well, especially /boot, what does it restore those from?  Do all phones come with stock images in a real internal ROM somewhere that it can re-flash those images from?    I can somehow imagine manufacturers not wanting be burdened with the extra cost that such a spec for hardware-recoverable images might have cost them, so it got left out of the standard and left out of most phones, which is why it's so easy to brick them.  So, instead, they give you the option to wipe /data and /cache only, and call that a "Factory Reset" because you're not supposed to be foolish enough to root your phone in the first place according to their way of thinking.  Since rooting my Android and reading hundreds of posts, I've found that many of the terms I learned and accepted as a Computer Science grad student in the 80's don't quite mean the same thing anymore so I have to verify what everything really means before I do something.    Comments to  answer the first part of my question.  But they don't really answer the second part of my question which is really a complaint:  Why call it "Factory Reset" if it doesn't really restore your phone to it's stock factory state?    At this point, the question is merely rhetorical.  I think I already answered this in my question, unless someone can correct me.
79878
I will have a few Android phones that I will have to let go.   I would like to make a proper clean wipe of the data, without no one being able to retrieve them, and do a factory reset.  I have read about the , encrypting the device before doing a factory reset, doing both, etc.  Since I am not an Android/adb guru, I would like to know if some of you would have some idea on how to achieve this with certainty.  I know "certainty" is a big word when it comes to proper data erasure on flash memory but still.  I have found some answers here and somewhere else, saying that encrypting and doing a factory reset on your Android device is enough, but I could not find a reliable source.  Just a few information that could be useful:   I'm running Linux as my OS and, therefore, I'm not looking for a Windows-based solution My devices are non-rooted and (almost) identical (Samsung A510F + 1 A510FD)
81442
So I have an old unlocked phone and I'd like to load up my own OS.  I've seen some mods out there.  CyanogenMod seems to be the most popular.  However, I was curious if I could just install a pure untouched version of the OS -- as distributed by Google. I seem to remember being able to download a clean compiled version of the Android OS.    Does Google distribute any binaries like this, and if not, is there someone out there that does?    Additionally, is this even worth trying?  These days is it necessary for Android to be packaged with special drivers and such for all of the different hardware out there?