Related
..::Team Viper Official Sites::..
Team Vipers Official Site
Team Vipers Official Wiki
Team Vipers Official Ticket System
--------------------------------------------------------------------------------------------------------------
Rodderik's 1.2GHz Overclocked Kernel
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip Mirror
Give Rodderik a thanks and buy him a beer, He paved the way for the Kernels with the first OC!!
--------------------------------------------------------------------------------------------------------------
..::Thanks::..
Thanks to ACS for the DK28 leak. Thanks to mysteryemotionz for some of the images.
--------------------------------------------------------------------------------------------------------------
..::Changelogs::..
ViperROM [TRiNiTY v2.0] EXT4-RFS DK28 Dual 4.0.4
Added New Theme
Added ViperWheelWidget - Custom Viper Widget
Added ViperPad - Custom Viper App Pad (Based of the Palm's SwipePad App)
Removed A Few Scripts Causing Issues
Returned The Artificial Intelligence Sounds
Added TTS Back Into The ROM
Google Nav Works Again
New Boot Animation
Governor Killer Baked In
AOSP Lockscreen Added
Added New App Icons
Moved Data/Tweaks To System/Bin/Tweaks
Optimized More For Speed & Battery
Changed Browser Start Page - Team Vipers Official Site
Added Wallpaper, Wifi Tether, And Launcher Pro To SDCard (VIPERaddons)
Modified Hosts File
Modified Build.prop
Modified Android.policy.jar
Modified MMS.apk
Themed Dialer
Modified SettingsProvider.apk To Always Allow 3rd Party Apps Install
Added ViperComm Widget
Modified A Lot Of Images
New Sounds
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
New Theme
New Shutdown Animation
New Transition Animations
Removed Some Scripts
Added Data/Tweaks
Governor Killer Baked In
Added A Few New Scripts
Modified For Speed
Modified For Battery Life
New Boot Animation
Custom Sounds - By Team Viper
--------------------------------------------------------------------------------------------------------------
..::ROM Downloads::..
ViperROM [TRiNiTY v2.0] EXT4-RFS Dual DK28 4.0.4
ViperROM [FRoZeN] EXT4-RFS DK28 Dual 4.0.3
--------------------------------------------------------------------------------------------------------------
..::Videos::..
ViperROM 4.0.4 Benchmark Scores
ViperROM 4.0.4 Features
--------------------------------------------------------------------------------------------------------------
..::Screenshots::..
COMING SOON!
SDCARD Partitioning Tutorial.
I know that with EXT4, partitioning the sdcard can be a hassle. Here's a little workaround to help you get it partitioned the easiest way I know without having to mount systems and such in Terminal Emulator. This way makes you flash 2 seperate recoveries, but I would rather do this than the other methods which could take upwards of a half hour or even longer. I've seen people that were working on it for a couple hours. Without further adieu:
NOTE: If you are running RFS, just follow step 1. and you'll be done. If you are running EXT4, skip right to step 2. and follow from there.
1. If you are running RFS, then you do not need to follow any other steps. In the green CWM2.5.5 recovery, just go to "advanced" in recovery and choose the Partition option. It's going to give you two questions for sizes that you want. The first size is going to be the ext size. For this it will give you a few options, but I don't recommend choosing anything below 512. You will see all the options when they pop up, just choose what you feel most comfortable with. The next thing it's going to tell you to select is the swap size. I again don't recommend choosing anything below 128 for this option. You will again see a list of options, so choose what you feel most comfortable with.
2. If you are running EXT4, then follow these steps and you'll be up and running with your new partition very soon. First thing you need to do is gather all the tools you're going to need. Here are the list of tools you will need:
A. One Click Root & Recovery 2.5.5
B. One Click Root & Recovery 3.0.0.6
Quite the long list huh? lol ...I told you it's gonna be simple lol.
Download both of these files (if you don't have one or the other already) and extract them to an easy to find location on your computer somewhere.
3. Ok, you're going to do this just the same as you would if you were rooting your phone from a stock state. And to answer your question that's running through your head right now, No, this will not return you to RFS. You will still be on EXT4 the entire time, so there's not real need to backup your sdcard or worry about having to sit through the backup&restore again. Once again, to be very clear... Even though you are flashing cwm2.5.5 recovery, you will REMAIN EXT4. So let's continue. Make sure USB Debugging is on and plug your phone into your computer. Do NOT mount the sdcard, just have the phone plugged in. Open the One Click Root & Recovery 2.5.5, and run the program. When it's finished, your phone will reboot. Do NOT unplug it until the script is complete. The script will say "Operation Complete. Hit any button to continue" or something along those lines. Just hit a button and the script will automatically close. You can now reboot into recovery and you will see the 2.5.5 recovery with the green letters. If you don't have the green letters, then you didn't run the right One Click, and you should start over using the correct one lol . For those that successfully flashed the 2.5.5 recovery, move on to step 4.
4. If you have the green letters, then we'll continue, if not, repeat step 3. with the correct one click lol. Now that you have the green letters, revert to step 1. When you're finished following the same instructions from step 1, move on to step 5. If you have any issues with anything from step 1. (which you shouldn't, but if you do) click here to go to Mibbit's irc chat website. Along the top left side you will see 2 tabs labeled "Home" and "Connect". Make sure you are on the tab that says "Home". When on the tab labeled "Home", you will see the box in the middle of the page. Right beside the letters "IRC:" is a dropdown box. You're going to click on the dropdown arrow and select "EFNET". Next, you're going to enter your nickname, and finally, beside "channel:" type "#viper" and select "Go". That will bring you to Team Vipers chat where one of us will be able to help you.
5. Now that you are partitioned, it's time to restore the EXT4 recovery. If you do not restore the EXT4 recovery, you will not be able to flash any new ROM's or Kernels, so you MUST restore the correct recovery. To do so, you simply do the same steps. Make sure USB Debugging is turned on and plug your phone in. You do NOT need to mount. Now you simply run the 3.0.0.6 One Click Root & Recovery. Let it run through it's process and it will reboot itself. Do NOT exit out of the command prompt until it says "finished, press any key to continue". Once your phone reboots, you can then reboot into recovery and you will see that you have the orange letters again. When you see the orange letters, you now have a partitioned sdcard and you are back on the correct recovery.
**ONCE THE KERNEL IS RELEASED (Which should be within the next 24 hours as long as my testers don't see any issues) THEN MOVE ON TO STEP 6.**
6. Now that you're partitioned, the only thing left to do is flash the kernel. Connect your phone to your computer and copy the Kernel to your sdcard if you have not done so already. To flash it, just choose "Install zip from sdcard" followed by "Choose zip from sdcard" and simply navigate to where you stored it on your sdcard. That's all. It's quite quick and painless and you should be able to do it all within 10-15 minutes.
VIPERrom Store where everything is FREE!
**Cleaned up post 13 January**
**If you want mods and addons download viperstore from the market**
NOTE: stuff is still being ported to the new edify scripting required for clockworkmod 3.0.0.5 so if something doesn't work submit a ticket from our website and we will get it ported over as soon as we can. For now you can access the store's contents that have been converted here.
VIPERchat in your browser chat.efnet.org (enter your nickname and #viper for the channel name)
VIPERchat Downloadable Version VIPERchat.zip (3.38 MB)
Voice Apps were removed in 3.0.3 to save space but if you want them Voice Apps **UPDATED FOR NEW CLOCKWORK**
Stock Sprint Apps (install .apk like normal):
SprintDK28_Navigation.apk (5.6 MB)
SprintDK28_Nascar(updated).apk (385 KB)
SprintDK28_NFLMobile(updated).apk (510 KB)
SprintDK28_SprintTV.apk (879 KB)
SprintDK28_SprintTVWidget.apk (84 KB)
SprintDK28_SprintZone.apk (367 KB)
First to post on this thread besides u
But yea ill look into the link for you right now
if i find it ill give to u
Edit: Here is the link http://forum.xda-developers.com/showthread.php?t=724171
not sure if that will help will look for some more
Reserved.. always wanted to say that.
Nice and clean separate thread me like...
Do i sense a 3.0.1 update to be sweet! or is the current 3.0 this version?
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work! And one quick question. When I try to install lagfix, everythiing works besides the last step, installing viperspeed. It says I cant install it because I dont have enough room. but I have 185MB free. any ideas?
Link? I hope it's not there or else I'll feel more jerky than usual. Oh and super-thanks for those file names on the battery mods, so important... I have a mess of files like GREENBATMODTHISTHAT with no versions or anything and I guess I didn't realize that I needed to keep mods organized by ROM.
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
azichek said:
Hi BT. Thanks for the great ROM. I am using 3.0 right now. What is the difference between 3.0 and 3.0.1? Thanks. Keep up the great work!
Click to expand...
Click to collapse
I think 3.0.1 is just the updated version of 3.0.
3.0.1 does have the aosp lock screen the 4g is fixed
and couple other things... At least that i think lol
Hope that helps
Added A2SD (Download Terminal Emulator, And type "start a2sd" followed by "launch a2sd" and it will back everything up on your sdcard)
Click to expand...
Click to collapse
Can you please clarify this for me, because I tried earlier and it gave an error when trying to install the terminal. Also I have used linux before but never used a terminal on a phone before lol...can you write down a few steps for us newbies
Again Thank you for your work and to your team
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
hemi dart said:
Hey BT I just want to thank you for all your hard work and your great rom. I hope this hasn't been answered but is it necessary to remove my original root before flashing any of your roms? I have flashed most all of them and I have not deleted it. I'm not having any problems with 3.0. Thank you....
Click to expand...
Click to collapse
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
DAVenom said:
Hey BT there is a app called WidgerLocker Lockscreen which lets you put any widget/app i believe on you lock screen that might be helpful i think..
Just installed it and brought back the aosp lock screen might wanna check it out... Send me a pm of ur email so i can send u the apk cause its a paid app
Click to expand...
Click to collapse
Widget locker is good, I installed it and then moved it to system apps. Works perfectly
Sent from my frozen epic4g
neuton said:
Another quick question BT, what are the other options for in the lagfix? Are they for future upgrades or not necessary at all?
Click to expand...
Click to collapse
2.2 is for the vibrant, minfree is setting the phones task killer settings (I recommend doing this), restoring the boot animation gives you a new boot animation, you can set a schedule if you want, and of course all the uninstall options
Sent from my VIPERrom [TRiNiTY] DK28 3.0
BThomas22x said:
3.0.1 is just a new name for it so if we make updates there's less confusion... It's still the same as 3.0, but hopefully this will eliminate some questions in the thread lol.
3.0.1 = 3.0 ...No new updates yet.
BUT!!!
Rodderik did make the battery mods!, check them out!
Click to expand...
Click to collapse
Haha thanks for clearing that up. I also sent you a pm about a weird lag fix problem i'm having. Thanks BT. The ROM is great.
Rodderik said:
nope you don't have to...just wipe 3x, wipe cache 2x, and wipe dalvik cache ONCE and flash the rom then you are good to go (assuming you are using the correct modem and if not then flash it first with odin)
Click to expand...
Click to collapse
I have the correct modem and 3.0 is working great. I have tried most of the other roms and yours have been the best by far. I thank you guys for that.
When I restore data from cockwork it broke lagfix. Anywork around?
Sent from my SPH-D700 using XDA App
Bt, awsome work, wish I had you for a neighbor. Question, scince going to 3.0 my usb tether stopped working, is it not supported in 3.0 ?
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 ?
Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.
Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release
YEZZZ
glad to finally see this here!
jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!
This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.
da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops
jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?
Woo hoo good job bud
Sent from my LG-P999 using xda premium
x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!
da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them
jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...
First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?
da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
hands down, a badass app...
SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!
da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.3.2.3:
-Fixes / enhancements to handle the multiple user setup introduced by Android 4.2 (see notes)
-Fixed a bug with deleting a backup with a space in the name
-Added highlights on keyboard key presses
-TF101: Ignore blkid when mounting /data
CHANGELOG for 2.3.0.0:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please acquire a recovery.log - you can do this in two ways - the fastest is "adb pull /tmp/recovery.log" right after you have the issue. Alternatively in the advanced menu there's an option to copy the log to the sdcard. Also consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
We also now back up and restore boot! Yay!
Want to compile yourself?
I'm using this config: https://github.com/ViViDboarder/android_device_asus_tf101
And this kernel: https://github.com/ViViDboarder/android_kernel_TF101
And compiling against CM9 source tree
Further device specific announcements will go here
A few thanks for this specific build:
Roach2010 for helping be me test and find the mystery kernel
RaymanFX for finding a config that worked. Still not sure where he found it yet exactly
And... Dees_Troy and eyeballer for their relentless nagging
first ...
well second lol
So, third ......thanks guys, that's awesome !
thanks, been waiting for this.
great work, i've been waiting forever and finally have this on all my devices and those that I support.
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
gdeeble said:
I've been using the other one RaymanFX had built and both are awesome. Only 1 change other than the known issues, would be remove the "Bootloader" button under restart. But just my opinion. Thanks Again.
Click to expand...
Click to collapse
Good note. That's a theme issue then. I can build a new theme zip or something later. Working on releasing the much delayed Nexus One build.
EDIT: I've been informed by Dees_Troy that we have build flags to do just this. So I'm adding them to my configs so the next build should have them removified.
It's worth pointing out that this build of TWRP has a recompiled kernel with boot and recovery exposed. You can finally back up boot and restore it.
GooManager keeps hanging at Looking for recoveries after trying to install OpenRecoveryScript. Unable to retrieve files...
Finally recovery on a touch screen device the way it should be! Thanks guys!
Sent from my SGH-I747 using Tapatalk 2
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
MassStash said:
Strange. But I copped the blob from twrp site as "not recommended" suposedly. Ran the command in terminal cuz I don't Fux with goo manager... Everything worked fine. No issues
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.
Click to expand...
Click to collapse
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
sidneyk said:
Since it's installed now and it wiped my data without asking, I'm going to clear things out and reflash everything. I will test if it tries to wipe my data again after I reinstall a few apps.
Click to expand...
Click to collapse
Weird. It didn't wipe my data. Just installed nicely as per instructions.
running great with no issues I used goo manager app but i flashed it through the flash roms selection on the main menu not the 3-dot menu install open recovery script selection.
sidneyk said:
I thought I would give this a try and went to the TWRP page link as instructed. Followed the instructions to download the open recovery through goo manager, which it did and it rebooted my tablet and all looked good. I then tried to reboot to recovery from Team EOS3 Power menu. The usual TWRP blue curtain was there and when it raised, I saw the text at the bottom that my /data partition was being formatted without formatting /data/media and the tablet rebooted, without ever getting to the TWRP recovery menu and I'm now back at the initial Google setup screen. Guess I should have made a fresh Titanium backup first. A warning would have been nice, or is this a bug?
Click to expand...
Click to collapse
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
ViViDboarder said:
Did you ever try to use goo manager with the old unofficial version?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No, I was using RaymanFX's TWRP build prior to this and before that Team Rogue Touch and before that Roach's CWM build, all flashed from within recovery. I only did the GooManager thing because that was the recommended method. Subsequent boots to recovery did not reproduce the data wipe and after reflashing my ROM and restoring my apps, I went into recovery without a hitch. It was only after installing this one through GooManager per the instructions. It downloaded, rebooted and flashed and rebooted back to Android (Team EOS3 JB #57). After a few minutes I rebooted to recovery from the Power menu in EOS3 and as soon as the blue curtain raised it was wiping my data partition - /data/media. Of course, I didn't expect that and didn't get any chance to stop it. I know I read somewhere before that open recovery wasn't working on the TF101, but since this was new and it was recommended to use open recovery, I just assumed that meant it was now working. Oh well, all is well now.
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
cbrox said:
never mind i figured it out, open recovery only works with internal for now.(it may be because TWRP-2.2.1.4 is mounting the micro SD as /sdc instead of /storage/sdcard0) I moved the goomanager folder to /data/media updated the download folder location in the goomanager app settings to /data/media/goomanager re-ran flash roms from the goomanager apps made my selections and order to flash and selected wipe Cache and Dalvik and it ran just fine, it rebooted to recovery, flashed all the zips(including my mods) in the proper order and booted back up with no issues.
Running EOS3-N58 at this time.
Dam sweet once i figured it out!
Great job!
Thanks
Click to expand...
Click to collapse
I had already flashed EOS3-N58, but had changed some files experimenting with getting Polaris Office to work and gave up. So, I followed your suggestion and moved a few other files that I normally flash along with the ROM and it worked like a charm. Pretty nifty. I setup the order to flash for EOS3-N58, gapps, Guevor kernel, nVidia codecs, iobusy, and DSP Manager along with the preliminary cache and Dalvik cache wipes and it just worked like you say. Thanks. I hadn't tried that feature yet, mostly because until now I thought it might break something since I had read that open scripting wasn't working yet for TF101 somewhere. I can say now, with this recovery and your change to the download folder, that it is working and working well. You just have to have whatever files you want to flash in that folder (or maybe just somewhere in /data/media) and you're good to go.