Maintain Root from V7 into OTA V8 - LG Revolution

This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.

Flashing back to v7 now to test this out.
:::EDIT::::
So far it is failing. I get to step 5 and I am not able to remount. Permissions denied.
Also your rar file has tripped my antivirus software.
Please post a link to any original instructions.
:::EDIT::::
Yep still fails completely at step 5. The root is not carried over at all.

These are original instructions. I emailed Dan (djrbliss). Your anti-virus picked up on one of the exploits contained in the .rar. Once you download even if your anti-virus removes one of the files the rest works fine. This is how I was able to keep root. It does work.
adding the ro.kernel.qemu=1 and the adb commands were from djrbliss.. the rest is all me
Just try the super1click.
in adb type "adb shell id" what is the output?
*Should read "uid=0(root) gid=0(root)" <--- if anything but, go back to /data/local.prop and make sure it is still there.. I might be crazy but think it disappeared once or twice on me..
then the S1C or just the adb commands from OP should work..
(Your anti-virus removed psneuter from the exploit folder.. not needed anyways)

I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
Click to expand...
Click to collapse
if you have any other issues beep me on IRC freenode #lgrevolution

Haxcid said:
I am running through the process again. I think I found where things went wrong. I will post back after I have run the process again.
:::EDIT:::
It is working. Seems I typo'd kernel. After running through things again, it worked like a charm.
Click to expand...
Click to collapse
Glad to hear.. I was close to starting over from scratch to make sure I didn't miss something.. lol

Hmm, didn't work for me will try again later
Sent from my VS910 4G using Tapatalk
Edit: Got it working, typo for me too it's qemu not qenmu lol

JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..

Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol

drt054 said:
JUST FYI.. I have been experiencing some issues with this method that I didn't know until now. At one time I have lost all sound (speaker, in-call, key beep) and /or Vibration. If this happens to you for short-term until someone much smarter than me figures out a normal root method go into /data/local.prop and just rename local.prop to local.prop.bak so you will have it just in case you need to adb push files. After you rename you should reboot. You will still have root on the phone without the file.
Dan/djr explained that ro.kernel.qemu=1 is what allows adb to run as root. Jcase told me that after you push the files you should remove that because it will cause problems if left, like above.
Like I said, hopefully someone will come up with something better..
Click to expand...
Click to collapse
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
---------- Post added at 10:02 AM ---------- Previous post was at 09:55 AM ----------
dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
.
I flashed back using the tot file, rooted then proceeded from there. Once I fixed my ignorant spelling issues everything worked great. Now that I have renamed the prop file and rebooted sound seems to be working.
My issue is now battery. The phone with no use is eating battery like a thunderbolt. It has been off charger for 2 hours with no use and its down to 84%.

dbeauch said:
Do we need to flash the V7 stock TOT? Shouldnt we be able to just use MTs all in one tool to just put stock recovery back on? My only question is I don't know what to do AFTER using the MT tool (option 5 or 6) lol
Click to expand...
Click to collapse
Yes if you already have the V8 update in order to gain root you have to go back to V7 Stock firmware. If you are on GingerVolt 2.0 you have to flash the V7 Firmware to get back to LG-STock and Stock Recovery. The LG1click does NOT work on the V8 update so there is no CWM-Recovery, or GingerVolt at this time until MT figures out how once again..

Haxcid said:
+1 to this. No sound. I was an hour late to work because my alarm was silent this morning LOL!
SORRY!!!.. like I said didn't realize it until it happened, lost vibration and went to check my voicemail and no sound. But made that /data/local.prop into a .bak file, rebooted and was fixed. MT said has something to do with that entry in place the phone thinks it is a terminal emulator instead of a phone or something like that..lol So hopefully this is only temporary.
There may be a new root out soon.. not by me, like I said by someone much smarter than me may have found a way.
Click to expand...
Click to collapse

Worked like a charm DRT thanks so much!
Here is what I did:
1) Flashed MTs ZV7 Rooted Stock (RevoZV7GBStock.zip)
http://forum.xda-developers.com/showthread.php?t=1348637
2) Created the local.prop file, etc.
3) Used MTs All-in-One tool to flash Stock Recovery (Option 5)
http://forum.xda-developers.com/showthread.php?t=1348557
4) Downloaded and installed the ZV8 update OTA
5) Used ADB to push files per DRT instructions
6) Rebooted
7) Confirmed that I still have root using Root Checked Basic!
A little bit different than DRTs posted method but I wanted to avoid having to use LGNPST, so at least I can confirm that this alternate approach works as well!

