Please help - Vibrant Q&A, Help & Troubleshooting

I have digged this forum looking for a solution to fix my phone and i cant seem to find anything....
Here is my issue
i rooted my phone, im still using stock rom with the latest update
then i flashed the voodoo lag fix via clockworkrecovery and now my phone
is stucked in the vibrant screen. I cant get into download mode or recovery
Please help.

Has anyone helped you yet bro?
Sent from my GT-I9000 using XDA App

Remember it could take voodoo up to ten minutes for the first boot. If not take your battery and sim card out, put back in and odin back to stock. And just in case something funky is in your internal memory from voodoo check the repartition box in odin. But normally you don't check that box.
Samsung Vibrant using Bionix 1.9.1 w/JACs UV/0C v1.1

I forgot to tell u the stock ji6, or stock rom with update has to be run with a backwards compatible kernel or u will get stuck at splash screen. Jdf is different kernel than ji6.
Samsung Vibrant using Bionix 1.9.1 w/JACs UV/0C v1.1

Related

[Q] Help! Got stuck flashing Nero over Macnut!

Hi. I am trying the ROMs one by one to decide which suites me best. I first tried Obsidian V4.2 and flashed Macnut R14 over it. So far so good. Then I tried to flash Nero V3 over Macnut R14 (all flashing was done with ROM Manager) but I got a exclamation mark several seconds after rebooting. The same problem even when I tried to flash Obsidian instead. (I can still reboot the phone via adb and then return to Macnut.) So what went wrong? What's the correct procedure for doing that?
Thanks in advance!
hhsz said:
Hi. I am trying the ROMs one by one to decide which suites me best. I first tried Obsidian V4.2 and flashed Macnut R14 over it. So far so good. Then I tried to flash Nero V3 over Macnut R14 (all flashing was done with ROM Manager) but I got a exclamation mark several seconds after rebooting. The same problem even when I tried to flash Obsidian instead. (I can still reboot the phone via adb and then return to Macnut.) So what went wrong? What's the correct procedure for doing that?
Thanks in advance!
Click to expand...
Click to collapse
Please Post in the right section. People won't even look at this most of the time if not in the Q and A. Please read the Forum rules!! and Odin back to stock then try flashing something. Probably have some Ghosts in there.
Yup that's it... You need to ODIN back to stock and then start over. Look around in the vibrant bible and you will see info about that very topic.
Look for the JFD tar and the stock .pit file!
Goodluck
Sent from my SGH-T959 using XDA App
If you had read the instructions on flashing 2.2 ROMs, you would have seen that you have to ODIN to stock, THEN flash the 2.2.
Sent from my Nero v3 Vibrant.
hhsz said:
Hi. I am trying the ROMs one by one to decide which suites me best. I first tried Obsidian V4.2 and flashed Macnut R14 over it. So far so good. Then I tried to flash Nero V3 over Macnut R14 (all flashing was done with ROM Manager) but I got a exclamation mark several seconds after rebooting. The same problem even when I tried to flash Obsidian instead. (I can still reboot the phone via adb and then return to Macnut.) So what went wrong? What's the correct procedure for doing that?
Thanks in advance!
Click to expand...
Click to collapse
Odin back to stock is the way you should do it. Likely you are needing sig or mounting done. Which can be done in recovery, if you know how to do it. If you do not. refer to the prev suggestions.
Side-note-make sure you have permissions updated in Rom Manager and Dropbox in back-up to smooth your path.
danerer said:
If you had read the instructions on flashing 2.2 ROMs, you would have seen that you have to ODIN to stock, THEN flash the 2.2.
Sent from my Nero v3 Vibrant.
Click to expand...
Click to collapse
no you don't.
to the op, did you change kernels or do a lagfix or voodoo?
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
funeralthirst said:
no you don't.
to the op, did you change kernels or do a lagfix or voodoo?
Click to expand...
Click to collapse
No. I did nothing special. I know that Macnut R14 comes with Super IO kernel while Nero V3 with stock kernel + voodoo. There is a voodoo folder under /sdcard however it is disabled with a disable-lagfix file.
I did once have voodoo enabled, but disabled it via CwM Recovery before flashing Obsidian 4.2.
I can't even flash Ginger Clone R2 over Macnut R14 (both with Super IO Kernel)!
Just ODINed JFD and everything went back to normal.

[SOLVED] voodoo help. Please.

