Database Develop

How to root 3T on OOS4.0 ?

Hey,
I bought my phone 2 days ago, after charging it I updated to OOS4.0 through the system updates using VPN, when I got home I unlocked the bootloader but did nothing else afterwards. I'm seeing a lot of threads with people having issues with TWRP and encryption, considering my last device was the OPO and I was running Lollipop (was too lazy to update it ) I'm kinda out of the loop.
How can I root it now that it's running Nougat ? simply flashing the twrp img using fastboot and then flashing the SuperSU zip or is there a different method ?
Any kind of help is greatly appreciated.
Also, one more question, is Xposed working on Nougat ? I had quite a few useful modules on my OPO, wanted to know if that's possible on the 3T as well.

The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.

WeirdSoup said:
The beta builds of the TWRP which are compatible with the OOS 4.0.0 are available. You can find them from the thread.
If you want to use the Xposed modules, you should downgrade to 3.5.4.
Click to expand...
Click to collapse
And where should I download SuperSU from ? Heard the project is being taken over or smth like that

B00steed said:
And where should I download SuperSU from ? Heard the project is being taken over or smth like that
Click to expand...
Click to collapse
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

WeirdSoup said:
http://www.supersu.com/download
Actually, I'm using the Magisk instead. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Is it better to install this instead of SuperSU ?

If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.

B00steed said:
Is it better to install this instead of SuperSU ?
Click to expand...
Click to collapse
It's case by case, and I don't know which one is good for you. Do some research and figure out yourself.
---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------
23Six said:
If you are interested in using apps which detect root or a modified system/bootloader (Android Pay, Pokémon Go, some banking apps) then yes. Otherwise, no benefit of Magisk (v10.2) for you and may as well use SuperSU which is simpler to install.
Click to expand...
Click to collapse
Magisk is open source, and it is also easy to install. You can also install the Magisk modules. It's not a simple root-hide app as many people still misunderstand.

So, with oxygen 4.0.1 the procedure will be the same?

TWRP Stuck Mount password
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers

junostik said:
Greetings guys..
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if you can please help me to root my 3T.
Cheers
Click to expand...
Click to collapse
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Thanks for quick reply, I'll check it.

bertozzi243 said:
I think you need latest twrp beta 1, it should be in twrp tread, look in last pages or here https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------

junostik said:
Installed TWRP 3.0.3.1 BETA .... How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now.
Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
---------blue animation-----------
Click to expand...
Click to collapse
I read that it takes some minutes if you are f2s and encrypted but I don't know how to proceed since I haven't flashed twrp and root yet.
Sorry but you may have to wait someone who has already done it

Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption th

Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption thing. Had to format userdata two times and lost already vital data since fone could't get decrypted after rom installation. What is the safest method to avoid this serious issue and I believe many users like me suffering with the same.
Hope somebody can help.
Thnx
Sent from my ONEPLUS A3003 using Tapatalk

ayyan84 said:
Afraid, I will start to hate my newly oneplus 3t due to this encryption/decryption thing. Had to format userdata two times and lost already vital data since fone could't get decrypted after rom installation. What is the safest method to avoid this serious issue and I believe many users like me suffering with the same.
Hope somebody can help.
Thnx
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
read read read read and read.

the_rooter said:
read read read read and read.
Click to expand...
Click to collapse
Where exactly?? ??
Sent from my ONEPLUS A3000 using Tapatalk

nano303 said:
Where exactly?? ??
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Xda-developers.com threads for said device. Google.com is also your friend.

Could u b precise and share few links. I have done a lot research before wiping my data.
Sent from my ONEPLUS A3003 using Tapatalk

the_rooter said:
read read read read and read.
Click to expand...
Click to collapse
the_rooter said:
Xda-developers.com threads for said device. Google.com is also your friend.
Click to expand...
Click to collapse
Nice useless garbage to fill your post count.
ayyan84 said:
Could u b precise and share few links. I have done a lot research before wiping my data.
Click to expand...
Click to collapse
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.

Spasticdroid said:
Nice useless garbage to fill your post count.
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.
Click to expand...
Click to collapse
so if flash the dm-verity and format userdata to remove encryption, that is a one time thing right? i don't have to deal with the issues whether a custom rom or a kernel is compatible?

