Database Develop

Downgrade OxygenOS from 3.5.2 to 3.2.6 with Root / Xposed / Debloat

So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone

Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?

darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
You're welcome.
Unfortunately, I can't provide guides for procedures I never went through.
But I asume that you could just flash any Custom ROM after you completely wiped your phone in step 4. So instead of flashing OOS 3.2.6 afterwards, just flash a custom ROM. Be sure that you have all zips you need on your internal storage and a backup to revert back to, if anything goes wrong. Otherwise you will have to use ADB sideload to install a ROM.

Ok, so I have a Modified TWRP installed already. Question is If I want to flash other ROMS after wiping system,dalvik/cache,data etc. Do I have to Flash official TWRP first followed by firmware,ROM, etc?
or firmware first then ROM and lastly official TWRP?
it's quite confusing.

I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life

gigeaky said:
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
Click to expand...
Click to collapse
Flash modified TWRP, and the recovery will return. then, follow the guide. it happened to me too.

darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
First flash modified TWRP than install official 3.2.4 than flash CM ROM or custom ROM

uniQ191 said:
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Click to expand...
Click to collapse
worked like magic. Thankyou for this education. it didnt work when i followed other folks. Much appreciated.

So it seems I have booted with 3.5.2 and modified recovery. Now my question is: can I reboot in recovery at step 7 and install the original twrp recovery? Or can I use flashify? As I don't have access to a pc

I did ok but cant use adaway do you have a fix for it?
Enviado do meu ONEPLUS A3003 através de Tapatalk

I'm trying to return to 3.2.6 after trying 3.5.2.
However, after flashing and booting 3.2.6, I boot into fastboot mode and the official TWRP refuses to flash. It reports that it's failed and then I'm left with no recovery until I reflash the modified TWRP.
I could try restoring my Nandroid backup of 3.2.6 with the modified TWRP, but I'd prefer to return to the official TWRP before doing this.
Any suggestions?
Edit: Fixed it. I downloaded the official TWRP again and it flashed. The first download must have been corrupted.

I followed a different method and successfully downgraded today to a former nandroid. I was rooted without xposed.
3.2.6 to 3.5.2 dirty flash
- installed modded twrp
- performed backup on 3.2.6
- installed modded 3.5.2 (the only that flashes in twrp)
- installed root SR1
- wiped caches only
- reboot
3.5.2 to 3.2.6 restore
- downloaded 3.2.6
- boot to modded twrp, wipe both caches, data, system
- flashed 3.2.6 stock and root SR1
- restored 3.2.6
- wiped caches
- reboot
- enjoying my LTE again
Without first installing stock, after a restore my phone was boot locking right after the oneplus white logo (capacitive buttons would light up, but it would not boot to red logo). Had to press vol down and power to force it to boot menu to select recovery and get back to twrp
Hope this helps someone, it's a bit easier than swapping twrps and no need to boot up/flash 3.2.x twice.

So if I am on the CB and want to go back to 3.2.6
I can flash 3.2.6 with the modded TWRP
Then flash Official TWRP and boot?

If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss

popab said:
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
Click to expand...
Click to collapse
i would also like to know this please

bigup7 said:
i would also like to know this please
Click to expand...
Click to collapse
I did it and it does work perfectly. Just make sure to wipe data from recovery after flashing.

I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.

null0seven said:
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
Click to expand...
Click to collapse
I am on CB Freddom os
I want to go back either to stock or to op3lite.
I cant reboot to recovery.
But adb works yet.
What to do plz suggest.
Sent from my ONEPLUS A3003 using Tapatalk

1. If system don't boot. Reboot to fastboot.
- Flash recovery.img. If PC don't see youre phone option 2.
2. If system boots, open phone like normal.
- Extract recovery img. Put it on the TWRP file on phone sd card.
- Download Flashify from play. Open it, flash img of recovery. Open recovery to chech if it works.
Try with both recovery (3.0.2.0 or modified 3.0.2.-19). One of those will work.

Im getting system partition has unexpected contents after OTA update after installing step 5 ????

[ROM] Community Build 3.5.4 Out Now

