So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
phillymade said:
Going to try this out. Been looking for a solution to this as well. Thanks.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 08:50 PM ---------- Previous post was at 08:43 PM ----------
So if Busy Box is installed to data, do I need to uninstall and install to system for this to work properly. As of now I'm getting a not found error.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
ArminasAnarion said:
Yeah you need your busybox installed on the system or it wont do anything
I have my busy box installed at /su/xbin
In terminal make sure you put su (then hit enter)
then type the command
If you put them together you get an error for some weird reason
Here is a picture of my busybox install https://www.dropbox.com/s/iwtutkots8bdd13/Screenshot_20160830-184451.png?dl=0
Click to expand...
Click to collapse
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
ps000000 said:
Will this thread make DPI change on rooted 7.0 possible ? :laugh:
Click to expand...
Click to collapse
Yeah dpi change it possible on Android 7! Currently running 420dpi!
phillymade said:
I did su then enter and got the error. perhaps it's where I have busy box installed.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Make sure you install busybox on /su
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
backslashV said:
This doesn’t work. After running this and then touch /sbin/su /system/bin/su /system/xbin/su
It says Read-only file system. Tried on the pixel c.
Click to expand...
Click to collapse
Wondering if this might help—running `blockdev --getro /dev/block/dm-0´ (my /system) returned “1” when I checked on Nexus 6P, and returned “0” after --setrw.
I wasn't able to sucessfully remount with the second command, however, due to ‘/system is busy’ or some such thing.
Code:
blockdev --setrw /dev/block/dm-0
mount -o remount,rw /system
You are a saint! While my /system was "writable" after root using Magisk, I couldn't change file permissions. Stumbled upon your method and was able to correct this, although I used my laptop. I had already installed busybox with Magisk, so I opened an adb shell, typed "su," then issued: busybox mount -o rw,remount system
Adaway, and AFWall+ is working fine and I was finally able to chmod 644 bootanimation.zip in /system/media of my Moto X Pure.
Thank you! :good:
Ericarthurc said:
So with Android 7 there seems to be a change in the way the system partition works and I tried a ton of ways to make my /system partition as writable. I tried an app, I tried terminal commands, and I tried a root file explorer. Nothing working; adaway wouldn't work without systemless zip flash. Emoji Switcher was also not working.
Well I found a fast and simple solution!
Install busy box and a terminal app
- Install busy box on system
- Open terminal app
- Run "su" (no quotes)
- Give the terminal app root access
- Then run "busybox mount -o rw,remount system" (no quotes)
- You should get no errors; it will actual do nothing, it will just go to the next line.
Now test that bad boy out and your system partition should be writeable. No more host errors in adaway!
Click to expand...
Click to collapse
* I installed BusyBox to /system/xbin using the app's install.
* I opened my Terminal app and typed su.
* I granted it access.
* I ran the exact command.
It just gave me another prompt as you said it should. But the File Manager that I have used on many rooted devices still won't let me check the box in its settings for Root Explore, even though it prompted me and I granted SuperUser access.
I don't get what I'm missing here.
UPDATE: I am now able to Apply Hosts in AdAway.
However, my File Manager that I have used in Root mode on every device still won't allow me to turn on "Root Explorer" mode. It did prompt me for SuperUser access and I did grant it (and double checked), but when I go to choose that option in the apps' Preferences, it says my device is not Rooted.
Any ideas?
Thank You.
Hi,
Okay, got it! Cancel my distress call.
Thank You!
Hi,
Had to redo my phone and while I can apply Hosts in AdAway (not being able to is a sure sign /System isn't Writable), when I try to make a change to my Build.Prop file found in /System it won't stay changed. I am using Nougat 7.0 with Magisk and every other Root app works fine.
Just for kicks, I tried running the commands you posted to see if it would help, but this time it didn't take the command (I do have BusyBox installed). Instead, it responded with; "Invalid Argument" as follows;
"mounting /dev/block/bootdevice/by-name/system on /system failed: Invalid Argument"
Then the prompt changed to "255|elsa:/ #"
Any ideas? It appears to see that BusyBox is installed, but it isn't working. Also, how do I check where my BusyBox is installed?
Thanks,
Dave
Related
Okay, so I've noticed that this rooting method is a little unconventional. It works through a compromised Fota.pkg which has setuid on /system/bin/sh as root. This is not a very safe, as any application that runs sh will gain root access to your system. Scary... :S Anyway, in order to fix this we need to take a few steps.
It is important that you do these in order, otherwise you may lose root access
Install a proper SU with whitelist
1. Download http://bit.ly/aWgALL
2. Unzip the system folder.
3.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push system/bin/su /sdcard/su
adb push system/app/Superuser.apk /sdcard/Superuser.apk
adb shell dd if=/sdcard/su of=/system/bin/su
adb shell dd if=/sdcard/Superuser.apk of=/system/app/Superuser.apk
adb shell chmod 6777 /system/bin/su
adb shell chmod 644 /system/app/Superuser.apk
4. Reboot your phone.
Fix sh to not setuid to root
1.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell chmod 0755 /system/bin/sh
Properly install busybox
1. Here, it's easier to look for the busybox installer app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
chai_archer said:
this might be stupid questions, i know. But where should I unzip the system folder that mentioned to? And where to type those command?
Click to expand...
Click to collapse
If you followed the root guide you can put it in the step 4 folder.
Then hit windows key + r and in the box type CMD
A console window comes up.
in the console window type cd <path.to.your.step.4.folder>
then go from there.
zephyrix said:
Properly install busybox
1. Here, it's easier to look for the busybox app from the market and then install from there. If you did everything correctly, then after you hit install in the busybox app a prompt will come up asking you to allow the app to have root. Hit allow.
You're done!
Click to expand...
Click to collapse
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
bcool15 said:
i did everything as mentioned but it dint ask me for permission wen installin busybox is it because i had it installed sometime before runnin this guide?
yea i knw im a noob after all
Click to expand...
Click to collapse
yep.
if you check the superuser app it should already be there.
zephyrix said:
yep.
if you check the superuser app it should already be there.
Click to expand...
Click to collapse
all i see in superuser app is titanium backup pro
that's strange. does busybox report that it's installed?
zephyrix said:
that's strange. does busybox report that it's installed?
Click to expand...
Click to collapse
nope it doesnt
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
unknown13x said:
well i tried all this and now i lost my root. Did EXACTLY what's written. Anyway to reverse this and get my root back?
Click to expand...
Click to collapse
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
bcool15 said:
i think i lost mine too but to reactivate there is command or prolly i just messed up summmwhere n redid my whole root with v3 update
Click to expand...
Click to collapse
use "su" to get root access... allow when the Superuser Whitelist notification pops up.
it worked for me....followed the steps, after i downloaded the busybox app i opened it and a box popped up "Superuser Request", it had discription of the busybox app and then asked whether to allow or deny the request....i then checked the superuser app and was able to see the busybox app in thr....
can anyone confirm if these steps were added in the new root method? please
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
root in adb
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
th4r said:
I tried this on the last root (ROOT_F2v2) and I lost root in adb..
I still had regular root
I had to revert it back with "chmod 6777 /system/bin/sh" to get adb do admin task again.. (I use adb regularly)
Does anyone know how to secure sh and still have root in adb?
Regards.
Click to expand...
Click to collapse
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Here are the answers....
bcool15 said:
can anyone confirm if these steps were added in the new root method? please
Click to expand...
Click to collapse
No they were not. The reason is that many of the rooting steps rely on a setuid "sh"
gfgodoy said:
I'd like to know that too, I mean, in 2v2 do we still need to do the whitelist thing?
Click to expand...
Click to collapse
Yes
Chillest said:
adb shell su
And after superuser popup add "unknown application" to the whitelist.
Click to expand...
Click to collapse
So what? The uid for the shell application launched after invoking "adb shell" is not going to match any of the installed applications anyways. The thing is that Superuser.apk installs a mechanism by which the user (human) can detect when an application is requesting root access. Based upon the nature of the application you may or may not want to grant root access. That is the whole point.
th4r said:
Yes that give me root in adb shell but adb is still running unprivileged.
I believe it's because we can't patch the bootloader yet, so we still have getprop ro.secure 1. :'(
I did a little script to toggle setuid on /system/bin/sh when I'm doing root stuff from adb
Sent from my rooted X10i
Click to expand...
Click to collapse
Oh yeah? I just use "su" whenever I want root access... and I didnt have to write any scripts to enable/disable it.
k1ckn1ck said:
I have installed this to protect the system.
The only concern I have is i cannot run for example my cleaning script.
If i type into cmd ;
"adb shell su" it comes up with a # and freezes. If i type in
"adb shell<enter>
su" it works fine. and i can paste all the commands in line by line.
If i do either in a bat or cmd file it crashes. How do i run scripts as su
Click to expand...
Click to collapse
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
j4mm3r said:
Then you shouldn't be rooting in the first place. Take my advice, lay off the rooting. It definitely doesn't have anything that will be of advantage to you.
Click to expand...
Click to collapse
easy now, it's a fair question, would be nice to be able to run cleaning scripts on a protected system. no need to be a prick
in answer to the question though, once the batch starts adb shell, it won't continue till that process ends
I did some googling for some comandline tools that might allow sending keystrokes to a process, but nothing easy appeared, looks like your only option is to use a linux friendly notepad to create some shell scripts you can execute from the sdcard. i.e. on device
su
chmod 755 /sdcard/myscript.sh
./sdcard/myscript.sh
easiest way to do scripts on a secured root IMO
Hi, I rooted my Vribrant, both ways (manually and with one click root). I installed terminal emulator. I tried the su command to check if I am root. The # appears normally. However I tried deleting a file with Root explorer, inside the system folder, and when I get back it's still there. I also tried deleting it manually from Terminal EMulator with these commands:
su
cd system/apps
rm Swype.apk
and I get this:
rm failed for Swype.apk, Read-only file system
I also tried:
su rm Swype.apk
and this is returned:
Permission denied.....
I also tried the exact same thing from adb shell (which I had to allow in superuser permissions program), but it gave me the exact same results. What's wrong? Am I doing something wrong? Thanks
In root explorer, try hitting the r/w button at the top and see if that works.
Sent from my SGH-T959 using XDA App
I know about the button. The strange thing is that inside system folder it grands me r/w permissions, and no matter how many times a press the r/o button it doesn't change. Still gives the results I said. However, besides root Explorer what's wrong with terminal emulator and adb?
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
rbirg said:
I'm not 100% sure how to mount as root in adb. I wish I knew myself heh.
Did any of those root methods install the superuser app?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes both methods installed the "Superuser Permission" app.
I7oobie said:
Terminal Emulator should return a "#" after typing "su"
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
It does normally.
linuxmotion said:
From a terminal write
adb root. (will give root)
adb remount. (will remount system as r/w)
adb shell cp /system/app/swype.apk /system/app/swype.apk.bak
Adb shell rm /system/app/swype.apk
This link is what i used to use to gain rw permissions
http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
Alternatively from terminal on the phone type
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Assuming your sys partition is mntblock3
Sent from Conical. 07
Click to expand...
Click to collapse
I tried the first method but it didn't work. When I entered adb root, it said "adbd cannot run as root in production builds". I searched a bit and found that I must have a rooted kernel for this to work. (I guess it's different from the root method I tried in "how to root vibrant").
Anyway the second way worked, where i replaced mntblock3 with stl9 for my phone. I tried the rm command and it worked! However as soon as I exited terminal, I couldn't delete other files. I had to retype the command. I can't do this everytime I need access in System folder. Why is this happenning? Does this have something to do with the fact that root explorer cannot change r/w to r/o mode while in system folder?
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Moved to Q&A, please post in the correct section.
s15274n said:
what if you open Superuser
Click on Root Explorer.
Click on Forget.
Open Root Explorer and grant Root Access and check to remember it.
work now?
Click to expand...
Click to collapse
No it didn't work. I also installed the latest version of SuperUser 2.3.6.1. But without a difference unfortunately.
What works for me, is installing sgs tools, and whenever I want to do write operations on system folder, run the appropriate script from sgs and then use root explorer......
Although I think there's something wrong? Why doesn't the mount r/w button work in root explorer, and why do I have to remount the file system through SGS tools, every time for it to work?
makes no sense to me either. Have you uninstalled RE and the installed it back granting root once reinstalled?
Yes several times.....
I am giving up. I just have to go through the whole process every time. I found some other people having this issue. I am on stock JI6 firmware. Maybe when I read a little bit more I will flash a custom rom.
Download and install Super Manager. Pretty handy program to use for Root users.
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
msnuser111 said:
I'm not sure what the issue is,but mine does it too. I'm running the "unofficial" froyo JK2 build,flashed via ODIN,and I'm having the same issues. root works,root file explorer is stuck in rw,won't let me switch to ro,and it can't do anything to files in / or /system. manually remounting it from terminal or sgs tools works.
Click to expand...
Click to collapse
At least I am not the only one with this problem.... haha
I forgot to mention that I use Root Explorer version 2.12.2
When I try a custom Rom I will post the results....
^ why not get the update, .4 is the most recent build. Do you have an illegal copy?
It's not only root explorer. It happens with other file explorers too like android mate and super manager... Inside system folder whatever, I do doesn't happen unless I unmount and remount like before
Can someone knowledgeable please submit a detailed post, which instructs how to remove any files added during the Root Process, as well as any other file permission changes or modifications of any other type?
I see many half assed posts in these forums made by unqualified members, which are nothing but a waste of time and clutter this great resource. I would appreciate it if this post could be addressed by those who truly understand this process.
The file that was used to Root the SCH-i905 from Verizon was the one attached to this post.
Thanks in advance! This could be a great learning tool if answered properly.
Can some one please respond? Or is it that everyone is too scared to post helpful information?
Well, since no one was of any assistance, I was forced to piece together information and come to an understanding of how this works, and how to fully reverse what was done by this Root Update.
To begin, I would like to mention, that removing Superuser.apk from the /system/app folder, along with 'su' from the /system/bin folder, will negate your Root Access, and put you back to your default levels of access. This will prevent Mobile Device Management Solutions, such as AirWatch, Zenprise, or MobileIron from detecting your device as being compromised.
I was not successful in removing these two files via the ADB shell, however I was successful when using a Terminal Emulator App on the Device itself.
1.) I began by installing a free Terminal Emulator from the Android Market.
2.) Launched the Terminal Emulator and typed 'su' , then pressed Enter to gain Root Shell Privileges.
3.) From the Root Shell, I typed the following commands to remount the '/System' Directory to gain Read/Write Access.
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
4.) I typed the following commands to remove 'Superuser.apk' and 'su'.
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
5.) Type the following command to remount the '/System' Directory back to Read Only.
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
6.) Sync your device with Google under Settings / Accounts & Sync.
7.) Reboot your device, and you are good to go.
It might be a good practice to perform a Factory Reset on your device after doing this, however this is not completely necessary. I tested the Air-Watch Agent installation after performing the procedure mentioned above, and the Air-Watch console no longer detected my device as being compromised.
I will add that on my sch-i905 I found the bin directory under system not under system/app. For me, replacing cd /system/app/bin with cd /system/bin did the trick but the rest worked a treat - thanks for the post!
Thanks for pointing out my typo. I corrected the path in my Post.
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
tbcpn said:
Thanks for this.
Does this restore the stock recovery that was replaced with Clockwork when the kernel.zip and recovery.zip files were flashed to obtain root? I do not totally understand the relationship between Superuser and CWR. I found a reference to a flashable stock recovery in post 14 here http://forum.xda-developers.com/showthread.php?t=1205639&page=2 , but I'm unclear on the instructions.
I'm trying to understand how, if possible, to return my VZW LTE Tab to out-of-the-box stock, if desired.
Rooted: Droid Incredible / Droid X / Thunderbolt / 3G-4G Xoom / Galaxy Tab 10.1 LTE
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Stock Recovery isn't required to Root the device. However, if you wish to install CWM via ROM Manager from the Android Market, Root Permissions are required.
If you use an ODIN Flash of CWM, there is no need for Root Permissions because you are flashing via ODIN.
The stock recovery zip file that you referenced in the other post should be fine.
Just use ODIN to Flash back to Stock Recovery and use the process that I mentioned to remove Root Permissions and Super User, and you should be all set to return your device after a Factory Wipe.
Cheers!
~Scott~ said:
I have the Superuser icon showing up in my apps folder, but I don't appear to have root access. I can't su in the terminal emulator nor can I load apps that require root access. I also tried removing the Superuser.apk via a file manager with no luck.
Any idea how to remove this thing if I don't actually have root access?
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
OK, I rooted again and fixed whatever was broken. Then I was able to apply these commands to unroot the device.
Thank you!
Click to expand...
Click to collapse
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
Scott,
I'm sorry for just seeing your post. I'm sure that you figured it out by now. You need to gain Root Access to your device again to remove Super User. You are in a Catch22.
If you are using an SCH-I905, Root your device, then download Script Manager from the Android Market.
Run this very simple Bash Script that I wrote to remove Root and Super User.
Paste this into notepad and save it as Unroot.sh then run with Script Manager.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/app
rm Superuser.apk
cd /system/bin
rm su
mount -o ro,remount -t yaffs2 /dev/block/mtdblock3 /system
Be sure to run the Script as Root from within Script Manager. The app will kind of freeze up as soon as it runs, which is normal. This will certainly take care of your problem.
Thanks for your post of stockrec in a different post. You saved me a month ago with that one.
Cheers!
Will Samsung know if I rooted my GT 10.1 LTE after using these commands, and sending in for warranty?
Does anyone know how often airwatch checks for the root? anyway to bypass the checks?
Is this the same for the US Cellular 4G Tablet? I have been reading and all that I have found was WiFi only files. Which if I were to root with those I lose the 4G radio.
Perfect.. Just what I need. Thanks
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
franky_402 said:
ok guys so i wanted to post this because ive been sitting here for two days trying to regain root on my prime after doing a factory reset to speed it up! It was pretty damn slow so i bit the bullet and its much faster now but unfortunately no root I tried to use the debugfs root method and it wasnt working multiple errors and still no root. Now a few things first i had used voodoo in the past to protect root, it sorta worked, voodoo stated my device had root but no program could actually get root. Also like i said the debugfs method was a no go and a few other options i tried. Im currently locked and rooted with full permissions. These are not my instructions but they solved my problem way too easily so i had to share. I found this over in the tf300 forums at this thread Nooktablets tf300 rooting thread i dont know if this will work if u have never rooted or never once backed up.. But i was having problems with errors in other methods so try it out and let me know how it works..
directions:
1) Download the unsure su from here and put it somewhere on your C Drive. It will be used in the following push step (Assuming windows) (This is a WIDE OPEN su without any controls). (sparky root i believe?)
https://www.dropbox.com/sh/jcpilpgoeta516e/tCB-Ep-3YQ
2) start a CMD window and logon to adb
3) su -
4) verify you have root:
id
uid=0(root) gid=0(root)........
If you don't you can try these instead of 'su':
"/system/su-backup" or "/system/su_backup"
5) remount system as RW:
mount -o remount,rw /dev/block/mmcblk0p1 /system
6) make a backup of current su just in case in adb
cat /system/bin/su > /system/bin/su1
7) open a new CMD window and push the su binary from step 1 to the sdcard using the path from where ever you put it.
adb push c:\<some path>\su /sdcard/
8) Then copy it to /system/bin from the adb session where you su'd.
cat /sdcard/su > /system/bin/su
9) Change permissions for SU
chmod 6755 /system/bin/su
10) download superuser (NOT SUPERSU) from play store if you do not have it already.
11) have superuser upgrade the su binary. It may fail to remount system as RO. Just rerun the update in superuser and it will work the 2nd time. You don't need to remount system as RO manually since superuser update of SU will do that for you.
12) congrats. your now rerooted.
13) remove the backup after you know your OKAY.
mount -o remount,rw /dev/block/mmcblk0p1 /system
rm /system/bin/su1
mount -o remount,ro /dev/block/mmcblk0p1 /system
Click to expand...
Click to collapse
This procedure worked for my TF201 with partial root after updating to 4.1.1. The only issue was step 11, the forced update of Superuser's su binary. The message was “Making sure new su works..." but the result after several minutes was still "Waiting....". Should I rerun the forced su update? Despite this Vodoo OTA Rootkeeper did restore root without problem and Root Checker says thumbs up.
At this point, is there anything to do like switching to SuperSU that would make the root more future-proof?
Thank You! I have been trying to regain root after jellybean ota on my Motorola Atrix HD for the last week and a half. Finally success . I cant thank you enough!
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
You should be able to switch to a different root app. Never used this method but I have switched from superuser to supersu. Install superuser and run the binary update. Should tell you your binary is out of date with the name of the binary for the other root app. Update and reboot, then go back to superuser and check the binary update again. If it says it's up to date, uninstall the old root app and move superuser to /system/app. Reboot and you're good to go!
Sent from my Atrix HD MAXX
i think i tried that. istalling and uninstalling and subdstituting su and supersu. was not updating no matter what. also my adb push was not working so i copy pasted the su with my laptop while in adb shell. also updated su binary while in shell. it was already a system app from my previous attempts. anyway im good now
any one get it to work with no root/first time root? my prime wouldnt update via ota once on ics so i had to use the sd card update method to update. and from then on i never rooted again i then updated to jb and until 2 days ago i wanted to reroot but noticed there was no root method for jb yet. voodo root keeper just has super user app installed and ./system supports root protection both checked.
I'm in the same situation as fcortes626, I had to upgrade via sdcard method, and voodoo root keeper didn't maintain the root. I can't find any su backup in my filesystem.
I wonder if we can downgrade using the sd card update then root and go on from there........?
Sent from my SGH-T999 using xda app-developers app
I cannot get the ad blocking host files to stick with this device. I have tried both Adfree Android and Adaway. The host files won't survive a reboot. Sometimes, I apply them and they revert back after a few hours of use. I am just wondering if anyone else has experienced this issue on this device. SU is functioning properly.
Peace
Not exactly the same, but I noticed any app I remove via Titanium Backup gets restored on reboot as well.
Both of these actions require writing to /system, which cannot be done with android booted up, until we have s-off.
Every time I try to write to system (On accident by running some root app without thinking about it) my device reboots. I figured that was normal for a rooted S-on device. That doesn't happen to y'all?
trickster2369 said:
Both of these actions require writing to /system, which cannot be done with android booted up, until we have s-off.
Click to expand...
Click to collapse
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Irieone said:
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Click to expand...
Click to collapse
you can not write to /system with android booted up.
So you can flash a rom in recovery but you cant edit anything in /system while in android
Irieone said:
I am pretty sure I was able to do this on the Rezound prior to S off. Also, how can one flash a ROM if your not able to write to the system?
I just want to understand this a little bit better. Thanks.
Click to expand...
Click to collapse
On all the newer phones, HTC (or Verizon) write-locked \system while the phone is booted in android. :good: But you're right, on the Rezound, you could write to \system while still S-ON.
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
nrfitchett4 said:
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
Click to expand...
Click to collapse
This has already been done my friend look in the development section. Also I think I saw a script that you can run in recovery that ads ad blocking hosts! CHEERS:highfive:
Here you go:
ad block is on that other site => http://rootzwiki.com/topic/36775-mod-debloater-adblock-restore-v3/
and theres some debloat love here in development => http://forum.xda-developers.com/showthread.php?t=2012388
nrfitchett4 said:
so I guess to debloat, someone will have to make one of those debloating tools that delete through adb.
Click to expand...
Click to collapse
Freezing in TiBu appears to work.
Going to have a go with AdBlock Plus since its supposed to work without root.
https://play.google.com/store/apps/details?id=org.adblockplus.android&feature=nav_result#?t=W251bGwsMSwyLDNd
Irieone said:
Going to have a go with AdBlock Plus since its supposed to work without root.
https://play.google.com/store/apps/details?id=org.adblockplus.android&feature=nav_result#?t=W251bGwsMSwyLDNd
Click to expand...
Click to collapse
Screw that who wants that running in the background, run AdFree and update hosts, hook up USB with debugging on and use ADB:
"adb shell" then "su" and grant yourself root. Then "cp /system/etc/hosts /sdcard" then type "exit" and "exit" to get out of the shell.
Then run "adb reboot recovery" and mount /system partition in recovery. Then "adb shell" and "cp /sdcard/hosts /system/etc/hosts" -- exit shell and reboot
Done
Do this or just push the host file http://db.tt/LQAUEcZM to /system/etc/ with the built in TWRP file manager if you don't want to use ADB.
Nowak4G said:
Do this or just push the host file http://db.tt/LQAUEcZM to /system/etc/ with the built in TWRP file manager if you don't want to use ADB.
Click to expand...
Click to collapse
Is anybody having trouble creating this symlink as instructed in AdAway on their Droid DNA?
I type the command and all I get is "ln: /system/etc/hosts: File exists"
I exit, reboot and the app still tells me the symlink is missing.
I'll be the first to admit my adb-fu is weak, probably my fault.
Edit: so, I did it the other way. When the app tells you the symlink failed it still creates a hosts file in data/data. I used TWRP/Advanced/File Manager to move this into system/etc.
Still, it would be nice to get the symlink working and have AdAway update automatically rather than having to go through this process periodically.
disc0rdian said:
Screw that who wants that running in the background, run AdFree and update hosts, hook up USB with debugging on and use ADB:
"adb shell" then "su" and grant yourself root. Then "cp /system/etc/hosts /sdcard" then type "exit" and "exit" to get out of the shell.
Then run "adb reboot recovery" and mount /system partition in recovery. Then "adb shell" and "cp /sdcard/hosts /system/etc/hosts" -- exit shell and reboot
Done
Click to expand...
Click to collapse
This is exactly what I did. I used root explorer to copy the host file from /system/etc and pasted it on the sdcard
Rebooted into recovery, mounted /sdcard and /system and ran adb to push the file
viola! done
^^
I think that's basically doing the same thing I did, but still the symlink would be nice so it could be automatically updated.
---------- Post added at 09:02 PM ---------- Previous post was at 08:44 PM ----------
OK, got a little tech support off the DNA IRC. As I suspected, I'm just dumb
Make sure to delete any existing system/etc/hosts and data/data/hosts before you run the command.
Works fine now!
Now that we have s-off, what are you guys using to block ads?
andyroidna said:
Now that we have s-off, what are you guys using to block ads?
Click to expand...
Click to collapse
The same thing we've been doing for the past 3 months. Nothing had changed in that respect since kernels with system write enabled came out.
Sent from my HTC6435LVW using xda app-developers app