Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
At the moment you can't until Google updates that feature to allow that. The multiuser is in its infancy. We will just have to wait I guess.
Sent from my Nexus 10 using Tapatalk HD
Thanks for your answer
waiting for this ...
It's actually the su binary which is tied to the primary user only at the moment... not sure how, or if, it can be built otherwise!
Furthermore, it is not even possible to enable developer settings (via build no) for second users, right?
So, without USB-Debugging no adb to backup second user apps (w/ data) using the Toolkit..
Is there any chance to fully backup second user apps? Apart from nand of course, as I would like to backup/restore apps for a switch to CM10.
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
craigacgomez said:
Superuser 3.3 now supports multi-user root... 3 modes... Owner only, Owner controlled & User controlled... I will post an update zip here once I built su & Superuser tonight!
Click to expand...
Click to collapse
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
djd338 said:
Wow... That would be truly amazing! Sounds like you are mod'ing the apps yourself, or are they updating to include the feature? I'm pumped at this possibility! Thanks craig!
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
craigacgomez said:
Nope... not my mod... official updates to Superuser... I've just built it with the new changes!!
Here you go... Superuser-3.3-arm.zip
Notable Changes (from Superuser 3.2):
1. Android 4.2+ multi-user support [3 mode -> Owner only, Owner controlled & User controlled]
2. Better handling of applications with multiple root (su) requests
Flashing using a custom recovery (TWRP or CWM). I recommend wiping data for the Superuser app and re-granting your root apps su access to avoid any problems.
NOTE: Even though Superuser 3.3 supports multiple users, you root apps may not... so there is no guarantee that all root apps will work fine in multi-user mode. For those app, you will need to wait for the app developers to update their apps to support multiple users.
Click to expand...
Click to collapse
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
jrod091 said:
So, could I use this updated su to change ROM control settings for multiple users on aokp?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I don't know if RC settings are global or user specific... depends of the settings... if the setting is specific to the user context, it will work, otherwise it won't...
drykc said:
Hello
Firstly sorry for my english
I'll tried to explain my problem
I successfull to root my device but only the main user account but I can't obtain access root in others account.
How can I do this ?
Thanks
Click to expand...
Click to collapse
If you are using SuperSu, the dialog asking for root permission shows up on the owner's user account. In SuperSu, only the owner can grant superuser privileges.
Sent from my Nexus 4
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Should probably ask in the n7 forum...
Sent from my Nexus 10 using xda app-developers app
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
The SoC in the Nexus 7 is Tegra 3, which has an ARM processor. You're fine.
Sent from my Nexus 10
Vlad7777 said:
Is Superuser 3.3 good for Nexus7? the file says "arm" - Nexus 7 is not an arm processor...
Click to expand...
Click to collapse
Lol of course n7 has an arm cpu!
For android phones and tablets, there's arm, mips, and x86. Any good android will 98% likely be arm. Motorola released an x86 (Intel) phone, and I'm sure there's a few other ones out there. And if you have mips, you probably got a cheapy Chinese tablet. xP
Swiped from my Nexus 10 using xda-developers app
Sorry for hijacking.
My main reason for root is to restore application data. Will I be able to restore the data on both the primary user and also the secondary user if I have root (either through the main or secondary user)
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
1234556789 said:
Did i do something wrong?
I had supersu installt- and need multiuser acsess . So i install Superuser in recovery with the zipfile .
But now no root app will work- with no user.:crying:
notice main user by starting: sorry i cant get root.... this was a try by /system/bin/su .
2 notice by superuser -on screen and in the log: superuser rights of ..app... are denied.
What do i do now ?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
KlipperKyle said:
It sounds like the zips don't play very well together.
Boot into recovery.
Mount /system
Delete /system/app/Superuser.apk
Delete /system/bin/su (if it exists)
Delete /system/xbin/su (if it exists)
Clear the Dalvik cache to err on the safe side.
You should now be unrooted. (In fact you could boot up, and you should see there is no superuser app installed)
Now, just flash the superuser zip again to root your device.
Click to expand...
Click to collapse
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
1234556789 said:
Thanks for it- but how i delete the files? On backup+restore i only can delete backups. Am i blind?
..............................................................................................................
edit: Tried a solution with nexus toolkit 4.2 i root once more, install superuser und install theupdate to 3.3.
get root for the main user- rootapps work-
but only the main user had root- i tried the update fixer -....gaining root acsess...fail.
so what is wrong?- had anybody a solution?
Kind regards
gandalf
Click to expand...
Click to collapse
It sounds like you have Superuser 3.3 installed and working, right? In order to use Superuser 3.3 with another user account, you need to go to its preferences and change Multi-user Mode to something other than "Owner Only."
"Owner only" means that only the owner can su.
"Owner controlled" means that the owner is the only one who can set and deny root permissions. Any filters are applied to all users.
"User controlled" means that each user can define allow/deny filters. Only use this option if you really trust other users.
Don't update to the version of Superuser on the Play Store. The version on the Play Store is 3.1.3. You already have 3.3 flashed on your system partition. Because you won't need the version on the Play Store, you can also stay away from ChainsDD's Superuser Update Fixer. (The update fixer is for an entirely different issue than the one you have.)
If you have installed these packages, you should uninstall them.
For future reference:
I should have been clearer about deleting files in custom recoveries. If you use TWRP, there is a built-in file manager under the Advanced menu. If you use ClockworkMod, you should use ADB commands: (ADB is a tool found in the Android SDK)
Code:
adb shell
cd /system
ls -al
[I](You should see a bunch of directories. If not, make sure /system is mounted.
This is an option in one of the recovery menus; I can't remember which
one offhand.)[/I]
rm app/Superuser.apk
rm bin/su
rm xbin/su
Then reflash the Superuser zip.
Related
Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
I believe Stericson has an app out that installs busy box for you with a single click. Just search "Busy box" in the market and it should come up. Not sure as to whether or not it works on the Incredible, as I've an Evo, but it should.
I tried that but it failed saying either I it couldn't remount or I wasn't rooted.
Sent from my ADR6300 using XDA App
bradatz said:
Does an update.zip exist for the incredible to add busybox to a stock rooted Rom? Or is there anyone willing to make one? I found one for the hero where they stripped down a rom and just left busybox, apps2sd, and Su. It would be greatly appreciated by many noobs like myself.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I think the unrevoked tool installs it for you.
I'll try that again, but I used 3.0 to root it. Maybe 3.1 will install it, I thought that was only windows fixes from 3.0
maybe
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Nice call!!! Worked like a charm. Thx.
NO
ejkeebler said:
kind of a rookie here, but couldn't you just install titanium backup and then click the problems button. I think it downloads and install busybox??
Click to expand...
Click to collapse
Wouldn't be permenant since NAND is still locked. Would lose it after reboot and have to do same thing over and over after every reboot.
http://www.unrevoked.com/incredible/payload-update.zip
Apply this payload-update.zip and it will install busybox. Just go to recovery and choose install zip from SD card and then choose this one
Then to test
go to cmd prompt
type adb shell
then when in shell type
busybox and you will see its now installed.
If you want the latest busybox, I've attached 1.16.2 freshly compiled.
One issue I ran into was that all the info on the forums has busybox being installed in /system/xbin. The PATH variable has /system/bin before /system/xbin, so that means the original symlinks to "toolbox" are getting picked up first - I don't know if I'm the only one who was annoyed by ls -al returning "-al: No such file or directory"
I guess "toolbox" didn't support this, so you can either install busybox to /system/bin, or leave it in /system/xbin and create a symlink called toolbox in /system/bin that points to busybox in /system/xbin.
As usual, backup your "toolbox" binary first before removing it from /system/bin.
Now ls -al returns a correct listing and I see no app breakage by the symlink method - Ti Backup runs just fine without needing to install its own busybox.
*edit - I guess this doesn't really answer the OP, but I figured I would share this anyway.
ok so I found a side effect - WiFi doesnt work after this. There seems to be a problem with dhcpcd and the new busybox, even though external dhcp support was compiled in...guess I've got some digging to do...
http://codehydra.com/Dinc/RootStock/roto-rooter.zip
that is a busybox install I ripped out of a N1 froyo root update.zip Cyanogen did, modded for the D-Inc.
Seems to work well for me.
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Not Really
... but it does NOT install the newest busybox; just one which is compatible with Titanium Backup.
Busybox.net shows v1.17 is the latest (unstable) release, and v1.16.2 is the latest stable. Titanium Backup pushes something in the v1.15 area.
http://www.busybox.net/
Also when I did it through titanium and went to busybox to install latest it said my system had none.
I have a busybox 1.16.2 version that I ripped from one of the posted ROMs that I can attach. It works on the Inc, and I think the whole DHCP / resolv.conf thing works too. At least it's the only version I tried where I can get wget working properly. You may need to create /system/etc/resolv.conf with some valid nameservers first though. Let me know if you want me to post it.
Hmm, nevermind. I tried with the busybox version I have, and WiFi does not get an IP address. Seems to be the same problem.
If you track it down, when you compile your version check if wget works properly also. There were some issues with that and DNS lookups. Don't forget you may need a valid resolv.conf.
Joe92T said:
the easy way is just to install titanium backup from the market and then click problems and it will install busybox for you in like 5 seconds
Click to expand...
Click to collapse
I second this , I used ones off the rooting forums and it never quite worked right until I let titanium backup install it for me. Also its much easier than pushing files to your device if you are unfamiliar with doing it, because you can download tb from market and it does the work for you
Sent from my ADR6300 using Tapatalk
Easiest way to stay current is to install the Stericson app. It can't install it for you due to the NAND lock, but
1) It's trivial to extract it and install manually from the .apk file.
2) It will give you an easy notification via the marketplace that a new version is available.
Who is affected? All devices pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Flash this with ClockWorkMod.... this is for any Pre Gingerbread ROM.... ie TNT anything, VEGAn 5.1.1 and below, Zpad anything, GAdam anything.
This is not necessary for any ROMS based off Gingerbread AOSP or CM7. Including VEGAn-TAB Experimentals.
Be Safe.
Even More Details here: http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
I checked out the zip and it just adds a blank text file (0 bytes) called profile to the /system/bin folder. So I am not sure what the fix is?
**EDIT** Nevermind it is a dummy file meant to prevent the virus. Thanks to the OP for providing this.
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Nasty stuff. I would say this patch is high priority and I'm already going through my own ROMs to add it in.
http://forum.xda-developers.com/showthread.php?t=977154
Link above has info on creating the file manually.
Jim
fyi -
http://www.pcworld.com/article/221213/keep_malware_off_your_android_phone_5_quick_tips.html
Lookout mobile security . In case you cannot find it via the market.
http://www.getjar.com/Lookout-Mobile-Security-with-Antivirus
Edit. I just installed the lookout app to scan my tab, everything was fine and then, i un-installed it since it was running on the background and taking 10% of the cpu..
Anyways, a nice app that can be used to do a quick scan..
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
xmr405o said:
I don't have a stock gtab but I'll ask anyways... how can our stock rom users be protected? Is there an alternate method?
Edit just saw the manual process. Im guess that's the way to go.
Click to expand...
Click to collapse
I'd curious to see what all the vendors are going to do about this. Granted, they could just say that the Market is not there, but regardless the security hole is still there and needs to be plugged up.
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
jimcpl said:
Hi,
I hope that this isn't too offtopic, but I was trying to create /system/bin/profile using a term and su, and when i went into root explorer to make /system/bin R/W, root explorer showed the dir as R/W already, and as mounted on /dev/loop9.
Is that normal?
I haven't installed dataloop, at least intentionally, so it seems strange that /system/bin would be mounted there, plus it being R/W by default?
FYI, I use z4root to get temp root. Could that be why /system/bin is R/W?
Then again, that wouldn't explain the /dev/loop9 mount ...
Jim
Click to expand...
Click to collapse
Hi,
Creating the profile file manually, it wouldn't persist,i.e., it was gone after rebooting, so I installed gojimi's zip usung CWM, and that worked.
I also did a mount w/o getting temp root, and /system/bin is not on /dev/loop9, so I'm guessing that when z4root sets temp root, it might be remounting /system/bin on /dev/loop9 itself.
Jim
You would have to download one of those sketchy apps to really be affected anyways, right? Who would do that?!
Appreciate the patch. This highlights the two problems with android though, google fixed this security issue in 2.2.2, but most carriers still haven't released that update. And the market needs some oversight, not authoritarian apple like, but some.
Sent from my T-Mobile G2 using XDA App
Is it possible to sticky this thread
Mods is it possible to sticky this thread so that it is easily visible.
Thanks
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Doctor LeVa said:
Hello guys. Is there a way to find out if our tablet is infected or not?
I mean if we have installed any of the apps in the list that automatically means that we are infected or not?
If infected what is preferred to do wipe the tablet or go back to stock rom??
Is there any manual for windows 7 noobies users?
Thanks.
Click to expand...
Click to collapse
Please read the thread completely, it is stated you can download lookout security to run a scan to see if you are infected.
downloading.....see what happens
There is a DroidDreamKiller app that allows you to check to see if you are already infected and install the patch. There is also a beta test app that gives you other information. Just search the market for DroidDreamKiller.
To devs: Thank You
TO Everyone else DO THIS ASAP
How do I flash the zip file after downloading it?
Thanks
Start cwm using volume up while powering on.
Once menu comes up select install zip using vol buttons
Use home to select.
Navigate to where you saved zip file
Select it with home button
Once install complete reboot from cwmod
MODs Please make this a sticky . It is being overlooked.
Now I am a very avid linux user (used the terminal a time or two) and I bought an acer a500 yesterday. This is my first android device and the first 2 things I did were update it and root it with iconia-root1.3 (gingerbreak didn't work). Now I have 3.1 and the root checker says that I have root. And the busybox installer says I have busybox installed.
Now this is where I get lost...
The root checker says I have root but not /system/bin/su or /sbin/su. Why would I have root if I don't have the application to switch users? Also it has su in /system/xbin but it won't let me move anything to /system/bin (which I assumed I could do as root??). So is root checker giving a false positive or what? and why can't I move any files above the directory /mnt (I'm using astro)? Do I have to selectively give certain apps root or what?
Also I need someone to explain this to me. Why do we need to root it if all of the applications are already in the android marketplace? Do they allow applications to be uploaded to the marketplace that won't work on non-rooted devices?? That seems like there would be a separate marketplace for rooted-only apps like cydia on iOS.
A quick reply: 'Root' allows you to have read/write access on /system/ . After root, you can add/remove any apps in /system/app, also, after root, you can flash CWM, you can then flash custom rom and kernel ... bla bla bla ~
Root is somehow different from 'jailbreak' in iOS. I think you could find more information on google. Cheers.
ardatdat said:
A quick reply: 'Root' allows you to have read/write access on /system/ . After root, you can add/remove any apps in /system/app, also, after root, you can flash CWM, you can then flash custom rom and kernel ... bla bla bla ~
Root is somehow different from 'jailbreak' in iOS. I think you could find more information on google. Cheers.
Click to expand...
Click to collapse
Root doesn't give you superuser(root user) access? I had always assumed that was the case, which means you can do any damn thing you please. Obviously you can't write to ro filesystems, but you could always remount them.
snowman4839 said:
Now this is where I get lost...
The root checker says I have root but not /system/bin/su or /sbin/su. Why would I have root if I don't have the application to switch users? Also it has su in /system/xbin but it won't let me move anything to /system/bin (which I assumed I could do as root??). So is root checker giving a false positive or what? and why can't I move any files above the directory /mnt (I'm using astro)? Do I have to selectively give certain apps root or what?
Also I need someone to explain this to me. Why do we need to root it if all of the applications are already in the android marketplace? Do they allow applications to be uploaded to the marketplace that won't work on non-rooted devices?? That seems like there would be a separate marketplace for rooted-only apps like cydia on iOS.
Click to expand...
Click to collapse
1.) The root app is in /system/app/ and the binary is in /system/xbin/ so you do have root.
2.) You won't be able to just write to any of those folders. You either have to remount them to be writable and use adb or use an app like root explorer that lets you remount on the fly and edit the files.
The same answer goes for the question why can't you move files to anything above /mnt. And yes to the second question. You'll have to set root permissions selectively.
Root doesn't have any effect on the marketplace or the apps you can download. This is not an iDevice.
Some apps need root to work (usually the ones that change system files) and that's why you have to have root. It's not necessary unless you either change system files or use an app that requires it (screen-shot apps, adfree,some file managers, reboot apps,...).
It's early so apologies for any mistakes I made. I hope that it's a little clearer now.
Hi all!
First off, I'm new to xda Developers so please excuse me if this is in the wrong forum! I thought I'd post information about a tool I wrote here which roots stock 4.0.3 leak on the A500, A501 and assumingly the A200 too. Its literally one click - just enable USB debugging. "ICS Root" also installs, optionally, FaceLock and Trebuchet (although FaceLock doesn't want to work. It lets you set it up though =P)
Since version 5.0.1 this also now works with the new 0.022.00 leak!
The full post is over at TegraOwners: http://forum.tegraowners.com/viewtopic.php?f=30&t=350
The only real system requirements are Windows (with .Net Framework 4) and an Iconia on the stock 4.0.3 leak. I hope somebody finds this useful its been tested by myself and a couple of TegraOwners users and it works well.
In terms of the technique used, it uses the great Jay Freeman's mempodroid exploit to gain root at which point it mounts /system rw and installs su, busybox and Superuser.apk so no real surprises there. Installing Trebuchet adds that apk to /system/app and installing FaceLock installs the apk to /system/app before installing the pittpatt folder to the flexrom (mounted as /system/vendor). I plan to open source it when all the requested features have been implemented and the code has been cleaned up.
Thanks!
~blackthund3r
EDIT 14/05/2012: ICS Root 7 is out enjoy!
Sent from my A500 using Tapatalk
cwm version?
why would it not work with cwm version?
With this tool does system remain writeable after rooting?
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
lowsum said:
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
Click to expand...
Click to collapse
If you are on the cwm with the HC boot loader it should work as Its Magic will be run..
if you are on the new boot loader as in the full non modded leak.. It will give you secure boot error ..
The new boot loader Blocks its magic.
Thanks
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
JeanBubu said:
why would it not work with cwm version?
Click to expand...
Click to collapse
It would but the cwm one, afaik, is prerooted?
Sent from my A500 using Tapatalk
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
nifterific said:
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
Click to expand...
Click to collapse
That's storage cos terminal works for me and running su in an adb shell works great too.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
# exit
[email protected]:/ $ su
#
Sent from my A500 using Tapatalk
SteamBishop said:
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
Click to expand...
Click to collapse
You're welcome and I'm glad it worked!
Sent from my A500 using Tapatalk
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
SteamBishop said:
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
Click to expand...
Click to collapse
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
Sorry for offending you and whoever else it did. Thank you for pointing that script out in that post. My intent was to offer a second comment to your assessment..
nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
New update out!!
blackthund3r said:
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Version 3 came out this morning
It features some bug fixes as well as a completely new remount menu which mounts /system rw properly on the fly. Tested with a busybox installer app
Enjoy!
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
paugustin said:
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
Click to expand...
Click to collapse
ah okay it appears a completely new leak has been released. It is possible that the mempodroid exploit has been patched up. I'm gonna look into it soon. I can't much tonight - I have school work. I'll see what can be done and what the differences between leaks are.
Sent from my A500 using Tapatalk
EDIT: mempodroid hasn't been patched See ICS Root v3.1
Hi blackthund3r
Thanks for the update 3.1 but could you please fix the problem on your hosting website? clicking on this file send to an error warning.
The other files can be downloaded though.
can someone post a mirror to the 3.1 version? current link is not working.
can somebody also confirm, if i root with this tool, i will be able to reinstall my clockworkmod recovery through 'acer recovery installer' and flash any other cwm rom? or do i have to downgrade to honeycomb 3.01, install iconiaroot for honeycomb and then acer recovery installer?
Gersma,
I'll be able to answer to your question as soon as I'll be able to download this tool and test it.
I am rooted and unlocked using the latest B29 update, US model. Most other root apps work fine, titanium, root explorer, etc. But when i try to add AdBlock it says failed to create host files, and something about creata sym link, but can't create it. Any ideas why this wont work? Thank you in advance
You need to disable Emmc write protection after root.. Search the forum they have given the commands to disable it thru terminal or adb
Sent from my ZTE A2017U using Tapatalk
adb shell reboot disemmcwp
Would write protection cause that error? I never had errors like that before disabling WP, just that the changes wouldn't stick.
Small Suggestion. Buy a Raspberry Pi 3 for $35. Install Pi-Hole as a DNS Server. . Configure the Raspberry Pi-Hole as the DNS on your router. Your entire Network devices are protected from Ads. Simple low cost solution to protect all devices in one shot.
Sent from my ZTE A2017U using Tapatalk
I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen
Kama45 said:
I am having the same problem, but I have tried reboot disemmcwp. SuperSu shows it has granted Adaway root, Adaway gives me the message "Either the su binary could not be found or you did not allow root permission for Adaway...."
I have reinstalled the app several times and deleted Adaway storage.
Is it possible I have BusyBox installed in the wrong location?
PS I am on Cyanogen
Click to expand...
Click to collapse
If you're on CM, you don't need to use SuperSU.
Settings > Developer Options > Root Access