Spasticdroid said:
Nice useless garbage to fill your post count.
I've spent the entire day dealing with the similar situation trying to get Magisk to work properly, and ended up removing the encryption.
TWRP 3.0.4-0 and newer may fix the issue now, but if it doesn't, either flash the disable forced encryption zip using the Toolkit, or the one from the TWRP thread, or flash a custom kernel which disables it, like ElementalX or blu_spark, all located in the Android Development sub-forum. I don't use custom ROMs so I won't know if they disable it in theirs. Read and ask them about it.
Then using a PC and fastboot, run "fastboot format userdata" then "fastboot reboot". This will WIPE YOUR DATA so back everything on internal storage up!
You won't be running encrypted anymore, and encryption can be re-enabled in Settings > Security.
Click to expand...
Click to collapse
Thanks for elaboration to avoid encryption but once u r caught into encryption, I think there is no way to decrypt but wiping data which is painful..
I m so still confused about the decryption password..
I have never registered any password for encryption
Sent from my ONEPLUS A3003 using Tapatalk

lpiratel said:
so if flash the dm-verity and format userdata to remove encryption, that is a one time thing right? i don't have to deal with the issues whether a custom rom or a kernel is compatible?
Click to expand...
Click to collapse
Yes. Flashing it once, followed by formatting via fastboot will remove encryption, and that's all you'll have to do.
As for Roms and kernels, as long as the devs have it disabled, you are fine. From a quick lookup on GitHub, ROMs here such as Official Resurrection Remix, Unofficial Unified LineageOS, and Unofficial CM have it disabled. The kernels listed in my other post have it disabled too.

ayyan84 said:
Thanks for elaboration to avoid encryption but once u r caught into encryption, I think there is no way to decrypt but wiping data which is painful..
I m so still confused about the decryption password..
I have never registered any password for encryption
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Well, you can't lock a door without a key, and if no key is made by you the system will have to use a default key created the the encryption libraries, and this is the reason recovery should use the ROMs encryption libraries both for using the correct encryption certificate and default encryption key if the user didn't enter one.
The default encryption key and certificate difference between 3.x, 4.x and other ROMs is the reason for the confusing situation on this phone, and as long as this is the case, my phone will stay unencrypted. ?

Spasticdroid said:
Yes. Flashing it once, followed by formatting via fastboot will remove encryption, and that's all you'll have to do.
As for Roms and kernels, as long as the devs have it disabled, you are fine. From a quick lookup on GitHub, ROMs here such as Official Resurrection Remix, Unofficial Unified LineageOS, and Unofficial CM have it disabled. The kernels listed in my other post have it disabled too.
Click to expand...
Click to collapse
thanks, that's really answer my question and confusion after reading other posts.

oos 4.0.3 rooted - but can't rid of dm-verity and bootload unlocked warnings

oos 4.0.3 rooted - but can't rid of dm-verity and bootload unlocked warnings.
Any help to remove this nagging warning would be appreciated.
-Thanks.
And by the way, besides the irritating warnings, what are the real implications of having this two situations? thanks.

That's the point of these warnings, to let you know that your device is compromited. There is no official way to turn them off.

You would think that if someone stole your phone, you wouldn't want them to know about any vulnerabilities by simply turning it off and rebooting...

Bootloader warning is going to remain there as long as your bootloader is unlocked. The dm-verity comes from allowing the system partition to be modifiable. There's a flashable script you can use, or you can run a couple of commands through fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
That just make the verity problem go away.

tzbigworm said:
Bootloader warning is going to remain there as long as your bootloader is unlocked. The dm-verity comes from allowing the system partition to be modifiable. There's a flashable script you can use, or you can run a couple of commands through fastboot:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
That just make the verity problem go away.
Click to expand...
Click to collapse
The script no longer works on OOS 4.0.3. The command was patched out due to the "security flaw".

Wow so neither of those are usable on 4.0.3 now?

Nope, you're stuck with the dm-verity message at boot now, in addition to the bootloader unlocked message. There is apparently a way to replace the OOS 4.0.3 fastboot commands with those from OOS 4.0.2 to remove the message, but mixing system components from different versions is pretty dangerous. It works for now, thought who knows what'll happen if you try it on future updates.

So flashing a kernel/supersu doesn't work anymore, either, to get rid of dm_verity?

tzbigworm said:
So flashing a kernel/supersu doesn't work anymore, either, to get rid of dm_verity?
Click to expand...
Click to collapse
Those still work. The fastboot commands don't work anymore since the update.
Sent from my OnePlus 3T using XDA Labs

