![]() ![]() Root acces and adb running as root are different.īoot image need to be modified to run adb as root. Have I overlooked a configuration detail somewhere? Do I need a modified boot.img as with the original (1.6) firmware? I searched online, and I found that even on rooted devices, it can give error messages as 'adbd cannot run as root in production builds'. I tried it on my phone (Note 2 Android 4.3), which is not rooted, and it didn't work. If I issue "$ adb root" from the PC, I get the response "adbd cannot run as root in production builds".Ĭonsequently, useful commands such as "$ adb remount", "$ adb push" or "$ adb uninstall" all fail with permission errors. The 'adb root' command's description says that it restarts the adbd with root permissions. I cannot, however, get adbd running on the phone to run as root, when the phone is booted to Android. ![]() I can also get a root shell on the phone when booted to Android using adb from the PC. I can root the phone using any of the three methods from the recovery image and applications will then be able to gain root-privileges. I have also installed Malez Recovery 0.6.1. I have installed OS_Acer_1.100.39.EMEA.GEN1_A21E_A without any mods - entirely stock. I have a Liquid A1 - not E the original 256M version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |