my method here will give you a permanent rooted shell and will give you read-only system root which is useful for using root apps to backup data or freeze system apps--works just like real root without being able to delete system contents--freezing apps however works like a charm and should reduce the need for rw root anyway
FOLLOW DIRECTIONS EXACTLY--I WILL NOT RESPOND TO STUPID QUESTIONS--PROBABLY WON'T RESPOND TO ANY QUESTIONS BECAUSE MY DIRECTIONS ARE PERFECT, WORK PERFECTLY WHEN FOLLOWED, AND ARE EASY TO READ. FOLLOW ALL STEPS EXACTLY. IF IT DIDN'T WORK, IT IS BECAUSE OF YOUR ERROR
This works best from a factory reset device, but will work from a already used device but all other root apps and superuser apps must have their data deleted and be uninstalled first
1) make sure device is at least 50% charged--doesn't matter most of the time; better safe than sorry
install latest superuser apk
http://www.mediafire.com/file/dx854fsys5pvxjh/SuperSU.apk
install dirty cow root apk (croowt) [comes from this post https://forum.xda-developers.com/android/software-hacking/root-tool-dirtycow-apk-adb-t3525120
http://www.mediafire.com/file/1hbey829hc7676a/CRooWt.apk
make sure usb debugging is activated in developer settings and make sure you have accepted the debugging access prompt on the phone for the computer you will use
make sure you have an external sdcard installed--the smaller the better for this first time
2) open dirty cow root apk
choose "get root"
choose "method 1"
hit "ok"
choose "ok"
app will direct you to unmount and remount sdcard, choose "ok" and it will take you to storage settings
unmount sdcard
remount sdcard
when finished proceed to step 3
3) open superuser
do not update su binary
go to settings and make the default action "grant"
remove any and all apps from superuser log including the croowt app
3) THIS MUST BE DONE FROM A REAL TERMINAL ON A PC--TERMINAL EMULATORS WILL NOT WORK FOR THIS STEP
from a working pc with adb setup, preferrably linux, input commands exactly as listed
adb shell
su
setprop persist.sys.k P816A06
reboot
5) once rebooted, open dirty cow root apk again
choose get root
choose "method 2"
hit "ok"
choose "ok"
if app asks you to open with a browser, choose one, and choose "always"
screen will go black, systemui will crash and then reboot
6) once systemui is back up and running
you now have read-only root
you can now freeze system apps or backup your data using apps that require root
Your shell will be permanently rooted when accessed from a computer using adb--this will last forever unless you undo the setprop
Your system however will only be temp, read-only rooted until the phone is rebooted.
If you wish to have your temp, read-only root reactivated, all you have to do is repeat step 5 and that is it.
You can do this over and over again.
GIVE STAYBOOGY SOME PROPS FOR MAKING YOUR LIFE WITH THIS PHONE BETTER
Does this only work to back up or freeze applications?
poseidon207 said:
Does this only work to back up or freeze applications?
Click to expand...
Click to collapse
ACTUALLY READ the first sentence of OP
I don't see how freezing system apps would negate the need for a real root method? Is this "Read-Only" root method working with lucky patcher or Kernel Auditor?
Can this be used to bypass the subscription check for tethering? I assume not since system isn't writeable.
Does this method work in the ZTE Maven 3 (Z835)?
I'm doing it wrong, probably
First of all, thank you so much for doing this. I've been following that other thread since it was new, and you've put far more effort into this than the phone or most of us deserve.
I've gotten stuck trying to run Dirty Cow. I have USB Debugging enabled, adb installed on my Linux computer which recognizes my Maven (i.e. I've allowed access on the phone), etc. It eventually goes from "Checking vulnerability" to "Your device is not vulnerable" and I'm unable to proceed to the "Get root" step. What am I doing wrong? Might be some recent system update? Probably less effort to just buy a Galaxy.
Please be gentle. I know I'm a noob.
z812 root
I previously rooted my maven with kingroot and the dirtycow exploit.sh file and today I was overwhelming the device by running multible windows and apps and the phone rebooted and root was still intact....haven't rebooted it again yet but I shall.
Related
I installed Z4 mod and ran it and it says my g-tab is rooted. I have read that custom ROMS are pre-rooted. In my limited linux experience - being root gives you total control over the machine. I ran Terminal Emulator and cd / to get me to the top of the file structure. I tried to mkdir test and I was denied because the file system is read only. Next I went into the system folder because a lot of stuff in there looks familiar. I again tried mkdir test and was denied because the file system is read only. It would seem that to be root I would need a password and Z4 didn't offer to give me one or let me set it. Thinking further, I wonder if the file system is mounted for read only and that is why I can't create a new directory. When I am running the rom (Vegan) I can write there (understanding that I am writing to the sdcard that is mounted - presumably with RW access. So, what is all this rooting talk about then? What is the purpose of being root if you still do not have access to the file system?
You need Superuser.apk, as well. Think of Superuser as similar to Windows UAC, and rooting as making yourself an administrator. Even though you have root (admin) access, UAC (Supeuser.apk) still needs to let you through.
You also need "root aware" apps. Perfect example is Titanium Backup and that's usually my "litmus test" for verifying if I really have root or not on a device.
yup, in my limited rooting experience (droid1 and gtablet), after the process, there was always a new icon in the app tray entitled "superuser". i didnt have to install it separately, it showed up after the rooting process. if you don't have the superuser app, im betting the root process was unsuccessful.
my memory tells me i had some problems with z4root rooting my tablet, and i had to do it a few times before it actually worked. that was back in december tho, so i dont know if the current version of z4 is different than the one i used, and if so, if kinks were worked out...
so yeah, i probably helped none.
I always though z4root and Superuser were kind of a package deal.
I use them on my Cowon D3, as Cowon completely locks down their recovery process. boo to that.
rodzero,
With z4root you install it first. Then, you install a file manager program like "Root
Explorer" and when it comes up you click to "Allow" it. After that, you can go in
through Root Explorer and create and change R/O to R/W as needed. Same same
with Titanium Backup, once you have "allowed" it you can do what you need
to with the program.
Rev
More Investigation.
Thanks for the fast responses! I do have Superuser installed and it pops up from time to time when an app wants su access. Using terminal emulator, I worked my way into and what do I find but su! I ran su and got was granted su rights in the terminal. I felt pretty smug so I headed into the etc folder thinking I would make a simple change to the hosts file just to see if I could do it. I'm used to using nano in Ubuntu but no nano here. I tried vi (which I really don't know how to use) and I got some strange display but I don't think it was an editor. So, for the sake of closing the loop - if I wanted to edit the hosts file and add a new host - how would I do it. The Terminal Emulator now seems to be in the list to be granted su whenever I type it in. I know how to move around the file system. What kind of text editor would I invoke to actually alter the file? OK.... I went and downloaded TED and worked my way back to the hosts file, added a line but TED doesn't have su rights to save the file. So it looks like su exists but I don't see how to run an app in su mode except for terminal where I can invoke it by a text command. What's the missing piece to get TED to ask for su access?
Just a guess, but TED need to ask for elevation of privileges. It's probably an app issue.
Hi XDA Community,
Your forums have helped me in the past and I spent some time scouring the posts before posting this one as I couldn't find anything that was specific to my issue. Since this is my first post, I thought that I would save a ping pong of responses, by being fairly expansive on what the problem is and what I have tried; thus hoping to pinpoint my issue a little quicker.
Device Details:
---------------------
Model Number: GT-I9100
Android Version: 4.0.3
Kernel Version: [email protected] #3
Build Number: IML74K.XWLP3
ROM Firmware: Samsung-Updates.com-GT-I9100_O2U_1_20120326173406_jiut50pyip.zip (via Samsung Kies)
Rooting Method / Kernel: Odin3v185 / CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5
Summary
--------------
Since the beginning of July 2012, I successfully upgraded from Gingerbread v2.3.6 to ICS v4.0.3 using Samsung Kies then initiated root privileges by using the CF-Root Kernel via Odin (versions shown above) - All has been working fine 100%.....
However, it appears that I seem to have lost my SU permissions and may have disabled my root access, even though my device was rooted and I would appreciate any assistance from anyone who might have time to shed some light on the situation.
Behaviour of Apps I have tried that require root
-------------------------------------------------------------------
SuperSU
SuperSU Pro v0.96 lists in the 'Apps' tab (denoted by a green # symbol) that I have granted all relevant Apps that require SU privileges. This includes AdFree, BusyBox Pro, Root Checker Basic, Root Explorer, SetCPU, Terminal Emulator, Titanium Backup, Triangle Away.
Terminal Emulator
Terminal Emulator displays the following and when I enter the su command at the prompt, I just see a carriage return with a grey block. In other words, I do not see the # symbol denoting I have su privileges.
a/local/bin:$PATH
[email protected]:/ $su
Root Explorer
Root Explorer no longer displays a directory listing and simply displays a pop up from SuperSU after tapping on Root Explorer, "Root Explorer has been granted superuser permission for an interactive shell." then the following message from Root Explorer itself:
"Root Explorer has not yet managed to obtain root access. Because of issues with Superuser, this often happens the first time the app is run but is usually fine from then on."
Root Checker Basic
Apart from the App stating "Please wait for Root Check to be complete. Systems appears to be running very slow" after tapping on the [Verify Root Access] button. It never seems to provide an output after a few minutes waiting. My conclusion is that it cannot get su permissions.
BusyBox Pro
SuperSU displays the message that Titanium Backup has been given root access, however I get the following message:
"Asking for root rights..."
Then after a few minutes I receive this most enlightening output:
"Sorry, I could not acquire root privileges. This application will *not* work! Please verify that your ROM is rooted and includes BusyBox and try again.
This attempt was made using the "/system/xbin/su" command."
I read somewhere that Titanium Backup uses it's own BusyBox installation and not the system wide BusyBox package so I went in to the Titanium Backup preferences and selected 'Troubleshooting settings' then chose 'Force system BusyBox' to see if my issue was a BusyBox specific problem. Again, it failed so not sure if it is BusyBox or my SU permissions that have somehow got corrupted or been disabled.
Additional Information
-------------------------------
Using 'ES File Explorer', I can confirm that the following file's exist at the appropriate location paths:
/system/xbin/su
/system/xbin/busybox
Conclusion so far
-------------------------
It appears that on the face of it that I have lost my root permissions, so I removed apps from SuperSU, then uninstalled the App (e.g. Root Explorer, Terminal Emulator et al.); then performed the rooting procedure again via ODIN and the CF-Root kernel. The process itself worked flawlessly and so after it rebooted, I installed the Apps in question from the Google Play Store again and they prompted to be granted SuperSU privileges. Unfortunately, the same issues arose where it appears that it cannot communicate with either the su command or BusyBox to do what it requires.
Does anyone have any ideas as the phone is fine apart from this and although performing a Titanium Backup backup around two weeks ago, I would sooner not have to wipe everything if I can help it. I wonder if it is an update that somehow confused things...Either way, I cannot use Titanium Backup to backup/restore due to it requiring SU/root permissions, of which I do not seemingly have anymore.
Any ideas please as I am scratching my head and have gone blurry eyed at spending hours viewing various forums and posts?
follow this steps:
1. Unroot your phone with the unroot method here
2. To be sure, unroot again with the method here
3. ROOT your phone again using Any of the Rooting methods in the links provided in step 1 or 2.
Good luck
ICS 4.0.3 Lost su permissions even though device was rooted - Resolved
:good: Issue Resolved :good:
Many thanks for contributing to my issue. I had come across the post before in your links and although the directions were not completely related, there was a section pertaining to a zip file that I must have missed.
Conclusion
----------------
As can be read in the post, I was unsure if my issue related to losing root, a possible corrupt su file itself or BusyBox. As you will see on the link below, Busy Box actually creates hundreds of symbolic links (symlinks) and due to my perhaps overzelous approach to wanting a quick fix; I must have inadvertently created too many links with different versions of Busy Box and therefore when an App that was correctly added and granted SU permissions within SuperSU, when it then communicated with Busy Box / su to authenticate; I can only imagine it got confused and was lost with all the dead symlinks. The net result was that although SuperSU stated that it had granted permissions to the Apps requiring root, it never got to communicate with the su file contained within /system/xbin. I hope that makes sense, well at least I am pretty sure that is what happened.
Solution
------------
Firstly, I cleared all entries contained within SuperSU and therefore removing all Apps from being granted with root access (they didn't have it anyway at the moment).
I saved the zip file contained at the following link on to my external SD card and choosing to 'install zip from sd card' within the CWM Recovery (Volume Up + Power + Home button); effectively this uninstalls Busy Box completely from your device, including hundreds of symlink files - including many which in my instance was causing issues with Apps that required root to function correctly.
Busy Box Uninstaller v1.0 here
I restarted my device and downloaded Busy Box from Google Play Store and when I opened Root Explorer and the other aforementioned Apps shown in this post, they prompted to be granted root permissions (SuperSU) and voila....it worked ! :good:
I hope this may help other droid users experiencing similar symptoms.
Due to lack of tutorials which contained CLEARLY written instructions on how to root LG Optimus L9 with Chinese method, I decided to write my own in which I'll explain everything step-by-step.
I also found (as I think) a 100% working way to restore normal SuperSU and delete the Chinese one, after resarching on it for about 5 hours.
WARNING: USE INFORMATION AND FILES AT YOUR OWN RISK. You follow this tutorial and use method described here at your own risk.
Step 1: Download and install LG drivers.
Because of the post limit I cannot post direct link to download, but they can be found here, in step 3): CLICK
Step 2: Download and install Chinese root.
a) Download this file: www--mgyun.com/vroot (replace -- with a dot .)
b) Install the software, using the installation buttons as you would on any other windows installation.
c) Connect your phone to your PC with ENABLED USB debugging and select "LG Software" as connection option.
d) Start the program, you will see a green button, press it.
e) When the phone is connected the software will recognise the phone and the green button will show "ROOT", click on it.
f) The phone is going to be rooted in some seconds and the process is finished when it will show a tick on the software.
g) The phone will reboot.
Tutorial taken from this topic: http://forum.xda-developers.com/showthread.php?t=2439667
Credits for it to aristide1997
Step 3: Download SuperSU application from Google Store.
Step 4: Launch SuperSU application.
a) It'll ask you to install SU binaries. Select NORMAL if you don't have TWRP/CWM installed.
b) A Chinese Superuser prompt will show up, asking if you want to grant SuperSU su privileges. Click the button on the right. Square should be checked.
c) If you followed previous steps correctly, SuperSU should install binaries without problems.
WARNING: It'll ask you if you want to uninstall other applications that are managing Superuser right but DON'T DO IT. If you uninstalled the Chinese Superuser, and now SuperSU doesn't work, go to Step 8.
If you encounter problems (Binaries couldn't be installed):
a) Make sure you have a strange Chinese application in your Application Drawer. It's icon is a shield with a gear inside. If not, go to Step 2 and repeat.
b) Make sure you've clicked button on the RIGHT with SQUARE CHECKED when Chinese Superuser prompt showed.
Step 5: Exit SuperSU application, reboot the phone.
Step 6: After reboot, launch SuperSU application. If there is no prompt saying that SU binaries must be installed and everything is normal, go to Step 7.
Step 7: Download Root Checker from Google Store and launch it.
a) Check for Root Status in Root Checker.
b) If there is a prompt from SuperSU, asking if you want to give Root Checker su privileges, confirm it and you're good to go. You can uninstall Chinese root.
c) If there is a prompt from CHINESE SUPERUSER, asking if you want to give Root Checker su privileges, just click back (don't confirm or deny). It means there is a problem. Go to Step 8.
Step 8 (TROUBLESHOOTING):
If you uninstalled Chinese Superuser and now SuperSU doesn't have root rights, go to a); otherwise go to b)
a) If you uninstalled Chinese Superuser and SuperSU doesn't work (saying that binaries installation failed), don't worry. Connect your phone to your PC with USB Debugging ENABLED and start Chinese Root Program again. It should find your device automatically and restore the Chinese Root. Go to Step 4 and repeat.
b) If there is a prompt from CHINESE SUPERUSER to give su rights to applications, instead of SuperSU it means that SuperSU didn't become the main Superuser application and Chinese Superuser still is managing su rights. It can be fixed though.
c) Go to Google Store and download Superuser by ChainsDD (NOT SuperSU. The application you need is named Superuser).
d) Launch it and scroll left. Click on "SU Binaries" with green text in it, under "Elite version is not installed".
e) You should see a console. There should be a red text in it, at the end about "myung" su binaries.
f) Click "Update" button.
g) A prompt will show up, if it's in Chinese click the button on the right to grant Superuser su privileges.
h) New SU binaries will be installed, making Superuser new default application to manage su rights.
i) You can now uninstall Chinese Superuser and install SuperSU or stay with Superuser.
ok so I'm completely new to all of this ROOT/Flash business... can someone tell me the easiest way to put android 4.4 on my LGMS76910e? or do I need to flash v20h first in order to move forward to get KitKat? My phone is already rooted right now. I used the chinese program and then installed SuperSu gave SuperSu Su permissions and made it a system app.... once I did that I rebooted into CWM v6.x(cant remember the whole thing) and tried to flash BobZhome's CM 11 android 4.4 for LG L9 but my phone said it couldn't be completed because my phone was a p940(I think).... so then I restarted the whole process....but haven't tried to flash BZ's stuff again.... What should I do? someone help me please!!
@halomastah09 you got very lucky that bobz set his CM11 to run on the 769's only, and when you flashed to v20h it changed your model# qand wouldn't allow you to install his rom. If it would've finished flashing you would've bricked your phone. Before you flash any custom roms to this phone you have to first unlock the bootloader.
My phone is LG MS76910e
my phone is recognized as LG P765 optimus L9. But it is a optimus L9 LG MS76910e model P769.
Does anything get screwed up if I root it?
I don't know whereto put this thread although ths seems like a right forum,anyway, I have a problem with this persistent king root, and I want to remove it but these chinese 'communist' devs won't let me. I tried the following things:
1 Manually delete kinguser app from /system/app part, and then install supersu from play store. The result it just says what su binary is occupied.
2. Install BusyBox. Download this popular replace_kinguser_with_supersu_2.4.zip and 2.0 files (this ones with mrw folder) and run it. Supersu installs, asks for update and su binary update. Yes, yes, looks great, but doesn't work. When running any root app, like terminal emulator, nothing happens, no auth prompt pops up.
3. Reroot with older kingroot version (4.5), do the same as 2. Same result
4. Set auth mode in Supersu settings to allow/deny, when oddly it works. Allows or denies immediately, and I can find this in Supersu's log.
So, everything seems working fine except what Supersu doesn't want to show me my root promts when I need them.
If any information about my device needed, I will be happy to provide it. For starters, my device is ITELL K3300, I am not sure what else coud be needed if you want to help?
First of all, Obi is a Chinese OEM. So the support for their products is very bad. Unlike renowned Chinese OEMs like Xiaomi and OnePlus. They never bother to release their kernel map. So most rooting apps won't work. Then they have implemented Bootloader lock, Signature Verification at boot, Secure Boot and A/B authentication and secure Ramdisk. All these are good from a security perspective. Would've been one of the most secure devices had they continued to support it by regularly patching security updates.
This was a bit of hit or miss on my part, I admit. But I'm proud and happy with the results. So let's get right to it. Follow the steps in the sequence otherwise can't guarantee whether it will work or not. There'll be video link posted. Showing the process or part of it at least. So you can use it for reference. I'm working on a custom ROM for this device as well. I'll also be porting a CWM/TWRP recovery for this device, unofficial as it's my personal project. The file lists and maps will also be uploaded for anyone who wants to help. This process also works on Obi Worldphone SF1.
Here's the video tutorial:
youtu.be/MmkaCb2C8wY
Step 1: Download Kingo ROOT 4.5.8 from the official website. Make sure your phone is charged. Close all apps running in the background using recents. This is done as the phone is very slow and underpowered. This is to help prevent it from crashing due to it's underwhelming performance.
Step 2: Click on One-Click Root in Kingo ROOT app. Wait for it. It'll be slow at 30% and 80%. Leave it as it is. Don't disturb and touch it. You'll see Rooted Successfully.
WAIT. DON'T START REJOICING NOW.
Step 3: Since the phone is Bootloader locked, what we have achieved here is a temporary root. The moment you reboot it, the root will be lost. If you want to make Payments, use apps which won't work on Root. You can leave the phone as it is. And root everytime you reboot. Following the same process. That way you'll always be able to retain that system intergrity and never lose your Bootloader locked status. The phone will be as secure as possible after a reboot. But in case, you want to keep the root after reboot and permanently root it. Follow the steps below.
Step 4: Since the Bootloader is locked, the SuperUser app can't be moved to /system/app directory. The temporary root won't allow such /system/ modifications. So to completely breach the system protection against rooting. We'll need BusyBox, Magisk Manager and XposedInstaller. Download from the official sources.
Step 5: Install BusyBox, Magisk Manager and XposedInstaller.
Step 6: Open BusyBox app and press Install. Wait for it to complete. You may notice that you were not asked to give it root/su permission. This is because of Temporary Root. It'll continue to grant all apps which require root permissions. So always be careful that you don't have harmful/malicious apps installed.
Step 7: Open XposedInstaller and install Xposed Framework. It'll reboot automatically. Once done, proceed.
Step 8: Now open Magisk Installer. There'll be two Install options one for Magisk and the other for Manager. If an update is available for the Magisk Manager from within the app, install it. It'll download to your Internal storage/Download/ directory. Install it directly or manually by going to that folder. Now install Magisk. You can choose to preserve AVB 2.0/dm-verity and force encryption if you still want to retain SafetyNet features. I'd recommend you to uncheck both else you may suddenly lose root access with no way to root it again. Hit next. In method, select Direct Install(recommended). Hit Let's go. Wait for it to complete. It'll download it from the internet then flash it. In case, you encounter, Signature Verification failed, reinstall XposedInstaller and retry.
Step 9: Will all that done, if you're greeted with Installed in Magisk. Then reboot your phone.
Step 10: Make Magisk Manager using Lucky Patcher as System App. It'll automatically do it for you. Otherwise you can use RootExplorer/ES File Explorer(first turn on Root Explorer and grant SU permission to ES File Explorer; yes this time due to successful install of Magisk it'll show a toast for 10 sec. to ask for root permissions) then go to system/app/MagiskManager (create this folder) then drag and drop the apk. Rename the apk to MagiskManager.apk and set permissions as rw_r__r__ using properties of either explorer. Then uninstall the app. Then reboot. You may need to repeat step 8 after re-rooting using Kingo ROOT app.
Step 10: After all this is done, just uninstall Kingo ROOT or leave it(In case, you choose to preserve the AVB2.0/dm-verity and force encryption, as you'll suddenly lose the root some day randomly). And you're done.
Things to keep in mind: In case, Root Unsuccessful using Kingo ROOT app. It'll ask to try using the PC Version. There's no need for it. The PC version won't work and no other ADB or Fastboot method work to unlock the bootloader of this device. Just go to app info and clear data. Then try again. This should fix the issue. You must have developer tools unlocked and ADB Debugging turned on. OEM Unlocking should be turned on as well.