Hi there,
My device was properly rooted (verified by Root checker).
But after
Code:
adb root
It returns
Code:
adbd cannot run as root in production builds
How to solve it?
Thanks.
Cheers,
Wen
ah! You can try FX file explorer, navigate down to the bottom till you see system root settings
enable it and mount remount the system (root) files without ADB thank you
golanpiyush said:
ah! You can try FX file explorer, navigate down to the bottom till you see system root settings
enable it and mount remount the system (root) files without ADB thank you
Click to expand...
Click to collapse
Thanks.
I tried FX file explorer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But after superuser in Magisk was granted to it and file "system (root) was remounted, adb root could still not work.
It returns "adbd cannot run as root in production builds".
Actually, this issue was solved by installing and enabling "adbd insecure", but afterwards, the device could no more be recognized by adb.
Device unrecognized by adb after checking "Enable insecure abdb" in "adbd insecure"
Hi there, After installing "abdb insecure" on my rooted device and checking - "Enable insecure abdb"; - "Enable at boot". The device is no more recognized by adb. After - adb shell, it returns - " * daemon not running; starting now at...
forum.xda-developers.com
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3 Options to install.
First step: Download "bootanimation.zip"
1. ADB
Navigate to the folder containing "bootanimation.zip" in terminal/command prompt.
Type the following
Code:
adb push bootanimation.zip /Data/Local
Then to test, set your device so display is in landscape (will not display properly if you have it on portrait and test it but will display fine either way on boot)
Code:
adb shell bootanimation
2. Root Explorer
Copy "bootanimation.zip" to your SD card
On your Streak open up Root Explorer (or any other app that allows you to copy paste to the internal memory)
Copy "bootanimation.zip" and paste it to /Data/Local
3. Terminal Emulator
thanks nickshertzer, his directions are for drop box but can easily be manipulated for simply copying the bootanimation.zip to your SDcard
nickshertzer said:
BTW, if you don't have / want to get out that sync cable for ADB, use dropbox & Terminal Emulator. Make sure you download the .zip using dropbox longpress first before running following command (requires Busybox / can't remember if it is installed default on Steve's ROM)
Code:
su
cp /sdcard/dropbox/bootanimation.zip /data/local/
reboot
Click to expand...
Click to collapse
Enjoy
very nice, pure and simple but smooth..
request if you're up to it:
honeycomb honeybee android HD bootanimation...(maybe buzzing around!) = sweeeet!
thanks!
Nice work will give it a try do you have any plans to add more to it
Worked fine on DJ-Steve's 1.6.1. Simple but nice.
Edit: also works on baseband 318, with the perfmod.
Hello,
At the beggining I had SDK Tools Only and everything was ok, after typing adb logcat I got logs. Then I installed ADT Bundle and run eclipse -> DDMS and in logcat tab I got logs. Then I installed a couple of programs to make screencasts. The next day I run eclipse -> DDMS and I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[2013-05-18 08:46:16 - ddms] ADB rejected shell command (getprop): closed
[2013-05-18 08:46:29 - ddms] ADB rejected shell command (logcat -v long): closed
[2013-05-18 08:46:29 - Unexpected error while launching logcat. Try reselecting the device.] closed
com.android.ddmlib.AdbCommandRejectedException: closed
at com.android.ddmlib.AdbHelper.executeRemoteCommand(AdbHelper.java:381)
at com.android.ddmlib.Device.executeShellCommand(Device.java:462)
at com.android.ddmuilib.logcat.LogCatReceiver$1.run(LogCatReceiver.java:110)
at java.lang.Thread.run(Unknown Source)
When I run adb logcat from console I got this message: waiting for device.
adb devices detect my phone
I have windows vista home premium
android 4.1.2
What I did:
- uninstalled SDK Tools Only
- reset adb / unplug and plugin my device
- I tried this one: adb -s emulator-5037 logcat but still waiting for device
- adt bundle - sdk manager -
- windows task manager - there is just one adb.exe running
but still I get waiting for device and the exception in eclipse.
thx in advance
c'mon guys help me out with this
Hello!
I think it's the easiest way to get root access. I was able to root my p760 at V20O. The app do almost everything for you or explains what you have to do but if you want, follow the steps below.
1. Download and install the drivers
Windows http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
2. Download and install the app http://www.firedrive.com/file/C31D92BBC45B3051 (it's official link).
3. In developer section select "Debugging Mode" as ON, and "Install from Unknown Sources" as ON in Phone Settings.
4. Run Kingo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Connect your phone to computer in charging mode. Press ROOT button.
6. The device should restart itself with SuperSu installed.
7. You will be asked to give access to ADB shell, do it.
8. That is all! Your phone is rooted.
Of course the app has ability to unroot.
Enjoy!
The tutorial isn't mine, I've just translated it. The original thread http://forum.android.com.pl/f764/kingo-czyli-prosty-sposa-b-na-zrobienie-roota-na-l9-382305/
very Good
Kingo: ROOT Status: YES, but...
Giancop92 said:
very Good
Click to expand...
Click to collapse
Kingo say that my LG L9 P760 is rooted but ES File Explorer don't let me overwrite gps.conf file in /system/etc.
tommyi said:
Kingo say that my LG L9 P760 is rooted but ES File Explorer don't let me overwrite gps.conf file in /system/etc.
Click to expand...
Click to collapse
install supersu from google play
Hello everybody
Is there anyway that i could control those other app's permissions ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want to prevent this app from knowing my network's informations due to its services wich is blocked in my country
Thanks
@Isam22
If you're on Android 6 or higher then you by means of ADB can revoke an app's specific permission: requires you a) know app's package name & b) the name of permission
Example:
Code:
adb devices
adb shell pm revoke <PACKAGE_NAME> android.permission.<NAME_OF_PERMISSION>
jwoegerbauer said:
@Isam22
If you're on Android 6 or higher then you by means of ADB can revoke an app's specific permission: requires you a) know app's package name & b) the name of permission
Example:
Code:
adb devices
adb shell pm revoke <PACKAGE_NAME> android.permission.<NAME_OF_PERMISSION>
Click to expand...
Click to collapse
Thanks man for answering
When i try to revoke the permission it tells me
Security exception: permission android.permission.ACCESS_NETWORK_STATE is not changeable permission type
Click to expand...
Click to collapse
What can i do ?
@Isam22
In Developer options turn on the USB debugging (Security settings) and Disable Permission Monitoring
jwoegerbauer said:
@Isam22
In Developer options turn on the USB debugging (Security settings) and Disable Permission Monitoring
Click to expand...
Click to collapse
I tried to but nothing happened
Is there another solution?
Thx again
You can try to remove app's permissions by means of APK Editor.
Google has made it easy to use ADB in Windows these days, but the ADB commands can only be used in a directory. This a Powershell script for Windows that will download the latest ADB from the Official repositories and install it System-wide or User-Wide, this script will also install latest Google drivers also from from the Official repositories. This script will help to install ADB and the drivers in an easy way. Most ADB installers come in exe format where you cannot see exactly what they do exactly. So I decided to write the whole thing as a Windows Poweshell script.
On my github page you can download the script and you can also find an explanation how to use the script. The big difference to others is that ADB & Fastboot drivers are updated in real time when this tool is used. For the drivers i have to update a link I'll do my best when a new driver comes out to update the link as soon as possible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
System-wide: ADB and Fastboot are installed to HOMEDRIVE\ADB directory, and added system-wide path.
HOMEDRIVE=C:\ so in case of the system-wide install option ADB will copy over to C:\ADB
Current user only: ADB and Fastboot are installed to UserProfile\ADB directory, and added path for current user. UserProfile=%SystemDrive%\Users{username} so in case of the Userwide-wide install option ADB will copy over to C:\Users\username\ADB
CMD or Powershell can use ADB and Fastboot from any directory.
If you are using this tool and you having problems leave a comment and I will try to help you
ķANKAN