Hi all,
I've got a OP5 currently running 5.1.0 which is unlocked, rooted & encrypted. I've tried to flash 5.1.6 on the stock recovery but it always says the installation has failed.
Going from my memory I tried the latest versions TWRP versions by Codeworkx and Bluspark, however when flashing they both result in an error code 7 and it aborts.
Does anyone know how I can simply get this phone to update? I'm hesitant to wipe data / system files in case I cannot flash the rom...
Amos91 said:
Hi all,
I've got a OP5 currently running 5.1.0 which is unlocked, rooted & encrypted. I've tried to flash 5.1.6 on the stock recovery but it always says the installation has failed.
Going from my memory I tried the latest versions TWRP versions by Codeworkx and Bluspark, however when flashing they both result in an error code 7 and it aborts.
Does anyone know how I can simply get this phone to update? I'm hesitant to wipe data / system files in case I cannot flash the rom...
Click to expand...
Click to collapse
That's because OOS 5.1.0 doesn't have Treble implementation (i.e. there isn't a separate vendor partition that is needed for it), whereas OOS 5.1.6 has Treble implementation (i.e. it needs a separate vendor partition to work properly and if it fails to find one, it'll not install only and error out).
You should try flashing OOS 5.1.4 over OOS 5.1.0 (which, I think, creates the vendor partition) and then try flashing OOS 5.1.6. Basically, the update path should be OOS 5.1.0 -> OOS 5.1.4 -> OOS 5.1.6. If it still doesn't work, try OOS 5.1.0 -> OOS 5.1.4 -> OOS 5.1.5 -> OOS 5.1.6. Should work.
Good luck! :good:
shadowstep said:
That's because OOS 5.1.0 doesn't have Treble implementation (i.e. there isn't a separate vendor partition that is needed for it), whereas OOS 5.1.6 has Treble implementation (i.e. it needs a separate vendor partition to work properly and if it fails to find one, it'll not install only and error out).
You should try flashing OOS 5.1.4 over OOS 5.1.0 (which, I think, creates the vendor partition) and then try flashing OOS 5.1.6. Basically, the update path should be OOS 5.1.0 -> OOS 5.1.4 -> OOS 5.1.6. If it still doesn't work, try OOS 5.1.0 -> OOS 5.1.4 -> OOS 5.1.5 -> OOS 5.1.6. Should work.
Good luck! :good:
Click to expand...
Click to collapse
Spot on thank you! Used the MSM tool in the end to force flash it to 5.1.2 and remove all traces of root etc. Then OTA updates it to 5.1.4 automatically as you said. And I've now just sideloaded 5.1.6 through the OTA updater.
Thanks again!
Amos91 said:
Spot on thank you! Used the MSM tool in the end to force flash it to 5.1.2 and remove all traces of root etc. Then OTA updates it to 5.1.4 automatically as you said. And I've now just sideloaded 5.1.6 through the OTA updater.
Thanks again!
Click to expand...
Click to collapse
Thought as much. No worries! Glad you got it sorted out.
Related
I am creating this thread keeping in my mind the several posts in various threads mentioning that they have accidentally triggered the DM-Verity flag and have an annoying message during startup or due to force encryption in the boot image the phone went back to encrypted state after flashing a new Stock Oxygen OS zip file in TWRP recovery.
So I decided to start a thread where I will post the links to the OFFICIAL BOOT IMAGES of Oxygen OS ROMs for both OnePlus3 and OnePlus3T which have been patched to disable the DM-Verity Flag and to disable the Force encryption that is present in the Stock Oxygen OS ROM.
NB: This thread is only for Nougat Based OOS ROMs. For disabling Dm-Verity and force Encryption in PIE OOS ROMs refer to my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324. For Disabling DM-Verity in Oreo Based OOS ROMs visit my thread here: https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
THIS IS FOR BOTH ONEPLUS 3 and 3T and read the instructions carefully and apply the file specific for your model
Disclaimer: I am not responsible for any damage to your phone by using this...
Nothing has been changed....
It is 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Links:
For ONEPLUS 3T
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/vm2k81s3pregdiv/boot-patched-4.5.1-OP3T.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/m8e3nu4ak4u1zkz/boot-patched-4.5.0-OP3T.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/g5rk4284lzyvqnu/boot-patched-4.1.7-OP3T.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/j3802c259gea6f2/boot-patched-4.1.6-OP3T.img[/URL]
Patched Boot Image Stable OOS 4.1.5
[url]http://www.mediafire.com/file/78ej52gmthok212/boot-patched-OOS4.1.5.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 15
http://www.mediafire.com/file/a436larx3ddx00l/boot-patched-Beta15-OP3T.img
Patched Boot Image OOS Beta 14
http://www.mediafire.com/file/brlvdth86lxi0yl/boot-patched-Beta14-OP3T.img
Patched Boot Image OOS Beta 13
http://www.mediafire.com/file/2clnhl0x4vu8bu8/boot-patched-Beta13-OP3T.img
Patched Boot Image OOS Beta 12
http://www.mediafire.com/file/2214mr1adpdwlx4/boot-patched-Beta12-OP3T.img
Patched Boot Image OOS Beta 11
http://www.mediafire.com/file/hywcwmv0a993ah5/boot-patched-Beta11-OP3T.img
Patched Boot Image OOS Beta 10
http://www.mediafire.com/file/n7nu0wj266e8fhh/boot-patched-Beta10-OP3T.img
Patched Boot Image OOS Beta 9
[url]http://www.mediafire.com/file/5lkp6fi33u9lkpt/boot-patched-Beta9-OP3T.img[/URL]
Patched Boot Image OOS Beta 8
[url]http://www.mediafire.com/file/4d5zrpff4jakjgk/boot-patched-OOS_Beta_8.img[/URL]
For OnePlus 3
STABLE OOS Boot Images
Patched Boot Image Stable OOS 4.5.1
http://www.mediafire.com/file/srdurw9pg4f614f/boot-patched-4.5.1-OP3.img
Patched Boot Image Stable OOS 4.5.0
http://www.mediafire.com/file/nrbuddj0652bf4u/boot-patched-4.5.0-OP3.img
Patched Boot Image Stable OOS 4.1.7
http://www.mediafire.com/file/2cb3jrqckb4suxw/boot-patched-4.1.7-OP3.img
Patched Boot Image Stable OOS 4.1.6
[url]http://www.mediafire.com/file/ytax9vfa9lyhd6d/boot-patched-4.1.6-OP3.img[/URL]
BETA OOS Boot Images
Patched Boot Image OOS Beta 24
http://www.mediafire.com/file/8fcbeiduhiewc9v/boot-patched-Beta24-OP3.img
Patched Boot Image OOS Beta 23
http://www.mediafire.com/file/9i3snrmmsinczct/boot-patched-Beta23-OP3.img
Patched Boot Image OOS Beta 22
http://www.mediafire.com/file/bauq66z2s6o2k1q/boot-patched-Beta22-OP3.img
Patched Boot Image OOS Beta 21
http://www.mediafire.com/file/r31feak94y3cm5z/boot-patched-Beta21-OP3.img
Patched Boot Image OOS Beta 20
http://www.mediafire.com/file/5h32hzw5ot1gbba/boot-patched-Beta20-OP3.img
Patched Boot Image OOS Beta 19
http://www.mediafire.com/file/y6446j7sxiw9jwx/boot-patched-Beta19-OP3.img
Patched Boot Image OOS Beta 18
http://www.mediafire.com/file/zfsji9mjjds7a6n/boot-patched-Beta18-OP3.img
Patched Boot Image OOS Beta 17
[url]http://www.mediafire.com/file/mrqhkq7igt7x4na/boot-patched-Beta17-OP3.img[/URL]
USAGE FOR STOCK OOS:
# Flash the downloaded boot-patched.img file corresponding to the Model and OOS version in TWRP immediately after flashing the Stock ROM zip in TWRP before doing anything (even before restarting or applying any patches, root, kernels, etc.)
# Restart back to TWRP Recovery.
# Done.
# Now do whatever you want like usual.. Flash root, kernel, mods or anything as usual
# You dont have to worry about triggering DM-Verity or Getting Force Encrypted again...
VERY IMPORTANT: FOR PEOPLE WHO HAVE ALREADY TRIGGERED DM-VERITY ON THEIR OOS OR CUSTOM ROM AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY, READ MY POST 2. AFTER GETTING RID OF DM-VERITY BY FOLLOWING THE STEPS IN POST 2, NEXT TIME ONWARDS WHILE UPDATING YOUR OOS OR CUSTOM ROM FOLLOW THE INSTRUCTIONS IN THIS OP TO KEEP YOUR OOS AND PHONE FREE FROM THE TROUBLE OF DM-VERITY AND FORCE ENCRYPTION...
FAQs:
Q: Is the boot.img file altered in anyway?
A: As mentioned above its 100% stock boot image except that the DM-Verity Flag and Force Encryption has been patched...
Q: My phone is already encrypted, will I lose encryption?
A: No. It only disables force encryption. That means if you have already disabled encryption in your phone it will prevent the phone from getting encrypted when you flash a stock OOS ROM..
Q: I happen to lose TWRP and revert to stock recovery every time I update OOS, I happen to lose data/apps accidentally while updating OOS after I lose TWRP ...Can this be corrected by using this method?
A: Definitely. Follow the steps correctly. Each time while updating the OOS, after flashing the Full OOS ROM.zip, immediately flash the patched boot.img of the corresponding OOS given in this thread and then restart back to TWRP recovery. Done. You will never lose TWRP again..
Q: I am Rooting my phone using Magisk/Supersu then why do i need this?
A: Its optional.. If you are rooting phone using Magisk/Supersu it patches the stock boot.img. But in case you have problems flashing Magisk/Supersu after flashing the STOCK ROM zip this can come in handy or as an insurance policy just flash this patched boot.img before doing anything. But is very helpful to those people out there who doesn't root their phone but has unlocked their phone or installed TWRP for other purposes..
Q: How to flash the patched boot.img in TWRP?
A: Default flash option is for zip files in TWRP. Select the flash image option in TWRP. Then select the downloaded patched boot.img file and among from the partition option (boot, recovery and system) select the boot option and then flash it.
Q: Can I use it for CUSTOM ROMs? / What to do while updating CUSTOM ROMs?
A: For hassle free and the best results whenever you update CUSTOM ROMs always do it this way...
The below steps are for CUSTOM ROMs only. (For STOCK ROMs follow the main step mentioned above in the section USAGE)...
1.Go to TWRP
2.Flash the required firmware zip file
3.Flash the corresponding patched boot IMG
4.Flash the ROM whether LINEAGE, RR, ASOP, etc.
5.Flash gapps
6.Flash root (magisk /su)
7.Flash kernel
8.At last Reboot...
There will not be any problem ever...
You can reboot after step 5
Steps 6,7 are optional
Q: What is "-Xn" seen after the OOS Version in the settings menu?
A: That's just my signature -Xn that I had put there to make sure that you have correctly done the procedure and the boot image that is currently in use is my patched boot image and to ensure you that you are 100% safe from DM verity and forced encryption..
Hope you find it useful...
Will update as newer OOS versions come....
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
THIS IS FOR PEOPLE WHO HAVE TRIGGERED DM-VERITY AND NEEDS TO GET RID OF THE DM-VERITY MESSAGE PERMANENTLY ON OOS OR OPEN BETA OR CUSTOM ROM. CONFIRMED WORKING EVEN IN THE LATEST OOS 4.5.1/BETA Nougat Roms...
THIS IS FOR ONEPLUS 3T AND FOR ONEPLUS 3 but be careful in using the correct files corresponding to the OOS version and your MODEL
FOLLOW THE STEPS EXACTLY AND 100% THE DM-VERITY MESSAGE WILL BE GONE WITHOUT ANY DATA LOSS OR ANY OTHER HARM!!!
Prerequisite : Install ADB for windows from here: [url]https://forum.xda-developers.com/showthread.php?t=2588979[/URL]
1)
Download 4.0.2 Firmware for Oneplus 3T from here: [url]http://www.mediafire.com/file/cx568em66025p5b/4.0.2_firmware_OnePlus_3T.zip[/URL]
Download 4.0.2 Firmware for Oneplus 3 from here: [url]http://www.mediafire.com/file/8tt5x4xxy4m488t/4.0.2_firmware_OnePlus3.zip[/URL]
2) Flash the downloaded 4.0.2 firmware OnePlus 3.zip or 4.0.2 firmware OnePlus 3T.zip file in TWRP.
3) DONT REBOOT TO SYSTEM. REBOOT TO BOOTLOADER FROM OPTION IN TWRP.
4) Connect your phone to the pc
5) Press windows button + X
6) Open Command prompt
7) Type "fastboot oem disable_dm_verity" without quotes and press enter
8) Type "fastboot oem enable_dm_verity" without quotes and press enter
9) DONT REBOOT TO SYSTEM. REBOOT TO TWRP RECOVERY.
10)
In case of Oneplus3T, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166(Courtesy: @kamilmirza)
In case of Oneplus3, Flash the required firmware files for Stable or Open Beta OOS corresponding to your current OOS (current OOS is the version of OOS which you are using now on your phone) in TWRP from this post: [url]https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628[/URL] (Courtesy: @jamal2367)
11) DONT REBOOT!!!!
10) VERY IMPORTANT: WITHOUT REBOOTING, Flash the downloaded boot-patched.img file corresponding to the OOS version and phone model(either stable or beta) in TWRP from post 1...
11) Reboot..The DM-verity message is gone forever...
VERY IMPORTANT: If you are attempting this method on a a CUSTOM ROM then after Step 10 flash the full CUSTOM ROM zip file + latest gapps again without doing any sort of wipes in TWRP immediately and then only reboot....
Enjoy!!!
FAQs...
Q: Will I lose any data after I do these steps?
A: Never. There will be no data loss or any untoward effects of the procedure. Your data and phone will be in the exact same state as it was a before except for the fact that the damn dirty Dm-Verity message will be gone forever!!!
Q: Will this work on CUSTOM ROMs?
A: Of course. It has been tested to be perfectly working on even CUSTOM ROMs. Just follow the instructions in this post carefully where specific steps for CUSTOM ROMs are mentioned.
HIT THANKS IF I HELPED YOU. IT DOESN'T COST YOU ANYTHING, BUT IT MEANS A LOT TO ME...
Thanks mate..... You made my day..... Working perfectly.
Nice to see this thread on the day of release of oos 4.1.5 itself.
Deleted..
So well explained and working perfectly
One if the most detail step by step explanation
Thanks dev.
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
MohamedRaafat said:
Hi,
I have already done the second method on 4.1.4 but without reflashing the firmware so will I have to do it again when Install 4.1.5?
Click to expand...
Click to collapse
Do the second method only if you trigger DM Verity while installing 4.1.5
To be sure you don't trigger DM Verity while installing 4.1.5 follow the instructions in the OP...
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
prorokrak said:
Hi,
would it be too bold to ask if something similar could be prepared also for OP3?
I have exactly the same problem with DM-Verity triggered on my OP3. I have seen several guides how to get rid of it but they are sometimes contradictory and the whole process seems to be a bit overwhelming.
This solution seems to be the cleanest of all I have seen but I am not so lucky to own OP3T.
Would you be so kind to prepare this also for us, OP3 owners, if possible?
Of course, there can be many valid reason why not and I can perfectly understand that. But I decided to ask, just in case...
Click to expand...
Click to collapse
I have been thinking about it for the past few days...
Anyways I thought as no one asked they were not interested in getting the patched boot images for op3...
Ok.. they have released OOS 4.1.6..
So will push the links for the patched boot images for both op3 and op3T tomorrow after I test and get hands on the flashable ROMs.
The OP has been updated to accomodate both ONEPLUS 3T and ONEPLUS 3
Now this thread can be used for both models and will be updated as new OOS version come..
Enjoy!!!
NEW UPDATE RELEASED!!!
Links in OP...
Oxygen OOS 4.1.6 patched boot images for ONEPLUS 3T and ONEPLUS 3...
Thenks for this!
sparky vicky said:
How did you flashed the bootimg? through twrp? it's asking for 3 options like boot, recovery,system? im confused
Click to expand...
Click to collapse
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Xennet said:
Just flash the patched boot.img and select boot in the twrp option..
It's the boot image so boot option...
Click to expand...
Click to collapse
Yes i choose boot but still the warning showing on boot
sparky vicky said:
Yes i choose boot but still the warning showing on boot
Click to expand...
Click to collapse
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Im on OP3T, OOS 4.1.6
sparky vicky said:
Im on OP3T, OOS 4.1.6
Click to expand...
Click to collapse
Which is the warning being shown and explain the steps you did
Xennet said:
Which phone are you using op3 or 3t..
Did you flash 4.0.2 zip and type the commands
Tell the steps you did.
Which is the warning being shown?
DM Verity warning or the the phone is unlocked warning??
Click to expand...
Click to collapse
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
---------- Post added at 05:28 PM ---------- Previous post was at 05:26 PM ----------
Xennet said:
Which is the warning being shown and explain the steps you did
Click to expand...
Click to collapse
Flashed 4.1.6 with twrp at same time without reboot flashed bootpatch and rebooted to system and still the dm verity showung
Did i collapsed the procedure?:silly:
sparky vicky said:
Dm verity warning showing and asusal the unlocked warning also. Im on 3T with OOS 4.1.6. I need to flash 4.0.2 zip before this? Those are not mentioned in OP?
Click to expand...
Click to collapse
Mate do read the second post in the OP...
For getting rid of the DM-Verity message..
The first OP post is only for those who have no DM Verity warning on their phone..
If you already have DM Verity warning on your phone you have to follow the second post..it is clearly mentioned in the OP.. AND WRITTEN IN BOLD LETTERS..
Once you get rid of the DM Verity warning from next time onwards you have to follow only the instructions in the first OP post..
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
yohouse2 said:
I currently run OOS 5.1.2 (xXx No limits), with magisk 17.1 and blu_spark 3.1.2 (non treble) twrp. I want to update to Open Beta 18, so today i tried by updating the twrp to twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t (successfully). I then removed magisk by the uninstaller and tried to boot into system (still haven't flashed the beta), and it wouldn't load. I then returned to the updated recovery to flash the full zip of the beta but had a zip verification error. I disabled zip verification then got error 7 in the twrp. For now i have reverted to a NAND recovery i had made before updating the twrp, but i would still like to update to Open Beta 18. What did i miss, and how can i make it work? please keep in mind that i would prefer a dirty flash over a clean flash if possible.
Thanks
Click to expand...
Click to collapse
It's been discussed 100 times on the xXx thread that it's not recommended to switch between stable and beta the dirty way cause you're facing issues. Like you.
It's also not recommended by oneplus in the official threads cause of issues.
A clean installation(look at the beta thread) saves you hours on troubleshooting/headaches in the future.
And latest stable build has advanced reboot menu instead of beta
So I'm running the 03/25/2019 Lineage OS microG build for my OP5, it is Android Pie and I have the latest codeworkxx TWRP 03/11/2019 and PIE firmware.
When flashing the rom (clean install) I decided to go unencrypted this time so I used the following force encryption disable zip found bellow after I clean flashed/installed the rom...
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
...followed by flashing magisk right after. Everything worked, LOS PIE is installed and unencrypted/rooted perfectly.
Problem I am having is that now when I try and install the weekly builds through the Android OS updater, it does it's thing, reboots to recovery, installs the update, magisks then re-installs through the survival addon.d script but then the phone just gets stuck into a bootloop. While reading the install messages in TWRP it does mention that magisk is removing dm-verity for what it's worth.
Does this have something to do with magisk or the LOS ROM having an "encrypted kernel" by default and how I am installing an encrypted kernel/update over an unencrypted phone? Or is this some issue with magisk?
Does this mean if I want to flash weekly updates while keeping unencrypted status I will have to dirty flash them by downloading the zip, manually placing it in my storage, booting to recovery, flashing, then flashing the encryption disable zip again and finally Magisk instead of of just pressing a button in the Android OS updater?
Luckily I restored successfully from a backup but I'm wondering is I screwed myself over here setting up my rom without encryption. Never had this issue updating with the weekly builds when my phone was encrypted.
What do you guys think?
Alright well I managed to update my ROM without bootlooping, just like I thought instead of being able to use the built in OS update manager that does everything for you I have to manually download/transfer file to my phone, flash rom update, flash force encryption disable zip and then magisk again.
While this is an alright workaround for now, is there anyway to regain the stock updating functionality built into the rom while remaining unencrypted and having it NOT bootloop my phone each time? What if I want to use addonSU instead of Magisk, I don't think the disable encryption zip works unless you flash Magisk right after unless I have to update the rom, flash the disable zip, flash magisk, remove magisk and then use addonSU.
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
lenci98 said:
So I have a problem with the Oneplus 5. I got the xXx Nolimits ROM that's based on OxygenOS 5.1.3 and installed the Magisk xXx Nolimits 4.3 aswell.
I want to upgrade it to 9.0.4, but it won't do it with TWRP 3.2.3-0. Haven't tried it with TWRP 3.3.0.
Could it possibly work, if I go back to full stock and upgrade it via OTA and then flashing it again via TWRP 3.3.0?
The vendor partition is the problem here, I think.
Thanks for any help!
Click to expand...
Click to collapse
That's exactly how to do it. Use an Oreo era Codeworkx TWRP to flash a full OOS ROM. You have to have used 5.1.4 to create the Vendor partition so flash that. Let it overwrite TWRP with the stock recovery, and then OTA up to latest OOS. Fastboot flash latest Codeworkx TWRP and you're done.
Uninstall Magisk before you begin.
strongst said:
You guessed right. You need to flash stock 5.1.4 OxygenOS (which will create the vendor partition).
Then you can update to 9.0.4/9.0.5(remove the compatibility.zip from the rom files) either with OTA or manually flashing(see official oxygenOS rom threads for 9.0.5)then you can update the twrp to 3.3.x.
After this you can flash XXX magisk mod 4.3 onwards as it's a magisk module.
Click to expand...
Click to collapse
Exactly this was my plan. Thanks for the help. I struggled with this for literally months!
Hi all,
I once tried to update my rooted onePlus 5 (Magisk) to the latest oxygen os version, and lost everything. (with a corrupted Nandroid backup haha)
Since then, I've been pretty careful not to update anything, OTA isn't working anyway.
But now is about time to update it all.
I have flashfire, and Oxygen Updater (currently downloading OOS 5.1.4)
My question, before I go any further is:
If I download ALL the updates on Oxygen Updater and then flash them with flashfire (flash ZIP & OTA --> Select downloaded firmware --> proceed), I should be able to gradually flash all the new update until OOS 9.0.2, Keep root, and more importantly, Keep ALL my data, apps and all.
Is that correct? Does anyone have a proper flashfire walkthrough?
I'm a bit hesitant as someone seems to have had issues with Magisk as per below source's comment
source: https://forums.oneplus.com/threads/...with-flashfire-bonus-tip-oneplus-3-3t.621501/
Thanks!
To upgrade from Oreo non-treble to latest
- From TWRP, flash OxygenOS 5.1.4, Magisk and all the other mods and boot up once (to create vendor partition)
- From TWRP, flash OxygenOS 9.0.8, Magisk, all the other mods and a Pie-capable TWRP
PierreVicquery02 said:
To upgrade from Oreo non-treble to latest
- From TWRP, flash OxygenOS 5.1.4, Magisk and all the other mods and boot up once (to create vendor partition)
- From TWRP, flash OxygenOS 9.0.8, Magisk, all the other mods and a Pie-capable TWRP
Click to expand...
Click to collapse
And that will NOT erase any of my data?
Is it not possible to do it with flashfire? I don't have TWRP anymore I think..
Thanks!
mattou78400 said:
And that will NOT erase any of my data?
Is it not possible to do it with flashfire? I don't have TWRP anymore I think..
Thanks!
Click to expand...
Click to collapse
I actually don't know what flashfire is.
You will not lose data in theory, but it's a good thing to make a backup