i Rooted my phone a few months ago and installed a few roms but didnt like any of my options so i kept the phone rooted with the stock look. now i want to try a new rom and my phone is telling me my phone isnt rooted any more...
any suggestions??
What is telling you that you are not rooted? Like trying to run certain root apps? How did you root? Which bootloader? Does is say s-on or s-off?
Sent from the MIUI powered 3d
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
ramseyattar said:
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
Click to expand...
Click to collapse
Do you have superuser installed on your phone?
ramseyattar said:
the rejection i am getting on rom manager is "an error occured while attempting to run privileged commands... sorry i am kinda a beginner on my 3D..rooting on my evo prior was so much simpler...and i used to use shoot me and all of a sudden it couldnt acess root permissions...
on my boot screen it says
s-off
hboot1.4.1000
radio 0.97.10.0530
Click to expand...
Click to collapse
looks like your bootloader is still unlocked, which is a very good sign.
more than likely the permissions on your root access where changed at some point in time. either from loading a ROM or removing/adding superuser.apk incorrectly.
my application, root checker pro, will show all the necessary information in order to troubleshoot.
my guess would be, you'll probably need to install the superuser.zip file from recovery mode and that should add the /system/bin/su binary for Superuser.apk back and set the permissions as 4755 on the su binary. this is the most common and simplist method of properly restoring root access for Superuser.apk users.
if you want, feel free to post up the root checker pro results and we can specifically troubleshoot. hope that helps!
joeykrim said:
looks like your bootloader is still unlocked, which is a very good sign.
more than likely the permissions on your root access where changed at some point in time. either from loading a ROM or removing/adding superuser.apk incorrectly.
my application, root checker pro, will show all the necessary information in order to troubleshoot.
my guess would be, you'll probably need to install the superuser.zip file from recovery mode and that should add the /system/bin/su binary for Superuser.apk back and set the permissions as 4755 on the su binary. this is the most common and simplist method of properly restoring root access for Superuser.apk users.
if you want, feel free to post up the root checker pro results and we can specifically troubleshoot. hope that helps!
Click to expand...
Click to collapse
my results were:
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:
http://www.revolutionary.io/
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
---xr---wt root root 26324 2011-08-12 15:27 su
Standard su binary location: ls -l /system/xbin/su:
lrwxrwxrwx root root 2011-09-07 20:28 su -> /system/bin/su
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
ramseyattar said:
my results were:
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:
http://www.revolutionary.io/
Superuser.apk - com.noshufou.android.su - version 3.0.6 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
---xr---wt root root 26324 2011-08-12 15:27 su
Standard su binary location: ls -l /system/xbin/su:
lrwxrwxrwx root root 2011-09-07 20:28 su -> /system/bin/su
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Click to expand...
Click to collapse
Those results are perfect in that they show exactly what the issue is!
If you are familar with ADB, the process is very simple to fix your root access. I've done this many times! A basic but important process to learn, in my opinion.
Reboot to recovery, from a computer type, adb shell and issue two commands as follows:
mount /system /system
chmod 4755 /system/bin/su
go ahead and reboot.
Alternatively, if you're not familar with adb, the next simpliest approach, in my opinion would be to load the Superuser-3.0.6-efgh-signed.zip file onto your sdcard. reboot into recovery and "flash"/install the .zip file. The superuser.zip file will execute the above commands for you.
Run Root Checker Pro again and it should trigger superuser prompting whether or not to grant root checker access. go ahead and grant it root access.
Root Checker Pro should confirm you have root access and for the /system/bin/su line it should show an "s" in the middle of the permissions, example: rwxsr-xr-x root root 26324 2011-08-12 15:27 su . the "s" being in the middle is important as this is the setuid bit essentially granting the su binary superuser permission/access.
Reasons the permissions were changed on the /system/bin/su binary ... really hard to say but we can narrow down the causes. In order to change the permission, the process/device/application would need root access. Everything executed in recovery mode usually runs as root and many users don't inspect the updater-script file of the ROM .zip before they load.
Sometimes flashing ROMs, which aren't setup properly, will remove or set incorrect permissions removing the setuid bit on the su binary.
Also, flashing an OTA file would definitely remove the setuid bit on the su binary.
Hope that helps!
Related
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?
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
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
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
Okay. I have a weird situation in my hands.
I'm attempting to root a tablet that's not out yet (It's a dev version that I got my hands on). So I installed adb and fastboot on my computer to do that. But when I type "adb shell", the command prompt has a #, which should mean my device is rooted, right? Actually, it says the following: http://gyazo.com/734b7a0eb125d7be02c09362e89a8cd2
The thing is, the tablet isn't actually rooted. But since I somehow have access to the root via my computer, what steps should I take to actually root my device? I've searched lots of guides online, but none ever accounted for having access to root when using "adb shell", so I don't know what to do.
Thanks in advance for your attention! ^^
EDIT:
Okay. A few more bits of info. I ran Root Checker Pro and this is what I got:
Code:
Superuser Application Status:
Superuser Application - version 3.2 - is installed
System File Properties for Root Access:
Check Command: ls -l /system/bin/su
Result: -rw-rw-rw- root root 380532 2008-02-29 17:03 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Check Command: ls -l /system/xbin/su
Result: -rwsr-sr-x root root 211739 2013-12-06 18:50 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!
When I read that, I did:
Code:
adb shell
cd /system/xbin
su
And it just returned "su". It doesn't actually root the device, which had lead me to think that I need to fix the setuid for the /system/bin/su file. Am I correct? If I am, how to do that?
EDIT 2:
Just discovered that my tablet doesn't have a recovery partition. Gonna work on creating one.
how can i root my device while its unrootable or dont have access
Sent from my QMobile T500 using XDA Free mobile app