[Q] Revolution HD 3.1.1 on HTC Sensation - lost root?? - General Questions and Answers

I successfully installed Android Revolution HD 3.1.1 on my HTC Sensation, but now I've lost root. When an app (e.g., Titanium Backup) asks for root rights, it gets denied. BusyBox is installed, and the phone was rooted previously. What could be going on?? Could I really have "lost" root? (I didn't think it was even possible to be running Revolution HD and not be rooted!)
Thanks....
---------- Post added at 09:31 AM ---------- Previous post was at 08:55 AM ----------
Running Root Check, I get the following error report:
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0-beta4 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 root
Standard su binary location: ls -l /system/bin/su:
lrwxrwxrwx root root 2011-09-12 10:24 su -> /system/xbin/su
Standard su binary location: ls -l /system/xbin/su:
-rwsr-sr-x root root 22228 2008-08-01 05:00 su
Alternate su binary location:
/sbin/su: No such file or directory
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
I double checked, and /system/bin/su is there but /system/xbin/su is not. So it seems that somehow su is not configured correctly, but I'm not sure what to do about it. Help!?
---------- Post added at 10:07 AM ---------- Previous post was at 09:31 AM ----------
Hmm. I uninstalled two different BusyBox installers and now I have root again. Don't know why, but things seem okay now. Odd.

Odd, yeah. But great that you got it back.

I found this thread through google, I just have a question for the same problem:
using:
HTC Desire HD
Android Revolution HD 6.1.1
S-OFF
lost ROOT
I've deinstalled root, and reinstalled but without luck. installed beta 3, without luck.
I'm not using busy box. What could I do to get this fixed?

lost root on 6.1.3?
I just installed Revolution HD 6.1.3 with full wipe (upgrading from 5.1.x).
I noticed that /etc/hosts file only contains 1 entry for localhost, when I installed adfree, superuser crashes.
Root checker shows the same as above. Could I lose root?
Looked into downloaded 6.1.3 rom zip and it contains only localhost entry in /etc/hosts.
How can it be? Any ideas?
Thanks.

Got root back
The problem was in superuser version 3.0.4 (which is bundled with revolution hd 6.1.3). Found 3.0.2 version, cleared data of 3.0.4 (Settings-Application-Superuser, stop app, clear data), installed 3.0.2 and root is back.

Related

[Q]

Hello everyone,
Been following posts here for a little while and I'm aware there is no right place to post this question. I have a rogers SGH-I727R which was rooted via SuperOneClick. After attempting to reinstall busybox I lost root access and can't quite seem to get it back. I've tried going through SuperOneClick to unroot/root however the program hangs and I'm forced to kill the process. The following are my results from "Root Checker Pro":
Superuser Application Status:Superuser application - version 3.0.7 - is installed!System File Properties for Root Access:Standard LocationCheck Command: ls -l /system/bin/su:Result: lrwxrwxrwx root root 2012-01-03 21:20 su -> /system/bin/busyboxAnalysis: File: su is a symbolic link pointing to another file: /system/bin/busyboxStandard LocationCheck Command: ls -l /system/xbin/su:Result: -rwsr-sr-x root root 22228 2012-01-0301:53*suAnalysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!Alternative LocationCheck Command: ls -l /sbin/su:Result: /sbin/su: Permission deniedAnalysis: File system permissions restricted and denied access.Alternative LocationCheck Command: ls -l /system/xbin/sudo:Result: /system/xbin/sudo: No such file or directoryAnalysis: File /system/xbin/sudo does not exist.Root User ID and Group ID Status:SU binary not found or not operating properlySystem Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbinADB Shell Default User:ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1Results provided on your SGH-I727R device
I apologize for the messy format. Any and all help would be greatly appreciated.
- Cam
Forget the one click, amd just use this method http://forum.xda-developers.com/showthread.php?t=1340526
---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------
For one are you android 2.3.6? Id suggest just following the link i posted
I am currently on 2.3.5 and it is the LTE HD not sure if it makes a difference or not but I noticed I forgot to mention that, thank you for the timely reply.
silver03wrx said:
For one are you android 2.3.6? Id suggest just following the link i posted
Click to expand...
Click to collapse
+1
I could not get SuperOneClick to work after I did the ota update to 2.3.6 with my original SR.
I had to exchange that phone and my replacement is on 2.3.5
SuperOneClick worked on my 2.3.5 phone first try.
---------- Post added at 02:51 PM ---------- Previous post was at 02:49 PM ----------
Never mind. Just saw your reply above.
Not sure about the LTE HD.
Yes it does. The recovery tar is for i727 skyrocket. Dont try it on a different device. I not sure what to tell you as you have a different device.

[Solved] New 4.2.1 update + root partially lost with Superuser App