drt054 said:
This is all thanks to djrbliss.. I just followed instructions.
***This method does not root the V8 OTA update rather it will maintain root from V7 LG-Stock firmware and will carry it over into the OTA V8 update. There is no CWM-Recovery or GingerVolt as of yet, that is left to the professionals.. MT This is only if you want to run the V8 OTA Update with stock software.. but with root.
1. Use LGNPST to get back to LG-Stock V7 firmware by flashing the .tot
Files: http://forum.xda-developers.com/showthread.php?t=1466655
Instructions: http://forum.xda-developers.com/showthread.php?t=1337386
2. Use the LG1click from MT to root only.. you need stock recovery to apply the OTA update.
3. Create /data/local.prop and type ro.kernel.qemu=1 then save it. I used root explorer but you can also do it through terminal: echo 'ro.kernel.qemu=1' > /data/local.prop
4. Phone Settings > About Phone > Software Update > Check New and download the update to V8 firmware.
5. After reboot go to whatever directory on your PC, where you have superuser.apk and su and
adb remount
adb push su /system/bin/su
adb shell chmod 6755 /system/bin/su
adb push Superuser.apk /system/app/Superuser.apk
If not sure use the 'files' from MT's LG1click
If that doesn't work download and run this:
Super1click 2.3.3 will push the files for you
http://dl.dropbox.com/u/50763513/SuperOneClickv2.3.3-ShortFuse.rar
***If nothing above is working*** (operation not permitted or read-only file system)
in adb type "adb shell id" should read "uid=0(root) gid=0(root)"
if not go back to /data/local.prop and make sure the file is still there (If not, just create it again in root explorer or other file manager that can edit files)
then "adb remount" and try to push the files again
then reboot and should be all set
OH, and if you don't want that remote desktop app it is /system/app/Aetherpal.apk I just renamed to Aetherpal.apk.bak rather than deleting it just in case..
Also if for some reason you wipe data (which I accidentally did) you will have to go back to Step 3 before getting the OTA update
And while they did fix some things in the update they left out fixing the touchscreen.. still goes unresponsive then you have to press power button to lock and unlock the screen to resume.
Click to expand...
Click to collapse
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks

Nckmsn said:
I am having a few challenges with the steps above. For some reason my root explorer is messed up. It won't open and I've tried uninstalling then reinstalling but it won't won't download from the market. I get another error.
Anyway i can't find another program that can create the prop file. Does anyone know another program or does anyone have some more detailed instruction on how to use terminal?
Thanks
Click to expand...
Click to collapse
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium

elreydotcom said:
1 open terminal emulator
2 type su, then tap enter
3 type echo 'ro.kernel.qemu=1' > /data/local.prop, then tap enter
4 close terminal emulator
5 profit
Hope this helps
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.

Haxcid said:
Don't forget to rename the prop file to local.prop.bak when you are completely done and on zv8 rooted or you will experience issues like no sound at all. Once you rename the file and reboot everything should return to normal. I would also give it a few days to work out any kinks, like battery drain and the likes.
H.
Click to expand...
Click to collapse
Ive been unable to get the adb part to work. I can't get the adb command line to come up on my pc. Anyway, so I'm on v7 unrooted with no sound. I have change the name of the prop file and even removed it but my sound wont come back. Do i need to complete the whole process for the sound to come back?

If you are unrooted you can't create the file, you need to get rooted first. Use the all in one package to root.
Sent from my VS910 4G using xda premium

Once I was able to finsh the entire process, I managed to rename the prop file and all sound came back. success!
Thanks

Made a post in another thread but any word yet I how we get CWM recovery from rooted zv8?
edit: MT let me know that I needed to recreate the prop file, reboot, and then choose the root option in his new all in one package for ZV8...worked like a charm!
Sent from my VS910 4G using xda premium

Related

[HOW TO] Remove ads using adfree android

