Database Users

[ROM]Plain_JaneT2 V2.0 7/18/10 Stock With everything ROOT!!

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
This rom is a version of Jcase's PlainJane that can be found Here.
I Just added to this rom the latest a2sd that can be found HERE
This rom uses Zanfurs OC path which can be found Here
Scripts from Bugless Beast Here
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*
Downloads at the end of this post.
Reviewed By andrew8806 at http://droid-roms.net
This is the 2.1 Eris OTA(JULY) With Root, A2SD, and Overclocking.
This is for people that like the SENSE UI, and have lots of apps.
I was using PLAINJANE and filled up the internal Memory, so I went about looking for a way to keep the rom and have all my apps.
Presenting PlainJaneT2 V2.0 Screenies attached New Fonts!
Change Log:
Code:
[B][U]PlainJaneT2 v1.0[/B][/U]-Added A2sd to Original PlainJane from Jcase.
[U][B]PlainJaneT2 v1.1-1.4[/B][/U]-Various Deodexed Versions of
the Rom that never were made public.
[U][B]PlaingJaneT2 v2.0[/B][/U]
-Based on JULY OTA
- Fully Deodexed without any FC (This was a Killer to figure out...)
- Added the Newest A2sd Preview 4
-Added Scripts to rom to enable ext mounting on linux
systems, get cpu Info, make system folder rw, and the ability to
zipalign all apks.
-Added Modified boot screen.
-Changed Default Fonts.
-Made it all stock (some People were asking to leave the apps untouched.
^^(I made a flash zip you can you use to get rid of the all BloatWaredelete)
Remember to BACKUP your sdcard before doing the step below!!!.
Things you need to know and do.
How to set up your sd card for a2sd:
Code:
1. Boot into recovery
2. Scroll down to PARTITION SDCARD
3.Click On PARTITION SD
4.Click trackball to confirm
5.Select Swap size 32mb is fine
6.Select ext size (I did 768mb you don't have to make it that big)
7.Click again to partition sd card.
8.Go to PARTITION SD menu and choose SD:ext2 to ext3
This New A2sd Makes it so when you go to the data/app folder, it actually takes you to the /system/sd/app folder. So when you use Root Explorer to look at the data/app folder you are actually looking at the /system/sd/app folder.
You know you are in the /system/sd/app folder in root Explorer because at the very top it says something like this "92.88MB used 593.51MB free" as we all know the Eris doesn't have that much space in the data/app folder. The space in the data/app folder might still be going down because the cache isn't moved to the sd card by default, if you want to change this you can change it yourself.
For a2sd help:
Code:
adb shell
su
a2sd help
Use of scripts:
Code:
Go into terminal emulator or adb and run these scripts
-"sys -rw" Will Make system Read and Write
-"sys -ro "Will Make system Read Only"
-"usb -e" Will mount Sdcards Partitions" On linux
systems will mount the EXT partition. Sorry windows people.
"usb -d" Will unmount the sdcard Partitions..
-"cpuinfo" Will give you the OverClock settings,
giving you the max, min, and what you have it set to.
-"zipalign_apks" Does just that zipalign all apks.
To change the over clocking settings Download Setcpu from this thread Here
Remember to Wipe Factory/cache Before flashing this rom.
Downloads:
PlainJaneT2 V2.0
PlainJaneT2 V2.0
- Flash this to get Default Fonts to original
DefaultFont.zip
-Flash this to get rid OF BloatWare
BloatWareDelete.zip
-Flash this to Disable the OTA that some people are getting
DisableUpdate.zip
Alternate Links
T2noob Roms
BloatWareDelete.zip Deletes
-AmazonMp3
-Stocks (widgets and app)
-Twitter (Widgets and app)
-HtcFootPrints (Widgets and app)
-Teeter
-Visual Voice Mail
-PDF VIEWER(the adobe one is better than this one, get it on the market)
I hope this helps someone, I Had a hard time getting a2sd to work because there isn't that much documentation on how to enable the boot.img for a2sd, now people don't have to go through what i did to get a2sd on 2.1 stock rom.And Jcase Gave me his ok.(In case you were wondering)

your freakin kidding me!
this is what ive been working on...well mine has a little tiny bit more but still...haha im actually like halfway through the upload
Code:
[SIZE="7"]Smash_Rom_0.8.1[/SIZE]
[B]Ill be releasing another AOSP non-Cyanogen Rom similar to this within a week or so.
[/B]
This is a rom for all those people who want to stick close to stock, but want all the perks of rooting.
This has been a while in coming, the Linux Kitchen is actually the child of this project :P
[SIZE="5"]Features[/SIZE]
-Plain Jane Based (Jcase)
-Overclock to 864Mhz (Zanfurs Kernel)
-Apps2SD (Tkirton)
-Espresso Rosie
-Wifi Tether
-Completly De-odexed (Andrizoid's Linux Kitchen ;))
-Metamorph Themes Work!
-Spare Parts Included
-HTC_IME from XDA with Voice to Text!
-
[SIZE="5"]Notes[/SIZE]
[SIZE="4"]General[/SIZE]
This rom is heavy, just over 100MB. You have to realize though that this is not an AOSP or even SLIGHTLY Vanilla rom, its completly stock based.
The fact that its Sense based is also going to have some effect on battery life. Don't expect to come from White Widow and see the same kind of battery life.
This rom also takes a HELL of a long time on first boot. Thats because of the de-odexed files.
[SIZE="4"]Installation[/SIZE]
Wipe data/dalvik and flash like normal from recovery.
If you experience FC's on the first boot, you may need to wipe your SD-ext. This can be done from the Recovery Menu under the "wipe" sub-section.
[SIZE="4"]Partition-ing [/SIZE]
-Make a backup of everything on your SD card.
-From the recovery menu choose Partition sdcard.
-Choose Partition SD
-Select the defaults for all the sizes.
-Choose SD:ext2 to ext3
-Copy back all of your files.
[SIZE="5"]Bugs[/SIZE]
-None...This rom just works.
[SIZE="5"]Thanks[/SIZE]
-Tkirton for his Apps2SD and for being in general an awesome guy.
-Jcase for his Plain Jane Base.
-Zanfur for his kernel.
[SIZE="5"]Screenshots[/SIZE]!
[SIZE="4"]Remember this is Stock based so theres not going to be many graphical tweaks other than the Espresso Launcher[/SIZE]

Andrizoid said:
your freakin kidding me!
this is what ive been working on...well mine has a little tiny bit more but still...haha im actually like halfway through the upload
Code:
[SIZE="7"]Smash_Rom_0.8.1[/SIZE]
[B]Ill be releasing another AOSP non-Cyanogen Rom similar to this within a week or so.
[/B]
This is a rom for all those people who want to stick close to stock, but want all the perks of rooting.
This has been a while in coming, the Linux Kitchen is actually the child of this project :P
[SIZE="5"]Features[/SIZE]
-Plain Jane Based (Jcase)
-Overclock to 864Mhz (Zanfurs Kernel)
-Apps2SD (Tkirton)
-Espresso Rosie
-Wifi Tether
-Completly De-odexed (Andrizoid's Linux Kitchen ;))
-Metamorph Themes Work!
-Spare Parts Included
-HTC_IME from XDA with Voice to Text!
-
[SIZE="5"]Notes[/SIZE]
[SIZE="4"]General[/SIZE]
This rom is heavy, just over 100MB. You have to realize though that this is not an AOSP or even SLIGHTLY Vanilla rom, its completly stock based.
The fact that its Sense based is also going to have some effect on battery life. Don't expect to come from White Widow and see the same kind of battery life.
This rom also takes a HELL of a long time on first boot. Thats because of the de-odexed files.
[SIZE="4"]Installation[/SIZE]
Wipe data/dalvik and flash like normal from recovery.
If you experience FC's on the first boot, you may need to wipe your SD-ext. This can be done from the Recovery Menu under the "wipe" sub-section.
[SIZE="4"]Partition-ing [/SIZE]
-Make a backup of everything on your SD card.
-From the recovery menu choose Partition sdcard.
-Choose Partition SD
-Select the defaults for all the sizes.
-Choose SD:ext2 to ext3
-Copy back all of your files.
[SIZE="5"]Bugs[/SIZE]
-None...This rom just works.
[SIZE="5"]Thanks[/SIZE]
-Tkirton for his Apps2SD and for being in general an awesome guy.
-Jcase for his Plain Jane Base.
-Zanfur for his kernel.
[SIZE="5"]Screenshots[/SIZE]!
[SIZE="4"]Remember this is Stock based so theres not going to be many graphical tweaks other than the Espresso Launcher[/SIZE]
Click to expand...
Click to collapse
mine is simple though, its just for people that like the simplicity of Plain Jane but filled their internal memory.
I Really wasn't trying to step on anyone toes, my bad.
This is so people have to waste their time, like me, getting a2sd to work on plain jane like i did.

t2noob said:
mine is simple though, its just for people that like the simplicity of Plain Jane but filled their internal memory.
I Really wasn't trying to step on anyone toes, my bad.
This is so people have to waste their time, like me, getting a2sd to work on plain jane like i did.
Click to expand...
Click to collapse
oh your not stepping on toes.
if anyones stepping on toes here its me releasing smash right after this.
i was kinda worried to release mine-i actually PM'ed you hoping we could work something out without either one of us getting pissed at the other
if you have no problem with it though ill release it once the upload finishes.
haha i just think its ironic that i kept this a secret and you were working on the same thing-i was in no way accusing you of stealing or any of that BS.
best of luck to you, feel free to hit me up anytime. id be glad to help you out with this or any other project you plan on starting.

so what are the perks of an espresso (sp?) rosie?

@Andrizoid Release Away my friend I don't mind.

Erisftw said:
so what are the perks of an espresso (sp?) rosie?
Click to expand...
Click to collapse
graphics.
just an FYI though...dont ask about why my rom is/isnt better in his thread. ill have mine up soon enough

Andrizoid said:
graphics.
just an FYI though...dont ask about why my rom is/isnt better in his thread. ill have mine up soon enough
Click to expand...
Click to collapse
Sorry to hijack your thread t2. Will probably flash this rom later.
Sent from my Eris using XDA App

t2nob!!!! This is just what I have been waiting for!! Thanks soooo much man!!! You rock!

Nice work t2noob!
Sent from my Eris using XDA App

t2noob,
Glad you picked this up. lmk if you need anything.
jcase

I tried flashing this rom and I boot looped. I wiped the phone like always after doing a nan back up.
Sent from my Eris using XDA App

KillaLude said:
I tried flashing this rom and I boot looped. I wiped the phone like always after doing a nan back up.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Mmm send me a pm and I'll try to help you out. Did you partition your sd card? That's the only thing I can think that will cause a boot loop.
Sent from my Eris using XDA App

Good release ....forgot how smooth Sense can be

Quick question about a2sd: Say you flash to another ROM that also uses a2sd. Do you have to delete any app data on the sd or does the new ROM overwrite it, or neither? LOL. Thanks for this ROM! just flashed and will let you know if there are any issues.

One random reboot. Used my phone for a sec, set it down, looked over and heard the vibrate and it was rebooting.
Sent from my Eris using XDA App

semmtexx said:
One random reboot. Used my phone for a sec, set it down, looked over and heard the vibrate and it was rebooting.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I have been using this rom for a while now and havent had reboots, If you didn't wipe the EXT partition its probably what caused it because most rom's are using the old version of a2sd and not the new one and it might be causing reboots.
If it reboots again let me know so i can see what's causing it.

Had another reboot. Before I flashed, I setup my storage card exactly as your instructions said. Only thing is, how do you know if the apps are being installed on the sd? If I go to data/ there is no app folder but there is in sd/data. Also I read on the darktremor thread about davlik cache decreasing and that can also be moved to storage card. Not sure how to do that though. I know it's not your ROM. Maybe I should try completely wiping and partitioning the card again?
edit: Removed sd card from device and installed apps lose icons and FC. So I guess they are installed to sd. Only thing is the phone rebooted when I reinserted the sd card. Suggestions? Thanks for your help man!!
edit: Oh man it's actually an endless reboot. What to do....
edit: Did a battery pull while it was looping and it booted up fine. No clue whats going on. I'll let you know if it reboots again. Oh man also, after the successful boot, my cd card seems corrupted. In astro, every item is just lines and square with file type "2". I'm going to wipe, repartition and try again.... wish me luck!!

semmtexx said:
Had another reboot. Before I flashed, I setup my storage card exactly as your instructions said. Only thing is, how do you know if the apps are being installed on the sd? If I go to data/ there is no app folder but there is in sd/data. Also I read on the darktremor thread about davlik cache decreasing and that can also be moved to storage card. Not sure how to do that though. I know it's not your ROM. Maybe I should try completely wiping and partitioning the card again?
edit: Removed sd card from device and installed apps lose icons and FC. So I guess they are installed to sd. Only thing is the phone rebooted when I reinserted the sd card. Suggestions? Thanks for your help man!!
edit: Oh man it's actually an endless reboot. What to do....
edit: Did a battery pull while it was looping and it booted up fine. No clue whats going on. I'll let you know if it reboots again. Oh man also, after the successful boot, my cd card seems corrupted. In astro, every item is just lines and square with file type "2". I'm going to wipe, repartition and try again.... wish me luck!!
Click to expand...
Click to collapse
Yeah its bad to pull sdcard while the phone is on because thats where all your apps are installed on, if you pull card your phone will look for the apps but wont find them thus causing the fc's
I would do a clean flash and wipe because it sounds like you messed up your sdcard when you pulled it. I've been running this rom for about a week and haven't had a reboot or anything like that.
Make sure you backup your sdcard if you don't want to loose any of your pictures and stuff.
EDIT: make sure you do a ext wipe also.

t2noob said:
Yeah its bad to pull sdcard while the phone is on because thats where all your apps are installed on, if you pull card your phone will look for the apps but wont find them thus causing the fc's
I would do a clean flash and wipe because it sounds like you messed up your sdcard when you pulled it. I've been running this rom for about a week and haven't had a reboot or anything like that.
Make sure you backup your sdcard if you don't want to loose any of your pictures and stuff.
EDIT: make sure you do a ext wipe also.
Click to expand...
Click to collapse
Hey t2noob! Well I think I have it this time. I was worried that somehow my sd card was trashed. I was trying to wipe the ext and recovery was giving me an error saying that it was unable to wipe. I had to wipe it using ADB. I completely wiped like 3 times, repartitioned, flashed, and everything seems to be ok. I'm thinking my sd card is possibly on it's way out. Also, I'm hesitant to try putting the Davlik cache on the card. I'll check back in tomorrow if there are any issues. Everything else seems fine though. Do you know of anyway to check and see if there is an issue with the sd card or do they just crap out when their time is up?

[Kernel] Voodoo (lagfix_3.0) + Backlight notification for Captivate. It works!

THIS IS FOR CAPTIVATE ONLY
I am not responsible for any damage caused to your device
BACKUP BACKUP BACKUP with Nandroid and Titanium Backup before installing this.​
What this is:
Voodoo lagfix beta 4 from supercurio
Backlight notification patches from neldar
Vanilla Captivate kernel built from Samsung sources.​
What this is *not*:
Unhelpful OC/UV kernel. I did start from his github repository, and cherry picked the changes I wanted while leaving the OC/UV out for now.
Voodoo color fix.​
How to install
Download captivate-voodoo3.0_bln_v1.10.zip. (You can also install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip if you do not want backlight notification).
Did I say backup first yet? Backup in case something fails and you need to recover!
Rename the downloaded file to update.zip, put it on the root of your built in sd card (not the removable one!), reboot into stock recovery mode, select reinstall packages. The first conversion takes a long time depending on how much data needs to be converted (the white AT&T screen). The phone will tell you as it progresses through the different stages ("please wait", "step 1", "step 2" and if all goes well "conversion successful"). Important: You have to install via recovery using the update.zip if you want the backlights to work because this also needs /system/lib/hw/lights.default.so to be updated for BLN support. Either that, or install the file yourself by pulling it out of the update.zip and putting it in /system/lib/hw, overwriting the stock version. If you do not want backlight notification, install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip instead.
Important
If you have installed v1.2 or below or installed v1.4 or installed v1.5 while I had it up, you need captivate-voodoo-beta4-v1.5a.zip to clean up the sound configuration first. Then install the latest release. You do not need v1.5a if this is the first time you are installing this (or are coming from stock), you just need the latest release.
Nandroid, ClockworkMod
Disable the lagfix as above before using Nandroid, Clockworkmod because they do not understand EXT4 yet and will not backup correctly.
More details on the voodoo lagfix on http://project-voodoo.org/installation as it is basically the same as the Galaxy S (international).
Enjoy!​
HSUPA (optional, bluetooth mic does not work):
Install Captivate Voodoo+BLN+HSUPA kernel+ I9000 JH2 modem: Before you flash this, first install the Captivate Voodoo+BLN kernel above. Then use ROM Manager to flash i897_hsupa_v1.10.zip. This will install a new Captivate Voodoo+BLN+HSUPA kernel that allows us to use the I9000 JH2 modem that enables HSUPA for us. There is no need to disable-lagfix if you already have Voodoo lagfix working, but it is a good idea to make backups in any case. Note: Bluetooth mic does not work with this yet.
Revert back to Captivate Voodoo+BLN+JH7modem:
Use ROM Manager to flash i897-captivate_v1.10-revert.zip. This will flash back to the Captivate Voodoo+BLN kernel without HSUPA and will also flash the Captivate JH7 modem. No need to disable lagfix if you are already running it.​
Uninstall:
Disable lagfix
1. Mount phone on computer (connect it so that you see its two card, one internal, one external if you have one).
2. Navigate to the Voodo folder on the internal SDCARD (there should be only one of the two cards that has this folder)
3. Create a file (or folder) named "disable-lagfix", no extensions. (right click -> new-> new file or folder)
4. Unmount your cards from the computer.
5. Shut phone OFF.
6. Turn back on.
You should hear the "Converting EXT4 back to RFS".
Scary way to get original kernel back
If you really really want to go back to the kernel you had before applying the lagfix kernel (why?), first disable the lagfix as explained above. Then you will need to get into adb shell, with root.
Code:
thor$ adb shell
$ su
# redbend_ua restore bml7-zImage-kernel-backup.img /dev/block/bml7
Be very very careful with this command. If you make a mistake, you can brick you phone for good.
If *I* wanted my original kernel back, I would just disable-lagfix, make a backup and then use Odin One-click to go to stock and then restore from backup. Much less scary and no danger of killing the phone.​
Changelog:
1.10 Added backlight notification. Changed to use stock sbin/init because the previous init might have been the cause of some ppl losing sdcard or usb (might have been!). captivate-voodoo3.0_bln_v1.10.zip captivate-voodoo_lagfix_3.0_v1.10_nobln.zip
1.9 Same as 1.8, but with a different method for handling init.d scripts so it uses the standard busybox run-parts. captivate-voodoo_lagfix_3.0_v1.9.zip
1.8 Make sure /data is mounted noatime, nodiratime - better performance and fewer writes to flash. Was an oversight that these were dropped. captivate-voodoo_lagfix_3.0_v1.8.zip
1.7 Cleaned up /system so nothing is left there after the phone comes up fully. No change in behavior. captivate-voodoo_lagfix_3.0_v1.7.zip
1.6 Clean voodoo installation with stock Captivate kernel (actually the same as v1.3, but to avoid confusion for ppl coming to this from stock). captivate-voodoo-beta4-v1.6.zip
1.5a Bugfix release that cleans up the mess from any previous voodoo installs that disabled sound for you. captivate-voodoo-beta4-v1.5a.zip
1.4 There is no 1.4 anymore. If you installed it, you need 1.5a above.
1.3 Fixed headphones problem (configuration problem for sound in general) captivate-voodoo-beta4-1.3.zip
1.2 Added init.d support to allow things like mobileAP etc to work. Do not use.
1.1 Totally vanilla update.zip - has nothing but lagfix. Do not use.
1.0 Left some pieces from my SRE installation on the update.zip - fixed in 1.1​
Credits:
Francois Simond, supercurio on XDA (Voodoo lagfix)
[email protected] (Backlight notification patch)
[email protected] (kernel help)​
Github repositories:
Voodoo initramfs used to build the kernel initramfs
Linux kernel sources, configs for Captivate to build this release
Toolchain used
Clone the repos, change the CONFIG_INITRAMFS_SOURCE to point to the voodoo initramfs in the i897_defconfig file under arch/arm/configs of the kernel and build with the build_kernel.sh in the top level of the linux kernel directory. The build_kernel.sh has to be edited to change CROSS_COMPILE to point to the toolchain and the AOSP variable has to point to the place where it can find the signing tools under the eclair build from AOSP.​
Donate:
I am a liver transplant survivor and I would not be here if not for the generosity of the person who was thoughtful enough to have signed up to donate his organs before he passed away.
And if you are feeling cash rich, you could also support supercurio for the voodoo lagfix and support neldar for the backlight notification. ​I have tried to keep the kernel as vanilla as I could so that I could isolate the changes to just the ext4 lagfix. I will include more things as I work on this and if I have the time!
I am putting everything on github so others can continue on this if I am lax
-Atin

oooo nice! 10 chars

my sweet jebus yes

Installing now. Lets see what all this talk has been about.
My phone is talking to me!

Great. Another reason to flash. Thanks. )
Sent from my f5 hitter.

GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?

DOAlaboratories said:
GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?
Click to expand...
Click to collapse
you can flash on top. you'll lose some of the things from SRE until I have the two merged fully.

Should I just Odin myself back to stock then do this or will it work over my root, lag fix, etc?

After a really bad experience with SRE and sleeping death, this is much needed. Thanks much

Ah.. so this is where everyone seems to be tonight lol.. going under my USER CP i see the vanilla/SRE/Capti-VibHybrid always refreshed!
Great to hear this I'm excited to see if anyone finds poquito bugs!

I just flashed this on top of SRE running jH7 and my
Phone is talking to me while
It's on the Att white screen! Crazy but it's sexy ahahahA

why not have this simply as a lagfix, and incorporate it into SRE, instead of trying to make yet another all-in-one tool?? It will be nice to just have one tool (SRE), and have the voodoo lagfix incorporated into that instead of the other way around.
Oh and btw, if you do incorporate unhelpfuls oc/uv kernal...PLEASE keep a version with stock clock speeds/voltages. Some of us have no desire for this, and as of now, it seems to be the source of most of the problems.

I have one request. I see that u are planning to incorporate oc/uv in this mod. Can u make a non-oc/uv version as well? My experie ce with it has been nightmarish

Just finished!
Got 1533 quadrant score with all my stuff intact. No fresh install! Loving this so far!
Edit: ran quadrant second time and I got 1785

Hey, looks like someone stole my thread layout... pshhhhh
this is going to be in SRE
the fix, not this...

designgears said:
Hey, looks like someone stole my thread layout... pshhhhh
Click to expand...
Click to collapse
I thought I felt strangely familiar reading the OP.... lol
Can we get a lagfix only update like on the main voodoo page? This one messed up my theme and that's gonna be a deal breaker. lolz jk
EDIT: Ahhhh and removed my overclock!!

wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
ha, and this is the I9000 kernel, its not even for captivate.

designgears said:
wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
Click to expand...
Click to collapse
first the thread layout, and now SRE! You should take this as a compliment, that means you are doing something right!

wow really DG?! dang .. something is very wrong with this IMO. :/ .. is this going to be another cyanogen type drama Dx ..
at least he mentioned your name in credentials..
lol it's written designgears(SRE) .. it's openly written he literally used your code .. X__x.. not as bad as the cyanogen drama.. D: .. >_>..
am i making this too dramatic than it is o_o?

1726 quadrant and no sleeping death yet. Im keeping a copy of this version

Where the hell is voodoo for fascinate. Noob

Here is the OP from the voodoo for fascinate thread in this forum:
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1
jt1134 said:
After you read this WHOLE post, read it again. If you are unsure about something, check the links below. kthx
OK guys, here it is.
For those unfamiliar with Voodoo : http://project-voodoo.org/
This kernel includes ONLY the voodoo lagfix, no color fix ATM.
For FAQs : http://project-voodoo.org/faq
Also now included is the option of using aosp style bootanimations. The attached zips include one. If you want to use your own, then place a compatible bootanimation.zip in either /system/media or /data/local.
http://www.droidforums.net/forum/droid-hacks/33932-bootanimation-zip-file-explained.html
http://www.dkszone.net/how-to-create-custom-boot-animation-for
First off, have PATIENCE PATIENCE PATIENCE!!!!!!
It takes a WHILE on the first boot to do the conversion and copy over your data. If you decide to revert back to stock, it will take a WHILE then to convert back. Don't reboot, let it do its thing.
Once you've flashed this kernel, don't just go flashing other kernels. Voodoo changes some key parts of your system and you will have fix them by hand if you flash another kernel without removing voodoo first. To remove, simply do adb shell "> /sdcard/Voodoo/disable_lagfix" and then reboot. If you want to re-enable voodoo, then remove that file.
If you have less than 220mb of space remaining on internal storage, then clean some stuff out before flashing this. I have also included a 1.2GHz overclocked kernel.
For those who get excited from staring at Quadrant all day: I KNOW YOUR SCORES ARE NOT AS HIGH AS THEY ARE WITH THE EXT2 "LAGFIX". This is to be expected. Voodoo does not mess with /dbdata but only /data. THIS RESULTS IN ABSOLUTELY NO LOSS OF FUNCTIONALITY OR USEABILITY.
If you are running the ext2 "lagfix", please uninstall it before using this. If you have problems, wipe data and try again. Voodoo should retain data, but nothing is foolproof. Be prepared to lose your data! If you have problems with force closes after uninstalling, make sure to wipe using the option in the privacy menu.
Thanks to Dirrk and DataSpree for help getting the kernel in a useable condition, and thanks to SuperCurio for the original lagfix and clues on how to get it working with the Fascinate.
If you would like to look at the code for yourself, please check my github @ github.com/jt1134
Enjoy!
******EDIT******
For anyone who flashed v0.1, I made a stoopid. Sorry. I've attached a fixed version. You will need to uninstall the current voodoo before flashing this. To uninstall simply do : adb shell "> /sdcard/Voodoo/disable_lagfix" . or, create a blank file in your favorite manner. You can also do this with a file explorer program such as Astro or Root Explorer. Then reboot. Once you've booted into android successfully, you can install the attached zip. If voodoo does not reinstall for you, make sure you have deleted /sdcard/Voodoo/disable_lagfix. Repeat: this is only if you are running v0.1!
edit: removed attached kernels. newer versions available on rom manager.
If you enjoy the work I do, you can contribute to my beer fund. Beer helps me think!
Click to expand...
Click to collapse
where the hell do i click to download the files. am i losing my mind or what!!!!!!!!!!!

Gotta read, man.
edit:
I should read edits, too

jt1134 said:
edit: removed attached kernels. newer versions available on rom manager.
Click to expand...
Click to collapse
There are a lot of words there... *shrugs*

CouchSpud said:
There are a lot of words there... *shrugs*
Click to expand...
Click to collapse
does it have to be rom manager premium??????????? i got the free one.
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1

fupamobile said:
does it have to be rom manager premium??????????? i got the free one.
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1
Click to expand...
Click to collapse
you really dont seem like someone capable of handling voodoo atm....there have been plenty of posts on all this stuff for months....use the search button

This is a bad time to flash to voodoo. DJ05 is right around the corner, and removing voodoo has resulted in more "help me" threads than anything else on this forum. That being said...
Who wants to start the bidding? 3:1 says he will have a "HALP ME MY FONE IS RUINED" thread within 2 days of DJ05 release.
Edit: Prediction #2, his plea for help post will include uninterrupted punctuation 10+ symbols long.

Its like you've seen this before or something!
Sent from my SCH-I500 using Tapatalk

[Kernel] - GB's Steam Kernel - OC/UV or Stock. Made from Unicorns and win.

What is a Steam Kernel?
This kernel uses SztupY's Steam Recovery instead of the standard ClockworkMod. Steam is based off of ClockworkMod, so all of the features you're looking for are here.
If it's based on ClockworkMod, then why would I want to install this?
Steam is a successor to the Universal Lagfix Kernel SztupY also made. Steam has a touchscreen interface at recovery, and a number of lagfix options, just like the ULFK, but with some additional options. Steam has options to convert /system to ext4 or jfs on top of the regular lagfix options. So, instead of using the buttons to locate that new ROM or theme or whatever, you just scroll down your screeen. Steam also has some advanced security features, which you can read about in SztupY's posts. One of the coolest things about Steam is that it automagically detects what filesystems you are using and re-writes init on the fly. So, if you're using an ext4 or jfs lagfix, you don't have to disable it before flashing Steam.
As you may have seen, there are two (I think minor) issues. For one, if you do it the way MikeyMike had people do it (use Voodoo to convert --> ext4), when Steam loads it will may mount /system nosuid, and it will seem like you've lost root. You haven't. It seems that either doing a /system conversion resolves this, so switch from /system formatted as ext4 to /system whatever, OR boot to Steam recovery, under 'boot options' select 'adb always on' and 'adb always root' or something like that, boot the phone, fire up adb and type
Code:
mount -o remount,suid /dev/block/stl9 /system
This will allow /system to be mounted with su access (kinda important!).
The other issue is that when you do a filesystem conversion on /dbdata or /data (one or both, I can't remember) after everything is done, you will get boot loops, doing a hard reset (hold down volume up/down/ and power)resolves this.
If you aren't doing filesystem conversions all the time, then this won't bother you much and these kernels are otherwise stable. This isn't a fault of Steam, SztupY designed it for 2.2, and we're using it on 2.2.1, a couple glitches would be anticipated, and these aren't anything that, imo, affect performance or stability.
As always - when doing these kinds of backups, make sure you have plenty of room on your SD card, or more than the total of the sizes of /data, /dbdata, /cache combined.
Finally, Steam NEEDS to be flashed either by Neldar's SGS Kernel Flashing App, or Heimdall (now for PC and OS X I think) or Odin via a tar file. I can't upload .tar files to xda, so I've attached a couple zips. These CANNOT BE FLASHED VIA CLOCKWORKMOD.
I've uploaded two kernels and a initramfs for anyone who wants to make a Steam kernel of their own. The OC/UV kernel is like my other ones, hopefully no issues with charging, voltage and clock speed can be controlled by xan's app, read other kernel thread for more info. The other kernel is basically a 'stock' reoriented kernel with Steam recovery.
Both kernels also have Neldar's 2.3 BacklightNotification Mod.
Some links about Steam
Here, and here.
Credits
Xcaliburinhand
SztupY
raspdeep
neldar
xan

So, if you think you're phone is getting 'charge death' (I prefer 'charger instability'...sounds a lot nicer doesn't it? ) try a couple things. (I don't think this is an issue with the Steam kernel here or with the most recent one from my other kernel thread, but if it is...)
- Get any kernel w/o the oc/uv patch.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- For it to be charge death, it has to occur while charging (I know, but you'd be surprised), it has to happen with a oc/uv kernel, you CANNOT have any setCPU 'screen off' profiles' (it's not just this kernel, screen off doesn't play nice on our phones afaik), and you cannot have any undervolt values set. (Read that closely - I'm not saying you can't UV, just that if it seems like charge death, remove all UV when charging and see if it happens. More below.)
- The reason I ask you to not undervolt at all and see if it happens is because I don't know if every other oc/uv kernel uses the stock factory voltages, so you may have been using UV settings that are referenced from an over-volted kernel, and so you might confuse freeze with charger instability.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.

Thanks for posting this and for all your help in the other threads.
Sent from my liberated Captivate via XDA App.

Ok I am using the steam recovery in serendipity and you say doing it that way makes you seem like you have lost root. I haven't had any issues with my apps on my phone that require root but steam gives me a status 2 error when trying to flash themes...would doing a system conversion fix that or is that a totally different problem?
Sent from my SAMSUNG-SGH-I897 using XDA App

Anything different from the attached kernel in this thread and the one in Mikey's rom?

That could be it because you're probably trying to write to system with the update.zip. Check by running an adb shell (or fire up the terminal emulator app) and just type 'mount'. If you see something like
Code:
/dev/block/stl9 on /system type rfs (rw,[B]nosuid[/B],nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
then yeah. Or like I said, use adb, but you might have to do that after every boot. Fileysystem conversion seems to be good.
Steam re-writes init on the fly, so if it's not doing the conversions at first, it apparently defaults to nosuid.

bts0uth said:
Anything different from the attached kernel in this thread and the one in Mikey's rom?
Click to expand...
Click to collapse
Ah well just updated to BLN 2.3, and added the no oc/uv one for people who don't want that.

This is what mine says when typing mount in terminal emulator...right or wrong?
/dev/block/stl9 on /system type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)

Could we flash the no oc/uv over the stock kernel in serendipity without disabling voodoo?
Sent from my SAMSUNG-SGH-I897 using XDA App

Gurgs said:
This is what mine says when typing mount in terminal emulator...right or wrong?
/dev/block/stl9 on /system type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
Click to expand...
Click to collapse
If you don't see nosuid, don't worry about it. I had had Steam recovery on my phone all last week but I went from RFS --> jfs as soon as I flashed so I had no idea this was an issue before it was released. MikeyMike had the idea of putting on the ROM and people could try it out, which I thought was pretty good, and still is. Just wasn't quite as easy as we thought.

crupp said:
Could we flash the no oc/uv over the stock kernel in serendipity without disabling voodoo?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes. BUT, since you aren't doing a /system conversion, what I wrote in the OP will probably apply to you.

Any progress on Voltage Control sticking?

MikeyMike01 said:
Any progress on Voltage Control sticking?
Click to expand...
Click to collapse
Any progress on making a ROM that doesn't have nine version in 48 hours?

glitterballs said:
Any progress on making a ROM that doesn't have nine version in 48 hours?
Click to expand...
Click to collapse
At least I fix what's wrong.

What is steam? This isnt a kernel we can simply flash with Odin?

MikeyMike01 said:
At least I fix what's wrong.
Click to expand...
Click to collapse
I'm flashing 1.9 now so we'll see about that.

psufan5 said:
What is steam? This isnt a kernel we can simply flash with Odin?
Click to expand...
Click to collapse
Steam is similar to cwm. It uses a pretty cool touch screen interface. Try sgs kernel flasher, its really easy to use. Don't forget to make a backup first.
Sent from my liberated Captivate via XDA App.

glitterballs said:
Any progress on making a ROM that doesn't have nine version in 48 hours?
Click to expand...
Click to collapse
You can, you just have to make a .tar of the zImage. You can't u/l .tar to XDA for whatever reason, so just posted zips.

MikeyMike01 said:
Any progress on Voltage Control sticking?
Click to expand...
Click to collapse
My voltages have been sticking since I downloaded your rom...i must of just got lucky or something...

Gurgs said:
My voltages have been sticking since I downloaded your rom...i must of just got lucky or something...
Click to expand...
Click to collapse
It sticks with the normal kernel, but not the steam one.

LolBoot xD SGS2 dualboot - NEW 12.12.11: Easy-Setup App v2.51

(I wasn't really sure if this might fit into "Development", so I put it here, maybe a mod will move it, if it's a dev topic )
Anyways, here we go, I DUALBOOTED two different, independant ROMs on the S2
Video of dualboot in action: http://www.youtube.com/watch?v=l9-V_6Ua_D0
** THIS IS NOT (YET) COMPATIBLE **
** WITH ICS (ANDROID 4.0.x) ROMS! **
-- this goes for custom ROMs as well as stock ROMs --
Icey Sammich compatibility will be added once Sammy released their ICS kernel sources.​
!!! There now is an app for more convinient and easy setup of the dualboot !!!
(04.11.2011) DualBoot setup app v2.00: http://forum.xda-developers.com/showpost.php?p=19049047&postcount=94
(12.12.2011) App has been updated to 2.51, lot's of good new stuff! >> Free Version -- Donate Version <<
Click to expand...
Click to collapse
First off:
This is only a little experiment I did like "c'mon, has to be possible" - this is NOT (at least yet) tweaked for usability and anything the like, just a humble experiment.
That said, don't flame me if things are rather complexicated to do this ATM.
Maybe I'll come up with a more userfriendly way of setting this up, maybe someone else does, maybe no one does.
Also now that I found a base on what to do, there might be different ways (more easy ones maybe) to set this up, I'll keep toying around with it.
But let's cut to the chase, shall we
So, how was this set up? I'll give a brief rundown of what I did:
I edited a few .rc files in the initramfs of the kernel to make it actually perform a full boot when recovery mode was triggered and to fire up recovery mode when in battery-charging mode.
I also edited a few mounts in the boot .rc for the 2nd OS (in "recovery" mode) to use different partitions for /system and /data, so that we'd end up with really independant installs.
What partitions did I missuse for that:
partition 12 (mostly unused, only when installing a stock ROM AFAIK) for /system - that's a neat choice IMO as p12 is 512MB in size, just as p9 where /system usually sits on
partition 7 (which is usually /cache) for /data
gives us only 100MB of user data space, but for now that's OK, as said, it's only an experiment on how such a thing could be done.
with the original partition for /cache "gone", I mounted a tmpfs for it.
So the OS still has a usable /cache
Then I set up the two OSes:
(dualboot kernel not yet flashed)
Launchprep part 1:
I made a CWM backup of my normal installation I was running (stock XXKG6 at the time).
I installed DevNull-Test AOSP as to it's instructions
Some su'ed voodoo via a terminal while having the 2nd OS (the DevNull AOSP one, in this case) installed - best done in recovery mode via ADB:
rm -Rf /cache/*
cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
That did "set up" the 2nd OS to where it's supposed to go.
Launchprep part 2:
Then, "advanced restore" of the backup made a few minutes earlier:
- boot
- system
- data
Reboot
At this point OS #1 is running again and OS #2 is sitting in hiding, prepared to roll - so, let's roll:
Flashed the modified "dualboot kernel" (via an App or Odin or magic, doesn't matter).
---> DONE <---
reached the point to where everything works as shown in the video.
As said above already, yes it needs some manual work to set it up, yes there's a lot of things that might not work, yes there are other/better ways to set it up.
It's only a humble experiment - lot's of space for improvement.
Maybe you like it - for those who do, I wanted to share this
Attached to this post you find the modified kernel I used, it's based on my v1.20 custom kernel (see sig) but with the above mentioned changes.

I've seen the video m8, this is totally different approach, ur giving this device a new dimension. love u "in a straight way" hahaa

there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
http://www.appbrain.com/app/bootmanager/com.drx2.bootmanager
well, one can hope!

Thanks OP this is an awesome concept! Very happy to see you posted it with a video! and nice boot animation!

sunwee said:
there currently an app called Bootmanager which also handle up to quadruple booting. But sadly currently only support HTC phones.
Click to expand...
Click to collapse
Yeah, that's the thing.... that app is HTC only.... but we have Samsung S-II and want dualboot as well.
I'm already brainstorming on how to enhance the actual usability of this, i.e. flashing a 2nd OS directely to it's place instead of first installing it to the main system partition. But there is problems when /data is not mounted to the original partition, at least stock doesn't like it on initial boot.... well, well....

That is great. Going to use this for sure. This should be in development for sure.
Congratulations already.
Sent from my GT-I9100 using Tapatalk

This is impressive bro sure will use it
but i want to ask one thing
SD card needed for this or not ?

That would be really cool (and definitely should goes to original development). Does it work with CM7/MIUI + custom rom?

vikas776 said:
SD card needed for this or not ?
Click to expand...
Click to collapse
No, so far this completely works with all internal storage.
But I have a few ideas I have yet to try to get mounted from other places - like images in /sdcard for example (I *so* hope that'll work.... )

Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Click to expand...
Click to collapse
I made this build based on my v1.20 custom kernel, so it has everthing that one has - plus the touchfix already

exactly what i was hoping for.
great job - pls continue your work

Hi i tried this with instanity rom last night. When I use the three buttons to boot it just sits there not booting. My guess is the kernel is not compatible. Unless I made a mistake somewhere.
Sent from my GT-I9100 using Tapatalk

Hm, yah, might be that the kernel isn't fully compatible with that ROM, what kernel does the ROM usually use?
Did you boot it up fully at least once before copying /data to /cache ?

Yes I did fully boot up. But his kernel didn't have advanced activated in recovery so I flashed your kernel and moved the cache okay. But it said /data not found when I ran the 2nd command line.
I will flash aosp later. I like that rom.
I am not sure what kernel nitr8 uses. I think it is his own, Insane.tar would you like it to see if they can work together.
Sent from my GT-I9100 using Tapatalk

Tricky103 said:
But it said /data not found when I ran the 2nd command line.
Click to expand...
Click to collapse
Hm, yeah, that sounds like something didn't work.... make sure you run those commands as root, i.e. "su" as very first command (I'll add that to the first post).
Give me a direct link to the ROM and I'll try it.
Make take a few days though as I'm away from my computer a lot because of work the next two days, but I'll try once time permits.
Well yeah, and this still is in highly experimental stage, if I (or someone else) should ever get this to more stable and reliable state, I'll make an easy to use installer/setup tool
But I got a few other ideas on setting it up I have to try first....

http://goo.gl/2uZCh
This is the complete rom. Only 47mb. I thought you would like the whole rom

Tricky103 said:
Hi
Does this kernel include any of the Hellcat kernel tweaks or are they work in progress.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
May be someday WINDOWS Mo 7 and Android on our sweet beast

Hi
I tried again with Aosp Dev-null. I still get this error "cp: can't stat '/data/*': No such file or directory "
after running this command line " cp -Rp /data/* /cache/ "
Any Ideas ?
It still doesn't boot if I press 3 button it brings up the boot logo and then black screens until it boots to the 1st partition.

Thanks for the link, will download and try as soon as time permits.
Also, try this command sequence, I got an idea what the issue maybe might be, give it a shot:
Code:
su
rm -Rf /cache/*
busybox cp -Rp /data/* /cache/
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p12 bs=4096
(use "busybox cp" instead of plain "cp", maybe it helps)
And some update on my ongoing thoughts for those interested:
- got an idea on how to make a more easy to use App for prepping and setting up the dualboot environment
- managed to do a neat thing I didn't really think it would work: issued a "mount" command and the OS thought it was mounting a partition of the internal flash (/dev/block/mmcblk0p12 in this test, but was testing for later on actually doing it with p9 - you might see where I'm headed here ) but instead of the partition it actually mounted from an .img file! (loopback)
i.e. "mount /dev/block/mmcblk0p12 /somedir" actually mounted "/somepath/someimage.img" to "/somedir" instead of the partition from /dev/block/... (you just gotta love Linux and it's flexible way of handling things....)
NOW, imagine /dev/block/mmcblk0p9 (the partition carrying the system) and p10 (data) being (kinda) transparently mounted from an IMAGE FILE
I "only" have to find a way to sneak this in before init starts mounting stuff.
If there's a way to do THAT.... unlimited multiboot from OS images, anyone?
(so far this is kinda dreaming, but would be cool to get it working )