Ok, So I flashed superclean 2.7 and it borked my phone. So I used Odin and the EB01 and PIT files mr.adrenalyne gave us as a fix for the situation. So after flashing via odin, I flashed CWR ALL tar file. Up until this everything worked great and I thought my ordeal was over. I opened root explorer and noticed a file called voodoo saved. So I booted into recovery and it went straight to red. Used to go to blue recovery then I would have to apply update.zip to red. So I checked the voodoo in recovery and it said lagfix and voodoo were both enabled. Im very puzzled by this and really only have 2 questions. How did I get voodoo and more importantly how do I get rid of it? As in total stock no traces of voodoo. Any help is appreciated. Thanks
Sent from my SCH-I500 using XDA App
http://forum.xda-developers.com/showthread.php?t=979744
read.
Whats up mike, I followed this method over at the AC forum, It doesnt work. After I disable lagfix and flash a new non voodoo kernel I then go into odin and flash back to stock EB01, boot, flash new CWM all and boom. Back to.voodoo enabled. I think im gonna have to format internal SD card to rid myself of this. Something is off and I cant seem to get of voodoo.
Sent from my SCH-I500 using XDA App
Try adrynalyne's 2.7 fix. There is a tar/odin in there that you should flash. It sounds like a dbdata issue.
After flashing the eb01 all in one, you can flash whatever rom you like.
GrainOsand said:
Whats up mike, I followed this method over at the AC forum, It doesnt work. After I disable lagfix and flash a new non voodoo kernel I then go into odin and flash back to stock EB01, boot, flash new CWM all and boom. Back to.voodoo enabled. I think im gonna have to format internal SD card to rid myself of this. Something is off and I cant seem to get of voodoo.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
it does work. you are missing something. if you flash nonvoodoo kernel and you can boot your phone then you dont have lag fix enabled. get quadrent from the market and run it. what is your score.
Ok I finally got it, I took a little trip over to the IRC, where one of the devs helped me figure it out. Turns out I must of picked up a corrupt file somewhere. Ive flashed my phone so many times since DL30 leak showed up I couldnt tell you where it came from, but no matter what I did or flashed I was still showing voodoo. To make a long story short I ended having to use heimdall to go back to the original build, the one before DI01. After that was done I was able to build my way back to EB01. Thanks for the help its all good now.
Sent from my SCH-I500 using XDA App

[Q] Bricked Vibrant

I need help! I was putting an gingerbread rom on my phone made by simply honey and it didn't work. It. went though the flash process like normal, but when it was time to reboot, it would only do the samsung vibrant download then it would say not enough space on partishoner then cut off and does the samething again. It won't let me reboot back into clockwork mod screen.
Can someone help me????
Get a stock voodoo kernel by supercurio for Odin and flash that. The use three buttons to recovery and try again or restore a backup or flash a Froyo rom.
Sent from my GT-I9000 using XDA Premium App

[Q] Stock Android for Vibrant?

Hello. A friend of mine recently bought a Vibrant that is stuck at a constant boot loop. I have a heavily modified Captivate, so I know that as long as the phone boots up, it can get to Download Mode. I am in the process of reverting the phone to JFD using Odin. My question is, which is the most recent OFFICIAL f/w available for the T-Mobile Vibrant?
"Official" Froyo I believe was KB1. But KB5 is the last leak we got (and most likely will ever get). I can't think of a reason why you shouldn't use KB5. Most will agree that it's better than the "official" KB1.
excellent, i'll look it up and install it. thanks a lot bro!
No problem. There's a stock deodexed KB5 somewhere in Vibrant Dev forum but if you want a slick custom rom I'd suggest either ZenDroid or Project-V.
Project v is a sweet 2.2 custom rom....only issue ive ever had with it is you dont get a notification for voice mail,so if you see a missed call...it doesnt mean you dont have a voice mail message....better go check.
Other than that its perfect with everything working.
Granted you can download other apps to work around the voicemail notification
I just flashed JFD via Odin 3, and I'm stuck in a boot loop. Any suggestions on what to do?
Sent from my SAMSUNG-SGH-I897 using XDA App
kafepuya said:
I just flashed JFD via Odin 3, and I'm stuck in a boot loop. Any suggestions on what to do?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Pull battery, sim, and ext sd if you have one. Wait 10 seconds or so. Put only the battery back in. Hold vol up+down and plug in usb to boot into Download mode. Try flashing JFD again. See if that works for you.

[HELP] Semi-Bricked phone on voodoo kernel

Hello,
My phone was previously running an unofficial version of MIUI and AOSP voodoo kernal. My phone became very buggy and what I was running on was old so I wanted to update to newer things out there today. So I knew I had to disable the voodoo kernel before installing the new ROM but getting into CWM via "Volume up and down and power" didn't seem to be working so I got into CWM using MIUI's reboot option. Unfortunately, this took me to a normal blue CWM so I though huh i guess I don't have voodoo installed then. So I wiped data and cache and attempted to flash the new ROM. about 10% in it rebooted my phone and now it gets stuck at the SAMSUNG logo. I actually can now get into the red voodoo CWM for some reason, but I can't disable it because my phone won't boot. Even though I can set it to disable since it won't boot im guessing it wont actually disable.
How can I get my phone back to stock so I can start over?
Thanks.
You need to see droidstyle's guide on flashing rooms and going back to stock. You should not have three fingered into recovery. There us a section there for your particular situation.
Sent from my SCH-I500 using Tapatalk 2
You should have put it into download mode and re-flashed your radio choice with atlas pit 2.2
Sent from my SCH-I500 using xda premium
Sorry, I resolved this by flashing a DI01 Image over Odin.

Categories

Resources