(Guide) Editing Root Explorer to work with Perma-Temp Root! - HTC EVO 3D

First off: This is a Paid app so I will not Post the App its self, This is just a Guide to make Root Explorer Work with our Perma-Temp Root so you never Lose Root Access via Root Explorer!
You need to know how to use smali & able to resign apk's, I wont be covering a how-to for those steps..
Step 1.).. De-compile Root Explorer using smali
Step 2.).. Open the File CommandShell.smali located at > \smali\com\speedsoftware\rootexplorer\CommandShell.smali
Step 3.).. Find the Strings
Code:
const-string v8, "/system/xbin/su"
const-string v7, "/system/bin/su"
const-string v6, "/data/bin/su"
Step 4.).. We now change those string to match these
Code:
const-string v8, "/sbin/su"
const-string v7, "/vendor/bin/su"
const-string v6, "/system/bin/su"
Step 5.).. baksmali it & resign the apk
Step 6.).. Unistall the current version of Root Explorer
Step 7.).. Now we can install via adb install or off the sdcard
That's it.. Hope that helps everyone with Root Explorer!
~Eugene

adb shell ln -s /vendor/bin/su /system/bin/su
Think it will work? I'll try it tonight and let you know.
Method:
Set system to rw.
Do the symlink : adb shell ln -s /vendor/bin/su /system/bin/su
Results:
Rootexplorer Works as root:
The real unknown is how long will this last.
Thanks for the symlinks.

willy900wonka said:
adb shell ln -s /vendor/bin/su /system/bin/su
Think it will work? I'll try it tonight and let you know.
Method:
Set system to rw.
Do the symlink : adb shell ln -s /vendor/bin/su /system/bin/su
Results:
Rootexplorer Works as root:
The real unknown is how long will this last.
Thanks for the symlinks.
Click to expand...
Click to collapse
I think everyone has already tried that... I know I have, when the symlinks fail you are left with no Root for Root Explorer though.
~Eugene

weird but my i downloaded root explorer and it works so does es explorer. i can see my root items. weird.

kaos420 said:
weird but my i downloaded root explorer and it works so does es explorer. i can see my root items. weird.
Click to expand...
Click to collapse
But can you edit those items, or any items in your root folders?
Not sure what the issue is with Root Explorer, but ES File Explorer can edit system files just fine for me without having to jump through any hoops, I've been using Eugene's old Perma-Temp Root from last Saturday (thanks Eugene!).
I've edited the SD card read-ahead buffer value in /sys/devices/virtual/bdi/170:0/read_ahead_kb to 4096 and it's stayed there all week.

Been rooted nearly all week, and just tried it... Root explorer still works. Just added a comment on build.prop to test. Made the change and created the backup file, then erased the backup file
Sent from my PG86100 using XDA App

Related

