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
Related
Here is the initial release of my kernel. I'd like to have some other stuff fixed/working, but for now, this is it. I've made a lot of changes and I tried to list them all below, but I know there is stuff that I missed. Currently, the only issue that I know of is that the boot animation will be out of sync and may skip on boot. I have currently retained the stock boot animation, but custom boot animations are also possible if people would like them.
Also, while this kernel can work for recovery, I currently have not tested it, so recovery will remain what it is (ie. jt1134's CWM). I plan on testing recovery soon and releasing an updated Odin for it, as well as just having the kernel zip re-flash recovery.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0807
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB storage in recovery
0730
Custom boot animation support
Updated recovery
0710
Voodoo Sound V10
Updated CWM Recovery
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Test CWM and flash recovery partition
Smooth out boot animation
Get an overclocking kernel out
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
Legend
voodoo/novoodoo - voodoo has the lagfix, novoodoo doesn't (I hope this was obvious)
Frequently Asked Questions
How do I install this?
You flash this in CWM. If you need CWM, you can find it here
Can I use ROM Manager to flash this?
If you didn't use Odin to flash CWM, this will not work. Also, ROM Manager is not compatible with CWM when it fully replaces stock recovery.
Can I install this over another Voodoo Lagfix kernel?
Yes. Any kernel that use's supercurio's lagfix can be flashed over any other kernel that uses it.
How do I disable Voodoo Lagfix?
Create a file on the SDCard named disable-lagfix within the voodoo folder (/sdcard/voodoo/disable-lagfix). You can also use the option in the Voodoo Control app (from the market) or the option in CWM Recovery to disable the lagfix.
How do I know if it is installed?
Go to Settings > About Phone and the kernel version should read:
Code:
2.6.32.9
[email protected] #1
Will this work with xxx ROM?
This will work with any currently available ROM that is posted here.
Can I overclock with this kernel?
No. Currently overclocking is not supported. I do plan on looking into implementing this in a future version though.
Can I use SetCPU with this kernel?
You can use SetCPU with this, but do not use profiles. If you have problems and are using profiles, I'm not going to try to fix them as profiles do not work properly on any SGS phone that I've seen.
Does this kernel include xxx feature?
If it is not listed in the first post, probably not. To be sure, check the commits to the source on Github.
Can you add/implement xxx feature?
If you can link to what you want added/changed, I can look into doing so. If you just say something like "I want bigger quadz!" with no information about what you want or where to find it, I'll just disregard your request.
I am having xxx issue, can you fix it?
See the NOTES section above. Failure to provide any steps to reproduce your error, or a log of the issue as it is occurring will not get your problem fixed. I need the output from logcat and/or dmesg to be able to fix problems. Use the following to obtain a log (easiest with ADB).
Code:
adb shell dmesg > dmesg.txt
adb logcat > logcat.txt
Enter one of the commands and attempt to recreate your issue. Logcat will run constantly until you stop it (disconnect the phone, or ctrl+c). Dmesg will dump the current buffer and end. Try to get a logcat first as it will be easier to capture the error. PM me the files once you've collected them and I will look into it. DO NOT POST THEM IN THE FORUM. Logcat and dmesg may both contain identifying information (like your phone number or email address) so PMing them to me will prevent everyone from seeing this info. If you need help, ask or join IRC.
If you would like something added to the FAQ, please post it in the following format:
Code:
[PLAIN][b]Put the question here[/b]
Put the answer here[/PLAIN]
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
papi92 said:
Flash in cwm.
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Yes, added installation instructions to OP
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Blanco954 said:
So if we already have voodoo lagfix installed based on other kernel do we try the non lagfix ver or is it ok to install the new file with lagfix included?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
If you have lagfix enabled you just flash the voodoo kernel, or disable lagfix and flash non-voodoo kernel if you want RFS file system
Thanks Hopper. I will give this a try.
Sent from my SCH-I510 using XDA Premium App
Worked like a champ for me...thank you!
Sent from my SCH-I510 using Tapatalk
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Flash, flashed!
Thanks again, imnuts!
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
We currently have only one cwm which is jt's, so I don't quite understand what you mean.
froodyo said:
confirming my noob status again:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
You do not need to go back to ed1. Just flash the appropriate kernel.
Click to expand...
Click to collapse
Thank you very much.
papi92 said:
Do we disable the lagfix the same way as we do with jts?
Click to expand...
Click to collapse
Yes, lagfix is disabled the same way with any kernel that uses supercurio's Voodoo Lagfix.
froodyo said:
I can just use CWM and install this right over your debloat and JT's kernel? OR, do I need to go back to non-voodoo ED1?
Click to expand...
Click to collapse
Kernels are almost always independent of the ROM, so yes, you can install this regardless of what ROM you are running (Stock, debloated, something else). If/When we get a non-TouchWiz based ROM, this may change, but for now, you can use this with anything currently available.
hoppermi said:
If you currently have lag fix enabled, you can only flash the voodoo kernel. If you do not have lagfix enabled, you can flash either kernel.
Click to expand...
Click to collapse
I set up novoodoo to try and avoid issues, so if you were on voodoo and didn't disable, the novoodoo should still work, but why risk it if you don't have to?
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Manjews said:
So I flashed the voodoo kernel and now my charge keeps randomly freezing and rebooting
Click to expand...
Click to collapse
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
hey i come from the fascinate and i love your work can't wait until you get voodoo sound working
i will be rooting a friends droid charge soon and then i will set him up with JT cwm voodoo and your kernel
glad to see some devs i already know working on the droid charge
khanfuze said:
Are you doing any under clocking? I had this problem before the new kernel trying to under clock with the screen off.
Click to expand...
Click to collapse
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Manjews said:
No but I think it might be set cpu related issue. I had the scaling set to on demand. I turned it off and so far it's running smooth with no issues.
Click to expand...
Click to collapse
Good to hear Samsung released broken cpu governors again
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
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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. Please do some research if you have any
* concerns about features included in this ROM before flashing it! YOU are
* choosing to make these modifications, and if you point the finger at me
* for messing up your device, I will point that finger back at you and laugh.
* Then I will put it in your eye.
*/
By using the ROM you agree with the above terms!
This thread is for the latest unofficial builds of CyanogenMod 7 for the Samsung Galaxy S 4G. This version is based only on upstream CM7 (currently CM 7.2.0 RC1). We have not made any theming changes, apk changes, etc. It's exactly how it would be on any other phone that receives CM7 nightlies (usually just slightly more broken). CyanogenMod 7 is stable enough on this phone where it can be used as a daily driver, provided a feature that you require is not broken. That said, you may encounter issues, so don't rely on everything. This is a beta port but we're getting very close to being ready to start the process of becoming official.
This thread is for development. If you have a problem and don't post logs (where relevant) or provide any detail, I will ignore you.
Please report issues with proper grammar, thorough explanation, and speak in a respectful manner. If you are reporting an issue that has already been reported, post some logs (logcat, dmesg, kmsg, last_kmsg, etc).
Working:
MTD and YAFFS2.
Tiny Preempt RCU in the kernel for lower memory allocation overhead.
ClockworkMod Recovery (CWM) 5.0.2.8
Power Management
2D and 3D Graphics
Sound
Brightness control
Modem/Radio/RIL
SMS/MMS
WiFi
BLN (Requires the use of neldar's BLN application. Use the pro version for the best experience)
Ringtones
Vibration
GPS
Rear Facing Camera
Front Facing Camera *New
Camcorder
Video Encoding and Decoding
cpufreq/underclocking, etc. No OC/UV.
Rebooting to recovery
USB Mounting in Android and Recovery Mode
Wireless and Wired Tethering
Bluetooth
Voodoo sound
911
Broken
Rebooting to download mode (not sure if anything can be done about this, short of hacking the bootloader)
Car/Desk dock audio
TV-Out
WiFi-Calling
Known Issues/Bugs
Check the Device Issue Tracker and the Kernel Issue Tracker
WiFi reception is reportedly poorer than the KJ6-based ROMs. (Please report if the new wifi driver has helped!)
If you find more issues, please check with CM7 gerrit before you think it's a problem with something we've done.
If you find an issue, please provide any relevant logs. It's also preferable to post it to our github issue tracker.
If the error is occuring in /proc/kmsg or /proc/last_kmsg, it's definitely kernel related. Post it on the Kernel Issue Tracker
If the error is showing up in logcat, chances are it can be fixed through modification of our device tree. Post it on the Device Issue Tracker.
Github/Changes: https://github.com/teamacid/
Instructions are in the second post.
Builds are in the third post.
Instructions
Build instructions: http://forum.xda-developers.com/wiki/Samsung_Galaxy_S/SGH-T959V/Building_From_Source
Get the build from the thrid post. Make sure you read all the instructions before trying anything!
INSTALLATION INSTRUCTIONS:
Installing CyanogenMod 7 @ SGS4GWiki
Builds & Modems
Builds & Modems
Builds
DO NOT attempt to flash these using ClockwordMod Recovery (CWM) 3.0.2.8
Twelfth Release (R13) - 03/22/2013 (04:37:48PM CDT) - Available on GooManager
update.zip:
Goo.im
Mirror
(md5sum: 48fabdf8be3fe2e52acbb6c008663b90)
Twelfth Release (R12) - 07/03/2012 (10:17:48PM CDT) - Available on GooManager
boot.img
update.zip (md5sum: a37b342792132316cb2a44f61cd0e542)
Fixed Eleventh Release (R11B)
boot.img
update.zip (md5sum: 5ea86295ef6a095cab83be6cc848def0)
Eleventh Release (R11) - 06/14/2012 (09:17:23PM CDT):
boot.img
update.zip (md5sum: b27ab2d86890381ce4109d613dedff46)
Tenth Release (R10) - 05/21/2012 (9:27:38PM CDT):
boot.img (debug version )
update.zip(md5sum)
Debug note: The debug version is meant to be used temporarily, when debugging a specific feature where extra kernel debugging is needed. Because of this, no external modules such as wifi are provided, causing wifi to no longer work until you go back to the regular boot.img.
Ninth Release (Fixed) (R9B) - 05/10/2012 (11:53:47PM CDT):
boot.img
update.zip(md5sum)
ADB Note: You need to use the Google USB drivers from now on, as opposed to the Samsung drivers. The Samsung drivers are only used for Heimdall/ODIN now, and not ADB.
I broke it. Use R9B.
Ninth Release (R9) - 05/10/2012 (06:15:24PM CDT):
boot.img
update.zip(md5sum)
Eighth Release (R8) - 04/30/2012 (12:43:31AM CDT):
boot.img
update.zip
Seventh (1st Reset) Release - 04/21/2012 (01:41:41AM PST):
boot.img
update.zip
Sixth Release - 04/19/2012 (6:47PM PST):
boot.img
update.zip
The download links to these are in the old thread, you shouldn't be using them:
Fifth Release - 04/18/2012 (2:13PM PST):
boot.img
update.zip
Forth Release - 04/09/2012 (10:17PM PST):
boot.img
update.zip
Third Release - 04/09/2012 (2:15PM PST):
boot.img
update.zip
Second Release - 04/08/2012 (12:15PM PST):
boot.img
update.zip
First Release - 04/05/2012 (8:12PM PST):
boot.img
update.zip
Modems
Here
Just a reminder, there is a "thanks" button for a reason. While devs do like to know their work is appreciated, the thanks button does that as well. We don't need the forum full of a lot of thanks posts. Thread cleaned.
My SGS4g is going up in a rocket this week but after that if I have any free time let me know if I could help you in any way
Incoming internet calls work well. I'm using my sgs4g exclusively on wifi, so I can't comment on mobile network connection; however, wifi strength is a bit weak.
Sent from my Galaxy Nexus using Tapatalk 2
I'm just glad to see you picked this up m4x
Sent from my SGH-T959V using xda premium
Noooo bryan!!!
Sent from my SGH-T959V using XDA
Happy to see this stay up.
Running R6 currently because I found it had better battery life than R7, even though (maybe because?) it doesn't properly report which apps burned down the battery (Settings->Applications->Battery shows 33/33/31 for the Cell standby/Wifi/Phone idle, with 2% for display and 2% for a game). With R6, from 6am-9pm (15 hours), battery goes down about 50% with moderate scattered usage including some games that burn fast battery.
If any logs are desired with either R6 or R7, just let me know what to run. Thanks.
Glad to see that you are still going to be contributing! That's awesome. You guys have been doing excellent work!
Thanks for all of your help.
In an email I sent to teamacid members:
M_T_M has helped to convinced me to stick around.
I'm gonna take two weeks off from hacking to get my life sorted out
and to clear my mind.
When I come back, my threads (heimdall, cm7, and kernel) will be
unlocked and updated.
Until then, I'll be hangin out in #teamnerd in case you guys need any help.
Click to expand...
Click to collapse
Nice to see you'll be back Bryan. You've done so much for our phone already, and you're a great dev, and put up with more than you should have to. Wish that was enough to make life not suck.
This is great news. My wife always enjoys the updates that you devs provide. Can't wait to see what comes next!
Anyway, back on topic, can't wait to try out this ROM soon
Sent from R2's G2
Not that I don't have access to *nix. but will there be a build to install that is similar to the way everyone is used to such as CWM, Basically a windows version?
Just a question of curiosity, I'm happy to see CM 7 here on our devices and am excited to see a final build once everything has been worked out.
Thank you very much for working on this build and to whoever helps out with it! you are a credit to the community.
neocorteqz said:
Not that I don't have access to *nix. but will there be a build to install that is similar to the way everyone is used to such as CWM, Basically a windows version?
Click to expand...
Click to collapse
Even on the Galaxy S, you have to heimdall the zImage(boot.img... same thing) as the first step to moving over.
After the heimdall step is done, you basically install cm7 through cwm.
We don't have RomManager/GooManager support... yet, but that will be worked out later.
bhundven said:
Even on the Galaxy S, you have to heimdall the zImage(boot.img... same thing) as the first step to moving over.
After the heimdall step is done, you basically install cm7 through cwm.
We don't have RomManager/GooManager support... yet, but that will be worked out later.
Click to expand...
Click to collapse
If you talk to pawitp over on that side, he can walk you through the two-stage recovery flash we do now. Going from BML to MTD does not require heimdall or Odin anymore on the i9000, Captivate, etc.
sixstringsg said:
If you talk to pawitp over on that side, he can walk you through the two-stage recovery flash we do now. Going from BML to MTD does not require heimdall or Odin anymore on the i9000, Captivate, etc.
Click to expand...
Click to collapse
Yes, our cm7 build uses the same two stage recovery.
But for some reason, I still have to heimdall the boot.img.
https://github.com/teamacid/android...mmit/7b72e16d2dc37ca8cd81e22357b98a5187656cce
and
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/blob/gingerbread/mkshbootimg.py
(edit): Unless... something changed with their two-stage recovery...
sixstringsg said:
If you talk to pawitp over on that side, he can walk you through the two-stage recovery flash we do now. Going from BML to MTD does not require heimdall or Odin anymore on the i9000, Captivate, etc.
Click to expand...
Click to collapse
http://www.quickmeme.com/meme/3oz1a6/
on topic: didn't want to leave CM7, but i'll be back once bryan comes back
After using it for two days, I'd say the the rom is very stable. Battery is relatively great. I'm not having the wifi or 4G issues that people are talking about. USB transfer worked for me once yesterday, but now when I try to hit the message about connecting to the computer (can't remember what it says exactly) in the notification menu, it doesn't open the option. Other than that though, everything is great.
Also, I think FB's instructions for installing the rom should be pasted here. It's what I used, and it seems to have caused zero issues.
bhundven said:
Yes, our cm7 build uses the same two stage recovery.
But for some reason, I still have to heimdall the boot.img.
https://github.com/teamacid/android...mmit/7b72e16d2dc37ca8cd81e22357b98a5187656cce
and
https://github.com/teamacid/android_device_samsung_galaxys4gmtd/blob/gingerbread/mkshbootimg.py
(edit): Unless... something changed with their two-stage recovery...
Click to expand...
Click to collapse
I think it might be, because the partition layout differences between bml and mtd, but at that point the real differences only exist beyond the system partition.