[Tutorial] Testing for true root

[aus9]

okey dokey....thats a relief we did not delete it

now what about that Chinese app in /system/app?

[bryfly]

okey dokey....thats a relief we did not delete it

now what about that Chinese app in /system/app?

No Chinese app in there that relates to su, unless it is hidden under another name

[aus9]

1)
Full reboot pls then
Lets try some true root tests only in Android please....open a terminal and run

Code:

su
id

To be anal....is your reply a similar response as per my photo in post 1?
If not is it to the same response as my quote box post 11?

Otherwise if you have time....a photo pls

2) Next as I don't know what your reply might be.....lets hope we get a nice response?
The next command you will see a response that will either show ro or rw on the next line in the terminal
ro=read only
rw=read write

Code:

mount | busybox grep /system

if you see ro then issue an attempt to change to rw as follows

Code:

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

You notice we repeated our earlier command to check the status

3) If you could not change to rw status.....with the new superuser app then I suspect you have a secure mode
kernel and need to install the app called adbd insecure from playstore

It will cost some money.....you download then install it
then run it.....and tick the box to enable it

repeat the tests

if the tests fail.......you can uninstall it.....and get a refund....no need to email developer its automatic

BTW this app is what I needed so I have tested it a fair bit

good luck

[bryfly]

1)
Full reboot pls then
Lets try some true root tests only in Android please....open a terminal and run

Code:

su
id

To be anal....is your reply a similar response as per my photo in post 1?
If not is it to the same response as my quote box post 11?
Otherwise if you have time....a photo pls
2) Next as I don't know what your reply might be.....lets hope we get a nice response?
The next command you will see a response that will either show ro or rw on the next line in the terminal
ro=read only
rw=read write

Code:

mount | busybox grep /system

if you see ro then issue an attempt to change to rw as follows

Code:

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

You notice we repeated our earlier command to check the status

3) If you could not change to rw status.....with the new superuser app then I suspect you have a secure mode
kernel and need to install the app called adbd insecure from playstore

It will cost some money.....you download then install it
then run it.....and tick the box to enable it
repeat the tests
if the tests fail.......you can uninstall it.....and get a refund....no need to email developer its automatic

BTW this app is what I needed so I have tested it a fair bit
good luck

done that, 2 screen shots att:- where it says busybox not found, for whatever reason it uninstalls itself , re-installed and re ran commands

edit. the third image is after I installed adbd insecure , shows different to the first image where it said it had root....

[aus9]

Hi

EDIT

EEK I may have misread your chat about busybox.

Did you have to download busybox or are you relying on what you saw in the terminal?

If in the terminal.......its because the command syntax was wrong.....busybox app still there and so no problem

Can you confirm what you meant by

for whatever reason it uninstalls itself , re-installed and re ran commands

#############################
Only if it was uninstalled read on
##########################
I put a different recovery image on and managed to get a nice bork so I could show you how to install it the way you have yet to try

Now your first image looks good
second image is bad....for extra reason
---There is no gap between / and system please
(2) loss of busybox is a concern

3) Therefore I urge you to consider redoing the running of supersu as per images

open app and you get first image....it says needs update and I had previously had it update but started again


leads to


then onto


finally it reboots my phone into recovery mode and I just caught the update occurring


that last image is tough to read.....it says PROCESSING

####################

Now another of doing it properly is as per image....you can boot into recovery mode.....MANUALLY
but you need a zip file to flash/unpack

its here
[Only registered and activated users can see links Click here to register]

size of download is about 700 kilobytes

###################

but I am not sure if you have ever used the recovery mode before?
There is always a first time.

PS a rooting tool called Framaroot can re-root your phone if we stray from the golden path

good luck

So let me know which way you want to play it.
I would like you do it this way.....as that is the way I did it.

I know you baulked when you saw a message about CWM and normal but normal means with /system currently booted while some things can occur when the Android file system is not active.....ok?

###############

Assuming you trust me and go ahead then repeat the tests we discussed and also I want you to do a full reboot before starting the tests and check that busybox is installed.

I give busybox---root permission all the time....not sure if you grant it 15 minutes etc------when I input
su

[bryfly]

right.... installed super su via cwm, then told su to update via cwm it reboot in to cwm where i was faced with a choice of select factory recovery yes / no went for no, also whenever my phone reboots I lose root, this in turn means I lose busybox so every reboot I have to reinstall root and busybox, will re try your tests in a minute........

EDIT:- su then id , gives same img as img 3, in my post above..

I do not understand in img one in my post above it seems to say I have root so not sure why it is saying no root now.

EDIT 2
Right now have root back and carried out some of your instruction , see image for result

[aus9]

ok we just have to be careful with hitting the space bar.

the first, second and last lines ....in terms of input are all good
the second last line failed = third line as we have a gap

try

Code:

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

that pesky third line is
mount space hypen o space remount comma rw space /system....with luck

2) reboot and lost rw will be proof you need adbd insecure
so once you have rw.....do a reboot

