• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

mellomommy said:
I haven't used the terminal emulator (or done much with linux at all). What would the commands be to run giantpune's installer in the terminal emulator? Thanks.
Click to expand...

You don't use commands to run the installer. If you want to use command line in the terminal, go here and the info is posted http://androidforums.com/showthread.php?p=4982904


UPDATE: however you will need to enter the name of the file you have stored on your SD card, when you get to that point instead of...part_13_cwm_9_21_11_54.bin
 
its seems no has been having trouble with the cwm yet, and its working great, can i post a a youtube tutorial on how to do this to spread the word? of course. no credit taken whatsoever, or should we wait for leslies rom for further testing? the rest of the optimus elite community would love this
 
Get the installer on your phone somehow. Either use adb, or your sd card, or download it there. It doesn't matter, as long as you know where it is. Then make it executable. Then run it as root and pass it the command "cwm" to install the cwm or "stock" to install the stock recovery. So one possible way to use it would be via adb.
Code: 
adb push c:\path\to\the\installer\lgoe_cwn /data/local/tmp
adb shell
chmod 0777 /data/local/tmp/lgoe_cwn
su
/data/local/tmp/lgoe_cwn cwm

The terminal emulator will be fine as long as it can run as root and you know the path of the installer.

This is it working in the terminal emulator app.
20120921194150.jpg
 
Pune....there's no way I can access the msl location via terminal or anything? Do I have to be connected to computer and use adb?
 
A few pages ago, I posted links to some partitions (before we even had the cwm showing images on the screen). One of the partitions I linked to was a boot partition with a modified kernel in it. If you flash that image to your boot partition (not the recovery one!), then you will have this virtual file on your phone while it runs in "normal mode". From there, you can access it with a text editor and terminal app or something like that.
 
Curtis1973 said:
quick question. would it harm sprint users if this version were pushed to their optimus elite? same phone, different network. just curious because I didnt want to give bad info to anyone if asked.
Click to expand...

Just pushed the recovery to my son's Sprint Elite. The phone still runs fine and the phone boots into recovery. Thanks Pune!
 
Okay, tests on the rom have finished.

It errors out when it tries to copy to the boot.img onto the boot partition. I double checked the installer against several other roms, it's correct. Everything else in the installer works (at least it appears to).

I suspect the recovery doesn't know where "boot" is located.
 
Leslie Ann said:
Okay, tests on the rom have finished.

It errors out when it tries to copy to the boot.img onto the boot partition. I double checked the installer against several other roms, it's correct. Everything else in the installer works (at least it appears to).

I suspect the recovery doesn't know where "boot" is located.
Click to expand...
Then how does it backup and restore the boot.img?
 
Maybe it isn't.
The phone may not be doing anything at all to the boot partition, so it just boots what was there. It's also possible it understands how to restore from a backup or even where boot is, but doesn't understand the command needed to install the new one. or it could be copying it, but not putting it back.

The code used to copy the files over is the same used on every installer, so whatever the issue is, it's not copying the required files over like it should.
 
Does the log file at /cache/recovery/log or last_log say anything useful?

EDIT: It looks like the restore doesn't overwrite the boot partition. So for now, we can assume the backup doesn't back it up either.
 
giantpune said:
A few pages ago, I posted links to some partitions (before we even had the cwm showing images on the screen). One of the partitions I linked to was a boot partition with a modified kernel in it. If you flash that image to your boot partition (not the recovery one!), then you will have this virtual file on your phone while it runs in "normal mode". From there, you can access it with a text editor and terminal app or something like that.
Click to expand...

Don't mean to be a pain in the ass Pune, but I found the file, its a .tar file, that I can't extract, so how would I just get the boot image out of that and how would I flash something to the boot partition with my phone? Sorry dude I know there's allot going on, just wondering

http://www.sendspace.com/file/hj6242
 
giantpune said:
EDIT: It looks like the restore doesn't overwrite the boot partition. So for now, we can assume the backup doesn't back it up either.
Click to expand...

But we are making great progress! Awesome work!

In other news, I just got my Elite operational again...
I never realized the original recovery was touch based. Darn newfangled devices adding new features... Now where did I leave my walker!. Anyhow, once I realized that, it was easy to get working again. I would say I was angry having bought a One V for my mom for no reason but ultimately that was the plan for her. The Elite messing up just sped things up. Oh well, leaves me a spare phone.
 
I downloaded a copy of harmonia, rebooted into recovery then realized my .zip was on the internal Sd not the usd. Rebooted my elite and everything started to FC. I couldn't even run a file viewer to move harmonia to the correct location. I rebooted again to run a restore on my nandroid, i get an error when wiping /system. After the restore the elite does a factory restore.

I just moved the zip to the correct location and tried to install it aborted because the zip wasn't signed. Again a factory restore.

I am using the first recovery posted, i am getting easy to reroot and install the second recovery.
 
How does /boot behave on other devices in cwm? Right now, I have a directory in the ramdisk named /boot, and an entry in the fstab with "/boot emmc /dev/block/mmcblk0p9". Listing the files in adb shows that "/boot" still points to an empty directory. What should it normally point to? Is "/boot" supposed to appear as a file?

EDIT:
I looked inside one of the backups, and there is a proper boot.img in it with a correct file header. So the backup is correctly created. It is just the restoring that is the issue.
 
Just installed clockworkmod on mine too. Thank you to everybody who has worked on this. It's awesome to see you guys do this stuff.
 
You must log in or register to reply here.
Back
Top Bottom