What would be the quickest way to update a rom. I think some have them built in from what I'm hearing like cyanogenmod, but i'm looking at others like pure android, is there a way to just drop the new pure android rom on top of the old one without starting from scratch and downloading all the apps over again and such? Is it as easy as just not wiping anything and flashing the new rom?
treysmith7 said:
What would be the quickest way to update a rom. I think some have them built in from what I'm hearing like cyanogenmod, but i'm looking at others like pure android, is there a way to just drop the new pure android rom on top of the old one without starting from scratch and downloading all the apps over again and such? Is it as easy as just not wiping anything and flashing the new rom?
Click to expand...
Click to collapse
quickest way.. download the update onto your phone, boot into twrp recovery, flash the rom, and supersu, then just reboot. if you are updating a rom, you dont have to wipe. if you are flashing a different rom, then you have to wipe.
Not wiping between flashes is known as dirty flashing and is generally only doable within the same rom. Pure nexus rom I know though if you're going from lollipop to marshmallow the dev is instructing a full wipe. It MIGHT work dirty flashing but I highly highly doubt it and honestly in the time it would be to dirty flash then have to restore a backup you might as well backup apps and clean flash it.
Just always look in the update post, if the dev says clean flash do a clean flash, its a shocker to some people but devs generally know what they're talking about when it comes to their rom.
if you are going from 5.1.1 to marshmellow, what you can do is make a backup in recovery, then flash the update. if toj do have issues, you can always restore your backup, then do a clean flash(wipe).
Related
I was hoping to flash Paragon tonight, but it said to flash to stock first and I had a few questions.
Why do some ROMs have you flash to stock while others you can just flash through ROM Manager?
Is the Stock backup I made through ROM Manager sufficient as a subsitute for an Odin flash?
If not, are there any Mac alternatives out there?
I'm trying to get a good understanding of what I'm tooling around with so I don't brick my phone.
Thanks for the answers
I wish I could answer all your questions, I'm guessing it's because the recovery uses a zip file and it does not update everything that odin would. Anyways, if you need any help flashing to stock I know that the FAQ page of the cognition rom found here has directions.
cognition.theidiotshideout.net/mw/index.php?title=ODIN#One-Click_JF6
It is not needed but many think it is best. Depending on the rom you are on you have a cocktail of lag fixes and kernels. Flashing stock gives a clear slate.
You can disable lag fix, delete davlik cache, clear cache. You should be fine but you may run into issues. May.
What are you running?
It's some sort of ancient lore past down from priests of captivate forum antiquity.
As for 'cocktails of lag fixes and kernels,' there is no reason your cwm install can't format those partitions, particularly in light of the fact that it has built-in support for ext4. I don't know why people think the stock flash functions are particularly better at dealing with it.
Do yourself a favor, make sure you have a working download mode combo, purge your mind of the flash to stock FUD and obliviously commence to flashing one froyo ROM right over another. You'll be glad you did.
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
wmbenham said:
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
Click to expand...
Click to collapse
It is like a default disclaimer to flash stock. If you flash the rom and have an issue, one if the first things they will ask is did you flash stock. As mentioned almost all lag fixes use some form of ext 4 filing and most clockwork recoveries can now handle ext 4.
So in summation you do not need to, if you flash and get stuck in a boot loop you need to. I would make sure you can get odin up and running, and recognizing your phone in either case just so you know you can use it if needed
Absolutely no need at all to flash to stock
Would you install Vista in order to install Win7?
As long as you format everything in CWM before you flash a new ROM, then everything is a clean slate. It'll wipe your stock install, so why install stock first?
This and the 're-calibrating' your battery are the two biggest FUDs about Android.
Stock Rooted OTA 4.08.605.15 710RD Rom
OUTDATED: NOT THE LATEST STOCK VERSION!! 4.08.605.19 is now available.
Thanks goes to soniclude for the ota pull.
Stock Rooted OTA 4.08.605.15 710RD rom. It is rooted, zip aligned, has busybox and comes in odexed or deodexed versions. Other than that it is untouched. Enjoy
[standard flashing disclaimer here]
Wipe everything in the mounts and storage menu in recovery, except sdcard and emmc. Then flash like any other rom.
DOWNLOAD ODEXED - MD5
DOWNLOAD DEODEXED - MD5
If you want a little more customized and tweaked rom check out Touch Of Blue, also updated to 4.08.605.15. Touch Of Blue v2.2
Current OTA or a leak?
nfiniti9 said:
Current OTA or a leak?
Click to expand...
Click to collapse
Latest ota that is being delivered in groups to people as we spaeak. This is a pull from someone who recieved the update yesterday.
?
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
ironside2011 said:
What are the instructions on how to install this Rom? Wipe everything just like wildstang83s Rom.
Click to expand...
Click to collapse
Correct, i think. It is probably safest to wipe everything, but might be able to be flashed over wildstangs rom.
cool
I'm gonna wipe everything. I've experienced 1 too many bootloops and hicupps specially with cyanogenmod. My Dinc just never seems to like those Roms
Thank you for this. Been thinking of going to a more stockish rom. The latest roms just have too many bugs and quirks for me.
Sent from my ADR6300 using xda app-developers app
1 more
I literally flashed over wildstang83 Rom . I'm gonna attempt another try but wipe the cache and delvik 1st. Wiping everything didn't do anything. I'll report back soon
Not booting..
Not getting to boot animation... I have tried 3 times now.. Wiped everything..Format boot/storage etc... Anyone get it to work?
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Nobody has replied to my post and I have not seen anyone report a trouble free install here so I'm gonna sit on the fence for a while
Did a full wipe and all seems to be working well
?
Just downloaded VR superwipe. I'm gonna redownload this Rom and give it another shot.
wrigbone said:
I was actually surprised and excited to see this update this morning but thought it would be ICS.
Long ago I rooted my phone just for gaining control and removing bloatware but ended up flashing my first rom with WildStang's Gingerbread OTA. After that I applied the "Warm" theme and been happy with that thinking there would be no more updates to this phone.
To the point - my question for you all is what do you mean by flash over? When the OTA is pushed is it just a patch or do they somehow send and entire install which removes the previous version, saves your data, installs the new version, and puts back your data? I don't have a problem with wiping and starting fresh, and it sounds like that is what everyone is recommending, I'm just trying to understand how it would even work flashing "over" my current version.
Click to expand...
Click to collapse
Flash over is just how it sounds. Literally flash on top of your current rom without wiping your data out.
Sent from my ADR6300 using xda app-developers app
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Topsnake said:
If you want to go completely back to stock can you ruu back to 605.2? Then re ota to .15?
Click to expand...
Click to collapse
Yes
I have a question.
I am running an ICS ROM how does this affect me....
Well my QUESTION is this:
What are the procedures to installing this and can I just reflash the ICS ROM I was on before.
The only updates with this push seem to be SMS and Bluetooth, is it even worth it?
Thanks for your time guys....
I performed a data/factory reset, cleared the cache partition as well as did a dalvik wipe but after installing it gets stuck on the white Incredible screen. Any ideas? Perhaps my kernal/radio? I honestly lost track of what kernal and radio I have so I am not sure.
So what's up with this ROM, I flashed like 3 times And it boots up.....then it starts a random reboot and just bootloops continuously. Is there any fix?
EDIT: seems the OTA update was a bust check this out........
http://forums.androidcentral.com/ve.../182357-dinc-system-update-4-08-605-15-a.html
Sent from my Galaxy Nexus using Tapatalk 2
@ cmlusco
So guy - you put this out here and it seems like everyone is having problems. How about some feedback. I'm getting ready to sell this phone in two weeks and want it to be on the current version but I'm not touching this ROM until I hear it freakin works. There are always a few people with issues but I'm not hearing anyone saying "flashed it and running with no problems". Appreciate the effort to get this out there but if your gonna take the time follow through on your commitment.
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
r0shi said:
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
Click to expand...
Click to collapse
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
If it were me i would never dirty flash between bases.
dladz said:
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
Click to expand...
Click to collapse
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
If you are mainly downgrading for S-off, I'd make a nandroid of your 3.0 & flash a new version of 2.7 (just so you don't have any issues while running RevOne). I dirty flashed 3.0 on top of 2.7 to test it out (I couldn't give up my tweaks!), and there have been comments in the Dev thread saying there aren't issues. But like the previous commenter said, it's always best to wipe and start fresh with a new base.
TLDR: Backup, Wipe, Flash clean! Just in case.
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Curly060 said:
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
Click to expand...
Click to collapse
I absolutely don't care who says it's ok or not, i've had a tonne of phones and i've flashed more rom's than i could even mention, when you do a dirty flash you are much more prone to problems, corruption and issues than with a full wipe, don't try to bash someone who knows what they're talking about.
Flashing a rom the dirty way can and does end with problems.
Why do you think people who bug report don't dirty flash? I've bug reported for many dev's for many phones and my reports are consistent and true, that is something you will not get if you don't do a full wipe.
Reason being for this is because no two phones are the same, so for one person it may work perfectly and for someone else it won't, it's that level of inconsistency that means that a full wipe is always recommended.
r0shi said:
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Click to expand...
Click to collapse
A nandroid will include all data on your phone, except what is stored on your 'sd card' partition. So a kernel is saved with a nandroid. So if you are switching between kernels backup and wipe cache/dalvik between.
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.
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.