This was created when we didn't have S-OFF yet.
If you have S-OFF or /system overlay script you won't need to go through all the steps simply download adfree android.
I know most of you will be able to do this. But I believe that it might not be as easy for the beginners. So here is a little walk through.
!NEEDs ROOT!
1. Download Adfree Android
2. Wait for it to determine local hosts then click on download and install hosts.
Now it will try to replace /system/etc/hosts but fail (it should reboot the phone but it didn't reboot mine)
4. go to adb and reboot your phone into recovery (with power on+volume down OR the command: "adb reboot recovery")
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
6. mount your system and sdcard you might be able to just use mount and mount everything but I've mounted them serperatly.
Here's how: "adb shell mount /system" next "adb shell mount /sdcard"
7. Now we're going to put it in the etc directory where it should be: "adb shell cp /sdcard/hosts /system/etc"
8. reboot the phone ("adb reboot")
That should remove most of the adds.
I know it's explained on a really low level of knowledge but I wanted to make it accessible for all of you.
Only the needed codes:
Code:
1. adb reboot recovery
2. start recovery-windows
3. adb shell mount /system
4. adb shell mount /sdcard
5. adb shell cp /sdcard/hosts /system/etc
6. adb reboot
has it the option to only block browser ads? when I tried it time ago it couldn't. I don't like to block the app ads
No it removes the adds everywhere. It simply blocks the links to adds. it doesn't actually remove them. they are still being called but they just don't show up.
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
PirateNL said:
Hi,
I have this very same problem for a long time now, with the constant reboots etc.
Followed your steps, but after the reboot, as soon as I press the button to update the hostfile, it reboots my phone
Thanks anyway...
Click to expand...
Click to collapse
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
A good guide, if a little misplaced, but another option is the /system overlay.
JonasDroid said:
Do you have root access?
Have you checked if the hosts file is at the root of your SD?
Click to expand...
Click to collapse
Yes and yes
where is the most recent hosts file? I'm using a vibrant and it says it worked, but of course, it doesn't. And it doesn't copy the hosts file to my sdcard either ? odd
Hello ,
Finally I got Adfree working
Ok it's not perfect because app continue to reboot the phone after updating the hosts file ,
and we need to copy it manually in recovery mode but it better than nothing
Thank you very much JonasDroid for this little How to .
PS:
For me step 5
JonasDroid said:
Code:
5. adb cp /sdcard/hosts /system/etc
Click to expand...
Click to collapse
was
Code:
adb shell cp /sdcard/hosts /system/etc
Bye.
Yeah indeed its adb shell cp thx for letting me know
Sent from my Legend using XDA App
Can you link me the apk of adfree? I can't download the app from my phone
BTW it's 'ADs" single d
short for advertisment (notice the single d?)
Fixed that English is not my main language
Sent from my Legend using XDA App
JonasDroid said:
5. Open up the recovery-windows (start recovery-windows (make sure your in the right directory))
Click to expand...
Click to collapse
Can't get "start recovery-windows" to work. What is the "right directory"?
Things seems to have worked for me without that portion. Many thanks, I will now change my review in the market for that app from one star to three stars. If they include a note describing this problem upfront I may bump it up further.
It could simply be called start recovery (depending on where you got your rooting tools)(if you've got the from The Unlockr you'll need the -windows)
If you have S-OFF or if you use an /system overlay script these steps aren't needed. (It was created when we didn't have S-OFF for our legends yet.)
Anyone having problems with adfree scripts on Legend since Froyo update? Neve had a problem witha rooted 2.1, but have lots of problems since rooted Froyo 2.2
It seems HTC may have some service which is checking for modifications to symlinks etc.
When I run adfree in my S-off CM7, i get an java.io.EOFException.
Someone else having this?
I had some problems at first, but reinstalling adfree android from market seemed to help. No problem now with CM7 (01/03 from ali ba) and s-off.
adfree no block ads!
Hi,
i install the adfree on my legend with 2.2 with sense.
i did download the host from the app all work ok got a message say it was success install and need to restart the phone.
i did it but still get all the ad like before on all apps.
pls help!
Have you followed the steps? (explained in first post)
Note that you should have a rooted legend (if you don't know what that is then you don't have one)

One click root after update: "We have root, but couldn't push busybox. Not sure why!"

