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.
Related
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.
hey guys,
I have problems about flashing the Kernel like OverStock v1.3, http://forum.xda-developers.com/showthread.php?t=967861
I am using Bionix -1.3.1 now, I just reboot into the clockwork recovery, it said that I need the Red Recovery, so if it is red words clockwork recovery, so it will work?
I just put the Kernel file into the sdcard and install like a rom?
Should I disable the Voodoo? If I need to disable the voodoo, after install the new Kernel should I enable the Voodoo again?
Thanks guys!
pxc668 said:
hey guys,
I have problems about flashing the Kernel like OverStock v1.3, http://forum.xda-developers.com/showthread.php?t=967861
I am using Bionix -1.3.1 now, I just reboot into the clockwork recovery, it said that I need the Red Recovery, so if it is red words clockwork recovery, so it will work?
I just put the Kernel file into the sdcard and install like a rom?
Should I disable the Voodoo? If I need to disable the voodoo, after install the new Kernel should I enable the Voodoo again?
Thanks guys!
Click to expand...
Click to collapse
Yes, you need red recovery for OverStock. You don't need to disable Voodoo to flash OS, but it won't hurt to either. Reboot into Red Recovery from your modified power menu (long press pwr button), select Install zip from sdcard, then choose Select zip, then navigate to the OS zip (which must be at the root of your internal sdcard, not in a downloads our other folder, nor on the external_sd), then choose Yes. It shouldn't take more than a minute or two, and then it will say the file had been installed successfully, then you choose Go Back, and then Reboot Phone Now.
This is all recalled from my swiss cheese brain, so if the selections don't match verbatim, choose the one most likely to have been what I meant.
As always, there's potential for things to go horribly wrong, and you can end up with a shiney paper weight flashing stuff, so please thank me now before you brick your phone and change your mind.
Sent from my rough sketch of a Vibrant on a brick I like to pretend is running Trigger 2.7 on OverStock 1.3...
Droidificator said:
Yes, you need red recovery for OverStock. You don't need to disable Voodoo to flash OS, but it won't hurt to either. Reboot into Red Recovery from your modified power menu (long press pwr button), select Install zip from sdcard, then choose Select zip, then navigate to the OS zip (which must be at the root of your internal sdcard, not in a downloads our other folder, nor on the external_sd), then choose Yes. It shouldn't take more than a minute or two, and then it will say the file had been installed successfully, then you choose Go Back, and then Reboot Phone Now.
This is all recalled from my swiss cheese brain, so if the selections don't match verbatim, choose the one most likely to have been what I meant.
As always, there's potential for things to go horribly wrong, and you can end up with a shiney paper weight flashing stuff, so please thank me now before you brick your phone and change your mind.
Sent from my rough sketch of a Vibrant on a brick I like to pretend is running Trigger 2.7 on OverStock 1.3...
Click to expand...
Click to collapse
I would only add I would disable voodoo, you don't have to but it does lower risk of potential problems.
oka1 said:
I would only add I would disable voodoo, you don't have to but it does lower risk of potential problems.
Click to expand...
Click to collapse
I'm kind of reckless with other people's stuff, so I wouldn't suggest that at all.
Seriously though, I have heard that not disabling VooDoo, even when it says you don't have to, does increase your chances of trouble. But on the flip side, it speeds the process up so freakin much I'm convinced that I can flash, brick, Odin, and flash again in the time it takes to disable voodoo, flash, re-enable voodoo. (j/k)
Droidificator said:
I'm kind of reckless with other people's stuff, so I wouldn't suggest that at all.
Seriously though, I have heard that not disabling VooDoo, even when it says you don't have to, does increase your chances of trouble. But on the flip side, it speeds the process up so freakin much I'm convinced that I can flash, brick, Odin, and flash again in the time it takes to disable voodoo, flash, re-enable voodoo. (j/k)
Click to expand...
Click to collapse
Lol that is so true about the amount of time it takes to enable/disable voodoo!!
I personally flash between overstock and kb1+voodoo on a regular basis and never disable voodoo and have not had a problem yet,but then again i dont have hardly any of the problem most seem to get with flashing and if i do.....i oden. I cant say weather its becuz i pay attention to details or if i get more luck than others
Bionix-V 1.3 w/a Splash of Color
Birgertime has done a great job getting EDT ROMs available via Rom Manager (I may have bugged him a couple of times). I was a bit shocked when I was reading the thread and saw people were having issues when they updated using Rom Manager. I think the consensus was that Rom Manager was not properly wiping.
This is what I did:
I was on Trigger 2.9.3 *I try every ROM and I just felt like being old school.
I opened Rom Manager and downloaded the latest Trigger 3.2,
I used the KB1 Modem, KB5 kernel, I selected a few of the apps I wanted (bloater, titanium, maybe a couple others)
I told Rom Manger to wipe and do a backup by clicking the two boxes.
Once the download was completed I proceeded.
It went into CWR and it did a backup... immediately it did a wipe (it showed the steps in CWR like normal)... and then it flashed the ROM and it rebooted perfectly. I have had NO issues with the ROM. It's perfect in my opinion.
What I want to know, for those who had issues... what was different?
Did you get rebooted into the red voodoo recovery (I was at the normal CWR)? I don't understand how it can work perfectly for me, and not others. I would like to know exactly what went wrong so we can go to @koush and try and get both Rom Manager and Clockwork Recovery working better for us.
Between this, Fix Permissions, Partitions F'ing people, stats not working (for the dev's) I think our phone needs this amazing app to be better, and I know koush can do it.
** If there are other things wrong with Rom Manager/CWR, please post... it would be nice to have a list of things to work on.
I can put up a test version on rom manager. The current Trigger 3.2 up there will wipe regardless of what you tell ROM manager.
PS: who rated it 1 star?
birgertime said:
PS: who rated it 1 star?
Click to expand...
Click to collapse
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
s15274n said:
Team Whiskey
EDIT, were you going to fix the prop so it showed 3.2, not 3.1? =)
Click to expand...
Click to collapse
I think I did when I uploaded the vvm fixed version
androidmonkey said:
Im confused. You said you used CWR to wipe and flash the ROM. What exactly did you use ROM Manager for?
Click to expand...
Click to collapse
To download it
Sent from my SGH-T959 using XDA App
duboi97 said:
To download it
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
androidmonkey said:
Ah, ok. I dont see why downloading it with RomManager would make a difference, unless its not completely downloading. The safest is like birgertime says in the Trigger thread, download on PC and check Hash.
Click to expand...
Click to collapse
Rom Manager is the most convenient way to do this. it also checks the MD5 before it flashes the ROM. Trust me when I say I know the process...
I just want to know from those who had issues with using Rom Manager to download/wipe/flash, what went wrong?
I flashed it using Rom manager.
I chose KB5 modem and KB5 Kernel.
along with things like Bloater and swype.
it rebooted into red recovery and seemed to go fine from there.
when it first booted up it seemed ok at first, I let it sit for a while like usual.
and then rom manager force closed.
from there it was just force close after force close.
So I rebooted back into recovery and wiped data and dalvik.
then I rebooted.
and everything works just fine, with the exception of it never installed any of the extras I chose (swype,Bloater, etc...)
but I had those in titanium backup just in case anyways so it wasn't a big deal.
Its been running beautifully ever since.
Pretty much same thing happened to me, it went to red recovery and seemed to flash just fine. then when it rebooted i kept getting force closes everywhere. rebooted to clear cahce, dalvik, and fix permissions and has been fine ever since. it didnt wipe my apps which i found a bit odd
Alright, so as I expected... it sounds like it was
THE RED VOODOO RECOVERY AS THE PROBLEM.
Anyone able to prove that wrong?
I mean, it makes sense, it's not the recovery Rom Manager expects to see.
So, how do we fix it? This would not be koush now, I do not think.
Where did the red voodoo recovery initiate? I remember it just showed up one day. was it supercurio?
Anyone know where I can get the 3.0 clockwork update.zip? I am currently on blue version and would like 3.0 to flash com rom can someone post the link? All the ones in the stickies lead me to 404 file not found on drop box...
http://forum.xda-developers.com/showthread.php?t=1046905
Scroll down below the ODIN packs and you will find the .zip versions.
They are 3.x and come in 3 different colors.
Tested the first link and I was given the download so you should be good to go.
Thank you for posting in the correct section!
gkirby11 said:
http://forum.xda-developers.com/showthread.php?t=1046905
Scroll down below the ODIN packs and you will find the .zip versions.
They are 3.x and come in 3 different colors.
Tested the first link and I was given the download so you should be good to go.
Thank you for posting in the correct section!
Click to expand...
Click to collapse
No thank you for being so diligent and responding! Two other questions:
How do I know if I am voodoo'd? I have the voodoo folder on my SD card but I do not know if I am actually voodoo'd as I didn't do anything to make myself that way.
Which one of those should I get to flash community rom 2.0?
cking122 said:
No thank you for being so diligent and responding! Two other questions:
How do I know if I am voodoo'd? I have the voodoo folder on my SD card but I do not know if I am actually voodoo'd as I didn't do anything to make myself that way.
Which one of those should I get to flash community rom 2.0?
Click to expand...
Click to collapse
I will answer these in reverse order as.... well.... it will be easier
Any of them, the colors mean nothing (dont quote me on that) and if you choose the PBJ version of Kangbang (community rom) you will get a yellow one! They all work the same but leading to the first question.....
....When you have the latest CWM3.X there is a voodoo option menu. If you click it you will be showen a list of voodoo check points (what I call them) that will tell you if and where the lagfix (voodoo) is enabled. If you flash a voodoo kernel you will automatically be converted to voodoo. **you will hear a nice robot lady voice tell you upon first start up**
If you just want a simple way of telling right now if you have voodoo. Pop over to the market and type in voodoo. Download the voodoo control app and open it. There is a menu that will tell you if it is enabled or not!
If I was going to do it I would grab the purple version (personal preference) and flash Imnuts's PBJ -50 kernel or the Kangbang (comm ROM) package that the kernel and ROM come in together. That way you will have voodoo, yellow updated CWM3.X, and the famed Kangbang (comm ROM)!
You can check right in CWM (under Voodoo), or via the Voodoo Control app.
https://market.android.com/details?id=org.projectvoodoo.controlapp
Is there anyway I can download a non-voodoo update.zip as I don't want to go voodoo.
cking122 said:
Is there anyway I can download a non-voodoo update.zip as I don't want to go voodoo.
Click to expand...
Click to collapse
any update.zip will work as far as I know and you can still use the 'voodoo' red CWM 3.x even if you don't want voodoo. I was using it for a while to flash the ComRom package with no kernel. As for checking if you have voodoo enabled, you can do what the others said or run the Quadrant app from the market. If voodoo your score should be 1500+, normally its around a 1000. Of course the scores mean nothing, its just a quick way to tell.
tapatalked from my KangBanged Fascinate
anoninja118 said:
any update.zip will work as far as I know and you can still use the 'voodoo' red CWM 3.x even if you don't want voodoo. I was using it for a while to flash the ComRom package with no kernel. As for checking if you have voodoo enabled, you can do what the others said or run the Quadrant app from the market. If voodoo your score should be 1500+, normally its around a 1000. Of course the scores mean nothing, its just a quick way to tell.
tapatalked from my KangBanged Fascinate
Click to expand...
Click to collapse
You no longer need the update.zip in root of SD card to get into CWM recovery.
Sent from my SCH-I500 using XDA App
XDAholic said:
You no longer need the update.zip in root of SD card to get into CWM recovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I figured, I just got into such a habit of having it there that its always there now lol
tapatalked from my KangBanged Fascinate
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"""""