Hi there
I fiddle largely with MTK based phones and when I tweak a phone, I normally only need ADB root access. So my general process has been to:
1. OEM Unlock the device
2. unpack the boot.img and change the default.prop values (ro.adb.secure etc) to allow ADB root access.
3. Use ADB to get temporary write access using adb Root, then ADB remount Rw. Then you can pull and push files.
However I have an MT8735b, Android 7.0, Alps based device that will simply not give me ADB root access. so when I run "adb remount rw" or any of the equivalent shell scripts you can use instead, it just won't give me write access.
So I heard that newer phones based on these chipsets and also ones like 6737M are locking the device up in other ways.
My question is, does anyone have any ideas or knows anything I could try to get root access?
Any help is much appreciated.
Related
I've followed the following thread CF-root 4.1.
Everything went fine and the kernel is rooted.
I can use apps which require root, like TitaniumBackup.
I also can use su to gain root privileges and also adb shell and then su. To make this more clear. I first get $ (user priv) and then with "su" i get # (root priv).
For this reason i can't use the adb push method, because i'm not root directly.
adb root which is suggested in a couple of threads isn't helping me. I get the following output. "adbd cannot run as root in production builds".
How can i fix it, so i can have root privileges directly when connecting via the adb shell?
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
bla
HellcatDroid said:
You need an "insecure kernel" for that.
There are several for download in a thread in the dev section.
Why do you need ADB to be running as root for pushing, if you don't mind asking?
Click to expand...
Click to collapse
Many thanks for illuminating people in this situation!
Cuz it's obviously more comfortable to do stuff using the computer's keyboard.
Now my phone is rooted, engineering boot ROM, with Cyanogenmod installed.
I'm wondering from a security standpoint, if someone happens to take my phone, and I happen to forget to disable USB Debugging, how can I make it harder to use ADB to reformat the phone?
By default, an ADB shell gives root access to the phone. How can you set the ADB shell to default to an unprivileged user that will have to 'su' in order to gain root access?
matkam said:
I'm wondering from a security standpoint, [...] How can you set the ADB shell to default to an unprivileged user that will have to 'su' in order to gain root access?
Click to expand...
Click to collapse
I'd really like to know this, too. :b
Dear Sirs/Madams,
I'm new to Android development and I'm writing my very first Android apps but recently I have encounter the below problem:
I want to call reboot command in non-rooted phone but as you know, reboot command needs root permission.
I want my app to run in both rooted and non-rooted phones. For rooted phones there is no problem.
However for non-rooted phones, I am trying to find a way to restart it without root permission.
I have been thinking of calling shell command in non-rooted phones (E.g, adb shell reboot), but I don't know how to put the script file
to an apk file and excecute the script within java code.
Therefore I'd like to ask for your help to solve this problem.
Thank you very much
Hi,
I'm new here afterwards I use this forum a lot of times before but its the first time I'm writting because i don't find too much information about my problem:
I have a mt6735 device with Android 5.1 unrooted, bootloader locked and a factory ROM. I know, I know... maybe you think I'm mad because I have a not rooted Android, but I can explain:
I need the phone unrooted because I use some apps which dont work propertly if the device its rooted. Furthemore I need to pass Basic integrity of SAFETYNET check.
Everything its ok but SELinux its in permissive mode by default (and f**k SAFETYNET check), and I need root access to change it. I'd it with ADB with engineer mode and enabling User2root witch give me access to root shell and the command setenforce 1. But the other day the device restarted itself and SELinux become permissive again... I needed to get access a PC install drivers again and use ADB to change it again but it isn't always an option (For example in the middle of a trip) I tried to change permissions of enforce file, but that only work before restart...
I see many solutions witch require to modify and flash boot.img but I prefer to avoid that.
My questions are the following:
1.- Its posible to change default SELinux mode? Or change permissions of the enforce file so I'll can use setenforce command without root from terminal?
2.- Its posible to run terminal (or a comand on terminal) with root privileges with user2root? It seems to be not possible, but if anyone can confirm it...
3.- Its posible to run ADB Shell locally (Without loosing configuration when device restart) to run comands like root as I do on the PC?
4.- Its posible to achieve this without flashing or using SuperSu? Maybe I ask for the imposible
Many thanks to everyone
First I have googled until my fingers bled knowing the answer is out there and apologize in advance if it has been covered in these forums elsewhere.
I have an android appliance running 4.3, I have root access via adb shell. What I want to do is grant root access to the standard users so I have root access using telnet. This is NOT a phone, it will NOT be on the internet so I do not need to worry about root being open to the world. I just need to be able to shell into it and be able to run any command needed via the normal user in telnet. Changing the user permissions seems like an easy way but all linux style sudo and user commands fail (it's a very cut down install in this machine).
Any help would be appreciated,
J
Bump, Anyone?