I recently decided to try ROMs other than CM. Blisspop came highly recommended. Since I didn't want to go through the pain of backing up my entire data ,I decided to dirty flash the ROM. The ROM is great, but the only problem is I'm not able to use the theme engine. As soon as I open the app, it crashes.I don't wanna clean flash. Any ideas to help me out of my predicament?
( The phone was running CM12.1 prior to BP)
Edit: I tried clearing the cache and the data before posting the question. A dalvik and cache wipe followed. Nada. I then dirty flashed the Tesla ROM, ended up with a bricked device. Had to reinstall recovery, and flash BP again. Works now. But I'd like to know what the problem was earlier.
Kishore Raman said:
I recently decided to try ROMs other than CM. Blisspop came highly recommended. Since I didn't want to go through the pain of backing up my entire data ,I decided to dirty flash the ROM. The ROM is great, but the only problem is I'm not able to use the theme engine. As soon as I open the app, it crashes.I don't wanna clean flash. Any ideas to help me out of my predicament?
( The phone was running CM12.1 prior to BP)
Click to expand...
Click to collapse
Do clear data of 2 apps
Themes
Themes provider
Sent from my falcon using Tapatalk
Related
I was wondering how perfect of a restore a CWM restore is.
I was running a custom GB ROM (rocket rom to be exact) and it was running flawlessly. I then decided I might try this new CM9 ICS ROM.
So to be sure about the CM9 install, I figure I'd install from a stock GB Rom. So I first did a CWM backup of my current rocket rom and then I restored an older stock (rooted) ROM. It seemed to work fine. Then.... after reading about the (few) issues wit this new CM9 rom I decided I'd wait a bit longer until a few more of the quirks are worked out.
So I then restored back my Rocket rom backup and even doing the flash cache and davik cache also. But now I notice my once working Rocket ROM is experiencing a lot of SODs.
So now I'm wondering how perfect my restore was. I really don't have a lot of apps or wireless networks and can easily restore my contact list. For that reason, do you think it'll help if I do a factory reset wipe and then reinstall everytyhing....or even go so far as reinstall rocket rom and then reinstall everything else manually without any restores...would that be really the best clean install....or would any of this not make a difference at all and wiping/reinstall a toatl waste of time and my prob is actuaully something else....
Thanks
I could do with knowing the answer to these questions too.
It would be good to get a detailed idiots guide to CWM, do's and don't's etc.
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
abhisahara said:
Well a clean install will surely get you rid of the SODs. There is some app and its data that is conflicting with the system and crashes the whole phone. So if you are ready to clean install everything that will fix everything
Click to expand...
Click to collapse
Sorry for the noob question.... what are SOD's?
adrok76 said:
Sorry for the noob question.... what are SOD's?
Click to expand...
Click to collapse
sleep of death, its the device not waking up properly from sleep
Pus it doesnt include efs, so its not complete backup. Handy if yu stay n same rom version, but thats likely not.
Squicky clean install is always best. Even only app and data recovering thought titanium can mess things up. Make it laggy and nonfunctional etc, Blegh
Sent from my GT-N7000 using Tapatalk 2
1. Install abyssnote42
2. Factory wipe, cache, dalvik
3. Restore your rocketrom backup
That's what i do with my rocketrom v23 backup
Zapped through server hops to XDA forums
its not perfect but its the best so far
all i can say is that cwm is the best and simple thing for me so far and if u get trouble some times while trying to shift from CM9 to normal ics or from gb to ics all I suggest is use redpill recovery from abbysnote
Richy99 said:
sleep of death, its the device not waking up properly from sleep
Click to expand...
Click to collapse
Yeah, mine does that from the clock on Dragon ICS 2.4 when charging it didn't use to, started since I started Dual Booting. 2.5 is out in the next hour or so according to the Dev page. Hope it fixes an otherwise awesome ROM.. Otherwise it's back to single booting and possibly on to Omega 12 until CheckROM is released..
Hey, I just wanted to know if it would be possible to dirty flash CM 12.1 from my current rom which is Pure Nexus Project. Would there be any problems considering CM 12.1 is based on Lollipop? Or should I flash Lollipop first then proceed with 12.1. Also I have no interest in the unofficial releases for CM 13.
Don't dirty flash....
Yea... pretty sure a dirty flash downgrade will have no hope of working...
You could always backup and try, that way you would have a restore point for when it almost certainly turns out to not work going from a MM aosp ROM to a lp cm rom via dirty flash...
I'm sure you already spent more time on this issue than actually doing a clean install would have taken.
Nowadays a clean install means a factory reset in recovery with what you keep all your files and personal data. You make a Titanum backup before flashing, and after you let Google install all your software, you just restore the data to the applications.
You basicly can't retain any system data going from one rom to another, so those setting will have to be set by hand anyway.
Sent from my Nexus 6 running cyosp using Tapatalk
Official CM13 is now out. And don't dirty flash, it probably wont even boot.
as many as are telling you not to dirty flash, i wont. but, i will tell you to make a nandroid backup in recovery first. that way when you do dirty flash, and things dont go well, you can always restore your backup.
So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.
saitek1911 said:
So recently my phone was behaving unstable, took a look at XDA, Flashed a new rom, like any other person here.
SO then i figure out that i cannot log into any third party apps, (facebook, instagram) and figure it may just be a bug with the app itself.
Upon further invetigation, i figure out that this happens on, ANY ROM! Even STOCK rom. i ran a restore back to it's original Stock room, flashed, fixed persmissions, wiped calvik,cache, i tried everything!
Everything is closing, nothing works, phone is slow, laggy, hot and everything is ****ED.
Please help a fellow out, i used roms on all my samsungs, nexus 5, now 6. I'm an experience user. Never had this problem before.
Click to expand...
Click to collapse
Did you try flashing the latest stock rom including userdata,img manualy in fastboot, start with fastboot erase system then flash system, userdata, boot, recovery, cache and that should fix iyour problems.
did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.
simms22 said:
did you wipe your data before flashing a rom? if not, you should have. if you wiped your data before flashing a rom, thus would not happen.
Click to expand...
Click to collapse
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.
saitek1911 said:
Ofcourse i do.
When coming from a other rom, then always clean flash.
When updates from the same rom, you can dirty flash.
Click to expand...
Click to collapse
when updating the same rom, you can USUALLY dirty flash, but not always. so, did you clean flash this time?
Do a factory reset, anyway.
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
I read everywhere that the safest way is to do a full wipe, and since you have nothing to lose it won't hurt, so i think you should.
nickos12 said:
Hi i flashed a month ago aicp to my xperia sp and now i want to install a nightly of the same rom.Do i have to do full wipe or just flash the rom?I am using cyanogen recovery.I am asking this because in my previous rom i installed a nightly update without wiping and i ended up bricking the phone.
Click to expand...
Click to collapse
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
so i sould install the nighlty without wiping?
TechnoSparks said:
yes it is practically the correct way to update a nightly.
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
In case of a problem, clean flashing sometimes aren't really your go-to method to correct stuff. Always assume it as a last resort.. In case you faced any problem do kindly share here.
Click to expand...
Click to collapse
so i sould install the nighlty without wiping?
nickos12 said:
so i sould install the nighlty without wiping?
Click to expand...
Click to collapse
Yes you may
Ok thanks
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
TechnoSparks said:
However do bear in mind that the nature of nightly is that it might have problems after different builds, therefore having a previous build zip handy would really help you. Also backups!
Click to expand...
Click to collapse
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
giannisv6 said:
nickos12 some questions raised i hope you don't mind posting here to spare a new topic
1. So you saying that a new update might/could be worst than the previous, correct ?
2. Do we need a full wipe of everything like first time (data, system, dalvid cache, etc) before install an update of the same rom (nightly 20151214) ?
3. Should i install it via recovery or ota ?
Click to expand...
Click to collapse
Yes, nightly is a daily release where changes are huge in the back end.. Sometimes a simple change can make a build unbootable. Sometimes it introduces new bugs. Sometimes it is better and fixes everything. It is of course a good thing to update to the latest if possible, it is just that it is also vital to know what we're going to face when we flash a new update. So that we can make backups beforehand in case something really bad happens.
If you are installing an update to the same ROM there is no need to wipe anything. Wiping is optional.
↑ Note, if you are reverting to a previous build, you will need to wipe everything as there will be conflicts for the system data. This is why frequent/periodic app backups useful.
You can do either both of them without any problem
Thank you very much.
It's the first time i flashed a custom rom (the AICP 10 successfully :cyclops: ) and i got overwhelmed with all these endless customization options .
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
you wipe cache and dalvik cache then you flash rom on top.
R77 said:
I have the exykings ROM I have magisk, viper and Dolby. I don't really want to do everything new again when flashing. When a new build comes how can I still keep my data like viper and Dolby?
Click to expand...
Click to collapse
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
bober10113 said:
you wipe cache and dalvik cache then you flash rom on top.
Click to expand...
Click to collapse
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
youdoofus said:
Titanium Backup Pro. back up your apps with data, run a batch command to restore them once youve properly installed the new ROM
this has historically been known to cause issues. its always best to factory reset at least once, wipe caches, reboot into TWRP, install new ROM(and GApps, if needed), go into file manager within TWRP and delete the android folder (just for good measure), boot and restore your apps/data with a backup app used before getting into the installation process
Click to expand...
Click to collapse
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
bober10113 said:
lol nuke it from orbit each time because there's a new rom base for that particular custom rom. yeah sure...
5% of the time when there really is an issue with a new build i think i have enough insight to know what to do.
changing rom completely yeah for sure. but i did respond specificially to his question where he was referring on maintaining the team exykings rom from update to update.
Click to expand...
Click to collapse
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
youdoofus said:
more often times than not, the 5% you mentioned are unaware of what to do if an issue arises. i wasnt trying to tell you what to do, moreso just bring it up into conversation for those just-in-case situations
Click to expand...
Click to collapse
If I were to go to advanced wipe when flashing a new build if I were to leave data option alone. Will that keep all of my data or not?
edit:
@R77
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
bober10113 said:
but that's what he says to not do. if you do so you maybe in the 5% and you just may have problems.(wiping all but data is considered a dirty flash)
but what i am telling you is that just wipe cache and dalvik cache and flash rom of the same dev. you should be fine. if you are not fine, and have weird stuff going on use regular factory wipe option in twrp wipe menu.
so one method is called: a clean flash.
the other called: a dirty flash.
on the same rom, dirty flash works fine 96 to 100% of the time. so dont worry about it.
if you flash an other rom from an other dev then clean flash is recommended for sure.
so its very simple as you can see. some have a tendency to make it appear difficult.
Click to expand...
Click to collapse
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
youdoofus said:
ive been flashing ROMs since the OG HTC Evo 4G and am keenly aware of the definitions and consequences of dirty flashing vs clean flashing. The android folder should be deleted irrespective of what youre flashing if we're being forward. I guess we are just going to overlook the hundreds of versions of various rom builds that REQUIRED a clean flash every time otherwise bugs were known to occur.
Click to expand...
Click to collapse
did i make it sound like i was replying to you?
guess i should have quoted him to make it obvious.
and again, if he's on rom A 1.0 and wants to upgrade to rom A 1.1 then no need to clean wipe or del android folder each and every time.
have you ever had an OTA ? samsung dosent wipe clean ure device just because u upgrade. so his question regarding a similar scenario would apply, dirty flash would work fine.
and again as stated before, if there is weird stuff happening then just clean wipe. no need to get nuclear each and every time.
btw various rom builds require clean flashes because they suppose people are coming from other roms. not saying that there aren't situations where continuously dirty flashing the same custom rom all along its progress wouldint eventually mandate ir benefit from a clean flash but i know of no one that clean flashes each time their rom dev updates/increments a build. they/we only do it incase of issues, this is of some sorts an unwritten law so to speak. devs even state it when users ask if they can do as such.