[Tutorial] Testing for true root

[aus9]

Hi
Try at own risk, but I suspect it should be safe enough.

#########
CREDITS
#########
vampirefo for his helpful explanation of true root and test as supplied in replies now embedded in the Windows section and updated Linux script.

WHAT IS TRUE ROOT ANYHOW?
A lot of buyers of Chinese, Indian, Korean phones from various resellers are told their phone is rooted. But that can mean just the su executable is installed and the maker of the ROM has not tested all functions.

So true root means amongst other things
1) That you have the su executable installed
2) that your Android system is in read write mode
3) That this condition persists over a reboot

Otherwise, you need a script to re-enable rw status
or,
an app that can defeat your secure mode kernel
_____________________

Please Note I may change, tinker or otherwise edit this post to keep it the most recent version. Pls check the edit date/time and you may need to re-read?
##############
ANDROID ONLY
##############

Pls install the following 2 apps which are: an Android Terminal and busybox
[Only registered and activated users can see links Click here to register]

I have changed my recommendation as first busybox offers normal or recovery mode install
[Only registered and activated users can see links Click here to register]

I used to use this one but YMMV
[Only registered and activated users can see links Click here to register]

For me to bypass my secure mode ROM I needed to install and enable this app.......YMMV
adbd insecure
[Only registered and activated users can see links Click here to register]

2) Open the terminal and issue the commands

Code:

su
id
mount | busybox grep /system

if command not found then you have no super user apk installed and need to root your phone. This TUT assumes you have su installed so skip the rest if you don't have it pls.

Next within Android look at your prompt......the stuff before the # symbol
I believe it must be root@something as per image. I have a bad image in a reply below as well.


Notice the id result must be as per image

If your image differs, I suggest you install a new su app from playstore called SuperSU by CHAINFIRE
once enabled you can delete your old app. Then do a full reboot please and recheck true root from the beginning.
[Only registered and activated users can see links Click here to register]

But be aware that playstore will not show any updates in the notification area for any "rooted" app. So you need to click on it within playstore to see if an update is available.......and to update it.....later on.....you need CWM or TWRP or similar tool installed.

You might also consider flashing via adb but I have not tested that.

The THIRD command is a check that busybox is working and shows an output that includes a status of your /system as either ro or rw
read only is occurs often on devices that have a secure mode as discussed by vampirefo below
read write means you are more likely to pass all other true root tests

3) You can try within Android to make your system go from ro to rw if you like?

Code:

su
mount -o remount,rw /system
mount | busybox grep /system

As thats a lot of typing if you ever reboot or shutdown your phone, I will test a downloadable script later


########
Linux
########

I have an udev system and use adb as a local user (non-root)
this requires a relaxed permission in the udev rule as showing for most
devices here....grab the raw file from here
[Only registered and activated users can see links Click here to register]

Use a text editor to change to perm 666 instead of 660

If you intend to redistribute his udev rule pls incorporate the License as per
[Only registered and activated users can see links Click here to register]

but that does not yet know about my iOcean so my rule is here

SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="666", GROUP="plugdev"

and to reload the udev rules you follow this instruction for a systemd system
[Only registered and activated users can see links Click here to register]
or if that fails use

Code:

sudo udevadm control --reload-rules

Script is here
Now version d
[Only registered and activated users can see links Click here to register]

##########
Windows
##########

USB window driver associated with Android
adb installed and running as Adminstrator

commands and explanation to follow

I have no Windows to test this on

change Directory into where you have the adb tools unpacked
Next we start the server off with a full restart

Code:

adb kill-server
adb start-server
adb devices -l

Thanks to vampirefo we have another test for true root

Code:

adb shell id

You must see something like this

Code:

uid=0(root) gid=0(root)

You must be able to see the serial number of your device to continue. If there is a question mark in the serial number, you are not running as Admin,

Next we test to see if you already have system in read write mode.

Code:

adb shell su -c "mount | busybox grep /system"

(above line has been editted as busybox is easier to type that /system/xbin

3 things will happen here
1) You get permission denied because you are not truly rooted. For most that means installing the abdb insecure app which worked for me
2) status shows as ro
3) status shows as rw

If (1) meant you downloaded and enabled the app, you repeat above command
If (3) skip the next bit
For (2) users only we attempt to mount as rw------and recheck for rw status

Code:

adb shell su -c "mount -o remount,rw /system"
adb shell su -c "mount | busybox grep /system"

If you got OK to here, we now discuss the owner and group rw permissions.

In this context * means r or w or x or -
For true root we need rw* rw* ***

But how to test?
In your folder/Directory place a text file you create with the following contents
cats
name the file aus9.txt
The file size you can see in properties.......I am guessing its about the same as Linux which is 5 bytes

