updating Validus rom - Ground Zero ROMS Q&A

I updated my bacon Validus ROM by simply downloading the latest update and flash it. It seemed to work.
However, on the forum I read you need to wipe system, data, and cache for every update in TWRP.
Is this really necessary? And if so, why is flashing the update over the previous build not recommended?
Thanks in advance!

CidAndroid said:
I updated my bacon Validus ROM by simply downloading the latest update and flash it. It seemed to work.
However, on the forum I read you need to wipe system, data, and cache for every update in TWRP.
Is this really necessary? And if so, why is flashing the update over the previous build not recommended?
Thanks in advance!
Click to expand...
Click to collapse
It's not mandatory, but it's recommended. Because if there's any issues, we want to make sure it's not caused by dirty flashing. But most of the times you will be fine with dirty flashing. If you encounter any issue, be sure to make a clean flash before reporting it, otherwise you are safe to make a dirty flash until the device maintainer states that you make a clean flash.
Enjoy your Validus

DeHuMaNiZeD said:
It's not mandatory, but it's recommended. Because if there's any issues, we want to make sure it's not caused by dirty flashing. But most of the times you will be fine with dirty flashing. If you encounter any issue, be sure to make a clean flash before reporting it, otherwise you are safe to make a dirty flash until the device maintainer states that you make a clean flash.
Enjoy your Validus
Click to expand...
Click to collapse
It all makes sense now. Thanks for the help!

Related

[Q] Rom + Kernel installation question

Hey Guys, Monday evening, i guess, i'm gonna receive my Nexus 5 32GB White... Well my question is:
After unlocking and rooting, I want to install Catclysm Rom + Franco.Kernel If i delete the Boot.img file inside the zip of cataclysm rom and replace it with the franco's img will it work?? will i have Cataclysm and franco.kernel at the first boot?? So i don't have to reboot again to flash the kernel
Thank you guys for your help
p.s.: In future when cataclysm will get another update, do i have to wipe evrything or just cache and dalvik?? (Before flashing i'll delete the boot.img file inside the zip so i won't loose the kernel)
p.p.s.:Maybe i'm crazy but i need to know these little things xD
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
viking37 said:
Hi,
Yes you can replace the boot.img inside the zip before flashing the rom..., but is it too hard to flash it separately?
With a rom update you can make a dirty flash (only cache partition+Dalvik cache) but if there is a new base it is recommended to do a full wipe to avoid some weird behaviors, bugs, etc... In any case if you do a dirty flash and you have some issues, you'll be good to do a full wipe.
Sometimes the dev recommend to do a full wipe...
For me it's always a full wipe, always begin with a fresh intallation so I'm pretty sure that all will be fine. It makes time to setup again the rom but...
Click to expand...
Click to collapse
Really thank you man, you solved all my questions I know it's not hard to flash the kernel separately but i'm lazy xD
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Enri1196 said:
Oh just another question if i want to upgrade my kernel, do i have to do a full wipe??
Click to expand...
Click to collapse
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
viking37 said:
Re,
Nope... no wipe needed (not even Dalvik/cache partition), just flash and enjoy.
Click to expand...
Click to collapse
Again thank you, i also pressed the thanks:good: button for all your other answers

[Q] Omni to CyanogenMod?

OK, newbie here.
I've had my TF300T for around 2 years (or maybe its just one )
Anyway, I finally broke down and unlocked, rooted and applied the latest Omni ROM to my system without issue.
So far I like it just fine but would like to explore other ROM's as well.
Being a newbie I'm sure if this is some simple question.
Can I just flash my system with a CyanogenMod ROM without doing anything else?
I am using TWRP which seems rather easy to use.
Forgive the newbie question as I'm still learning all the parts and pieces of all this.
Cheers
Did you install the kitkat version of OmniRom? If so, then you can install the KitKat version of Cyanogenmod without a problem. The TWRP version for Jellybean is different than the KitKat version.
Sent from my TF300T using xda app-developers app
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Yeah, I installed the kitkat version of OmniRom so I was thinking it would be OK to install CyanogenMod after doing a wipe first.
Thanks!
ChiefIlliniwek5 said:
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Click to expand...
Click to collapse
Yeah, you shouldn't ever dirty flash anyways though unless you are just updating nightlies. From ROM to ROM dirty flashing is a no-no and could result in FCs or bootloop unless you wipe data.
ChiefIlliniwek5 said:
I shouldn't think it would be a problem, especially if you do a clean wipe first. I know there's a lot of discussion and debate about when you can dirty flash or when you should clean flash, but I like to play it safe so I always clean wipe if I'm switching roms JMHO.
Click to expand...
Click to collapse
Can you define clean flash?
Other than Dalvic Cache and Cache what other things need to be wiped to constitute a clean flash?
ricktendo said:
Can you define clean flash?
Other than Dalvic Cache and Cache what other things need to be wiped to constitute a clean flash?
Click to expand...
Click to collapse
Wiping /data & /system

will dirty flashing make my device slower?

iv'e been dirty flashing new updates to the rom iam using (euphoria) ever since i first got it, and was wondering if i should do a clean install once every few versions.
1. if i dont have any bugs, any point in doing a clean install?
2. does the device get slower after a few dirty flash upgrades?
thanks =P
DjDafiDak said:
iv'e been dirty flashing new updates to the rom iam using (euphoria) ever since i first got it, and was wondering if i should do a clean install once every few versions.
1. if i dont have any bugs, any point in doing a clean install?
2. does the device get slower after a few dirty flash upgrades?
thanks =P
Click to expand...
Click to collapse
No to both questions. I dirty flash every cm12 build and I can't attribute slowness or bugs specifically to a dirty flash.
Euphoria isn't cm but its still android and the same basic logic would apply. I would clean flash when switching Roms, not necessarily when updating to a later version of a ROM.

