So im running CM7
and i want to try some other roms out
but i want to know if its safe to go from 2.3 to 2.2?
if not can someone help me, and tell me how to flash a 2.2 rom coming from a 2.3 one correctly?? Thanks in advance
I flashed from gingervillian1.5 which is 2.3.2 to virtuous1.0.1 then restored back to gingervillain without a problem. I did it thru CWM 3.0.5(downloaded, backed up, then installed from sd with a data/cache wipe).
A Gingervillain-ized G2
Yep, its just fine. Be sure that you flash the latest CWM Recovery 3.0.0.5 before moving between 2.2 and 2.3. Do a ROM manager backup, and a full Data wipe, Cache wipe, Dalvik Cache wipe, then flash the new ROM.
After you have a backup of a 2.2 rom and a 2.3 rom, you can safely move between them with ROM manager.
Related
I am running Skyraider 2.5.2 Sense (Froyo) on my HTC Incredible with Clockwork Mod 2.5.0.1 recovery with Baseband 2.05.00.06.11 & Kernel 2.6.32.15g5e1ad8b. PRI 1.28_002.
I tried to flash the Android DSP equalizer (http://bel.fi/~alankila/android-dsp/) and my phone locked up and I had to nand & Titanium restore.
My phone's happy now but I'd really like the DSP - which is supposedly working on Cyanogen 6.0 RC2.
I have no idea what might happen if I use ROM Manager to download and flash Cyanogen 6.0.0-RC3 at this point.
Sorry if this is a moronic question but any illumination would be welcome. Thanx!
As a rule of thumb, ALWAYS wipe before flashing a rom. The only exception to the rule is when a dev Specifically says otherwise.
My rule of thumb is to manually change roms (not using rom manager). Backup, wipe 2x each (data + cache), wipe dalvik cache,then flash. I have NEVER had boot loops or anything else happen after following that.
As to the dsp, I can confirm that the dsp with eq is NOT working with skyraider. It does work with CM6 though.
Hope this helps.
Sent from my ADR6300 using Tapatalk
what he said. ^^^ ditto. nandroid backup, wipe wipe wipe, install new rom.
I usually backup current rom, download new rom and wipe before installing all from rom manager. I have not had a problem yet.
Sent from my ADR6300 using Tapatalk
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
KR3UZL3R said:
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
Click to expand...
Click to collapse
need more info. how did you go about trying to do this? what steps did you? More info on what you did can help someone figure out where you went wrong. Did you create a nandroid backup before you flashed the ROM? what recovery are you using? Did you wipe data (factory reset), cache, and davlik cache prior to flashing the ROM? If you did make a back up, and can get to Recovery (volume down and power button, then select recovery) I would wipe all data, cache and davlik cache, then flash a nandroid backup. If you didn't make a nandroid backup, I would try wiping everything again, and try flashing the ROM a second time.
http://shipped-roms.com/index.php?category=android&model=Supersonic
THAT SHOULD GET U BACK TO STOCK
Ive just rooted, installed the lastest radio and installed the latest CM 6.1.1
After i rebooted phone it is now stuck in bootloop
Help?
Desire SLCD On telus if that matters.
Oh and i cant go back into Recovery. I can go into Hboot
check your reply on android forums
Restore the nandroid you made before flashing, or do a full wipe (in clockworkmod: data/factoryreset, cache and dalvik cache under advanced) and reflash the rom.
Hey Everyone,
I had Starburst with Data2SD flashed on my Desire with some things cooked in from the UOT. I found the MIUI ROM and I figured I wanted to try it. I made a Recovery backup so that if I didn't like it, I could get right back to where I left off. I flashed the CDMA MIUI ROM which was a mistake because my Desire is GSM (Doh) But I went in to recovery and selected the backup I made before I flashed MIUI and restored it, it restored successfully but when I reboot it just sits at the white screen that says htc and it doesn't go anywhere after that. I can reflash the Starburst ROM and reinstall the Data2SD and it will boot and everything and then I go back in to recovery and restore just the data from the back up and it doesn't boot after that. Can anyone help me figure out where I'm going wrong? I don't really want to start from scratch. Any help is appreciated. If you think you can help but don't understand what I'm asking, either post here or PM me. Thanks. I would really like my Desire to work so I can stop using my dreaded Iphone.
Did you do a full wipe before you restored your backup? Make sure you do a factory reset/data wipe, cache wipe and dalvik wipe (from advanced menu)
If it still does not work, try wipe just the cache and dalvik cache after restoring the backup and see if it will boot then.
I upgraded to the latest clockworkmod 3.0.0.5 and when I switch ROMs, I notice some of my item's are still "cached". For example, I was using Evervolv and then did a wipe of data, cache, and davlik, and flashed the RC1 for CM7. GApps are not packaged with either of these ROMs but when I booted up CM7 for the first time after flashing, GApps are installed, without me doing so. Is there an issue with the latest version of deleting cache or am I not doing enough wiping?
I am running into exactly the same problem. Works fine for flash over but the minute you choose wipe in ROM Manager of do a data wipe in recovery it does not make any difference. Not sure it is clearing anything in cache or data or at least consistently.
None of the other ROM devs have posted this so I am not sure what is going on
I am still messing with it
EDIT: You may want to post this in the ROM thread also so the devs are aware
i had the same problem.. From what i have been ready downgrade to cwm 2.5.1.2 and it should help..it did for me. the new cwm isnt running as good with some of the roms out there.