I'd like to flash to Cog 3.04 directly if possible without Odin'ing back to 2.1. Is it ok to flash directly to 3.04 and if so, what the best way to wipe everything first to start form as blank a state as possible? I'm without a windows PC right now...
Thanks!
hate to bump but if anyone can provide a quick answer... thx.
I flashed 3.04 over 2b8 without any problem.....
You can try that but no guarantee that it will work.you may run into problems and have to flash back to odin then you will be sol with out a computer
Sent from my SGH-I897 using XDA App
You should be fine flashing from one version to another. If you enabled lagfix I'd disable that first, and to be on the safe side do a CWM backup, but other than that you should be fine. I've been flashing another ROM back and forth without going stock many times without issue.
You can go and flash custom ROMs on top of each other and it might work, but don't be surprised if you boot into Cog 3.04 and have to deal with a bunch of force closes or other weird behavior.
I ALWAYS recommend people flash back to stock and Master Clear/GSM Master Reset. That gives you a blank slate to work with. It takes less than 10 minutes, but some just believe that's too much work/time for them.
Your call.
I've never had an issue flashing updates on top of Cognition. I'm pretty sure as long as your lag fix is the same between versions then there should not be any problems.
I flashed serendipity 5.0 over 4.3 last night with no problems. I just disabled lagfix before I did.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks everyone for your helpful input.
Is it possible to master clear without going back to stock? I'd like for everything except the external sdcard to be cleared.
When you upgrade from the kernel baked into serendipity, do you need to do anything other than flash the new one? When I did this without changing any kernel settings in CWM, I got horrible battery drain, and looked to see kswapd0 jumping in at 50-75% on osmonitor. I know this has something to do with the lagfix but didnt want to monkey around in CWM until I was clear. In other words does flashing k13a over the serendipity speedmod carry over tweak settings or does it not, which would have caused my problem, or could the runaway kswapd0 be from something else? Flashing back to the backed up original kernel does fix the runaway process.
Only reason I want to upgrade is to keep learning how this all works together. And im a sucker for the latest and greatest. Searching yielded info on that process, but not much about how to remedy the issue, so apologies if im missing a relevant thread.
Thanks in advance.
Captivate fixed by Serendipity 5.7
sonicdescent said:
When you upgrade from the kernel baked into serendipity, do you need to do anything other than flash the new one? When I did this without changing any kernel settings in CWM, I got horrible battery drain, and looked to see kswapd0 jumping in at 50-75% on osmonitor. I know this has something to do with the lagfix but didnt want to monkey around in CWM until I was clear. In other words does flashing k13a over the serendipity speedmod carry over tweak settings or does it not, which would have caused my problem, or could the runaway kswapd0 be from something else? Flashing back to the backed up original kernel does fix the runaway process.
Only reason I want to upgrade is to keep learning how this all works together. And im a sucker for the latest and greatest. Searching yielded info on that process, but not much about how to remedy the issue, so apologies if im missing a relevant thread.
Thanks in advance.
Captivate fixed by Serendipity 5.7
Click to expand...
Click to collapse
I would start by calibrating the battery. http://forum.xda-developers.com/showthread.php?p=7723557 this usually fixes my drain. hope that helps otherwise i would start with a stock reflash with odin before trying again it couldnt hurt.
I dont think its battery stats.since.flashing back fixed it, pretty sure its a setting im not fixing or an incompatible app.
Captivate fixed by Serendipity 5.7
sonicdescent said:
I dont think its battery stats.since.flashing back fixed it, pretty sure its a setting im not fixing or an incompatible app.
Captivate fixed by Serendipity 5.7
Click to expand...
Click to collapse
yes, 5.7 comes with k13a.
It does? Mines still k12s.
after upgrading to CM7 i am having problems with my phone...its keep getting random shutdowns and reboot by itself...is there any know reason that will resolve this problem. If there is none, what I have to get back to stock or back to original settings.
I know how annoying that can be same thing happened to me on my phone when I did it I didnt really bother trying to find a solution for it. To gett to stock its just a matter of finding 2.1 stock rom and flashing it with Odin.
What version of CM7 do you have? They used to have a problem with the Wi-Fi sleep option that made your phone reboot a lot.
They fixed it in an update they put up a few days ago.
I have the update....so how can I install it
Sent from my Captivate using XDA Premium App
Hi guys
I've been messing around with jvb, jvh, jvo and now jvp for a little while now, when flashing a fresh jvp the other day I had my 1st ever error in odin and my phone had a blue screen. I pulled battery and started again. I think my usb has been playing up on my laptop. So I got back into download mode and redid the flash but started with eclair, then froyo then back to jvp hoping to clear out any errors. Since then I had ramads deodexed jvp running great with hardcores kernel. I had flashed several of his kernels as he updated quite frequently. I then stated having issues with wifi toggle. Id click it on and it would flicker on and off. Then just stay off, so id click it again and same thing. Eventually it would either turn on and work fine or it will reboot my phone. Since then I have tried other kernels and it still does it whether its a fresh copy of jvp or just roms flashed over the top. So far I think with just ramads jvp it is ok but I havent tested enough. I remember reading on gto's forum about doing a full clean from eclair using 3 files and repartition but I can't find 2.1 or 2.2.1 with 3 files. I also remember reading about wifi errors and driver fixes but I can't find that any where. Can anyone help. Links to other posts or links to 3 file 2.1 & 2.2.1. also if I wanted to go back to froyo can I use froyo bootaders after having gb bootloaders. If so how would I do it. Thanks garth
Sent from my GT-I9000 using XDA Premium App
I've found that turning wifi off then trying to turn it back on straight after causes the reboots, i also found that stock jvp not Ramads jvp doesn't flicker at all. Just turns on ok. So it maybe root or cwm causing wifi to flicker. But battery life is terrible on stock jvp. So far browsing the net for no more than 30 mins on hsdpa, installing a few apps and battery died in 5hrs. Also went back to froyo 2.2.1 and wifi worked great. Then added hardcores kernel k13e and a cooked Rom but had many force closes even after wiping everything. Not sure what else to do, maybe root phone again, add all the goodies i like and just deal with wifi paying up sometimes, hoping to get a sgs II soon anyways
Sent from my GT-I9000 using XDA Premium App
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!