Develop Bugs

Reverting from CM13 to stock OOS

After using CM13 for a month, I decided to restore my original OOS 3.2.4 backup yesterday in TWRP (I wiped data, system, cache and dalvik beforehand). After restoring, I rebooted system but it would not get beyond the initial OnePlus logo, so i figured there was something wrong with the backup. I realised it only included boot, data and system, but not system image. Anyway I restored my CM13 backup which is working fine, but I would still like to go back to OOS. Will it work if I do the following...
1) Flash stock recovery
2) sideload full 3.2.4 image through stock recovery
3) factory reset in recovery
Could I avoid factory resetting and keep my storage data if I do this...
1) Flash stock recovery
2) sideload full 3.2.4 image through stock recovery
3) reflash TWRP
4) restore my original OOS backup again (boot, data, system)
Sorry if this has been answered somewhere else, in these forums, but the only threads that talk about returning to stock seem to be for OOS users going back to earlier OOS versions or unrooting and/or relocking the bootloader. None of them mention specifically going back to OOS from a custom ROM as far as I can see. I just wanted to check I'm on the right track.
Thanks

System Data is 20.2Gb when running OOS 4.0.1. How to fix?

On a rooted OP3 running OOS4.0.1 with H2OS mod and Viper. Any idea why my system data is so big?

I had it on custom rom. Just did a full wipe. No idea where it comes from but now i'm back to normal.

WNijhof said:
I had it on custom rom. Just did a full wipe. No idea where it comes from but now i'm back to normal.
Click to expand...
Click to collapse
a factory reset or did you wipe everything in twrp and reflash the ROM?

Old data that isn't totally wiped from your storage prior to installation is what causes this. Simply do a nandroid backup, wipe everthing and do a clean install.

Which [Android 8] daily driver to move to from FreedomOS 2.10.4 [7.1.1] ?

Back after a long time.
My OP3
- Freedom OS 2.10.4 [Android 7.1.1]
- BluSpark Recovery v40
On my OP3 I've always been on Freedom OS . Mostly due to
- Being close to stock,
- Debloated
- rooted for ad blocker, cerberus and titanium
However off the late facing lot of issue with network. Frequent drops on VoLTE and 4G networks on both sims. VoLTE sim will often disconnect and I will end with "Dial-> Immediate Call Ended" issue.
=> What would you recommend to use as daily driver ?
Would appreciate if you should add links. Any additional info regarding prerequisites (recovery, firmware etc) will be helpful.

You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.

qhsusb_bulk said:
You can try:
1-OxygenOS 5.0.3 with RenderZenith or Derp kernel.(Do not go for open beta OxygenOS builds, they are abandoned.)
2-Paranoid Android 7.3.1(Nougat but it won't upset you)
3-If camera, VoWiFi and OTA updates are not important, OmniDragon.
Everyone's expectations are different. These are just mine experiences.
You should update your TWRP before flashing, i guess it is outdated; PA and OxygenOS contains their own firmware but for OmniDragon you can use Open Beta 39/OxygenOS 5.0.3 firmwares.
Click to expand...
Click to collapse
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3

hyperorb said:
Thanks. Will check OxygenOS 5.0.3
Any reason why you did not suggest LineageOS?
Also will I be able to keep custom recovery and root with OxygenOS 5.0.3
Click to expand...
Click to collapse
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.

qhsusb_bulk said:
According to my experiences, unfortunately LineageOS 15.1 is not a daily driver on SD820 phones. Used it on Mi5 and OP3, both of them suffered with lag, overheating, shuttering, deep sleep not working sometimes (lost apx.%30 battery per night), bad camera quality. It is good rom, but this issues must be solved.
You can keep root and TWRP on OOS. Process:
1-Flash TWRP and boot it.
2-Make the wipes(dalvik/data/cache/system are must, if you want full wipe of userdata you can select internal storage too.
3-Install OxygenOS zip, custom kernel zip(optional) and latest Magisk beta zip(16.7 today).
Reboot and profit.
Click to expand...
Click to collapse
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?

hyperorb said:
Thank you for helping with my queries.
So it's just like flashing a custom rom. Also If I wipe internal storage then the ROM zip file will also get wiped. Wonder how do I copy it then?
Last set of queries before I flash this coming weekend
- Whch TWRP ? Latest blu_spark should do ? (I remember blu_spark had specific TWRP for OP3_OP3T
- I remember reading about recovery getting overwritten when flashing OxygenOS.. Will it happen with full rom zip
- Any precautions you would like to suggest ?
Click to expand...
Click to collapse
Yes, if you wipe internal storage, the rom will be wiped. But you can just copy it from your pc while you are in twrp.
Latest Blu_spark twrp works fine for me. Will work for you too.
If recovery is overwritten, you can just flash twrp again via fastboot. It won't be overwritten then.
I think there was a way that after you can avoid having to fastboot by just installing twrp again right after you have flashed oos rom and then reboot. But I am not quite sure if it works. Maybe someone else with experience can elaborate. Anyways, the fastboot method will definitely work.

@hyperorb , If you flash Magisk right after OOS, your recovery won't be replaced by Oxygen one.
For recovery, you can use Official TWRP or OmniDragon TWRP.

many thanks @qhsusb_bulk @Harsh862
will try wit latest blu_spark first but will also keep others handy. Will not refresh internal storage for now. Maybe once I get a bit comfortable with this part. Will revert once I update.

OP3 OOS 5.0.3
Attaching link in case someone else need

Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System

I've been on nitrogenos for half a year. Maybe your could give a try

hyperorb said:
Easy breezy.
Thanks to @[email protected] Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Is this offical Rom?

Yes. I downloaded from OnePlus forums

hyperorb said:
Easy breezy.
Thanks to @qhsusb_bulk @Harsh862 Upgraded to OOS 5.0.3
1) Backups ( whatsapp, titanium, nandroid)
2) Remove all security - pin , fingerprint
3) Reboot to recovery
4) Upgrade TWRP to 8.6.1 blu_stark
5) Reboot to recovery
6) Full wipe except internal storage
7) Flash OOS
8) Wipe dalvik / cache
-------
9) Flash Magisk 16 (1600). I'm not sure what happened but it froze at a point with some message about /Vendor . Screen went black which white LED on.
10) Waited for 30 sec
11) Manual reboot to recovery
12) Wipe dalvik / cache
13) Flash Magisk 15.6.3
14) Wipe dalvik / cache
15) Reboot to recovery
------
16) All Ok
17) Reboot to System
Click to expand...
Click to collapse
Step 9 happens to me everytime I flash OOS/OB. I simply wait for the white led to come on, press the Power button for 8+ seconds and phone switches off. Restart in recovery mode and flash Magisk. This time it will install.

