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 ????
I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.
Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1
You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo
just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.
Hello
I was on B180 (PRA-LX1C432) rooted with magisk
No updates available in settings/update firmware, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
Thanks !
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota, maybe I can use fastboot to flash only system and boot, and the reflash magisk to patch new boot img ?
anyone ?
Nobody updated after root ??
Ok, this is what I did and happened:
- In TWRP, flash magisk uninstaller script: ERROR 1. After reboot magisk was still here. That was a bad start...
- So I opened magisk app, click Uninstall and then Complete Uninstall. After that I made a reboot as asked, and device rebooted twice.
- Then, went to download mode and flashed stock recovery. And reboot.
- Then went to settings/updates/download latest full ota. It downloaded but refused to start the install process claiming to free up more than 900MB... Nothing on my internal sdcard so I had to uninstall some apps... cool !
- Then it reboot and installed the update
- First boot took a while, I still have "this device cannot be trusted" on start, and OEM unlock in settings is grayed and ON, so I think the bootloader is still unlocked
- Theme and wallpapers were reset with the update
For now I don't have flashed back twrp neither magisk .
In the meantime have you flashed TRWP and Migistik ? And again: do you have still to update your signature or something went wrong in installing fw B194.
Lastly: what do you mean by "went to download mode and flashed"...
I found an easy and convenient way to flash Huawei updates when twrp is installed. No data loss. In my case I updated from June to July patch without any hiccups.
1. Download the HWOTA8 folder zip to your device and extract it to the root of your SD card. I provided the link at the bottom of the tutorial.
2. Download the Huawei update and wait till it finished.
3. Boot to twrp and go straight to the HWOTA8 folder.
4. Now install the hwota8_update.zip, this will install a special no check version of the stock recovery.
5. After reboot you'll see a failed update attempt, ignore the message and boot to system.
6. Now that we have the stock recovery you can go straight to the update app in the settings and install the update.
7. After 5 minutes the update should be finished and the device will boot to system.
8. The bootloader will be still unlocked so you can modify again with twrp, magisk and so on. No data loss.
Download
https://mega.nz/#!7AxVwBBZ!W9YyQ7qSAxZo-px8xYR18rBIhycKlqOhS4n8ogTioaI
gude, tried this today to upgrade P10plus from .382 to .385. worked as promissed. afterwards just installed the TWRP and magisk to get back root. thx
Dear Sir,
Thank you for the clear and concise method for flashing stock updates when TWRP is installed.
Please help me with instructions how to upgrade my unlocked, rooted and TWRP installed Android 7 ROM to OREO.
My phone model number is: VKY-L09
Build number: VKY-L09C02B102
EMUI version: 5.1
Android: 7.0
Kernel: 4.1.18-gfd75bb
TWRP: 3.1.0-0
there is only one thing that makes me wonder: i cannot install a differential update, this always fails, so the complete package will download ( almost 3GB ), then the installation will be successful. any idea why?
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom
title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?