Database Develop

Terminal Emulator??? Access "adb shell"???

how do i use the terminal emulator app to access adb shell?

adb shell is only used when you're on a computer, like when using android sdk tools. When you use the terminal emulator you use different commands try This Link for some help using the terminal emulator, they're basically the same as linux commands.
also this should be in the Q&A section

lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.

foil said:
lol the terminal is the 'shell'
if you're running a terminal right on the phone, then consider yourself already @root when you're typing in commands.
Click to expand...
Click to collapse
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
/ $ su
~ # |
Click to expand...
Click to collapse
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.

subcypher said:
Sort of. You are a user, but not "root". To become superuser you have to use the SU command.
I'm sorry if I'm nitpicking here. Your original point remains true. You don't have to use ADB at that point to run commands. You run the command without ADB right in the terminal.
Click to expand...
Click to collapse
No, you're fine. I was just assuming that he was already rooted, but you're right - it's a regular user account unless you change to superuser.

in order to do what you probably want you will have to type su. It should then ask for SU permission and then you should gey
Code:
#
.

hello everyone, idk if im in the wrong place, but im trying to connect my non rooted phone to my rooted tablet with terminal emulator.Is there a way for me to use adb because it worked with my previous phone...its not working and isn't showing any device when i input "adb devices"...Can anyone help me please, help would be greatly appreciated ?(btw usb debugging is enabled on my phone)

Root instructions...

Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe

Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.

Any reason to not use the one click method? Seems to be working

bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.

Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.

Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .

MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.

navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App

MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.

Just so everyone knows. SuperOneClick can root and unroot this phone ok.

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!

Thanks for posting this here for me Haxcid!
Sent from 1885

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App

Is there recovery for this now? Did I miss something?

stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.

Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.

stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?

make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools

Possible New Rooting Method!

Well, this is interesting.
On my Revo4g, all I did was enable USB debugging in internet only mode, and i'm faced with this:
Code:
c:\tools\android\android-sdk-windows\platform-tools>adb shell
# busybox whoami
busybox whoami
whoami: unknown uid 0
#
Looks like there's no need for rageagainstthecage, or any exploits. ADB is run as superuser already! (although for some reason ro.secure is set, and it seems to be ignored, so it possibly may be a bug)
EDIT: Nope, verified. Toggle ADB debugging on and off, and you're root!
This is most definitely not what LG intended, but hey- it works!
Still no signs of fastboot without accidentally erasing recovery or something. Looks like it's left in as emergency-only.
If you're not rooted, try this:
Open ADB shell
Your command prompt should be "$"
Run
Code:
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Congrats! You're root.. now you can push "su" and whatnot.
That was strangely easy...

thecubed said:
Well, this is interesting.
On my Revo4g, all I did was enable USB debugging in internet only mode, and i'm faced with this:
Code:
c:\tools\android\android-sdk-windows\platform-tools>adb shell
# busybox whoami
busybox whoami
whoami: unknown uid 0
#
Looks like there's no need for rageagainstthecage, or any exploits. ADB is run as superuser already! (although for some reason ro.secure is set, and it seems to be ignored, so it possibly may be a bug)
EDIT: Nope, verified. Toggle ADB debugging on and off, and you're root!
This is most definitely not what LG intended, but hey- it works!
Still no signs of fastboot without accidentally erasing recovery or something. Looks like it's left in as emergency-only.
If you're not rooted, try this:
Open ADB shell
Your command prompt should be "$"
Run
Code:
kill `busybox pidof adbd`
Re-run ADB shell, your command prompt should change to "#"
Congrats! You're root.. now you can push "su" and whatnot.
That was strangely easy...
Click to expand...
Click to collapse
OKAY... So, I don't need to do superoneclick? And I don't need to go through the painful process of downloading 3-4 programs?

markapowell said:
OKAY... So, I don't need to do superoneclick? And I don't need to go through the painful process of downloading 3-4 programs?
Click to expand...
Click to collapse
Well, if you've got ADB installed, then no you don't need superoneclick, but it's main claim to fame is that it's got all of the tools bundled together.
Stick with superoneclick until I get an easy method put together...

LOL... That's sweet!

Like I mentioned elsewhere... LG wants Verizon to think all is locked down and such but secretly behind its back it is giving us free candy. Like when grandpa and grandma hide money in your room before leaving...
They left in everything needed, we only had to put the pieces together.
Bravo LG bravo... now can we have the source code for this device for 2.2 and 2.3..

