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
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
i just got my phone running ED01 today and it unrooted my phone. i rerooted it and all that jazz but my question is this...
i can't reboot into cwm recovery?
it just reboots me back into stock recovery.
do i download the latest cwm, rename it to update.zip (not update.zip.zip) and problem solved?
Put a new kernel on your sd card. As soon as you finish rooting, boot immediately into cwr and flash the kernel. If you let the phone boot before you do this, the stock kernel overwrites the recovery.
This happened to me earlier today and had me pulling my hair out. Nemesis2all had the answer.
yes! YES! that was just what i needed.
thank.you.
Ughh. I am having a very similar problem and I have been trying to solve it for the past 4 hours with no luck. Could you please tell me what you did to resolve this?
I was on SC 2.9 with JT's TW voodoo kernel. I decided to go back to stock and start from scratch by flashing the DI01 all in one Odin package in Odin. (I disabled voodoo before doing this). Everything went smooth as butter. I then got the vzw prompt to OTA Froyo. I downloaded and installed it just fine. I then re-rooted. Now I am having a hard time trying to get CWM to flash/install. I flashed 'cwm-recovery-all' in odin. Odin says it was successful and reboots my phone. When I try to boot into recovery, it goes to the blue android 2e screen. I go to 'apply update.zip and thats when I keep getting errors.
"E: failed to verify whole-file signature
E: signature verification failed "
I'm sure I am forgetting a step or missing something
farewell_goodbye2u said:
Ughh. I am having a very similar problem and I have been trying to solve it for the past 4 hours with no luck. Could you please tell me what you did to resolve this?
I was on SC 2.9 with JT's TW voodoo kernel. I decided to go back to stock and start from scratch by flashing the DI01 all in one Odin package in Odin. (I disabled voodoo before doing this). Everything went smooth as butter. I then got the vzw prompt to OTA Froyo. I downloaded and installed it just fine. I then re-rooted. Now I am having a hard time trying to get CWM to flash/install. I flashed 'cwm-recovery-all' in odin. Odin says it was successful and reboots my phone. When I try to boot into recovery, it goes to the blue android 2e screen. I go to 'apply update.zip and thats when I keep getting errors.
"E: failed to verify whole-file signature
E: signature verification failed "
I'm sure I am forgetting a step or missing something
Click to expand...
Click to collapse
First, grab a TW kernel, for example JT's TW voodoo kernel and place it on ur SD card. Next remove battery and enter download mode so u can Odin CWR. Once it's done u should see that it succeeded flashing CWR in Odin. Next reinstall battery and enter recovery mode by holding down both volume buttons and power button. Once u see the samsung logo, release and it should enter red CWR. Then flash the TW kernel and reboot. U should be golden. There's no update.zip file to worry about.
As mentioned on the previous post, the stock kernel overwrites CWR and defaults back to stock blue recovery. Good Luck...
will survive said:
First, grab a TW kernel, for example JT's TW voodoo kernel and place it on ur SD card. Next remove battery and enter download mode so u can Odin CWR. Once it's done u should see that it succeeded flashing CWR in Odin. Next reinstall battery and enter recovery mode by holding down both volume buttons and power button. Once u see the samsung logo, release and it should enter red CWR. Then flash the TW kernel and reboot. U should be golden. There's no update.zip file to worry about.
As mentioned on the previous post, the stock kernel overwrites CWR and defaults back to stock blue recovery. Good Luck...
Click to expand...
Click to collapse
Thank you so much for the help. I will try this now and report back.
Edit: You are a genius! Back up and running and voodoo enabled in 15 mins thanks to you. It was great hearing the voodoo robot voice again. Haha. Thanks again kind sir and everyone here at xda for being such great help in a time of need. Now off to choose a good rom!
Sent from my SCH-I500 using XDA App
farewell_goodbye2u said:
Thank you so much for the help. I will try this now and report back.
Edit: You are a genius! Back up and running and voodoo enabled in 15 mins thanks to you. It was great hearing the voodoo robot voice again. Haha. Thanks again kind sir and everyone here at xda for being such great help in a time of need. Now off to choose a good rom!
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Glad it worked out for u.
As for ROM's, I am currently trying out Evil Fascination v3.3.1. So far loving the rom.
will survive said:
Glad it worked out for u.
As for ROM's, I am currently trying out Evil Fascination v3.3.1. So far loving the rom.
Click to expand...
Click to collapse
that was exactly my problem too but after flashing a custom kernel everything is running smooth. and i'm trying out evil fascination and it is GREAT
djdeaver said:
that was exactly my problem too but after flashing a custom kernel everything is running smooth. and i'm trying out evil fascination and it is GREAT
Click to expand...
Click to collapse
Couldnt agree more. This rom is great. I wouldn't expect anything less from Nitro. Also, I took my phone off the charger an hour and a half ago and im at 99%. I would have been at 87 - 90% before using this new combination.
Edo1 radio
Jts TW voodoo 4/15 kernel
Nitro evil fascination rom.
Sent from my SCH-I500 using XDA App
I am new to this so I need help. Got impatient with verizon a few weeks back and downloaded and flashed my phone with Odin using ED01 build of Froyo for Verizon Samsung Fascinate. Everything was great, the phone was rooted and had CWM Voodoo lagfix recovery 2.5.1.x. Verizon releases Froyo finally and I decided to flash my phone back to Verizon Stock using DL09-leak zip. It loaded fine and starts fine. The only thing is now my phone is stuck with zero memory showing in the internal memory. I can't add apps or do anything. There isn't even enough memory to keep the initial setup setting. I have to enter them each time the phone is powered up. Someone tell me how to fix this problem. There are no apps on the phone above stock apps. I even backed up my SD card and reformatted it to be sure there was nothing on it mucking up the system. Same result.
Had Nandroid backups which when restored had lost apps from previous and also no memory. Can't even download terminal emulator to do command lines, even if I understood them.
It's a voodoo problem. Flash DI01 full Odin package and it will be fixed.
Sent from my SCH-I500 using XDA App
where to find this?
http://forum.xda-developers.com/showthread.php?t=867648
Sent from my SCH-I500 using XDA App
Had the same issue. Used the D101 and fixed. Since then re-rooted and running the cm7 rom and kernels. Kept the d101 in my computer with odin just in case.
Sent from my SCH-I500 using XDA Premium App
You ROCK
thanks to iwasaperson and adrenalyne. You ROCK!!. My phone went back to stock and now is updating to 2.2. Now that I can fix it.... Should have lots of fun!!!!
You're welcome
Sent from my SCH-I500 using XDA App
Allright, so there I was, running a rather stable Comm Rom 2.0 Voodoo Rom with the ED10 Kernel/Radio, and then I saw the thread on the OMFGB GB release, that I, of course, just HAD to have...
So, my first mistake was being impatient and not being able to find any installation notes, and pretending that I knew what I was doing by installing the rom via CWM mod.
Here's the rub, for some reason, whenever I did the 3 finger salute, it would pull a RED CWM that went orange when I applied update.zip ... because if I tried to install rom from sd card with the initial CWM boot, it wouldn't install anything, it would just error out unless I applied update.zip. After selecting apply update from zip, it would boot the orange CWM and allow me to install whatever I wanted...
So after applying the OMFGB rom, it showed the Fascinate/ Cyanogenmod 7 bootscreen, then went to boot loop. I panicked, pulled the battery, then backed up everything to my computer, and formatted the sd card in FAT32 with Windows 7 64 bit...
Shortly thereafter, I was using ODIN and the original "return to stock" files, and ended up getting into the stock OS.
Now I never show 3G or even 1x, and never pull data at all... when I go to place calls, it says that verizon cannot authenticate my phone... when I activate, it reboots and says everything was successful, but was noticeably a faster process than standard activation. Upon reboot, nothing improves... the os is there, everything shows that everything is fine, yet I am still not able to place calls...
Here is where it gets weird... My wife called me today, and the call came through... I received text messages, but still couldn't make calls... My bill is zeroed out, I'm not locked out that I know of, and I just want my phone working again...
Running out of ideas. I have flashed ED01 DL01 and even reapplied the stock .PIT in odin... I am going to try heimdall while I wait for help from here, but any quick help would be GREATLY appreciated...
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I will definately take this into consideration, but first i want to confirm that my phone is in full working order...
I appreciate the quick response, and hope to get some more love from the community.
Sent from my Transformer TF101 using XDA Premium App
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Trying this in about 15 minutes, will report asap...
Again, thanks for help...
Sent from my Transformer TF101 using XDA Premium App
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
martyr2k6 said:
when you say OP of CM7 thread, which one, there seem to be many CM7 threads... link please?
Click to expand...
Click to collapse
also, lets assume I am completely as stock as possible... how should I get CWM on, and which version please link...
Also it miht be worth mentioning, though I think I already did... but when I go to activate my pjone, it says its successful, but then I go to make a call and it say that verizon annot authenticate my phone...
Here's a confusing screenshot...
Sent from my Transformer TF101 using XDA Premium App
Alright the issue is resolved, my main concern was whether or not I could use my phone for phone calls... after finally mustering up the guts to call Verizon, it turned out that the main problem in which I was experiencing was due to some form of typical midnight updates that big red does... apparently, my phone, missed some form of update that ended up de-authorizing my phone, but Verizon was able to help out, even at this late hour.
On the good note, everything went through just fine as far as flashing cm7... I just seem a bit conflicted with which rom is best. I guess its just a matter of personal preference, really. So far I prefer jt's rom just fine, but I might be switching back and forth between jt's and omfgb...
Thanks again for all the help folks, I appreciate it more than you could know.
Sent from my Transformer TF101 using XDA Premium App
xwhofarted said:
sounds like your modem may be messed up
this is what i would do:
1) Odin this it is an "Stock" ED01 DB/DO
http://www.multiupload.com/9JSTWA6Y6L
LET IT BOOT FULLY
2) flash the CWM in the OP of CM7
3) Do all Wipes then Flash CM7 0704
let boot fully
USE the Shutdown menu to get to orangeCWM
4) Do all Wipes then flash CM& 0713
let boot fully
USE the Shutdown menu to get to orangeCWM
5)Flash OMFGB
pull battery & 3 finger salute to redCWM
6) Do all Wipes then re-Flash CM7 0704
reboot and bingo you are at OMFGB
Click to expand...
Click to collapse
Not sure that I totally understand as to why I need to flash cm7 0713, then omfgb, then reflash cm7 0704... seems a bit redundant.
If you could clarify this for me and what improvement this offers, I would appreciate it.
Sent from my Transformer TF101 using XDA Premium App
Because omfgb apparently doesn't convert to mtd but cyan does, so you have to flash cm first
Sent from my SCH-I500 using XDA App
riceje7 said:
I believe the issue is you need to convert your system to mtd before flashing omfgb...some one correct me if I'm wrong though as I don't want to spread false info.
but Try installing jt's 0704 cm7 build following his instructions, then install his 0713 build (possible unnecessary step but it worked for me), then flash omfgb. You will most likely have to flash jt's fixed cwm to subsequently flash his cm7 as I had to since I was coming from a stock restore. And now I'm running a blazing fast omfgb...I was able to restore all my apps and data in half the time it took on com rom...good luck let me know how it goes
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
yup, that was your mistake. prior to flashing omfgb, you need to be on jt's cm7.
I'm too lazy to read all the posts but try flashing cm7 via cwm4. then, Odin back to stock using the right files and configurations. there's a sticky in the development section.
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.