Can I stay encrypted when making a clean upgrade to OOS 5.0.8?

I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?

msafiri said:
I am currently on the last open beta OOS, rooted with supersu and twrp-3.2.3-0. I know that i need to make a clean install of 5.0.8, so i shall wipe data/system/cache/dalvik, flash the latest 5.0.8 full zip, then reboot to recovery to flash magisk and then finally reboot to system.
My concern is - my phone is currently encrypted. Can i simply update as planned above, or do i need to take any additional steps to remain encrypted or go to decrypted state.
What could be the advantages of remaining encrypted or going decrypted?
Click to expand...
Click to collapse
Since you are on OOS (though beta), flashing 5.0.8 should not affect your encryption status. Your plan is ok.
Encryption is related to security. Decrypted means lesser security though I have no idea by how much. It is your call.

Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.

abhibnl said:
Yup, switching betweeb Beta to stable OOS will not affect encryption in anyway. Encryption will only be removed IF you manually format your data partition or the recovery does it for you.
Click to expand...
Click to collapse
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?

msafiri said:
Thank you. That was helpful. So in my case, i would have to erase data partition using TWRP to update from open beta to OOS 5.0.8, so the partition would get decrypted. But then i believe clean flashing the 5.0.8 zip would re-encrypt the data partition. Is my understanding correct?
Click to expand...
Click to collapse
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
Yep, i understand the difference in the operations on the data partition now. Thank you once again for the clarification.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
One small addl. info. After flashing TWRP, there is no need to reboot to recovery. Simply flash Magisk right after TWRP and then boot to system. Flashing Magisk at that stage prevents TWRP being overwritten by stock recovery.
EDIT: or you can skip flashing TWRP and boot back to recovery after flashing the ROM and then flash Magisk alone before booting into system. Either way, you save one step.

abhibnl said:
No, when you "wipe data", it doesn't remove encryption. When you "format data", it removes encryption. I hope the difference is clear enough for you to grasp easily.
all you need to do is, if you have twrp, make sure you have OOS 5.0.8 zip, Magisk zip, working TWRP image - available in internal memory.
Then you need to Wipe System, Cache, Data - Do not check Internal Storage/Memory. or simply Factory reset from within TWRP. Then flash OOS 5.0.8 zip. Once it's done, flash TWRP recovery image from within TWRP. At this step, make sure you "reboot" back to recovery. If you will reboot directly to system, it will replace twrp with stock recovery.
Once you reboot to TWRP, flash magisk and you are all set!
Click to expand...
Click to collapse
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
I always download the full OTA zip and flash it manually wiping only system and cache/dalvik partitions, and I never had any issues whatsoever. Sure you will need to reflash magisk since your kernel and firmware will be flashed again.

msafiri said:
I successfully completed the clean flash from last open beta to 5.0.8 and have magisk 18.0/twrp 3.2.3-0. Going forward, can i accept a new OTA update say 5.0.9 directly, or should i have to flash the full zip again? also would the process change when going to Pie later on?
Click to expand...
Click to collapse
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.

tnsmani said:
Since you have Magisk and TWRP, the OTA either will not download or if it downloads, it will not flash. So you need to download the full zip (usually, the full zip will be automatically downloaded when the update detects changes to your system ie. root) and flash it. So long as you use the same above mentioned method to flash the full zip, Magisk will automatically flash going forward and your TWRP and Magisk will be intact. When going to Pie, since it is a different version ie. from Android 8 to 9, you should wipe system, data, Dalvik and cache before flashing Pie.
Click to expand...
Click to collapse
Thanks. That clears my doubts.

TWRP Data encrypted. (Didn't have any lock pattern or code)

I tried installing Corvus OS 14.5
Here's what I did;
1.Downloaded and placed rom .zip into my phone files.
2.successfully Installed TWRP 3.5.0_10-UNIFIED
3.Wiped: Dalvik/ART Cache, System, Vendor, Cache, Data
4.Went to the install section, all folders in random letters and numbers.
Help!
And how do I get out from this situation.

Reflash stock ROM (MIUI 12) and try again with TWRP and Custom ROM.

wojownikhaha said:
Reflash stock ROM (MIUI 12) and try again with TWRP and Custom ROM.
Click to expand...
Click to collapse
I already did. Though, I think I should find a method to prevent this.