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.
Related
Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs
Dear all,
I've rooted my phone in July 2018 with the latest stock build from that timeframe. I'm getting notifications of OTA updates for the past 6 months that I've been swiping away and putting off. Obviously I cannot update OTA.
What are my options to update my phone if I want to maintain root? Is there a full build somewhere that I can install via twrp and flash SU or magisk over? Are there fully functional ROMs that I can periodically flash via TWRP to stay up-to-date and rooted? Or am I forced to revert to stock, update via OTA, then re-root?
I'm familiar with rooting but the G6 pathways have confused me compared to my previous OnePlus and Nexus phones. Thanks for your help.
You should only have to re-flash
OEM
Vendor
Boot
Recovery
to be able to apply the OTA.
Afterwards you just need to boot the twrp and install Magisk again, and maybe use the dmverity patch to disable forced encryption. <-- This has to be done BEFORE the first boot of the upated system, otherwise the phone will be encrypted again.
At least this is how it works on the G6 Play.
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
You can do that without loosing your apps/userdata.
Best bet would be to find the latest full image for your make/model and flash everything via fastboot. Just skip the part "fastboot erase userdata" or something like that, and you are good to go. Just remember the dmverity thing, if that is important/applicable for you.
Re-root is necessary either way, but that takes like 5 minutes, that shouldn't hold you up.
tintn00 said:
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
Click to expand...
Click to collapse
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
HueyT said:
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
Click to expand...
Click to collapse
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
tintn00 said:
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
Click to expand...
Click to collapse
If u want to backup data partition on TWRP, u have to be unencrypted for Moto G6 as TWRP can't decrypt data.
Rooting is just Magisk 18.1 and has nothing to do with encryption.
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
HueyT said:
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
Click to expand...
Click to collapse
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
tintn00 said:
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
Click to expand...
Click to collapse
Unlocked is safest guarantee against bricking. Don't worry about "uncertified" in Play store
For Unlocked Bootloader Devices - Flash at your own risk. Make sure to take a complete internal memory backup before flashing.
Following is a copy-paste from OP Forums
Hey everyone,
We know everyone is excited to finally try the delicious Pie update on the OnePlus 3 and OnePlus 3T. Thanks to the feedback from our beta testers, we are getting closer to launching Android Pie on the OnePlus 3 and 3T.
Now, we would like to invite you to download and try the Community Build available here and continue to help us shaping the stable update. Anyone can try this build, but please have in mind it won’t be available via OTA, you’ll have to download and install it yourself.
Community Beta for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_075_all_1904171151_74affb85cc694452.zip
Community Beta for OnePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_075_all_1904171149_20a0443ddf734944.zip
Those who download the Community Beta build will get OTA update when the stable build is released.
Changelog
System
Updated system to Android™ 9 Pie™
Brand new UI for Android Pie
Updated Android security patch to 2019.4
Do Not Disturb mode
New Do Not Disturb mode with adjustable settings
New Gaming mode 3.0
Added text notification mode
Added notification for 3rd party calls
Phone
Deep integration with Google Duo
Camera
Integrated Google Lens mode
Instructions for updating to the Community Build
For those on the latest stable version 181206
Preconditions: Boot Loader should be locked
Steps:
Download the file from the link provided on the forum post
Move the downloaded file to internal storage root folder using the File Manager.
The device can then be updated via two methods.
First method: Local Update
Open Settings -> System update -> Click top right setting icon
Choose Local update
Click on the downloaded file and wait until the device reboots
Second Method: Recovery Update
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
For those who are on the latest Open Beta version 180712
Note: The entire data will be wiped since there will be a version transition from Open beta to the stable version. If you made a OnePlus Switch backup, be sure to make a copy of it before moving forward.
Steps:
Download the file form the link provided on the forum post
Move the downloaded file to internal storage
Device can be updated only via Recovery Update:
Turn off the device -> Press power and volume up key simultaneously until the device enters the Fastboot Mode
Navigate to Recovery option using volume and power button -> Choose English -> Install from Internal storage -> Select the downloaded zip file -> Select 'Yes'
Wait until the installation is complete -> Reboot
Thank you once again for all your patience and we can’t wait to get your feedback.
We are one step closer to releasing the Pie for OnePlus 3 / 3T, you can now download and try our community build right now.
Never Settle.
EDIT 1
Procedure that worked for me
So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
EDIT 2:
Community Beta 2 Released 5/6/2019
Hey everyone,
Here is the Community beta 2 for the OnePlus 3 and OnePlus 3T, the update primarily contains bug fixes:
Changelog
Bug fixes
Clock timer and stopwatch interface display is incomplete
Microphone doesn't work when earphones are plugged in
Crash issues with native message app
Community Beta 2 for OnePlus 3
https://oxygenos.oneplus.net/OnePlus3Oxygen_16_OTA_080_all_1905061403_459f9d6e543f4a16.zip
Community Beta 2 for onePlus 3T
https://oxygenos.oneplus.net/OnePlus3TOxygen_28_OTA_080_all_1905061406_f9d7f76f3a5d45da.zip
I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?
brian13th said:
I am at the latest open beta, unlocked bootloader, rooted with twrp recovery. Does anyone know if I could flash this build through twrp?
Click to expand...
Click to collapse
I am currently at work. I will flash it once I am home. but make sure you take complete backup of your internal memory. It will mess up your internal data partition if you have unlocked bootloader. Don't take an unnecessary risk with your data.
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.
FSadino said:
Flashed over closed pie beta (unlocked bootloader) with stock recovery. No internal data lost. :laugh:
Click to expand...
Click to collapse
kojakcr said:
Flashed over closed pie beta (unlocked bootloader) with Red Wolf recovery. No problem, no data loss.
Click to expand...
Click to collapse
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?
abhibnl said:
That makes sense as you already had the closed pie build. Also, one question, are you both currently encrypted?
Click to expand...
Click to collapse
I am
FSadino said:
I am
Click to expand...
Click to collapse
Seems like there is no other way than to format internal memory once. I'm on stock 5.0.8 rooted and UL BL
Where I found a download link from stock recovery.
On the OnePlus page I don't found it.
After flash stock recovery I must locked bootloader
Thanks
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Clean install, twrp 3.30-1, magisk, everything's fine
Thank you oneplus
On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19
What's the procedure if I'm on twrp with custom rom?
Ed_Newgate said:
What's the procedure if I'm on twrp with custom rom?
Click to expand...
Click to collapse
The procedure is always the same, the results may be different.
Factory reset
Wipe data, system, cache, art
Flash zip
Reboot
So I've managed to install it and as expected, I had to format and delete everything on my internal memory. Here is the procedure I've followed and I'm 100% sure it'll work for others too.
Stuff I did before flashing:
1. Took a complete backup of internal memory.
2. Downloaded ROM + Recovery ( I use Holy Dragon custom twrp) + magisk 18.1 zip to an external OTG drive
My Configuration before flashing:
OOS 5.0.8, Unlocked BL, Magisk and root, Custom Kernel, Custom HolyDragon recovery
Procedure I followed:
1. Boot to recovery.
2. Wipe System, Dalvik, Cache
3. "Format Internal Memory". Please note, I formatted internal memory, not just wiped. This will remove encryption for once which will help the rom boot. It won't boot on encrypted partition with unlocked bootloader on first start up.
4. Flashed ROM zip.
5. Flashed twrp image.
6. Pressed power button for as long as possible until it rebooted again.
7. Pressed volume button before it could reboot so that i can select recovery. This step is important. If you won't do it, your recovery will be replaced with stock one.
8. Flash magisk zip. 18.1
9. Reboot system. It will take 10-15 minutes as it will reencrpt the storage.
10. Profit! Enjoy your new official oos pie on OP3/T.
Some things to note:
1. On first boot, it WILL NEED either mobile data or wifi. It downloaded some update and then installed and proceeded.
2. It will ask for your previous pattern. It didn't work for me so i simply login with my previous Gmail account on 5.0.8 and login successfully.
3. You will need to install magisk manager on first boot. It will show magisk not installed. Don't panic. Simply reboot your device once and it will appear in magisk on second reboot.
Let me know if you need additional help.
would u say worth changing to this from the one3os cb rom all seems to be the same there as this?
ireaper4592 said:
would u say worth changing to this from the one3os cb rom all seems to be the same there as this?
Click to expand...
Click to collapse
I can't say for sure. I have never tested CB. But this is the latest we have and it could have some under the hood fixes. I would recommend flashing this over CB
I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...
HouseFuzzy said:
I need some help. I was on the latest Lineage OS version, got into recovery and formatted my data. Then I flashed the OOS Pie version. Got stuck on the OOS boot animation. Then I tried flashing the last OOS Beta and the last Official OOS but both are stuck on the same OOS boot animation. I also tried locking my bootloader and then starting again but didnt work out either...
Click to expand...
Click to collapse
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright gonna give it an other try then. Flashed the Pie OOS now via TWRP at around 11.20 german time. If its not getting over the boot animation by like 12.00 german time im gonna reply again.
---------- Post added at 12:16 PM ---------- Previous post was at 11:27 AM ----------
abhibnl said:
You should be stuck on the booatanimation for at least 10-15 minutes. It's re-encrypting your /data partition.
Click to expand...
Click to collapse
Alright been letting it go an hour now. Still in the boot animation.
svandasek said:
On the 3T build I can't get it to install magisk for God's sake. The system partition is full and it seems it installs magisk fine, but when I boot up it says it isn't installed.... Tried different versions from 17.2 to 19
Click to expand...
Click to collapse
Having similar issue, but on my side Magisk is installed, apps correctly receives the root privileges, but AdAway can't install the hosts file, it says system partition is full.
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.
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!