Hi everyone,
The CB 3.5.4 is out
This update includes:
Added new App Lock feature
Fixed keyguard crashes when enabling sim card lock in multiple languages
Optimized accent colors in default themes
Optimized translations for certain languages
Improved the quality of expanded screenshots
Increased system stability
General bug fixes
Download full zip with Hot Fix : Link
Drive Mirror by @rkrohan
AFH Mirror by @shafi31
If you’ve already flashed a previous community build, you will receive this update via OTA. If you haven’t, you will need to flash this build by ADB sideload. Your data my transfer, but there is always a possibility of losing personal data, so be sure to backup all of your important data before flashing this build. As stated before, once you flash the community build, you’ll continue getting community OTAs.
- Feedback on UI/UX: https://goo.gl/forms/BioIINdnCsUhTauc2
- Bug reporting sheet: https://goo.gl/forms/P2DPrEqQWIafmyyE3
Note: If you flash this community build, you’ll receive community OTAs (but not official OTAs). You’ll need to manually (clean) flash back to our official builds to continue receiving official OTAs. Rolling back to official OxygenOS versions require wiping data and cache.
Source: OnePlus Forums

Installation & Screenshots
Installation for Rooted Users with TWRP:
> Method 1 with Modified TWRP (Credits @eng.stk)
Updated TWRP Recovery Needed 3.0.2-22 available here Credits @eng.stk
Download full zip with Hot Fix : Link
Drive Mirror by @rkrohan
AFH Mirror by @shafi31
If you come from Official Build or CB Dirty Flash would work fine
Flash the Updated TWRP 3.0.2-22 either image flash via existing TWRP or via Fastboot Mode
1. Boot into Modified Recovery:
2. Wipe Dalvik & Cache
3. Flash the full 3.5.4 Zip
4. Wipe Dalvik and Cache
5. Flash SuperSu (Optional if you need to maintain root)
6. Flash Xposed, Kernel any other mods (Optional)
7. Flash Modified TWRP as image (even if you are already on it)
8. Reboot to into recovery directly to verify TWRP still functional (this will prevent recovery from being overwrite by the stock)
9. Reboot System & Profit
PS: System will reboot twice if you flashed SuperSU, Dont Panic
If you come from a custom rom, i recommend a clean flash.
After the recovery update by @eng.stk we no longer need to run the CB 3.5.4 with 3.2.X firmware and the latest Kernel is r137 which can be flashed.
Check out his download page here and always flash the latest
*******************************************************************************************
> Method 2 with Modified Script using Official TWRP Credits @ahmediftikhar,
Downloads :
Firmware Version 3.2.7 G-Drive | AFH
Oxygen OS 3.5.4 CB with Hot Fix (NO firmware - Modified Updater Script ) G-Drive | MEGA
Official TWRP 3.0.2-1
SUPER SU 2.78
If you come from a Custom Rom Factory Reset and Clean Flash
If you come from OOS based rom Dirty Flash as below:
1. Boot into Official TWRP
2. Wipe Dalvik cache + cache
3. Flash the Firmware zip
4. Flash OOS 3.5.4 zip
5. Wipe Dalvik and Cache
6. Flash official twrp as image (even if you are already on it)
7. Reboot to into recovery directly (this will prevent recovery from being overwrite by the stock)
7. Flash SuperSU Optional (If you need Root Access)
8. Reboot System & Profit
PS: System will reboot twice if you flashed SuperSU, Dont Panic
Screenshots Attached
OTA Only with Hot Fix Only Here

What I did for installing 3.5.4 :
I was on 3.5.3, using Twrp 3.0.2-19
I downloaded 3.5.4 and clean flashed using TWRP 3.0.2.19.
After installation,I pressed Reboot. I got a warning : No system installed, still I slided for reboot. I went black but I forced phone to restart again. after a few mins, It rebooted.
I went back to Recovery, but it cleared TWRP and installed Stock recovery, again I flashed TWRP 3.0.2.19, and installed SuperSu.
Now, everything is allright.

