Hi
I was looking to get root access to my sgs2 and tried the method using 'odin3' and 's2 root' explained in this thread:
http://forum.xda-developers.com/showthread.php?t=1125414
(I also did the optional 'step 11' and reflashed an original kernel)
Everything went good, but then I tried Titanium Backup, Root Explorer and SU; the first says I dont't have root, Root Explorer hangs and SU functions but does not show any apps... It also wants to update binary, but that does not function neither.
So, I did use root checker to verify and it said that I don't have proper root... ???
Then I tried the Root Checker Pro tool who logs this:
"
Superuser Application Status:
Superuser application - version 3.1.3 -is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: No such file or directory
Analysis: File /sbin/su does not exist.
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-xr-x root shell 22228 2011-09-27 23:12 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root 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: shell (non root) user - ro.secure=1
Results provided on your GT-I9100 device by Root Checker Pro version 1.2.7 from joeykrim in the Android Market - http://goo.gl/NcnHn"
Is there someone who can tell me what this log exactly means?
It looks i do have root, but not properly? Now what ... ?
Open Superuser and try and update the su binary. If it doesn't work, just do what the majority do and flash a relevant CF-root kernel.
If you don't lose anything, reflash and start again.
oinkylicious said:
Open Superuser and try and update the su binary. If it doesn't work, just do what the majority do and flash a relevant CF-root kernel.
Click to expand...
Click to collapse
I tried... it failed...
So, you propose CF-Root; But I do have some questions about it 4 u:
1) after cf-root it isn't possible to use 'app2SD' (read that in a post...) ?
2) I also read that now that S3 is released, dev leave SGS2 and kernelswill not be updated anymore... ?
3) Can I still use Kies ? or how do I know a new firmware has been released for SGS2 (4.0.4 - Jelly Beans) ? I suppose checking this forum, but if Chainsfire's thread isn't updated anymore, what then ?
4) After CF-Root and in the supposition there are no more updates, do I have to unroot to reroot using another method ?
5) (linked to previous questions): what do you think, as experienced user, of this thread : http://forum.xda-developers.com/showthread.php?t=1746794
How reliable / thrustfull is it ?
And, if it is, what method do you suggest me ?
Thank you also for helping me out !
Losing things ?
TheStickMan said:
If you don't lose anything, reflash and start again.
Click to expand...
Click to collapse
What do you mean by lose anything ?
And are you telling me I should do the procedure again (all 11 steps) from Liryquidperfections method ?
Thx
Anyone ?
Oinky?
Related
I hope somebody can help me.
Since yesterday all of a sudden I could not download anything anymore from the market.
I rebooted and some programs were not working anymore (android market & quickpic don't launch).
Also my go launcher ex dissapeared everywhere ... without any reason.
When trying to use my titanium backup it said that no rooting privilages got granted.
I checked and I could not find my superuser / rom manager anymore ..
Searching the internet brought me to this topic.
I downloaded the RootcheckPro APK and ran it on my HTC Desire with below result.
Is there anybody who can help me :-(
I am desperate ...
Thanks in advance.
(Busybox - All was fine)
Below is the error messages I get when running "ROOT"
Root Access is not properly configured or was not granted.
The following link is a suggested Guide for obtaining root access on your device. No guarantee the guide will work. Please use the guide with CAUTION!! Suggested guide for your device:
Unrevoked
Superuser Application Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: ls: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x 1 root root 22240 Aug 1 2008 /system/xbin/su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/bin/su:
Result: ls: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: ls: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
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 HTC Desire device by Root Checker Pro version 1.2.1 from joeykrim in the Android Market -
Click to expand...
Click to collapse
What rom are you on?Did you move any apps to the sd (apps2sd) card instead of the system to save space?If something like this happens to me and i can't figure it out,i just reinstall the rom over the top without wiping anything,it will usually fixes my problem,but its good to do some research first.
Here is info ROOT CHK PRO Gave me.... Root Access is not properly configured or was not granted.
Super User Applications Status: Superuser application - version 3.1.3 - is installed! SuperSU application - is NOT installed. The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access: Standard Location Check Command: ls -l /system/bin/su: Result: -rwxr-xr-x root shell 380532 2008-08-01 07:00 su Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Standard Location Check Command: ls -l /system/xbin/su: Result: lrwxrwxrwx root root 2012-08-17 20:51 su -> /system/bin/su Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location Check Command: ls -l /sbin/su: Result: /sbin/su: No such file or directory Analysis: File /sbin/su does not exist.
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: shell (non root) user - ro.secure=1
NOW WHAT DO I DO TO CORRECT?
Results provided on your SPH-D710 device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market
Sent from my SPH-D710 using xda app-developers app
Which method did you used to attemp to gain root access?
im assuming it flashed improperly, try to flash it once again
root issues
AzulCz said:
Which method did you used to attemp to gain root access?
im assuming it flashed improperly, try to flash it once again
Click to expand...
Click to collapse
I AM LOOKING FOR METHOD I USED BUT I THINK IT WAS ODIN TAR WITH DATA SAVED BUT IT I DID NOT HAVE TO GET RID OF YELLOW TRIANGLE THEY SPEAK OF.. I KNOW MY PHONE INFO SAYS 4.0.4 AND FI27? I will try re-doing it and see if it works. ALSO WHAT IS MY NEXT STEP UP AFTER I FIX THIS? JELLY BEAN / C10 AND WHATS BEST WAY TO GO ABOUT IT? ALSO, LAST THING, I HVE THAT KIES AIR CUZ IM ON SPRINT SO PLEASE I NEED A SIMPLE INFO ON HOW TO ERASE. THANKS A MILLION AND I LOOK FOWARD TO FUTURE HELP!:good:
i have been trying this for awhile now and so far i only have it unlocked and running cwrm touch. i have super su and superuser on my phone but both fail to gain root access when i try and update the binary. i have a log that may help you guys understand the problem.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 0.96 - is installed!
System File Properties for Root Access:
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 2008-08-01 08:00 su
Analysis: Setuid attribute present and root user ownership 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: lrwxrwxrwx root root 2013-02-17 00:54 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
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: shell (non root) user - ro.secure=1
any idea on how to get it to root? ive tried to install a custom rom and it would work but it wouldnt get past the loading screen. so i had to flash back to the stock rom. i also cant get su because its not rooted. id appreciate any help you guys can offer. thanks!
kodi.roberts said:
i have been trying this for awhile now and so far i only have it unlocked and running cwrm touch. i have super su and superuser on my phone but both fail to gain root access when i try and update the binary. i have a log that may help you guys understand the problem.
Click to expand...
Click to collapse
For the initial rooting you have to flash a superuser app from recovery rather than installing it from the Play Store or an apk. After the initial rooting is done and the app itself can get root permission, you can update using using the app.
The current flashable SuperSU zip file can be downloaded from this post.
ramjet73
Hi , ive been trying to find an answer for a few weeks with no success , and as Google always seems to send me here , i thought ask here
I have a generic tablet thats rooted , this is confirmed by root checker & validator , but i have no Su binary ?
All i want to to is make one directory writable so i can add the media line to permissions for external storage , as this has been a pain not being able to use , but whatever i try doesnt work , Su & super dont work as they state no Su binary , so im at loss as to what to attempt next ?
Any help would be really great , who would think trying to add a few words could be so much trouble , coming from a pc background im very astounded that its so hard to do and also the bad implication of the external sd card ? but apart from that Android has been like a breath of fresh air
Ps Supersu does ask if i want to try and go into safe mode and flash ??? or something like that...........
Cheers
ANDROID VERSION 4.2.2
KERNEL VERSION 3.3.0+ (WED JULY 31ST 2013)
SOC CHIP = SUPER DOULCORE A20
BASEBAND VERSION 1.3_20130731
BUILD NUMBER KT100-L1-D35-0572-201308012
Results provided on your MID device by Root Checker Pro version 1.2.8
Congratulations! You have root access!
Super User Applications Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
SuperSU application - version 1.60 - 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 67080 2013-08-14 11:48 su
Analysis: Setuid attribute present and root user ownership 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:
Root user id:
uid=10061(u0_a61)
Root group id:
gid=10061(u0_a61) groups=1028(sdcard_r),3003(inet),50061(all_a61)
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
Any help would really be great , while i still have some hair left.....................
Ps have i posted to the coreect forum ?
several heysape
Is it possible to mount the system r/w through the terminal app ?
Try this. It worked for Strike II, which I suppose you have.
You can boot into recovery with 'adb reboot recovery' command
JCarangoH said:
i saw this recently...
http://forum.xda-developers.com/showthread.php?t=2146226&page=4
looks like we can root all our unbranded A20 allwinner tablets with Lannig's zip file, i tried and now i have my tablet rooted at last
here's the link for the ZIP file: http://ge.tt/api/1/files/2ujyScg/0/blob?download
- just put the zip in your SDcard
- reboot in Recovery mode (stock recovery i mean)
- apply update from EXT
- reboot and Enjoy
Don't forget to say thanks in the thread above...
Click to expand...
Click to collapse
Is it possible to unlock the bootloader + root and keep the original rom? I can't find a stock rom for the 32gb wifi tablet
Sent from my SGP512 using Tapatalk
Anyone?
Sent from my SGP512 using Tapatalk
SnowManWales said:
Is it possible to unlock the bootloader + root and keep the original rom? I can't find a stock rom for the 32gb wifi tablet
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
Wrong thread but yes it is possible. And here are link to latest stock rom for SGP512:
http://forum.xda-developers.com/showthread.php?p=54755457
Thanks for the info, but I do think it's a general question, so not the wrong thread
Sent from my SGP512 using Tapatalk
SnowManWales said:
Thanks for the info, but I do think it's a general question, so not the wrong thread
Sent from my SGP512 using Tapatalk
Click to expand...
Click to collapse
Hey there,
Lets see if I can sort this out, as remember, we have a multi national group of users, and not always do we understand the question.
Now, being a new Z2 owner, but not new to android development, here is the deal as I see it.
You keep the original "stock" rom, but only in a sense. Yes, the core components are still in place, but more than likely a few things have changed.
1) most likely the boot.img, as in the case of an insecure kernel. Although this change is mostly done in ramdisk and not the kernel itself.
2) unlocked bootloader (depending on which root method you use)
3) addition of superuser or superSu
4) possibly some exploit files, most which may be cleaned up on rooting.
Bear in mind a couple other things might be changed, but in the end, it's still basically a stock OS as far as the core files go.
If you want to know if there is an easy way to go back to a totally "factory condition, well, you will need to flash a factory ROM (ftf image). Generally this takes care of things except for the DRM files (if you unlock bootloader, then you should back them up first)
Hope this is a little more inline with what you were requesting.
Personally, I rooted the latest version without doing the bootloader unlock. I believe by unloking bootloader, you only lose the DRM keys, and your /Data (downloaded apps). Somebody correct me if I'm wrong.
Well I unlocked the bootloader, rooted the device, tried to install busybox but no luck
BusyBox file was not found in the system declared path.
A popular method of installing BusyBox is to use this BusyBox app by Stericson in Google Play.
Results provided on your SGP512 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market - http://goo.gl/NcnHn
And root checker tells me this
Congratulations! You have root access!
Super User Application Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT 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: -rwxr-xr-x root root 121260 2014-10-23 16:16 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
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:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
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: shell (non root) user - ro.secure=1
Results provided on your SGP512 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market - http://goo.gl/NcnHn
Sent from my SGP512 using Tapatalk
SnowManWales said:
Well I unlocked the bootloader, rooted the device, tried to install busybox but no luck
********
BusyBox file was not found in the system declared path.
A popular method of installing BusyBox is to use this BusyBox app by Stericson in Google Play.
********
Super User Application Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - is NOT 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: -rwxr-xr-x root root 121260 2014-10-23 16:16 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Click to expand...
Click to collapse
Probably what's going on, is exactly what the error logs are telling you. You have root access, to look at files, but you have no /system RW access. Understand Root and /System RW are 2 different things (although most rooting methods generally give you both).
The "SU" file it refers to, is the superuser binary file. Without it being installed, nothing is going to work right. I might suggest you do one of the following.
a) Use the original root program, and run it 2 or three times and verify it installs the SU binary.
or
b) Use the root method that installs the custom recovery, and flash install the superuser package. (unfortunately this involves unlocking the bootloader)
Regardless of which method, you will still probably need to use your file explorer to set /system to RW after the rooting process.
Good afternoon guys, when root for the new version 4.4.4??
Thankss