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
Related
So i rooted my phone and installed clockwork rom manager and downloaded nero v3_voodoo.zip and put it on my phone..boot into recovery mode and now i get
--Installing: SDCARD:/Nero_3_voodoo.zip
Finding update package...
Opening update package...
Installing update...
and it stays like this for hours.
Thank You
Which rom/ version are you coming from? Can you boot up normally, not in recovery?
Sent from my SGH-T959 using XDA App
you rebooted into ClockWorkMod Recovery, right?
@Fearless yes.
@jrod from stock and yes i can boot up phone and it works normally it just doesn't flash the new rom
Weird
I want to say that I had this problem @ one point. I think I downloaded a new copy of the ROM. Sometimes the download get corrupted at one point or another. Have you hit boards.teamwhiskey.com? or head to the IRC chat channel? they have a GREAT support community.
I really hope you ran a titanium backup, or else you will loose all apps. I really suggest springing for the paid version, because the restore is only one click.
ok...try re-downloading the ROM again and see if that works
@led Thank You!
@fearless
Downloaded update.zip to root phone did that blah installed clockwork mod app granted superuser always, clicked flash clockwork did that, copied nerov3 onto sd card opened clockwork selected reboot into clockwork recovery once in recovery i selected the zip i wanted to update to which was nerov3voodo.zip clicked yes and it finds and opens it fine just soon as it hits installing it gets hung up for a long time hours so i just pull out the battery and boot back up to normal android with root
Im not 100% positive if this is required or not but when I flash a rom I always start from stock rom, then use samsung mini kies to update to Ji6, then flash the rom of ur choice. I did nero v3 that way too.
Sent from my SGH-T959 using XDA App
I did the same as jrod after a soft brick recently....
mac
is there kies mini for osx?
Ur gonna have to research a lil cuz it wasn't easy to find, at least for me it wasn't lol and im not sure if there is kies for osx. Again im not sure if this routine will fix ur problem I just know it never fails for me. The one time I did flash straight from stock rom, it was a different rom (not nero) and it worked but it seemed real buggy. I say this cuz I flashed the same rom twice, once from stock JFD and once from JI6. Coming from JI6 seemed much smoother
Sent from my SGH-T959 using XDA App
cgol92 said:
Downloaded update.zip to root phone did that blah installed clockwork mod app granted superuser always, clicked flash clockwork did that, copied nerov3 onto sd card
Click to expand...
Click to collapse
Wait a minute, the way I'm reading this Nerov3 was on the SD card and not the root of the phone?
If that's the case both update.zip and nerov3.zip have to be on the 16g root memory of the phone, not the SD card.
I can't install the ROM. I keep getting an error. It says:
E: Failure at line 12:
copy_dir PACKAGE:data DATA:
Installation aborted.
Any ideas why???
bLaZe412 said:
I can't install the ROM. I keep getting an error. It says:
E: Failure at line 12:
copy_dir PACKAGE:data DATA:
Installation aborted.
Any ideas why???
Click to expand...
Click to collapse
Let's back up blaze. We need the who what where when and why before we can help you.
Sent from my SGH-T959 using XDA App
jrod33084 said:
Let's back up blaze. We need the who what where when and why before we can help you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Haha aite. Ima fill u in. But it might be a difficult to follow, lol:
1) I began by installing the custom ROM "[ROM] Vibrant AOSP ish JK2 1.1 Official FROYO". I had done the back-ups with Clockwork Mod and whatnot. And I also installed the BusyBox.
2) So I successfully installed the custom ROM. However, I read that there was an issue with SD Card's not working??? So I found the .zip file that fixes it and I put it on my SD Card. I then launch into Clockwork Mod, but it freezes on the Vibrant screen. It just boot loops. So I guessed I bricked it.
3) I try numerous times to ODIN it back to stock. It somewhat worked. However, after the Galaxy S screen, it just turns black and nothing loads. Like the interface doesn't show up.
4) I then restore it to a previous state through Recovery. But now, the SD card issue is still present. Like, I can't update/download any apps.
5) I find NERO v3 and I put it on my SD Card. I boot into recovery, and try to install it through there.
6) As I try to install it I get that,
"E: Failure at line 12:
copy_dir PACKAGE:data DATA:
Installation aborted." message.
IF ANYONE CAN PLEASE HELP ME, IT WOULD BE GREAT!!!! Lol.
Hi guys so i planned to upgrade my samsung galaxy to custom rom 2.2. i will appreciate if someone can please tell me that which is the best and stable custom rom for Tmobile Samsung Galaxy S Vibrant (US) Version. i heard that Nero v3 with voodoo lagfix is the best so far. Please correct me if i am wrong. Thanks
bLaZe412 said:
Haha aite. Ima fill u in. But it might be a difficult to follow, lol:
1) I began by installing the custom ROM "[ROM] Vibrant AOSP ish JK2 1.1 Official FROYO". I had done the back-ups with Clockwork Mod and whatnot. And I also installed the BusyBox.
2) So I successfully installed the custom ROM. However, I read that there was an issue with SD Card's not working??? So I found the .zip file that fixes it and I put it on my SD Card. I then launch into Clockwork Mod, but it freezes on the Vibrant screen. It just boot loops. So I guessed I bricked it.
3) I try numerous times to ODIN it back to stock. It somewhat worked. However, after the Galaxy S screen, it just turns black and nothing loads. Like the interface doesn't show up.
4) I then restore it to a previous state through Recovery. But now, the SD card issue is still present. Like, I can't update/download any apps.
5) I find NERO v3 and I put it on my SD Card. I boot into recovery, and try to install it through there.
6) As I try to install it I get that,
"E: Failure at line 12:
copy_dir PACKAGE:data DATA:
Installation aborted." message.
IF ANYONE CAN PLEASE HELP ME, IT WOULD BE GREAT!!!! Lol.
Click to expand...
Click to collapse
Ok ur right that was alot to follow lol. Ur gonna have to start all over and odin back to stock. Make sure you have both the right ....512.pit file that goes next to the PIT selection in odin , obviously. And the ....jfd.tar file that goes in the pda selection. Check the repartition box also. Let odin and the phone do its thing. It usually will sit on the galaxy s screen for a couple minutes. Did you have any lag fixes installed? If so I hope you disabled them first
Sent from my SGH-T959 using XDA App
adiprince1 said:
Hi guys so i planned to upgrade my samsung galaxy to custom rom 2.2. i will appreciate if someone can please tell me that which is the best and stable custom rom for Tmobile Samsung Galaxy S Vibrant (US) Version. i heard that Nero v3 with voodoo lagfix is the best so far. Please correct me if i am wrong. Thanks
Click to expand...
Click to collapse
Depends what ur looking for. The newest and reputable ones are nero v3 and axura 2.2.5.7. Nero is a lil more stable but not by much. Axura is a lil more snappier/faster but also not by much. Both are themed specifically to the makers choice so its ur call which to go with. Without customizing anything I like neros theme better but after I flashed blackfroyo to axura I loved it. Also it seems that nero is more customizable but that could be cuz axura just came out a few days ago. So its ur call. Try em both out. I did. Give one a couple days then the other so you can really wee the positives and negatives. DONT forget to disable voodoo if you try multiple roms
Sent from my SGH-T959 using XDA App
jrod33084 said:
Ok ur right that was alot to follow lol. Ur gonna have to start all over and odin back to stock. Make sure you have both the right ....512.pit file that goes next to the PIT selection in odin , obviously. And the ....jfd.tar file that goes in the pda selection. Check the repartition box also. Let odin and the phone do its thing. It usually will sit on the galaxy s screen for a couple minutes. Did you have any lag fixes installed? If so I hope you disabled them first
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I have the *True Stock* files for ODIN. I can get ODIN to do its job, but it doesn't load anything after the Galaxy S screen. Hmmm....perhaps it is the lag switch. How do I disable it?
bLaZe412 said:
Yeah, I have the *True Stock* files for ODIN. I can get ODIN to do its job, but it doesn't load anything after the Galaxy S screen. Hmmm....perhaps it is the lag switch. How do I disable it?
Click to expand...
Click to collapse
You have to disable the lag fix before you start flashing. Which lag fix do you have?
Sent from my SGH-T959 using XDA App
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
diceburna said:
Just updated flashed my phone to Axura 2.3.1.2 and for some odd reason the boot animation keeps rebooting. I've disabled voodoo lag fix and I am still experiencing the same problem. :-?
Previous rom was axura 2.2.1 froyo rom for eclair
Click to expand...
Click to collapse
Which rom specifically?
Also you shouldnt have to disable voodoo if you are coming from another voodoo rom.
have you tried reflashing the rom?
I got the same prob. Try to get back to stock T959UVJFD using odin and reflash.
Axura is nice but it shows many compatible troubles when trying with different kernels/mod.
I tried reflashing several times but no luck so far. And the previous rom I was using was the froyo rom for eclair the download zip file name is AXURA22VE...I'm thinkin I should probably have ODIN to stock Eclair, then update my phone to stock froyo before flashing this rom.
dont bother with stock froyo just odin to jfd then root install cwm and flash the rom
going to stock froyo includes the updated 3e recovery which can be circumvented but requires extra work on your part.
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
diceburna said:
Thx shreddintyres :-D
You know I forgot to state this earlier but I can get to recovery mode (cwm v2.5.1.3 red lettering not green) should I just do a backup and restore from there?!?! I am not sure if the axura 2.3.1.2 file I have is corrupt or is it something I am doing wrong on my end when flashing the rom?
Click to expand...
Click to collapse
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
nomadrider123 said:
Sounds like a bad download to me. I would redownload it. I flash in the red cwm all the time.
Click to expand...
Click to collapse
same here
@op when did you download axura 2312? the D4A server went down a couple days ago and we are trying to restore all the files on the new site.
Redownloading 2312 will be not be possible at this point in time, i have posted a download for 2310 in the Axura development thread until the site is fully functional again. there isnt a very large difference between 2310 and 2312.
if you are still able to add files to your phone i would try to flash from CWM first otherwise if you cant jfd will be your only choice.
Hope this Helps
Thx guys I'm in the process of recovering from cwm now, tbh I haven't used ODIN before so before I try it hopefully my nandroid backup will restore everything. I downloaded the 2.3.1.2 rom I believe the day it came out.
the downloads on the d4a webiste are back up for the vibrant rom
http://devsforandroid.com/index.php?topic=23.0
Sweet I just finished dl'ing 2.3.1.3 hopefully it all works out. BTW I was able to easily restore my backup...flashin new rom now will update soon.
thanx men that really helps
All is well :-D I guess the old file I had was corrupted bc I flashed this rom w/ no problems at all...Thx
I'm not new to rooting, i used to have a rooted Evo. But all this DL09, EB01, stuff for the fascinate is getting confusing.
When i rooted my fascinate the first time i flashed a DL30 rom and my phone semi-bricked, it just hung at the samsung logo (i think the problem was i had the DL09 modem???). I had orange CWM but to get into it i had to go through stock blue recovery and apply update.zip every time. after i flashed the DL30 rom blue recovery wouldnt flash the update.zip, it said validation failed.
So i used odin to flash DJ01 stock, then the EB01 all in one root/recovery/SC 2.9, and then i flashed the red CWM-all. I no longer have blue recovery at all, which i think is good.
But now my problem is im afraid to flash a new rom. Since i no longer have to go through blue recovery to get to CWM i should be ok to flash anything right? If i mess it up so bad that it wont boot into the OS i should still be able to get into recovery and restore my backup regardless of what i flash through CWM right?
Also, on a related note. I have a theme for EB01 that i like (Im on SC 2.9 now). if i flash SC 2.9.2, then a new kernel, will my theme that worked on SC 2.9 still work on 2.9.2?
What I recommend is starting off getting an EB01 base.
Start here:
http://forum.xda-developers.com/showthread.php?t=1029436
After you Odin stock EB01/repartition, new recovery, radio, kernel of your choosing (make sure to enable voodoo lagfix if choosing a voodoo kernel)
For a rom I would download the debloated EC01 Rom here:
http://forum.xda-developers.com/showthread.php?t=1035420
From there flash a theme of your choosing, make sure to wipe cache/Dalvik before installing a new theme.
Just make sure to reboot after everything flash.
Follow the steps in the links I provided.
Fyi, EC01 is the newest. Also you can also wait till Monday as its rumored that Froyo will finally be released. From my reading it could most likely happen next week.
Hymizzle said:
What I recommend is starting off getting an EB01 base.
Start here:
http://forum.xda-developers.com/showthread.php?t=1029436
After you Odin stock EB01/repartition, new recovery, radio, kernel of your choosing (make sure to enable voodoo lagfix if choosing a voodoo kernel)
For a rom I would download the debloated EC01 Rom here:
http://forum.xda-developers.com/showthread.php?t=1035420
From there flash a theme of your choosing, make sure to wipe cache/Dalvik before installing a new theme.
Just make sure to reboot after everything flash.
Follow the steps in the links I provided.
Click to expand...
Click to collapse
That is not the question i asked. Im asking if its safe to flash any rom/kernel/theme now that i have red CWM. When i had orange CWM and had to go through blue recovery to get to it i hosed my system partition, couldnt get to CWM, and had to flash back to stock through odin.
So just to clarify. Is it safe to flash whatever i want now that i have red CWM?
Yes you should be ok. I flashed over twenty different themes thru CWM red. Just don't forget to wipe before.
holy cow
10 chars
ghostt021 said:
Yes you should be ok. I flashed over twenty different themes thru CWM red. Just don't forget to wipe before.
Click to expand...
Click to collapse
Super clean 2.9.2 comavolt w/Alien Black theme
Flashing THemes
I've downloaded two files....
One is a theme zip file
Two is an applications zip file, associated with the theme.
When I attempt to flash them using CW, it only shows the ROM files, as options to flash...
Help !!
Badger51 said:
I've downloaded two files....
One is a theme zip file
Two is an applications zip file, associated with the theme.
When I attempt to flash them using CW, it only shows the ROM files, as options to flash...
Help !!
Click to expand...
Click to collapse
How did you download them, to where did you download them?
Theme zip files
I downloaded them to my dropbox folder, on my SD card
I think your a bit rushing thru this. Cool down, a read a bit more, and show a bit more patience. Could you elaborate a little bit more? What theme are you installing, and is it specifically for the Fascinate?
Cooling down
Cooling down is always good advice..
Not sure what you want me to elaborate on...
TheSonicEmerald said:
I think your a bit rushing thru this. Cool down, a read a bit more, and show a bit more patience. Could you elaborate a little bit more? What theme are you installing, and is it specifically for the Fascinate?
Click to expand...
Click to collapse
Just a heads up Sonic. He also posted this question over in the themes section so he may be getting confused trying to switch back and forth and possibly getting different answers between the two threads. Just don't want you to waste your time of giving him the correct advice like you are doing, and have it go for naught.
Ok so I ran Jt's vanilla gingerbread for about week and a half and even tho I loved what I saw the rom was to unstable for me. No fried sd card issues but recovery problems and bootlooping issues. So I odined back to stock ed05(full odin) and after flashing CWR v4 decided to go with powerwash debloated ed05. After and foreclosure issue I did a complete wipe and factory reset and flashed a recovery for the powerwash from the sd card (that I had made right after I had flashed the recovery thru odin) Here's the strange part, the recovery had an error and the phone went into boot up. The bootloop from the vanilla gingerbread rom came up (even tho odined over) and now is stuck in a bootloop again. The same as when I was on vanilla gingerbread. No biggie here as verizon is in the process of replaceing the phone just and F.Y.I. maybe help understand some of the issues with gingerbread. P.S. the bootloop starts as triangle with the android robot then right into the cyanogen logo then starts over.
Wait... You sent your borked phone back to Verizon?!
Sent from my SCH-I500 using XDA Premium App
ghostt021 said:
Ok so I ran Jt's vanilla gingerbread for about week and a half and even tho I loved what I saw the rom was to unstable for me. No fried sd card issues but recovery problems and bootlooping issues. So I odined back to stock ed05(full odin) and after flashing CWR v4 decided to go with powerwash debloated ed05. After and foreclosure issue I did a complete wipe and factory reset and flashed a recovery for the powerwash from the sd card (that I had made right after I had flashed the recovery thru odin) Here's the strange part, the recovery had an error and the phone went into boot up. The bootloop from the vanilla gingerbread rom came up (even tho odined over) and now is stuck in a bootloop again. The same as when I was on vanilla gingerbread. No biggie here as verizon is in the process of replaceing the phone just and F.Y.I. maybe help understand some of the issues with gingerbread. P.S. the bootloop starts as triangle with the android robot then right into the cyanogen logo then starts over.
Click to expand...
Click to collapse
..Did you format your phone with the atlas 2.2 PIT file when returning to ED05?
ccampos784 said:
..Did you format your phone with the atlas 2.2 PIT file when returning to ED05?
Click to expand...
Click to collapse
Yes sir. The more I think about it I'm wondering if maybe somehow something from gingerbread remaining on the sd card even tho I also reformatted when I went back to stock.
Skrazz said:
Wait... You sent your borked phone back to Verizon?!
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Yep. But I flashed it back to stock and did to OTA up date.
You flashed an mtd recovery than flashed a bml rom with mtd recovery. cwm4 should not have even been flashed if you had no intention of flashing an mtd rom.
good day.
chopper the dog said:
You flashed an mtd recovery than flashed a bml rom with mtd recovery. cwm4 should not have even been flashed if you had no intention of flashing an mtd rom.
good day.
Click to expand...
Click to collapse
I thought so too. However the first time odined back to stock and flashed powerwash it had it's own CWR v4 are to two different? They look to same except for the logo (rom manger on gb and a banana on pw)
ghostt021 said:
I thought so too. However the first time odined back to stock and flashed powerwash it had it's own CWR v4 are to two different? They look to same except for the logo (rom manger on gb and a banana on pw)
Click to expand...
Click to collapse
Interesting, I hadn't noticed that. I Odined a full stock tar package with the stock recovery when I came off of VGB. Now on Powerwash CWR shows as v4.0.1.4 with a banana background. I don't see any mention of this in the Powerwashed OP. Any clue what's going on? I may try a full reflash tonight if I get the time. It will distract me from debating whether to go back to VGB.
drnihili said:
Interesting, I hadn't noticed that. I Odined a full stock tar package with the stock recovery when I came off of VGB. Now on Powerwash CWR shows as v4.0.1.4 with a banana background. I don't see any mention of this in the Powerwashed OP. Any clue what's going on? I may try a full reflash tonight if I get the time. It will distract me from debating whether to go back to VGB.
Click to expand...
Click to collapse
Wish I knew. I odined the stock packages three times myself. Once my phone was reading only half of the sd card (nothing thru gallery had to use astro to view pictures) music was fine. So I reformatted the card and Odin the stock package just to be safe. Also I just a error status 7 message in recovery and then a bootlloop. So I odined back to stock using the package with pit file thinking maybe I goofed something. I flashed vgb again with no theme(just in case that was the problem) it ran great for a couple of days, then I pulled my sd card to load some wallpaper onto it from my ps3 and when I placed the card back in the phone same problem nothing could be viewed in gallery even tho phone showed card was present thru setting and under sd card and storage.. When I booted into recovery again I got status 7 error cant' mount recovery followed by the bootloop from hell. So using the odin package I odin back to stock and this time only flashed cwr v4 recovery (that's when I noticed the different logo) I did nothing else I was running debing,debloated Ed05 did a factory reset cause my contacts was dulipating bad from 171 to 829. As soon as I rebooted I got the cyanogen logo followed by the triangle with a "?" bootloop from hell. Not sure what happened again wish I knew
drnihili said:
Now on Powerwash CWR shows as v4.0.1.4 with a banana background.
Click to expand...
Click to collapse
Sounds like that is the 0808 PBJ kernel.
xwhofarted said:
Sounds like that is the 0808 PBJ kernel.
Click to expand...
Click to collapse
That would be my guess about the banana, but I'm a bit confused by the CWM4. Does powerwashed routinely install that?
drnihili said:
That would be my guess about the banana, but I'm a bit confused by the CWM4. Does powerwashed routinely install that?
Click to expand...
Click to collapse
I would assume since the PBJ is the latest kernel out there for Froyo and TW. I wouldnt see why it wouldnt be included.
Hello all, I want to install Clockworkmod on my Samsung Vibrant T959 so I can install a custom ICS ROM. I ran into some problems along the way. I can not seem to install CWM correctly. I had the phone under Froyo 2.2, kernel version 2.6.32.9, and build number froyo.uvkb5. After flashing the recovery by ROM Manager, I would still be stuck at the stock recovery. I have the correct files to download:update.zip. After clicking on "reinstall packages", the recovery said "replacing stock recovery with Clockworkmod recovery". The problem is that after that message, the phone restarts into the stock recovery. I tried it 4 times in a row, but I'm still stuck at the stock recovery. The system keeps saying that it will replace the stock recovery with the CWM recovery, but that did not happen with me. I would keep getting the same message when I click on "re install package". What am I missing that does not allow me to do this? Thanks all.
Are you on 2.1 eclair or 2.2 froyo?
I'm pretty sure you need to be on 2.1 but don't quote me.
Also, I believe there is an issue with the newer versions of ROM manager, recovery mismatch. (Again don't quote)
I haven't had to mess with that stuff in a long time. Either way I'm posting a link that will help you along. If you have any more questions just shoot.
http://forum.xda-developers.com/showthread.php?p=9375927
Paranoid, sitting in a deep sweat...
Thanks for the reply. Like I said in my last post, I am running at Froyo 2.2. I already bricked my phone for failing to downgrade to 2.1. I already rooted my phone, my problem is that I could not install CWM correctly by the stock rom. After the message states that it is replacing the stock rom, my phone goes back to stock with no changes.
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Your positive you dont have a 4g?
Sugartibbs said:
woodrube has some great guides, I use the update.zip method, rom manager didnt like my phone, post if you still have problems and Ill give you more accurate directions on guides.This is probably heresy, but i never could get rom manager, even pro to do what I wanted,and Im sure it was me.
Click to expand...
Click to collapse
You do not understand, I am having the problem that CWM could not install properly. When I chose "install packages" the steps went by and ended with "Replacing stock recovery with CWM recovery". Usually, that would jump straight into CWM recovery after it's installed. That did not happen to me, After installation, my phone restarted and booted back into stock recovery. I tried installing again but I always go back to stock recovery and not Clockworkmod recovery as I planned.
Ive never seen that error message, I know its frustrating, but the t959v 4g comes loaded with Froyo 2.2,the a 2.1 eclair odin will brick it.Just trying to help.
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
Paranoid, sitting in a deep sweat...
---------- Post added at 11:06 PM ---------- Previous post was at 10:44 PM ----------
In the link I sent is the AIO toolbox download. There is a guide how to use it in this link. The DL links are dead in this one so get from previous.
Paranoid, sitting in a deep sweat...
IIRC the update.zip method does not work in Stock 2.2 because of the 2e and 3e recovery mismatch. If you to go to 2.1 Eclair, then you can use the update.zip method and then flash your ROM of choice after that. If you decide to stay on 2.2, you'll have to get the 3e method. It is in the Development section, so you'll just have to search 3e and it should come right up.
All this is provided you have a T959 (3g) and not a T959v (4g). Sorry but lately there have been many 4g users flashing our ROMs and then freaking out.
You can also find a bunch of files in my Repo thread stickied in the Dev section.
samsgun357 said:
Go back to 2.1, uninstall ROM manager, use the update zip in the guide link I posted.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Maybe you'll get it now.
Good luck.
@Woody, thanks buddy.
I linked your repo thread in my previous post.
Edit: well the link isn't in my posts, must not have sent??? But here it is
http://forum.xda-developers.com/showthread.php?p=31279153
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
nfkod said:
The first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
^^ this is not true.
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
naturallight said:
I had a issues with my apps doing the same thing. I had to get busy box and install a older ver 19.2. It corrected the issue. Updating superuser caused my headache
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I have no idea what you are talking about?????
Paranoid, sitting in a deep sweat...
If you have the proper xda version of update zip on your sd...,, theres no need for a kernel flash.
I have the same exact issue as the original poster. 2.2 froyo and all. I even replaced my stock 3e recovery with the modded one, but I get the same issue. Says its flashing CW recovery but it always reboots and comes back with the stock recovery. What exactly are we doing wrong?
Follow steps in this guide, update.zip b is probably best but you need to Odin back to stock first.
http://forum.xda-developers.com/showthread.php?p=9375927
Alright so I managed to get CWM on my 2.2 Stock Vibrant and even got it permanently. What I did was download SGS Kernel Flasher and install it. Then I went the Samsung Vibrant Kernel Bible and found the stock kernel with Voodoo lagfix included that matched my phone (because the kernel has CWM built in) downloaded it, and placed it on the root of my card. Launched the app, backed up my current kernel and then flashed the new one. Everything went smooth and then my phone rebooted and was stuck on the Vibrant screen for 20 minutes. I was pretty sure I messed my phone up. Also it was talking to me which I didn't realize at first, because I was expecting my phone to be talking to me! Finally made out what it said and it said something along the lines of not enough space on the partition, closing... It was hard to understand because it was in a robotic voice. It eventually rebooted and loaded up like normal. Checked the about phone but saw nothing different. So I decided to reboot to recovery just to check and sure enough, CWM 2.5.1.3 comes up, and comes up every time Finally, now to figure out what to do to get on a jellybean ROM
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
samsgun357 said:
When I say Odin to stock that's 2.1 eclair. Voodoo lagfix will cause issues going to a JB ROM.
You don't need to try and re-invent the wheel.
Odin to stock 2.1 eclair JFD.
Put ROM on sdcard
Go to recovery, install update.zip from guide I linked.
Wipe and flash ROM.
It can't get much easier. I am not trying to come off as a ****, only to help you, and avoid future issues.
BTW, I saw your pm, I can't reply because it keeps crashing the app. If you go in and disable voodoo lagfix you should be able to flash PA without issue. It will take 3 flashes. You only need to wipe before the first flash. Wipe cache, dalvik cache, factory/data and format system in mounts and storage. If you get in a boot loop, pull battery then use button combo back to recovery. GB boots are not required.
Click to expand...
Click to collapse
QFT. Just yesterday I ran into the same problem as reported by the OP and a few others. I HAD to downgrade to 2.1 via JFD Odin. Then flash the update.zip. I then just downloaded ROM Manager to get CWM working. However, I did see in some instructions that sometimes even though you know you have CWM installed, it will still default to stock recover. I simply applied the update.zip again and it eventually fixed itself. Not sure what that was about, but I did see it in some instructions, and I experienced it as well.
nfkod said:
the first thing you need to do after obtaining root is flash a kernel. You can't install a rom from re-install packages. That has to be done in a custom recovery, which is built into the kernel. Easiest way to do that is download a kernel and flash it with sgs kernel flasher. I would suggest immortality kernel. After that you can go into the custom recovery and flash your rom of choice.
Click to expand...
Click to collapse
great help dude.i fixed finaly."""""thanks"""""