I'm running CM 7 on my phone, which obviously comes rooted. When I open up a terminal on the phone, I have to "su" to escalate to having root privileges. This means that the phone will ask if its OK first.
But, when you run an ADB shell when the phone is in debug mode, it goes straight to giving root access.
Is there any way to have ADB start underprivileged, so you have to run "su" to gain root access?
Advantages would be when you forget to turn off debugging mode and your phone gets stolen. A thief would have a much harder time stealing any of your information or re-flashing your phone.
Related
I have a phone that came pre-installed with su, busybox and superuser; but the permissions are not set correctly for the user to access su and get root. The phone is running Android 1.6 and when you connect it to a computer in debug mode it is not recognized as an Android device; even though the phone says it is plugged into a computer and in debug mode. The only thing that comes up is the drive to access the SD card. My question is thus: Is there any way to change the permissions of su on the device itself? I have tried running a terminal emulator but when I type "su" the result is permission denied. Since I don't have permissions I cannot do a chmod on the device itself. If anyone knows a method I can do this I would appreciate it very much.
I am trying to root my droid and i am getting stuck at this point
here is the time line of events
1. rooted successfully via easy root a really long time ago
2. after an ota update i receive an error when i attempt to reflash the phone or back up the rom anything that requires super user permissions fails saying "permission denied"
here i am now haha
After running RATC, you're not getting root UID (0), and you're staying in adb shell, so it's normal that adb devices command isn't working.
However, the real problem I see here is that RATC isn't working. Are you sure that you're using correct exploit - is RATC working on your FW version? Maybe you have to use psneuter...
sorry could you possibly put that in layman's terms im some what technical but im some what new to android stuff
UPDATE: nvm the above how do i figure the FW version ive looked in the about section of the phone but it doesnt seem to be there whats the best way to obtain the FW version?
I don't own Droid but same principles more or less should be same for all Android phones. So, to simplify it:
Basically, when you execute RATC (rage_against_the_cage) exploit, adb shell should disconnect and you should be thrown back to Windows' CMD prompt and adb shell should get root permissions. But in your case this isn't happening, adb doesn't restart and RATC isn't working.
Can you try with SuperOneClick v.1.6.3?
i was looking at that ill go ahead and try that
still a no go i attached some screen shots
Which Android version have you got? 1.6 or 2.1? Try with psneuter exploit.
i rooted with unRevocked3, on htc. very easy!!!!
I have a Japanese Sharp 005SH Android phone. Currently, the phone had been locked up at the start screen due to the phone being out of network service for a long time.
I have rooted the phone before, and have SuperUser installed.
Currently, I am trying to get rid of the screen-lock service by the publisher by using the command "adb shell am start -a android.intent.action.DELETE -d jp.co.sharp.android.secure.StrongBox"
The problem now is. whenever I enter adb shell, the prompt is $ sign. When I type "su", nothing happens, and the cursor just blinks. I guess that this means the SuperUser app on the android phone has come out with a prompt which I need to touch to grant access. However, this is not possible as the screen is locked by the aforementioned publisher service.
Question
1. Is it possible to gain root access through ADB with the device screen locked?
2. Is it possible to remove the publisher's service without root access (and with the screen locked)?
Thank you for your time in reading this post.
Warmest Regards
If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
LordFME said:
If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
https://play.google.com/store/apps/details?id=fme.adb
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
Click to expand...
Click to collapse
This is useful. Thanks :good:
Glad you like it
No need for multiple threads on same topic,
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
I'll close this one.
Darth
Forum Moderator
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.