Related
Some say, just disable Voodo and you'll be fine. But how to disable? Isn't it possible to uninstall it completely?
Some say, just boot into recovery and do a cache wipe and factory reset. This sound easy enough, but would this work?
I have international version GT i9000, stock ROM, only modification is root, and voodo color correction + lag fix pack.
squyerkul said:
Some say, just disable Voodo and you'll be fine. But how to disable? Isn't it possible to uninstall it completely?
Some say, just boot into recovery and do a cache wipe and factory reset. This sound easy enough, but would this work?
I have international version GT i9000, stock ROM, only modification is root, and voodo color correction + lag fix pack.
Click to expand...
Click to collapse
And i Quote directly from the Site for All the lazy people out there.....
" Create a file or folder named “disable lagfix” in a a directory named “Voodoo” in your internal SD card.
Reboot
Done !
If you really want to uninstall it, you’ll need to flash another kernel like the original coming with your Firmware, or flash at least the “PDA” version of a Firmware.
Kies don’t see the phone when you’re in Ext4 mode. You’ll need to “disable lagfix” before Kies see it. "
about the cache wipe / factory reset , im wondering myself but being a kernel im 99.99% sure it wont be touched but just in case anything does go crazy id like to keep this part open for either someone more informed than i am or Curio himself to answer
and let me add a small Q here regarding the quoted part " Kies don’t see the phone when you’re in Ext4 mode. You’ll need to “disable lagfix” before Kies see it. "
how come everytime i hook up kies mtp starts on the phone but kies doesn't recognize it yet after a driver recovery it does ? is this like a temp fix ?
Say I do the disable voodo lag fix thing, by creating the file on my internal SD card, and then do the factory reset\cache wipe. And then install Froyo via kies, would the voodo lag fix be gone now? Or would it be still around with Froyo?
squyerkul said:
Say I do the disable voodo lag fix thing, by creating the file on my internal SD card, and then do the factory reset\cache wipe. And then install Froyo via kies, would the voodo lag fix be gone now? Or would it be still around with Froyo?
Click to expand...
Click to collapse
not the expert here but from what i understand , the voodoo lag fix is a kernal and ud need a FW update to mess around with that.
so from what i see factory reset/ cache wipe wont but installing Froyo will
Here are the steps:
1. Disable Voodoo lag fix.
2. Boot into recovery and do factory wipe/reset
3. Load original or newer firmware 2.1 or 2.2 using Odin and check off repartition!
4. Do factory wipe/reset again.
5. Restore all apps and settings
6. Done...enjoy fresh phone.
rmanaudio said:
Here are the steps:
1. Disable Voodoo lag fix.
2. Boot into recovery and do factory wipe/reset
3. Load original or newer firmware 2.1 or 2.2 using Odin and check off repartition!
4. Do factory wipe/reset again.
5. Restore all apps and settings
6. Done...enjoy fresh phone.
Click to expand...
Click to collapse
regarding step 3. Can I do a Kies update like normal instead of Odin?
So? technically updating via Kies and Odin should give the same result or what?
Is it ok to upgrade from Assonance 5.2 to Cognition 3.04 directly? or do I have to go back to stock and then upgrade?
Thanks
green
I think the recommended way is to go back to stock and flash.
It is recommended to return to stock first.
Having said that, I have flashed about 100 times, and never returned to stock first. If the ROM has a wipe, and no wipe option, just choose the WIPE version, and you should be OK.
If your NEW to flashing - I would suggest going back to stock.
I would read the instructions of the chef/developer on if you need to disable any type of lagfixes etc before attempting to flash over the top of another ROM.
And the reason for flashing back to stock as it will wipe all remnants of the prior ROM (where it matters) from your phone letting you kind of start "fresh". This prevents any type of conflicts (i.e. forgot to disable the prior lagfix) and soft bricking your phone.
So - flash away as long as you understand how to recover from a failed flash.
Do not use odin 1 click if you have a build 1010 phone. There is a longer route you have to take to get back to stock. In general, just erase all user data from clockwork if you have the red recovery and are moving to another rom with the voodoo lagfix. Save odin for brick situations or if you are having problems.
Can =/= should. Spare yourself the trouble and time later, and just spend the time now to do it right. Backup, flash stock, master clear, load new ROM. No guesses, no trouble.
thanks folks so, if I have to flash to stock, can I use the stock rom saved/backed up in clockworks when I originally flashed? or is there any other method I should follow?
thanks
One click odin has the OEM ATT ROM built into it. Bloatware and all.
Scenario:
- I'm running Phoenix 4 ROM
- I want to try another ROM
- I have a copy of the JH7_OTA-1.zip
Can I just use ClockworkMod Recovery to flash the JH7_OTA ROM, then do a master clear from the phone and then apply any ROM I want?
Would that not accomplish the same thing as putting the phone in download mode and doing a stock restore via ODIN, followed by a Master Clear, and then flashing any ROM?
Can someone clear this up for me because it seems that both methods accomplish the same thing. They restore your phone to factory stock ROM as it's suggested by majority of the ROM before applying them.
Thanks
You can go from one rom to another without flashing stock.
I just went from doc jpy base to andromeda armani base. All I did was disable lag fix and kernel tweaks then flashed
I did so knowing I had odin just in case
What mcord11758 said except you don't actually need to disable anything. Just flash.
So that's the confusing part because:
Cognition ROM used to saynow there is just a DL link)
"flash back to I897UCJF6 (Recommended)"
and
How to flash PHOENIX Roms:
"1. BACK UP!!!
2. Use Odin One click to Flash Stock
2a. Wait for it to reboot and then re-enable debugging, hook phone back up to pc and Master Clear"
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
I would love to hear from one of the developers but I couldn't ask this question in the Dev Forum due too my n00b posting status.
Thanks for anyone who takes the time to provide some insight.
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Vezee said:
I got the concept that if running any lagfix it's best to disable it when updating the same ROM to a newer version but when doing a factory ROM it wipes out the ROM contents including the file-system format be it EXT4/EXT3 back to the Samsung RFS.
Click to expand...
Click to collapse
The partitions get formatted either way (unless it's now wipe, in which case I guess data and datadb don't). If are running ext4 and your new kernel supports ext4 then why disable it?
mcord11758 said:
Phoenix and cognition both use ext 4 filing and the clockwork recovery built in understand it.
You have no less risk flashing jh7. in essence you are doing the same thing
flashing stock was more necessary when recovery could not understand ext 4. Today you can change to three different kernels in one day without ever disabling a lagfix
Click to expand...
Click to collapse
Thanks, that was the answer I was looking form I didn't exactly understand that the restriction was the recovery rom. It makes sense.
Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.
Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked
Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.
OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.
Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?
If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore
That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.
This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug
Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0
Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug
I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0
Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing
Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0
hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu
Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0
yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..
changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0
ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(
Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.
before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.
The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over
So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?
I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot
I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot
I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot
I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.