Before you root your LG Revolution:
Install the latest USB driver software
http://www.lg.com/us/support-mobile/lg-LGVS910
===============
You MUST do this.
===============
All Credit goes to das7982,
I just found the answer.
___________________
use root explorer and go into
system/etc/ and delete the file called
install-recovery.sh
Why? BECAUSE Clockwork will not work without deleting the install-recovery.sh
because it is a shell script designed to over write any new recovery you try to flash over it.
THEN ROOT:
Download
http://forum.xda-developers.com/showthread.php?t=1348557
Extract and run "V8 all in one root + CWM"
and choose install root and CWM and viola.
Generally I would move this thread as a duplication, however, until the OP of the root tools adds this in his first post, I'll let it stay.
The install-recovery.sh and on other devices boot-recovery.p are previously known issues which cause the installed custom recoveries to get overwritten when booting back into a stock rom. This file should be deleted after root, and before installing a custom recovery, unless you plan to boot immediately into Custom Recovery and install a custom rom.
The issue, is you have to ROOT FIRST and gain /System RW.
So the title should be "Before you install CWM". (not sure how the root tool works if you can just root only, or if the author can add the cmd to delete this file when rooting and installing CWM. Should be able to somehow. They do it in the 500 forum)
But sometimes people miss this 1 little step, so the thread will remain.
Rock On!
MD
I thought this thread was a joke because to root your phone via PC you have to install the drivers so ADB can even see the hardware...
Lol
I was gonna say who has a revo that is not rooted.
This makes sense. Bcuz of the .p file or the install-recovery.sh, the aio's repeatedly fail at fully installing cwm. If you push cwm directly from the device, you don't even have to mess with the .p or the install-recovery.sh.
Regardless of anything, It's a good find KangKilla. Awesome clarification MD.
Hi I'm trying to install above since viper4android wont work with the stock su, but no luck.
I've tried installing from the market per this:
1. Install SuperSU from Play Store.
2. Open SuperSU and grant it SuperUser permissions (important; if you delete SuperUser before you grant rights to SuperSU you lose your root and need to either reflash the ROM or flash the zip I linked above).
3. gone into supersu settings and told it to grant su on boot, and grant to anything in the system folder as well
and I've also tried installing the zip version in recovery. I've also tried using the file manager in recovery to rename the current su binary in system//xbin and put the new one from the zip file in the directory.
Any way I try installing it freezes on boot up and I have to restore a nand to get my TP working again.
Overall loving flintmans new evervolv, it's really smooth, but the sound on the TP is pretty low and crappy sounding without viper4android so it's a pretty big issue for me.
Can anyone help please?
PS I cant find the apk for the current su, maybe thats part of my issue as well. Also Supersu works with 3.4 kernel version of cyanogenmod so its not a kernel issue.
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
One Hype said:
Just flashed Sinless ROM and although it came with SuperSU by chainfire. I decided I wanted to remove it and install superuser by clockworkmod instead. For some reason superuser app didn't actually root the system, so I attempted to uninstall it and reinstall SuperSU. This is where I'm stuck. I cannot remove superuser app no matter what I try, even deleting it with a file manager or disabling the app. Anyone have any ideas? Really need my root back. Thanks
Click to expand...
Click to collapse
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
KiraYahiroz said:
If it's in /system, you need root to remove it (which you don't have). I suggest going into recovery and then flashing Superuser with the SU binaries that allows root to work.
Link to ClockworkMod's Superuser: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
One Hype said:
Tried this and that is what I am attempting to remove from the system to no avail. Anything else I can try? I don't know why it won't give superuser access either.
Click to expand...
Click to collapse
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
KiraYahiroz said:
So flashing that zip didn't flash the SU binaries either?
Try flashing this then: http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
The main important thing is to get the SU binaries installed to allow the superuser apps to work. Once you have that installed try to change superuser apps again (do not choose the full remove option as that will also remove the SU binaries).
Another option is to try flash the ROM again.
Click to expand...
Click to collapse
Just did this buy with v.1.8 of SuperSU and everything worked perfect. Thank you
This patcher is now outdated. Use the new SuperSU instead. http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This zip is a systemless version. That means that you'll get root and be able to use it normally, but your system partition will not be modified, like in normal root methods. Only for Marshmallow.
Keep reading for disadvantages and advantages
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
If you have rooted before, flash the system partition (or reinstall the ROM) before flashing this zip.
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Reboot to TWRP. If it asks you whether you want system to be mounted as r/w, and if you want to take OTAs later, choose to keep system read-only (this will replace TWRP with stock recovery on reboot).
Flash SuperSU-v2.56-20151030013730.zip
Reboot
TWRP will say that you are not rooted, just ignore that. Do not tell it to root it.
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Well done bro!
I'm just waiting for this
Help regarding installation
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
out386 said:
Chainfire had released a newer version of his SuperSU that doesn't need to modify the system partition to provide root access. This method doesn't have much of a practical application right now, but it allows you to flash OTA updates without having to unroot or flash the stock system partition.
HOW TO USE:
Download the attached zip, and flash it from a recovery (I tested it with TWRP).
Download SuperSU 2.56 (or newer, if it supports systemless mode) from here: http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2 (Just download the apk)
Flash SuperSU-v2.56-20151030013730.zip
Reboot
This will work with all Marshmallow kernels, even the stock kernel.
Drawback : A factory data reset will remove superuser privileges. If that happens, simply flash SuperSU-v2.56-20151030013730.zip again.
TO RECEIVE OTA UPDATES :
Just make sure not to do anything that modifies /system. For example, no build.prop changes, and no system app removal. Or even if you do these, make sure to undo these changes before flashing an OTA. You can flash OTAs without unrooting now.
Flash the stock boot.img for your current Android version before flashing OTAs.
BUGS :
I didn't find any, yet, but Chainfire wrote the following on his thread:
Apps with hardcoded paths to su (seriously?) will bork
Factory reset unroots
Factory reset wipes pin
...
Bugs... Bugs everywhere!
ADDITIONAL INFO :
This zip will replace sepolicy as mentioned on Chainfire's thread (thanks to @metaspook for the patched sepolicy, which I extracted from his zip), so you'll be able to get root access even on SELinux enforcing kernels (only the stock MM kernels right now). Also, you can flash any other kernel (as long as it comes in a zip format, not as an img) before or after flashing this, and you'll still have root access.
Click to expand...
Click to collapse
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Good.... Thanks for posting
metaspook said:
Good work n thanks for mention bt can't understand why u created a patcher again where I'v already created one!
Its ok, good job.
Click to expand...
Click to collapse
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
<accidental double post, sorry. Can't delete>
kalpitandroid said:
I am using MicroMax Android One with Marshmallow
Currently, I've not tired the phone.
When I open recovery, I see some options like Apply update from SD card, mount, cache wipe, factory reset, etc.
So which option should I use to flash the zip file.
Click to expand...
Click to collapse
You need to install a custom recovery first. Go to the Android One (First generation) General forums on this site. You'll find a how-to at the very top of the list of threads. Once you have a custom recovery, flash this using the "install zip" option.
out386 said:
Yes, well, I would never have reposted the same thing, so, I'm sorry if it seemed like that.
This one uses Chainfire's new systemless root method. Unlike other root methods that need modifications to /system, this method uses modifications to the boot image to set up and run the su daemon from a loop device on the /data partition and achieve root. Right now, that doesn't have much of an advantage except to make flashing OTAs easier. Chainfire made it because future devices might need it. I made the patch because someone on FB asked about it.
Click to expand...
Click to collapse
Hmm... gotcha now.. Good work!
If u ever need any help just pm.
Thank you...
out386 said:
<accidental double post, sorry. Can't delete>
Click to expand...
Click to collapse
I'm almost entirely new to messing around with stock firmware on a locked bootloader, its been unlocked for 2 years. I relocked it, TA keys are fine, I had TWRP, I was able to write to the system partition, I had external storage write permissions, and all of those things have dissapeared entirely. I was able to use an xposed module for getting external storage permission back.
-I can't install TWRP again because the installer on a locked bootloader requires the system to be remounted rw or already have access to a recovery.
-The xposed solution to the exteral sd isn't ideal, and again I need TWRP or to do it manually by mounting the system rw.
-FlashFire doesn't work regardless of what variation of options I give it.
-I pulled the kernel image out of the pre-rooted zip I initially used but it won't fastboot. It says USB debugging isn't enabled when I try it using flashtool, though it is on when the system is up. I was hoping that the rewrite permissions or possibly even TWRP would be available if I reflashed the kernel image. This won't work.
The reason for being on Lollipop is that for whatever reason, push notifications still really suck for me on Marshmallow, enough so that it isn't a workable option.
Having either TWRP or being able to remount the system rw would, from the look of it, lead to being able to fix the thing entirely.
The only workable solution I have right now is to flash stock Marshmallow, install TWRP which is rather easy on current MM, then reinstall the pre-made zip I already had for Lollipop. This is a huge pain given that I just put a lot of time into my setup and even just the settings I'm using in Xposed would in itself be difficult to restore as its quite a lot. Everything is backed up via Titanium.
Essentially, "Is there a workable solution to my problem that doesn't involve flashing MM, putting TWRP back, reflashing LP, then setting up what I know I need to all over again followed by the inevitable supprise down the line of still needing to re-do some of my apps that didn't quite go well? The goal is to get TWRP back, and this seems like it isn't going to happen if I can't write to the system.
??
Also, If I just pull /data entirely via adb, my laptop already uses ext4 for the filesystem, but it there a way in this scenario where I could absolutely ensure that I could do it, and then put it back while not screwing up file permissions assuming I did the whole falsh MM, install TWRP, flash LP thing?