Help! Just installed Vodoo, phone won't boot right. - Vibrant Q&A, Help & Troubleshooting

Ok, i read the how to for the new kernels, it said its easy and what not. I even pm'ed another person on here as i am still kind of new asking was it safe with my current ROM and all that and i got a yes, now i know its my risk to try i just understand what went wrong. I'm on 2.1 still on the stock ROM and JFK and i downloaded the Vodoo Clockwork recovery version with colorfix zip. I went into clockwork and entered reboot mode, then chose the zip from there and heard a weird voice when the phone turned off saying step one, this may take a few minutes. Then i heard entering step 2, then finally i heard conversion successful. Now when it rebooted it went through the Vibrant and t mobile screen beginnings fine, stayed at the Galaxy S screen for a while then goes to a black screen everytime. I've even rebooted the regular way as i can't get the phone on. Please what happened and how do i fix it?

Email me bro [email protected]
Sent from my SGH-T959 using XDA App

It sounds like your NAND chip is too big.

I had the exact same thing happen to me when disabling voodoo to do a backup. I ended up flashing JI6 via Odin then re-flashing bionix without the voodoo lagfix.

tenjhotenge said:
It sounds like your NAND chip is too big.
Click to expand...
Click to collapse
Can you elaborate?

Either your NAND chip is the bigger version or you just haven't waited long enough. The first initial boot with voodoo is a long one. How long did you wait for it after the screen went black?
Voodoo Beta 4 currently only works with vibrants with the smaller NAND chip. But if you really want the voodoo lagfix on your bigger NAND-chipped vibrant, there is a way around to installing it. Go here:
Larger NAND Voodoo Fix
Voodoo Beta 5 should address the larger NAND chip issue but as of this post, that is the current solution for voodoo.
EDIT: BETA 5 is supposedly scheduled for release tonight

Related

[Q] Phone doesn't boot, sits at black screen after boot animation

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.

[Q] Need help restoring phone with odin.