Now i'm for sure rooting today, as i already have adb installed. Epic.

So i ran ADB Shell and it automatically gave me "#". I then proceeded to "kill 'busybox pidof adbd' " and it said it did it. Still had "#". I don't seem to have root though. I can't delete bingsearch.apk, can't do anything in setcpu.
When i installed super user from the market, it did say there was an update, so it asked if i wanted to install it. I said yes, and it said an error occurred but it put a zip on my sd card to update the binary and that i need to reboot into recovery and install it.
Any ideas? I don't have cwm yet so i can't exactly do that. Here's how the whole thing went down:
Code:
C:\AndroidSDK\platform-tools>adb shell
*daemon not running. starting it now on port 5037 *
*daemon started successfully *
# kill 'busybox pidof adbd'
kill 'busybox pidof adbd'
[1] Terminated kill "busybox pidof adbd"
#

Nevermind, i just went with super one click and i have root now.

powder007 said:
I then proceeded to "kill 'busybox pidof adbd' " and it said it did it.
Click to expand...
Click to collapse
Those were back-ticks, like this: `` not single quotes: ' '
powder007 said:
I don't seem to have root though. I can't delete bingsearch.apk, can't do anything in setcpu.
Click to expand...
Click to collapse
setCPU will require superuser.apk and a working su. Did you mount the system partition r/w by hand before trying to delete bing? Using this method, you'd have to mount r/w, then push su, etc.

Ah, my bad. I'm semi new to adb. Thanks for pointing that out.
I had the super user app from the market. On root explorer it didn't give me a Mount r/w button, so i knew i wasn't rooted.

The problem with this rooting method is that it's incomplete.
My method gives you entry to a root shell-- it does not "root" your device.
A "rooted" device requires a file in /system/bin/ called "su", which allows normal Android apps to access root functionality on the device.
The method I detail allows you to manually remount /system as r/w and push the required file to the proper location without requiring an exploit.
Once I have some time free from working on the deodex'd rom, and porting CM7, I will make a super-super easy one click root application for windows/linux.
Until then, this thread is mostly for technical reference for devs, and something interesting that I found

[ROM][Lollipop 5.1.1] UnOfficial LineageOS for Otter2

Hi all,
Found my old Kindle Fire2 lying around so thought i'd have a go at building whatever I can for it. Seems like there was already source code in the repo's for CM 12.1 but nobody had built it. Well I've built it and it seems to work fine!
Only had to fix a script which had broken since CM 11 for wifi and all seems good.
NOTE RE MAC ADDRESS
FYI your MAC address will now get randomly generated at first boot. If keeping your existing MAC address is important, don't flash this.
I can't take any responsiblity for this, I've purely built it and fixed a couple of issues. Please thank whoever contributed to the source in the repo's.
I've only installed from a complete wipe. Don't try it unless you're prepared to wipe your device.
Enjoy...
ROM
cm-12.1-20170728-UNOFFICIAL-otter2.zip
Open Gapps pico for 5.1
http://opengapps.org/?download=true&arch=arm&api=5.1&variant=pico
Going to have a go at building CM13 next. Tried 14.1 but got hung up on selinux issues so going to take a step back to CM13.

Original link fixed

I need to fix the wifi script at boot. Currently if you install the rom you'll need to open a terminal and run:
/system/bin/fix-mac.sh
Wifi should start shortly after...

works perfect.
also perfect timing. i picked the otter2 yesterday from my dads house, who didnt use it anymore, because he switched to an galaxy tab long time ago.

I am currently having trouble with the Wi-Fi
It just hangs at Turning on Wi-Fi!
I have tried to clear cache and dalvik cache after installing gapps and lineage
I also performed a full wipe before flashing the rom
EDIT: Sorry didn't read further down

I am having an interesting problem with this ROM. It appears stable until I install any app, either from APK or play store. afterward everything force closes and will not work again until data is wiped or permissions repaired. when the permissions are repaired, any installed apps from APK or play store vanish like they were never installed. copying anything to /system/app works fine, but that is not a long term solution.

Raised a couple of threads about the wifi issue for a bit of help but nobody had replied. I'll have another look when I have time. Can't say i had any issues after installing app's though.

Think I might have fixed the selinux policy as i misread the neverallow rule and didn't realise it actually excludes sdcards from remount, so I can explicitly allow it.
Hopefully new fixed build to come soon.

