Soo Im running SC 2.9.2 with Sense Theme and I try to flash Jt's new EC kernel but it never changes. Im still on kernel 2.6.32.9 and its pissing me off! I first boot into red recovery and disable lagfix through voodoo, then reboot. Then boot back into recovery and flash the kernel of choice, then go renable lagfix in voodoo and reboot! The lady talks and everything BOTH times.. but once my phone is completely rebooted its exactly the same! What am I doing wrong? at first I didnt think that lagfix was a huge part of it but after reading posts and talking to friends it made it seeem like it was.... so IDK HELP!!!
Thanks in advance
The 2.6.32.9 kernel is the right one. The only thing that should change from kernel to kernel is the date and the email address/username right after the kernel version.
On JT's kernel you should see Something like Mar 27 in the date area. I don't know what the email address says since I'm no longer on it though.
Edit: Also note, you don't have to disable voodoo lagfix if you're already using a voodoo kernel and you're flashing another voodoo kernel
Voodoo --> Voodoo (Don't need to disable lagfix)
Voodoo --> NonVoodoo (DO need to disable lagfix)
NonVoodoo --> NonVoodoo (Lagfix should always be disabled, shouldn't even have the option to turn it on really)
NonVoodoo --> Voodoo (Lagfix should be disabled by default when flashing a voodoo kernel)
Thanks for the help. but to be exact, where does this date show up so I know if it worked?? My system looks exactly the same as before when I look under "About Phone".... so im just skeptical that it flashed cuz my batt hasnt gotten better and it doesnt seem much faster. should i wipe batt stats? will that make a difference?
Thanks!
go into terminal (or download one from market)
type:
su
{Press enter}
cat /proc/version
{press Enter}
You will see:
Linux Version 2.6.32.9 (kernel author@virtualbox) (gcc version 4.4.1 (yada yada yada) COMPILE DATE
If that compile date is the date the the author released the kernel you are running it.
it says version not found!? and it doesn't say anything in terms of a kernel number or anything!
HELP!!!!
Thanks!
i get the same thing..... on a side note i thought superclean 2.9.2 came with ec10 kernel
@tumness420 i had the same problem when you do the su in terminal than you do cat /proc/version make sure you have a space between cat and / i tried it and it works
running "uname -a" can give you the build date/time as well.
Great! Thanks for the help! @mrtonee
Now the only question is, if the kernel didnt flash through CWM recovery how else am i to do it? considering I have a mac instead of PC.
or are there any other trick tips or shortcuts into flashing kernels?
cus it says installation complete when I run it, but I swear the kernel didnt flash
Does having a theme have anything to possibly do with why kernels dont flash properly?
Thanks in advance!
tumness420 said:
Soo Im running SC 2.9.2 with Sense Theme and I try to flash Jt's new EC kernel but it never changes. Im still on kernel 2.6.32.9 and its pissing me off! I first boot into red recovery and disable lagfix through voodoo, then reboot. Then boot back into recovery and flash the kernel of choice, then go renable lagfix in voodoo and reboot! The lady talks and everything BOTH times.. but once my phone is completely rebooted its exactly the same! What am I doing wrong? at first I didnt think that lagfix was a huge part of it but after reading posts and talking to friends it made it seeem like it was.... so IDK HELP!!!
Thanks in advance
Click to expand...
Click to collapse
Just so you know...the kernel doesn't bring any visual changes. Its changes are "under the hood" so you can't see them. Like was stated if you are going from one voodoo kernel to another, you don't need to disable lagfix. Also, the easiest way to tell if you are running a voodoo kernel is to download Quadrant Standard and run the full benchmark. A voodoo phone scores 1400+ whereas a nonvoodoo phone scores around 900.
Related
As the new OC'd Voodoo kernels have come out (from JT and Dirrk), I wanted some clarification as to how exactly one would go about installing an OC'd Voodoo kernel from 0.2 Voodoo stock.
I've been hearing that you have to "remove" Voodoo first, "disable" Voodoo first, or even just install the new OC Voodoo kernel on top of your 0.2 Voodoo stock. It seems a little convoluted and ambiguous to me, and I was wondering if someone could kindly clear this up as simply as possible.
You can install right over top
If you are running a VOODOO kernel, version 0.2+ and just want to flash another voodoo OC kernel, you can flash it right over...whether it is jt's over dirrks or vice versa....
Now, if you want to flash another REGULAR kernel and you have voodoo, then you MUST run disable_lagfix FIRST...otherwise, you will end up with lots of trouble...
Today I finally rooted my phone and installed fusion 1.1 custom rom. I have been reading on the whiskey team's site about disabling voodoo before you reflash anything but I can't tell if the fusion 1.1 rom enabled voodoo or not on my phone, does anybody know or know how I can check and see? Thanks in advance.
BTW it was the fusion 1.1 with the stock kernel
If you downloaded Fusion 1.1 directly from the Team Whiskey site and did not go out of your way to also download Voodoo or a kernel that includes Voodoo and flash it separately, you don't have Voodoo. Not only would you have flashed it separately, but you would have gone through a 15 minute file system conversion process narrated by a female android. "Converting file system to optimized extension 4. Step 1. Step 2. Conversion complete." or something to that extent.
You can check by looking for a folder named "Voodoo" on /sdcard. You could also just run Quadrant and look at your score. If you score under 1000, you don't have Voodoo or don't have it enabled. Or you could re-flash and see if you brick. Learning to use Odin would not be a bad thing.
tl;dr: Fusion 1.1 is Voodoo capable, but does not include Voodoo by default. If you aren't sure if you have it, you probably don't.
P.S. search
Well I didn't flash anything seperately, just the Fusion 1.1 rom and there was no 15 minute conversion process announced so I guess I don't have it. I just wanted to be sure in case I decide to reflash it, I don't want to brick my phone.
You said learning to use Odin would not be bad thing, can it be used to recover if you brick a phone from something like not disabling voodoo before reflashing?
Thanks for the info. I did search but could not find anything directly that said yes or no fusion 1.1 has voodoo or not and some things I found on the whiskey team site made me think it was installed even though I didn't think it was originally. Thanks again.
The first thing to understand about the Vibrant is that it is virtually unbrickable. When people talk about bricking a Vibrant they are usually refering to a "soft brick" which can be recovered via Download Mode + Odin. Before you go all willy-nilly, you may want to make sure you are not hardware locked and can access Recovery and Download modes without having to use adb. You probably already confirmed this, as you've already flashed Fusion.
Definitely spend some time reading over the Vibrant Bible: http://forum.xda-developers.com/showthread.php?t=771111
Lots of good information in there including how to recover with Odin, do Nandroid backups, flash kernels, flash modems, apply themes, etc...
Also to add, if you download Terminal from the market and open it up.
In adb shell or terminal type 'mount'
If it is disabled is should read '/dev/block/mmcblk0p2'.
If it is not disabled, it will read '/dev/block/mmcblk0p4'.
This is to check and see if VOODOO is running or not.
Got that directly from the Team Whiskey website. Odds are if your Fusion questions aren't answered here then it's on the Team Whiskey site. Team Whiskey
I have looked for terminal on the market but I don't see anything called just terminal. Does it have a weird typing or something?
Sent from my SGH-T959 using XDA App
tording99z28 said:
I have looked for terminal on the market but I don't see anything called just terminal. Does it have a weird typing or something?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Android Terminal Emulator is what i use.
tording99z28 said:
...but I can't tell if the fusion 1.1 rom enabled voodoo or not on my phone...
BTW it was the fusion 1.1 with the stock kernel
Click to expand...
Click to collapse
If it's stock, you don't have Voodoo. To add Voodoo you must download JAC's kernel w/Voodoo on the Team Whiskey download page.
~SB
Sorry if this is posted elsewhere, I could not find anything via search.
I am still pretty new to flashing, I haven't used ODIN yet but am willing to learn, but I was hoping to put it off for now.
My problem: I am currently running Bionix-v official OTA 2.2 and when after I disabled Voodoo via recovery, it still boots into the red clockwork recovery, the phone is running fine, (except I am having issues sending picture messages) when I check in the red clockwork recovery it does say that voodoo is disabled.
My questions: Am I doing something wrong? And can I flash other roms over this regardless of whether or not they have Voodoo enables by default? Can I ODIN if the phone has Voodoo enabled?
Thanks! You guys made me love my Vibrant after months of frustrations with T-mo and Samsung!
...as long as Linda talked to you after you rebooted and converted the filesystem back....
You did click disable lagfix and reboot right?
Ya, she did go through the conversion, I did click and reboot, I am just worried because the recovery is still red, which I thought meant voodoo was enabled? Maybe I just misunderstood that part...
Yea your recovery will be red until you install a rom without voodoo or and older version of voodoo, or you reboot into recovery via rom manager.
Thanks! Sorry I was just over worried I guess, terrified of bricking!
hi
im new to Samsung and android, i want to test out some
ROMS. my phone was bought secondhand and it came pre
loaded with the details in my signature.
i have read through most of the newbie guide lines here on
this site on how to flash but nowhere (as for what i saw)
does not mention on how to test if your phone has a lagfix or by
which method.
as i have read you got to turn off the lag fix before flashing ROM's
so how do i turn mine off.
thanks
HtcDia
*** my current phone details are in my signature ***
Thank you for posting in the correct section and reading some material before posting!
As to your question, if you are completely stock (rooted or not), your Vibrant does NOT have a lag fix enabled. Most of the newer Roms allows for flashing over a lag-fixed (Voodoo) enabled kernel, but only if it comes equipped with a Voodoo injected kernel.
Basically
No lagfix enabled -> Can flash any rom (voodoo kernel or non voodoo kernel)
Lag fix enabled (Voodoo) -> Can flash roms with Voodoo kernel without turning off Voodoo | Must disable Voodoo to flash non-Voodoo kernels
edit: I'm not sure if that is the answer you're looking for but if you go to the red CWM recovery, you can go to Voodoo -> Disable Voodoo. If you do not have a red recovery, then most likely you do not have a Voodoo enabled kernel, thus do not have a lagfix in place. (I assume you also did not use One-Click Lagfix)
thanks anthonys2r
i have not seen either voodoo or anything pertaining to it on my phone nor
have i done the one click fix.
so i can safely assume that i do not have one in place.
thanks for the answer it is perfect
HtcDia
^ You may want to start "fresh" and use ODIN to go back to stock... very easy process (check my signature).
You likely DO have a lagfix (ext4 "voodoo"). But, if your next rom has voodoo enabled, it will not matter if you disable it or not.
There is an app, Voodoo toggle in the market you can use... or you can reboot into CWR and go to the voodoo section. It will also tell you.
Here is the Simply Honey ROM THREAD
Not sure if you were planning on updating or trying a new rom... if the latter, really recommend going back to stock again. I would also encourage Trigger 3.2... its 2.2 but it's stable/themed well!
opening a terminal emulator and typing the command: mount should tell you what file system you're running. Unless everything lists RFS you have a lagfix enabled. If not just 3-button to recovery and scroll down to voodoo... It will tell you inside if it's activated or not.
s15274n
It's funny you should suggest that i should checked your signature
because most of the stuff that i have gathered initially till present
came from your links LOL.
thanks for providing them as they are great material for android scardy
noobs like me.
yes i do have voodoo. i actually found it lol.
if im right what i want to do is now upgrade my version.1 Simply Honey ROM
to another stable version just to get a feel of flashing and stuff
thanks
HD
Good stuff man.... glad that it helped.
s15274n said:
Good stuff man.... glad that it helped.
Click to expand...
Click to collapse
On a related question, i can't initiate voodoo for some reason. I read the log and it said "model not detected". Anyway to correct this?
I cant seem to enable voodoo on my phone I have trigger 3.2 and I flashed overstock 1.5.2UV, I'm coming back from CM7 and I don't have the red clockwork recovery either? What can I flash to get this going I have Voodoo toggle that doesn't work neither does voodoo control ...
Did you odin back to stock and then flash Trigger and Overstock?
yw2012 said:
On a related question, i can't initiate voodoo for some reason. I read the log and it said "model not detected". Anyway to correct this?
Click to expand...
Click to collapse
Mine says the same thing anyway to correct this...I've already odin, wiped, re partition with odin and still nothing
jneal9 said:
Did you odin back to stock and then flash Trigger and Overstock?
Click to expand...
Click to collapse
Yes I did, I'm going to do a few more things to see if I can get it to work
Hm. When booting Trigger for the first time did you hear the voice enabling voodoo?
No Im sure it has to do with CM7 file systems or something...
If you odin'd back and checked repartition that should have wiped the CM7 filesystem and reverted it back to stock RFS.
And you are on Trigger and don't have the red Clockwork?
jneal9 said:
If you odin'd back and checked repartition that should have wiped the CM7 filesystem and reverted it back to stock RFS.
And you are on Trigger and don't have the red Clockwork?
Click to expand...
Click to collapse
I did check repartition it didn't work log file in voodoo folder still says model not detected, Im about to see what happen when I flash trigger 3.2 again I formated system in CWM and odin with repartition checked....
still nothing dam...
Just read another possible solution in a different thread that I didn't think of...
http://forum.xda-developers.com/showthread.php?t=1096439
Try to use Eugene's odin rom, and then go back to stock JFD and see if that fixes it.
I got it you have to odin Eugene's froyo that doesn't brick, then I used Eugene's 2.2 Downgrade odin flashed that annnnnndddddd now I'm flashing Trigger and I can hear Lindas voice now
Happy flashing.
Hey guys so ive been trying to Flash the SUPER_DragonMODz kernel but for some reason it does not want to work. Ive used sgs kernel and used the clockworks mod to install the kernel but for some reason it doesnt want to work. Not sure what im doing wrong. Ive tried installing while on Axura 2.2.9, Bionix 1.2, and even did a complete factory reset with ODIN but nothing seems to work.
Thanks for the help guys!
Voodoo
From what I have read that kernel is good but it only oc's when you are using multiple processes, gaming, ect...
Make sure your rooted.
Why don't you try loading up a voodoo+ lag fix on whatever rom you are running. I seen a huge difference in speeds and stability plus easy access to clockwork recovery that overrides the stock vibrant recovery. Then you can download CPU Master and put your mhz/ghz to what you want on boot up
Give it a try.
Don't know about bionix but Axura may have a framework that is incompatible with that kernel
Also, go into recovery and flash it through there instead using a app that will give you the best chance for a kernel to take. But, my guess that kernel may not be for that rom. Try a different one and see..........