Database Develop

New to device and the whole firmware thing

OK, long story short. Came for the nexus 6 and nexus 6p to oneplus 3t. The 6p had to flash vendor.IMG after every new ROM flash. But what is this whole firmware thing in this device? I have tried to find answers before asking but, what should I DO and NOT DO to have a brick? Like, wanting to go from a nougat ROM to an Oreo ROM, but not sure how. And then if I wanted to go from a n/o ROM to a beta, not sure how...then if I wanted to downgrade from an o or beta ROM.......please help

Treat the OP3T pretty much the same as you would the Nexus 6. The only difference is, like you've discovered, that OnePlus provides firmware files rather than factory images.
The installation instructions for the different firmwares (stable and beta) are found in the first few posts of the respective threads:
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240

It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)

Mizart said:
It's pretty much the same as flashing vendor image. OnePlus just simply offers Firmware images which flash the Modem and the Firmware.
If you're gonna be on OxygenOS and Custom OxygenOS ROMs then you wont need to worry about flashing the firmware. Some of the Custom ROMs such as Paranoid Android and PureFusionOS also flash the recommended firmware automatically.
However, others don't and require you to flash a particular fimware image manually. Usually the Firmware to be used would be mentioned on the ROM thread itself.
Once you've Unlocked the bootloader and flashed a custom recovery, The most common process for flashing ROMs which do not have an included firmwares goes as follows:
1. Reboot To Recovery
2. Wipe Cache & Dalvik Cache, System and Data Partitions
3. Flash Firmware
4. Flash ROM Zip
5. Flash GAPPS
6. Flash Magisk/SuperSU (Optional).
7. Reboot
And that's it.
That is the standard procedure for most of the ROMs, but, I'd advice reading the OP Instructions properly first in case theres anything different.
PS. For moving to Oreo from Nougat, follow the same, but be warned, If your current ROM is encrypted and the new one isn't you'll be locked out of your device until you flash the old ROM back OR wipe userdata with fastboot, which wipes the Internal Storage.
PPS. For moving from a Custom ROM to Oxygen OS, best way to go would be to flash the official recovery again and sideload the official ROM zip via ADB (In some cases, encryption still might cause the same issue as above)
Click to expand...
Click to collapse
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?

jamescable said:
That was very informative, thank you!!! Just one more question tho. What would happen if I didn't flash the correct firmware? Like, there is a RR ROM with custom sultan or something that looks like it needs a beta firmware, I'm not in beta firmware, so would I have any issues?
Click to expand...
Click to collapse
I'm not entirely sure but in most cases the ROM would simply refuse to flash. Like for RR, if you don't flash a correct firmware then the flashing returns an "Error 7" and the installation stops. But even if it does flash through, it would either not connect to a network or get stuck in a bootloop, but nothing too serious which you can't rectify.

[Solved] Official Oxygen OS 5.0 boot loop problem for rooted users

Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.

Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.

I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.

Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?

DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.

Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.

fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files

so...the no verity is only for decrypted users right?

fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.

The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.

igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?

Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.

I've triyed this. All good till i flash 5.0 & Magisk & no verity....

Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.

Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,

1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?

MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.

BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.

MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.

raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.

3T - Stock ROM, TWRP, Magisk & OTA updates

Hi,
I have a somewhat general question about different OTA update application methods for OOS when Magisk and potentially TWRP is involved.
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Going forward, I'd like to be in a state where I have a Magisk-rooted phone, able to use TWRP, and receive OTA updates. Generally I've seen these two methods being recommended:
1) With TWRP:
a) download full image from OP site;
b) boot to TWRP, flash said image, followed by re-flashing TWRP as flashing full image restores stock recovery;
c) wipe dalvik & cache
d) reboot to TWRP & flash Magisk
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Now, my questions:
1. Which of the two methods above should be preferred?
2. Could either of the two methods used for OTA updates without losing data nor apps/settings?
3. Is there anything inherently different between flashing full image as in method 1) vs. going for the regular incremental OTA update as in method 2)?
4. for option 2), should b.1 OR b.2 be used? Magisk tutorials page seems to be recommending the latter.

I like to keep things simple, so if I'm going to install TWRP, then that's what I use for updates.
There's no benefit in swapping recoveries, especially since you end up with the same result.
By the way, it's been a long time since TWRP stopped patching kernels to prevent it being replace by the stock recovery. So, your step 1 is simpler:
a) download full image
b) flash it in TWRP
c) flash Magisk
And that's it. There's no need to wipe Dalvik or cache. I've not wiped either of these for years (and I've updated countless ROMs) and I've never had an issue requiring me to wipe them.
Sent from my OnePlus 3T using XDA Labs

Thanks for the reply.
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Any specifics re. Android P releases, or old flashing methods should work the same?