[How to] Installing Superuser Whitelist on Nook Color

Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Thanks for the info. Just a quick note that on Cyanogenmod 6.1 RC2 (Nexus One), the su binary is actualy at /system/xbin/su rather than /system/bin/su
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
Code:
linux$ adb pull /system/app/Superuser.apk
linux$ adb pull /system/bin/su
From a machine with ADB working, and communicating with your Nook:
Install Superuser.apk, and copy the su binary to /data/local:
Code:
linux$ adb install Superuser.apk
linux$ adb push su /data/local/
Shell into the Nook, remount the system partition read/write, and install the su utility to /system/bin:
Code:
linux$ adb shell
# cd /system/bin
# mount -o remount,rw /dev/block/mmcblk0p5 /system
# cat /data/local/su > su
# chmod 6755 su
# ls -l su
-rwsr-sr-x root root 26264 2010-12-01 10:27 su
#
reboot Nook Color to get Superuser to show up in "extras." Now, you can get root from inside the Better Terminal Emulator Pro shell.
Click to expand...
Click to collapse
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
2. More elaboration on "whitelist", please
3. If possible, show some example why someone might need this. I'd rather try to edit build.prop: pixel density, whatever, plus changing stock system Droid Sans into, say, much more beautifil Segoe WP. But it's just me though.
Thank you
Click to expand...
Click to collapse
For #3, somebody may want to replace system fonts to support other languages than English. I have done that to Android 2.1 phones too.
aludal said:
Thank you, very useful instruction!
Couple of questions though:
1. Any public repo where the working in NC Superuser.apk could be downloaded from? Not everyone out of NC owners owns Galaxy Tab.
Thank you
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
hharte said:
Get superuser whitelist. I pulled mine off a rooted Galaxy Tab:
linux$ adb pull /system/bin/su
Click to expand...
Click to collapse
Thanks Man, this was the part i didn't get and it's working now
PTzero said:
Here you go: http://forum.xda-developers.com/showthread.php?t=665974
Click to expand...
Click to collapse
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
califrag said:
So I installed this version of the Superuser apk but it seems to be an old version (2.0.3) with the ninja icon.
The latest version is 2.3.6.1 but I can't seem to get it to install (INSTALL_FAILED_UPDATE_INCOMPATIBLE).
Which is the latest version of Superuser apk that works with nC that has the 'Android Skull and Crossbones' icon and does anyone have the apk?
Click to expand...
Click to collapse
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
dark79 said:
That's odd. I was able to install 2.3.6.1 with no problem. I pulled it the apk off my Nexus One.
Click to expand...
Click to collapse
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Will this work on just linux or windows?
You can do it on windows using ADB
califrag said:
Could you pull and post your Superuser apk and your /system/bin/su file? I don't have a nexus one and when I tried using the Superuser apk and su file from the cyanogen 6.0 Nexus ROM it didn't seem to work either
EDIT:
Nevermind I got it working using the files attached (latest version 2.3.6.1)
(from here: http://forum.xda-developers.com/showthread.php?t=682828)
I also noticed that it had to grant itself Superuser permissions when I hit the "settings" tab. Under the settings tab I also noticed my 'su' version was 'original' and there was an update available which changed it to version '2.3.1-ef'. Not sure if this needs to be done for it to work right or not but thought I should mention it.
Click to expand...
Click to collapse
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
sminker said:
What did you do to get this? I tried installing using ADB and Android Commander. I get the same error that says INCOMPATIBLE. This is the only program giving me issues.
Click to expand...
Click to collapse
Make sure to download the 'eclair\froyo' version.
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
sminker said:
this is the file im using
su-2.3.6.1-ef-signed
i did have it installed once and uninstalled, but now i cant reinstall it
Click to expand...
Click to collapse
use adb shell and go into /data/data and do an 'ls'
remove any directory there that looks like 'com.noshofou'
i was able to use z4root to get it installed
when I do:
cat /data/local/su > su
I get:
Cannot create su: remote access failed
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Is there any advantage to put the binary into xbin versus bin
discourse said:
Is there a Windows tutorial for how to install Super User on the NC or an apk that does the same thing?
Click to expand...
Click to collapse
I would like a windows walkthrough also

[TUTORIAL] Easy method to change framework-res.apk with shell script

I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
hugerth said:
Is there any method to get back original framework from SDCard, and paste it to /system, when my phone doesn't want to boot?
Click to expand...
Click to collapse
Use xrecovery..
Sent from my E15i using XDA App
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
hugerth said:
Can't install... ok... I reflash 1.6 and root it again, install 2.1 and xRecovery for the future...
Click to expand...
Click to collapse
ops.if you have working rootshell, you can replace it using rootshell. but, since you've go back to 1.6, it doesn't matter. just install xrecovery in the future, quite useful.
Now I have system back (after about 2h) with working xRecovery and... God!.. why I haven't noticed it before...
i wanna ask how to recover the framework-res.apk from the xrecovery??
mount /system and use adb push
edit: new script. revised operation
D:\adb>adb remount
remount failed: Operation not permitted
any help here? I need to replace the framework
nm, forgot to chmod 06777 /system/framework
Thank you for you work. I hope to see this work Just rebooted my phone after applying your script.
propc said:
I created script to change framework-res.apk
--New-- Script with safer operation uploaded.
Requirements
-rooted
-busybox installed
1-copy framework-res.apk that you want to replace to the root of your sdcard (make sure it's in root)
2-extract reframe.zip(attachment) to root of your sdcard
in adb shell, use this command:
Code:
su
cd /sdcard
sh reframe.sh
your phone will reboot. and done! your framework-res.apk replaced safely.
Original framework-res.apk backed up as framework-res.apk.orig in /sdcard
Click to expand...
Click to collapse
Can u tell me where to find the adb shell
Sent from my E15i using XDA App
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
you can always change a framework by installer from available theme
mzmz83 said:
Use Super One Click, it comes with adb. Copy cmd.exe to SOC folder. Now start cmd, now type 'adb shell' (click enter) and then the other commands.
Sent from my E15i using Tapatalk
Click to expand...
Click to collapse
This is what I see when I open superoneclick t shows Root, shell Root, Unroot, allow non market apps....
Now in superoneclick folder that it comes in when u open it this is what u see
Superuser.apk
Superoneclick
Su
Sqlite3
Regeagainsttecage
Bushels
Addbwinusbapi
Adbwinapi
Ashland
Adblinux
Adb. Application
But when I try to open adb app it does not open a screen comes up then it closes so there is where am stuck at:-( :-( can u help me out from there??????
Sent from my E15i using XDA App
adb won't stay open if you click it, it will just flash out on the screen.
it was supposed to be somekind of a "bridge" for the cmd and the phone...
correct me if i'm wrong please...
You have to copy cmd.exe to the SuperOneClick folder, then you have to open the cmd.exe, not the superonecklick.exe.
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
oubsty, Thanks you
Boshe said:
I'm trying to replace framework and when I type in shell I got:
cd /sdcard
#
sh reframe.sh
sh: Can't open reframe.sh
#
Click to expand...
Click to collapse
I think it works if your phone is charged by your laptop/computer only. You do not allow it to connect. I mean you can not reach SDCard through Total Commander, etc. only charging.
Help
# sh reframe.sh
sh reframe.sh
sh: Cannot open reframe.sh
#
any ideas
got SuperOneClick 1.5.5 ( busybox )
root explorer ( only thing in superuser )
SE's PC companion running in background [ keeps asking for mount, but is ignored ]
got Android full SDK installed - drivers, ADB, 'the works'
root'd succesfully -(( WORLD-1-8_2.0.1.A.0.47 )) White-DarkBlue / Pink
4Gb Kingston HC4 sdc4/4gb 18 - un partitioned.
I wish to remove some bloat, and change to a custom theme.
{EDIT} - how to access recovery mode?, got customization = home-back-back-home-back-home-home-back
Dalvik Debug Monitor won't run, adb error2
thanks in advance.

[How To] Disable Auto-mount on boot

Hi All, just got the NT for a week and has been busy reading and learning. Thanks to all devs that make this into a full tablet.
It's a pain that we have to manually disable the automount each time we reboot NT. So here is a simple fix (Your NT needs to be rooted to use this fix):
Method 1: Using Root Explorer
1. Set /system to read-write
2. open the file /system/bin/clrbootcount.sh in text editor
3. Add the following line at the bottom:
Code:
setprop persist.service.mount.umsauto 0
4. Save and set permissions to 755 (All Read, Top Write, All Execute)
Method 2: Using ADB
Code:
adb remount
adb shell
cd /system/bin
echo "setprop persist.service.mount.umsauto 0" >> clrbootcount.sh
Reboot and see if it works
Note: For 1.4.1 users, please use DeanGibson's method below: http://forum.xda-developers.com/showpost.php?p=22007574&postcount=9
do you add
setprop persist.service.mount.umsauto 0
underneath the word "done" when viewing in root explorer?
promek said:
do you add
setprop persist.service.mount.umsauto 0
underneath the word "done" when viewing in root explorer?
Click to expand...
Click to collapse
Yes. Add it as the last line will do.
Having made this mod, how do you mount for pc accessories sd?
rei901 said:
Having made this mod, how do you mount for pc accessories sd?
Click to expand...
Click to collapse
Use NT hidden settings
Sent from my LT18i using XDA App
thanks it works, confirmed working by using ADB
You don't have to do any of this if you boot your NT from the microSD card.
It works flawlessly.
installed and it works. using root explorer
thanks
Use the provided "hook" file
cobrato said:
Code:
setprop persist.service.mount.umsauto 0
...
Click to expand...
Click to collapse
Why not just put the above line in /data/boot_complete_hook.sh ??? That's what it is for; it's invoked by /system/bin/clrbootcount.sh -- That way, you don't have to modify clrbootcount.sh, and the change will persist across a /system restore or B&N update.
Create /data/boot_complete_hook.sh, with the following as the first line:
Code:
#!/system/bin/sh
Add your "setprop" line above.
Mark the file as executable:
Code:
chmod 755 /data/boot_complete_hook.sh
DeanGibson said:
Why not just put the above line in /data/boot_complete_hook.sh ??? That's what it is for; it's invoked by /system/bin/clrbootcount.sh -- That way, you don't have to modify clrbootcount.sh, and the change will persist across a /system restore or B&N update.
Create /data/boot_complete_hook.sh, with the following as the first line:
Code:
#!/system/bin/sh
Add your "setprop" line above.
Mark the file as executable:
Code:
chmod 755 /data/boot_complete_hook.sh
Click to expand...
Click to collapse
Yes it's better to create boot_complete_hook.sh. In fact I have to do that in 1.4.1 - changing clrbootcount.sh will cause bootloop

[Q] Can't paste file in /system/etc. after setting permissions to RW

I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
Theres other apps that use root that are free,just use google or try android/apps on here,the search function is your best friend.ES gives me issues also.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
You can use the terminal emulator, this way (assuming the host file is located in your sdcard):
Code:
su
mount -o rw,remount /system
cp /sdcard/hosts /system/etc/hosts
--set permissions here if you need
mount -o ro,remount /system
Personaly, I don't face any problem with ES File Explorer, but you can try this one (free, lightweight and useful)
cant is cant
RoberGalarga said:
You can use the terminagoing to be lator, this way (assuming the host file is located in your sdcard):
Code:
su
mount -o rw,remount /system
cp /sdcard/hosts /system/etc/hosts
--set permissions here if you need
mount -o ro,remount /system
Personaly, I don't face any problem with ES File Explorer, but you can try this one (free, lightweight and useful)
Click to expand...
Click to collapse
The problen was defined, he said he is rooted he set the permissions, set the system or as mounted read write... the answer is not just use this app, if you are rooted # not $ and you can not read or write something it is not going to be a standard answer... I have tje same problem, I thonk it is because I used a rooter for chines operating system, and it gained root but has some issues. A hint to this was that I had to run ot 2ce to do the rooting. This is for sure tho, if ypu cant do it in terminal as su, np app is going to be sble to do it for you. I suggest to do as I am going to to do, and that is to hard reset, and find a non chinese tablet rooter.
j0nthn said:
I can't copy the file 'hosts' back to system/etc. after I cut it out of the folder a couple mins ago. When I use ES File Explorer (don't wanna pay 4euros for Root Explorer..) to try and paste it back (with everything set to RW and having root permissions) it says 'permission denied'. I don't know what I'm doing wrong.. Help is greatly appreciated.
Click to expand...
Click to collapse
its due to root permission............try reseting root permission through superuser app.................

[Q] K47 / C9_89 an S3 Clone [Solved]

OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
SpongeR0b said:
OK, I'm running into difficulties with this phone..
..It arrive pre-rooted, I installed Titanium Backup and removed iReader.
In the Play store I noticed that SuperUser and Google Keyboard needing updating but when I tried to do so all I got was "Error Installing - Package file was not signed correctly" which I assume has something to do with a slightly different version of the program initially installed?
Then I went into SuperUser itself, clicked on the spanner icon, scrolled down and tapped on the check for updates button..
..indeed it found an update and proceeded to update in a similar style terminal box.
However.. according to Titanium I no longer have root access, I quickly downloaded Root Checker Basic which also confirmed this.. bugger I thought.
Moving onwards, I just downloaded SRS Root from srsroot.com. Tried rooting and it exited out saying I already had root access.. hmmm, so then I removed root access, the phone rebooted and then I re-applied the root.
Although I am still suffering from not having proper root access :crying:
Please help me to get full root access back again, thanks in advance. :angel:
Click to expand...
Click to collapse
UPDATE : After running Root Checker Pro it told me that SuperSU wasn't installed.. I downloaded that from the play store and re ran Root Checker Pro, it now tells me..
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.91 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 22364 2014-01-27 21:08 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
I still have Root Explorer on the phone and seem to be able to navigate through the normally hidden directories.
Suggestions please!
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - version 3.0.2 - is installed!
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-xr-x root root 22140 2008-02-29 02:33 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: root user - ro.secure=0
Results provided on your K47/C9_89 device by Root Checker Pro version 1.3.4
Click to expand...
Click to collapse
SpongeR0b said:
To my surprise, I bit the bullet today and reset my phone to stock defaults..
..unfortunately even this still did not fix the incomplete root
Please help!
EDIT : I've been tinkering again.. Here's what I understand (and what I've done)
System\bin\ - Kinda not the most important place to store a file relating to an installed .apk's
System\xbin\ - The more important place (kinda like the System32 directory) relaing to installed .apk's
System\app\ - The directory where the .apk file's themselves live (kinda like Program Files\xxx Application)
Well I noticed I had an .apk in apps called root_Superuser.apk and this was present even after un-rooting my phone.
I removed this file, using these commands :
adb remount
adb pull /system/app/root_Superuser.apk
Seemingly this didn't remove the file, so then I tried :
adb remount
abd shell rm -f /system/app/root_Superuser.apk
After a quick reboot this had indeed removed Superuser, then I reused the SRS Tool to re-root.
Then I read that SU 3.0.2 was a safer bet.. (although it was a post from 2011 - attached)
So I downloaded that and proceeded to push the superuser.apk and su files into their correct places (as below)
adb remount
adb push superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
After the files were correctly in place I needed to set the correct file permissions, I did this as follows :
abd shell
[email protected]:/ # CHMOD 644 /system/app/superuser.apk
[email protected]:/ # CHMOD 777 /system/xbin/su
[email protected]:/ # CHMOD 777 /system/bin/su
Finally I realised I had given /xbin/su the incorrect permissions so ammended them to :
abd shell
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
The reason why I am writing exactly what I did is so I myself don't forget anything and also to show others how to do stuff should I be doing it correctly!? I wasn't sure if the su needed to go into xbin or bin so I put it into both directories and thus I can remove which ever one is incorrect once I get a reply from somebody!
Here's my current log from Root Checker Pro - I shall not be doing anything else without further assistance.
Click to expand...
Click to collapse
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
joeykrim said:
Great to see the Root Checker apps being used! Given you posted a link back to this thread in the Root Checker thread I'm posting my reply here.
The route I usually take and recommend, which does all of those steps you've performed, such as copying files and setting the correct permissions, is to load an "official" .zip file from the custom recovery.
If you have a custom recovery, I'd recommend loading SuperSU.zip, which has worked very well for me on my devices: http://forum.xda-developers.com/showthread.php?t=1538053
From the XDA post, there is a link to the .zip file that can be downloaded and loaded in the custom recovery: http://download.chainfire.eu/supersu
If you don't have a custom recovery, I think most of the steps you've taken are correct, but based on the Root Checker Pro output I'd be concerned that the Superuser.apk file you installed and the su binary aren't communicating and might be out of sync. This can be caused by many reasons but the solution is to make sure you installed a matching .apk and su binary.
Hope that helps and good luck!
Click to expand...
Click to collapse
Thanks for your reply JoeyKrim, unfortunately I don't think a custom recovery is available for this phone at present? I've had SuperSu on my device and to be honest not a great deal worked using it. I've also had both CWM / TWRP installed on the phone and both of them cannot find a suitable ROM to implement. I guess because of the phone being fairly new and a knock off doesn't exactly help me! :cyclops:
I will re-root my device and if that isn't successful manually try to match both superuser.apk and su binary with yet another version of superuser!
EDIT :
Here's what I've tried this morning (unfortunately now I have ran out of time and must get ready for college)
adb remount
adb push Superuser.apk /system/app/
adb push su /system/xbin/
adb push su /system/bin/
adb shell
[email protected]:/ # CHMOD 644 /system/app/Superuser.apk
[email protected]:/ # CHMOD 4755 /system/xbin/su
[email protected]:/ # CHMOD 4755 /system/bin/su
Superuser available to download from http://hosted.androidsu.com/superuser/
Using: su-3.0.1-d-signed.rar I get Superuser v3.0.1 (36), Su binary vnull (legacy)
su-3.0.1-efgh-signed.zip I get Superuser v3.0.1 (36), Su binary vnull (legacy)
Unsure of differences between d & efgh versions? Moved onto next version..
su-3.0.2-efgh-signed.zip I get Superuser v3.0.2 (37), Su binary vnull (legacy)
Renamed ([email protected]:/ # mv Superuser.apk root_Superuser.apk) seemingly no difference?
I was wondering if root allowed apps were renamed as root_appName.apk - I've left the file
name as this (i.e. Superuser.apk is NOT in my system/app/ directory and yet Superuser still
runs fine???)
Superuser-3.0.6-efgh-signed (Only binary updated) v3.0.2 (37), Su binary vnull (legacy)
su-bin-3.0.3.2-efghi-signed.zip Superuser v3.0.2 (37), Su binary vnull (legacy)
Isn't Su binary 3.0.3.2 the more up to date binary??? According my my Superuser's self update
it is?
Trying this release? - Also copied Superuser.apk to root_Superuser.apk as well this time..
Superuser-3.1-arm-signed Unable to check the versions.. different menu
Additionally myt Root Explorer (root_Root explorer.apk) now cannot gain root access which
is the first time this has EVERY occured
Superuser-3.1.1-x86-signed Unable to check the versions.. different menu
OK, so I know for sure that 3.1 is a more recent version of Superuser than I have ever had on
my phone, and of course root explorer doesn't now work, so trying an older version..
Superuser-3.0.7-efghi-signed.zip Superuser v3.0.7(41), Su binary v3.1
Again.. Root explorer no longer working.. tried deleting root_Superuser.apk
(adb shell rm -f /system/app/root_Superuser.apk)
Hasn't seemed to do anything different.. Removing all SuperUser files, ran out of time to
experiment with. Annoyed that now even my Root Explorer isn't working, I seem to be going
backwards and not forwards!!
After un-rooting (using SRSRoot) I once again have access to my Root Explorer??? Weird.
Click to expand...
Click to collapse
O.K, I'm ready for step by step instructions, anybody know how to help me please?
EDIT :
Thanks to tijsh111 for providing a working root solution to my problem..
http://forum.xda-developers.com/showthread.php?t=2219062&nocache=1

Categories

Resources