So today I finally took the leap and flashed my phone (I've had it since it launched). I flashed it with Axura 2.2 and everything went great. I was playing around with it for a few hours, then I got greedy and decided to add the Voodoo lag fix, and this is where things got messed up. Basically, it didn't take, i got a female robot voice telling me I didn't have enough space available. So after that the phone was still working as normal, but I lost all my info saved in the internal memory and the phone started acting weird and wasn't booting up properly. So I did some reading and came to the conclusion that i should go back to stock and start all over again.
That's where I'm stuck right now. I'm trying to use Odin to restore to stock, I downloaded all the necessary files, and entered them into the proper fields in Odin. But, when I connect the phone (In downloading mode) it doesn't say [com7] in Odin like it's supposed to, it says [com3] instead.
And that's where I'm stuck at. Any idea where I screwed up and how to unscrew it up? Thanks....
Redo it com can be anything a long as it connects and stays connected you did it right from what I understand
Nerov3 voodoo
Hotstuff5964 said:
So today I finally took the leap and flashed my phone (I've had it since it launched). I flashed it with Axura 2.2 and everything went great. I was playing around with it for a few hours, then I got greedy and decided to add the Voodoo lag fix, and this is where things got messed up. Basically, it didn't take, i got a female robot voice telling me I didn't have enough space available. So after that the phone was still working as normal, but I lost all my info saved in the internal memory and the phone started acting weird and wasn't booting up properly. So I did some reading and came to the conclusion that i should go back to stock and start all over again.
That's where I'm stuck right now. I'm trying to use Odin to restore to stock, I downloaded all the necessary files, and entered them into the proper fields in Odin. But, when I connect the phone (In downloading mode) it doesn't say [com7] in Odin like it's supposed to, it says [com3] instead.
And that's where I'm stuck at. Any idea where I screwed up and how to unscrew it up? Thanks....
Click to expand...
Click to collapse
Any com is fine mine mostly shows 3 but once in a, while 5
No worries its the same
Sent from my SGH-T959 using XDA App
voodoo has been giving my phone issues as well. argh!
Anyway, like xrider said, I believe any COM is fine.
Odin won't do anything for me with [com3]
I actually got it go to [com4] earlier, Odin did it's job and completed. Once I rebooted the phone, it still wasn't right. It opened up to that screen where you use the volume buttons to move, then press power to enter, like if it was still rooted. I clicked on reboot and it started back up like normal. So I was getting ready to flash axura again, I downlaoded OCLF, titanium, and rom manager again. But when I clicked on the OCLF app, EVERYTHNG was unavailable. So I figured I would try and restore to stock again. And, now I'm stuck there again. I'm getting the [com3] thing again, the phone is in downloading mode of course, but now, i have some red letters on top of the screen that say, "keypressed, 164"
:\
I'll give you my two cents since I had to learn about ODIN the hard way earlier this week. It doesn't matter what com port it shows (mine showed com1 I think, but never 3 or 7). I know you said you were going back to stock, but does that mean your are going back to JFD, or something else? Do you have the 512 pit and the right tar file? Are you repartitioning or not? I certainly don't have all the answers, but it's still a little too fresh in my head to forget. Also once you get back to root, I would highly recommend Nero v3 (I don't run Voodoo. Haven't really understood the advantages/disadvantages, plus it seems like it could be over my head), it's a really great ROM and some of the new mods are starting to come out.....
I was gonna post up some pics of what I'm looking at, but I cant because I don't have enough posts yet! Guess I better whor3 it up!
gtiryan said:
I'll give you my two cents since I had to learn about ODIN the hard way earlier this week. It doesn't matter what com port it shows (mine showed com1 I think, but never 3 or 7). I know you said you were going back to stock, but does that mean your are going back to JFD, or something else? Do you have the 512 pit and the right tar file? Are you repartitioning or not? I certainly don't have all the answers, but it's still a little too fresh in my head to forget. Also once you get back to root, I would highly recommend Nero v3 (I don't run Voodoo. Haven't really understood the advantages/disadvantages, plus it seems like it could be over my head), it's a really great ROM and some of the new mods are starting to come out.....
Click to expand...
Click to collapse
I don't even know what JFD is When i said stock I meant to well.... stock, like out of the box. I think I have all the right files, I got them off a post here on XDA. As far as repartitioning, I've read to do it, and not to do it, so I've tried it both ways. I might give that Nero v3 a chance. I was really impressed with Axura 2.2. But like I said, I got greedy and added Voodoo-doo
Well I figured out part of my problem, I was using an outdated version of Odin. I was using 1.0, I upgraded to 1.7 and it worked and reset my phone. The only problem I'm still having is, the phone feels like it's still rooted. Do I have to manually unroot it, to get it back to normal? Also, when I open the OCLF app, NOTHING is available to chose from, everything is in red. And lastly, when I hook it up to my pc, it doesn't show up in my computer.
Hotstuff5964 said:
Well I figured out part of my problem, I was using an outdated version of Odin. I was using 1.0, I upgraded to 1.7 and it worked and reset my phone. The only problem I'm still having is, the phone feels like it's still rooted. Do I have to manually unroot it, to get it back to normal? Also, when I open the OCLF app, NOTHING is available to chose from, everything is in red. And lastly, when I hook it up to my pc, it doesn't show up in my computer.
Click to expand...
Click to collapse
How does the phone feel like its still rooted? If its still rooted you should see the superuser app in the drawer or you can d/l the terminal emulator app from the market and type su. SU will tell you if you have root or not. Aslo try a diffrent usb port on your pc, that happens to me once and a while.
badaphooko01 said:
How does the phone feel like its still rooted? If its still rooted you should see the superuser app in the drawer or you can d/l the terminal emulator app from the market and type su. SU will tell you if you have root or not. Aslo try a diffrent usb port on your pc, that happens to me once and a while.
Click to expand...
Click to collapse
Ok, I was making a mistake, it wasn't rooted after the reboot. It's just something doesn't feel right.
I restored with Odin again, so that's all good. I want to try out Nero v3 this time, like was suggested earlier, the problem I'm having now is, I'm having a hard time downloading from the market. I'm trying to download ROM Manager from the market, but it just says "starting download" and nothing ever happens.
Back in business! Flashed it to Nero v3, this is thing is FAST baby!
Yeah buddy!

[Q] Cannot disable Voodoo lagfix

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!

[Q] ICS b4 was running great, rebooted to samsung logo

getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
exzacklyright said:
http://exzacklyright.blogspot.com/2012/01/how-to-flash-ics-on-verizon-samsung.html
Click to expand...
Click to collapse
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartition and wipe out every bit of data I had. The posts about howto fix CWM bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OP, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
wizayne said:
Thanks for the response. Sounds like a good guide for newbs but in my case information is redundant. I have no problems with the install, unless recovery switches to cm7 recovery during reboot and cannot manage to boot/flash/nandroid until I Odin stock ei20 with repartitions and wipe out every bit of data in had. The posts about howto fix cwm bootloop for cm9 do not seem to work for me, as the post says.. Please reread the OPEN, ya got me excited thinking there was a solution ;-/ thanks anyway, maybe it will help another user.
Click to expand...
Click to collapse
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
mkuehl06 said:
have you tried flashing glitch kernel to the phone. imo it sounds like a kernel issue and not so much a phone issue.
Click to expand...
Click to collapse
The problem started after using ics from alphalulz v1 on around build 3 team hacksung IMMEDIATELY AFTER flashing glitch kernel v14 build 4...I have since kept away from glitch on ics, and the problem remains.
Lately it hasn't been as bad though and it seems by hitting random buttons during boot that it will eventually start but reading tells me glitch v14 build 5 is still recovery bootloop ridden and I haven't seen a word about it in the OP for ANY ics components be it team hacksung roms or glitch kernel, and an issue like this which from reading is seemingly widespread *should* be mentioned.
Any suggestions?
In your op you said e120, what phone are you using. E120 isn't a fascinate build.
Sent from my SCH-I500 using XDA App
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
wizayne said:
Ei20 is the latest and greatest version of gb/radio from uscc for the mesmerize, not that it'll change the outcome afaik to go to anything else... unfortunately ;-/
But it is a full flash package if ya open the tar up complete with movinand, sbl, radio, rfs, etc.. I think it is a 10 or 11 file package and I've used it a hundred times with making the switch from mtd to bml
Click to expand...
Click to collapse
That makes more sense to me now I know what phone your on. Try rootzwiki they have a mesmorize section, they can help ya out more than I can. I have fassy so idk much about mes
Sent from my SCH-I500 using XDA App

Q: blank screen after T-Mo splash animation, possible to fix without wiping?

Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737

Categories

Resources