I am rooted with SuperSU and have the latest Franco kernel installed, yet the dm-verity message still persists on boot.

Can someone explain what dm-verity is and how it affects us? Sorry for my ignorance.

SlimJ87D said:
Can someone explain what dm-verity is and how it affects us? Sorry for my ignorance.
Click to expand...
Click to collapse
TL;DR Dm-verity is a security feature that was flawed before OOS 4.0.3. Oneplus fixed it with the latest update, but it means that we can't get rid of an annoying message on boot.
DM-verity is an optional security feature in linux (therefore android). When initially activated, it essentially remembers the state of your phone's integral system files. If at any point after enabling, something changes in the critical system files, it will assume that something has gone wrong (for example, malware with root access) and prevent the phone from booting. The critical system files that it checks aren't the normal system files for your ROM, but rather important files in the boot partition, where an average user would generally not have access to.
Enabling certain features in TWRP will modify some of these monitored files, causing dm-verity to suspect malware and prevent the phone from booting. Rooting your phone after making these modifications can prevent dm-verity from bricking your phone, but it still trips the alert, resulting in an annoying, but harmless message at boot. Another method of circumventing dm-verity is to deactivate it and reactivate it, whereby it would assume your modified partitions is the default version. This was how people got rid of the boot message before, as dm-verity wouldn't be able to detect any changes. Being able to deactivate and reactive dm-verity is a security flaw though, as a feature like this would be pointless if any attacker could just turn it off with a fastboot command. This is why Oneplus patched out the commands.
Most people who install custom recoveries are likely going to root their phones anyways, so it's not going to affect the phone's functionality if dm-verity is tripped. The main gripe I have with it is that now there's a second warning message at boot (after the unlocked bootloader message), which, to be honest, is at most a mild inconvenience.

Delete

https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094

I have the problem of not being able to disable dm-verity on my 3T since 4.0.3, but it's made for a much bigger problem than the "popup" on boot, I now cannot pass SafetyNet (for Android Pay), if I flash back to Sultan CM13, or LOS14.1 (with 4.0.2 firmware and disable and reenable dm verity) it works fine, but even flashing the 4.0.2 firmware and doing the disable enable stuff, SafetyNet still doesn't pass, which is a nightmare.

Anova's Origin said:
I am rooted with SuperSU and have the latest Franco kernel installed, yet the dm-verity message still persists on boot.
Click to expand...
Click to collapse
Can you please start the file you used to root?

ddaharu said:
Can you please start the file you used to root?
Click to expand...
Click to collapse
It was the one included in the OnePlus 3/3T toolkit (v4.5U). I tried rooting with the one on chainfire's website a while back when I was on OOS 4.0.2, but I kept getting stuck in a bootloop. The one from the toolkit worked fine while I was using it.

Anova's Origin said:
It was the one included in the OnePlus 3/3T toolkit (v4.5U). I tried rooting with the one on chainfire's website a while back which I was on OOS 4.0.2, but I kept getting stuck in a bootloop. The one from the toolkit worked fine while I was using it.
Click to expand...
Click to collapse
Hmmmmm. I don't have a pc..... I'll look to see if I can find another. Thanks bro

You can use this one https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094

I suggest you to use chainfire SuperSU to get root..I personally use this .I also tried phh superuser but it's not working properly so use SuperSU

Disable encryption on 7.1.1

Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!

Mephisto_POA said:
Hi guys,
I tried a couple of years ago disabling encryption on my Nexus 6 and the performance was great, but as updates were released it turned out to be a pain to keep up always having to manually update the phone. My nexus 6 now is crawling and I'm thinking about trying to disable encryption. I could not find any sort of reports if it can be done on 7.1.1
Has anyone tried? Is there any guide? Thanks!
Click to expand...
Click to collapse
It's no different. If your bootloader is not unlocked, unlocking it will wipe the user data partition. If the bootloader is already unlocked, you'll need to wipe the user data partition.
*IN EITHER CASE YOU WILL LOSE YOUR DATA. DO A BACKUP FIRST
Then flash a ROM with an included kernel that doesn't force encrypt. Or, just flash a kernel that doesn't force encrypt.
Now that I've answered your question, IMHO, it's not worth the effort. If your phone is crawling, do a factory reset. On a stock ROM, go to Settings > Backup & Reset and make sure you have your Google backup settings enabled. Use the Factory Data Reset button to actually reset. READ through the information and confirm. This will cause your phone to reboot with a wiped system partition.
If your on a custom ROM I'm going to assume you know how to wipe through recovery.