[Q] Flashing the CM12 Nightlies

Hi all!
First off, I apologize in advance if this is a dumb question. But basically, I'm running a rooted One and I've been waiting for the official nightly builds for CM12, but now that they're finally here, I can't seem to flash them. I keep getting random errors when I try. I'm currently running on the latest 11s update that was OTA with TWRP, and I've unlocked my bootloader and everything. Anyone have any input? I've read in some places that you can't update to the CM12 nightly from 11s, and if that's the case, what's the best way to go from 11s to 11 without losing any data?
Thanks in advance!
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
timmaaa said:
There's no reason why you couldn't flash CM12 while coming from CM11 or CM11S. Are you making sure to wipe before flashing? I's very important to do that when switching ROMs, and even more so when you're flashing an entirely different Android version. You need to perform a full wipe (system, data, cache, and dalvik cache) before flashing the ROM, this will not affect your personal data on the internal storage (the virtual sd card). It will wipe your apps though obviously so just make sure you back them up with Titanium Backup beforehand, and you can restore them after the new ROM boots up and you install TiBu again (just don't backup/restore any system apps or settings, that'll cause problems).
Click to expand...
Click to collapse
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
CaptainBlackbeard said:
Do I absolutely have to wipe? It says on the blog post from Cyanogen that there's no need to wipe. I'd like to circumvent that if possible, I just like having my sms logs and homescreen and such.
Click to expand...
Click to collapse
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
timmaaa said:
You need to wipe. Every time you flash a ROM you must wipe. There are plenty of apps that can backup your SMS for you, and your homescreen should be easy to set up again.
Click to expand...
Click to collapse
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
I'd wipe even going from CM11 to CM12.
Transmitted via Bacon
soralz said:
According to CM blog...
CM11>CM12 no need to wipe btw, unless you want to downgrade. But CM11s>CM12 DOES need to wipe. An S makes a huge difference.
Click to expand...
Click to collapse
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
No, can't, unless you wait for CM12s. But I guess you can backup everything with Ti Backup then restore it back, No harm doing that though.
CaptainBlackbeard said:
Ah, gotcha. I guess as a workaround, is there any way I can go from CM11s to CM11 without wiping, and then from there from to CM12?
Click to expand...
Click to collapse
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
dirty flash
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
dd2 said:
i have dirtys flashing my self is there an app for dirty flashing, i have found app like cyandelta but isnt support many roms only CM12.
Click to expand...
Click to collapse
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
timmaaa said:
Why on earth would you want to use an app to flash a ROM? They're notoriously unreliable, and renowned for causing problems. Couple that with dirty flashing and you're asking for trouble. Just flash the way you're supposed to, in recovery.
Transmitted via Bacon
Click to expand...
Click to collapse
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
dd2 said:
ok, thank you but can i dirty flash through recovery or is always better to fresh flash everytime.
Click to expand...
Click to collapse
If you're just updating the same ROM (flashing a newer build of the exact same ROM) you can usually dirty flash. Any other time you must clean flash.
timmaaa said:
Why the big fear of wiping? Don't you want to do it the right way? Trying to cut corners like that is what causes bugs.
Transmitted via Bacon
Click to expand...
Click to collapse
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
CaptainBlackbeard said:
Well, I went ahead and did the wipe, but now I can't get SuperSU to work and I'm getting the "There is no SU binary installed, and Super SU cannot install it." error, and as a result Titanium isn't going to work correctly, and so now I get to redownload everything manually. So I guess that's why I don't like wiping.
Click to expand...
Click to collapse
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
timmaaa said:
Don't give up so easily, or maybe custom ROMs (and particularly early builds) aren't for you if you can't deal with small issues like this, it's part and parcel of all this.
You just need to work out SuperSU. Which version did you flash on which ROM?
Transmitted via Bacon
Click to expand...
Click to collapse
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
CaptainBlackbeard said:
I flashed the version the Oneplus One toolbox had and then updated it on the latest nightly.
Click to expand...
Click to collapse
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
CaptainBlackbeard said:
Alrighty, I'm trying the new version now. As for the installing Titanium before anything else, that's what I had done originally and it didn't work :/
Click to expand...
Click to collapse
Did you read the second part of my post??
timmaaa said:
Well there's your problem. Stop using the toolbox, because it's most likely flashed an old and incompatible version of SuperSU. Just delete the toolbox altogether, it really isn't needed for this phone, plus it seriously stunts your learning.
You need to download the latest beta version and flash that instead.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Transmitted via Bacon
---------- Post added at 10:26 AM ---------- Previous post was at 10:10 AM ----------
Actually, come to think of it I don't think you need to flash SuperSU on CM12, I'm pretty sure they've built root access into Privacy Guard for CM12. So by flashing SuperSU you've probably borked it. Clean flash again but this time only flash ROM and gapps, then install Titanium and you should be prompted to grant root access when you open it.
Transmitted via Bacon
Click to expand...
Click to collapse
The new version you linked worked!
Now I'm attempting a restore through TItanium. How long does it usually take? It's been sitting at 0% on the first app for a little while now.

[Q] - No Calls or SMS OxygenOS or CM12

OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.

Categories

Resources