Hi, I know a few people have asked about the Wi-Fi issue, but im not aware of how to open a terminal once everything is installed. the only terminal I can find is in the recovery mode but it wont find the file you mentioned

I just flashed and executed /system/bin/fix-mac.sh after installing "super su", but still WIFI does not start. Any additional hints? Thank you very much for the efforts.

Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"

guys do you have the latest twrp for kf2? all links are dead on other threads.

Apologies if this is obvious - but how did you install the latest SuperSU without Wi-Fi? Is it a case of downloading the apk and transferring via adb?
Is the build working otherwise? The old CM one is beyond repair - works for a couple days and then gets itself into boot loop.
Thanks!
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse

---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
androidbenutzer said:
Found a working solution:
1. Activate terminal in settings
2. Install latest SuperSU
3. Open terminal and execute "su 0 setenforce 0"
4. Execute "/system/bin/fix-mac.sh" afterwards
--> WIFI should start and "stay alive"
Click to expand...
Click to collapse
not work:crying:

rapmen said:
---------- Post added at 09:30 AM ---------- Previous post was at 09:21 AM ----------
[/COLOR]
not work:crying:
Click to expand...
Click to collapse
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...

nebula_rider said:
Same here... all steps ok, but Wi-Fi still won't turn on. Heart-breaking! Build working fine otherwise...
Click to expand...
Click to collapse
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!

androidbenutzer said:
I bricked my Otter2 today, so I had to restart all over:
1. Flash the Android-Image in TWRP
2. Flash the GAPPS-Pico-Image in TWRP
3. Flash the SuperSU-Image in TWRP
4. Allow the Terminal in the Android developer settings
5. Open the terminal and execute "su 0 setenforce 0"
6. Allow "root" in the appearing popup.
7. Execute "/system/bin/fix-mac.sh"
8. Activate WIFI
9. Done
This works!
Click to expand...
Click to collapse
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!

nebula_rider said:
Ok so I gave this another go - thanks for the encouragement androidbenutzer! - and can confirm that it does, indeed, work!
My problem was with step number 7. This is going to sound so so lame, but I was just typing "system/bin/fix-mac/sh" on Terminal (without the quotes). It looked like Android was trying to run fix-mac.sh, but failing to mount something. For the fellow rookies out there, you first need to navigate to /system/bin. I'm sure there's a very simple way to do this, but since I know no better, this is how I did it:
cd\
cd system
cd bin
THEN type "fix-mac.sh" (without the quotes).
Wi-Fi switched on and remained on.
Thanks dom_b and androidbenutzer! So glad to have the wee otter2 up and running again!
Click to expand...
Click to collapse
I tried all the steps, and still no luck.

pakidermo5000 said:
I tried all the steps, and still no luck.
Click to expand...
Click to collapse
Actually you wouldn't get too far even if you could turn the wi-fi on. The build is plagued with the "Trebuchet has stopped" error, which apparently is common in CM. I tried every fix recommended online, without success.

I didn't read the entire thread but here's a super easy way to fix the wifi issue. Connect a USB cable from the Otter2 to your computer. Make sure you have adb installed. Open a command prompt and type:
adb.exe /devices
Now look at the security message on the tablet. Click yes
adb.exe shell
At the shell prompt, type the following:
[email protected]:/ # /system/bin/fix-mac.sh
---------- Post added at 02:42 PM ---------- Previous post was at 02:05 PM ----------
SuperSu is here:
http://rootmygalaxy.net/download-latest-supersu-v2-82/

Freedom OS - "adb root" returns "cannot run as root in production build"

Freedom OS - "adb root" returns "cannot run as root in production build"
Hi! How can I run ADB as root? I'm on FreedomOS. I've tried flashing ElementalX Kernel, but it didn't fix this.
Apparently I need ro.secure = 0 and ro.debuggable = 1. How can I set this? Could someone upload a modified boot.img with those set?
Or, the main problem, could someone run the pull_library.sh script on their 3T that can be downloaded from here: https://github.com/OnePlusOSS/android/blob/oneplus3/6.0.1/pull_library.sh
It won't pull some of the files.
Thanks!

Is "adb root" different from typing:
adb shell
su
You also need to have adb root access enabled in Magisk Manager or SuperSU app.

