After I flash what seems like any kernel with Voodoo in it, I get stuck at the Vibrant boot screen after Linda says Voodoo's been activated. The last one I tried was Jocelyn's Categorically Worthless. I usually wait 15 minutes before pulling the battery out and ODINing back to stock. Is it a kernel problem? Or does my Vibrant simply not like Voodoo?
To be clear, I'm not looking for a soft-brick solution. I know how to use ODIN and have gotten myself out of many a jam. But I've been trying to figure out how to get Voodoo on my device for months and haven't come up with anything (yes, I've searched far and wide). I'm still using Nero v1, since none of the Voodoo'ed kernels bundled with Team Whiskey's newer ROMs have played nice with my phone.
Any help would be appreciated!
Do you have a lot of apps installed? That's the only thing I can think that might be making it take so long. Try doing it right from a fresh odin with no apps installed and it should convert in about 10 mins
Maybe try odining with Eugene's Froyo that doesn't brick then see what happens.
I don't think it's the apps; the hang still occurred when I tried to flash Jocelyn's kernel on top of a clean install of Nero v1. I hadn't done a Titanium restore or synced my Google account or anything like that yet.
[EDIT: Is Linda supposed to say anything after she tells me Voodoo's been enabled? Because if not, then I think I actually made it through the conversion in under 10 minutes and something else is going wrong afterward.]
As for Eugene's Froyo, I'll try that tomorrow and let you know. Just to make sure -- are you suggesting I ODIN with Eugene's ROM, and then try Voodoo again directly? Or should I ODIN with Eugene's Froyo, then flash another custom ROM that doesn't include Voodoo, and then try the new kernel after that?
Thanks!
Related
So, I messed up. The plan was to uninstall RyanZA's lagfix, then flash JAC's new OC/UV kernel with Voodoo. I got distracted, and didn't uninstall the lagfix before flashing (through Clockwork, if that matters). My phone didn't boot after an hour, so I figured I'd nandroid back and not be so stupid this time. When I tried, I found that I couldn't because of the change to the /data from Voodoo. So then I figured I'd just use Odin to go back to stock, I've done it a couple of times before. That didn't work either, Odin went just fine, but it still doesn't get past the black screen. I read the Voodoo thread, and saw the "disable-lagfix" thing you can do, but now I can't mount my sdcard, and when I try to push it with ADB, it says permission denied. How can I fix this? Also, as an aside, since I flashed the stock back on, with the T-Mobile boot anim and all that, will I be able to get it replaced, if need be?
Flash this first:
http://forum.xda-developers.com/showthread.php?t=740558
Then flash back to stock with odin, worked for me.
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Zaphodb2002 said:
Yeah, reading into the voodoo thread some more, I found it, and just fixed everything. Thanks for the quick reply! Odd that the froyo rom fixes it, but whatever, happy to not have to go to T-Mo tomorrow!
Click to expand...
Click to collapse
Yeah, I soft bricked my phone yesterday and couldn't get it back up and running with the stock rom until after I flashed eugenes froyo rom first. My guess is that because eugene codes his roms to automatically format your OS drive it clears everything out and sets a fresh slate so you can than flash the stock rom back without issues.
Pure speculation on my part though. Glad you got it fixed.
I am unhappy with ji6, my gps and compass no longer work and i've had nothing but problems since the update. also the call waiting dial screen lag sucks. I would like to go back to my previous rom which was basically stock rooted with ji2 gps fix and accurate battery mod. I have this saved as a backup, but I am afraid to flash it. When I flashed the new ota update it bricked my phone. I was unble to load my previous backup through clockwork recovery. I had to completely wipe my data and start over. any advice on the safety of trying to flash back to my backup rom, will it conflict with the ji6 framework?
Thanks
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
yeah, maybe i'll try bionix first, It's just that I was really happy with the way it ran before this stupid update.
I also was fond of my setup before the update. Bionix made it better again. Hope you like it, worst case go back to stock.
I will say I would make sure you can revert to stock from bionix. I have seen a number of posts with issues, but that may be from people who had the oc kernel? I can't say with certainty.
Same here, i flashed bionix (first time using bionix) I flashed bionic 1.7 w ji2 modem oc/uv no voodoo and this thing flies! Gps is fine, navigation is usable.
s15274n said:
There should be no issues at all. I assume you still have the stock kernel too... if you had an oc kernel I would go back to stock first.
just go to rom manager and click on restore, then select your old backup... should take you to cwr and reboot when done.
My first thought was to download a custom rom. I just flashed bionix 1.7 and it seems much better than stock JI6.
I would really urge doing that...
Click to expand...
Click to collapse
I tried flashing back to my backup...(stock, rooted with bat mod and ji2 gps fix) and it got stuck in the vibrant startup screen, same as when I ran the ota. I guess my previous setup is no longer an option. Before I try another rom and have to redo all of settings and apps again, I would like to try to at least get the gps working on the ota ji6. Any advice on how to do that would be appreciated. So far I have tried all of the things I was able to find in other threads...deleted gps data, made sure lbstest settings are stock, turned off wireless, etc. I still get no locks at all.
Is bionix really that good? I'm considering it. I'm on my stock rom, stock kernel.
I think i'm going to try it out.
So...
Let me start off by saying I've been doing a lot of searching and reading already and pretty confused.
I've been playing around with my Vbirant trying to install the Voodoo Lag fix. Currently I'm running stock rooted JI6. Every time I install the voodoo lag fix, I get stuck at the Vibrant screen. Had to odin Eugene's Froyo that doesn't brick then odin back to stock. Tried this multiple times and kept getting stuck at the Vibrant screen.
Finally, tonight I tried going back to the original JFD and was able to apply the voodoo lag fix.
What I'm trying to figure out is how to apply the voodoo lag fix specificially to a stock JI6 build. Can someone tell me what the heck I'm doing wrong? I've verified that I don't have the larger NAND.
Below are some of the links that I've used for reference. Thanks for your help!
http://forum.xda-developers.com/showthread.php?t=791478
http://forum.xda-developers.com/showpost.php?p=8322865&postcount=131
http://androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/
Are you actually applying the correct voodoo.zip file for your phone version? Try renaming it update.zip and reinstalling packages in recovery, that might work.
Thanks Bobbbb. I've tried both 3.0 and beta4 specifically for the Vibrant. Renamed both to update.zip and put it on root of the internal SD, rebooted into recovery and did a re-install packages. Get "Linda's" voice, all 3 steps, and then it's just stuck at the vibrant screen. Let it sit there for 20-30 minutes and finally gave up. This was all for stock JI6.
For stock JFD, it only took maybe 10 minutes for the whole process.
I bought a T-Mobile Galaxy S T959. When it turns on, it says "Samsung Galaxy S GT-i9000", then the screen changes to "Samsung VIBRANT" I reflashed back to stock using odin, but it still shows the same gt-i9000 boot screen.
Does anyone know how to change it back to normal? So far, I have rooted the device, installed clockwork and flashed to the bionix rom, and installed sgs kernel flasher from the market.
I watched some videos online that showed the kernel boot screen changing after flashing a new kernel through sgs kernel flasher, but I dont know much about kernels or which one needs to be flashed.
Does anyone know what needs to be done, or have any ideas I should try?
Thanks
Well theres nothing wrong with that but it seems like it bothers you so which kernel did u used to odin???
Sent from my SGH-T959 using XDA Premium App
This is happening because the phone in the past was flashed with an I9000 based kernel. Eugene I beleive used to make some back before we had Froyo. I also had that bootup screen for a while. I don't have it anymore.
I believe I lost it through one of the many kernel flashes I have done. Just flash some of the latest kernels. It MAY clear this issue for you though it really is not an issue.
It is just the wrong picture stuck in some folder on the phone. There is no harm done to your phone nor is there anything wrong or defective with it. The only thing is that it may bother you. If it does bother you, go on a flashing spree and flash some kernels and roms. I think sooner or later you will get rid of it without even trying when you upgrade your ROM/Kernel.
Thank you, I appreciate your replies.
I bought this phone from someone online, so it was like this when I got it. Therefore I am unsure of which roms/kernels were flashed onto it in the past. I have flashed many roms, but those only seem to change the boot animation. The kernel boot screen is staying the same. Like I said, I dont really know much about kernels.
Would there be one which you recommend I try that might fix it?
I know its not really a problem, but for some reason it just annoys me seeing it say gt-i9000 at startup.
My ultimate goal is to be running the latest build of team whiskey's bionix rom. I have no clue which kernel I should flash or that would work with it.
Any help or advice is greatly appreciated.
Thank you
Try the bullet kernel.
http://edtdev.com/forum/topic/86-kernelbullet-1420ghz-4202011/
It is the fastest kernel for the Vibrant to date (1.42Ghz STABLE on most phones, outstanding battery life, all features and tweaks). It also has a custom boot screen which MAY replace your I9000 one. I'm saying MAY because I am not fully sure. In either case it is either the best or one of the best kernels for this phone to date.
As for ROMs, Team Whiskey quit Vibrant development around late February. They have moved on the the Nexus S and G2X so I'm not sure their latest ROM is the best. It's certainly an amazing ROM but there may be more recent ROMS which have more features or speed. Choice is yours.
You may try flashing some Froyo kernels from Eugene. Since his kernels likely introduced the I9000 boot you have now, flashing newer versions MAY get rid of it...who knows. Alternatively, there is another option if you are SET on getting it out.
If you flash with ODIN and also check repartition, I beleive ODIN will WIPE everything off the phone completely. Yes, all backups...everything will be gone but it should in theory also take that I9000 with it. It's a bit more risky than normal ODIN but the choice is there if you are set on it. Try the other options first and if you decide to do a repartition, READ on how to do it properly first.
@}{Alienz}{
Thank you, I tried to flash a few kernels and it seems to me like what you said about the wrong picture being stuck in the phone is what the problem is.
I Re-flashed with Odin and did a re-partition as well, but the image is still there. After rooting and flashing the bullet kernel, it still shows the gt-i9000 screen and then it switches to the bullet screen instead of the vibrant one it used to be.
After trying a few kernels, they all seem to replace the screen after the i9000 kernel screen.
Im going to keep trying to get rid of it, but i wanted to thank you for your response as I am one step further now.
Ah. Dumb-stuck image problem then huh. I thought the kernels would flash it right out. Well...you can ask someone above me about how to get it out.
Go to the EDT dev website. www.edtdev.com and join their IRC. See if a developer there can help you out with getting rid of it.
Also try the Team Whiskey IRC chat. They have more devs and people in their IRC that may be able to help. Their chat is located here:
http://webchat.freenode.net/?channels=teamwhiskey&uio=d4
I'm sure someone at those IRC chats will help you out.
try flashing the stock "param.lfs" file through odin
Okay I have had this problem and know exactly how to fix it. What happened was whoever had that phone before you flashed an I9000 gingerbread kernel with I9000 gingerbread bootloaders, that's why it shows that every time. Here is what I did to fix it. I don't know if it has to be done this way, this is just how I did it.
Step 1: download both of these files
PDA:http://dl.dropbox.com/u/23420259/Eugene_JK2_Froyo.tar.md5
PIT:http://dl.dropbox.com/u/23420259/s1_odin_20100512.pit
Step 2: Flash those files through Odin, but make sure you uncheck repartition, as I have read that if you leave it checked while flashing those files you might end up with a hard bricked phone. It will boot straight into recovery after it's finished flashing and will have some errors, that's okay just click reboot system now.
Step 3: Odin back to stock 2.1 like normal.
After you do that and Odin back to stock 2.1 wait like 10 minutes and then flash whatever rom you like. After step 2 though you should be rid of that awful GT-I9000 boot screen. I just Odined back to stock 2.1 to get rid of the broken recovery. I don't think you have to do this.
Let us know if this helped you, so that if it doesn't work someone might have an alternate way to fix it.
Oh also before I forget, I have to give credit where credit is due. Those are files are Eugenes files and I am in no way saying that I developed or had a hand in developing them.
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.