Simple to use. Useful for those who want ROOT access via ADB or Device for Backup, etc. It is a modified scripts from Doomlord and some1 in the CDMA threads...
Prerequisites
1) Uninstall all HTC Sync & Drivers
2) Download and install http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
3) Make sure your device Display is set to NEVER TURN OFF & not locked in the lockscreen
Instructions
1. Download attachment
2. Extract to C:\
3. Execute file Step 1
4. Execute file Step 2. If doesnt work, go to C:\files and execute Step 2
5. Remount SD card again from the DEVICE SETTINGS page
This will work for all devices not limited to EVO 3D.
For locked bootloaders (any versions), this will result in a temporary ROOT access, and will be lost after reboot.
Please feedback for whichever H-Boot this works on.
Thanks to our following comrades...
Team Revolutionary with their ZergRush exploit
http://forum.xda-developers.com/show...1296916&page=2
DoomLord with the automated script
http://forum.xda-developers.com/show....php?t=1321582
For the third guy I cant remember where.. maybe the CDMA section with the permatemproot stuff..
With this script, Titanium Backup and Root Explorer will definitely work even on LOCKED bootloaders (will lose root after reboot, just rerun the script)
For problems especially with SUPERUSER FCs, please download and run the .bat file in the UNROOT.zip. This will clean the system of all old temp root stuffs like superusers, etc...
Appreciate your thanks..
i dun understand why but it didn't work as did ur last tool, it always saids adb server out-of-date, re running or sth, it does the same in every step, and when it comes to moving files/manipulating permissions, i just get loads of errors
I'm on HBOOT 1.49.0012
P.S. i cant unlock using HTC Unlock method too no matter how many times i try (i read the instructions carefully and followed them closely) but still got unlock token check failed error......
tomanlam said:
i dun understand why but it didn't work as did ur last tool, it always saids adb server out-of-date, re running or sth, it does the same in every step, and when it comes to moving files/manipulating permissions, i just get loads of errors
I'm on HBOOT 1.49.0012
P.S. i cant unlock using HTC Unlock method too no matter how many times i try (i read the instructions carefully and followed them closely) but still got unlock token check failed error......
Click to expand...
Click to collapse
Reboot your device and try again... see edited post above..
Not sure about HTC Unlock method...
For UNLOCKED evos, it will give permanent ROOT access
For LOCKED evos, it will give temporary ROOT access
If you have problem unlocking, try grabbing a RUU file here and reflash your ROM... maybe factory reset wont hurt either...
it has run thru all the process with success, but when i try to open root explorer it show superuser force close???
looknsee said:
it has run thru all the process with success, but when i try to open root explorer it show superuser force close???
Click to expand...
Click to collapse
Also the Same thing happened to me !!!!
Yup, not working here either.
It says it installs everything ok, but when I go to update the su binary, it force closes out. When I use TI backup, it says I don't have root access.
Hope this helps so that we can at least get temp root. I just want to remove the bloatware!
Thanks for the hard work in any event!
tried this on sensation xl and it worked, root access to some apps like root explorer but terminal says access denied. it seems to unmount the internal sd card which programs need to run and only a reboot remounts sdcard but obviously root is gone after reboot. hope one of the XL devs can use this to create a working solution for our XL
ObsoleteSoldier said:
Yup, not working here either.
It says it installs everything ok, but when I go to update the su binary, it force closes out. When I use TI backup, it says I don't have root access.
Hope this helps so that we can at least get temp root. I just want to remove the bloatware!
Thanks for the hard work in any event!
Click to expand...
Click to collapse
dont need to update the SU binary.. just run the scripts and they are good to go...
however, SYSTEM/APP are in locked partition of the bootloader.. you may need to unlock your bootloader first.. but you may remove some in the Data/app llike gmail and stuffs (i prefer Exchange email than using Gmail app)
shingers5 said:
tried this on sensation xl and it worked, root access to some apps like root explorer but terminal says access denied. it seems to unmount the internal sd card which programs need to run and only a reboot remounts sdcard but obviously root is gone after reboot. hope one of the XL devs can use this to create a working solution for our XL
Click to expand...
Click to collapse
If your bootloader is unlocked, then you may be able to reboot and still have root..
Can I use these scripts to get root access without s-off ?
wasdly said:
Can I use these scripts to get root access without s-off ?
Click to expand...
Click to collapse
S-OFF not required.
FULL ROOT if UNLOCKED BOOTLOADERS
TEMP ROOT if LOCKED BOOTLOADERS
Reason : Files in SYSTEM partition are locked, hence changes made are temporary and will be lost after reboot
Yep full root acheived with u.locked bootloader on HTC sensation xl. Confirmed and working
Sent from my HTC Nexus One using xda premium
Just tried on my HK Evo3D (HBoot 1.49.0012, completely stock, no HTC unlock) and it works. But it took me a few trials to get it working.
For those who have problems with the script (e.g., permission problems during the script) try:
(In the following steps, make sure ur evo3d is disconnected from ur pc when you reboot it. Just to make sure that it is clean.)
1) reboot your phone
2) run the unroot script
3) reboot once more
4) run the root script "Step 1.bat"
5) *** go into the "files" directory ***, and run the "Step 2.bat"
6) at this step you should see the superuser is installed (check the app drawer)
7) go to Settings to mount your sd card
I have managed to root it and run through a titanium backup successfully. Thanks for the great work!
Though temp root is gained, system is still mounted as read-only
tried these, neither one worked:
1) adb remount
"remount failed: Read-only file system"
2) su; busybox mount -o remount,rw /system
No messages, no errors. But still system is in ro mode:
# busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
# mount | grep system
mount | grep system
/dev/block/mmcblk0p22 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
3) su; fixit; busybox mount -o remount,rw /system
Same result.
Seems, after running "Step 1.bat", the /system is temporary mounted as "rw", (that's why the script could complete without warnings/errors). But after Step 2 finishes, /system is back to "ro" no matter what...
Any insights?
ktchana said:
Just tried on my HK Evo3D (HBoot 1.49.0012, completely stock, no HTC unlock) and it works. But it took me a few trials to get it working.
For those who have problems with the script (e.g., permission problems during the script) try:
(In the following steps, make sure ur evo3d is disconnected from ur pc when you reboot it. Just to make sure that it is clean.)
1) reboot your phone
2) run the unroot script
3) reboot once more
4) run the root script "Step 1.bat"
5) *** go into the "files" directory ***, and run the "Step 2.bat"
6) at this step you should see the superuser is installed (check the app drawer)
7) go to Settings to mount your sd card
I have managed to root it and run through a titanium backup successfully. Thanks for the great work!
Click to expand...
Click to collapse
ktchana said:
Though temp root is gained, system is still mounted as read-only
tried these, neither one worked:
1) adb remount
"remount failed: Read-only file system"
2) su; busybox mount -o remount,rw /system
No messages, no errors. But still system is in ro mode:
# busybox mount -o remount,rw /system
busybox mount -o remount,rw /system
# mount | grep system
mount | grep system
/dev/block/mmcblk0p22 on /system type ext4 (ro,relatime,barrier=1,data=ordered)
3) su; fixit; busybox mount -o remount,rw /system
Same result.
Seems, after running "Step 1.bat", the /system is temporary mounted as "rw", (that's why the script could complete without warnings/errors). But after Step 2 finishes, /system is back to "ro" no matter what...
Any insights?
Click to expand...
Click to collapse
1) Reboot phone
2) Connect in DEBUG MODE
3) Run Step 1 script
4) Run Unroot script
5) Reboot phone
6) Connect in DEBUG MODE
7) Run Step 1
8) Run Step 2
You may have previously attempted some other methods, therefore you need to clean the system first...
If your bootloader is LOCKED, you still can gain TEMPORARY ROOT access and run you Titanium Backup (restore settings, data apps).. however, the SYSTEM partition is still locked, which means, whatever changes you done to the SYSTEM partition (like restoring some SYSTEM apps) will be lost after reboot.
I got forceclose with the superuser.
I dont know why, but i guess the root process was finished
Got temp root and su support with untampered stock (vodafone branding), unlocked bootloader HBoot 1.49.0018 on HTC EVO 3D GSM shooteru
System continues to be (expectedly) in ro mode.
Lost access to SD card, had to reboot to use it again...
Permanently disabled without any problems some apps that were bugging me - Thanks
Christoph
bdigitalstudio said:
1) Reboot phone
2) Connect in DEBUG MODE
3) Run Step 1 script
4) Run Unroot script
5) Reboot phone
6) Connect in DEBUG MODE
7) Run Step 1
8) Run Step 2
You may have previously attempted some other methods, therefore you need to clean the system first...
If your bootloader is LOCKED, you still can gain TEMPORARY ROOT access and run you Titanium Backup (restore settings, data apps).. however, the SYSTEM partition is still locked, which means, whatever changes you done to the SYSTEM partition (like restoring some SYSTEM apps) will be lost after reboot.
Click to expand...
Click to collapse
Thanks for your inputs. But my phone was completely stock and I have never tried other root methods before trying this one.
I observed that, /system actually get rw for a short time after the mount -o remount,rw command in step 1. But somehow it will get back to ro by itself. The time is unpredictable in a sense that sometimes step 1 script cannot finish successfully (cannot copy busybox, su to /system because it changes back to ro so quickly).
I know that the SYSTEM rw is just an overlay and all changes will be gone once rebooted. I am asking this because I just wonder if I could playaround and test something like changing fonts without s-off or HTC unlock.
---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------
-Ho- said:
I got forceclose with the superuser.
I dont know why, but i guess the root process was finished
Click to expand...
Click to collapse
After temp root, go to market and install superuser again. Then run apps like titanium backup and it should work. At least in my case.
---------- Post added at 05:18 AM ---------- Previous post was at 05:13 AM ----------
chw9999 said:
Got temp root and su support with untampered stock, unlocked bootloader HBoot 1.49.0018 on HTC EVO 3D GSM shooteru
System continues to be (expectedly) in ro mode.
Lost access to SD card, had to reboot to use it again...
Permanently disabled without any problems some apps that were bugging me - Thanks
Christoph
Click to expand...
Click to collapse
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
ktchana said:
Thanks for your inputs. But my phone was completely stock and I have never tried other root methods before trying this one.
I observed that, /system actually get rw for a short time after the mount -o remount,rw command in step 1. But somehow it will get back to ro by itself. The time is unpredictable in a sense that sometimes step 1 script cannot finish successfully (cannot copy busybox, su to /system because it changes back to ro so quickly).
I know that the SYSTEM rw is just an overlay and all changes will be gone once rebooted. I am asking this because I just wonder if I could playaround and test something like changing fonts without s-off or HTC unlock.
---------- Post added at 05:13 AM ---------- Previous post was at 05:10 AM ----------
After temp root, go to market and install superuser again. Then run apps like titanium backup and it should work. At least in my case.
---------- Post added at 05:18 AM ---------- Previous post was at 05:13 AM ----------
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
Click to expand...
Click to collapse
Re-do it again only the first time got FC from superuser
After i got the FC, i cleared the data of superuser
Everything seems work
Thanks
ktchana said:
After temp root the SD card is unmounted, that's why you can't use it. Did you go to Settings to mount the SD card again?
Click to expand...
Click to collapse
Yep, it dawned on me and I found that option - now I can use Titan to backup everything
Is there a possibility to add automatic remounting the SD into the script using adb? I am not really familiar with this...
Thanks again
Christoph
Related
This is how i managed to install the Google Maps 5.7.0 ownhere/Brut.all MOD which enables Navigation in countries where originally you cnt use this app. this is a modified version that seamlessly replaces the original app.
i tried to follow the instructions provided in the original thread but i kept facing problems and errors like "Application not installed" when trying to install the app, and "remount failed: no such file or directories", among others.
i also dnt have the Maps app availble in the market in my country, i can only sideload it.
it took me few days of googling to finally make it work on my Galaxy Ace. i'm running a rooted stock 2.2.1
it's simple once you got the right instructions. but as usual, i'm not responsible if your phone just decides to go brain dead on its own
for this you need ROOT access, Superuser, ADB and Titanium Backup
in Titanium Backup, choose Maps and back it up (app+data).
in case things dnt work out, you can always use this backup to restore the original app and data.
in Titanium Backup, choose Maps and wipe data then uninstall.
in Titanium Backup, choose Street View, wipe data and uninstall.
use whatever way to place the maps5.7.0-ownhere.apk file in the root of your sd card.
(i dnt know what's the diffrence between maps5.7.0-ownhere and maps5.7.0-ownhere-testkeyresign. i used the first and it's working fine.)
now connect your phone to your computer and make sure you keep your screen on. that's very important for the next step to work.
launch ADB and enter these commands:
adb shell (in the next line, a $ will appear)
su (when you inter this, Superuser in your phone will prompt you to grant root access. confirm it. a # will appear in the next line)
mount -t rfs -o remount,rw /dev/block/stl9 /system (this will remount your system in Read/Write mode)
cp /sdcard/maps5.7.0-ownhere.apk /system/app/maps5.7.0-ownhere.apk
mount -t rfs -o remount,ro /dev/block/stl9 /system (remount system back in ReadOnly mode)
exit
exit
Maps should appear in your app drawer.
you can now reinstall Street View.
if anything is not clear enough, just ask
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Sent from your phone
is it working
an0nym0us_ said:
I think its more easy to just use root explorer to copy that googlemaps apk to its proper place, because what i understand from that adb command is it copy the googlemaps apk to /system/app folder which could be done in just two or three click with root explorer. Cmiiw
But nevertheless, thanks for this tutorial tho
Click to expand...
Click to collapse
that was the first thing that came to my mind when installing didnt work. i copied the file with root explorer but the Maps app didnt show up in the app drawer.
i only speak from my own experience, i'm no expert.
thank you for the contrbution
imranaryan said:
is it working
Click to expand...
Click to collapse
it is working on my phone
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
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
icy201 said:
Hello, im having a couple of problems regarding my filesystem as well as the app supersu and its binary file.
To start, i rooted with kingroot and switched to supersu using terminal emulator commands. There are still kingroot files in my xbin which i will attatch a picture showing the contents of my xbin folder in attatchments (i also have .tmpsu in xbin) please ask if you need more pictures or information of files located in my directories.
The problems i need help with is:
1. I cannot mount /system or any foler in that directory as r/w, i feel that there is a file located somewhere that is preventing me from mounting /system as r/w.
2. I cannot update the su binary, i have tried normal and twrp modes neither work. Ive also tried flashing the UPDATE-supersu-2.78.zip in twrp and that doesnt work either. It says that it installed but nothing changes once i boot back into system, i feel that me not being able to mount /system as r/w is preventing me from updating the su binary.
I need help on how to regain conrtol of my /system and how to update the su binary. Any help? Thank you
Some specs of phone:
Android 5.1
Cpu model - AArch64 processor rev 4
Kernel version - 3.10.65+
Model - blu vivo xl
Click to expand...
Click to collapse
download root checker from the play store and make sure that u have root access on your device
messi2050 said:
download root checker from the play store and make sure that u have root access on your device
Click to expand...
Click to collapse
It says i have properly installed root access. Something fishy is going on with my root and my system.
icy201 said:
It says i have properly installed root access. Something fishy is going on with my root and my system.
Click to expand...
Click to collapse
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
messi2050 said:
then u can try to completely uninstall root from inside super su/king root apps and then reinstall it
Click to expand...
Click to collapse
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
icy201 said:
I did try that too, it took around 15-20 minutes to uninstall then when i rebooted the app was gone but my device still had root. I did get it to uninstall root 1 time then i went and flashed the zip file and the same problem occured again. Maybe kingroot just f-ed up my device so root will never work properly again? Maybe a virus? Idk whats going on with it.
Click to expand...
Click to collapse
Your device does not have twrp/cwm port ?
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
These are the only possible solutions ive been able to find that do kinda make sense.
"It's because you need a boot.img with r.o secure=0 in the build prop" i went and looked and my file says r.o secure=1 that would explain why my system will not mount as r/w.
Another post i found said -
"I've found the source of the problem asking in the MIUI forums, the boot image will not accept a modified /system.
You have to use the adb interface: adb devices then adb disable-verity.
Disclaimer: I'm not responsible for any damage caused by these operations."
The second solution seems more reasonable and alot easier to do. My question now is: will one or both of these solutions possibly fix both my problems? And the second solution disabling verify should that be okay to do without messing up my device? I do have that recovery i could flash but dont wanna do anything that might make the phone not boot into recovery.
icy201 said:
It does, i have twrp(touch) 3.0 for blu vivo xl. Thats the only way i got my device unrooted one time. What i had to do i had to boot into recovery, mount /system, reboot into system then root explorer would allow me to mount /system as r/w but i believe theres a script or something somewhere that is locking the /system into read only mode cause after a short period of time (around 5 minutes or so) i can no longer modify or delete anything in that folder even though it still says its in r/w and if i close root explorer and reopen it it shows that its back in read only mode even though i didnt change it back to that.
Edit: if i mount /system in twrp and boot into system when i boot back into twrp system is not mounted anymore, idk if its supposed to do that or not.
Click to expand...
Click to collapse
Yes that's normal , your problem is because of a buggy root
messi2050 said:
Yes that's normal , your problem is because of a buggy root
Click to expand...
Click to collapse
I just remembered something. I think i know what bugged it. I was trying to do an ota update for my device and it wouldnt let me. I found another app by chainfire called flashfire. I tried to flash the ota update and i had the option "inject supersu" enabled even though i already had supersu installed and everything else i needed for root. I guess doing that messed up all my su files ect.. But how do i fix it? I cant uninstall root cause my /system folder is locked into r/o. If i press full unroot in supersu it will remove the app (although it takes a while!) but all the files needed for root stay.
Guess there just no fixing this phone. Someone really hacked it good i guess, problem is still there and nothing can fix it...
Update - thread can be closed
Problem fixed, to fix the problems i was having i had to download the stock system files for my device and flash them, after that just installed the latest supersu 2.78 zip and remount problem is fixed.