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

Root ClockWorkMod

ktb83 said:
This CWM works fine as far as I know. A working ROM and proper updater-script for the ROM is what comes next.

I've already flashed giantpune's custom kernel boot partition using CWM.

If anyone wants to try it, here is the flashable ZIP.
http://www.sendspace.com/file/ljn9np MD5: e08f68ecf75de78285ef447b1a5fc24f

Don't hate me if it kills your phone. It worked fine for me
Click to expand...

What exactly is this for? Is it because the boot partition wasn't overwritten or.....I don't know just trying to figure out what is necessary, I flashed cwm via the terminal, so is this necessary?
 
DsyMnapTic said:
What exactly is this for? Is it because the boot partition wasn't overwritten or.....I don't know just trying to figure out what is necessary, I flashed cwm via the terminal, so is this necessary?
Click to expand...
do i flash it like a rom or like a update like stock recovery?
 
DsyMnapTic said:
What exactly is this for? Is it because the boot partition wasn't overwritten or.....I don't know just trying to figure out what is necessary, I flashed cwm via the terminal, so is this necessary?
Click to expand...
I think the only improvement made to the kernel in this boot partition is cleaning up all the battery spam in the logs. No, it is not necessary. There are other improvements he has made, but I think GP hasn't released a version of theboot partition which includes them yet. He can correct me if I'm wrong.

slutyman said:
do i flash it like a rom or like a update like stock recovery?
Click to expand...
You flash that ZIP in CWM.

landonh12 said:
Does this kernel support overclocking?
Click to expand...
No.
 
DsyMnapTic said:
What exactly is this for? Is it because the boot partition wasn't overwritten or.....
Click to expand...

The boot and recovery partitions are being backedup and restored properly. It was just a stupid mistake on my part that made me think they weren't. All the nandroid backups created with this cwm should work correctly.

As far is this kernel is concerned, it is essentially stock. It removes a lof of dmesg spam, which won't make a bit of difference to anybody that doesn't know what that is. The only reason anybody else would benefit from this kernel is because it creates the same virtual file that is accessible while cwm is running that shows you your msl. Having this kernel on your boot partition means that you can read your msl using an app file browser and text reader.

20120922132721.jpg
 
giantpune said:
The boot and recovery partitions are being backedup and restored properly. It was just a stupid mistake on my part that made me think they weren't. All the nandroid backups created with this cwm should work correctly.

As far is this kernel is concerned, it is essentially stock. It removes a lof of dmesg spam, which won't make a bit of difference to anybody that doesn't know what that is. The only reason anybody else would benefit from this kernel is because it creates the same virtual file that is accessible while cwm is running that shows you your msl. Having this kernel on your boot partition means that you can read your msl using an app file browser and text reader.

20120922132721.jpg
Click to expand...

Thankyou very much pune, exactly what I was trying to figure out! :D
 
landonh12 said:
Instructions for flashing the kernel?
Sorry if all this asking is annoying. Great work guys and keep it up.
Click to expand...

Okay I'll spare ktb the aggravation....just go into recovery and flash the zip like you would a custom rom.....install zip from SD card>>>choose zip from SD card>>>update.zip (wherever you saved it)
 
DsyMnapTic said:
Okay I'll spare ktb the aggravation....just go into recovery and flash the zip like you would a custom rom.....choose zip from SD card.
Click to expand...

Yup.

Or the internal sdcard if you leave it in /sdcard/Download/ or move it to /sdcard/ after downloading directly to your phone. The normal choose zip from sd card is linked to the external microSD if you have one.
 
I'm looking at the cause of the goofy timestamps on the nandroid backups. When the recovery app starts up, it uses ctime( time(NULL) ) and prints the correct time ins the log file. So we know it is able to get the right time that way. The nandroid code is using strftime(backup_path, PATH_MAX, "/sdcard/clockworkmod/backup/%F.%H.%M.%S", blablablabla ); when it generates the time stamp path name.

The way they are getting the string in the second method works fine when I try it with the NDK. Does anybody have any ideas about where in the recovery source tree the actual bug is? Or if not, do you have any suggestions for a workaround?

Nevermind. the log times are wrong, too.
 
When I was in the recovery, I went to flash the kernel but changed my mind because of the risk, so I went to back out and it said back button is disabled. So I pressed the back soft key and it went to the main menu, but when I chose something, the screen would flash and then go back to the main menu. Battery pull got me out of it and my phone is okay. Any thoughts?
 
I think thats a "feature" of cwm. Scroll down through the whole menu 3 times to disable it and 3 more time to enable it.
 
Yeah that is a irritating feature of CWM. If this happens you can do as GP said or when this happens it adds Back at the bottom of all the menu's. You can scroll and select back to return to previous menu. During this time it disables the back key and it just flashes the screen

EDIT.. GP I see what landonh was seeing. Normally when the back button gets disabled it only disables the back button and you then have to select back in the menu's. But when back button gets disabled it also disables the search key as select.

I was able to get out of it back scrolling thru menu until it said back button was enabled and the search key worked again
 
Hello all,
I've tried installing this CMW and get this:
" cannot open for read: No such file or directory".
I'm staring at the CMW in my /sdcard and it's mounted as r/w.

Thoughts?
 
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?
 
You must log in or register to reply here.
Back
Top Bottom