Related
I've been doing a lot of reading on this forum trying to find the best way to update to Froyo... seems like every ROM says it requires me to wipe my data. I'm curious why that is? The official OTA update can update to Froyo without wiping my data, so why can't any of the ROMS on this site do that?
I'm just looking to update to Froyo and then customize it how I prefer.
I am already rooted, removed all the sprint/htc bloatware i dont want, customized my boot up animation, and changed the sprint banner... Certainly I will have to re-do some of this after the upgrade, but I would prefer not to have to re setup all of my home screens, re-install apps, lose my app data, etc...
I understand that titanium backup can help make this a lot easier, but the question remains... if the official OTA update doesn't require a data wipe, why do these un-official updates?
Thanks,
~ Andy
ydnandy said:
I've been doing a lot of reading on this forum trying to find the best way to update to Froyo... seems like every ROM says it requires me to wipe my data. I'm curious why that is? The official OTA update can update to Froyo without wiping my data, so why can't any of the ROMS on this site do that?
I'm just looking to update to Froyo and then customize it how I prefer.
I am already rooted, removed all the sprint/htc bloatware i dont want, customized my boot up animation, and changed the sprint banner... Certainly I will have to re-do some of this after the upgrade, but I would prefer not to have to re setup all of my home screens, re-install apps, lose my app data, etc...
I understand that titanium backup can help make this a lot easier, but the question remains... if the official OTA update doesn't require a data wipe, why do these un-official updates?
Thanks,
~ Andy
Click to expand...
Click to collapse
1) This should be in the Q&A section.
2) I can't speak for the Evo, but my wife's Moment, when it was upgraded to the official 2.1, did not require a data wipe either.... Because the official update did the data wipe for you. Either way, she lost all her data. I suspect this is the same for the official froyo.
3) If you want things to go smoothly, always do a backup (nand, TB, etc) and always do a full wipe before flashing a new ROM. In some cases, this applies to themes and other upgrades. If you don't, it's on your hands if things go awry.
this is as i understand it. perhaps we'll get lucky and one of devs will come in and clarify this point for us.
quick answer:
when you call your IT guy with a problem what is the first question they ask? "when did you last reboot?" and then they have you reboot anyway. does that solve all problems? hell no. but if you knew how many times it did you'd understand why we do it.
... "did you wipe" seems to be that same kinda question.
what i think:
There are several partitions used by Android. and much like its big brothers the Linux OS's...the use of these partitions is well guided but not law. hence, some folks feel that dataX should be here and others feel it should be there.
there can also be configs that would conflict (things like HTC Sense are very deeply intertwined into the Android OS so an AOSP build would have conflict).
hence, to ensure that you (the end user of whichever ROM) have the best experience it's best to have you start with a clean slate. (it's plain old step one troubleshooting especially when dealing with so many non-techie folks)
once you have more familiarity you'll notice some folks don't wipe...but if they have issues, you'll often hear them go do a full wipe and report the issue was resolved. this is more true when upgrading...not so much when transitioning.
since the OTA was developed by the same organization that developed the existing OS...no wipe is needed.
the same can generally be said for those of us using CM6 and then flashing the nightly builds
the same can generally be said for those using Fresh ROMs and flashing updates provided by Flipz.
the same cannot be said for someone coming to CM6 from Fresh. much difference.
basically, the rule of thumb is "when in question...wipe". why? because if you don't and if you experience issues you may assume the ROM is bad or the dev is an id10T. then the non-techie may erroneously post such comments...causing a stampede. the board gets filled up with 'this rom sux' and 'plz help' for things that would have been a non-issue had a wipe been done.
I am already rooted, removed all the sprint/htc bloatware i dont want, customized my boot up animation, and changed the sprint banner... Certainly I will have to re-do some of this after the upgrade, but I would prefer not to have to re setup all of my home screens, re-install apps, lose my app data, etc...you can try using Titanium. it worked well for me when moving between Sense based ROMs. it will save most of your settings. it had issues when i transitioned to CM6...so i had to reconfigure my email, IM, desktops, etc.
when you flash a new ROM, expect your custom boot animation to be reset to whatever the dev chose...but using PushBoot makes it very easy to fix.
if you use adw (mabye launcherpro) you can export your settings and then import them after the flash
you won't loose the pics/movies/mp3/etc by doing a sd:ext wipe. (just in case you were concerned)
For two months I have tried to install Cm6 and currently shadow rom. Every time after install from clockwork or nandroid I get the same bootloop splash htc screen. I have installed other roms with no problem....there must be a common issue with cm6 & shadowrom. I have wiped full, cache, davlik and even formated system cache etc. I have a 2.x radio kouche kernel and newest hboot. I've tried changing sd cards etc. No avail......any suggestions would be appreciated.
SamuraiXDroid
I would try wiping dalvik/cache before the flash, flashing, then wiping dalvik/cache again before the first boot of the new rom. I would also suggest trying kings kernel or koush's test kernel by flashing them from cwm recovery directly after the rom.
Aside from that, I could only guess that you might have a corrupt area preventing a full install of your rom/kernel which isn't too uncommon but which I have no experience with. I've heard there are ways to get around this by building the kernel manually or by restoring it from another nandroid (say king's on a ruby nandroid? though I'd venture to guess Ruby would have the same problem), but it seems fairly difficult.
I'm not a developer, but I hope my suggestions can hope point you in the right direction. I'm using the latest nightlies of CM6 and they are awesome. I hope you get the chance to try it.
Thanks jaguox for such a quick reply. So I tried this.method on both cm6 and shadowrom. Wiped full wiped cache wiped davlik. Installed rom and gapp and kernel. Tried koush and kingkernal....wiped davlik...cm6 boot loop.....shadowrom brings me to android touch screen initial setup. I try to touch screen but my phone dosnt respond....screen freeze. Sussesful installs I've had are sky raider virtuous most.sense roms...the only froyo I have that works is ruby...my fav right now. I would love to have cm 6....I've posted on this forum a few times as well as cyanogen forum. I hope im not the only one with this.issue.......
SamuraiXDroid
Here are some more ways to potentially solve your problem. Again, I am not a developer so I am just mentioning a few solutions that might work, I am not entirely sure what is wrong with your device. I'm just trying to help you hammer away from all sides.
Are you wiping data manually too? People have noted success before where they had none before by wiping data/dalvik/cache twice before flash and once after. Not sure why this would solve anything but it is worth a try.
Try installing cyanogen without GApps (I do this anyways with the nightlies since it seems to be corrupt for some reason) and then installing them later if it boots correctly.
I use the Paid rom manager for the ease of use for nightlies, but here is a web link to the nightlies which you can try if you don't have paid: http://mirror.teamdouche.net/?device=inc They are more up to date and stable at this point than 6.0.2 was (for me at least). I am using build 100 and have tried the packaged in kernel, koush test 6, and adrynalyne's, and all work well.
Adrynalyne has another kernel for AOSP roms you can try: http://adrynalyne.us/?p=79
You can also try using the phone to reformat one of your SD cards just to eliminate that potential pitfall, though I don't think you would be getting that far anyways if it was not formatted correctly (Menu>Settings>SD card). This will wipe any data currently on your SD card.
Now, I would wait for someone else to provide confirmation that this should work since I haven't done it personally, but you could also try restoring boot.img from a Ruby Nandroid with KK1/2 installed (Install Ruby, install KK, make nandroid backup, install CM6 w/o Gapps, nandroid>advanced restore>select ruby nandroid>Restore boot). This should restore a working AOSP kernel for CM6/shadow to use however I am unaware if there are any other consequences. I also suggest KK or adrynalyne since I do not know what Ruby uses and KK and adrynalyne have both worked for me on CM6. The reason I think the kernel is not installing correctly is because your touchscreen is not working and AOSP roms use a different driver than sense roms for it. I could be completely off base however.
Also, out of curiosity, which radio version exactly are you using?
Hi Jaguox,
Thanks again for the help here is what I tried. I do own the market app ClockworkMod Revovery v2.5.0.5/rom manager. I came from Ruby 1.1.1 with the newest kouch Kernal and radio 2.15.00.07.28. I then wiped data, cache and dalvik twice. I then installed cm nightley 96&98/shadowrom (two seperate installs of course for each rom). I then installed Adrynalyne/Kingkernal kernals and wiped dalvik cache once more. I did not install gapps and let the rom boot. Interesting enough the roms bypassed the intial setup and booted to the home screen. But both roms with both kernals still would not let me have touch access to the screen. So I could see the roms but I couldnt touch them...aaaahhhhhhh the irony. I also tried a reformatted sd card.....same outcome. One time out of the hundred I have tried in the past two months allowed me to initiate my account in a cm nightly and access apps. I rebooted after a fix permission and got a boot loop. That was the farthest I have ever made it. Its strange that both these two roms that share the same dna give my phone the same effect. I appreciate anyones help in solving this mystery.
Thanks in advance!
?
SamuraiXDroid
Same issue on my Dinc. I have.wiped, rewiped and.still.the same out come on 2.1. I did not have this issue when I installed the first release of SR a while back. I have no other issues with other ROM's. Help?
Sent from my ADR6300 using XDA App
So shadow rom first release woked for you? There must be some common denominater for why our phones cannot take certain aosp roms? Ruby works but not cm6 or shadow......very strange.
So I think shadow rom found the fix to the issue I was having....hopefully this thread helps anyone in the same vote as me.
http://forum.xda-developers.com/showthread.php?t=808972
I think i've just got my head around ROMs and all the other millions of acronyms. I do like the look of the Oxygen ROM, only i'm not a fan of the green icons in the status bar, is the colour changeable, and does anyone suggest Oxygen as a good ROM to flash for a first timer?
I must add i love the dark bar and prefer having a dark background, so silver/bright etc task bars are a no no
Cheers.
Oxygen is a great ROM, but i would reccomend u go for a froyo rom first so u got more options with themes and such. but rly its a matter of taste and what u want .. stability or experimental.
Experimental: CyanogenMod 7
Stable: eMIUI, Oxygen 1.0.4
Sense roms?
Hmm im using Sense HD port now, since everything works. its stable¨
im using InsertCoin with my own tweaks and theme
u can allways check out my FroSTeD GingerBread theme for Oxygen 1.0.4^^
Rom and theme here
BUT, if u decide to go for a Android 2.3 Rom i rly recommend CM 7, Oxygen 2 RC7 is just as good but less theming options i think.
Heres a nice theme for CM7 Rom
Clicky
I tried the insert coin 1.8 and got caught in a never ending bootloop lol.
I have Leedroid 2.3d A2SD. It's slick and stable and had no issues with it.
grentuu said:
I tried the insert coin 1.8 and got caught in a never ending bootloop lol.
I have Leedroid 2.3d A2SD. It's slick and stable and had no issues with it.
Click to expand...
Click to collapse
then u did not do it right. read the whole first page. then u can complain if u did everything 100%. ive not had 1 single rom on bootloop. to get insertcoin to work u need EXT 4 partition with 1gb recommended. its not hard if u actually read what to do istead of just trying the easy way like Leedroid is. and leedroid was boring and old news
Well im now running on Oxygen 2.3.2 which is really nice.
However...i keep getting a message saying "The application settings (android.process.media) has stopped unexpectadly. Please try again"
This is ALWAYS the case when i choose the "sound" option from the settings menu.
Can anyone shed any light on this?
It means you didn't wipe properly before installing the rom. Boot in to recovery and wipe cache and dalvik cache (under advanced) start up and see if the problem persists, if yes you need to do a full wipe(data/factory reset, cache and dalvik cache).
Shall give it a go. Odd seeing as i did wipe it all before 0_0
Also, i assume if i factory reset, is that from the recovery menu, and then re install the ROM?
Yes, all wipes from recovery and then reflash the rom. Keep in mind all the data on the phone will be gone.
Exactly the same problem...i'm using Launcher Pro Plus if that's any help.
This is precisely why i've put off flashing ROMs for this long, to prevent naffing up my phone, and now
Well if you don't want any issues I don't understand why you would install a RC, also I'm pretty sure the fc is not a rom issue but a user issue.
If you did everything correctly you should have a normal functioning rom (except form the know issues), even with launcher pro plus cause i have the same setup.
Have you ever disabled signature verification? If yes there is a small chance your issues are caused by a corrupted zip file.
If you can't get oxygen to work and want a really stable custom rom use Leedroid. If you are done with rooting and custom rom's just run the latest RUU.
Thanks for the quick reply, where can i access the lastest RUUs to flash them from please? I may well try again at a later date, but it seems too much hassle currently with having to reset and change everything *sigh*
I've just reset to the last point using Nandroid before i flashed the ROM. I've still got root access which is good, but everything runs back to normal now.
A brief foray into the murky waters lol!
mrfish123,
Pretty sure I know what is causing your problem as I recently resolved this issue myself. If I'm right you did a full wipe before installing, but the issues started after restoring your apps (titanium backup?).
What I was doing was wiping and then restoring all apps with data. Lots of these are system settings/apps which come from the old ROM, so in effect you re restoring all the stuff you wiped in the first place.
What you need to do is:
Wipe (system wipe from recovery, and do the chache and dalvik cache too for good measure).
Install ROM
In Titanium select 'restore missing apps with data', but before you run it, go through the list and uncheck absolutely everything which is not obviously an app you have installed yourself, so anything HTC, system etc. You only want to restore your apps.
Once I did this I had no issue installing a custom ROM, and have had no problems running it for over a week.
auraxsense!
Redux-RC2.1 (Gingerbread 2.3.2) highly recommended - smooth and fast
http://forum.xda-developers.com/showthread.php?t=896213
running leedroid atm, so far everything seems nice
So I have a Kindle Fire, and it had 6.3. I used Fire Utility to root and install TWRP. Then I installed the MoDaCo Rom 6.3. I am thinking I would now like to install an ICS Rom instead. Looking around, I was thinking of using the latest Reloaded ICS Rom. But most of them look alike as far as features go. Any suggestions on which is best right now? I am looking mostly for stability and lack of problems. Let's say I install the latest Reloaded ICS Rom today, download and install and configure a bunch of apps, and then in a couple days, they release a newer/fixed version of Reloaded. Can it be easily upgraded without losing all of my apps and settings and customizations, or does everything need to be wiped clean and reloaded again? Thanks for your replies!
Welcome to the boards! So in my opinion, every user experience will be different since everyone will use their device differently. Further, you will likely have SOME issues that you may have to live with. (Even on my HTC EVO phone, the rom I use had been in development for many months after I switched to it!).
I am a casual user, primarily using my Kindle for basic browsing, email, Facebook and some games. I am currently using Reloaded, and absolutely love it... but there are some issues with it that I can live with, such as powering off being a bit troublesome. There are threads for all of the common issues with workarounds for the mean time.
With regards to upgrading within a rom type, it will depend on how substantial the update is. Most incremental updates should allow you to simply flash over your existing rom, wipe cache and dalvik, and you maintain your set-up. However if there are fundamental changes to the rom, you may have to perform a clean wipe. Generally speaking though, I think the devs have been good about letting the users know if a full wipe is required for a given new version.
Hope this helps!
(And, if I'm inaccurate anywhere here, other members are more than welcome to correct me. )
Ok, so major revisions may wipe require everything to wipe, but minor/bug fix releases I should be able to flash over-top and maintain my apps and settings. Sounds good to me! I think I will try going to Reloaded this weekend. Anyone else have suggestions? Thanks!
Titanium backup makes switching between Roms/updating easy... make sure you do the pay version if you plan on switching a lot... one touch restore for ALL of your apps at once is very nice and worth the money
Sent from my Kindle Fire using XDA
Most of the ICS roms are pretty much the same.
I recommend gedeROM v1.2 and Energy™ ROM
Hey guys, I just rooted my DZ and now I’m ready to switch to a custom rom (I’m currently on stock 2.2 sense rom). After doing some reading I think I want ILWT. As I have never done this before I would feel more comfortable knowing what I’m doing rather that regretting something latter. So here goes
First of all, if I first wipe data/cache with superwipeG2 and do a nandroid backup, will the backed up rom work after restore? (I would like to back up the stock rom, without the apps I installed).
Second, I know I need to wipe everything with superwipeG2 before going to ILWT, but should I also do a factory reset?
The most important thing is will ILWT run ok without eng-hboot, as I did not flash it during rooting (I didn’t feel comfortable with that)? From what I understand ILWT will automatically flash a new kernel with all kinds of goodies? I don’t need a super extra fast rom, I just want it to be reasonably stable so I’m guessing I’ll go with ILWT kernel. Also, how wide spread are the GPS issues, does everyone suffer from it or it just happens to some people?
So what do you think about my choice and is there anything else I should know before I proceed? All your answers would be much appreciated, thanks
ILWT is the best and stable ROM if you ask me. I just recently left it to play with the ICS ROMs floating around. I had no issues with the GPS while I ran ILWT. I have GPS issues now with the ICS ROMs, but I expected that. I would flash the hboot if I were you. While it seems intimidating, it actually isn't and very easy to do as long as you follow all the instructions on the rooting guide.
I didn't do a factory reset, but I did do a superwipe and wiped cache/data/davlik just to be safe.
As far as the OEM ROM goes, http://forum.xda-developers.com/showthread.php?t=1442988 is a GREAT resource to go back to OEM specs and has a nifty directory with all the official OEM ROMs.
Hope this helps a bit. I'm also a noob at this ROM thing and have learned a ton while reading all the info on this forum.
ILWT is the best in stability and speed, and it is a super extra fast rom
i think superwipeG2+ will wipe your /system partition too, which contains the rom, so if you super wipe, then backup, you won't be backing up anything... maybe
what i'll doo is just wipe data/factory reset and then flash ILWT, and then reboot... that's it
Thanks for the advice guys. I’ll flash the rom first thing in the morning
liud said:
Thanks for the advice guys. I’ll flash the rom first thing in the morning
Click to expand...
Click to collapse
No prob... I'm happy to help
———————————————
i didn't mean to flame you, nor to mock you in any kind of way
If you want a nandroid of your current rom without the apps and such just do a factory reset before you do the nandroid. Of course this may be silly for you would have the same affect as just flashing the rom later. Get an engineering hboot, well worth it. Then do a superwipe (I also wipe everythin else cause I'm a little ocd, even fastboot -w) and then flash away. Remeber when you have a rom the way you like it, even a week or more for now, do a backup and then if you screw up in the future you'll be saved
Sent from my HTC Vision using xda premium
ILWT is about as fast and stable as they come. If you are used to Sense, and like things such as the Sense widgets and camera, you may miss them. Otherwise, ILWT is one of the best out there, and you will not be disappointed.
Anyway, if you make a nandroid, you can always go back if you don't like ILWT (or any other ROM for that matter). Nandroid is pretty awesome, as it will restore the complete image of the system when you backed up, with apps and data intact, just as you left it before flashing the new ROM.
I'd say the GPS issue only happens to a small minority of people on ILWT and other versions of CM7. I didn't have the issue with the GPS not connecting at all, but apparently some people do. And its an issue that has popped up for some people from time to time, on various CM7 builds in the past. I did have an issue with GPS fix being slower than on stock Sense (maybe 2 minutes versus 5-10 seconds), and the following fix did the trick, and got me consistent GPS fix in seconds:
http://forum.xda-developers.com/showthread.php?t=1472870
At least one user used the same to fix his issue of no GPS fix, after I suggested it:
http://forum.xda-developers.com/showthread.php?t=1616627
Again, thank you all for your help
My DZ just got some ILWT love and its running perfectly ))
Does anyone remember Pyromod Mecha Micro ROM? I am still using that rom, and it was the fastest and saved a ton of battery life.
Is this ILWT rom better then pyromod mecha micro?