laur89 said:
Hi,
I'm still running 3T on 4.0.3 (as rooting with SuperSU broke OTA updates) and will be clean flashing Android P release once OP releases one.
Click to expand...
Click to collapse
There is nothing stopping you from installing an Oreo version OOS (such as the latest stable 5.0.8). Who knows when stable P is coming. Maybe soon, maybe not that soon?
Just download the full zip, flash in TWRP, and flash Magisk right away (do not reboot before flashing Magisk). Same process BillGoss suggested in a previous reply.
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
laur89 said:
Hi,
2) Without TWRP:
a) restore stock recovery if using custom one;
b.1) restore stock boot image of currently installed android version by flashing it via fastboot; OR
b.2) restore stock boot image using Magisk's 'RESTORE IMAGES' option;
c) reboot and follow through with the OTA update from your phone menu (as you'd do normally with completely stock setup);
d) download stock boot image for the version you updated to, and patch it with Magisk Manager;
e) flash this boot image again using fastboot;
Click to expand...
Click to collapse
I wouldn't mess with any of this. The phone is modded, and it seems that the above process is just trying to "trick" the system into thinking it has never been modded, so you can do an incremental update. For no actually benefit, and just making a much more complicated process.
Full zip makes for a cleaner install than incremental, anyway. You can keep your user data in either case, so again, you aren't gaining anything with incremental (versus full zip) OTA.
---------- Post added at 01:03 PM ---------- Previous post was at 12:55 PM ----------
laur89 said:
Any idea if there's anything specific that needs to be taken care of depending on whether phone is encrypted or not?
Click to expand...
Click to collapse
Well, are you encrypted, or not?
I've always had the phone encrypted, so can only say for certain about that condition. If it is encrypted, it will stay that way. There are a few TWRP builds that don't play well with encryption. But for the most part, just flash the update as stated previously, and you don't need to worry about encryption.
If decrypted, I believe flashing by TWRP will keep it that way. If you flash an update by stock recovery, I think it will force back to being encrypted. But again, I can't say for certain, as I've always been encrypted.
laur89 said:
Any specifics re. Android P releases, or old flashing methods should work the same?
Click to expand...
Click to collapse
The community beta P release is having issue with devices which are bootloader unlocked and encrypted. If the device is just one of those (or neither) and not both, then it seems to work fine in most cases.
For the stable P release, I'm guessing it will work the same as the "old flashing methods" which has been described above. But we won't know for certain, until a stable P build is released.

Few questions regarding rooting and flashing.

Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?

MoistPicklez said:
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
Click to expand...
Click to collapse
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Click to expand...
Click to collapse
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
So installing most ROMs seems fairly straightforward, following
the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything
from the internal storage? So at that point I'd have to copy back
all my ROMs and zips back to the phone in TWRP and flash from
this point correct?
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.

MoistPicklez said:
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
Click to expand...
Click to collapse
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
MoistPicklez said:
So installing most ROMs seems fairly straightforward, following the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything from the internal storage? So at that point I'd have to copy back all my ROMs and zips back to the phone in TWRP and flash from this point correct?
Click to expand...
Click to collapse
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
Code:
adb pull /sdcard
MoistPicklez said:
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
Click to expand...
Click to collapse
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Click to expand...
Click to collapse
Awesome info, big thanks to you my good sir. Finally
on Havoc 2.9 and decrypted. Now just gotta get a feel
for this phone and keep on reading. Cheers!

going to back to custom ROMS

hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks

masterchop said:
hello, I used to be a custom ROM junkie in the past but after some time i got bored and never did it again.
now looking at my current device which i never installed a customer ROM before its quite old as its running Android 8 and i would like to jump to 10 or 11.
I am confident i understand the process but its been a few years and i have some questions:
-for example this is the 1st device i encrypt so i am not sure if this affects.
-the device has no custom recovery so i have to start there but not sure if i have to remove encryption or if its ok.
-Also i would like to see if you have any advice for me or somehting i should pay attention beside install TWRP, format all but storage and install zip file for custom ROM
Thanks
Click to expand...
Click to collapse
You've missed all the fun with the upgrade to OOS 9.
So, you'll need to upgrade your firmware to 9.0.6 because all the latest ROMs require it. Take your time and carefully read https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055.
You do not need to remove encryption (depending on how you upgrade your firmware).
If you've got a locked bootloader (which I'm expecting you do), them you need to unlock it so that you can flash TWRP. And unlocking will wipe all data from your phone. So backup everything you want to keep to your PC.
If you don't boot into recovery after flashing TWRP and install a patched boot image (see https://forum.xda-developers.com/on...ty-disable-oxygen-os-t3922324/post79357241)or flash Magisk, and reboot your phone, you'll lose TWRP because OOS automatically restores the stock recovery.
So the order is:
1. Backup
2. Unlock bootloader
3. Flash TWRP
3. In TWRP flash patched boot image (remember you're still on OOS 5.x so use the right one!) or Magisk.
4. Have fun moving to a custom rom.
Sent from my OnePlus 3T using XDA Labs