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

Root ClockWorkMod

Also, before I forget (again) to ask, how should we go about updating CWM if there is another update published? Do we remove the current build entirely, reinsert the stock recovery, then reinsert CWM? What is the updating process in detail?
I've just been updating by writing over the old version. Haven't had any problems so far.
 
Agreed no reason to go back to stock

I would treat it the same as the system partition with a rom. If you are installing a completely new one I'd erase the partition then install the new one. If you are simply upgrading to a new version of the same one your probably safe to just write over it.
 
Agreed no reason to go back to stock

I would treat it the same as the system partition with a rom. If you are installing a completely new one I'd erase the partition then install the new one. If you are simply upgrading to a new version of the same one your probably safe to just write over it.

Reverting to stock and reinstalling the new build of CWM would have been worst case scenario. Good to know it works just by overwriting it, though. Adding that tidbit to the FAQ shortly.
 
I have a workaround here for the incorrect timestamps. I have it reading a file from the SD card like "/sdcard/nandroid/timefix" that contains a month/day/hour/year to add to the day it thinks it is. Then you(the user) can put whatever values in that file you want to to make it have the date you want. Does anybody have any better, more correct, or less hacky solutions for this issue? I would be glad to hear them.
 
Leslie,

Looking at the updater script I see a couple things that may be an issue. Looks like these lines are mounting some blocks that our phone doesn't have

I have been messing with this off and on for so long, I have no idea where those numbers came from. Good catch though.


I'll mess with the installer tonight and send out some betas for others to test, my Elite is running, but damned if I can get it to accept the update or even replace the TOT file, tried last night to no avail. Hopefully tonight I will get it when I get done working and I can do direct testing.
 
I apologize as I'm new to Linux and Android, but I'm willing to learn.

Would an AOSP ROM work with this phone? Or would certain packages/drivers have to be preinstalled.
 
I apologize as I'm new to Linux and Android, but I'm willing to learn.

Would an AOSP ROM work with this phone? Or would certain packages/drivers have to be preinstalled.


Most likely no. Any ROMs for different phones would have to be ported to ours, which would take some time. I'm in the same alley as you my friend.. Willing to learn and I have learned slot here.
 
I have been messing with this off and on for so long, I have no idea where those numbers came from. Good catch though.


I'll mess with the installer tonight and send out some betas for others to test, my Elite is running, but damned if I can get it to accept the update or even replace the TOT file, tried last night to no avail. Hopefully tonight I will get it when I get done working and I can do direct testing.

No Prob, Just trying to help any way I can... Looking forward to testing any more releases for you if you'd like to send em my way..
 
I have a workaround here for the incorrect timestamps. I have it reading a file from the SD card like "/sdcard/nandroid/timefix" that contains a month/day/hour/year to add to the day it thinks it is. Then you(the user) can put whatever values in that file you want to to make it have the date you want. Does anybody have any better, more correct, or less hacky solutions for this issue? I would be glad to hear them.
looks like a clean fix to me. all you gotta do is look at a clock and know the date and put it in. the phone will fix any offset once booted up with a signal


edit: meaning it will set appropriate system time,but probably not rewrite to any files contained.
 
While that kernel is running (ie while you are in the recovery), do "adb shell" and enter "cat /sys/devices/virtual/lg_fw_diagclass/lg_fw_diagcmd/msl"
Is this possible to be done via terminal emulator? I can't get my Elite and my computer to play together so I can't use ADB.

[joke]BTW Giantpune, I hate you. This week Torchlight 2 released, I've been waiting for this for evar and because I've been helping test the recovery, kernel and ROM I've played it only 45 minutes in 2 days.[/joke]
 
Just a warning, I would recommend avoiding the "Partition Internal SD Card" option at all costs. I haven't seen that setting in the menus, so it may not be enabled. But if you do see it, don't used it, and pleas let me know where it is. I happened to run across the code involving that option, and the way it works looks like a 1-way trip to brickville on our phone. If it does exist, it will be right under a menu item that says "Fix Permissions"


As far is the workaround for improper timestamps is concerned, I'm open to suggestions as to where the file should be read from. Right now, I put it at "/sdcard/clockworkmod/timefix" and it works fine there as long as your SD card is mounted. If the SD is not mounted, then it will not adjust the time, and you get the dates from 1980. The issue is that somebody might unmount the SD card without realizing that it will cause the timestamps to go all cooky again, and then make a backup and not know where it went because of the wrong date. I can automatically mount the SD card when it wants to get the date, but then you may have people wondering why they unmounted the SD card and it mounted itself for apparently no reason.
 
