haven't updated my phone in quite a while now, and was wondering if there is a method to update to latest OOS without having to perform a backup-->clean flash-->restore.
obviously the backup should stay, is it possible to update without clearing data?
what about oxygen updater app?
thanks
knoximator said:
haven't updated my phone in quite a while now, and was wondering if there is a method to update to latest OOS without having to perform a backup-->clean flash-->restore.
obviously the backup should stay, is it possible to update without clearing data?
what about oxygen updater app?
thanks
Click to expand...
Click to collapse
If you are changing Android version, it is better to clean flash. Clean flash involves wiping System, Data, Dalvik and Cache. Internal Storage where your photos and other files are stored need not be wiped. That said, it is prudent to have a backup of the photos and other files stored on your PC/Laptop since you never know whether ultimately you end up wiping Internal Storage also.
Obviously, you will lose root (and TWRP) which you have flash again. For root, Magisk is better than SuperSU on Oreo.
I have no experience with the Updater app.
Related
I want to flash CM10 preview 7. After I install all my apps and want to upgrade to preview 8 will i loose the apps and have to reinstall them? how do i upgrade to a newer version maintaining my apps?
lucapeluca said:
I want to flash CM10 preview 7. After I install all my apps and want to upgrade to preview 8 will i loose the apps and have to reinstall them? how do i upgrade to a newer version maintaining my apps?
Click to expand...
Click to collapse
I'm fairly certain you can upgrade to newer preview without wiping your apps; just flash without wiping data beforehand. However, if you keep flashing without ever wiping data, you'll probably run into issues sooner or later and have to wipe data to fix... I'd recommend flashing version that comments say is safe, and only upgrading when you see a feature you really want added.
I've just been wiping dalvik for the last few updates. Probably will continue doing this until I have a problem.
I'm just wondering why Sprint's ota updates don't require a data wipe, but flashing the stock ROM in a custom recovery needs the wipe? I installed cnexus's rooted stock on my phone and initially tried a dirty flash, but had problems, so I wiped and did a clean install and all is good. My wife's phone is being prompted for the ota and I want to update her but I'd prefer not to have the Knox bootloader. I would simply update her phone as I did mine, but she'll kill me if I wiped her data. So, why can the ota install without the data wipe but the (essentially) same ROM installed manually can't? Anybody know?
An OTA just adds new file, a rom overwrites the entire system, that's why a full wipe is always recommended. I think there is a thread somewhere here that has flashable OTAs though. It sounds like she is rooted, so why don't you use a backup app like titanium?
Titanium is great and you will never have to worry about losing data. Plus its good to clear out the phone every once and awhile to keep it running fresh.
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
savvymatthew said:
When I try to flash SuperSU it fails and just aborts.
I have tried flashing stable and all the beta builds same results. I'll attach a screenshot of it.
Originally I had root with everything working fine but decided to try and update through the update app when I was rooted. This was when I was on 3.2.4 trying to get to 3.2.7. All the update process seemed to do was revert my phone to unrooted and did not update to 3.2.7. Ever since then flashing SuperSU didn't seem to work. I waiting for a full zip. Of 3.2.8 to come out thinking flashing full update would fix it. It didn't.
Everything is running fine on 3.2.8. Just any attempt at flashing SuperSU fails.
These were all dirty flashes.
I have not tried a complete restore to stock yet. Would like to avoid this if possible.
I have no active modifications to my system.
Click to expand...
Click to collapse
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
LS.xD said:
Clean installation will probably fix it and has less risk of potentially bugs compared to dirty flashes.
Click to expand...
Click to collapse
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
savvymatthew said:
Yeah kinda figured that. How exactly do you force a fresh install and? Sorry for the noob question.
Click to expand...
Click to collapse
OnePlus.net offers the rom files as download:
OOS 3.2.6 (capable for OTA 3.2.8)
Open Beta 7
I'm using the Open Beta at the moment and it runs without any issues
OOS roms can be flashed with custom TWRP
For a clean installation just wipe partitions (System; Data; Cache; Int. Storage) with TWRP before flashing the new rom
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Hw4ng3r said:
Just don't be surprised if you wipe your int. storage, you will lose all of your roms and things you've downloaded to your phone. I never wipe int. storage, just Cache, Dalvik, Data, and System.
Click to expand...
Click to collapse
Thank you for pointing on that I backup all my stuff on my computer once a week but others may not.
By never wiping your internal or manually deleting folders you will collect garbage over time when you change android installations.
I have a back up from when i first set it up, so its very old. After i Flash and set everything up again think im gonna start making weekly back ups, with all the roms and stuff for this phone probably be smart.
Thanks guys
I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.
wHiTeWoLf007 said:
I'm running Android Oreo on the Beta line. I've felt that Camera quality used to be better in Nougat, and occassionally phone heats up with Oreo. So I'd like to switch back to Nougat. But I've seen a couple of threads mentioning about a potential data loss(whole internal storage getting wiped) and needing to install a rollback build before installing a stable Nougat ROM. Could someone shed some light into this? Is flashing the rollback build really necessary if I can flash the stable OOS 4.5.1 via TWRP? And, would I lose data in internal storage during the procedure? Thanks in advance.
Click to expand...
Click to collapse
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
tnsmani said:
The info you asked for and the steps with links everything is available here: https://forums.oneplus.com/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
Click to expand...
Click to collapse
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?
wHiTeWoLf007 said:
I checked the thread and noticed that it's all about installing via the stock recovery. My phone's bootloader is unlocked and I have TWRP installed. So my question is, do I really need to install the rollback build? Can I not directly flash the 4.5.1 zip file via TWRP and be done with it? Or is there a purpose to installing the rollback version? I mean I read in that thread that after installing the rollback version via stock recovery, a factory reset should be done(which would erase the whole internal storage I assume?) and then the 4.5.1 zip file should be flashed. If I could use the advanced wipe option in TWRP to wipe the cache, data and system partitions and install the 4.5.1 zip file, do I need to go through the tedious procedure of installing via stock recovery, which would potentially erase my whole internal storage?
Click to expand...
Click to collapse
Why would OnePlus provide the rollback build if there are other reliable methods of downgrading?
I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.
drmuruga said:
I think rollback version is for stock recovery users and data loss + . And if you decrypted your data already downgrading is just flash zip in twrp and no data loss but you keep decrypt.
Click to expand...
Click to collapse
You mean the dm-verity thing? So it will be fine if I flash the Nougat zip file and install SuperSU binaries via TWRP to fix the dm-verity issue? That's what I've been waiting for as an answer. Thanks.
I've been using the G6 Play for about a week now, and first thing I did was to flash a custom ROM. It was complicated, but in the end I managed to do it. However, I'm having problems with the current ROM I'm using, Resurrection Remix (namely the lack of FM Radio, and the fact that it randomly reboots to recovery while I'm using Twitter specifically), so I was trying to upgrade my phone to what seems to be the next release of RR. However, I can't afford to lose my current data because I don't have enough storage space to run Titanium Backup, and most non-GSI ROMs that I know of can be upgraded without requiring the full wipe of data. What I've already tried is the following:
Delete the current System partition but NOT Data
Use Fastboot to flash the new ROM
Return to TWRP to fix the partition, then resize it
Reinstall OpenGApps
Reinstall the verity disabler (Disable_Dm-Verity_ForceEncrypt_08.18.2019)
Install Busybox
Install Magisk
Install Magisk-Props to avoid the "Google Play uncertified" error
Clear Dalvik and cache
Reboot
However, every time I do this with anything but the ROM I'm currently running, the system attempts to boot and after the boot logo appears for a few minutes, it reboots directly to TWRP. (Same thing happens to me at random while using the Twitter app specifically, for some reason!). My question is: is it absolutely necessary to wipe data in order to upgrade a GSI ROM from a version to the next? If so, what is the fastest way to restore all data, and should I invest on an external SD card?
I think it mostly depends on the rom you're using, some of them seem to be more sensitive than others. I know in the past I've been able to upgrade AOSP and Descendant successfully.