Related
Phone: Incredible 2, running Android 2.3.3 Stock Verizon ROM
S-OFF and Rooted : using revolutionary 0.4pre4
HBoot: 6.13.1002
Recovery: Revolutionary CWM 4.0.1.4
I'm having ROOT Access/SU problems. I need access to some files in the root/System/ directory and am unable to get r/w.
I s-off/rooted my Incredible 2 using the instructions on this tutorial http://forum.xda-developers.com/showthread.php?t=1219246 (The How To Root DInc2) and the instructions on the revolutionary.io website. (Essentially: Get S-Off via revolutionary> flash recovery CWM> flash su.2.3.6.3-efgh)
The revolutionary s-off process was successful and I got s-off.
I flashed Superuser su.2.3.6.3-efgh-signed.zip and seem to have Root. The binaries are upto date according to the app.
I have Titanium Backup, Root Check, BusyBox Installer installed. I had to install Busybox. All these apps run properly. I can wipe, backup, and install system app data via Titanium Backup. Root Check says I have root access and the correct Busybox location.
The Problem
I installed Root Explorer today and I am successfuly able to change from R/O to R/W and back on the root directory and on the SDCard. But when I go to the System directory I cannot change from R/O to R/W.
Tryed to connect to the Inc2 from my PC (winXP) via ADB. ADB Devices command shows my device. When in ADB Shell the default profile is $. When I type in SU I get back the message "SU: permission denied" I do not get a prompt from Superuser on the phone to give access.
(To see if the problem was in the steps I was doing I tried this on my rooted Incredible 1 and in Root Explorer I was successfully able to remount the System directory from R/O to R/W and back. But the same problem with ADB I have on both Inc1 and Inc2. (Inc1 was s-off/rooted with Unrevoked3/Unrevoked Forever, with su.2.3.6.1-ef-signed.zip.)
I'm not sure what went wrong where, since some of the root access is working. Any suggestions? Help?
Thanks,
that happen to me before. and the only way to change the r/o to r/w is going back to stock,if you have a stock back up rom you have to run that one,and then you can install the rom you want,and the you can change with root explorer s/o to r/w.if you dont have a stock back up you have to install the PG32IMG,and then you have to go to revolutionary and install the recovery.dont forget to turn off the fast boot.if you dont know how to do that,setting,power,and then uncheck the fast boot to off.
I dont think your binaries are up to date.
Try installing SuperUser 3.0 and report back - with updated binaries. The binaries should show at least verison 3.
I had issues to with the Root access that came with revolutionary and this worked for me.
You are on the right path though.
I'd like to try and avoid flashing the original Verizon ROM back on the phone. I'll leave that for last resort. There is stuff that I've done to the phone that I would rather not have to go through to do again.
In Superuser I tap on the 'check for binary updates', the respone after checking is that the 'su is up to date'. The version that I'm currently using su.2.3.6.3-efgh-signed.zip the files are modified in 2008 and 2011. So it seems to be upto date.
Is there a place I can download the latest version of Superuser 3.0?
The version of Superuser3.0 that I was able to find, when I open the zip file, shows all the files last modifed in 2008.
You wont have to flash back.
Follow my advice and install the new SuperUser on the market. It is 3.0.
Once in the application go to update binaries and update anyway.
Reboot and let us know how it works.
Those 2.3.6.3 binaries didnt work for me either. Now im fine after following my own advice.
Oh - and also - check to make sure that you have allowed specific permission for the application you are having issues with - within SuperUser.
You will be pleased to see that the new SuperUser can automatically grant Root to all of your apps...dangerous, but speeds things up.
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
gunnyp said:
@tinkbtrar. Thanks!
Ugrading to the latest Superuser 3.0 and updating the binaries did help! Still some problems, but making progress.
I can connect via adb shell and get SU privileges. # shows up! I think I now have r/w privilege on /system. Not sure, but I think I do. (I'm still learning adb shell and linux commands)
But I still cannot get Root Explorer on the phone to work properly. Same problem as before. I can get r/o and r/w on the root directory, but cannot get r/w on the System directory. The button turns green, but the nothing changes.
I can live with getting SU privileges in adb shell, but it would really be nice to get r/w on System in RootExplorer.
Click to expand...
Click to collapse
Be sure to click thanks if you haven't already. Lol.
Try wiping data...force closing and uninstalling root explorer (thru manage applications...not CWR).
Should take care of it. And because you are rooted you should have full access to filesystem via adb already.
Sent from my Xoom using xda premium
try mount -t ext3 -o remount,rw /dev/block/mmcblk0p25 /system with adb. thatll remount /system as readwrite
Sent from my Incredible 2 using XDA App
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
trust me you will have to do what i said before in the second post...
gunnyp said:
@tincbtrar, gave you the thumps-up!
No go with Root Explorer yet.
I wiped data from CWM, uninstalled, and reinstalled Root Explorer, but still could not get r/w on the System directory using Rootexplorer.
Anyone, any ideas/suggestions?
Click to expand...
Click to collapse
You paid for Root Explorer. It doesn't work for you. I'd be bugging the developer since it's clearly not doing the job.
@android-incredible
yes, i looking more and more like i may have to flash my rom backup that i made right after s-off. let's see, since i can get su in adb shell i can get done what i need to so reflashing is not utmost urgent.
i'm not sure it's rootexplorer since i've not seen other posts with similar issue. if the flash of the rom backup does not do it, that may then point to rootexplorer. lets see...
Hello there,
I just flashed a new ROM (Gingerbread 2.3.7) last night. After signing in the Google account everything is great; the old apps got redownloaded and all. I noticed that there is no apps listed in the superuser. I tried 'su' command in the emulator terminal & I got permission denied.
Luckily all the apps are working in perfect harmony. However, how do I get the superuser permission back? It seems like my device is not rooted. Do I need to root my phone again? Fingers crossed I don't.
Initially, I tried to flash the Ice Cream Sandwich. I tried multiple times but to no avail. I even tried to change the HBOOT (from CM7 > downgrader > Stock HBOOT) but the process failed. I afraid that this might be the cause my root access got lost. Anyone can verify this?
Thanks!
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
beachcomber said:
Su app will be built into the ROM so you should still rooted. Sounds like Su settings are just defaulting to deny. Open Su, menu > settings and check its set at prompt (safer than allow). After flashing new Rom you'll need to launch apps that require root access to allow them permission again. You might need to update the Su app or binaries if permissions don't stick.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
xuminarc said:
beachcomber,
1. my Superuser is set at prompt.
2. I am not sure which app that require root access. Could you give me some examples so that I can run them?
3. I tried to update the su binaries, but I got this:
" checking current install path...FAIL!"
" failed to find currently installed su binary. Update cannot continue."
Therefore, what do you suggest?
Thanks.
Click to expand...
Click to collapse
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Alaa said:
Take a backup. Download this. Flash it through recovery. Reboot and check if it works.
Click to expand...
Click to collapse
Thank you! It works!
A Work in progress.
DISCLAIMER!
This Document ONLY applies to Acer Iconia A100 devices. For info on upgrading from HC to ICS you can look HERE to see the method I used to upgrade from stock HC 3.2 GEN2 to ICS (Note: This was before the general ICS release. It works on OTA update also) Then follow these directions to get to CWM with Custom ROM.
I'm writing this because we STILL don't seem to have a single clear set of instructions. So here is my attempt at getting one started. Please feel free to point out errors, or help us build a set of directions. I'm not trying replace anyones documentation or take credit for anything. All the info in these directions can already be found here in various posts.
Thanks to Vache, Civato, ZeroNull, Euclid's Brother, Ptesmoke, abliss, aznmode, eew245, crossix, Icewyng, toyface, PG101, Smokku and Everyone else for all the Work an Insight.
ROOT
To root ICS Leaks you need to use mempodroid(info & file here). Eew245 wrote up instructions (on applying mempodroid on A100 to obtain a root shell). ZeroNull also has made a basic script found here that will root the device for you if you prefer.
I use the method outlined by Eew245. You can use your own "su" and "busybox" binaries if you saved them. This method provides full permanent root.
I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox).
UNLOCK
ZeroNull has made an easy to use package with instructions here If you don't have the Android SDK installed ZeroNulls method works fine. However if you want to use your own platform-tools you will need to modify the scripts first.(Just change the path for adb. Otherwise it will try to look for adb in the scripts working directory instead of platform-tools).
Pic of Bootloader warning about unlocking from Acer
PIC HERE
Lock Unlock Icons from same bootloader screen.
PIC HERE
Note: If you miss the window of oportunity running the script or unlock commands the first time. You DON'T need to rerun the whole script. The a200 bootloader is already installed. You just need to fastboot reboot bootloader again from your console, THEN you can use the vol keys and home to unlock the bootloader. BUT do what ever you feel safest doing and just pay attention and be careful. (Here I'm referring to the waiting too long after the script boots recovery into unlock mode. If you wait too long it times out and you can't choose unlock until you fastboot reboot bootloader again.)
RECOVERY
(make sure you have installed the a200/unlocked bootloader first. You will see a message at the top of the screen that says (UNLOCK MODE) when bootloader is showing it's message at boot.)
Here is the message I'm referring to PIC HERE
NOTE: When installing a Custom Recovery at some point you have to rename /etc/install-recovery.sh or remove it. I would recomend you rename it to install-recovery.sh.bak. You should do this before doing "adb reboot bootloader" otherwise when you try to reboot into recovery from ROM manager you will get a dead android because cwm will be overwriten with the old recovery(and you don't want that). If you DO get a dead android carefully read the directions again. Q. Why didn't I put this in a step? A. Because I dont want people to brick a device so I want to make sure they are paying attention before I tell them to rename a file that will keep the system from fixing recovery if they mess up.
Using Acer Recovery Installer 2.99 Beta(NOT MARKET VERSION)
=======================================
Download .apk enable non-market installers. Run installer, enjoy.
The Acer Recovery Installer 2.99 Beta is found HERE
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Or you can also use A100 TWRP recovery v2.1.0+ I have not tried it yet. It looks nice, has touch screen functionality, I think it uses a different backup format or something though. I'm not sure and have not had time to read up on it yet.
NOTE: Read my note above about /etc/install-recovery.sh
FLASH FROM CWM
==============
If you used ADB/Fastboot method you will need a way to reboot into CWM. ROM manager or bootloader reboot thingie will work for this.
If you installed Acer Recovery Image you can use it the app to boot into CWM.
CWM 5.5.0.4 uses the Volume Up/Down Toggle to navigate the menu and a short click of the power button to select things. Be careful about what you choose to do in CWM.
MAKE A BACKUP!!
===============
If you have just installed a custom recovery NOW would be a GOOD time to make a backup with CWM.
To Install a Custom ROM
===============
(BE CAREFUL. MAKE SURE The ROM you choose to install DOESN'T have a bootloader.blob and/or /recovery folder inside. Otherwise it could overwrite your CWM)
Just put the .zip file on an SD card and put it into the device. Use ROM Manager or Acer Recovery Installer
More to come, and I will add some pics showing what various screen look like when I'm able.
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
i +1 the question what will break if i update busy box?
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I don't know if this helps or makes things worst, but I have updated busybox after using Zeronull's root script on pretty much every ICS leak, CM9, and Flexreaper without any issues at all. I always read that warning, but ignored it because I need a more complete busybox version for certain tasks I run on my tablet.
NoSudo said:
A Work in progress.
Using ADB/Fastboot to flash CWM
============================
Use the steps found HERE(obviously don't re-root, unlock, just follow the other parts.
Click to expand...
Click to collapse
Just a little tip. Actually same thread post#28 uses very simple method thanks to mapaz04 to flash the recovery.
Great job though!
I did almost the same in my native language.
cheeb said:
"I suggest you install superuser.apk and busybox installer after rooting. Superuser.apk will provide access control for superuser and busybox installer will allow you to update busybox. I also recomend installing terminal emulator(don't forget to configure it to use /system/xbin/sh after you install busybox)."
So ZeroNull says to not update busybox ...you say to update it...is there really a problem if you update it??
Click to expand...
Click to collapse
I have not used ZeroNulls root method. So I am not sure why he says that. I think his script MAY just use the su and busybox in place in /data/local/ or something(not sure havnt D/L the package to figure it out). You CAN setup su and busybox in the correct locations WITHOUT an issue in ICS.
I use the "hard" method which is very simple. I KNOW you can remove the /data/local/tools copy afterwords doing it by hand.
An Explanation:
The reason you have to push su, mempodroid, busybox, and a mount script to /data/local/ is because you can get write access to it WITHOUT su. Then you run mempodroid which does a little magic and tricks system into thinking a shell was started by root. This drops you into the # prompt(temp). Then you mount /system(still using the files from /data/local). Then you copy the files to the correct path inside /system. Once you chmod su and run it you get root becase su is a special kind of executable. It's what is called an SUID application. As long as the permissions are correct to allow you read/exec access to both su and busybox. You no longer need /data/local/tools. At this point you CAN update busybox and su if you like.
P.S. You can also use your OLD su and busybox for the whole thing. I saved my old su and busybox and always just reuse them then update.
If you want to understand more I would suggest reading up on what SUID is all about and also learn about Unix file permissions.
I can confirm that: rooting,bootloader unlock and change on the recovery can be made with OTA update.
Nice work!
gertjanad said:
Nice work!
Click to expand...
Click to collapse
Thanks, and a bump to keep the info around the first page.
Added to bump it back up so people can find it.
Is there a kernel that allows overclocking yet
Sent from my A100 using XDA
I have not played with OCing, I honestly don't see a need.
I know cwm 5.5.0.x has an Overclock menu so I'm guessing yes you can. But I am not familiar enough with the device/cpu to know how the multipliers etc are to be configured, nor do I experience lag or performance issues that would cause me to desire lowering battery efficiency and increase heat for faster performance.
Though I am familiar with the process on PCs both jumpered and jumperless.
Up!
Hi,
i have a rooted Desire Z currently running CM9 RC2, and I've noticed recently that my # shell has been replaced by a [email protected]:/ and it seems like I don't have root access there. I can't ls in /data/ for example, and su throws a permission denied error. However, apps that require root access(such as Titanium Backup) still seem to work. I noticed this happen right after I installed and ran Busybox. I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access. I'm not sure if this app is what caused it, but it was when I noticed it.
In any case, short of a nandroid restore how do I get back shell root access and the proper shell?
Thanks.
Most likely your root access under System Settings -> Development was changed from "ADB and Apps" to "Apps Only".
PS: why would you be installing busybox, CM9 came with it (likewise with superuser and su).
Thanks. That worked.
Like I mentioned in my original post
I did not even install busybox from the app as I already have it. I was just trying to get the apk file for another device with no internet access.
Click to expand...
Click to collapse
goister said:
Thanks. That worked.
Like I mentioned in my original post
Click to expand...
Click to collapse
Though your quote here conflicted so wasn't sure :
I noticed this happen right after I installed and ran Busybox.
Click to expand...
Click to collapse
Sorry for the confusion, by running busybox I meant simply launching the Busybox app(which is just an installer, not busybox itself), but not clicking the "install busybox" button in the app to actually install busybox on my phone.
Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
doublehp said:
Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
Click to expand...
Click to collapse
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
akitten007 said:
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
So, is there a way to install busybox via recovery ?
I did 3 things in recovery: all in /system/xbin
- chmod +s su
- touch t
- mkdir tmp
after reboot to normal mode, SUID bit was removed, but t and tmp are still here.
So, how do I install busybox ?
New issue: /data has the nodev flag; is it possible to remove it ?
I did not found /dev/shm ; was it moved somewhere else ? Any other place for similar use ? (world write temp folder in RAM).
akitten007 said:
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
doublehp said:
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
Click to expand...
Click to collapse
Now you're starting to go over my head. If you want to keep your current kernel, I would try using this method here to manually add the module that disables the protection http://forum.xda-developers.com/showthread.php?t=2702575. I usually just install busybox using rom toolbox or any other busybox app. You could search for a busybox zip, but just disabling the write protection is a better option in my opinion. And I have actually 0.00 idea what flags mean on folders (sorry).
I rooted using TWRP recovery and super su. That guide you posted gives unnecessary instructions. TWRP automatically installs the SU binary and Super su the first time you boot into it. I was able to update Super su via google play, no need for the update zip. Just follow the instructions after rebooting to system from TWRP recovery.
I'm s-off, unlocked, my kernel, firmware and os are stock, only thing that isn't is recovery. I have write access to system and external sd card. All I did was make it writable with root explorer and have installed busy box no problem using this app https://play.google.com/store/apps/details?id=stericson.busybox.
I was given a better fix.
http://forum.xda-developers.com/showthread.php?t=2701816
In short:
adb push /mnt/big/tmp/wp_mod_m8.ko /mnt/sdcard/Download/
insmod /mnt/sdcard/Download/wp_mod_m8.ko
mount -o remount,rw /system
cd /system
touch z
mkdir zz
reboot
[email protected]_m8:/storage/emulated/legacy # cd /system/
[email protected]_m8:/system # ls
app
bin
build.prop
customize
etc
fonts
framework
lib
lost+found
media
priv-app
tts
usr
vendor
xbin
z
zz
[email protected]_m8:/system #
The miror is on maintainance for now. So, the guy on IRC gave me his local backup. I will push it here for 30 days:
http://dl.free.fr/gSha53ljz
(server will delete it after 30d nobody downloads it)
Busybox still fails to install; don't know why.