I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
rmp5s said:
I flashed the DoW rom/kernal using clockworkmod on my vibrant and it gets to the boot screen (the screen with tw in brackets and an atom cloud) and just hangs. Anyone know what's goin on?
Click to expand...
Click to collapse
As far as I know DoW is a kernal not a rom. Make sure it will work with whatever your current rom is. Working great flashed over nero5.
I would odin back to stock, flash custom froyo rom then kernal....
By chance did you have lag fix disabled?......works fine with nero 4.1 and 5 for me.....but I found nerov5 works great without it
Sent from my SGH-T959 using XDA App
K5C5S5 said:
I would odin back to stock, flash custom froyo rom then kernal....
Click to expand...
Click to collapse
+1
Also remember that not all phones will handle the oc'd kernels
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
I'm currently running Bionix oc/uv and love it.
I DID undo the lagfix before flashing this.
If I could get a link to the stock odin files to flash so I could give the amazing sounding DoW a shot, I'm sure I could get it working.
Im running DoW 1.3 on AxuraJL5, and it does the same thing. i often have to pull the battery for a successful reboot. its sucks, but ive learned to live with it
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
funeralthirst said:
if you can get into recovery, you can try flashing a different kernel or reflashing your rom.
Click to expand...
Click to collapse
With all due respect, if I could get into recovery, I wouldn't be posting this...
I made a fresh Nandroid before trying this but I can't get to recovery or anything.
brandonkahn said:
wrong section to post this in, not to be a drag but its just that these forums can get clogged up with stuff like this if we dont keep posts in order. Q&A or under the DoW thread would suffice.
Click to expand...
Click to collapse
I understand. If a mod moves it, it's all good. Just looking for help...my phone is sitting stuck at the atomic bomb screen still. It's been 2 hrs...just lookin for a hand. :-D Thanks!
have you tried getting it into download mode? i know you said you cant get into recov. but download mode is different.
first, do you know how to get into download mode?
well in short if you dont, when ur phone hangs.. pull the battery. with the bat. out hook it up to ur comp with odin running... as ur holding down the vol. up and down buttons stick in the batt. then you will be in download mode. then flash back to JFD
Maybe im wrong but isn't the dow kernel for 2.2. Didn't he say he was on bionix and isn't that a 2.1?
Powered by Axura with a dash of Voodoo
you are correct, i missed that he stated he was using bionix. OP there is your problem, you flash a 2.2 kernel with a 2.1 rom. flash back to stock via my instructions and you willl be fine.
you will need this http://forum.xda-developers.com/showthread.php?t=734475
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
GreggoryD502 said:
Glad we got that taken care of.before he hard bricked his phone.
Powered by Axura with a dash of Voodoo
Click to expand...
Click to collapse
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
rmp5s said:
lol...I did this with my wife's phone...no boot and no recovery is very disheartening to say the least. lol
So...I flash back to stock using the thread provided and then flash DoW?
Click to expand...
Click to collapse
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
DoW works with any Nero (2.2) Team Whiskey Rom. You have to disable Vodoo LF before flashing, otherwise you will get stuck in a boot loop. Make sure to let the Rom run for a few minutes after flashing before replacing the kernal. You can always pull a logcat to see what your phone is doing when it hangs.
brandonkahn said:
after you flash back to stock you of course are going to want to root your phone again, then youre going to want to go to team whiskey and download Nero... a 2.2 rom that works with the kernel. then you will want to flash DoW. I would also consider downloading setcpu because that kernel will drain the heck out of your bat. make sure you dont set to boot with setcpu, and just use the conservative setting.
team whiskey http://teamwhiskey.com/DownVibrant.html
again make sure its a 2.2 rom.
Click to expand...
Click to collapse
Very fist, I wanna say thanks a million to all the replies and help. :-D
Ok...now...to set the record straight, my phone just tries to boot to the DoW and does nothing after. It just hangs.
Yes. I was running a 2.1 rom (Bionix) with a 1.2ghz oc, the uv kernal and the voodoo lagfix (which WAS DISABLED before flashing) but I thought I did everything right. If I had known that switching from a 2.1 rom to a 2.2 rom would have been this much more involved than I thought, I might have reconsidered...lol
I did a Nandroid backup using clockworkmod prior to doing anything else. I got to the red recovery (not 100% sure how I did it, to be honest) and tried to flash my backup and it didn't work.
I'm going to try the previous post about flashing back to stock, then doing the DoW flash but that's kind of a last resort. I'd like to not wipe my data, nandroid, etc before flashing but it's kinda whatever at this point since my phone doesn't work at all right now...lol
Thanks once again all of you!!! This is what makes Android what it is.
Related
I noticed something since i updated to JI6 while using Clockwork recovery. while on JFD i was able to do a backup using the following steps:
HOW TO MAKE A NANDROID BACKUP *ALWAYS BACKUP BEFORE YOU FLASH A NEW ROM
1 - Open Rom Manager
2 - Click on Flash Clockwork Recovery (you can skip this if you have already flashed the recovery before)
3 - Click on "Reboot Into Recovery"
4 - At the prompt, click "ok" to reboot into ClockworkMod Recovery
5 - If this is your first time, you may be at the stock recovery on the Vibrant. Thats normal. Click on "reinstall packages" (ALSO: Volume up and down navigate, and power is used to select an item).
6 - Now, you are at ClockworkMod's Recovery. Scroll down (volume down), to "Nandroid" and select it (power button).
7 - Click on Backup. It will run it's course. After it finishes just reboot.
8 - You now have something you can always fall back on in case you F up. Thank Koush and all the testers.
Now when i tried to do a backup on JI6 i no longer see Nandriod option all i see is "backup and restore". is this normal? has anyone else noticed this? will impact the backup/restore process?
That might not be a JI6 thing. Koush just updated rom manager. Thats most likely the reason.
jdkackley said:
That might not be a JI6 thing. Koush just updated rom manager. Thats most likely the reason.
Click to expand...
Click to collapse
how do i get the update?
open ROM Manager and tell me what version of clockwork recovery you have. Its up at the top.
jdkackley said:
open ROM Manager and tell me what version of clockwork recovery you have. Its up at the top.
Click to expand...
Click to collapse
clockworkmod 2.5.1.2
when i select "check for rom updates" it says that i am not set for OTA and i need to contact dev.
Your all good bro! Thats the same version Im running and I just checked, I dont have NANDROID anymore either. That was all part of the recent update I guess.
As for the second question, ROM updates is talking about the actual ROM the phone runs off of, You know like ECLAIR 2.1, or Eugenes or Sombionix's roms. Not the ROM manager APP. The APP will let you know when it needs to be updated, it checks what version you are running versus what the latest version availible is everytime you open it.
jdkackley said:
Your all good bro! Thats the same version Im running and I just checked, I dont have NANDROID anymore either. That was all part of the recent update I guess.
As for the second question, ROM updates is talking about the actual ROM the phone runs off of, You know like ECLAIR 2.1, or Eugenes or Sombionix's roms. Not the ROM manager APP. The APP will let you know when it needs to be updated, it checks what version you are running versus what the latest version availible is everytime you open it.
Click to expand...
Click to collapse
what about flashing to a old clockworkmod? or is there no need to? i just want to make sure that when i backup i will not have any issues if i need to restore..
one more Q. any particular way to name the backups? i know there is not that much room to be specific with the name.
adinis78 said:
what about flashing to a old clockworkmod? or is there no need to? i just want to make sure that when i backup i will not have any issues if i need to restore..
one more Q. any particular way to name the backups? i know there is not that much room to be specific with the name.
Click to expand...
Click to collapse
well answer my own question, i reflashed clockwork to 2.5.1.1 & 2.5.1.0 and the nandroid option still does not come up only "backup & restore"....
anyone on the best way to name your backups? not that much room to be specific.
if you choose to back up from ROM manager you can name it whatever you want. Just go into Rom manager, tap backup current rom, when the little box pops up click it and change the name to whatever you want. It will automatically boot into clockwork mod and take care of the back up for you. let it finish, patience is critical whenever flashing anything or backing anything up. And your done. You will now have a complete backup you can use when the going gets tough. Are you running a stock vibrant?
jdkackley said:
if you choose to back up from ROM manager you can name it whatever you want. Just go into Rom manager, tap backup current rom, when the little box pops up click it and change the name to whatever you want. It will automatically boot into clockwork mod and take care of the back up for you. let it finish, patience is critical whenever flashing anything or backing anything up. And your done. You will now have a complete backup you can use when the going gets tough. Are you running a stock vibrant?
Click to expand...
Click to collapse
as my signature states lol!!!! :
T959UVJI6 (Updated 10/13/10)
ClockWorkMod 2.5.1.2
OneClickLagFix
Titanium Backup
nothing much more done to it...... so far at least, i might want to try the following:
bionix 1.9.1 w/stock kernel
bionix 1.9.1 w/kingklick OC/UV kernel
bionix 1.9.1 w/Jacs OC/UV kernel
bionix 1.9.1 w/Jacs OC/UV/VOODOO kernel
not sure which one to try as i have the oneclicklagfix and dont want anything to get screwed up cause reflashing and getting the phone back to what i had it is a pain, lol!!!!!
adinis78 said:
as my signature states lol!!!! :
T959UVJI6 (Updated 10/13/10)
ClockWorkMod 2.5.1.2
OneClickLagFix
Titanium Backup
nothing much more done to it...... so far at least, i might want to try the following:
bionix 1.9.1 w/stock kernel
bionix 1.9.1 w/kingklick OC/UV kernel
bionix 1.9.1 w/Jacs OC/UV kernel
bionix 1.9.1 w/Jacs OC/UV/VOODOO kernel
not sure which one to try as i have the oneclicklagfix and dont want anything to get screwed up cause reflashing and getting the phone back to what i had it is a pain, lol!!!!!
Click to expand...
Click to collapse
Dont worry, you wont screw anything up, all four of those choices wipe everything and flash a kernel. My suggestion is to flash bionix1.9.1 with JAC's OC/UV kernal. its pretty sweet. Stay away from voodoo right now. No offense, but your not ready yet. VOODOO really can F*%k your stuff up if you dont disable it before flashing other stuff. Trust me, once you start flashing you will never be happy! LOL Thats how i started.
The best thing you can do is read read read. Then when you think your ready, READ some more. If you ever need help feel free to pm me. Im always on. Sorry I didnt even look at your sig. And HAPPY FLASHING BRO!
jdkackley said:
Dont worry, you wont screw anything up, all four of those choices wipe everything and flash a kernel. My suggestion is to flash bionix1.9.1 with JAC's OC/UV kernal. its pretty sweet. Stay away from voodoo right now. No offense, but your not ready yet. VOODOO really can F*%k your stuff up if you dont disable it before flashing other stuff. Trust me, once you start flashing you will never be happy! LOL Thats how i started.
The best thing you can do is read read read. Then when you think your ready, READ some more. If you ever need help feel free to pm me. Im always on. Sorry I didnt even look at your sig. And HAPPY FLASHING BRO!
Click to expand...
Click to collapse
so if i flash bionix 1.9.1 w/Jacs OC/UV kernel, i can go back to what i have now after i back it up? and could i use oneclicklagfix with it? any diff from voodoo to oneclick? and i am sure i need to disable oneclick before i flash.
adinis78 said:
so if i flash bionix 1.9.1 w/Jacs OC/UV kernel, i can go back to what i have now after i back it up? and could i use oneclicklagfix with it? any diff from voodoo to oneclick? and i am sure i need to disable oneclick before i flash.
Click to expand...
Click to collapse
No need to disable lagfix it will get wiped and reformatted. However I did see a way to do it, but i dont use them so i dont know how its done. The whole point of backing up is so you can get back to where you were in case something goes wrong or yu dont like what you see. As far as one click lag fix (OCLF) and voodoo go, its like night and day. VOODOO is INSANELY fast. ALL THE TIME. but they are truely different approaches at the same goal. But for now i reccomend you stay away from voodoo.
Have you read this?
https://sites.google.com/site/projectbionix/installation-guide
jdkackley said:
Have you read this?
https://sites.google.com/site/projectbionix/installation-guide
Click to expand...
Click to collapse
not yet but will take a look at it......
thanks for everything...
No problem. Im here to help when i can.
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 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
Hello,
Not sure if this has been brought up before.
I flashed the simply galaxy (gingerbread) rom last night. I come from bionixV 1.2.1.
I have 2 issues right now. I can not see the recovery. When ever I boot into recovery it freezes/hangs
in the vibrant boot logo. I read somewhere that the recovery is behind the boot logo and I can not see it.
I tried the 3 button combo and the rom manager reboot into recovery - I still can not get into recovery
I will appreciate any help.
Also, I installed titanium backup, it installed correctly, but I can not see it in the app drawer.
thanks,
"- Can not see recovery. Use CWM app or method of changing kernel to flash anything"
tomasitoc said:
Hello,
Not sure if this has been brought up before.
I flashed the simply galaxy (gingerbread) rom last night. I come from bionixV 1.2.1.
I have 2 issues right now. I can not see the recovery. When ever I boot into recovery it freezes/hangs
in the vibrant boot logo. I read somewhere that the recovery is behind the boot logo and I can not see it.
I tried the 3 button combo and the rom manager reboot into recovery - I still can not get into recovery
I will appreciate any help.
Also, I installed titanium backup, it installed correctly, but I can not see it in the app drawer.
thanks,
Click to expand...
Click to collapse
I think I told this before in the rom's thread, you cannot boot into recovery by choosing that option from the power screen. You've to flash a 2.2 kernel (overstock) using the sgs kernel flasher app and then reboot, press the 3 buttons combo and you'll have the recovery screen full functional.
READ, READ AND READ my friend before you flash any rom.
I flashed the overstock 2.1 using the SGS kernel flasher app.
Now my phone hangs at the overstock logo.
I took out the battery and powereed on, it still hangs at the overstock logo.
I can do the 3 button combo to go to recovery.
SGS Kernel flasher bricks me everytime....not really recommended....but that could be that only way to flash a kernel I guess...or ODin
flash to stock..
tomasitoc said:
I flashed the overstock 2.1 using the SGS kernel flasher app.
Now my phone hangs at the overstock logo.
I took out the battery and powereed on, it still hangs at the overstock logo.
I can do the 3 button combo to go to recovery.
Click to expand...
Click to collapse
You've to use the 3 buttons combo to get into recovery. Take the battery off, press power and the volume buttons, when the vibrant screen shows up, take your finger off the power and keep the other on the volume. TARAAA, you're in recovery.
OK , I understand flashing overstock kernel, allows me to do what I want in recovery. after I finish what I have to do. I need to flash back to a 2.3 based kernel
What kernel do you recommend so that I can use simply galaxy again?
How about the lidroid kernel, it says recovery works and no headset toggle to use? Have you tried lidroid kernel?
http://forum.xda-developers.com/showthread.php?t=1058802
tomasitoc said:
OK , I understand flashing overstock kernel, allows me to do what I want in recovery. after I finish what I have to do. I need to flash back to a 2.3 based kernel
What kernel do you recommend so that I can use simply galaxy again?
How about the lidroid kernel, it says recovery works and no headset toggle to use? Have you tried lidroid kernel?
http://forum.xda-developers.com/showthread.php?t=1058802
Click to expand...
Click to collapse
No. And I advise you not to either, it could well brick your phone for good with it's bootloader modification. I'd suggest flashing the Gold 2.0 kernel. Then when the phone boots up, flash the beta 7 kernel, using the sgs kernel flasher.
Abu-7abash said:
No. And I advise you not to either, it could well brick your phone for good with it's bootloader modification. I'd suggest flashing the Gold 2.0 kernel. Then when the phone boots up, flash the beta 7 kernel, using the sgs kernel flasher.
Click to expand...
Click to collapse
@abu-7abash
will you be kind enough to post me a link to gold 2 kernal and the beta 7 kernel. I tried a search i am not sure if its the correct kernels you mentioned
thanks
There you go, they're attached in the op here
thank you
I noticed you have malice 2.3.1 ,is this a gingerbread rom?
Nope. It's a 2.2.1 one. Im not running it at the moment though, been jumping through 4 roms in the last 24 hours alone, hard to keep up with the sig
based from your experience what is the 2.3 rom that you like best
At the moment it is a classified one, maybe in a day or two it will be posted around here. You'll know it then
In the meantime, SimplyGalaxy is the best around I say.
@abu-7abash
Sorry for all the questions. I went to the link you posted which is Damiangto's forum. I am unable to find the kernel. I registered and I still can not find a download for the kernel
can you guide where in the website it is
thanks
Better yet I attached them for you.
thank you very much.
question:
the simply galaxy has voodoo enabled?
Does thi kernel have voodoo? if it doesn't that mean I have to disable voodoo before flashing these kernels?
tomasitoc said:
thank you very much.
question:
the simply galaxy has voodoo enabled?
Does thi kernel have voodoo? if it doesn't that mean I have to disable voodoo before flashing these kernels?
Click to expand...
Click to collapse
No need to disable voodoo.
Sent from my GT-I9000 using XDA Premium App
No you don't have to disable voodoo. They both support ext4
@abu-7abash
why do I have to flash first the gold 2.0 and then flash the beta 7.
can I just flash immediately to beta 7
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"""""