quaresma158 said:
What I did for installing 3.5.4 :
I was on 3.5.3, using Twrp 3.0.2-19
I downloaded 3.5.4 and clean flashed using TWRP 3.0.2.19.
After installation,I pressed Reboot. I got a warning : No system installed, still I slided for reboot. I went black but I forced phone to restart again. after a few mins, It rebooted.
I went back to Recovery, but it cleared TWRP and installed Stock recovery, again I flashed TWRP 3.0.2.19, and installed SuperSu.
Now, everything is allright.
Click to expand...
Click to collapse
Is it still needed to use the modified TWRP?
What would happen if I install official TWRP after having installed and booted 3.5.4?
Would it break something or the system would boot normally?

Great! Downloading

Giocarro said:
Is it still needed to use the modified TWRP?
What would happen if I install official TWRP after having installed and booted 3.5.4?
Would it break something or the system would boot normally?
Click to expand...
Click to collapse
Then theres no recovery all you can see is black screen
Sent from my ONEPLUS A3003 using Tapatalk

great news
---------- Post added at 09:24 AM ---------- Previous post was at 09:24 AM ----------
will try today....

Someone send me a link for TWRP flashable ROM ... In the given link that only for stock recovery...
Sent from "Oneplus 3" via XDA apps

Im on 3.5.3 with modified twrp.
1. Reboot to recovery using modified twrp
2. Flash 3.5.4 zip
3. Flash SuperSU
4. Wipe dalvik/cache
5. Reboot
No problem at all. ?
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

Effusob said:
Im on 3.5.3 with modified twrp.
1. Reboot to recovery using modified twrp
2. Flash 3.5.4 zip
3. Flash SuperSU
4. Wipe dalvik/cache
5. Reboot
No problem at all. ?
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
I totally lost link to modified twrp (3.0.2.19)
Can you give me a link
Edit : nvm found it
Sent from my ONEPLUS A3003 using Tapatalk

Normas Interruptor said:
Someone send me a link for TWRP flashable ROM ... In the given link that only for stock recovery...
Sent from "Oneplus 3" via XDA apps
Click to expand...
Click to collapse
Read the FAQ dude
Can we use another recovery system other than the Oxygen recovery?
TWRP is a popular recovery and we have provided flashing instructions if you are using TWRP on the OnePlus 2 and X.
The instructions we have provided are device specific, so please make sure you read the instructions for your device.
Click to expand...
Click to collapse

if you haven't read on the oneplus community people are having an issue where if SIM lock is enabled they can't get past the initial PIN screen, just be aware

gfunkzero said:
if you haven't read on the oneplus community people are having an issue where if SIM lock is enabled they can't get past the initial PIN screen, just be aware
Click to expand...
Click to collapse
Any one have this Issue ??
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

Delete

Funk Wizard said:
Hi everyone,
The CB 3.2.4 is out
Click to expand...
Click to collapse
You might wanna correct that.
---------- Post added at 02:49 PM ---------- Previous post was at 02:42 PM ----------
The update message also says Added option to adjust background colors and control default theme. But download.oneplus.net page doesn't mention this in their changelog. Weird.

Could anyone check if the changing DPI messes with the quick toggles?

juginkrebs said:
Any one have this Issue ??
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Happened to me. I updated via OTA and then I cannot input my SIM PIN since lockscreen keeps popping up. Tried wiping cache, data, system recovery etc... and now I am downloading 3.5.3 to flash again since I still cannot use the phone.

GREAT NEW FEATURES.
i cant see a Feature, we've been waiting a long long time for

Effusob said:
Im on 3.5.3 with modified twrp.
1. Reboot to recovery using modified twrp
2. Flash 3.5.4 zip
3. Flash SuperSU
4. Wipe dalvik/cache
5. Reboot
No problem at all.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
can you give me the download link of this ROM ?

Anyone managed to successfully dirty flash? I have root and Xposed, cant OTA and I'd like to have my data intact.

[Official] Android 9 Community Beta for OnePlus 3/3T

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.

Working TWRP for Mi9T Pro on Android 10 (QFKEUXM) **SOLVED**

Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
**UPDATE**
I flashed the latest TWRP from this thread and all went smoothly. Also managed to get Viper4android working which was my biggest concern coming from Android 9. Happy days :victory:

_ray_ said:
Now that we have finally got the update in the EU region I want to know if anyone has successfully flashed TWRP or any other recovery?
In case anyone wondering I have managed to get root with the latest magisk via patched boot image method.
Click to expand...
Click to collapse
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Good luck and please do post back the results :good:

Fatal_Scythe said:
I'm currently on MIUI 10.3.4.0 Stable with OrangeFox Recovery installed, Going to attempt updating later since, afaik, OrangeFox has Support for OTA Updates.
Click to expand...
Click to collapse
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Sent from my Redmi K20 Pro using Tapatalk

I'm also interested in this. I want to keep TWRP and magisk post-upgrade to Android 10

I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system

_ray_ said:
Good luck and please do post back the results :good:
Click to expand...
Click to collapse
ishaqtkr said:
Waiting for your feedback, because my orangefox is ready for OTAs but i think because i forgot to check DM VERITY and FORCED ENCRYPTION it asks for password when rebooting for update and ruins it...this is my guess. So please share your feedback and it you checked the 2 options unlike me.
Click to expand...
Click to collapse
Okay so, coming from 10.3.4.0 Stable, OFox Recovery and encrypted, the update ran through fine without any problems. Since I'm encrypted I had to enter my password first but after that it started installing the Update. as far as I remember, I've seen that Orangefox's script that prevents Orangefox from being overwritten after every update (it's called OTA.bak I think) already handles both DM-Verity and Force-Encrypt on it's own, at least I didn't had to take any further steps regarding Encryption and such stuff and after updating it booted into MIUI 11 just fine (which ofc since it's an Major Update took a little longer than usual but at least it eventually did)

desiresiscool said:
I updated with no issued with the following steps:
1. Installed latest TWRP from here https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
2. Download latest Magsik
3. Download recovery zip for miui 11 rom
4. Reboot to recovery
5. Install rom zip ( do not reboot after install)
6. Install Magsik
7. Install TWRP img via recovery that you downloaded in step 1
8. Reboot into TWRP
9. Reboot to system
Click to expand...
Click to collapse
So what do you do when you're on 10.3.4 pfkeuxm Rom and running with twrp and magisk installed?
Can't I install the miui 11 rom via twrp and then immediately flash magisk again?

Following the advice here, I've got the update installed with twrp and magisk working fine. The only problem I have is that I can't read/write the system partition so titanium backup isn't working. Any ideas how I could fix it?

Oxygen OS 10.0.5 is now live - Oxygen OS 10.0.5.GM21BA (EU)

Just to match the other threads for issues and discussion :
Official links :
Incremental : https://otafsg1.h2os.com/patch/amaz...OTA_024-025_patch_2003270113_ad17667b654b.zip
Full : https://otafsg1.h2os.com/patch/amaz....25_OTA_025_all_2003270113_4588ebe57af551.zip
Mirror links (AFH) :
Incremental : https://www.androidfilehost.com/?w=files&flid=307735
Full : https://www.androidfilehost.com/?w=files&flid=307737
Oxygen Updater also listing both the incremental update and the full update.
Installing :
For the uninitiated, Download either package and copy it to the root folder of your phone's storage, then go to the following location on your phone :
Settings > System (at the bottom) > System Updates (at the bottom) > Tap on the cog icon on the top right > Tap on local upgrade
The build available in your root folder should be listed, tap that and follow the instructions.
If you are coming from the beta release ring back to the main release ring you will most likely be prompted to wipe your data, ensure you have backed up all data you want to keep beforehand.
If you are upgrading from one release ring build to the next then you may want to clear your cache.
My Android 10 repo :
https://www.androidfilehost.com/?w=files&flid=296897
XDA page updated with official links :
https://www.xda-developers.com/onep...t-pro-5g-oxygenos-updates-march-2020-patches/
(Edit : Fixed the links, helps if you copy it properly :/ )
(Edit : Added official links and re-formatted )

Some users who already received the update previously had reported overheating and higher battery usage, tests on the official forum have shown better benchmark results compared to previous builds, so the heat and battery usage might be caused by this. No confirmation from OnePlus as to whether this was why the update was obviously being delayed.
Post any relevant improvements or reports of heating/battery differences below.
Remember to allow adequate time to gauge any difference in battery usage though.

Would flashing this over Beta 11 wipe my phone? I'm also rooted with TWRP.
Sent from my GM1915 using Tapatalk

How to update from OB11 to STABLE and keeping root and twrp
BACKUP all you want to keep safe.
I was on ob11 with latest Magisk Canary and twrp 3.3.1-79
Update from OB11 to STABLE 10.0.5 :
1- uninstall ALL Magisk modules. Reboot to System.
2- install Oos 10.0.5 stable with Settings > Local upgrade . DON'T reboot!!!
3- open Magisk > Downloads. Install TWRP A/B Retention Script. DON'T reboot!!!
4- back in Magisk. Touch install. Choose (Install to inactive slot after' OTA)
5- reboot to system.
Let the phone start. Mine at first start to twrp then to system.
This CLEAN istalls 10.05. It ERASES apps messages...

Done. Installed over 10.0.4 with TWRP and Magisk. WORKING.

I was hoping to not lose apps and messages.
Sent from my GM1915 using Tapatalk

Hi Guys,
I have downloaded full OTA update 10.0.5 from above link.
Flashed rom using TWRP, flashed TWRP image (3.3.1-79 by mauronofrio), rebooted to recovery and flashed Magisk 20.4.zip file.
After system reboot it is still showing OOS 10.0.4 with january 2020 security patch....
Did the same three times, initially twice with OTA zip file taken from Oxygen Updater later with ROM from this thead, same outcome - still on 10.0.4.
Is there something I'm doing wrong?? Can you please advice.
Thanks...

Yanoosh_GA said:
Hi Guys,
I have downloaded full OTA update 10.0.5 from above link.
Flashed rom using TWRP, flashed TWRP image (3.3.1-79 by mauronofrio), rebooted to recovery and flashed Magisk 20.4.zip file.
After system reboot it is still showing OOS 10.0.4 with january 2020 security patch....
Did the same three times, initially twice with OTA zip file taken from Oxygen Updater later with ROM from this thead, same outcome - still on 10.0.4.
Is there something I'm doing wrong?? Can you please advice.
Thanks...
Click to expand...
Click to collapse
You've only installed on one slot, use TWRP to change the slot and flash rom, TWRP and Magisk again.
Either that or just use TWRP to change the boot slot.

djsubterrain said:
You've only installed on one slot, use TWRP to change the slot and flash rom, TWRP and Magisk again.
Either that or just use TWRP to change the boot slot.
Click to expand...
Click to collapse
Great, changing the boot slot worked. Thanks.:good:

Hi guys, just updated to this 10.0.5, reinstalled twrp, but when starts WiFi won't stay on & network icons are a mess as in aren't showing correctly, would this be due to twrp needing an update as I've tried several versions & same result, returning to stock everything works perfectly again, any help would be great thanks

NHNXDA said:
Hi guys, just updated to this 10.0.5, reinstalled twrp, but when starts WiFi won't stay on & network icons are a mess as in aren't showing correctly, would this be due to twrp needing an update as I've tried several versions & same result, returning to stock everything works perfectly again, any help would be great thanks
Click to expand...
Click to collapse
Remove all Magisk modules first, restart then added it back, it's call recording module!

Up and running with TWRP 3.3.1-79 and Magisk 20.4.
Only one day of usage, so too early to draw conclusions, but I have seen no overheating or high battery drain.
If anything, it actually looks to have improved from 10.0.4:
BTW, SOT was 2h57

Why does this update wipes, makes factory defaults?

BoroZG said:
Why does this update wipes, makes factory defaults?
Click to expand...
Click to collapse
Did you install from Open Beta?

Hirs_E_Fruit said:
Did you install from Open Beta?
Click to expand...
Click to collapse
Yes beta 11.

BoroZG said:
Yes beta 11.
Click to expand...
Click to collapse
That's why

hoseth0711 said:
That's why
Click to expand...
Click to collapse
So, no way to avoid factory reset?

BoroZG said:
So, no way to avoid factory reset?
Click to expand...
Click to collapse
It's a different release ring so no, that's the way it's always been tbh

metzo32 said:
Remove all Magisk modules first, restart then added it back, it's call recording module!
Click to expand...
Click to collapse
Its the idiot, being me, I was using the wrong command line for twrp, instead of boot, I used flash boot, which of course flashed twrp as my boot.img & messed it up, I blame covid & isolation, realistically it was my silliness.

Flashed on T-Mobile 7pro, then xXx, no issues so far, great battery life.