While that kernel is running (ie while you are in the recovery), do "adb shell" and enter "cat /sys/devices/virtual/lg_fw_diagclass/lg_fw_diagcmd/msl"

I tried this to get my msl and its saying "cat: can't open '/sys/devices/virtual/lg_fw_diagclass/lg_fw_diagcmd/msl': No such file or directory"

Any ideas guys? I'm in recovery and i did adb devices and it showed my phone in recovery.
 
Here's a recovery image that contains the workaround mentioned earlier for the incorrect timestamps. Download part_13_cwm_9_22_17_32.bin from Sendspace.com - send big files the easy way
md5 3fbe49417b6d4153ffec2d3b963bacd8

In order to use the workaround, you need to know how many days/hours/minutes your time is off by. You can use adb while in recovery and type "date" and it will tell you when it thinks it is. I went here Date Difference Calculator - number of days between dates and typed in my phone's date and the current date and it told me how many it was off by. Then I created a file on my microSD card in the clockworkmod folder called timefix. And in that file I put the values to be added to the time my phone thinks it is. Every line ends with a '\n' newline, not a "\r\n".
Code:
hour=10
minute=29
day=11946
So it takes the "Jan 8 10:10:04 GMT 1980" from my phone, adds 11946 days, 10 hours, and 29 minutes to that for the backup names. It will be a bit more accurate if you just use minutes, so 17202869 minutes. If you don't plan on using the work around, there's nothing else changed, so no point installing this version over the last one.
 
Is this possible to be done via terminal emulator? I can't get my Elite and my computer to play together so I can't use ADB.

[joke]BTW Giantpune, I hate you. This week Torchlight 2 released, I've been waiting for this for evar and because I've been helping test the recovery, kernel and ROM I've played it only 45 minutes in 2 days.[/joke]







I tried this to get my msl and its saying "cat: can't open '/sys/devices/virtual/lg_fw_diagclass/lg_fw_diagcmd/msl': No such file or directory"

Any ideas guys? I'm in recovery and i did adb devices and it showed my phone in recovery.

JUST FYI: I flashed the boot image file right from cwm and everything was super quick and fine, I mean its up to you if you want to risk, but I don't really see much of a risk, and its nice to be able to access your msl from your file explorer
 
JUST FYI: I flashed the boot image file right from cwm and everything was super quick and fine, I mean its up to you if you want to risk, but I don't really see much of a risk, and its nice to be able to access your msl from your file explorer


So.. Go into cwm, go to install zip, ans install update.Zip?
 
JUST FYI: I flashed the boot image file right from cwm and everything was super quick and fine, I mean its up to you if you want to risk, but I don't really see much of a risk, and its nice to be able to access your msl from your file explorer
Yes, I flashed the kernel but then you have to run the command from adb while in recovery. Something I can not do. My device will not show up on my computer.
 
Yes, I flashed the kernel but then you have to run the command from adb while in recovery. Something I can not do. My device will not show up on my computer.


I think you can go look at the file..
Also, where should I put the zip? /sdcard/? Leave it in downloads?
 
@MACFET not sure why it quoted someone else

No, if you flashed the boot.img you should be able to access the file which contains your msl directly from the phone, if that's what you are trying to do
 
I think you can go look at the file..
Also, where should I put the zip? /sdcard/? Leave it in downloads?

This particular zip doesn't necessarily matter where you put it just know where its at when you need to access it from the recovery......the normal choose zip from SD card option in the recovery is referring to External_SD, so If you don't have one you'll need to store the file in your internal /sdcard

Sorry, tired...you'll need to choose the install zip from internal sdcard or what ever the option says, just not the regular choose zip from sdcard unless you have it stored on External_SD.
 
This particular zip doesn't necessarily matter where you put it just know where its at when you need to access it from the recovery......the normal choose zip from SD card option in the recovery is referring to External_SD, so If you don't have one you'll need to store the file in your internal /sdcard


So /mnt/sdcard? And then what do I do from there because it only shows folders in the "choose zip from sd card"
 
@MACFET not sure why it quoted someone else

No, if you flashed the boot.img you should be able to access the file which contains your msl directly from the phone, if that's what you are trying to do
Should? Or can? It is my understanding that you need to flash the kernel and then run the command through adb to generate the msl file.
 
So /mnt/sdcard? And then what do I do from there because it only shows folders in the "choose zip from sd card"

You can further access the sub folders just click on where you have it stored, but it sounds like you have it stored on the internal. So you need to go back and select install from internal SD option
 
Well its in /mnt/sdcard and /sdcard. Root directories of both.. And they are the exact same.. Same files.. Same everything
 
Back
Top Bottom