-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root ClockWorkMod
- Thread starter salvy512
- Start date
-
- Tags
- lg optimus elite
I said destroy. Because there is a real possibility of it. If I could guarantee that I could fix anything that went wrong, then I might as well be trying all this out on my own phone.
I'll give it a shot. I have insurance on my Elite at Best Buy. Easy swap.
Here's a link for the current "stable" build. http://www.sendspace.com/file/k11vyc
md5 5786e86ee273e3056da36dba1067406c
You'll probably want to delete/rename /system/etc/install-recovery.sh to keep it from getting overwritten. This is how I flashed it:
Just so you know what you're getting into, this has only been run on 3 phones. We checked that it mounts the correct partitions at the right mountpoints. /emmc is that fake internal sd card. /sdcard is a real micro-sd. We were able to wipe the data and cache directories and it didn't write past the limit and cream the stuff on the following partitions. adb runs as root. /cache, /system, and /data are mounted at bootup. You can mount the others manually. And, well, thats about everything thats been tested. Use at your own risk. If you can't handle your phone being possibly destroyed, then you'd better not mess with this until enough people have confirmed each of the functions as working.
If you are one of the brave people that try this out, be sure to let us know if you tried some feature and it works. As I said, I've never used an android recovery in my life. I have no idea how it is supposed to behave.
md5 5786e86ee273e3056da36dba1067406c
You'll probably want to delete/rename /system/etc/install-recovery.sh to keep it from getting overwritten. This is how I flashed it:
Code:
$ su
# dd if=/data/local/tmp/part_13_cwm_9_21_02_09.bin of=/dev/block/mmcblk0p14 bs=512
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.563 secs (3272964 bytes/sec)
# md5sum /dev/block/mmcblk0p14
5786e86ee273e3056da36dba1067406c /dev/block/mmcblk0p14If you are one of the brave people that try this out, be sure to let us know if you tried some feature and it works. As I said, I've never used an android recovery in my life. I have no idea how it is supposed to behave.
Try the latest one he posted. It should work fine.
Guurak
Newbie
Whoops, must have clicked on the wrong link.
HaTrEd360
Android Expert
Is it gonna be possible to fix the reboot issue? Like soon or is it gonna be another long wait? I'm jw, not impatient or anything. I hope Drew still continues working on COT because it looks hella cool, some of us might even prefer it. Maybe someone can get ahold of him to let him know how we finally got.it to work? Might help him port COT easier as well. :]
EDIT: Also, it looks as if your trying to install something? But getting the no signature crap? Everytime I've ever needed signatures I used ZipSigner2 from the Market and it makes it work in recoveries.
EDIT: Also, it looks as if your trying to install something? But getting the no signature crap? Everytime I've ever needed signatures I used ZipSigner2 from the Market and it makes it work in recoveries.
It is fixed. Don't worry, it runs fine now. No signatures required, just toggle signature verification in CWM. giantpune will post another build later on with the signature verification turned off by default.
Leslie Ann
Android Expert
I have the three roms ready, so if you have the recovery, PM me know if you want to test. These could be risky, so you should be prepared to brick or at least have to redo everything.
Gp looks like you got the reboot issue nailed down! Sorry your Guinea Pig ran off last night 
. But glad others could help. I also did a backup and it didn't freeze on reboot like the first build. Looks like it's working like it should.. Now I guess next step is flashing a rom with it. Did anyone take Leslie up on one of hers?
Edit.. gp do you recommend your modified boot partition of just delete install recovery file
. But glad others could help. I also did a backup and it didn't freeze on reboot like the first build. Looks like it's working like it should.. Now I guess next step is flashing a rom with it. Did anyone take Leslie up on one of hers?Edit.. gp do you recommend your modified boot partition of just delete install recovery file
Gp looks like you got the reboot issue nailed down! Sorry your Guinea Pig ran off last night
Edit.. gp do you recommend your modified boot partition of just delete install recovery file
I renamed /system/etc/install-recovery.sh to install-recovery.sh.bak which worked fine.
I do eventually want to use gp's modified boot partition. He took care of cleaning up all the BATT messages which kept getting constantly logged as well as other improvements.
Yeah I prefer to use the modified kernel but wanted to make sure there were not issue that he knew of.... The more stock LG / VM crap I can get off my phone the better
Think I might pm Leslie about trying out one of her rom's
Proceed at your own risk. Be careful. I don't believe CWM has been tested on an Elite running ZV4, but it seems to run well on ZV5. This guide was written specifically for the CWM BIN file named part_13_cwm_9_21_02_09.bin, but it will work for future releases from giantpune. Just alter the below commands to reflect the different file name.
Install with terminal emulator on your phone:
1. Download the CWM bin file and copy it to the root of your /sdcard (you can leave it in the Download directory if you want, but the following dd command will need to be slightly different if you do).
2. Run the terminal emulator app. (Download: https://play.google.com/store/apps/details?id=jackpal.androidterm)
3. Type su and tap the [Enter] key (Allow root access if you are prompted by Superuser/SuperSU)
4. Type busybox md5sum /sdcard/part_13_cwm_9_21_02_09.bin and tap the [Enter] key
Check to make sure the returned value matches the md5 which is posted along with each CWM bin file.
5. Type dd if=/sdcard/part_13_cwm_9_21_02_09.bin of=/dev/block/mmcblk0p14 and tap the [Enter] key
Once it's finished writing CWM to the recovery partition you'll see some output regarding the speed and size of the operation.
6. Type busybox md5sum /dev/block/mmcblk0p14 and tap the [Enter] key
Once again, check to make sure the returned value matches the md5 which is posted along with each CWM bin file. Close the terminal emulator app.
7. Run a root file explorer (such as Root Explorer) on your phone. Navigate to /system/etc/ and Mount R/W (read/write). Then rename the file named install-recovery.sh to install-recovery.sh.bak. If you don't see this file at this location on your phone, then you're finished.
Finished.
That's normal.. that is the output you should get from step 4.
If the file install-recovery.sh doesn't exist at /system/etc/install-recovery.sh, then that means either your phone came with the ZV5 update installed already or you're on ZV4. This has not been tested on ZV4 as far as I am aware. If you're running ZV5 and it's not there, then there's no problem, you're finished.