We then copy into Android system and recheck its owner group permissions and size.
My faulty device transferred it with only owner perms......so its a good test to do pls

Here is my suggested command

Code:

adb push aus9.txt  /system/aus9.txt
adb shell su -c "ls -al /system/aus9.txt  "

You are now checking that the size you can see in Windows was the full amount of the transfer into Android PLUS
that owner and group are root root PLUS
perms are minimum of rw* rw* ***

When finished with this test we can clean up the Android with

Code:

adb shell su -c "rm /system/aus9.txt"
adb kill-server

Optional, delete that file from your Windows folder

good luck

TODO

Can some kind Windows soul confirm you need usb driver correctly installed before you can use adb?

Hint, if you can't get it working you may prefer to use Linux?

[vampirefo]

True root is gained only from unsecure boot.img, secondary root is gained by suiding su binary either by direct command or via installing a su app.

secure boot.img only secondary root can be gained.

Code:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4

not secure boot.img true root or 100% root.

Code:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=1
persist.service.adb.enable=1
persist.sys.usb.config=mass_storage,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4

[aus9]

vampirefo

Are you suggesting that my gapp abdb insecure is not gaining true root?

[vampirefo]

vampirefo

Are you suggesting that my gapp abdb insecure is not gaining true root?

You can only gain secondary root unless you modify boot.img, or if your boot.img is already unsecure.


Quick test for root?

Code:

adb shell id

my output

Code:

adb shell id
uid=0(root) gid=0(root)

post yours

[aus9]

Thanks you are too quick for me
reference
[Only registered and activated users can see links Click here to register]

Code:

gordon@box:/a/1ANDROID/9build/1root-tests$ adb shell id
uid=0(root) gid=0(root)

disable abdb insecure and retest

Code:

adb kill-server
gordon@box:/a/1ANDROID/9build/1root-tests$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
gordon@box:/a/1ANDROID/9build/1root-tests$ adb shell id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),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)

I believe I can now say
abdb insecure is a confirmed app that will give true root to most devices if needed

EDIT

I will update my first post to include this info thanks.....all credit to you of course

---

Ok I feel this is as far as I need to go to be anal on root checking

If any kind Windows user can see if it works or not, feel free to comment

[aus9]

EDIT

Ok I think I have found one more test this is internal to Android

First attached image is the old FALSE root as discussed next

I just updated the su apk thru gapp......opened a terminal and ran su command and prompt has finally changed to root@"myphonename"

second attached image is proof su APK is now working correctly

The other tests still need to be done as your stock ROM may come as ro etc

---

[aus9]

51-android-rules has been updated to
[Only registered and activated users can see links Click here to register]

I rec'd a reply from upstream maintainer.....he is now using usbids and has not accepted my iOcean usbid as its already reported
---but reported as a HTC device by make and by model as a fairphone

0bb4:0c03



2) Ok last tests for Sunday

I turned off abdb insecure and found my device was not true rooted after a full reboot so my updated su was not enough.

test (2) enabled that insecure app and also ticked another box for it to be enabled over reboot
full reboot......retest......fails

In checking the app again......I found that its gone back to disabled

this is a puzzlement

I imagine most people do not reboot their phones but leave them permanently
---but I am trying to work out what is funny.....about my phone

Its possible I should offer feedback to that developer, but I am mentioning it here
a) as a way of making online notes what I tested.....something I failed to do in the past
b) to let other users know it is not all smooth sailing.
----meaning its a lot trickier than it looks.

cheers

[vampirefo]

Yes a lot of phones will show up as HTC (High Tech Computer Corp.), I didn't know a github existed for 51-android rules, I always make my own 51-android rules, but nice to know someone out there is collecting android ID's and maintaining a list of such devices.

[aus9]

a quick word on the superuser app

If your stock ROM came from China and has a su app, it is unlikely to update thru google apps

I suggest you install SuperSU made by CHAINFIRE

Once it is installed you can delete the existing su app

2) But playstore will not inform you when SuperSU updates.
Instead, once every so often, click on it...in playstore and it will display if update is available

3) You need CWM or TWRP or other recovery design to update this app.

Thats how I fixed my prompt in above images

good luck

EDIT
(4) I will be testing a change in my grep command....as when you do it in Android it takes too long to use the standard keyboard with my old line of

Code:

su
mount | /system/xbin/grep /system

to

Code:

su
mount | busybox grep /system

test complete------Linux script now version c.....Windows howto updated

[bryfly]

managed to find my way across to your thread about true root, have read through it and I think that this might be beyond me as I do not really understand what to do, thanks for your help so far though.....