CWM 3.1.0.1 PURPLE UPGRADE WITH RFS/EXT4/USB MASS STORAGE SUPPORT!
Some of you might be asking,
WHY DID I DO THIS?
Well, as soon as I released cwm 3.0.2.5, I got requests from all over the epic community, to make some changes to cwm, changes I couldn't incorporate, until I learned to compile the ClockworkMod binary itself. So, with some help from skeeterslint and Rodderik, I did just that...
So, the changes in CWM 3.1.0.1 purple are:
* USB Mass Storage working from the menu, and top text changed, to reflect safe removal of sdcard from PC *before* leaving USB Mass Storage menu
* Purple text and icon color, everyone seemed to hate the orange color
* Key Codes fixed, menu is now the select key, and top text changed to reflect this
* Only one "No" in confirmations, only need to click down once to get to "Yes"
* Built-in busybox is full Cyanogen busybox 1.16.2, with --install -s feature built in
* sd-ext ext4 partition listed in recovery.fstab, a direct change from koush
* Compatible with cwm 3.0.2.5, and has been tested by many in irc.fossnet.info #epic channel
These features are the direct results of feedback from both devs and users in the irc channel... so, if you want input on things like this in the future... it pays to be involved in the epic irc channel!
Please note: some people have had the samsung recovery appear after this flash, and in my testing, in some circumstances, the stock kernel can actually flash back the stock recovery. Due to this, I highly recommend that anyone flashing the new cwm with this flash, please also flash my clean kernel, located here: Clean Kernel EC05 thread Also note, that the one click version of this should not have this problem, since it takes away the ability of the stock kernel to flash the samsung recovery.
OK, there's been some confusion to what the recovery kernel is and does... even among developers at times... so let me explain, before you download:
This flashes the recovery partition of the phone. When I release a CWM upgrade, I am flashing bml8, which is the recovery partition. The recovery partition is only booted when the phone is powered off, and a 3 finger boot is performed, using vol down, camera, and power, held down until the menu appears.
Reboot recovery relies on the kernel (bml7), or a cwm redirector (from the stock kernel, is what the one click root does) to provide cwm, which is why you get an older cwm version with reboot recovery with most kernels. My Clean Kernel EC05 was made to provide a bassline for other kernels for cwm reboot recovery, so until other kernel devs incorporate the new recovery into their kernels, the Clean Kernel is the only one that does reboot recovery to cwm 3.1.0.1. I hope this clarifies things a bit.
I have been actively training other kernel devs on how to incorporate cwm reboot recovery into their kernels, so that koush himself can start pushing cwm updates officially through ROM Manager. This is how ROM Manager is intended to be used (and once was, before ext4 invaded the epic development scene)... but for this to happen, the new recovery needs to be standardized, and everyone on the same page, for this to happen. I know koush will be ready to push official cwm updates for the Epic through ROM Manager, as soon as we as a community are ready for it.
NEW!!! Thanks to qbking77 for making this video, showing both install methods in action, for those that just hate to read instructions:
http://www.youtube.com/watch?v=dsRA7q4JWPQ
DOWNLOADS
cwm3.1.0.1.purple.zip
Flash this with your current ClockworkMod to be upgraded!
NEW!!! If you have problems with the flashing the zip, or just wanna use Odin, here is an Odin flashable tar will get you all squared away, with a quickness, just load the file into the PDA slot of Odin
cwm3.1.0.1.tar.md5
NOTE: if you're phone won't boot after flashing the zip from cwm, just flash this, there is no need to flash a complete stock tar.
Notes:
* This flashes bml8 kernel only, this kernel is stripped of bloat, for minimal file size
* 3 finger boot required to enter the bml8 recovery from power off
* Key assignments: vol/keypad up/down= up/down, camera button/menu softkey/keypad enter= enter, back softkey/power/keypad delete= back
hehe: has mkasick keyboard patch, so thumbing is faster!!!
* Full restores of backups done from prior cwm versions may not be possible. Do backup and restore > advanced > {choose backup} > and selectively restore the partitions you need.
* Once new backups are performed, those backups can be restored to *either* rfs or ext4.
* Now backup and restore includes both the kernel and recovery too
* Use in conjunction with my Clean Kernel, for ROM Manager support, other kernels will soon follow suit:
Clean Kernel EC05 thread
credits:
THE COMMUNITY!!!! I HAVE FINALLY SEEN DEVS WORKING TOGETHER IN WAYS I DIDN'T THINK WERE POSSIBLE...
LET'S KEEP THIS UP, AND KNOW THAT COOPERATION BENEFITS EVERYONE!!!!
* kain203: donated the use of an 8 core linux machine for my use in compiling kernels and the cwm binary. This *greatly* increased my productivity, and allowed me to edit and compile everything for cwm and my kernel, *all* from my Epic 4G, believe it or not...
* Rodderik: without his initial kernel training, I never would have gotten this done at all, also, helping with installing packages necessary to get cwm to compile, he also generously provides the hosting for these files you're downloading.
* koush: the friggin man! The creator of ClockworkMod and ROM Manager! He gave me the advice I needed to finally get dual fs support!
* tanimn: for hosting of cwm koush files in this github, and sharing experience that was genuinely helpful
* vocaltreat: the cwm3.1.0.1 purple clockworkmod icon
* skeeterslint: help in getting cwm to compile, and pointing me to files to edit, from his prior expertise on cwm
* mkasick: for the keyboard sysfs patch, for faster key response
Notes for sources:
The Samsung kernel, ClockworkMod, and busybox, are *all* open source, and as such, mods to all, should have the sources included. Since I like to *practice* what I preach, here are all the sources for the CWM kernel, recovery, and busybox edits:
https://github.com/DRockstar/CWM-3.1.0.1-Kernel
https://github.com/CyanogenMod/android_device_samsung_epic4g
https://github.com/DRockstar/android_bootable_recovery
https://github.com/DRockstar/android_external_busybox
Nice work. You going to make this a one click method?
Nice thanks for this man flashing now.
Sent from my Epic S 4G using XDA Premium App
Sweet!!!!
Is this compatible with EE03? I see it flashes a kernel and assume that it isn't compatible with the gingerbread leak.
ebejoe said:
Is this compatible with EE03? I see it flashes a kernel and assume that it isn't compatible with the gingerbread leak.
Click to expand...
Click to collapse
Yes it is. Just flash it through your current clockwork.
Awesome work. Flashing from Yellowstone.
Sent from my SPH-D700 using XDA Premium App
qbking77 said:
Yes it is. Just flash it through your current clockwork.
Click to expand...
Click to collapse
Flashed and is working well. Nice work.
Now I need that initram for my kernel drock! Goodjob..
Sent from my SPH-D700 using XDA App
Awesome Job Pimpin'!!!!!
Sent from my SPH-D700 using Tapatalk
I almost forgot to post all of my sources for this, which is very important to me... sources for the cwm Kernel, recovery, and busybox, are all listed at the bottom of the post.
Worked perfect first try. I actually am using Genocide 1.1 kernel and had no problem. Thank you for the hard work. The purple looks sharp. I can see a purple and black theme in the future now
Sent from my SPH-D700 using XDA Premium App
Really like not having to scroll through so many "NO"'s just to flash something.
Excellent work
The busybox is awesome too.
Will this work correctly on gingerbread or will it mess up the kernel?
Sent from my SPH-D700 using XDA App
marcusant said:
Will this work correctly on gingerbread or will it mess up the kernel?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Flashing this cwm kernel to bml8 won't affect the gingerbread leaks, just do not flash the Clean Kernel on the gingerbread leak, or the phone won't boot.
DRockstar said:
Flashing this cwm kernel to bml8 won't affect the gingerbread leaks, just do not flash the Clean Kernel on the gingerbread leak, or the phone won't boot.
Click to expand...
Click to collapse
I am aware about the 2nd part. Can I include this in my rom?
Sent from my SPH-D700 using XDA App
I've been using this with ee03 and it works fine.
Sent from my SPH-D700 using XDA Premium App
1. Can you make a version in red?
2. Can I use this in my rom?
Sent from my SPH-D700 using XDA App
marcusant said:
1. Can you make a version in red?
2. Can I use this in my rom?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sure, you can use the recovery in your ROM...
As for the red, it does entail a minor edit with a recompile of the binary, and repackage of the kernel... atm, my donated vm is down, but perhaps later I can do something for ya
Just did my first theme flash from the new recovery. Its so much better not having to scroll through the "NO's." I didn't think it was that big of a deal at first but it really is much better. Great job.
Sent from my SPH-D700 using XDA Premium App
Related
This kernel is intended to be a simple rooted kernel, based off samsung stock, with only simple mods ... its feature are:
NEW!!! NOW HAS CWM 3.1.0.1 RFS/EXT/USB CWM REBOOT RECOVERY AND ROM MANAGER SUPPORT!
I do think this will be my last froyo kernel build... unless some bug comes up, that has to be fixed...
Kernel developers: feel free to rip my initramfs, for cwm 3.1.0.1 reboot recovery, it should work with all known builds, and may need just a little editing of the .rc files and sdx.sh in /sbin, to get your mods in place. The github is updated, and is ready for prime production!
Changes and features as of v1.05:
* CWM reboot recovery updated to 3.1.0.1 Purple edition, with customized recovery for the Epic4G
* Voodoo sound updated to v9, from supercurio
* busybox 1.18.0 removed, and cwm recovery busybox full 1.16.2 is replacing it, making the kernel even smaller
* thumbEE kernel support reverted, as my testing indicates that deep sleep is affected, draining battery faster
Changes and Features as of v1.04:
* ClockworkMod 3.0.2.5 Reboot Recovery, compatible with RFS and ext4
* fixed busybox DNS, thanks Rodderik!
* Added scripts for USB Mass Storage, mountums & umountums
* Voodoo Sound Driver v8 update, from supercurio
* RNDIS / wired USB tethering support built in from kernel
* THUMBEE built in from kernel for cortex a8 optimization, thanks Rodderik!
* build_kernel.sh modified to reflect EpicCM/nullghost script, but with some special revisions.
* rclean updated, to clean root files without any errors, in case would like to be used, before a stock kernel flash
* Root and busybox with minimal system mods
* designed to allow OTA update after flashing back the stock kernel, provided the user hasn't modified other necessary system files
* RFS and ext4 compatible
* REBOOT RECOVERY TO CWM 3.0.2.5 BOTH RFS AND EXT4, ROM MANAGER COMPATIBLE
* CIFS, TUN, & TMCPSS Clamping enabled from kernel
* market app malware patch, writing blank /system/bin/profile at boot
* mkasick sysfs keyboard patch, with my keytimer script
* voodoo sound 7 by supercurio, controlled by voodoo control app in android market
* additonal custom scripts in /sbin for cleaning root, busybox, and flash kernels and recoveries
This kernel was built to replace the traditional one click root method for my all in one root and recovery script.
Link:
DRockstar.Clean.Kernel.EC05.v1.05.zip
NEW!!! for flashing with Odin, we'll have to get used to this, in future, for rooting the phone by flashing a rooted kernel
You can use this odin flash to effectively root the phone:
Clean.Kernel.EC05.v1.05.tar.md5
Sources:
http://github.com/DRockstar/Clean-Kernel-EC05
Credits:
* kain203: donated the use of an 8 core linux vm for my use in compiling kernels and the cwm binary. This *greatly* increased my productivity, and allowed me to edit and compile everything for cwm and my kernel, *all* from my Epic 4G, believe it or not...
* noobnl & joeykrim- this kernel was originally inspired by noobnl Andromeda kernel for eclair, and uses the same joeykrim root and busybox method
* Rodderik, without his guidance, patience, and original working victory_03_defconfig, this kernel wouldn't have been possible. Some commits in sources taken from his sources.
* supercurio, for his voodoo sound, commits directly from his github source
* mkasick, for his sysfs keyboard patch
* nullghost and tanimn, for help getting github set up, and having easy to follow github sources
* koush, for ClockworkMod, and help in finally getting dualfs support, and direct input for cwm
* vocaltreat, for purple cwm icon
* skeeterslint and Rodderik, for helping me get packages installed, and ClockworkMod binary compiled
Sent from my SPH-D700 using Tapatalk
NICE!
Do you BONSAI?
Nice work man keep it up!
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
contradude said:
goodness, I went to vote this 5star and my machine hiccupped and rated it one star. your work here is awesome, keep it up
Click to expand...
Click to collapse
You can always go back, and revote the star rating...
Sent from my SPH-D700 using Tapatalk
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
lattiboy said:
Hey there, thanks for this, but I'm unable to update profile or prl. I get the unknown error. I am running ace rom v2. Any tips?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Good work man.
Sent From My Evo Killer!!
blazinazn said:
There was a fix for this in another thread. I don't think it's related to the kernel though cause I was able to update my profile and prl successfully.
EDIT: This is the thread I was referring to, may want to check it out:
http://forum.xda-developers.com/showthread.php?t=1041415
Click to expand...
Click to collapse
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
lattiboy said:
Thanks. I followed the instructions, but it now says "Internal Error". Hmmm.....
I wouldn't care, but to use my Airave correctly I'm supposed to update PRL and Profile.
Click to expand...
Click to collapse
Strange, you may want try rebooting the phone and trying again. This issue should have been resolved but then again I always had problems updating the profile/prl even when it wasn't on Sprints side with my first epic. I got a replacement (refurb) and haven't had any issues since.
Why would someone rate this thread less than 5 stars? ...
Anyways great job dude you released some good stuff
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
LiberatorUSA said:
Hey DRockstar,
good work on putting out a clean kernel. I havent had any time to look into the modem delta thing lately.
Since you compiled the kernel you must know if the USB driver is compiled into the kernel. I'm suspecting it is right? If so maybe flashing a new kernel can actually fix my USB problem.
Click to expand...
Click to collapse
I didn't mess with the usb drivers, and no one has reported any problems connecting usb. You can feel free to see if this fixes your USB problem, but I doubt it will have any bearing on it, honestly.
Sent from my SPH-D700 using Tapatalk
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
LiberatorUSA said:
Well I still don't understand how people with DK28 can have USB problems since they seem like independent systems. So if flashing DK28 screws up a USB config or something then flashing a new kernel might help. Its a long shot but worth a try.
Do you know if this one works with CM7 A4?
Click to expand...
Click to collapse
No, it won't.
I wish I could give this a try right now, but i don't have a computer to install clockwork on my phone. guess i'm waiting till quitting time.
just a side note the link in the OP has a typo
http://drockstar.devphone.org/EpicKernel/DRockstar.Clean.Kernel.EC05.v1.02.zip
Does anyone know, is there something like this I can flash, that will give me ext4 cwm3? Cant get to a computer right now.
Oops, wrong thread.
Sent from my SPH-D700 using Tapatalk
Can someone point me in the direction of a clockworkmod flash that doesn't also root. all the ones i have found seem to be expired links
Can't wait to try this. Thanks
@ masterface: Use the one posted by Dameon. Right click to open it. Open in new window. Then you should be able to download it like normal instead of getting blank page. Hope that helps
Sent from my SPH-D700 using XDA Premium App
OK guys, you have NO idea what it has taken to get to this point...
Welcome to the first officially supported ClockworkMod for the Epic 4G since cwm 2.5.1.0, I think it's been over a year now...
Changes since 3.1.0.1:
* Backups are tar files by default, with the filesystem type noted in the filename. Backups automatically reformat to the backup filesystem before restore. This will work to restore rfs and ext4 setups. So, for example, if you're currently on rfs, but your backup was done while on the ext4 filesystem, the restore will reformat back to ext4 before restoring. Older backups done by cwm 3.x and ACS Recovery can be restored by this ClockworkMod version, and will not reformat before restoring older backups.
* This cwm is not meant for mtd partition layout / yaffs2 filesystem, that is another matter entirely, and mtd will require it's own cwm build and kernel, that will most likely be in the official CM repo when it's done.
* One "No" in confirmations, for all but factory wipe: Make a blank file called .one_confirm (that is a period in the beginning of the name), and place it in /sdcard/clockworkmod directory. This works right now with 3 finger boot from power off, but will be added to the next Clockwork Recovery update in ROM Manager. When that happens, then it will also work from the option Reboot into Recovery, when called from ROM Manager. This is now official, so that in the future, anyone with ClockworkMod 5.0.27+ will be able to benefit from this. Thanks to chris41g for this edit and push to the official source.
* Keycodes were fixed to work with the gingerbread kernel... and menu was fixed up a bit.
up = vol up, keypad up, keypad left
down = vol down, keypad down, keypad right
back = back cap key, power button, keypad backspace key
select = home cap key, keypad enter key, camera button
toggle display = keypad d key
reboot = power button 5 times, no matter where you are in the cwm menu
NOTE ON KEYS:
If your current kernel is a froyo kernel, then the cap keys will be reversed... We will have some growing pains, until everyone is on board with gingerbread, and the kernel devs start implementing the kernel mod described below, to change the mode of reboot recovery to go to bml8 recovery partition. If you are running gingerbread, then you can flash this prerelease:
Clean_Kernel-2011-11-20-15.51.32.zip
md5:389f5b1745352326c9357c1252cd37b9
This isn't exactly finished yet, but it's stable, and has voodoo sound, root, busybox, etc.
* DO NOT REPARTITION YOUR SDCARD WITH CLOCKWORKMOD. There are problems associated with this that I will detail later.
* I highly recommend flashing both the new recovery kernel and the ROM Manager update... pretty soon, ROM Manager will be able to flash our favorite ROMs, by downloading and flashing from ROM Manager.
* FOR USERS OF ACS RECOVERY:
At this time, I recommend flashing the new cwm over ACS Recovery. Testing has shown that backups done when the ROM Manager fakeflash is called through ACS Recovery, is that the backups won't be in the proper format... they will probably work, but not in the way the CWM 5 intends it too, with fs saved tar backups.
I know that some of you are avid fans of ACS Recovery, and I have nothing against that. In fact, it should be pretty easy for chris41g to make a new version if he so desires... and, he did contribute to the official source, which is something I truly appreciate In fact, I have been working with koush, to get some other of the most requested features, into the official cwm sources, so they can benefit everyone in android. One of the first new features to be put into the next cwm update in ROM Manager, is the ability to have only one "No" in the confirmations, if the file /sdcard/clockworkmod/.one_confirm is present. chris41g authored this for the cwm sources. Also, we have been given the go ahead to implement the inclusion of reboot into download mode from the main cwm menu in the official sources as well
WHAT TO DO IN ROM MANAGER:
Firstly, flash the new recovery with odin/clockworkmod.
Also, I'd recommend a known working kernel for the new recovery:
Clean_Kernel-2011-11-20-15.51.32.zip
md5: 389f5b1745352326c9357c1252cd37b9
This isn't exactly finished yet, but it's stable, and has voodoo sound, root, busybox, etc.
Nubernel by nubecoder for gingerbread
other kernel devs feel free to link me to your posts!
Get ROM Manager from the market, and choose Flash ClockworkMod Recovery.
Choose the Samsung Epic4G.
It should then download, and you should see ClockworkMod version: 5.0.2.7
Now, whenever you use ROM Manager for anything, it will automatically load the latest supported ClockworkMod for the Epic.
DEVELOPERS: Please visit this forum thread, and learn all you need to know about getting your zips listed in ROM Manager, and the features available for you to use.
KERNEL DEVELOPERS: It is highly recommended at this time to use this commit, to change boot mode for reboot recovery to boot from bml8 recovery partition:
https://github.com/EpicCM/android_k...mmit/ea1dbf2c9be977aeb6f78d871e0b05d989bfad59
OK, here are the links:
cwm-5.0.2.7-epic4g.tar tar flash for odin
cwm-5.0.2.7-epic4g.tar mirror
md5: edd321a3aa2ba4c73f1d3612e9b19c05
cwm-5.0.2.7-epic4g.zip zip flash for cwm
md5: 869baf2d6a52b5604764f70556c9482e
TUTORIAL VIDEOS COURTESY OF QBKING77:
Flashing ClockworkMod Recovery Kernel:
http://www.youtube.com/watch?v=xuLWzeJ1lT4
Setting up ROM Manager for the Epic 4G:
http://www.youtube.com/watch?v=6KTZj3LOsxc
Thanks goes to:
koush - Creator of ClockworkMod, and very good guy for his patience and willingness to listen to the needs of the Epic community, and the android community at large.
mkasick - help with C code to support rfs formatting in the official cwm sources.
chris41g - inclusion of code in official sources to permit one "no" in confirmations, if file /sdcard/clockworkmod/.one_confirm is present
DEVELOPER NOTES:
Yes, this time there are developer notes! I will be adding more over the next couple of days.
SOURCES
ClockworkMod Binary:
https://github.com/CyanogenMod/android_bootable_recovery/tree/gingerbread
Epic4G device file sources:
https://github.com/koush/android_device_samsung_epic4g/tree/master
ClockworkMod Recovery kernel sources:
https://github.com/EpicCM/android_kernel_epic4g_gb_official/tree/cwm_5.0.2.7-rfs-ext4
I have put the branch trees in the URLs, since the masters could be subject to change in the future.
WHY CWM 5 WAS A CHALLENGE
ClockworkMod version 5 now stores the backup filesystem in the name of the tar backup files. When I first submitted my device files to koush for ROM Manager support, it became clear that now ClockworkMod would have to support the formatting of rfs volumes for the restores to work properly. This took me a while, but thankfully with the generous advice of mkasick, I wrote the function and pushed to the official source:
https://github.com/CyanogenMod/android_bootable_recovery/commit/a8f265dd6f764188d07ea2637d5638b8c64e4a6b
To experienced C programmers, this is easy stuff, but hey, admittedly, I'm a very new to C programming, and I wanted to learn... and I wanted to get it as correct as possible the first time... so this took me a while
RECOVERY KERNEL DETAILS
The important thing with a recovery kernel, is that it only needs to do one thing:
Load ClockworkMod, and anything ClockworkMod might need.
For this reason, there are minimal kernel modifications for the ClockworkMod Kernel. The following details, however, are worthy of note:
* This kernel supports kexec, as in the future, dual boot may become the norm.
* The boot mode for reboot recovery has been modified to reboot the bml8 recovery kernel, and not the boot kernel recovery.
* I left in the keypad timer patch by mkasick, since it really makes a difference in scrolling through the menus in ClockworkMod.
* The initramfs /sbin was modified to only have files needed for ClockworkMod, along with the following scripts and binaries that I often find useful:
bmlwrite - binary to flash kernels
bmlflash - script to flash boot or recovery kernels easily
bclean - script to clean all busybox files from /system
rclean - script to clean all busybox and root related files in /system
FOR BOOT KERNEL DEVELOPERS
It is highly recommended at this time to use this commit, to change boot mode for reboot recovery to boot from bml8 recovery partition:
https://github.com/EpicCM/android_ke...0b05d989bfad59
LESSONS FROM HAVING WORKED ON CLOCKWORKMOD RECOVERY
When I did ClockworkMod 3.1.0.1, I created a custom recovery, with some requested features. However, with time, it became apparent that having an official recovery with ROM Manager support was ultimately more favorable than having a custom one. Furthermore, with just a little effort and cooperation, the official source can be appended to include the most requested features. We're not the only ones asking for those features. I now believe that contributing to the official source benefits the entire community in the end, and not just one or two devices.
Along with my rfs formatting commit, I invited chris41g to contribute as well, and hence his following commit was also accepted, which allows only one "No" to appear in confirmations, when the blank file /sdcard/clockworkmod/.oneconfirm is detected:
https://github.com/CyanogenMod/andr...mmit/a8f265dd6f764188d07ea2637d5638b8c64e4a6b
Again, very simple here, but solves the most requested modification to ClockworkMod probably ever, and now, anyone with ClockworkMod 5.0.2.7+ can enjoy it too!
I really want to thank chris41g for taking the time to contribute. I respect and appreciate his work on the ACS Recovery, and I feel that his work will make even more of a difference in the end- to a lot more people than just the Epic 4G community.
I truly hope that my example can be an inspiration to others, to cooperate with other developers for the benefit of all. This may appear idealistic, but I believe the Epic 4G community has matured and has already started reaping the benefits of this cooperation. I also believe that in learning from others, you are also given the obligation to help others, who will, in turn, help others, and so on. I should hope that the benefits to all are obvious. And with that, I'll stop "preaching"... hehe.
Rockstar! Thanks are in order!
Sent from my SPH-D700 using Tapatalk
Great news!
Sent from my SPH-D700 using XDA Premium App
First page reserve. This recovery is great.
Sharing via any means i can. Gonna get Kevin to do something with our roms now
Great job! Thank you for all the hard work that you put into this!
Sent from my SPH-D700 using Tapatalk
All i can say is wow. Thanks.
Sent from my Legandary Epic or my Galaxy Tab rooted (feels naked without a ROM)
Sweeeeeet!!! Thanks Drockstar! And devs!
Could we get md5's
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
hear the md5 from the cwm flash 869BAF2D6A52B5604764F70556C9482E
Thanks Drockstar!! Been testing it out and it works awesome!
Sent from my SPH-D700 using Tapatalk
Thanks!!! This rocks.
Sent from my SPH-D700 using XDA App
i know this is dumb but i gotta ask what color is it ?
Thank you for this. Since its official and no longer a port does this mean no more having to wipe 3x?
Sent from my SPH-D700 using Tapatalk
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
Basically Cyan/Ics blue
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
It is a cyan looking color...real easy to see/read. Me lovez it!
Sent from my SPH-D700 using xda premium
Digglez said:
i know this is dumb but i gotta ask what color is it ?
Click to expand...
Click to collapse
These are the official colors for cwm 5, pics are here:
http://forum.xda-developers.com/showthread.php?t=1354095
Eins7ein said:
Thank you for this. Since its official and no longer a port does this mean no more having to wipe 3x?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Well, honestly, wipe 3x hasn't been an issue for a while now... if you need to wipe, just do factory wipe from the main menu only once.
The version that flashes from ROM manager has one minor issue - the capacitive back button acts as a select button, but the menu key works as a back button... That's all I've noticed so far, other than the three finger salute going into my previously installed CWM 3.1...
Sent from my SPH-D700 using XDA App
styles420 said:
The version that flashes from ROM manager has one minor issue - the capacitive back button acts as a select button, but the menu key works as a back button... That's all I've noticed so far, other than the three finger salute going into my previously installed CWM 3.1...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well the the finger boot to cwm 3 is sure as hell not right...
sent from my always aosp epic
Got plenty of "no" choices again before getting to a "yes"...that's annoying. Otherwise, pretty cool.
DRockstar said:
Reserved for developer notes
Click to expand...
Click to collapse
DRockstar ... got a question ... R U gonna make us a GB version of CleanKernel that will work with this new CWM ?
READ ME FIRST! This is beta. Some things may not work properly. If you find a problem, please either respond to this thread, or add a bug on the issue tracker on github. Thanks!
Introduction
This kernel is built from Samsung's T959VUVKJ6 Kernel source drop with some slight modifications.
There are plans for this kernel to have voodoo sound, bln, and optimizations in the future.
But for now, stability and code cleanliness are top priority.
The thread title will update as I do. I don't have any scheduled plans, so don't ask for ETAs.
Changes
My code is hosted on GitHub. You can find the latest changes there.
Btw... I actually tag my releases
Plans
I sorta did a little brain dump on what I'm thinking here.
Initramfs
We are now on a new version of CWM: v5.0.2.7
Old backups from previous nandroid's WILL NOT restore with this version, as the nandroid backup format changed.
Also, if you're updater-script and update-binary that are using amend instead of edify, please switch to edify. Amend is no longer supported.
New recovery fixes backup & restore, adds the ability to restart adbd and restart to download mode.
Current Support
AFAIKT, this kernel is basically just like stock, but adds ext4(and jbd2), tun, cifs, fuse, and si4709 modules.
Debug info was recently disabled, which should also speed things up a bit.
ChainDD's Free Superuser.apk and /system/xbin/su are automatically installed/updated if needed.
Same with RaverX3X's bootanimation binary.
Download
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+:
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Flashing
Either flash from CWM or:
Install Heimdall
Extract the zImage from the CWM zip file
Change your directory to where the zImage is
Put your phone in download mode
Run the following:
Code:
heimdall flash --kernel zImage --recovery zImage
Credits
drhonk (cwm+voodoo initramfs)
krylon360
RaverX3X (moral support, testing, bootanimation binary)
SeafoodExpert(aka ericmpanda), FBis251, and zargeus (for testing)
pawitp (thanks again for your help earlier)
supercurio (for voodoo lagfix and everything else!)
ChainsDD (for Superuser.apk and su)
Benjamin Dobell (for Heimdall, my current favorite program)
Last, but not least...
Samsung (for the source, of course)
Release History
Beta 3.1 (an RC): sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
Disable broken DMA Acceleration and Deep Idle.
Nothing else updated. Another kernel update will happen soon
Beta 3 (tagged in git): sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Update CWM to v5.0.2.7
Fix backup & restore
More kernel cleanup
Beta 2d (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2d-unsigned-update.zip
Add bootanimation as a voodoo extension. This will install /system/bin/bootanimation just like su and Superuser.apk.
Updated to ChainsDD's Superuser.apk to build v3.0.7 (41). 'su' is still 3.0.3
Beta 2c (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2c-unsigned-update.zip
Basically reverted back to v0.0.2
Double checked that su and superuser are updated
Worked with Krylon360 and RaverX3X to finally get initramfs bootanimation working. Now the rom just needs the right /system/bin/bootanimation (and it needs to be executable! yea. I ran into that one... :sigh: )
Beta 2b (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2b-unsigned-update.zip
Removed 'disabled' from bootanimation service, as suggested by Krylon360
Updated Superuser.apk and su
Beta 2a (no kernel update, just initramfs): sms-T959V-KJ6-v0.0.2a-unsigned-update.zip
Removed 'disabled' from samsungani service, as suggested by Krylon360
Beta 2 (tagged in git): sms-T959V-KJ6-v0.0.2-unsigned-update.zip
More build clean-up
Disabled Debug Info and a few other debug options for performance
Made ext4 and tun as modules, now also packing cifs, fuse, and si4709
Initial Beta (tagged in git): sms-T959V-unsigned-update.zip
For more details, check out github... really. Everything I do, there is source for!
Changes to the kernel can be found here.
The bug tracker for the kernel is here.
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
jigglynuts said:
awesome work! I am very excited to try this. Downloading now and will update as soon as I have a few minutes to spare.
Click to expand...
Click to collapse
Great! I'm about to pass out... lol.
As the Title says/warns... this is beta2.
I am running this on my phone, as well as a few other people, and we haven't ran into any major issues... yet.
If you actually find a bug, please submit a new bug to the issue tracker on github.
:sleeps:
:happydance
Thanks for your work!
Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding?
Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Updated op with an update to remove disabled from samsungani in init.rc.
Thanks for the tip, Krylon360!
Finally a KJ6 kernel compiled form source! Thanks so much, will try it shortly!
Caligula36 said:
:happydance
Thanks for your work! Mind I ask, i know rfs and ext4, but what is the mtd+yaffs 2 you mentioned adding? Will ext4 voodoo conversions take place in the same manner as before?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Basically, the internal storage on your phone is a flash device.
BML and FSR (aka XSR) acts as a software-based FTL (Flash Translation Layer).
This allows you to put filesystems like fat or ext4 on a flash device.
Hardware FTLs are everywhere. Look at your memory stick for instance. There is an FTL between the usb device controller and the nand flash chips that actually store the data. You can format your memory stick with ext4, btrfs, ntfs, whatever...
Samsung decided to go further down the rabbit hole with RFS, which is basically a modified version of FAT(32?) with ACLs and Journalling. IMO, silly.
BUT, fsr/rfs are proprietary modules and are built with a kernel that has a set of symbols exposed. If I disabled debugging (like I did) and something in one of those fsr/rfs modules depended on it, then the fsr/rfs modules wouldn't load (unless you trick it).
Moving to controlling the flash on the phone (in which the flash type on this phone isn't nand, but OneNAND-Flex) with MTD gets us away from the proprietary modules, but introduces a new problem. Can't use ext4 for /system, /data, and /cache anymore. Instead you have to use a flash filesystem, like yaffs2 (which is what the CM supported Samsung phones use). I would like to see a test on this phone with UBI/UBIFS though. I think that might have better performance then yaffs2 or jffs2 (but almost everything, including my grandma is faster then jffs2... seriously).
It's subtly modified stock, and I'm using the same initramfs (minus kernel modules, of course) that kj1 with voodoo lagfix had (now with boot animation support with the latest update). Lagfix and all should work just as it did before.
Ask, and ye shall receive... (or better, get a whole page about how flash works)
Just what I've been waiting for... I've missed CWM, but wanted to keep the kj6 kernel.
I'll push this later this morning as time permits and see how it goes.
Thanks!
How fast is boot with this?
I am using it with the simply simple rom right now, perfect combination!!!
Sent from my SGH-T959V using XDA App
Will it work with init.d scripts ? lockscreens and thundervolt...
itzik2sh said:
Will it work with init.d scripts ? lockscreens and thundervolt...
Click to expand...
Click to collapse
It's just a kernel it has init-d support and boot animation support.
lockscreens are framework dependant not kernel dependant.
Sent from my HTC Glacier using xda premium
I've been using this for a few hours now on top of Valhalla o/c'd to 1.3ghz and it's been running great so far. Good job man.
Sent from my SGH-T959V using xda premium
how long does it take to boot. Normal or voodoo kernel time.
airfluip1 said:
how long does it take to boot. Normal or voodoo kernel time.
Click to expand...
Click to collapse
Shaved 4-5 seconds off my boot, on Octane 2.x
Sent from my SGH-T959V using xda premium
Running great on icbinb kj6.
Many thanks for this.
Just flashed, no issues so far
Sent from my SGH-T959V using XDA App
Okay, user error... got it flashed with Heimdall after all... we'll see how she plays...
Working well with ICBINB Official KJ6. Nice work. Glad to see some developers are back in action with this phone.
Description
This is an Amon Ra style custom recovery based on drellisdee's (aka getitnowmarketing) source with a few changes added by me.
The "nandroid" script includes code to auto-reboot your phone upon completing a backup, which could be especially useful after a long, compressed backup, but it's never been an option in the UI. I wanted this feature to be included in the backup and restore menus simply for convenience, i.e. restore a nandroid before going to bed so the phone is ready for you in the morning, make a backup while you're mowing the yard so the phone is ready for you when you come inside, etc.
Accordingly, I modified nandroid-mobile.sh to include autoreboot on restore and modified and built a new recovery binary to offer autoreboot in the backup and restore menus. While tinkering with it, I decided to modify the font color and background graphics. Themes and features explained below.
Change Log
Code:
v4.3 - Add Get Current ROM Version to Other menu
Add initial dalvik wipe to Superwipe to ICS and AOKP themes from v4.2.1
v4.2.1 - Very minor
Update mason theme to new logo
Add initial dalvik wipe to Superwipe (forgot it on v4.2)
v4.2 - Add Roboto font (from CEnnis91)
Reorganize and clarify wipe menu, add Calkulin's Clear Temp (wipe Temp Files in recovery) and Superwipe
Center main recovery screen header and switch to all caps
v4.1 - Added two new choices to the top of the wipe menu:
Combined cache & dalvik wipe
Combined boot, cache, data, system (aka Calkulin's FORMAT ALL) wipe
Changed auto-reboot message from "Rebooting recovery..." to "Rebooting phone..."
v4.0.1 - Fixed symlinks to dump_image and flash_image, which should correct any restore issues from v4.0 (thanks drellisdee)
Modified nandroid-mobile.sh and extracommands.c to allow recovery to handle autoreboot versus the script (thanks drellisdee)
Added message and three second delay before autorebooting (thanks drellisdee)
Features
All features from v3.11 + autoreboot + improved wiping options + roboto
Known Issues
None at this time
Important Notes
1. To autoreboot, just select that option along with your other backup/restore choices and run as normal. Upon completion, you will see a reboot message along with a three second delay before rebooting.
2. The AOKP theme is just that-- a themed recovery-- not officially endorsed/supported by the AOKP team so please don’t bother them with anything related to this recovery.
3. Compatible with nandroids made under previous versions of Amon Ra (and probably CWM... dunno, never use it. Someone else that tries- Chime in!)
Download
All versions available here:
http://d-h.st/users/smelkus/?fld_id=5397#files
Latest versions mirrored here:
http://goo.im/devs/smelkus
Install
Using fastboot (using .img)
fastboot flash recovery /path/to/<recoveryname>.img
Using bootloader (using .zip)
Rename file to 'PC36IMG.zip' and place on root of sd card, reboot to bootloader, allow bootloader to scan, volume up to accept update
Special Thanks/Credits
drellisdee (HUGE help- thanks! <-- buy him an energy drink)
Amon_RA (Donate link)
pensive
Koush
Cyanogen
Brainaid and infernix
CEnnis91
Ropodope for testing
There IS no better recovery than this for the evo. No way, no how. It's a pleasure to have this on my phone bro. Thanks for letting me test it. All of the greatness of amonra and so much more. Now xda members get it! Even better.
ropodope
Change, nothin' stays the same. Unchained, and ya hit the ground runnin'.
I'd never trust another recovery on my evo =)
Been running this since it dropped on TCD. It would be foolish to run any other recovery. Thanks for doing this. The reboot script is such a perfect addition.
What about an option for auto reboot in flash menu? When selecting the last item to flash you could check auto reboot instead of going back twice for reboot. Just throwing it out there, not sure if its even possible.
Sent from my PC36100 using xda premium
Download link doesn't take me to download the files.
Clicked on link but no files found
sent from a rooted EVO 4G running Radiance RLS-ONE SENSE 3.5 Anthrax kernel infected!!!!
No files found!
sent from a rooted EVO 4G running Radiance RLS-ONE SENSE 3.5 Anthrax kernel infected!!!!
Yeah, it's broken.
Thanks. Heard great things and I like the themes...his/hers type.
But, there's nothing to download. Does it take time to show up on the site?
Good to see this on xda for everyone to flash and love. I also grabbed it from TCD while checking out the Reloaded Preview. It improves on the already great RA Style 3.11 Recovery. Thanks for working on this and sharing it.
Sent from my PC36100 using xda premium
here it is!
http://d-h.st/users/smelkus/?fld_id=1930#files
ropodope
ropodope said:
here it is!
http://d-h.st/users/smelkus/?fld_id=1930#files
ropodope
Click to expand...
Click to collapse
Which folder am I to look in?
Sent from my PC36100 using Tapatalk
Never mind I found it
Sent from my PC36100 using Tapatalk
Fixed OP, sorry about that.
Smelkus,
Thanks for the new recovery! Like everyone else, i had been on amon ra forever. ropo, LOTK et al recommended your recovery and i'm loving it. i'll recommend elsewhere whenever i can. thanks again!
Nice,works great,thanks.
Sent from my modded OG EVO using XDA
Smelkus
Absolutedly the best...solid with great features
finally a recovery that wipes cache and dalvik in one click.... Thanks alot man
Glad to see more people getting their hands on smelkus' work!! He's the real deal people!!
I can't wait what he has in stored for us in 4.2
Great job again smelkus!!!
Hello Galaxy S users,
Specifically, in this forum, it's Galaxy S 4G.
I know you've been watching T.V., and know (maybe... well here in E-merica) a little about universal health care... well I have something totally unrelated to talk with you about. [word this sentence with Steven Colbert's voice]
Universal Recovery.
As it stands, our bootloaders know nothing about the silly recovery partition on our devices.
And on stock roms, it is a total waste of good space we could put to any other partition (mostly data).
When this topic first reared it's ugly head, I thought to myself about just incorporating the unused space to data. But no! I have seen the light. And it is good!
There are a few different recoveries out there that are mostly a preference thing.
Stock Android Recovery (think the "3e" thing...) (totally friggin stock. No modifications)
ClockworkMod Recovery (cwm)
ClockworkMod Touch Recovery (cwm-touch)
TeamWin Recovery Project (twrp)
manual partition magic (that really only devs know about... [Bryan Jedi waves his hand in your face] forget I said anything here.)
... to name a few. Granted I will not support/help you on the first or last versions of recovery mentioned above.
I would like to use the recovery partition to unify the storage of the recoveries.
As we have seen with the radio partition... On stock, it is a bml partition without rfs. The modem.bin is written (redbend_ua) directly to the bml12 partition and read back by /system/bin/rild
On (Gingerbread(mtd)/CM7/ICS(mtd)/CM9) MTD based roms, the radio partition is a yaffs2 formated partition in which modem.bin's are simply copied to. A symlink (/dev/block/bml12) to allow rild to work correclty... (well and a nasty hack on SGS4G to pad the modem.bin with zeros, because the rild reads more then the size of the modem.bin but less then the size of bml12)
Lets say we format the recovery partition as yaffs2 (or either vfat or ext4 on bml roms), and store ramdisk-recovery-<version>-<fstype>-<recovery-type>.img files there.
Examples:
ramdisk-recovery-gb-bml-cwm.img
ramdisk-recovery-ics-mtd-twrp.img
Then create a cwm update.zip that allows you to switch your recovery based on what is in the /recovery partition.
The title of this post is [RFC]... This is a Request For Comments.
As an amendment to this RFC, I would also like to have universal updater.sh and updater-script files to be created so that one could say, flash:
stock bml gb (cwm) -> ics mtd (cwm-touch)
ics mtd (twrp) -> stock bml gb (twrp)
ics mtd (cwm) -> gb mtd (cwm-touch)
gb mtd (twrp) -> stock bml gb (cwm-touch)
gb mtd (cwm-touch) -> ics mtd (cwm)
...without ever needing to go to download mode to run a oneclick or odin.
This thread should eventually turn into a development thread containing the results of this discussion.
...
A little while back, I started a poll.
The results of the poll, and comments lead me to believe that users are more interested in obtaining root and having the latest version then anything else.
All of these recovery methods should provide root access to install which ever rom you want (rooted or not rooted) and whatever recovery you want to use.
Goals (no particular order):
Run an updater.zip OR run an android app to change the current version of recovery.
Unify the updater.sh and updater-scripts for our roms, so you guaranty that you can flash from any rom to any rom (unless it has not been updated to use this new standard)
Do something with the lost 6-7M of unused space currently known as 'recovery'.
Let me know what you think. I already have a WIP, but it only supports cwm (at the time of this writing. cwm-touch and twrp coming soon...).
I am working on minimal environments (android manifests) to build each specific recovery nightly so that these will always stay up to date with what is in our repositories.
Being an RFC thread, please provide some helpful feedback.
ALSO, I leave this open to other Galaxy S phones as well!
You too have a device with this stupid recovery partition.
If all Galaxy S phones used the same codebase for updater.sh and updater-scripts and for setting the currently used recovery, it would be a win for everyone.
OK, Technical section:
--------------------------------------------------------------------------------------
On the latests CM10, a patch was applied by pawitp a little while back to allow a simpler packing of ramdisk and recovery.
Because of this, you can basically repack the initramfs with a different recovery.
If we changed our stock bml gb kernel, cm7 (and other mtd based kernels) to use a similar recovery method, we could unify the way we change between recoveries.
--------------------------------------------------------------------------------------
...Comments go here VVVVVVVVVVV
As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.
FBis251 said:
As we were discussing on #teamacid, I think I can help with figuring out the mtd -> bml portion of this since most of my previous work has been with installer scripts and the recovery environment.
Bryan was telling me that it should just be a matter of flashing the bml zImage and to reboot and continue the install.
I definitely think that storing the recovery.img files in /recovery would be a great solution. It'll keep the kernel/boot.img files leaner and allow us to update the recovery without messing with the kernel.
Click to expand...
Click to collapse
Essentially, yes. There are two "universal"s here.
Universal recovery selection
Universal updater.sh and updater-script usage
And, yes, kind of... the reservoir may also be apart of the big problem here.
There is much experimentation and discovery to happen before anything really results from this thread.
I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2
I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium
GreyDark said:
I'm interested in the implications this could have to the S devices with a flash counter.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
I know that the sgs4g has a flash counter, but it never increments.
I think it was something they were thinking about, but never got working for the release.
VillaCastana321 said:
I definitely support the movement. What can I do to speed up the process or help with this development?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
I just need to finish my WIP and let other devs at it so they can make changes to it.
The WIP is driven by what is in the OP of this thread. It is not written very well and not very detailed.
I hope that changes over time with feedback.
Having botched my share of kernel/recovery flashes, this would be very interesting if I could always access something that would let me flash a known-good kernel/recovery from microSD when I next mess up.
Admittedly, I could stop flashing unknown kernel/recovery when I'm not within reach of Heimdall, but...
So the SII can use triangle away for the flash counter while with the SIII it's still usable yet not recommended from what I saw. By using dd to get the recovery in, the SIII dodges the counter again, (first time by using Odin to get root) but there can always be people who might even do that wrong. I don't know about the other S devices, but if there was an easy way to get root and a custom recovery, definitely a plus for average users.
Sent from my SGH-T959V using xda premium
I think its a very good idea. It makes perfect sense, I don't see a downside and see its possible. It would be great actually
Sent from my SGH-T959V using xda app-developers app
This sounds awesome... would b willing to test.....
sent from my t959w running RemICS, Voodoo sound, Rom Toolbox pro.
Fun starts in a month or so.
Wait... For... it.
bhundven said:
Fun starts in a month or so.
Wait... For... it.
Click to expand...
Click to collapse
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro
abonides said:
Patiently waiting... teeth clenched....staring at my screen,watching for that post up..... LOL
sent from my t959w running RemICS-UX, Voodoo sound, Rom Toolbox pro
Click to expand...
Click to collapse
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.
Cooptx said:
So you are told to wait about a month, and you are spazing after six days? Wow, really patient.
Click to expand...
Click to collapse
I think he was joking
pisherthefisher said:
I think he was joking
Click to expand...
Click to collapse
I hope so
SMH
Sent from [CONTET DELETED]
love the idea <3
Sorry,my sick twisted humour cannot b appreciated via text.
sent from my t959w running RemICS-UX, Voodoo sound