redpoint73 said:
Is "adb root" different from typing:
adb shell
su
You also need to have adb root access enabled in Magisk Manager or SuperSU app.
Click to expand...
Click to collapse
That's the thing, I can do adb shell and su properly, I get a su prompt and I'm good. But even with that I can't pull certain system files, remount system rw, or edit certain system files.
I need ADB to run as root for that, and there is a difference. ADB shell and su just allows me to run device commands and stuff as root (like terminal app on Android) but ADB root lets me use ADB commands as root like what I mentioned above.
There's apparently two solutions. One, a modified adbd binary that doesn't check for ro.debuggable (which I can't find) or have a kernel that sets ro.debuggable to 1 in default.prop. Or I need a userdebug or engineering build of Freedom OS based off of OxygenOS.
I can't find any of those, and my decompiled stock kernels don't boot the phone properly.
Or, I could get around all this if someone would be able to upload the files I don't have from their device.
Also, where do I set ADB root access in Magisk?
Sorry for the wall of text haha,.just lots going on

NateDev said:
Also, where do I set ADB root access in Magisk?
Click to expand...
Click to collapse
In Magisk Manager, open the 3-line menu icon (top left corner), go to Settings, and you will see under the Superuser heading, the toggle for "Superuser Access" (Apps only, Apps and ADB, etc.).
NateDev said:
Sorry for the wall of text haha,.just lots going on
Click to expand...
Click to collapse
No apology needed. Thanks for the clarification. I don't use adb often. On this device, not even once, I don't think.

redpoint73 said:
In Magisk Manager, open the 3-line menu icon (top left corner), go to Settings, and you will see under the Superuser heading, the toggle for "Superuser Access" (Apps only, Apps and ADB, etc.).
No apology needed. Thanks for the clarification. I don't use adb often. On this device, not even once, I don't think.
Click to expand...
Click to collapse
Ok, thanks, I'll try that when I get home and see if it works

NateDev said:
Hi! How can I run ADB as root? I'm on FreedomOS. I've tried flashing ElementalX Kernel, but it didn't fix this.
Apparently I need ro.secure = 0 and ro.debuggable = 1. How can I set this? Could someone upload a modified boot.img with those set?
Or, the main problem, could someone run the pull_library.sh script on their 3T that can be downloaded from here: https://github.com/OnePlusOSS/android/blob/oneplus3/6.0.1/pull_library.sh
It won't pull some of the files.
Thanks!
Click to expand...
Click to collapse
If all you need to do is set ro.debuggable and ro.secure you might be able to use Magisk's resetprop tool to set them on the fly.
Code:
resetprop ro.debuggable 1
resetprop ro.secure 0

Didgeridoohan said:
If all you need to do is set ro.debuggable and ro.secure you might be able to use Magisk's resetprop tool to set them on the fly.
Code:
resetprop ro.debuggable 1
resetprop ro.secure 0
Click to expand...
Click to collapse
Thanks, so I opened up ADB, and ran
Code:
adb shell resetprop ro.debuggable 1
but it tells me "resetprop: Initialize error". I've just assumed tho that resetprop is included when you install Magisk. If it's not, how can I install it? I also tried running "resetprop" in Termux on my phone, but it says resetprop can't be found.
Thanks

NateDev said:
Thanks, so I opened up ADB, and ran
Code:
adb shell resetprop ro.debuggable 1
but it tells me "resetprop: Initialize error". I've just assumed tho that resetprop is included when you install Magisk. If it's not, how can I install it?
Thanks
Click to expand...
Click to collapse
It needs su...

Didgeridoohan said:
If all you need to do is set ro.debuggable and ro.secure you might be able to use Magisk's resetprop tool to set them on the fly.
Code:
resetprop ro.debuggable 1
resetprop ro.secure 0
Click to expand...
Click to collapse
Didgeridoohan said:
It needs su...
Click to expand...
Click to collapse
Sorry, forgot to mention, I tried it with su in adb shell as well, changed to #, but still gives same error...
Nevermind, a reboot of the phone fixed it. Unfortunatly I still get cannot run in production builds, even when the 2 items are set to the proper values. This guide: https://forum.xda-developers.com/showthread.php?t=1794203 says it should work with those 2 set, but for some reason it doesn't. Time to find a new solution...

NateDev said:
Sorry, forgot to mention, I tried it with su in adb shell as well, changed to #, but still gives same error...
Click to expand...
Click to collapse
Hm... Works fine running it in a terminal emulator (I just tested).