yes its a pain but if you lose rw.....we will know for sure ok?

I will recheck this post tonite in about 20 minutes then call it a nite

[bryfly]

ok we just have to be careful with hitting the space bar.

the first, second and last lines ....in terms of input are all good
the second last line failed = third line as we have a gap

try

Code:

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

that pesky third line is
mount space hypen o space remount comma rw space /system....with luck

2) reboot and lost rw will be proof you need adbd insecure
so once you have rw.....do a reboot

yes its a pain but if you lose rw.....we will know for sure ok?

I will recheck this post tonite in about 20 minutes then call it a nite

Ok mate----cheers for your help, lost root again, I think there maybe cross contamination between 2 super su installs, even though I totally uninstalled one and reinstall the other, will keep trying to see if I can get rid of it.

Have a good kip, guess you are in NSW as it is about 11pm there...

---

ok we just have to be careful with hitting the space bar.

the first, second and last lines ....in terms of input are all good
the second last line failed = third line as we have a gap

try

Code:

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

that pesky third line is
mount space hypen o space remount comma rw space /system....with luck

2) reboot and lost rw will be proof you need adbd insecure
so once you have rw.....do a reboot

yes its a pain but if you lose rw.....we will know for sure ok?

I will recheck this post tonite in about 20 minutes then call it a nite

Ok mate----cheers for your help, lost root again, I think there maybe cross contamination between 2 super su installs, even though I totally uninstalled one and reinstall the other, will keep trying to see if I can get rid of it.

Have a good kip, guess you are in NSW as it is about 11pm there...

Is this the one you want?????

[aus9]

no my brain needs a rest I am in WA

on reboot you lose true root due to secure mode
its no big deal----sometimes safer

but not if you need or want to do things.....
things that can not be named (Harry Potterism)

2) Its up to use to search your /data/app and /system/app
but use the forum or google to research any app you are not sure

I can not immediately tell if you have truly deleted the Chinese app.
Normally you have it but as you say you can no longer find it,
---I am not sure your explanation is correct

let me think about it

In the mean time, on my phone.....if I reboot I don't lose the su function
but I lose rw function

is that clearer?-----that is why I invented this tutorial
its called true root for that reason

---

Hi

In this discussion NORMAL root means that when you issue the su command your prompt changes from $ (at left)
to #

TRUE ROOT means your prompt also changes to root@phone
for you root@Coolpad8297W:/ #

Altho my tests are many, we have limited to just the Android to save you learning any adb commands.
##############################################################################

Your third image post 24......I can see what you mean
its not moving from su to root@phone
hmmm

There are 2 ways to go here....maybe more but lets keep it simple

#########
ZIP METHOD
#########

Involves you rebooting into recovery mode with the downloaded zip file on your microsd card

CWM will have an option to flash a zip, you navigate to it and select it and let it do its business

On reboot of phone, we are looking for no loss of the root prompt when running command
su

It is NORMAL for a secure phone to lose rw status. But you can make it rw with the command.

######
CHEAT
######

This option has you with busybox installed
-you do the commands for su and id and get true root image
you mount your /system rw
------I won't ask you to install adbd insecure

and then we have a go at spoofing your MAC

Altho I said it was off topic, me thinks we will now add it here to see if we can get somewhere fast.

#######
SPOOFING
########
spoofing means make a false MAC. If you shutdown your phone or reboot, you lose the spoofed MAC

You can only try this command if your /system is rw and you have root powers and busybox installed

You enable WIFI first please......the command will take it down.

Code:

su
busybox ifconfig wlan0 down
busybox ifconfig wlan0 hw ether 01:02:03:04:05:06
busybox ifconfig wlan0 up

###########################################################
I will leave it to you to decide what to do next.

Personally I think at some point Device2 will need to be re-examined as its not my experience that an user has to keep on installing busybox.

but I do agree I should not offer you too many options in case you suffer information overload?

good luck

EDIT
#############
ENGLISH CWM
###########
Assuming I have your device correct, there is an English recovery of CWM here
[Only registered and activated users can see links Click here to register]

download it and use mobileuncle to Update the recovery
I have a movie in the tutorial section on how to do this as you have a mediatek device
[Only registered and activated users can see links Click here to register]

no need for USB drivers

It might be worth discussing in case you have a fear about bricking?

Once you have a decent recovery on your phone we could re-seduce you into trying out the zip method?
In the image at needrom you can see an option = install zip from sdcard........Yes would be what I cry out!

[aus9]

Now re-looking at busybox since that is an issue for you.

go to playstore and your apps and uninstall your current one

search for busybox on rails and install that
[Only registered and activated users can see links Click here to register]

It offers 2 ways to install.....normal and you guessed it....via recovery
try normal first and see if you lose busybox --do a reboot
if you do then re-open and choose CWM

2) Be aware you will lose rw....that is normal and is not an issue from my point of view
as you already know how to fix it

good luck