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.
Related
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
So to start off, i was having some issues with not being able to make a nandroid. I was getting bad boot image errors. I had tried everything from atlas pit with fresh stock, to the new gb, and now comrom 2.0/2.1 with the non voodoo setup. I was recently downloading some new kernels to try and really wanted to try them out. So i tried pbj -50v, flashed via cwm red, still unable to perform nandroid. Saw kernel flasher lite on market and tried to flash via it, failed. Downloaded pbj sv, tried flashing it via sgs kernel flasher, success kinda, it failed to perform reboot as app stated it was doing. Used tsm power mod to boot into recovery. It came up yellow and as v3.2.0.0! This is new to me as i had been out of the root scene due to a faulty micro usb port, as i was only able to achieve dl mode and recognition of phone in odin once and immediately stocked it and ota'd thru the months. Finally got vzw to send me a refurb running ed04. I immediately installed cwm, failed nandroid. Tried ec09 &then nameless 4.1until it borked my sd. That's when i popped in my my old bb storm sd and started on my quest as stated above.
Anyone know what i did, lol?
*Forgot to mention that i was able to do a nandroid in the yellow cwm. Yay!
Sent from my SCH-I500 using Tapatalk
I called flash mananger lite by the wrong name above. I called it kernel flasher lite by mistake.
Sent from my SCH-I500 using Tapatalk
Yellow cwm is specific to the pbj kernels
Sent from my SCH-I500 using XDA Premium App
Cool. I was hoping i hadn't screwed something up again, lol.
Sent from my SCH-I500 using Tapatalk
Hi. I had a similar (I think) problem. I had CWM 2.5.1, and was getting a date of 2000-1-1 on repeated attempts to backup. Tried 3.0.2.8, but the backup image failed immediately. Someone replied to a post I made and said that he had the same problem, which was fixed by enabling voodo. I assumed that meant I had to flash a voodo kernel in order to enable voodo. So, knowing that I probably want to flash Evil Fascination, I flashed imnuts' 531 -100uv voodo kernel and booted into recovery. Wasn't expecting what i saw - Yellow CWM 3.2.0.0. Different. Ran a buckup, and...Success! Checked the clockworkmod folder on SD, and there is a backup file with the correct date.
I was evidently getting the date error. Looked in my sd and there were at least 4 folders labeled as you mentioned. I'm on otb1.6 now, as i couldn't get the voltage control app to work on pbj -50. I'm currently on cwm red and doing valid nandroids as well. I've been running stable at 1.4ghz on demand setting. Got a 1917 quadrant this morning. Finally happy. Doing little visual tweaks now.
Sent from my SCH-I500 using Tapatalk
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.
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
major problem.
i flashed team perfection objection ics rom. felt that i wanted to go back to stock and thats when the problem showed up.
i havent flashed any other custom rom before the objection ics. i came from stock rooted telus.
tried flashing the tar file from this thread
[STOCK][ODIN][GB][Telus] For those who wish to revert to stock Telus
http://forum.xda-developers.com/showthread.php?p=27508953#post27508953
- sometimes odin freezes but when it doesnt and actually finishes flashing, phone wouldnt start up after the automatic reboot. (how long should i wait for the initial boot to start? i wait for about 2-3 minutes of nothing but black screen before resetting)
i tried flashing the backup files from this thread
[ROOT]For TELUS Note (i717D) - No Flash Counter
http://forum.xda-developers.com/showthread.php?t=1585440&highlight=telus+rooted+system
- after flashing, boots but gets stuck at the "touch the android screen to begin"
anybody have an idea whats going on?
tried 2 different stock tar files through odin and i cant get any of them to work.
i flashed back to the objection rom through cwm to make sure that my phone isnt bricked or anything. seems to be working fine. havent tried any other custom roms though.
any help would be appreciated.
thanks
Hi you may have a partition that is corrapted or there may be something wrong with that telus Odin flash. Go to dev section. There is another Odin flash for telus. It is a stock telus rom rooted that is flashed through Odin. It does work, I hav e used: t before. I will send you a link when I get home from work.
Sent from my SAMSUNG-SGH-I717 using xda premium
I use to have a telus note now I have a rogers note. I may still have a back up of a telus rom. Will check my computure when I get home
Sent from my SAMSUNG-SGH-I717 using xda premium
I may have found your problem. When using Odin, and flashing a backup file, it does not format your phone partitions. So you first have to go into cwm and do a factory wipe, wipe dalvik and go into advance and wipe the other dalvik . Do a battery pull, and now put your phone into download for Odin. I have telus kernel, telus modem and telus stock recovery that can be flashed in cwm. Just not sure if I have the stock from still. Pm me if you have any questions
Sent from my SAMSUNG-SGH-I717 using xda premium
Just a update wipe data, wipe cache and wipe dalvik cache before you use Odin to flash a rom. I told you partly wrong in precise post
Sent from my SAMSUNG-SGH-I717 using xda premium
thanks for the help guys
thanks for the help guys.
i dont know if its a partition problem though but it really got me worried.
for some reason i got it to flash properly and it booted up with no problems.
now im thinking thats its the odin software that was causing the problems. the first one that i used to root my phone a couple of weeks back had an "evo 4g" title at the top. it didnt gave me any problems back then so i ignored it. and thats the same one ive been busting to use last night to flash back to stock. anyhow, i tried using a different odin3 that has "android+slp" label on it and i noticed that it was freezing less and actually finishes the flashing but the bootup still has some problems. i get stuck at the bootup logo for a couple of tries. after sometime i just flashed it over and over again until i hit the jackpot.
is there anyway that i can check if my partitions are still broken? im thinking that i wont be doing any flashing until the update comes in july. the ics roms arent stable enough for me anyway.
oh what do i do if wanna get the official ics update? i have stock system, i think, but its rooted. do i just flash stock kernel and unroot it?
i found an article in lockermikedotcom that allows you to unroot using a batchfile. i was wondering if you guys can point me in the right direction. thanks
If you have a stock rom but it is rooted, flashing a stock kernel usually does not remove root. You would have to install stock recovery first and then you adb to remove the superuser and busbox files from your phone to get it totally stock like it was before you rooted it. This batch file DooMLord_v1_unrooting_zip will unroot your phone .It work on the Rogers Note anyways. http://www.mediafire.com/download.php?7ysrb3v7tfu9t1a