Hey everybody,
I am looking around on my LG with adb and found that I cannot run root in production builds and not allowed to change verity settings because of a User build. I was wondering if anyone has had luck with changing these two settings?
I used adb disable-verity and adb root.
Thanks!
Related
I want to push a couple scripts down android devices - as an IT Administrator, I am using Zenprise at work and can push down scripts to devices there. I want to push down a script that will enable unknown sources if not enabled already. And I would like to push another script to activate the GPS if it is not turned on already.
And do this on non-rooted phones......
I know this sounds like Im trying to mess with users, I'm not, Im just trying to streamline the config for the endusers.
Can anyone give me some help here?
bump? anyone ?
its possible but i dont know how to write a script for that.....google????? good luck
aal1 said:
I want to push a couple scripts down android devices - as an IT Administrator, I am using Zenprise at work and can push down scripts to devices there. I want to push down a script that will enable unknown sources if not enabled already. And I would like to push another script to activate the GPS if it is not turned on already.
And do this on non-rooted phones......
I know this sounds like Im trying to mess with users, I'm not, Im just trying to streamline the config for the endusers.
Can anyone give me some help here?
Click to expand...
Click to collapse
I would tackle this by running the getprop command before and after setting that option and seeing what the differences are. But to change these settings you are going to have to use the setprop command, which requires root. You might be able to do it with the default.prop file, but I think that is only read in at first setup.
Hello,
with my old Nexus S i used to access adb at the very start of the booting process.
Now with my Galaxy Nexus i have to wait the boot to complete to access it.
I've tried editing default.prop, init.rc and init.tuna.usb.rc with no luck.
Anyone knows if it's possible or it's the mtp that prevent adb to be used earlier?
Thanks.
Also noticed that with persist.sys.usb.config=mtp,adb can't run adb as root while with persist.sys.usb.config=mtp it works, but still after boot is complete. Weird.
bump
have you looked in roms git repos?
Sent from my i9250
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
mkhopper said:
So, by going into the settings menu of the FTV and toggling the ADB Debug flag, this allows for installing via a push from ADB.
The text that is displayed when changing this value also says that by enabling the setting, it allows for package installs from unknown sources.
Is this not quite the case though?
Using ES File Manager, when selecting an apk package located in the downloads folder on the device, the message shown in the attached screenshot appears.
Since there's no way to do so from the front-end, I am assuming that we will need root to change the flag to truly allow installing from any source?
Any possible way to do this without root?
Click to expand...
Click to collapse
Yeah, this isn't currently possible for the public. There is a root exploit(s) already developed but they have not been released yet. The developer, jcase, said he will release an exploit on the same day the upcoming Fire TV update is pushed (the exploit will not be compatible with the update so if you want it you'll need to follow the instructions in the other thread for blocking OTA updates).
mkhopper said:
Any possible way to do this without root?
Click to expand...
Click to collapse
Are you having issues with ADB? We can probably help you get those resolved.
Chahk said:
Are you having issues with ADB? We can probably help you get those resolved.
Click to expand...
Click to collapse
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
Not at this time. Amazon disabled side-loading of APKs from the device itself. Root would be the only way to get around that.
mkhopper said:
Thanks, but no. I use the automatic tool to push packages with no problems. I was just looking for other methods of package installation that could be done directly while on the FTV.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2715315
Sent from my MZ617 using XDA Premium 4 mobile app
Kramar111 said:
http://forum.xda-developers.com/showthread.php?t=2715315
Click to expand...
Click to collapse
several days ago it occurred to me to alternatively use sshd for terminal access, because:
-a) I feel a little unsafe leaving adb wifi enabled all the time (ok it's only a small thing to turn it on and off, but still) - and for security reasons there is no way to enable/disable it programmatically e.g. from a script/shell/terminal/app (well theoretically this is not exactly true, but practically it is)
-2) some people (i.e. me) would like to do shell/terminal remotely sometimes, rather than on the AFTV (and other people don't have/want a keyboard)
ssh access makes a great alternative to Term.apk, but the problem is:
- Term.apk and/or (pick your favorite android ssh server) don't have permission to run e.g. "pm install foo.apk" - it will fail. (btw 'pm' is a great command, take a look sometime at all the options. it shares a lot of functions as the adb command itself. 'am' is another fun command...)
- so, the hilarious workaround of enabling adb wifi, "adb connect", and then finally "adb shell" or "adb install" etc., is still required. (b/c the adb user is in the 'shell' group, among others - giving it permission to run /system/bin/pm) - oh well.
for random reference:
Code:
127|[email protected]:/ $ id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
[email protected]:/ $ exit
[email protected]:/ $ id
uid=10009(app_9) gid=10009(app_9) groups=1015(sdcard_rw),1028,3003(inet),50009(app_40009)
(also note it appears the adb shell user might possibly have 'mount' abilities, but since the /dev/block/sd* nodes permissions' are really locked up, who knows...)
Hello,
There is only one thing I want root for - to enable the modification suggested here http://forum.xda-developers.com/nexus-5x/help/miracast-t3232833 to enable miracast.
Is there a way to obtain root without any custom recovery or flashing anything? Like in some way use adb to simply modify the build.prop file on the device?
Thank you for your thoughts.
schwarznavy said:
Hello,
There is only one thing I want root for - to enable the modification suggested here http://forum.xda-developers.com/nexus-5x/help/miracast-t3232833 to enable miracast.
Is there a way to obtain root without any custom recovery or flashing anything? Like in some way use adb to simply modify the build.prop file on the device?
Thank you for your thoughts.
Click to expand...
Click to collapse
You're on the right track!
You absolutely can edit the build.prop by using ADB. Just google how and you do not need root in order to edit build.prop. I've done it with my work phone to change the density.
Hi There. Thanks for replying. I see that the concept is pretty simple -- use adb to pull the build.prop file, edit it, and then use adb to push the build.prop file back.
This page has an example: https://www.quora.com/How-do-I-edit-the-build-prop-file-in-Android-without-Rooting-it
What I can't figure out is how to actually push the file back without rooting. I think I have to mount the system partition in read/write. To do that I think I need root. I try running adb as root, to then mount the partition, but I get "adbd cannot run as root in production builds." Any suggestions on how to get around that?
SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?
atulclassic said:
SInce google has released separate ADB and fastboot binaries now, i was just exploring the commands available in adb.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
I came to know that adb has a command 'adb disable-verity' and 'adb enable-verity'.
Did anyone tried this yet? How this works? Will it decrypt the device?
Click to expand...
Click to collapse
It should not work on stock OOS as it is not a userdebug build.
MisterCoolBeans said:
It should not work on stock OOS as it is not a userdebug build.
Click to expand...
Click to collapse
but we can change it to userdebug build by modifying the build.prop
atulclassic said:
but we can change it to userdebug build by modifying the build.prop
Click to expand...
Click to collapse
You can try but I believe it won't work.
Our build prop has "ro.build.type=user", Did some searching and found several mods that required changing
"ro.build.type=user" to
"ro.build.type=userdebug"
Go ahead and try it and let us know if it works.