Related
Hello all.
the other day i installed [ROM] VIPERrom v1.0.2. The install went great, just as any other ROM install I've done in the past. Today i wanted to try my luck with quantum but ran into a road block.
every time i boot into manual recovery mode to run the update.zip to access clockwork i get a very weird error i cant seem to figure out. Google really hasn't
been much help either.
When i hit update.zip i get:
E:can't mount sdcard/dev/block/vold/179:1 (no such file on directory)
Then another error saying the E:/update.zip is invalid or something along those lines.
I want to say this might have something to do with file structure change in viperrom maybe? Recovery is still 2e and i always boot to manual.... The phone and ROM still functions fine, i just want to try quantum or go back to baked snacks or another 2.1 variant for battery life....
I have reformatted my sd after backing up to my pc... no dice
Is a possible remedy to try and flash back to stock di18? Or could that cause issues...? what about odin?
for anyone else who happens upon this problem, just flash back to a stock release with odin.
Fixed me right up!
Thanks for the tools devs!
While you can go the Odin route, a simpler method would be to go to CWM recovery, factory reset at least 3x, clear cache at least 3x, and instead of selecting "update.zip" choose "install zip from sd card" then navigate to the ROM you want. Since you are changing ROM's all together it is not an update.
leatherneck6017 said:
While you can go the Odin route, a simpler method would be to go to CWM recovery, factory reset at least 3x, clear cache at least 3x, and instead of selecting "update.zip" choose "install zip from sd card" then navigate to the ROM you want. Since you are changing ROM's all together it is not an update.
Click to expand...
Click to collapse
Thanks... yes, its not an update.zip, its a rom... you need to choose "install zip from sdcard" then "choose zip from sdcard"... glad you got it fixed though
Sent from my Epic [IMPact]
That didn't work for me last night
leatherneck6017 said:
While you can go the Odin route, a simpler method would be to go to CWM recovery, factory reset at least 3x, clear cache at least 3x, and instead of selecting "update.zip" choose "install zip from sd card" then navigate to the ROM you want. Since you are changing ROM's all together it is not an update.
Click to expand...
Click to collapse
Sent from my SPH-D700 using XDA App
i had the same exact problem couple days ago.. and fix it the same way as you hahaha.
One thing i dont understand though guys, yall said we can just install from zip where i do not see that option straight up.
All you see is reboot, apply sdcard update.zip, wipe data and wipe cache. How did yall directly go to install from zip? am i missing something?
Thanks!
I think everyone here is talking about the update.zip from the normal recovery.
For me i always have to hit apply update.zip in normal recovery to get to clockwork unless i use rom manager.
Sounds like you guys are talking about the stock recovery, not clockwork. To be clear, clockwork recovery is loaded by powering on the phone while holding the vol. down and camera buttons at the same time. If you are in the right recovery you will see the option you seek!
Sent from my Epic using XDA App.
thanks all for the replies. i was talking about the stock recovery...
Any time i want into clockwork i do the vol d+camera+power combination.
That take me to manual stock recovery where i load an update.zip to access clockwork....
Stock wouldnt let me load clockwork anymore... Odin fixed it but this raises another question for me....
Do i have clockwork set up correctly? Should the button combo take me straight to clockwork?
Sorry for being a noob guys and thanks for the help!
I'm out and about and can't link it but noobnl posted a redirect fix that let's quickboot and root manager take you straight to clockwork. It bypasses the stock recovery thus no need for the update.zip anymore. I think that's what you need...rom manager is supposed to work with it too I believe.
sent from an Epic4g through the cosmos
UltimateNubs said:
Do i have clockwork set up correctly? Should the button combo take me straight to clockwork?
Click to expand...
Click to collapse
If you have the current version of cw then the three button boot should take you directly to it. Not sure what the problem is, maybe someone more experienced than me will know.
So I have been trollin through a bunch of threads and searching before I ask. I am rooted running Stupidfast v1.23 and jt super clean rom on DI01. I was reading through flashing back to stock package via oden, but i noticed you need a stock nandroid recovery. I currently have CW. Do I need to get the stock nandroid or just flash the package?
If this has been asked a million times, I am sorry. Please direct me where to go.
Anyone?? There has to be an answer out there somewhere...
I believe if you go to the development forum and check the stickies there a post with the Odin to stock info that has the stock nandroid in it. I think that's where it is - I go to so many forums I can never remember where I saw what. I'm on my phone right now but I will check later to make sure.
Sent from my SCH-I500 using XDA App
You don't need a nandroid backup if you just want to go back to stock.
http://forum.xda-developers.com/showthread.php?t=782204
Or, flash adrynalyne's DI01 Odin package to get you back to 2.1-update1.
http://forum.xda-developers.com/showthread.php?t=867648
Stock nandroid is in the dev forum. Probably a few pages in though.
I'm retarded. I meant to say do i need a stock recovery (not stock nandroid) or does the package provide all of it.
A Nandroid backup is just a backup image taken through CW Recovery. You can't have one without the other (at least, not on this phone -- some other devices have different custom recovery tools you can choose to use)
But that doesn't matter anyways, because Odin flashes work regardless of what you have or don't have on your phone. It's like restoring Windows from a recovery disk -- it wipes and replaces everything. That'd be why it's named after a god. Doesn't matter if you're rooted, doesn't matter if you have CWR installed, it'll wipe the slate clean and start you off fresh.
P.S. I'm not sure "trollin" means what you think it means. If you'd gone trolling in a bunch of threads, it's highly unlikely anyone would help you.
Trolls smell bad, live under bridges, and cause hazard to passers thorough. I knew what you meant.
You wanted a stock nandroid recovery. That brings your phone back to before you messed it up. Nandroid is a backup program that is run via Clock Work Recovery (which can be run from recovery mode - to run, flash a special clockwork recovery in odin, install rom manager app, run that, click the install button which in turn downloads and copies an update.zip file to the root of your sd card, then from recovery mode *vol +&- while powering up* you ' install' update.zip which essentially runs it)
You run nandroid from therein... or from the Rom Manager front end.
Actually you would run it, except you cannot.
# Nandroid is a BACKUP program. You need to have made your own image before hand for it to be helpful! #
However, thanks to Adrynalyne, you have another option for restoring your phone to stock:
http://forum.xda-developers.com/showthread.php?t=867648
A caveat. It is a large file, and somewhat of a strain to host. You only need to use it if your phone is totally borked and you do not know what else to do. Otherwise, you can often repair your woes by opening up CWR and using the clear data commands (which do not touch the sd card) & the install from sd card option, which in turn lets you find a rom you previously installed on your sd card and rerun it. Unless of course you installed voodoo, in which case you need a whole other thread before proceeding....
SIDE NOTE: Here its the classic piecewise restore I used back in the day, which includes stock kernel, stock system rom, and Odin:
http://forum.xda-developers.com/showthread.php?t=782204
Unfortunately the only di01 (first vzw updated modem) posted publicly is the one in the first link. If you need to replace your modem/radio/baseband, then you need to find dj05 separately, or simply have used adrynalyne's restore (linked up top) in the first place.
However, when you do get your phone back to happy - my tired finger asks you to do just one thing:
Run the "Backup Current ROM" option the moment you install Rom Manager - or don't install it!
Swyped w/ XDA App. When in doubt, mumble. Nandroid: Don't use Rom Manager without it.
My samsung fascinate has VooDoo on it. I did not put it there, I am not comfortable with ADB shell and the commands that go with it. Its a D101 that HAS to run at 800Mhz with Voodoo (Not the 1.2 the specific voodoo is) at 1.2 nothing runs and constantly redraws the homescreen.
I tried the automatic uninstaller, and the red recovery stays to haunt. I've tried other kernels while disabling Voodoo.
My phone was running fine up until recently where it would have random reboots and have trouble booting back up.
I came across flashing back to stock with ODIN. the system file went over fine, and I even did the stock kernel and (PIT)
i Just flashed them all through ODIN.
The phone boots up fine to the main screen, where then I get the error message about a UID ? (Sounds dirty) it says to wipe data or my phone will have inconsistencies. Then gives me a button that says "feeling lucky"
Message as follows "UIDs on the system are inconsistent, you need to wipe your data partion or your device will be unstable" Only button to click is I'm feeling Lucky
everything force closes, red voodoo still shows up in recovery. What am I missing or doing wrong?
I bought this phone this way and like i said i know NOTHING about ADB or all those commands, etc.
Can somebody help me out? I'd even gladly send it to a trusted member for repair with a donation, of course.. until then I'm using my OLD bb curve
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
make sure you use the pda option in odin and not the phone..aparantly using the phone option can really screw things up
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
BrianWM said:
I did another factory data reset, and my UID message vanished. Although, VooDoo is still in recovery even after flashing D101 through ODIN.
My phone gave me the notification of an update (DL09) It downloaded it, and when it went to install it - it booted right into the red VooDoo recovery.
I'm going to flash DL09 through ODIN now, but I'm thinking VooDoo isn't about to go anywhere.
Click to expand...
Click to collapse
are you disabling voodoo before flashing these new kernels?
Powell730 said:
are you disabling voodoo before flashing these new kernels?
Click to expand...
Click to collapse
Yes, VooDoo is disabled.
BrianWM said:
Yes, VooDoo is disabled.
Click to expand...
Click to collapse
so did you use the odin files and flash it via PDA in odin? if so, did that revert you to total stock? i believe those .md5 files contain the stock recovery.
EDIT:
do you know what version of voodoo you're using?
http://forum.xda-developers.com/showthread.php?t=804784
that guide should help you, if you're using voodoo 5 there is a guide there that specifcally says "if you're still getting the red voodoo menu flash this file then flash a nonvoodoo kernel." check that article out by ady if you havent already.
flash voodoo boot right into recovery. adb shell into the device and type
cat /voodoo/partition_tables/fascinate > /dev/block/mmcblk0
And then reflash everything with Odin.
Also one of adrynalyne's di01 packages doesnt flash recovery. So either flash my dj05 or go to adrynalyne's cwm odin thread and flash a regular update.zip cwm tar.
Sent from my SCH-I500 using XDA App
A proper, 100% full Odin tar will replace everything on the phone, including voodoo, and the partitions that it formatted as ext4 will now be RFS again. Since the full DJ05s and DL09s came out I use it as a first resort instead of a last resort. Flash the full tar, CWM, the kernel, then nandroid and I am good to go in about 15 minutes.
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
ivorycruncher said:
Just to throw my two cents' worth in here, red CWM is not synonymous with Voodoo. It's just the version of Clockworkmod recovery that is capable of working when the lag fix is enabled. It's normally installed with Voodoo kernels, but the Voodoo lagfix itself can be completely disabled, and red CWM will still work just fine. If you got the OTA notification for DL09, it sounds like you have a stock ROM, which means Voodoo is actually gone, so you just need to restore the recovery from red CWM back to stock so that the OTA patch will be able to install properly.
Click to expand...
Click to collapse
Presentation is everything, thanks for the info!
[RED-CWM] (not orange)
Alright sick of scanning 3 different threads trying to help people with the new Clockwork manager I decided to write up this guide. This was tested from stock, I flashed back to stock to test both these methods, and they should work for everyone.
Stock versions tested: DI01 (stock), DJ05 (stock), odin method works flawlessly on these versions. cwm was not replaced by sammy kernel.
Stock DL09 will remove cwm on reboot, install a different kernel adryn's should work, pick your poison here: http://forum.xda-developers.com/showthread.php?t=915709 flashed cwm via odin. install kernel, then rebooted, if you get stock recovery flash via odin one more time.
Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, http://dl.dropbox.com/u/2056318/update.zip on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)
To get to stock use adrynalyne's DI01 package get it here: http://forum.xda-developers.com/showthread.php?t=867648 flash via odin.
First I would like to thank jt1134 for fixing up the new cwm get your perferred version here: http://forum.xda-developers.com/showthread.php?t=942021
Odin method (preferred method stock users do this one!)
1. Alright let’s do this, head over to jt’s original post and download the cwm-recovery-ALL odin:
2. Plug phone into PC and turn off phone
3. Pull battery in phone and then press the down volume button
4. Open odin on PC and press PDA load cwm-recovery-ALL.tar, DON’T MESS WITH ANY OTHER SETTING! Then hit the start button.
5. Boot into recovery (cwm) do this by holding both volume keys plus the power button till you see Samsung screen, you can let go then.
6. Congrats your done now install your custom roms, kernels, radios, and other various things!
Clockwork manager method (only if you have cwm installed already)
1. Copy new cwm-recovery-ALL.zip to root of SD card. (do not need to rename!)
2. Boot into recovery
3. Choose install zip from sdcard
4. Choose cwm-recovery-ALL.zip
5. Reboot your phone and delete update.zip from root of SD card, and recovery-update.zip from clockworkmod folder.
The cwm should be red, and should say voodoo no matter if you have a voodoo kernel or not.
Rom manager will not boot your phone to recovery, install a new shutdown menu that includes boot to recovery or do a manual boot to recovery.
The new clockwork manager installs to the boot partition of the phone that's why you no longer need the update.zip file. Do not flash the cwm from Rom manager, it’s not needed folks, and will put your phone into an endless boot. The cwm jt gave us is customized for our phones.
Post your questions here I will be happy to answer them.
Below I attacked the clockwork manager files, plus odin3 v1.3 but visit jt's OP and give him a thanks, I'm just the translator, hes got plenty of other crap to do rather than test this out.
I am not responsible for any bricked, broken, or abducted phones.
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
vlucchetti said:
Tried it, works fine. Took a bit on that first boot into recovery after the install was run (already had cwm installed), you know that held breathe of "did it work"!
Click to expand...
Click to collapse
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Takafiji said:
just be sure not to flash cwm from rom manager application, or you'll be holding your breath till you black out
Click to expand...
Click to collapse
Seriously thinking of deleting ROM Manager altogether. I did dl Adryn's revised ROM Mgr but may switch to doing everything through cwm.
I think the slight delay after the double samsung flash is the program working through blue in the background so it jumps right to red afterward.
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
lfrench0 said:
Adryn's kernel isn't working for me. But that's what searching is for.
I also owe you a huge thanks for all your help earlier.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
no prob thats what we're here for.
any custom kernel built for dj09 will work. only use a kernel for your raidio/rom version ie: dI01, dj05, dj09, dl30, ebo1 etc...
Hey Takafiji,
I posted a similar thread over at Android Central about the same time as yours here at xda. I discovered this ability to boot directly to red cwm, and I put together the how-to thread and everything was great until I booted to recovery one time and saw stock blue (2e) recovery. I played around with different options, but couldn't completely get rid of blue recovery. I decided to do some research in jt1134's thread and saw the link to yours and read everything here. I have tried every method in your thread and jt1134's thread and I keep running into the same problem. I can install the new cwm just fine and I can keep booting directly into red cwm just fine until.........I flash a new ROM. I can flash themes, patches, add-ons no problem, still able to boot to red cwm. As soon as I flash a new ROM, I boot to stock blue recovery. The only ROM I have been flashing is Adrynalyne's superclean 2.4. I read in jt1134's post that flashing a stock kernel will revert you back to stock blue recovery. The kernel in Adrynalyne's sc 2.4 is the farthest from stock we can currently get in nonvoodoo EB01. My guess is we will not be able to boot directly to the new red cwm on nonvoodoo until the devs get their hands on the source code and we get some custom nonvoodoo kernels. Any thoughts? Thanks
landshark68 said:
Hey Takafiji, Any thoughts? Thanks
Click to expand...
Click to collapse
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Takafiji said:
ummm not sure here, you could try a voodoo kernel, they work wonderfully. how are you rebooting to recovery? rom manager doesn't work all too well in that area, try using the power menu and reboot to recovery that way. i will do some more testing but ive been jumping around on different eb01 roms just fine. Is it all roms or just superclean ones?
Click to expand...
Click to collapse
I got rid of Rom Manager as soon as we got the long press power button menu with recovery in it. The only ways I boot to recovery are long press power and holding volume down, volume up, and power buttons.
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Takafiji said:
ummm have you tried applying a older cwm after booting to blue recovery? maybe if you booted to that then installed jt's new cwm you'd be set. just a thought. http://dl.dropbox.com/u/2056318/update.zip should work, if it comes up unsigned we will have to explore different options. I'm trying to figure out why its going blue with a non-stock kernel, the new cwm installs to the boot partition.
Click to expand...
Click to collapse
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
landshark68 said:
Already tried that if the old cwm you are linking me to is the new red cwm for froyo we had before the current one. Loaded that cwm via ODIN, had new red on base of sd card, installed via old red cwm, no luck, went back to blue as soon as i flashed sc 2.4. The only thing I'm thinking is I don't think the kernel in sc 2.4 is truly a custom kernel. I believe I read the kernel in 2.4 is still the stock kernel, just slightly modified by Adrynalyne. Thanks.
Click to expand...
Click to collapse
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Takafiji said:
have you tried flashing stock di01, then jumping to a stock eb01, maybe that would work. not sure but i know the dl09 recovery overwites cwm. maybe you just got parts of it still stuck there...
Sorry wish i was a c programmer i'd jump on board and start helping create a custom kernel.
Click to expand...
Click to collapse
No problem. I'm just going to keep going through blue recovery to get to red cwm until we get some custom nonvoodoo kernels. I updated my OP to advise everyone there on nonvoodoo to put update.zip back on the root of their sd card and do the same for now. Thanks again for the brainstorming and ideas.
EDIT- Also to let you know, yes I already tried flashing back to DI01 then to EB01. We are definitely thinking along the same lines.
Well now I'm totally gorked up. I followed Zacisblack's method with your addition of doing the ODIN install first. Now when I get blue recovery and hit apply sdcard:update.zip I go to green cwm. Trying to figure out a solution to that now.
EDIT - fixed that problem. Fortunately I still had a copy of the cwm_froyo.tar
I also have the same issue when flashing a new rom. It always goes to blue recovery.What I have to do every time is in blue cwm go to apply sdcard/update.zip which gets me in green cwm. Then I go to choose zip and scroll down to clockwork and choose cwm-recovery-all and flash it again then scroll down to update.zip and flash it then i go to applysdcard/update.zip and flash that then i reboot. Then next time i boot into recovery it always goes straight to red cwm. Sounds like a pain (and sometimes it is) but in reality it only takes like 5 minutes. I wish i didn't have to do that every time i flash a new rom but thats just part of my routine now as its what works for me.
I might not have to do all of those to get back to red but thats the way i originally got red cwm on my phone from a great write up on jt's thread (sorry but don't remember who did the write up). Maybe I'll experiment with just flashing one of those zip's next time i flash a rom to see if there's a faster way.
But I would really like it if there was a way to just always go to red cwm with a new rom instead of going thru all that.
Fantastic tutorial! Just what I was looking for! Thanks a million!!
Thanks Takafiji! I had just installed the Superclean v2.6 non voodoo and got the stock blue (2e) recovery as well. I tried to apply the update.zip and it took me to orange. I read your original post and it worked wonderfully!
Takafiji Quote from OP:
"Nonvoodoo EB01 currently some people report it will boot to blue recovery after installing new roms. nonoodoo users should leave, <drop box link to update.zip> on the root of there sdcard that way after a new install of a rom you can get back to cwm. after applying udate.zip, install cwm-recovery-ALL.zip. (Thanks Landshark68)"
...now, if I could just figure out why Google Voice can't seem to find my contacts, i.e. voice command "Call Mark Davis", nothing found and defaults to looking on the web.
My phone won't even update the app. When I try it d/l's, starts then aborts saying it isn't properly signed. Guess I'll stay with Adrynalyne's modified one for now.
I used ODIN to flash the new-CWM, but it always seems to boot into blue recovery. Using update.zip gets me into green, which seems to work fine for flashing roms. I've occasionally seen red recovery, but when using update.zip takes me right back to green.
Am I doing anything wrong here?
Thanks for the write-up I flashed recovery with ODIN
In read recovery and working great
again THANKS for the writeup
So I got my continuum 3 weeks ago, first Droid phone. Decided to root, took me about 5 hours finally figured it out using SuperOneClick.
Wanted to check out some custom ROM's so I plugged my USB cable in and transfered the .zip file to my sd card and booted into cwr and tried to install the .zip from the sd card and rebooted, nothing was different or had changed. Did that a few times and realized that I hadn't wiped user data or cache or delvik so I did that all in the cwr and installed to .zip rom and rebooted.
This time when I rebooted a few things were different. All of my apps were in alphabetical order, the home screen was back to stock except for my background was one I had just installed. My contacts were gone (thank God I backed them up).
So I rebooted again.... hung at Samsung logo....
I had also put the Peanut Butter Jelly time kernal on my sd card out of luck I installed that and rebooted. This time everything was the same as my previous horror boot except all of my apps that were set to run on boot fc'ed and all of the other apps that I have are just icons. None of them open or they do and fc. Market will not open. My phone is a phone and a camera and the browser works.
I am very new to droid but learn quickly. I cannot post on the continuum dev threads because I am a noob. Hopefully one of the continuum devs will see this and know what to do to help.
Thanks a ton, I do not mind donating for help.
You said that you wiped user data?
That would remove all of your data, including your applications...
Your apps are toast, but your phone is not...
If you made a backup before you flashed (which you are supposed to xP) , then you can easily restore your apps then...
But if you didn't, then go back into recovery and do a full wipe... When you boot up, you should be back to the original state..
If not, then i am going to have to have you flash one of our rom zips... But i really dont think it'll come to that xP
Sent from my SCH-I400 using XDA Premium App
Recovery
I made a backup and when I try to load it it says checking for md5 sums then gives me an error that it can't mount (unmount) the "/system".
So if I go back to recovery and wipe everything and reboot that should return me back to stock??
I don't care about the apps I dled I can always get those back but I can't even open market it fc everytime, no way to re-dl it.
1. what rom have you/are trying to install?
2. how are you installing the rom? you can't just go into cwr and click "apply sdcard:update.zip". you have to go to "install zip from sdcard", then go to "choose zip from sdcard", and then find the rom you put on your sdcard and select it. make sure you're flashing the rom file, not the cwr file because they are both named "update.zip". to make sure you're flashing the right file i would put cwr in the root of your sdcard and the rom file in some random folder.
3. did you install voodoo or novoodoo? and if you correctly installed either, the boot up video should be messed up when you turn on your phone. did you make sure the peanutbutta jelly time kernel was exclusively for the continuum, and you didn't accidently flash a kernel for some other phone?
4. if you truly did install the correct peanutbutta jelly time kernel, i would recommend flashing back to the original kernel (let me know if you need it). if you installed voodoo, you'll need to put a blank file in /sdcard/voodoo/ named "disable-lagfix"
ntien said:
1. what rom have you/are trying to install?
2. how are you installing the rom? you can't just go into cwr and click "apply sdcard:update.zip". you have to go to "install zip from sdcard", then go to "choose zip from sdcard", and then find the rom you put on your sdcard and select it. make sure you're flashing the rom file, not the cwr file because they are both named "update.zip". to make sure you're flashing the right file i would put cwr in the root of your sdcard and the rom file in some random folder.
3. did you install voodoo or novoodoo? and if you correctly installed either, the boot up video should be messed up when you turn on your phone. did you make sure the peanutbutta jelly time kernel was exclusively for the continuum, and you didn't accidently flash a kernel for some other phone?
4. if you truly did install the correct peanutbutta jelly time kernel, i would recommend flashing back to the original kernel (let me know if you need it). if you installed voodoo, you'll need to put a blank file in /sdcard/voodoo/ named "disable-lagfix"
Click to expand...
Click to collapse
1. I was trying to install the super clean
2. I was trying to install from zip on sd card then selecting the sc_cont.zip I believe it is called
3. I had both voodoo and no voodoo, with no voodoo I had no bootani's with voodoo it was the factory bootani but distorted.
4. I just tried the original kernal and system from http://forum.xda-developers.com/showthread.php?t=967165 and now my phone's bootani is stock stock but after the verizon screen my phone turns off.
So now my phone is bricked again. I tried going back to pbj (peanut butta jelly) voodoo kernal and the same distorted bootani comes up then the phone turns off. I can get into crm but that appears to be all I can do.
Is there a different place to get the stock kernal or is the link I posted the right one.
I would really like my phone back to stock and root again. But first things first... get it to boot to a phone.
Forgot something, when I attempt to boot into crm the lady comes on and says "Convert system partition, system is not available" Then it sits and the weird lines from voodoo and the bootani from voodoo. If i could get into "phone" I could create the file you are saying but the phone turns off after that. Back to boot like a loop.
Instead of creating a super large thread, how about you just hop into the IRC, and i will try my best... i have a couple ideas to try...
#Samsung-Continuum
http://webchat.freenode.net/
Thank you so much to trail blazer
Basically I had the wrong update.zip installed and couldnt even mount the usb to cpu to do anything about it. Luckily i had a msd to sd adapter and was able to switch out my update.zip to the correct cwm. Thank you so much blazer and imnuts!!! you guys are my heroes.