ktmom said:
...., IMHO, it's not worth the effort. If your phone is crawling, do a factory reset.....
Click to expand...
Click to collapse
My 7.1.1 uses the lite stock rom of Danvdh.
I think you're right about the hassle. Only decrypting is not enough. But debloating and removing unused stuff and decrypting the data partition did raise performance on my N6.

Yeah, I know it is a bit of a hassle, but considering there will be no more updates after 7.1.1 it should be a once only process right? Is possible to disable encryption on 7.1.1. without rooting?
I'm happy to unlock the bootloader and wipe the phone, not a problem.

Mephisto_POA said:
Yeah, I know it is a bit of a hassle, but considering there will be no more updates....
Click to expand...
Click to collapse
Don;t forget the monthly security updates.
I am using the lite stock room of Danvdh. It's a pre-rooted stock room.
But I think updates can be dirty flashed because the system, radio and bootloader will not change anymore.
So root and install TWRP to flash the updates

the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption

Mephisto_POA said:
the problem with rooting is that many apps will not work, I'm cool staying without root and vanilla android, I just want to get rid of the encryption
Click to expand...
Click to collapse
In that case the post of @ktmom is applicable.

I am on 7.1.1 and have used the fed patcher mentioned on this site and it has worked nicely on custom and stock ROMs. But u have to be rooted.

NLBeev said:
In that case the post of @ktmom is applicable.
Click to expand...
Click to collapse
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused

Mephisto_POA said:
I'm a bit illiterate in this aspect, apologies. but I could not find a vanilla android for nexus 6 with just encryption disabled and no root. I would really appreciate if you could give me some directions?
The NEXUS 6 ANDROID DEVELOPMENT and NEXUS 6 ORIGINAL ANDROID DEVELOPMENT seems both to have only modified versions. I'm a bit confused
Click to expand...
Click to collapse
Plain vanilla unencrypted would be google factory image plus a non forced enforcing kernel. B14CKB1RD, Franco there are others.
Custom ROM that is close to vanilla but comes with a non forced encrypting kernel would be Pure Nexus.

Mephisto_POA said:
I would really appreciate if you could give me some directions?
Click to expand...
Click to collapse
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/

NLBeev said:
I have only one direction for you and that's the lite stock rom of Danvdh.
The kernel is the modified part. (no forced encryption).
After flashing this rom, you can unroot by uninstalling supersu.
https://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?

saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
That was an answer to a different question.
The ROM you installed I believe has a non-force encrypting kernel. But just installing a non-force encrypting kernel isn't enough. You need to wipe user data and install a kernel that doesn't force encrypt.
Please read back a page to two for the whole recent conversation that has more details, like the fact that you'll lose all of your data in this process.

saltyzip said:
Hi, I also want to remove encryption from my Nexus 6 Stock as it is a stuttering mess.
I have rooted and installed the stock rom of Danvdh, but to my disappointment on boot up the phone is still showing as encrypted.
Have I done something wrong?
Click to expand...
Click to collapse
Got it working, just followed this:
Just because forced encryption is disabled doesn't mean it decrypts you. You have to do that yourself by formatting data either through TWRP (TWRP > Wipe > Format Data button) or through fastboot (fastboot format userdata), which will wipe out your app data and your internal storage partition so make the appropriate backups.

saltyzip said:
Got it working, just followed this:
Click to expand...
Click to collapse
You going to take credit, you should at least use your own words ?

I've gone with your guys suggestion with stock lite, working like a charm, very snappy. The phone feels indeed light, and multitasking is way smoother now, thanks!!!
just on a side note, after you install the rom you need to wipe the data partition to get rid of the encryption

Installed twrp on bn Nexus 6 os 5.1 OTA for 7.1.1 encrypted it
No clue how to fix this I'm a noob unlocked bootloader unencrypted Android 5 then it OTA updated to 7.1.1 and now can't get to twrp to wipe encryption how can I get this going again phones working just can't use cable to computer have the SD card reader micro SD any help would be appreciated

kudabee61 said:
...just can't use cable to computer...
Click to expand...
Click to collapse
Get your phone's USB port fixed, then you can fix the ROM issue.

Help requested with updating Custom ROM.

Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!

Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.

Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?

Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.

DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,

Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.

DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs

Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,

Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.

Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!

Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.

Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.