One click root after update: "We have root, but couldn't push busybox. Not sure why!"
I just updated .890 which seemed to go fine with no errors (unfroze all bloat, but did not unroot), but I lost root, as expected.. but when I use Pete's one-click root tool (latest version), it gets to step 3 and gives me the error about not being able to push busybox...!? It says I "have root", but none of my apps recognize it.. I've pulled the battery, rebooted and retried like 10 times... still can't get it to re-root. I've made sure Debugging and Unknown Sources is enabled and tried in Charge Mode and Mass Storage mode... Am I going to have to stock flash this thing and re-update & re-root?
I THINK I have some type of root.. maybe... because Root Explorer will let me mount the System directory as R/W and I can TRY to manipulate files, but if I delete something (like su), it appears to delete successfully, but the file comes back if I refresh the directory.. but I also noticed when I go into the System directory, Root Explorer claims I only have 1MB of free space out of 318.00MB... how did that happen? If I try to run Superuser.apk, it force closes on me.
Any help or ideas are greatly appreciated...
there's an app on the android market that will push busybox if you have root. I'd look into that
edit: have you attempted to run the one-click root again? and if that doesn't work you can try to use the adb method if you're comfortable with it. And make sure that all of your drivers and everything are up-to-date
I have done battery pulls and like a dozen+ re-tries at the 1-click root, always get the same error.. I have been into the ADB shell to try and figure this out and I see the ADB Shell starts out by giving me a # prompt... that means writable/root, right? Any instructions on what I have to do from there?
I will look into that push busybox app, thanks.
http://wiki.rootzwiki.com/index.php/Motorola_Droid_3
This is where all the info about the adb and one-click stuff. The tough part about the adb method is manually pushing su to the (i think) system/xbin folder. Then i just used the app on the marketplace to push busybox. But there's a download link for both of those on the website
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Kraxis said:
Thanks for the links. I think a problem with my ADB is when I reboot it (step 3), I no longer have a # prompt.. it goes back to the $ prompt... the only way I can seem to get the # prompt in ADB is when I use Pete's temporary ADB root... but once I reboot, that goes away. When I try to do step 4, rm /data/local/12m, it says it's a directory and it's not empty and it won't remove it. :\
How do I normally make ADB give me that # prompt so I can write/edit? or am I totally off-base here?..
*edit* I am going to try and do Pete's temp ADB root again and just try steps 18+ and see if that gets me anywhere...
Click to expand...
Click to collapse
After temp ADB root, steps 18 and beyond should do it. You may want to check /system/bin and /system/xbin to remove the old su binaries before pushing the new one. Some folks have one in each location for some reason. Put it in xbin, but if it doesn't work, /system/bin will. Superuser wouldn't recognize xbin for me so I moved it to /system/bin and i'm good since.
Anyone have a thought on the xbin not always working? I think this is the 3rd topic i've seen with this issue, not including myself.
Sent from my DROID3 using XDA App
OK, I got root back! I used steps 18+ for "ADB Method" (after using Pete's temp ADB root) and essentially replaced SU and Superuser.apk, CHMOD'd it rebooted and I had root! Thanks guys!!

Manually Root w/ Zerg after 893 OTA

I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?
Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App
I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
you forgot last step....then update and youll still have forever root
I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk
Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App
what version could you not root?
Does zerg work on 5.9.901 ?
luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.
THANKS!
Flawless victory!
Binarality!
Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?
This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?
1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb
One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App

HELP!!!! trying Install CWM on zv8

Ok so here it is almost day 2 trying to install CWM on zv8 after using "mt's easiest way to keep root thru zv8'. (Oh and by the way MT your the MAN). Now getting to zv8 was easy, But getting the recovery installed is another issue all together. First started with the AIO bat. file which installs cwm (kudos to MT and djrbliss). And it reads
"system cannot find the path specified'.
SO ok well apparently the computer isnt reading the phone found out the driver has issue shows the error message(on both my laptops).
ok lets try the terminal emulator with
brad6360 said:
1) Download the cwmrecovery.img to your SD. ( I downloaded MT's zip file and then extracted all with root explorer, but you only need the cwmrecovery.img file.)
2) Use root explorer to copy or move it to the /data/local/tmp directory (make sure permissions are set to r/w/exe).
3) Launch terminal emulator and type these commands:
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
rm /data/local/tmp/* 2>/dev/null
4) exit terminal emulator and then reboot.
You can then try the vol down+power button combo upon boot to enter CWM.
Good luck.
Click to expand...
Click to collapse
didn't work and I the local.prop file in the data folder.
Someone PLEASE HELP!!!
(not a noob or expert but I can read and follow directions lol)
Are you sure you still have root level access?
Does adb detect your phone at all?
Still have root access I used root explorer to add the local.prop.
Adb recognizes my phone it shows a serial number under adb devices
Is there a way I can flash cwm in adb?
Sent from my VS910 4G using XDA
Use the newest aio from Mt. It worked for me. The simplest way is to flash the v7.tot then 'JUST' root, create the local.prop file, then ota to v8. Then continue on with Mt's aio to install cwm. Don't worry about having complete root access (cuz I didn't, but had cwm). Flashed broken out and haven't looked back.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
What happens when you go into recovery? Is it the stock recovery? Stock v8 didn't have the option to boot into recovery. Just a thought. When I did it I got a lot of errors, but it took.
--My REVO is Broken, tweaked, SC'd, and TB'd. Just awesome!
mrand1 said:
Thats where I'm stuck. I'm on zv8, using mt's easiest AIO to update from zv7. The AIO for cwm isn't installing nor through the terminal emulator. Any other suggestions?
Sent from my VS910 4G using XDA
Click to expand...
Click to collapse
I have the same problem, Even when i Flash zv7 tot and try old AIO it says
Cannot find specified path
and i am not a noob and have broken out an old revo with mt's help but this new one with pre loaded zv8...No luck yet
had to manually push
I'm glad that I'm not the only one having this issue
Can you use Root Explorer to check and make sure adb is pushing the image file to your phone? Look in this directory: /data/local/tmp/cwmrecovery.img
You could always do this manually using adb. Here's how.
1. Open the ZV8CWMRecovery folder on your PC.
2. Double click the 'Files' folder to go into that directory.
3. Highlight/select and copy the address of your current folder location on your PC. It will look something like this:
Code:
C:\Documents and Settings\username\My Documents\Downloads\ZV8CWMRecovery\Files
4. Click Start>Run>type 'cmd' and hit enter/return to open your command prompt.
5. Type 'cd', hit your spacebar, then paste your address which you copied in step 3 into your command prompt, hit enter/return.
6. You should now be positioned in the folder containing the adb and CWMRecovery files.
7. Type the following to copy the CWMRecovery image to your phone:
Code:
adb devices
adb remount
adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img
adb shell dd if=/data/local/tmp/cwmrecovery.img of=/dev/block/mmcblk0p14 bs=4096
adb shell "rm /data/local/tmp/* 2>/dev/null"
adb shell rm /system/etc/install-recovery.sh
adb shell rm /system/recovery-from-boot.p
adb shell rm /data/local.prop
adb reboot
Phone should reboot. Try and boot into CWMRecovery after it reboots.
idk if I'm not doing something right or wrong. I have usb debugging and internet connection, and I'm getting "remount failed: operation not permitted".
I had the same issue but following these instructions helped me, what finally helped me was typing a wrong command wich gave me a help menu with all the commands, the important one being "adb reboot [Recovery:Bootlaoder]"
adb reboot recovery did the trick, then wiped flashed broken out and sooo happy to be done with it.
after pushing CWM in command prompt of course
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
slimzim said:
I'm also getting "remount failed: operation not permitted" when trying adb remount in the command prompt just as mrand1 apparently did.
I (perhaps noobishly) skipped that step and did adb push cwmrecovery.img /data/local/tmp/cwmrecovery.img but after trying the next step got cannot open for write: Permission denied.
I'm trying to get back to Broken Out 1.1 - when it first came out I successfully downgraded to zv7 by flashing the .tot and then doing the OTA update, but now when I try to do that I can't seem to get the OTA to start downloading. I flashed zv8 tot in order to test the latest root method (which works) I just can't get CWM on there now - I don't seem to have any recovery at all actually. Any help would be appreciated.
Click to expand...
Click to collapse
I did the same thing, flashed to zv8 tot, was able to root but was unable to flash cwm recovery. I tried manually doing it and running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img. It appears I do not have any recovery either. Trying to get to Broken Out! Any help is appreciated, thanks guys!
asauber said:
I tried ... running MT's AIO. It's telling me permission denied on all of the steps except the push cwmrecovery.img.
Click to expand...
Click to collapse
For what it's worth I also tried that with the same results.
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
Man, that was too easy!
Thanks for posting this slimzim. This worked straight away for me, I'm installing Broken Out as I type! I'm actually a little glad this happened because now I'm a little more familiar with terminal emulator and what local.prop does. Never had to use it in the past. This is exactly the second phone I've ever rooted and am usually able to just use AIOs.
And of course, thanks to mtmichaelson for chatting with you about it and doing all the hard work in the first place!
slimzim said:
I finally got this to work much more easily thanks to a quick talk with mtmichaelson. Here's the method:
1) Get to ZV8 (I got there via LGNPST)
2) Root using the tool found here: http://forum.xda-developers.com/showthread.php?t=1621625
3) Open a Terminal Emulator
4) Type: su
5) Hit enter
6) Type: echo 'ro.kernel.qemu=1' > /data/local.prop
7) Press enter
8) Reboot
9) Use the ZV8CWMRecovery.bat found here: http://forum.xda-developers.com/showthread.php?t=1583023
Good luck!
Click to expand...
Click to collapse
So far not working...repeating process now...
da_morales said:
So far not working...repeating process now...
Click to expand...
Click to collapse
If you've done all steps exactly it should work. I went through a ton of other "fixes" that didn't work, I believe the key here is when you use the terminal emulator directly on the phone to create local.prop. I was trying to create local.prop in every way but that, and until I did it directly on the phone did I have success.
Good luck!
local.prop missing
I used the Easy ZV8 All in One Rooting Tool, and have no sound at all like a couple of other users. One of the suggestions was to rename the local.prop file in the /data folder to local.prop.bak.
I assume this is the /data folder in the internal folder? When I did the steps for the all in one rooting tool (coming from rooted zv7), there is no local.prop file in my /data folder to rename, yet I still have no audio for ringtones, phone calls, etc. except for the boot up sound on the splash page.
Any ideas why my local.prop file isn't even there? I even tried copying the one from the mtmichelson zip file into there, still no avail. Thanks!
I have the same issue. I used the echo command in term emulator and the local.prop file was there. rebooted and the file is gone. I have root but cannot install cw recovery. I have tried AIO, adb, and terminal emulator but nothing makes it stick. Any help would be greatly appreciated
Rob

cwm touch

So iam running bo 2.0.1 with cwm 5.5.0.4. Tried to update to cwm 6 touch by replacing cwm image in pretty much all the aio's.. it'll either say it pushed and still reboot into old cwm or I'll get permission denied on /data/local/temp/sh and mmcblk14 even after giving them all read write and execute permission. Can someone help me get this on my revo? Maybe a guide to do it with adb? It would be much appreciated..... sorry if this is posted in wrong section... I wasn't sure where it would be seen by the dev 's who can help
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
slimzim said:
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
Click to expand...
Click to collapse
The same exact way I've done it. Numerous times with no success. It said it pushed but reboot back into 5.5.0.4
Anyone else have this problem? How can I achieve this with adb or file explorer... the method posted just isn't pushing the image...
To do it from within the phone... (Insert the usual disclaimers here about messing your phone up here. It's all you from here on out)
You can open up the .bat batch file of one of the rooting tools that have CWM install scripting.
Copy the commands they perform in preparation for the procedure. Remove adb shell and push from the commands as you will be doing this from inside the phone, not via adb. I think you might have to remove some open/close quotation marks too, unnecessary from the terminal prompt.
Rename the new CWM file to match the command prompt change the command to match the new CWM filename.
Move that file to the expected location (/local/tmp if I recall correctly).
Use app Terminal Emulator to create a terminal windows and type su and Press enter. That will get superuser access.
Then, issue the commands you took note of from the batch file.
Reboot to Recovery to test if successful.
I used this basic process to get CWM on after rooting stock ZV9 a few weeks ago. Combing through a couple different batch scripts, I wanted to make sure I wasn't going to bork my phone. The adb remount command doesn't seem to work after rooting for some reason. That seems to be the cause of adb failure to update CWM.
If you get into trouble, I can't help you much there as I'm not that advanced. Good luck.
Anyone else with tips please chime in and help the chap :beer:
Sent from my VS910 4G using Tapatalk 2
Ill try it out. Thanks for the advice
Didnt work.. iam hoping that resetting back to stock and using that image from the start will work
Weird. I was expecting to hear good news since that's how I got CWM onto my phone. Good job trying!
Sent from my Transformer Prime TF201 using Tapatalk 2

Categories

Resources