Hello
I have upgraded my TF300T with the last ASUS update (4.2.1).
After the upgrade, I have a partially rooted device.
All the apps already declared in the whitelist of Superuser are still gaining the root permission (root explorer...). But any new installed applications cannot access root
After a few hours of research with google I found that supersuser app is not compatible with Android 4.2 but I didn't any clue to repair that.
[UPDATE] Solution in post 4
Thx
Re: [Q] New 4.2.1 update + root partially lost with Superuser App
Do not uninstall anything that has root! I had the same problem when updating from ICS earlier in year. Will post update when I find my notes.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=1995207
Check out this thread - you can see where I thanked the poster near the end. I downloaded the binary as instructed. I use ES File Explorer. I checked the permissions of the installed su. I then copied the new binary replacing the old one. I checked permissions again. I don't remember if I had to change them or not but they were the same when I was done. I then believe I updated the binary from the market. Lastly with fingers crossed I rebooted. For me root was completely restored and I was good to go.
Sent from my DROID RAZR HD using xda app-developers app
Reilly1812 said:
Do not uninstall anything that has root! I had the same problem when updating from ICS earlier in year. Will post update when I find my notes.
Sent from my DROID RAZR HD using xda app-developers app
---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------
http://forum.xda-developers.com/showthread.php?t=1995207
Check out this thread - you can see where I thanked the poster near the end. I downloaded the binary as instructed. I use ES File Explorer. I checked the permissions of the installed su. I then copied the new binary replacing the old one. I checked permissions again. I don't remember if I had to change them or not but they were the same when I was done. I then believe I updated the binary from the market. Lastly with fingers crossed I rebooted. For me root was completely restored and I was good to go.
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply but it does not work for me.
Solution
After several tries, I found a way to solve my problem.
As it could be useful for some other people, here are the steps to repair your root
All credit goes to Koush for the fix
Requirements : adb / su binary
Follow this link and dowload su binary on your computer
Extract the contents to a folder
Start a cmd window
Run adb shell
In adb shell type
Code:
/system/bin/su
Check you are root (id or # prompt)
Remount system as RW
Code:
mount -o remount,rw /dev/block/mmcblk0p1 /system
Open a new CMD window and push the su binary from step 1 to the internal storage
Code:
adb push <your path>\su /sdcard/
From the adb session where you got root, type
Code:
mv /system/bin/su /system/bin/su.back
cat /sdcard/su > /system/bin/su
chmod 6755 /system/bin/su
Done (maybe reboot)
If it does not work for you, you can restore your old binary if you prefer...
worked for me
fuzzynco said:
worked for me
Click to expand...
Click to collapse
Is there any way to do this from a terminal app on the device? I just updated and had this happen. I'm suprised more people didn't have an issue/ no general warning went out.

[Q] Latest kitkat update no more ROOTED DEVICE

I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - 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 71140 2008-08-01 16: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!
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.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /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: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
TheKicKer69 said:
I updated my motorola xoom to 4.4.2 3 weeks ago
(thread []http://forum.xda-developers.com/showthread.php?t=2593757&__utma=248941774.598456778.1394750856.1394750856.1394750856.1&__utmb=248941774.2.10.1394750856&__utmc=248941774&__utmx=-&__utmz=248941774.1394750856.1.1.utmcsr=google|utmccn=%28organic%29|utmcmd=organic|utmctr=%28not%20provided%29&__utmv=-&__utmk=22130616 ) -
all was excellent I got my xoom functioning like new - received update for my OS 3 or 5 days ago (Version from Screenshot of my Xoom http://imgur.com/ekkKd0J ) which i did to update the current 4.4.2 and worked like a CHARM;
just opened Titanium Backup said device NOT ROOTED. used root checker Pro, Supersu, Superuser and all show device not rooted.
Downloaded TWRP and reinstalled but did not hlep.
ROOT CHECKER PRO gives the following analysis so please hope someone can help me. (I can see a solution in the analysis below but dunno wot to do) Cheers, Roger
Root Checker Pro:
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - version 3.1.3 - is installed!
SuperSU application - version 1.93 - 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 71140 2008-08-01 16: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!
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.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /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: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn
Click to expand...
Click to collapse
I see that you have omni. Have you tried reflashing the root from omni thread?
Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger
I think I can help you
TheKicKer69 said:
Until now I only followed to the letter that Thread and this is how i jumped from 4.2 to 4.4.2; and in that thread it clearly says if u r upgrading from that update u won't need to wipe so when i got the notification 4 or 5 days ago there is a newer update to 4.2.2 I did and it went smooth only thing that went berserk is it says device ain't rooted.
Dunno wot else to do (I reinstalled like i said above latest TWRP [used to use CWM but if i need to update i will have to wipe everything as the thread says] and Supersu)
tx for the help,
Roger
Click to expand...
Click to collapse
Hi Roger,
Boy, I don't know how to stress this enough. Before doing anything, make a backup. After you are finished, you should reinstall your programs from the backup manually. Don't do an automatic reinstallation as there are some CM11 Program files that would make the Omnirom installation go into an endless loop.
CM11 has the Su built into it. If you use Omnirom you should first clear your Dalvik Cache and Cache, preferably doing a factory reset before installing your Rom as I mentioned about looping above.. You might want to install a newer Gapps file, as well as flashing a Superuser file-this last is a must with Omnirom
These 3 files should all be installed from your external sdcard. Just be careful not to format either of your sdcards.
k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger
TheKicKer69 said:
k, I did a full install just like in the thread and for some strange reason it is still NOT rooted! wot gives lol. (remember the first time i did it i got my xoom working flawlessly.
is there any other thread that also provides kitkat for my xoom - i really don't care about omni or any other developer just need to have my xoom with latest kitkat.
tx,
Roger
Click to expand...
Click to collapse
keeps getting weirder and weirder! This is from Root Access Pro! wth is going on? (remember did complete reflashing and followed all steps that i did the 1st time when it worked flawlessly - and yes i did d/l Superuser and SuperSu and also reflashed SuperSu that comes with the thread for updating)
Root Access is not properly configured or was not granted.
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 - 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: /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: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 104800 2014-03-28 14:52 su
Analysis: Setuid attribute NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
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 Xoom LTE device by Root Checker Pro version 1.2.8 from joeykrim in the Android Market - http://goo.gl/NcnHn

[Q] Big Part&OMNI no more root (need 2 backup 2 change my Xoom to SAMSUNG Q9050 12.2

[Q] Big Part&OMNI no more root (need 2 backup 2 change my Xoom to SAMSUNG Q9050 12.2
since I changed to BIG PART and OMNI i have 4.4.2 which is awesome but my Xoom Verizon doesn't show rooted anymore for Titanium Backup or any other Root app (even root checker pro tells me i am not rooted)
anyway my question is:
i am thinking of buying Samsung Q9050 (12.2" Tablet) how can i backup all of my games and apps and even system (like my wallpapers etc...) since i cannot use Titanium Backup
i know i can dump all of the Xoom on my PC but how to restore them and how to know which apps to restore since i can't see the folders containing my games , apps, etc..)
hope to get help.
Cheers,
Roger
P.S.: wot do u think about the Samsung Q9050 2.3 Ghz 12.2"?
You need to flash SU in recovery, once that is done you will be rooted and can backup with titanium backup. OmniROM doesn't come with root included
I did flash SU many times (SU 1.86) it actually comes in the OmniROM thread where i flashed my XOOM
http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=22130616
is there an SU u recommend? btw i cannot seem to download an SU i can only Install an SU (from google play store) - where can i actually D/L an SU in order to b able to place on SD and flash?
(in the thread we download:
Download Root
UPDATE-SuperSU-v1.86.zip)
tx a lot for the help;
and another dumb question - if i'm able to use titanium backup i can basically restore any backed up app on any android device right? whether it's a fone or tablet right? reason i ask is my xoom is the only android i use
Root Checker Pro Result:
Root Access is not properly configured or was not granted.
Super User Application Status: (SUPERSU 1.94 IS INSTALLED I MARKED IT)
SuperSU application - version 1.94 - 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 71140 2008-08-01 16:00 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: shell (non root) user - ro.secure=1
Results provided on your Xoom LTE device by Root Checker Pro version 1.3.6 from joeykrim in the Android Market - http://goo.gl/NcnHn
matt4321 said:
You need to flash SU in recovery, once that is done you will be rooted and can backup with titanium backup. OmniROM doesn't come with root included
Click to expand...
Click to collapse
Solved! D/L http://forum.xda-developers.com/showthread.php?t=1538053
SuperSU 1.94 fixed it while the V1.86 didn't!! maybe i should post also there if someone has/had my problem

Su installed but not available

Hi guys... I'm new here, and I'm losing my hope resolving my problem.
at first I have my rooted phone with kingroot installed, and I installed busybox and worked fine with root apps.
it start when I got confused to move busybox in /system/bin since it is not available in system/xbin. at first it can't install. what I did was I changed permission to r/w of system/bin try to install busybox applet in there and it succeas . but it gave me a big problem. my kingroot failed to recognize I'm rooted or I have lost my root? or root access. I tried rooting it but it can't go. it only get to 70% as always but failed. and I lost a high rate of succession. actually my first root was fast and ez.
I tried checking my su and root with some root/su checkup.
using DevCheck available in GPlaystore, it says
"Device is rooted" and
Busybox: "system/bin/busybox".
upon using RootCheckerBasic , its says " Sorry! Root access is not properly installed in this device."
and using Busybox Checker... its gives Busybox Available: YES
Path: /system/xbin, and SuperUser gives
Su Available: YES
Su access given: NO
Path: /system/xbin/su
Version info busybox and su: both not found.
so please help me with this. for the future this would be helpful.
mobile: Cherry mobile astro 2 (Philippines)
Model: Q490
Android: 5.1 lollipop
sc7731c
You need to unlock the bootloader
Hello, from what you said, that it happened after moving BusyBox to /system/bin instead of /system/xbin?
but there must be files for bb in /system/xbin and /system/bin
and if bb gives you the option to uninstall do it.
and then, reboot
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
thaiphuoc1 said:
You need to unlock the bootloader
Click to expand...
Click to collapse
read the whole thread before posting, we apprentice that you are trying to help, but copying the same statement all over the forum won't help, read the post first

Categories

Resources