So I have been messing around with EB01 for the last few days and I am a newbie. So far everything has gone great. I first flashed SuperClean 2.1 Non-voodoo and the upgraded to Superclean 2.2 non-voodoo. Finally, I got some advice and added voodoo by flashing just the EB01 Voodoo Kernel from jt1134. Everything has worked awesome. Voodoo definitely working, confirmed w/ Quadrant Score of about 1500.
I see that Superclean 2.3 is out for EB01 and I want to try it out. Since I already have voodoo installed w/ Superclean 2.2, what steps do I need to do to safely upgrade? I have done everything right so far and don't want to mess this up.
Here is my best assumption: Download EB01 Superclean 2.3 voodoo version and flash without wiping or diabling lagfix.
My main questions are:
1. Which Superclean version do I flash since I want to stay with voodoo (in other words do you have to flash the voodoo version or is that just being redundant since I already have voodoo intalled?)
2. If I am staying with a similar ROM, do you need to disable lagfix?
3. Can you give me scenarios when I should disable lagfix?
4. I upgraded from SC 2.1 to 2.2 without doing a wipe and it worked great. Is a wipe necessary from 2.2 to 2.3, or did I just get lucky before?
If you are running voodoo you don't want to flash anything but voodoo over it. You do not need to disable lagfix. I would recommend wiping cache to keep wierd little remnants from hanging around. The only time you would need to disable lagfix is if you were going to flash a non-voodoo kernel. Hope that helps.
I think that helps. So it sounds like I should keep flashing the superclean voodoo versions when a new one comes out if I want to upgrade. I should select "wipe data and cache" in ROM Manager before upgrading. I use Titanium Backup to backup my apps. Is there any other way to get back your apps and settings other than using Titanium Backup and running a restore?
Also, I am running the Superdark ROM over the top of Superclean 2.2 voodoo. Would my best option be: flash SuperClean 2.3 while wiping all data and cache. Flash Superdark again. Reinstall all apps and settings.
If you want to stay with voodoo, yes. I don't ever get into Rom Manager anymore. With all of the new themes out with reboot options built in it's just easier to boot straight into recovery and take care of business there. I install my rom/kernel (since thats how Adry's packaging them at this point) then install my theme since the rom over-writes your theme changes, then I wipe the cache partition a couple of times and the dalvik cache a couple of times. Then reboot.
Edit: Sorry I forgot to mention that if you don't do a data wipe then all of you apps and settings usually stay intact. But backups are still a good idea should something go wrong.
I'm watching this thread too.
I had 2.2 and was having issues with it - looking to go up to 2.3 now that the screenshot app is back.
I have just flashed 2.3 voodoo over 2.2 voodoo without wipe, all is working fine.
No issues encountered.
Have you restarted your phone yet? That's when I got all my issues.
brettdacosta said:
Have you restarted your phone yet? That's when I got all my issues.
Click to expand...
Click to collapse
Yes, multiple times, been flashing mods.
I have just flashed 2.2v-2.3v and have not run in to any issues. I don't wipe anything and still have not run into anything weird. On 2.2v I did notice my pics from my camera weren't in my gallery, but 2.3v seemed to fix it.
Same here, I did an upgrade from 2.2 to 2.3 and no issues encountered. i did wipe the cache/dalvik cache but was willing to try it sans full wipe
I backed up just in case although
Mikes30000 said:
I think that helps. So it sounds like I should keep flashing the superclean voodoo versions when a new one comes out if I want to upgrade. I should select "wipe data and cache" in ROM Manager before upgrading. I use Titanium Backup to backup my apps. Is there any other way to get back your apps and settings other than using Titanium Backup and running a restore?
Also, I am running the Superdark ROM over the top of Superclean 2.2 voodoo. Would my best option be: flash SuperClean 2.3 while wiping all data and cache. Flash Superdark again. Reinstall all apps and settings.
Click to expand...
Click to collapse
Whoa now, don't use ROM Manager to flash ROMs in voodoo! Use the red voodoo recovery. You shouldn't have to wipe data to go from 2.2 to 2.3. Just wipe cache and dalvik cache to be safe. I'd just do a nandroid beforehand to ensure you can go backwards if something runs funny.
I was able to go from 2.2 to 2.3. I did however backup and then wipe data, cache, and dalvik. I got rid of a few small issues that I was having in 2.2. Namely, I could connect to certain wifi hotspots and not others. As soon as I installed 2.3, I locked on immediately.
Thanks for the ROM Manager advice. I did all my work through the red cwm. I am going to try a 2.3 to 2.4 update now with just wiping caches.
Do you guys have any advice w/ Titanium Backup? Once I clean installed 2.3, I, like a lot of people noticed that the new market redownloaded almost everything that I had downloaded in the past. Pain in the ass, because I had to uninstall a lot of crap. I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
how do i know if i have voodoo or non voodoo? im on a stock deoxed EB01. do i need to install voodoo kernel before i install a voodoo superclean?
sorry new to this fascinate.
Mikes30000 said:
I was able to go from 2.2 to 2.3. I did however backup and then wipe data, cache, and dalvik. I got rid of a few small issues that I was having in 2.2. Namely, I could connect to certain wifi hotspots and not others. As soon as I installed 2.3, I locked on immediately.
Thanks for the ROM Manager advice. I did all my work through the red cwm. I am going to try a 2.3 to 2.4 update now with just wiping caches.
Do you guys have any advice w/ Titanium Backup? Once I clean installed 2.3, I, like a lot of people noticed that the new market redownloaded almost everything that I had downloaded in the past. Pain in the ass, because I had to uninstall a lot of crap. I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
Click to expand...
Click to collapse
The reason it tries to download everything is the automatic restore function inside settings > privacy. It should be unchecked, and youwon't have to worry with it. Keep back up checked though at least I did. Good luck.
Mikes30000 said:
I used Titanium to restore my USER apps and data and that went well. Is there anything with SYSTEM data that I should ever be restoring that can help out with getting my previous setting back?
Click to expand...
Click to collapse
The only thing from system data that I've restored is calendar data and calendar data storage. That has successfully restored my appointments, etc. that were in the stock calendar. I wouldn't load back any system apps, especially when going from eclair to froyo because you'd likely be overwriting newer apps with older ones.
dadsterflip said:
how do i know if i have voodoo or non voodoo? im on a stock deoxed EB01. do i need to install voodoo kernel before i install a voodoo superclean?
Click to expand...
Click to collapse
stock is non-voodoo. the voodoo superclean installs the kernel with it. however I caution you to do your homework about voodoo and how to use it properly before making the jump. You can hose up your phone pretty good if you don't use it right.
Related
So I just got my Fascinate and have rooted it, installed clockwork mod and worked on flashing a couple of roms. But here is the thing, when I flashed a ROM on my old Incredible, it was always starting brand new unless I was doing a restore on clockworkmod. Well, the Fascinate seems to be different. When ever I flash a ROM, All of my apps, are still there with out doing a Titanium back up, all the Verizon apps are still there even though the ROM creaitor said they weren't there. I know the rom flashed, because I have the vanilla lock screen. Is this the way the Fascinate is or do I have a funky phone?
do you erase data or have voodoo installed?
bomber889 said:
do you erase data or have voodoo installed?
Click to expand...
Click to collapse
Yes, I do have Voodoo installed via the Kernel I am running. Is Voodoo causing this to be different then my Dinc? I also do a full wipe of everything before flashing a new rom or restoring an old one.
sonar_chris said:
Yes, I do have Voodoo installed via the Kernel I am running. Is Voodoo causing this to be different then my Dinc? I also do a full wipe of everything before flashing a new rom or restoring an old one.
Click to expand...
Click to collapse
You should read up in the voodoo threads. There's some different steps to take when running it.
I recently installed a stock kernel with voodoo lag fix in it from:
http://forum.xda-developers.com/showthread.php?t=870480
and I was curious if I were to flash a new rom, would that voodoo lag fix still be there or would the new rom completely just overwrite it or whatever.
It will still be there as long as the rom your flashing comes with a voodoo kernel. Just make sure you read the flashing instructions from the dev who put the rom together. They always let you know if its safe to flash over a voodoo enabled rom/kernel.
Trigger + Overstock = Awesomeness
GreggoryD502 said:
It will still be there as long as the rom your flashing comes with a voodoo kernel. Just make sure you read the flashing instructions from the dev who put the rom together. They always let you know if its safe to flash over a voodoo enabled rom/kernel.
Trigger + Overstock = Awesomeness
Click to expand...
Click to collapse
This is generally correct. But if you flash from one framework to another Say going from a Bionix to an Axura or trigger, then for me, I always disable voodoo first then I flash, safer that way.
how do you disable voodoo?
is it a must to wipe dalvik cache and to wipe data/factory reset when flashing a new rom, i wnana try the trigger + overstock rom.
I am currently running stock kernel with voodoo lag fix on froyo KA6...
fragmentttt said:
is it a must to wipe dalvik cache and to wipe data/factory reset when flashing a new rom, i wnana try the trigger + overstock rom.
I am currently running stock kernel with voodoo lag fix on froyo KA6...
Click to expand...
Click to collapse
Disable voodoo from the RED recovery. It will be under advanced options. Let it finish and then factory data reset/dalvik cache wipe. Its always a good idea and will give you the best odds (while already high) at a perfect outcome.
After this feel free to flash Trigger then the overstock kernel.
would there be any problems if I DIDNT wipe dalvik cache and do a factory reset?? becuz i really dont want to lose my apps.
fragmentttt said:
would there be any problems if I DIDNT wipe dalvik cache and do a factory reset?? becuz i really dont want to lose my apps.
Click to expand...
Click to collapse
Just use Titanium Backup to backup and restore your apps.
Sent from my SGH-T959 using Tapatalk
fragmentttt said:
would there be any problems if I DIDNT wipe dalvik cache and do a factory reset?? becuz i really dont want to lose my apps.
Click to expand...
Click to collapse
There could be problems if you don't do that. Just back up your apps with titanium. Just make sure when you restore thru titanium that you only restore user apps. Don't restore all apps and system data.
Trigger + Overstock = Awesomeness
drewdude007 said:
Just use Titanium Backup to backup and restore your apps.
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
This works well. However keep in mind some devs have said not to restore TI backups on certain flashes. I can't remember the particulars but the backed up app data conflicts somehow.
Sent from my SGH-T959 using XDA App
unless you know for sure that the new ROM is using voodoo....remove voodoo.
Matter a fact. You should always revert back to stock and go from there...Tedious i know but it helps to avoid so many issues its not even funny. trust me i know.
Trigger updated their rom that includes Overstock kernel. I've never installed a kernel before. Do you you flash it the same way as the rom since they are together?
If I want to change rom, do I have to remove the kernel?
The kernel is included with the rom
Sent from my SGH-T959 using XDA Premium App
christpuncher said:
The kernel is included with the rom
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
In the official thread, there were 2 links; one for just the rom and one for rom with Overstock
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
CalabiYau said:
Hi
I have a SGS with jpy + voodoo. I have done some CWM backups.
I plan to change to JVP. I assume that I'll need a clean install and some titanium work.
Can I simply use JVP CWM restore to go back to my JPY if I finally get disappointed with JVP?
In that case, it will be an exact photo of the CWM JPY backup or I'll need to reinstall data or apps???
Thanks a lot!!
Click to expand...
Click to collapse
You have to do a clean install. With Odin, pit 512, Re-partition and the 3 files. I advise to wipe data and factory reset before flashing.
You should restore the backup titanium applications, but only the applications carefully restored, not the data. JPY to return to the same but now flashing the JPY. If you have any lagfix enabled is recommended to disable it before doing anything. In Spain we say "better safe than sorry."
But then if i go to jvp I'll loose the chance to go back easily to JPY??
I mean that installing cleanly JPY again.,.......
Hello,
went through this today (from JVP back to CWM backup of JSD, never used repartition, flashing tool = heimdall), ran in some problems as I thought that the Gingerbread bootloaders work for Froyo,too (I think I read that somwhere here at XDA).
1) Tried flashing Froyo kernel (speedmod) only and restored CWM-Backup of JSD after factory reset/cleared cache and dalvik cache -> did not work, booting stopped at SGS logo without progress for a really long time (longer than recreating dalvik cache used to last).
2) Flashed a complete self-made JSD-ROM including bootloaders and then installed CWM backup of last running JSD system (again, after factory reset, dalvik & cache clearing) -> worked fine, no problem for hours now.
Maybe I did something wrong at first try, maybe needed the correct bootloaders - don't know.
Hope this helps you a little bit - recreating running system from CWM *full* backup including apps and settings finally worked for me, data on sdcard and external_sd will not be touched (unless you format internal sdcard which is /sdcard directory).
Edit: Be sure to have a copy of your full CWM backup on your harddisk so in case something goes totally wrong you can restore the backup to your SGS recovery, the backups are saved in /sdcard/clockworkmod/backups/)
Yes, I guess this should work. A clean JPY installation, then CWM and then restore...
By the way, we did you go back to JSD??? JVP was faulty??
No, believe me or not, I somehow "feel better" with JSD, JVP made absolutely no problems here, it felt very fast, stable, without (for me) noticable errors, no battery drain.
Maybe I'll try 2.3.4 again in some weeks as I like experimenting with Linux/Android in general but for now JSD is my choice. Only real advantage (again, for me, maybe you don't need this) of Froyo/JSD is that I can reenable logcat using speedmod recovery tweaks.
I use this as a reliable root back to Froyo from custom roms or gingerbread. Not failed me yet. I keep plenty of backups so touch wood, no fowl ups yet.
http://forum.xda-developers.com/showthread.php?t=1100906
are you using the Stock ROM ?
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Android 17 said:
I'm stuck at the boot-screen of Deck's 1.2 rom, however, I can still access HBOOT and Clockwork Mod Recovery.
I don't see an explicit option, but is there a way I could access Apps or other data to save as a back-up?
I foolishly deleted my rom back-up, and last time I used Titanium Backup was a few weeks ago, so it's not a good option. Thanks!
Click to expand...
Click to collapse
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
mattykinsx said:
As long as the .zip for the ROM doesn't wipe /data, you could reflash "Deck's 1.2 ROM hopefully fixing your issue and not losing your apps.
Click to expand...
Click to collapse
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Android 17 said:
I already tried wiping cache and dalvik, reflashing the rom, and I still get stuck in a boot-loop =/
Thanks for the suggestion though.
Click to expand...
Click to collapse
You could wipe /boot and /system as well and reflash and see if that fixes it.
mattykinsx said:
You could wipe /boot and /system as well and reflash and see if that fixes it.
Click to expand...
Click to collapse
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Android 17 said:
I just tried that and it didn't work either. This is maddening.
The last thing I remember doing was tinkering with the lockscreen settings in the advanced settings. I set up a rotary revamped lockscreen with Dolphin Browser HD as my custom application. I have Dolphin saved to SD too, but I don't see why such a small thing would cause constant bootloops.
It ran fine before 1.2 stable and messing with the lockscreen.
Click to expand...
Click to collapse
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
mattykinsx said:
I have titanium backup run every night along with my call log back up app and go sms to back up texts.
Prevents this kind of thing.
Nothing you've said you have done explains a boot loop.
Click to expand...
Click to collapse
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Android 17 said:
That's a good idea. I usually just use Titanium backup when I'm doing a full wipe or flashing a ROM with significant updates, but since I'd been using Deck's for a while and having no issues whatsoever really and just updating incrementally, I didn't think to backup in a while.
I had actually backed-up the ROM prior to flashing 1.2 stable, but I needed to delete it to make room to back up the newer version, and I didn't think it'd be a big deal since it was stable for a few boots. I guess I got too comfortable.
This is ridiculous, I didn't make any changes to the ROM or flash any new radios or anything of the sort that should cause a bootloop.
I do also use the Theme Manager MattedBlues theme but I've been using that for over a week or so with no issues, so I doubt that's the cause.
Oh well, thanks for the ideas though.
Click to expand...
Click to collapse
Sorry I took my Xanax to sleep or else I'd likely be able to think of some kind of solution.
Hopefully someone else can help you out.
I think in CWM if you mount System&Data /apps you could utilize adb pull..... Also did you set up any custom partitions, a2sd, data2ext, ect... ?
Sent from my HERO200 using XDA App
Actually thanks for the suggestions guys, I managed to dig up an older version of the rom saved on my downloads folder and flashed it and booted.
For some odd reason, an older release labeled as experimental works better than the 1.2 stable...
It's strange too because I looked around Deck's thread and no one else reported any problems similar to what I was having at all.
For all intents and purposes it appears to be very stable and functional for everyone BUT me
Thanks for the suggestions though. I guess I'll hold off on flashing any roms for a while or wait for a newer version and try flashing with a full wipe.
Cool glad you got her going.
Kaaameeehameeehaaaaaa!
After updating to 3.01 ...occassionally my power button does not turn screen on, keyboard lights up, but screen will not come on...have to pull battery...anyone else??
No problems here. That kernel is kickin ass on my phone. A clean install, wipe cache dalvik and data, will alleviate 99% of those quirky problems.
Backup your apps and data thru titanium backup
Go to cwm
wipe cache
wipe dalvik
wipe data
Install ROM
Install kernel
if your installing a theme, wipe cache and dalvik again, probably not necessary, but it won't hurt, then install theme.
Reboot system
Go on the market, and get your apps, especially Titanium Backup.
Try to restore your apps back thru Market rather than titanium, this ensures that your apps are not corrupt in some way. If there are certain apps that for one reason or another are no longer available from Market but you absolutely gotta have it. Restore it from titanium.
Restore data from Titanium, but only whats absolutely necessary.
Sometimes things get corrupted when flashing over and over and the above method works everytime to get it back solid and glitch free.
Restore only the data
Xalky said:
No problems here. That kernel is kickin ass on my phone. A clean install, wipe cache dalvik and data, will alleviate 99% of those quirky problems.
Backup your apps and data thru titanium backup
Go to cwm
wipe cache
wipe dalvik
wipe data
Install ROM
Install kernel
if your installing a theme, wipe cache and dalvik again, probably not necessary, but it won't hurt, then install theme.
Reboot system
Go on the market, and get your apps, especially Titanium Backup.
Try to restore your apps back thru Market rather than titanium, this ensures that your apps are not corrupt in some way. If there are certain apps that for one reason or another are no longer available from Market but you absolutely gotta have it. Restore it from titanium.
Restore data from Titanium, but only whats absolutely necessary.
Sometimes things get corrupted when flashing over and over and the above method works everytime to get it back solid and glitch free.
Restore only the data
Click to expand...
Click to collapse
Thanks,
Should have provided more pre-info...did the wipe davlik and cache thing as normal. Have moved between the voodoo and samurai kernel and OP problem is the first I have encountered. Thinking about going backl to Sam 2.08...no problems there. thanks again for the speedy help!
Yep,
3.01 is amiss ...went back to 2.08 and all is fine now... on the development forum it looks like other users of 3.01 are experiencing the same problem...
Naddict said:
Yep,
3.01 is amiss ...went back to 2.08 and all is fine now... on the development forum it looks like other users of 3.01 are experiencing the same problem...
Click to expand...
Click to collapse
I am using Samurai 2.0.8 as well with absolutely NO problems
The screen not coming on is a wakelock.... your cpu doesn't like the 100mhz step which means you need to get that unchecked in voltage control unselecting it that should fix the wakelock...maybe ^^
Sent from my OG Epic
Thanks Biggoron, I saw a post about that issue somehwere and I turned off the 100mhz step in voltage control...still had the issue and, as I mentioned earlier, am seeing other users still having the problem with all three 72mhz versions....interesting....I have always been a lurker and never contributed...so now I am working on my 10 posts just so I can at least offer my observations. Thanks again
Figured it wouldn't of changed anything thus the ....maybe^^
Hopefully earthbound will figure out the issue have you tried any of the 60hz versions to see if it still occurs?
Sent from my OG Epic
No,
I went back to the Voodoo kernel (1.01oc/uv), it has been pretty stable, and so was Samurai 2.08....
No problems with 2.08 or 3.01 power button, even running at 100 mhz. However, my rotation lag came back not sure if it's the rom (Marcusant's v1) or the kernel, or something else... it seems the only issue so have to live with it.
for what iti is worth, I also noticed a little "lag" or interuption in my notification sounds with 3.01...but that is all behind me now. sticking with voodoo 1.01 for now. seems to be the most stable other that nube's...anyone know when he is putting up a new kernel?