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.
i have a motorola flipside with 2.2.2 installed. somehow it lost its root and will not reroot z4root keeps shuting down and giving some odd error saying The application z4root (process com.z4mod.z4root) has stopped unexpectedly. Please try again and leaves only the option to force close the app. i left gingerbreak running all night and when i woke up it was still running not getting anywhere theyed superoneclick it will not finish im getting very fustrated with this phone i even went as far as asuming somthing on the phone went bad and flashed it to a stock att rom and still cannot get the root to finish and apply. is there some way i can mannualy root this phone? also yes usb debuging is on allow unknown aps to install is enabled
anyone please this dam phone is practicaly useless without a root to me id rather be using my stupid windows 7 phone at this rate because at least it had my ringtones and allowed me to use a different backround image than stock att ones.
---------- Post added at 02:09 PM ---------- Previous post was at 01:47 PM ----------
ok i have come accross this but i am a little lost at the steps
wiki.rootzwiki.com/index.php/Motorola_Flipside
it says to download 3 files psneuter busybox and super user unzip the downloads into the same folder. then it says to open a terminal and change to the folder i dont understand this what am i suposed to to? it then says i need android sdk installed and working witch i do i installed it for android screencast. then it says adb devices but does not say how im suposed to enter this command. after that im fairly sure its from the cmd entering the commands shown on that link. can anyone tell me how to get throgh the first few steps please?
copyed from link
Manual Root
[edit] Download
psneuter: Download
Superuser: Download
busybox: Download
Unzip the downloaded files into the same folder
Open a terminal and change to the folder.
You need the android SDK and ADB working. To make sure type:
adb devices
if your device lists, then you are ready to go!
[edit] Gain Root
Run the following commands:
adb push psneuter /data/local/temp/psneuter
adb shell
chmod 755 /data/local/temp/psneuter
./data/local/temp/psneuter
ADB should hang, wait a little while and then type:
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
Type:
exit
adb push busybox /data/local/temp/busybox
adb shell
chmod 755 /data/local/temp/busybox
./data/local/temp/busybox mount -o rw,remount /system
The last command should return nothing
update i learned how to do the procedure and finished sucesfully however the phone is still not rooted. i did reboot the phone after it seems faster now but not rooted.i downloaded the root checker app and scaned the phone it emailed me a log and here is that log
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
System Environment PATH: /sbin /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:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location: ls -l /sbin/su:
/sbin/su: Permission denied
Alternate su type binary location: ls -l /system/xbin/sudo:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
Results provided on your MB508 device by Root Checker version 3.7 from joeykrim in the Android Market
is it even posible to root this phone?
i guess im not allowed to be helped or somthing.
i have a procedure here that i had to build up from 2 seperate write ups. i had to use this one http://androidforums.com/droid-all-...oid-without-rsd-lite-up-including-frg83d.html along with this one together http://wiki.rootzwiki.com/index.php/Motorola_Flipside to get it to root properly.
here is what i did. u will need the downloads from both links for this to work i beleive. follow the steps from the second link to gain root once u get to where the number simbole is shown in the command line u need to switch to the instructions in link 1 and start at step 13 and follow to the end. this works to root your flipside when nothing els will work at least for me it did none of the apps that are suposed to root for you worked for me.
thank you me for having to figure this out on my own have fun
Problem rooting
I rooted my Flipside at its stock state and it worked fine. And then I upgraded my software to 2.2.2 Froyo and lost the root so now I am trying to reinstall z4root and re-root the phone but z4root now doesn't work. It gets successfully installed but when I hit PERMANENT ROOT it just stays in that window with the turning wheel and gets stuck there. It doesn't completely root. I've tried the hard reset by pulling the battery, and hitting the back key and forced closing it and then trying it again. Nothing works! HELP!
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
jovanphilip said:
I once had a flipside. I rooted it the stock rom and then updated to gingerbread and then rooted again. I used superoneclick though. I'm not sure which version, but there is (or was) a flipside forum here on xda with documentation on the entire process.
Edit: here's the forum link: http://forum.xda-developers.com/forumdisplay.php?f=772
Click to expand...
Click to collapse
Really? I thought the only upgrade I can do to it is from stock to Froyo. How'd you do that? I'm sorry. I am totally untechie. :/
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.
This is tested and working on NSZ-GS7 REL10 for US
Thanks to the guys with gtvhacker making the temp root. we are now capable of having a static root.
i have now achieved static root, changing the /system
# pwd
pwd
/system/xbin
# ls -l
ls -l
-rwsr-xr-x root root 1062992 2013-07-23 20:06 busybox
-rwxr-xr-x root shell 70604 2008-08-01 14:00 dexdump
-rwxr-xr-x root shell 11736 2008-08-01 14:00 fw_loader
-rwxr-xr-x root shell 67736 2008-08-01 14:00 hciconfig
-rwxr-xr-x root shell 189380 2008-08-01 14:00 hcidump
-rwxr-xr-x root shell 40736 2008-08-01 14:00 hcitool
-rwxr-xr-x root shell 31432 2008-08-01 14:00 hidd
-rwxr-xr-x root shell 10360 2008-08-01 14:00 mfgbridge_trigger
-rwsr-xr-x root root 91992 2013-07-23 20:06 su
Click to expand...
Click to collapse
I have used the starting point from entonjackson making the root for Acer A1-810, using dd to seek through the mmcblk0 to write a modified /system
see more details on that approach here
the big secret to writing the new filesystem:
1. follow gtvhacker instructions to get temp root on your box. (find instructions on temp root here
2. as root do a chmod 777 /dev/block/mmcblk0 ; chmod 777 /dev/block/mmcblk0p11
3. dump the filesystem: /data/local/tmp/busybox cat /dev/block/mmcblk0p11 >/mnt/media/usb.E234-1928/system.fs
4. on a linux box: mount the dumped filesystem (system.fs) with -oloop to be able to modify it.
ie. mount -oloop /tmp/system.fs /tmp/1
5. copy your busybox and su to the /system/xbin/ folder where you mounted the system.fs (use files attached to this post)
5a. remember to set permissions on both files, owner - root/root, permissions 4755 on both files and you are safe.
6. umount your dumped filesystem from location you mounted it.
7. write back the newly modified filesystem (i renamed it now to system.with_root) .
/data/local/tmp/busybox dd if=/mnt/media/usb.E234-1928/system.with_root of=/dev/block/mmcblk0 seek=149248 bs=4096
thats is awesome Dexter congrats!!, i have a question: how much should be the size of the dump system.fs?
bovoro said:
thats is awesome Dexter congrats!!, i have a question: how much should be the size of the dump system.fs?
Click to expand...
Click to collapse
should be 1 GB
mmm, is a 3.99GB system.fs for me, and I inserted su and busybox to /xbin/, but i forget to give permits :S. is neccesary?
i flashed back system.rooted , but is 3.99 GB and appear no free space in device :S maybe for 3.99GB file
bovoro said:
i flashed back system.rooted , but is 3.99 GB and appear no free space in device :S maybe for 3.99GB file
Click to expand...
Click to collapse
instructions updated in post #1, sorry.
bovoro said:
but i forget to give permits :S. is neccesary?
Click to expand...
Click to collapse
its important that su command has correct suid permissions (4755) and ownership (root)
Dexter_nlb said:
1. follow gtvhacker instructions to get temp root on your box.
Click to expand...
Click to collapse
And these are?
Appreciate the work this obviously took. Might be over my head, technically. Going to need to give it some study.
BELASCO said:
And these are?
Appreciate the work this obviously took. Might be over my head, technically. Going to need to give it some study.
Click to expand...
Click to collapse
i have updated post #1 with reference on how to get temp root.
ill attach my su + busybox used in post #1 now.
Thanks so much buddy!!!, I was able to root , now what? , What kind of access we have with this type of root? all folders? can i install Superuser Apk ?
bovoro said:
Thanks so much buddy!!!, I was able to root , now what? , What kind of access we have with this type of root? all folders? can i install Superuser Apk ?
Click to expand...
Click to collapse
maybe this one works now on our device? xposed installer, i do not think it needs to modify /system. but since my box is bricked until i get REL10 or REL11 to fix it, i cannot experiment much.
modifying the build.prop, and changing to a more old version, it would be possible to reinstall an update? or protect for future automatic updates?
Are we able to mount the / system folder as rw?
* adb shell mount-o remount, rw / system
I made a copy of my build.prop, that security is only that blocks to downgrade?, "firmware is too old." message
# ro.build.product is obsolete; use ro.product.device
ro.build.product=NSZGS7
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=S052913/M12_OTA/HC_3.2_Localhost,release-keys
ro.build.fingerprint=sony/NSZGS7_C02_MX2/NSZGS7:3.2/MASTER/20130529185822:user/release-keys
ro.build.characteristics=tv,nosdcard
# end build properties
bovoro said:
modifying the build.prop, and changing to a more old version, it would be possible to reinstall an update? or protect for future automatic updates?
Are we able to mount the / system folder as rw?
Click to expand...
Click to collapse
/system can only be changed if we can modify root partition, which i did and semi-locked my box, until i reinstall root filesystem using REL10 update. so until more experiments are done, i would say no to this. /system is fine, root partition is a no go.
i believe so.
maybe you can actually help if you are willing to spend time writing another /system.
1. download the REL07 from the gtvhacker wiki
2. copy the build.prop from REL07 to your existing /system
3. install it and reboot once, so the new build.prop takes effect. (i believe you need to set proper permissions on it ie. permissions 644)
4. search for an update, you should get the REL10 downloaded
5. as you got root, you can easily extract it from the /cache partition where i hope its placed, otherwise its somewhere in a /data folder.
6. i am also told you can see the full path to where it is downloaded from google, in the logcat. so if you can dump logcat when searching and downloading update. that of course is easier to share.
7. then write back your old /system with root. and leave it.
possible?
yes man , really works , im downloading from my gtv REL10 MX region but what I did was use my system.fs old, mounted in linux and replace the build.prop file REL07 and voalá downloading system update REL10 , this can be work for change region im MX region , i can change to a US .
bovoro said:
yes man , really works , im downloading from my gtv REL10 MX region but what I did was use my system.fs old, mounted in linux and replace the build.prop file REL07 and voalá downloading system update REL10 , this can be work for change region im MX region , i can change to a US .
Click to expand...
Click to collapse
can you share the REL10 (or just the link to the clients.google.com site with the REL10 build) ? would really appreciate it, so i can get my box up and running again.
of course man, but is the mexican version, right now im try to change build.prop us instead MX and instal alogcat for sharing the US link
---------- Post added at 01:01 AM ---------- Previous post was at 12:47 AM ----------
bad news man,I have not updated yet, but when I reboot my box came the boot animation, and then went into a loop of a blue circle, is that how you did your box? I will enter recovery mode since I have the build.prop REL08 think I can upgrade to unbrick (i hope)
update:
I could not capture the OTA link, but I can share the zip, I'll upload it to dropbox
---------- Post added at 01:48 AM ---------- Previous post was at 01:01 AM ----------
bro here is the US ota http://android.clients.google.com/p...REL10_NSZGS7_U2_2203_133772_20130529_URSC.zip , i dont know if i can post links here, if not i will delete inmediatly
bovoro said:
I could not capture the OTA link, but I can share the zip, I'll upload it to dropbox
Click to expand...
Click to collapse
thanks very much appreciated , i hope it works as i am told it would with the same release installed
edit: downloaded and installed.. my Box is back in business!
Dexter can you please post a video on how to I new this root but have the slightest idea where to start thanx in advance
Dexter_nlb said:
This is tested and working on NSZ-GS7 REL10 for US
Thanks to the guys with gtvhacker making the temp root. we are now capable of having a static root.
i have now achieved static root, changing the /systemI have used the starting point from entonjackson making the root for Acer A1-810, using dd to seek through the mmcblk0 to write a modified /system
see more details on that approach here
the big secret to writing the new filesystem:
1. follow gtvhacker instructions to get temp root on your box. (find instructions on temp root here
2. as root do a chmod 777 /dev/block/mmcblk0 ; chmod 777 /dev/block/mmcblk0p11
3. dump the filesystem: /data/local/tmp/busybox cat /dev/block/mmcblk0p11 >/mnt/media/usb.E234-1928/system.fs
4. on a linux box: mount the dumped filesystem (system.fs) with -oloop to be able to modify it.
ie. mount -oloop /tmp/system.fs /tmp/1
5. copy your busybox and su to the /system/xbin/ folder where you mounted the system.fs (use files attached to this post)
5a. remember to set permissions on both files, owner - root/root, permissions 4755 on both files and you are safe.
6. umount your dumped filesystem from location you mounted it.
7. write back the newly modified filesystem (i renamed it now to system.with_root) .
/data/local/tmp/busybox dd if=/mnt/media/usb.E234-1928/system.with_root of=/dev/block/mmcblk0 seek=149248 bs=4096
Click to expand...
Click to collapse
@Dexter_nlb
Hi dexter,
I was wondering if you can help, i have a copy of the file system and I have mounted it using the command you specified,
mount -oloop /tmp/system.fs /tmp/1
but it mounts it as a read only file system. therefore I cant copy over the su and busybox. Can you help.
Update.
got it fixed. now fingers crossed will flashback to system.
What superuser app are you using with the box. Tried chainfire version but it did not work.
Is the su you posted chainfire version?
Cheers
Optimal
Files System corrupt
Problem Resolved
Woot has this box on sale today, can't wait to get mine and try this. Why doesn't XDA have a section for gtv?
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