Related
As OnePlus don't provide download links for all of for their Oxygen OS ROMs & OTA update zips, I've mirrored them on AndroidFileHost and put the links in one post so that they're easy to find.
This is not a support thread for issues you may have with Oxygen OS roms. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread.
There are two types of file for each ROM: signed flashable zips and OTA incremental update zips.
Signed flashable zips: These are recovery-flashable zips of the full ROM that won't overwrite your data partition. They can be flashed via stock or TWRP recovery.
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. They can be flashed via stock or TWRP recovery but will only work on non-rooted devices with no modifications to system files.
I've also included links for TWRP custom recovery and SuperSU
Magisk is also reported to be working with OOS 3.6.0+
NOTE: If you're using XDA Labs, the download links may not work - use a web browser
Signed flashable zips
Oxygen OS 3.6.1: OnePlus2Oxygen_14_OTA_032_all_1710240102.zip
Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_031_all_1706262034.zip
Oxygen OS 3.5.9: OnePlus2Oxygen_14_OTA_030_all_1704191749.zip (VoLTE fix)
Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_029_all_1703131134.zip
Oxygen OS 3.5.7: OnePlus2Oxygen_14_OTA_028_all_1701052113.zip (Fix for lost IMEI)
Oxygen OS 3.5.6: OnePlus2Oxygen_14_OTA_027_all_1612271635.zip
Oxygen OS 3.5.5: OnePlus2Oxygen_14_OTA_026_all_1612220228.zip
Oxygen OS 3.1.1: OnePlus2Oxygen_14_OTA_021_all_1610121102_wipe.zip
Oxygen OS 3.1.0: OnePlus2Oxygen_14_OTA_020_all_1608262242.zip
Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_019_all_1606041303.zip
Oxygen OS 3.0.1 Beta2: OnePlus2Oxygen_14_OTA_018_all_1605231631_OpenBeta2.zip
Oxygen OS 3.0 Beta: OnePlus2Oxygen_3.0_beta_bb10c034d8a4466d.zip
Oxygen OS 2.2.1-2: OnePlus2Oxygen_14_OTA_013_all_1604202136.zip
Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_012_all_1602261837.zip
Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634.zip
Oxygen OS 2.1.2: OnePlus2Oxygen_14_OTA_010_all_1511091726.zip
Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_009_all_1510112055.zip
Oxygen OS 2.1: OnePlus2Oxygen_14_OTA_008_all_1509191929.zip
Oxygen OS 2.0.2: OnePlus2Oxygen_14_OTA_006_all_1508211811.zip
Oxygen OS 2.0.1: OnePlus2Oxygen_14_OTA_005_all_1508192013.zip
Oxygen OS 2.0: OnePlus2Oxygen_14_OTA_002_all_1507251956_wipe.zip
OTA incremental update zips
Oxygen OS 3.6.0 > Oxygen OS 3.6.1: OnePlus2Oxygen_14_OTA_031-032_patch_1710240102.zip
Oxygen OS 3.5.9 > Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_030-031_patch_1706262034.zip
Oxygen OS 3.5.8 > Oxygen OS 3.6.0: OnePlus2Oxygen_14_OTA_029-031_patch_1706262034.zip
Oxygen OS 3.5.6 > Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_027-029_patch_1703131134.zip
Oxygen OS 3.5.7 > Oxygen OS 3.5.8: OnePlus2Oxygen_14_OTA_028-029_patch_1703131134.zip
Oxygen OS 3.5.6 > Oxygen OS 3.5.7: OnePlus2Oxygen_14_OTA_027-028_patch_1701052113.zip (Fix for lost IMEI)
Oxygen OS 3.5.5 > Oxygen OS 3.5.6: OnePlus2Oxygen_14_OTA_026-027_patch_1612271635.zip
Oxygen OS 3.0.2 > Oxygen OS 3.1.0: OnePlus2Oxygen_14_OTA_019-020_patch_1608262242.zip
Oxygen OS 3.0.1 > Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_018-019_patch_1606041303.zip
Oxygen OS 3.0 > Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_017-019_patch_1606041303.zip
--------------------------------------------------------------------------------------------
Hotfix update for users with Deutsche Telekom & Congstar SIMs
Oxygen OS 2.2.1 > Oxygen OS 2.2.1-2 : OnePlus2Oxygen_14_OTA_012-013_patch_1604202136.zip
--------------------------------------------------------------------------------------------
Oxygen OS 2.2.0 > Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_011-012_patch_1602261837.zip
Oxygen OS 2.1.2 > Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_010-011_patch_1512111634.zip
Oxygen OS 2.1.1 > Oxygen OS 2.2.1: OnePlus2Oxygen_14_OTA_009-012_patch_1602261837.zip
Oxygen OS 2.1.1 > Oxygen OS 2.1.2: OnePlus2Oxygen_14_OTA_009-010_patch_1511091726.zip
Oxygen OS 2.1 > Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_008-009_patch_1510112055.zip
Oxygen OS 2.0.2 > Oxygen OS 2.1: OnePlus2Oxygen_14_OTA_006-008_patch_1509191929.zip
Oxygen OS 2.0.1 > Oxygen OS 2.0.2: OnePlus2Oxygen_14_OTA_005-006_patch_1508211811.zip
Oxygen OS 2.0 > Oxygen OS 2.0.1: OnePlus2Oxygen_14_OTA_002-005_patch_1508192013.zip
TWRP & SuperSU
Oxygen OS 3
Official TWRP custom recovery
Modified SuperSU v2.82 TWRP flashable zip
Modified SuperSU v2.79 TWRP flashable zip
Modified SuperSU v2.76 TWRP flashable zip (Last Chainfire release)
Oxygen OS 2
Official TWRP custom recovery
Latest stable SuperSU
Unofficial Oxygen OS fastboot zips
These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. Along with the factory images, these contain flash-all bat scripts for fastboot flashing on both the 64GB & 16GB variants.
Using the flash-all bat file will revert your rom to fully stock Oxygen OS and will wipe your data partition (including userdata) and replace any custom recovery with stock. If you wish to keep your custom recovery and/or data, add "REM " (without the quotes) in front of the relevant lines in the bat file before running it. Alternatively, you can just enter each line from the bat file manually in a command window.
Note: The fastboot zips have been updated with new flash-all bat files that now flash the backup partitions too.
Oxygen OS 3.0.2: OnePlus2Oxygen_14_OTA_019_all_1606041303_fastboot.zip
Oxygen OS 2.2.0: OnePlus2Oxygen_14_OTA_011_all_1512111634_fastboot.zip
Oxygen OS 2.1.1: OnePlus2Oxygen_14_OTA_009_all_1510112055_fastboot.zip
The 3.0.2 images are sourced from @fareed_xtreme's Official OP2 Stock Reset to OOS 3.0.2 thread.
The 2.2.0 images are sourced from @fareed_xtreme's Official OP2 Stock Reset to OOS 2.2.0 thread.
The 2.1.1 images are sourced from @paultje162's Unbrick/Recover OnePlus 2 Back to stock 100% thread.
Credits to @fareed_xtreme & @paultje162 :good:
Unofficial Oxygen OS firmware zips
TWRP flashable zips containing just the firmware from Oxygen OS 3
Oxygen OS 3.6.1: OOS_3.6.1_Firmware.zip
Oxygen OS 3.6.0: OOS_3.6.0_Firmware.zip
Oxygen OS 3.5.9: OOS_3.5.9_Firmware.zip
Oxygen OS 3.5.8: OOS_3.5.8_Firmware.zip
Oxygen OS 3.5.7: OOS_3.5.7_Firmware.zip
Oxygen OS 3.5.6: OOS_3.5.6_Firmware.zip
Oxygen OS 3.5.5: OOS_3.5.5_Firmware.zip
Oxygen OS 3.1.1: OOS_3.1.1_Firmware.zip
Oxygen OS 3.1.0: OOS_3.1.0_Firmware.zip
Oxygen OS 3.0.2: OOS_3.0.2_Firmware.zip
Utilities
EFS_Backup.zip
Flashable zip to backup EFS partitions (modemst1 & modemst1). Includes Restore_EFS.bat to restore EFS via fastboot.
My_Backup.zip
Flashable zip to backup EFS partitions (modemst1 & modemst1) and persist partition. Includes restore_all.bat to restore the partitions via fastboot.
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Winflo said:
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
That's correct, you can't take OTA updates if you have root.
You can definitely trust @Spannaa, he's a well respected member here at XDA. I'm not sure whether he wants you to thrust him though
It's unknown where the unofficial TWRP comes from but the official TWRP comes directly from the Team Win Recovery Project.
Winflo said:
Verry nice post , does this mean when i root and use twrp , i cant do otas anymore and have to flash the complete updated rom via twrp ?
Edit and btw who made the twrp zips?
Can i thrust you ? ;D
Gesendet von meinem ONE A2003 mit Tapatalk
Click to expand...
Click to collapse
Best to use the official TWRP version. It was made by the twrp developers and tested by me. I would use it over the unofficial one.
In regards to OTA's, they can only be flashed if the system partition is stock. So if you have modified it, by adding root etc, You wont be able to flash the OTA. To resolve it, you can dirty flash the previous recovery and then the OTA. I have also tested this with the official TWRP recovery and it works 100%
Heisenberg said:
That's correct, you can't take OTA updates if you have root.
You can definitely trust @Spannaa, he's a well respected member here at XDA. I'm not sure whether he wants you to thrust him though [emoji14]
It's unknown where the unofficial TWRP comes from but the official TWRP comes directly from the Team Win Recovery Project.
Click to expand...
Click to collapse
Okay , so he made the Rom zips ? Could be compromised easily that was my worrie.
Winflo said:
Okay , so he made the Rom zips ? Could be compromised easily that was my worrie.
Click to expand...
Click to collapse
Well they're signed zips, which means they're created and signed by OnePlus (or their Oxygen team). There's nothing to worry about.
Good to have this on here. There is a thread on the OP forums but I don't go there often
Updating oxygen on my OPT
Hi I have been trying to update my OPT A2001 variant to a higher version of oxygen. However i'm stuck on oxygen 2.0.0. and can't seem to update through recovery and the OTA isn't available at settings.
My bootloader is unlocked and have got TWRP 2.8.7.0-oneplus2 recovery. SuperSU is installed and root checker confirms root access (I can't update binaries though..).
I've tried installing every version of oxygen past 2.0.1 in full versions and the patches. None of them work and they give the same error.
The logs:
Ioperation_start: 'Flashing'
Installing '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
script aborted: This package is for "OnePlus2" devices; this is a "oneplus2".
This package is for "OnePlus2" devices; this is a "oneplus2".
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'
Error flashing zip '/sdcard/OTA/OnePlus2OxygenOS2.0.1.zip'
Updating partition details...
I Data backup size is 4207MB, free: 33647MB.
I:Unable to mount '/usbstorage'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse
I would really appreciate any help. If you need more info, please ask!
Cheers:good:
michalanchelo said:
Hi I have been trying to update my OPT A2001 variant to a higher version of oxygen. However i'm stuck on oxygen 2.0.0. and can't seem to update through recovery and the OTA isn't available at settings.
My bootloader is unlocked and have got TWRP 2.8.7.0-oneplus2 recovery. SuperSU is installed and root checker confirms root access (I can't update binaries though..).
I've tried installing every version of oxygen past 2.0.1 in full versions and the patches. None of them work and they give the same error.
The logs:
I would really appreciate any help. If you need more info, please ask!
Cheers:good:
Click to expand...
Click to collapse
I can see two reasons why you cant use the OTA.
1 If you are using the official twrp recovery, you have the first version, there was a bug in it and the device name was set to oneplus2 and not OnePlus2 That is why you are getting this error: "This package is for "OnePlus2" devices; this is a "oneplus2"." - There has been a newer version (same version number) which has been released to resolve this issue
2 The next reason why you cant update the OTA is you are rooted. You have modified the contents of the system partition. The OTA checks the contents before installing and if different wont install.
I would suggest you do the following:
Update to the current version of TWRP from the site, it is same version number, but newer build
Download the full 2.1 rom and dirty flash.
Root device
You will then be good to go. For future OTA's you will need to un-root and then you will be able to install the OTA's.
Stephen said:
I can see two reasons why you cant use the OTA.
1 If you are using the official twrp recovery, you have the first version, there was a bug in it and the device name was set to oneplus2 and not OnePlus2 That is why you are getting this error: "This package is for "OnePlus2" devices; this is a "oneplus2"." - There has been a newer version (same version number) which has been released to resolve this issue
2 The next reason why you cant update the OTA is you are rooted. You have modified the contents of the system partition. The OTA checks the contents before installing and if different wont install.
I would suggest you do the following:
Update to the current version of TWRP from the site, it is same version number, but newer build
Download the full 2.1 rom and dirty flash.
Root device
You will then be good to go. For future OTA's you will need to un-root and then you will be able to install the OTA's.
Click to expand...
Click to collapse
Thank you very much kind sir for your fast reply and clear feedback/solution I wouldn't have figured that out by myself anytime soon
Have a nice day!
I am currently using oxygen 2.0.3, stock, non rooted. Can I dirty flash the 2.1 rom with stock recovery or should I use TWRP?
Sent from my ONE A2005 using Tapatalk
It should, apparently, work in stock recovery so give it a go
EddyOS said:
It should, apparently, work in stock recovery so give it a go
Click to expand...
Click to collapse
Thanks, worked for me!
Sent from my ONE A2001 using Tapatalk
Worked for me as well. Its the way to go I think.
Sent from my ONE A2001 using Tapatalk
timmberg said:
Thanks, worked for me!
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
Kishes Mist said:
Worked for me as well. Its the way to go I think.
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
Good to know, I wasn't sure if they were TWRP-only
I actually used the latest version of TWRP. But how did it was re flashed 2.0.2 which un rooted then put the 2.1 in a queue so basically it flashed then flashed again all in one go
Sent from my ONE A2001 using Tapatalk
Kishes Mist said:
I actually used the latest version of TWRP. But how did it was re flashed 2.0.2 which un rooted then put the 2.1 in a queue so basically it flashed then flashed again all in one go
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure the cumulative zips overwrite TWRP with stock recovery, so what I did is flash the zip with TWRP, then flash the TWRP recovery image before rebooting. This way you avoid needing a computer or root access to get TWRP installed again.
ΦDroid said:
I'm pretty sure the cumulative zips overwrite TWRP with stock recovery, so what I did is flash the zip with TWRP, then flash the TWRP recovery image before rebooting. This way you avoid needing a computer or root access to get TWRP installed again.
Click to expand...
Click to collapse
The full rom zips don't overwrite TWRP ?
Sent from my OnePlus 2
Spannaa said:
The full rom zips don't overwrite TWRP ?
Sent from my OnePlus 2
Click to expand...
Click to collapse
OK, I just assumed that it did since the 2.1.0 OTA directly from OnePlus overwrote it. I'll keep that in mind next time.
Edit: thanks a lot for sharing these, I already managed to break WiFi the first day with this device by flashing kernels. The full rom zip fixed it right away.
Sent from my ONE A2005 using Tapatalk
Which version of the kernel should I download?? The obivous of course is to download the first, it is just that it says CM and I was wondering if this version of the kernel is only for CM roms. I want to keep the stock rom and jsut flash the bluespark kernel. Should I go for the first one?
Also, where I am supposed to save the kernel file in order to install it? I don't have an SD card.
Thanks in advance.
http://prntscr.com/aerhrq
There is a Q&A section.
CM > CM based roms
OOS > OxygenOS stock rom
Enviado desde mi ONE E1005 mediante Tapatalk
Fotios Sikalias said:
Which version of the kernel should I download?? The obivous of course is to download the first, it is just that it says CM and I was wondering if this version of the kernel is only for CM roms. I want to keep the stock rom and jsut flash the bluespark kernel. Should I go for the first one?
Also, where I am supposed to save the kernel file in order to install it? I don't have an SD card.
Thanks in advance.
http://prntscr.com/aerhrq
Click to expand...
Click to collapse
It's the second file from the top on your screenshot. You can save it on the internal memory too, but you still need to root the phone and install custom recovery. Somewhere in the general section there's a thread about rooting and flashing.
(just so you know, you "flash" a kernel or a rom, not "install" - don't worry, you'll get there )
Regarding the screenshot:
The first one is the latest version uploaded by the OP (the developer - the one who started that specific thread), it says CM since it's only for CM based roms, not stock ones. All the ones under that one are for stock, hence it says OOS (oxygen os), just the version differs .98, 101, 104, the higher the version number the newer the kernel - the upload date in the middle can help you figure out which one is the latest version if you can't tell by the file name.
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Oh. I have that problem too. CM 13.1 not stable!
Jaccob25 said:
Hi everyone. I was read a lot off discussions about i9100 with CM12.1 but I still don't know how to do it without some problems.
My phone actually running CM13.1 latest nightly build with Team Win TWRP recovery v 2.8.XXX and maybe DorimanX kernel? I don't know how to find Kernel name and version... I would like to ask you how to go to Cm12.1 build with pico or nano GAPPS (And what build I should download). I need the most stable build for daily use. Next how to replace CM recovery with TWRP 3.0.2. . I am totally confused. I'll be glad for any help.
Click to expand...
Click to collapse
Firstly look under settings -> about device and it will tell you the kernel version. If it says 3.0.101-CM------, you have the stock CM13 kernel. You said you have TWRP 2.8.x.x and not CM recovery?? This means you already have the isorec recovery enabled. All you need to do is flash the 3.0.2-1 .img from this recovery and you will have the newer one installed. And just do normal backup/wipes and install CM12.1 as you would any other rom. Just remember to use 5.1 gapps(arm;5.1;pico/nano)
Here is the last official CM12.1 I uploaded
Here is a more up to date unofficial CM12.1
noppy22 said:
Firstly look under settings -> about device and it will tell you the kernel version...
Click to expand...
Click to collapse
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Jaccob25 said:
Yes I have stock cm13 kernel and TWRP flashed. Can I flash new TWRP via Odin?
Thank you very much!
Click to expand...
Click to collapse
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
noppy22 said:
I don't think you can flash a .img file with odin. Honestly if you want to downgrade to 5.1.1 it would be easier to do it in one go.
Flash CM12.1, gapps, then TWRP 3.0.2-1.img all from TWRP 2.8
Click to expand...
Click to collapse
Ohh I thought that TWRP can't flash img file.
Thanks for advice. I try it today.
So I try that and almost everything works fine. Only GPS fixing seems like a little bit problematic. But I don't know my testing was short. I will see.
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
teraghik said:
May I ask a supplementary question - I am in a similar position, I have an i9100 which I upgraded from stock 4.1.2 Jelly Bean to CM13 following (most of) djibe's guide here
So I now have CM13 ROM with kernel version 3.0.101, re-partitioned with Lanchons repit, and with recovery TWRP 3.1.0 installed and functioning.
I want to revert from CM13 to CM12.1. From above, I believe that I can simply backup, wipe, then flash the CM12.1 ROM (I'll be using the last nightly, cm-12.1-20160203-NIGHTLY-i9100.zip) - is that correct?
My question/confusion is, do I also need to flash an isorec-compatible kernel (ie kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100.zip)? The isorec thread (here) says that the "Official CyanogenMod 12.1 and 13 kernels are now IsoRec-compatible", so it seems to me unnecessary, but many threads/guides on XDA say to flash one of Lanchon's kernels.
Please could someone advise, and my apologies for what is probably an ignorant question.
Click to expand...
Click to collapse
You are correct. Isorec support was implemented before that last nightly iirc. No need to flash any kernels.
Note: Only use the official TWRP 3.1 from the TWRP website or the.gangster's one which is basically the same. They are compatible with the earlier android versions.
Hi Noppy,
Thanks very much for taking the time to reply and help - I am using "the gangsters" TWRP 3.1 from djibe's thread, appreciate the heads up. I can confirm that I flashed CM12.1, and it works fine!
Why don't you follow my tutorial to get the perfect smooth Android 7.1 for SGS2 ?
Here it is : https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
TWRP built for the Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
Flash through twrp or fastboot
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
To permanently flash it:
Code:
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Official
Unofficial
XDA:DevDB Information
[OFFICIAL] TWRP 3.4.0.0 [lux], Tool/Utility for the Moto X Play
Contributors
althafvly
Source Code: https://github.com/TeamWin/android_kernel_motorola_msm8916
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2020-10-19
Reserved
hmm.. what does this mean? does it mean that it opens up for treble support? or does this bring treble support? either way, thank you
How's your twrp different from @squid2 's ?
Will GSIs boot on lux if this recovery is used properly? Just wanna know if anyone tried.
plb-dev said:
Will GSIs boot on lux if this recovery is used properly? Just wanna know if anyone tried.
Click to expand...
Click to collapse
I tried and it would not boot. I have a question to you, from which stock rom did you upgrade to custom roms? I am trying different modem imgs and none of them are really good.
Shepxda said:
I tried and it would not boot. I have a question to you, from which stock rom did you upgrade to custom roms? I am trying different modem imgs and none of them are really good.
Click to expand...
Click to collapse
The first custom ROM i installed was AICP N from stock 6.0.1 . Then I kept switching between nougat ROMs, and even some alpha oreo ROMs. When stock 7.1.1 came out I installed it, kept for a while and then kept switching between custom ROMs again. Currently in LOS14.1 .
New Twrp Builds Based Android 9.0
https://sourceforge.net/projects/althafvly/files/twrp/
althafvly said:
New Twrp Builds Based Android 9.0
https://sourceforge.net/projects/althafvly/files/twrp/
Click to expand...
Click to collapse
now while you going to be official maintainer for lineageOS why don't put twrp on the twrp official device status too!
This TWRP version works fine. Thanks OP for the build!
LineageOS 17 falied to flash OTA
I guess my post thread makes it more clear what's the issue. I had downloaded latest update and it failed to flash the update(TWRP). It booted to recovery well from updated menu. I am attaching logs for the same.
@althafvly any word from you?
methuselah said:
I guess my post thread makes it more clear what's the issue. I had downloaded latest update and it failed to flash the update(TWRP). It booted to recovery well from updated menu. I am attaching logs for the same.
Click to expand...
Click to collapse
You need to use lineage recovery for ota support. Lineage is now more focused on lineage recovery than twrp. Older/newer twrp might or might not work.. Because lineage17 officially support lineage recovery.
althafvly said:
TWRP built for the Moto X Play. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery.
Flash through twrp or fastboot
To temporarily boot this recovery:
Code:
To permanently flash it:
Code:
Download
XDA:DevDB Information
[UNOFFICIAL] TWRP 3.4.0.0 [lux], Tool/Utility for the Moto X Play
Contributors
althafvly
Source Code: https://github.com/twrp-m8916/twrp_recovery_manifest
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2020-06-12
Click to expand...
Click to collapse
THANKS :highfive::highfive::highfive::highfive::highfive::highfive::highfive::highfive::silly::silly::silly::silly::silly:
Official Builds Up (android-9.0 based)
thanks for the official support. You have really achieved a lot lately! does the official version work with ota von los17? some device this will not work from may 2020.
Hi guys. I currently have built 3.1.1-r1.
I am having troubles installing LineageOS 17.1 weeklies.
Then I said, I need to update TWRP.
But, I already did data wipe on my phone.
Is it still possible to flash new TWRP? I find I only need to boot into fastboot, then fastboot flash recovery twrp.img and then back to recovery. Is that right?
teteu86 said:
Hi guys. I currently have built 3.1.1-r1.
I am having troubles installing LineageOS 17.1 weeklies.
Then I said, I need to update TWRP.
But, I already did data wipe on my phone.
Is it still possible to flash new TWRP? I find I only need to boot into fastboot, then fastboot flash recovery twrp.img and then back to recovery. Is that right?
Click to expand...
Click to collapse
Yes, that should work. Look here for more details on how to do it properly (just ignore the bit about LOS recovery if you need TWRP):
Install LineageOS on lux | LineageOS Wiki
wiki.lineageos.org
works LOS OTA with TWRP 3.5.0 again? I am currently using LOS recovery but would like to use twrp again because of backup and settings. has anyone tested it?
R!ffRaff said:
works LOS OTA with TWRP 3.5.0 again? I am currently using LOS recovery but would like to use twrp again because of backup and settings. has anyone tested it?
Click to expand...
Click to collapse
unfortunately not, the OTA update no longer destroys the LOS but the update script does not run. the phone boot into the twrp, that's it
for aööe who want to have OTA updates should switch to the lineage recovery. for all others who need a manual update, you can continue to use twrp
.One time use of a computer or laptop is required for booting in to oreo recovery. Your internal storage is going to be wiped in this process so backup your stuff.
Recovery for oreo firmware OrangeFox-R10.1_O1-Stable-riva.zip
Nougat firmware fw_riva_miui_HM5AGlobal_V10.1.1.0.NCKMIFI_8cb19207b7_7.1.zip
Recovery for nougat firmware OrangeFox-R10.1_N1-Stable-riva.zip
Fix for sensors and ril sensorfix.zip, efsfix.zip
1. Download all above files
2. Boot into oreo recovery through fastboot (you can continue or skip and use the AIO zip below)
3. Flash nougat firmware and nougat recovery
4. Format internal storage
5. Flash given fixes
6. Reboot
[UPDATE: 30/01/2020]
All in one zip is available
Download:
Downgrade (O To N)Firmware.zip
Guide for using this zip
1). Reboot to oreo recovery
2). Flash O to N zip file (from above link)
3). Reboot to recovery again
4). Flash the nougat fw based recovery you want,
or just skip this step.
5). Reboot to recovery again( if u flashed a new recovery)
6). Wipe System, Vendor, Data, Cache, and Dalvik
7). Flash ROM
8). Finally, reboot to system
NaAnBcEhEuL9A8K7 said:
[*]Recovery for nougat firmware download
Click to expand...
Click to collapse
Whoops, we can't find that page.
fix please. Thx)
sjcbank said:
Whoops, we can't find that page.
fix please. Thx)
Click to expand...
Click to collapse
Fixed
My first thought was: why downgrade from Oreo to Nougat??
supergrass said:
My first thought was: why downgrade from Oreo to Nougat??
Click to expand...
Click to collapse
Because custom roms won't boot on stock oreo kernel.
NaAnBcEhEuL9A8K7 said:
Because custom roms won't boot on stock oreo kernel.
Click to expand...
Click to collapse
What custom ROM are you using? I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
supergrass said:
I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
Click to expand...
Click to collapse
There is something called personal preference.
Just like you prefer MIUI some others prefer custom ROMs
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
Firmware-7.1+RecoveryProject-3.1-Nougat.zip
Firmware-8.1+RecoveryProject-3.1-Oreo.zip
sjcbank said:
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
Firmware-7.1+RecoveryProject-3.1-Nougat.zip
Firmware-8.1+RecoveryProject-3.1-Oreo.zip
Click to expand...
Click to collapse
Where you got this?
NaAnBcEhEuL9A8K7 said:
Where you got this?
Click to expand...
Click to collapse
Here for you
https://4pda.ru/forum/index.php?showtopic=879215&st=10980#entry82426459
supergrass said:
What custom ROM are you using? I have found them all disappointing, one way or another. I'm currently on rooted MIUI 10 Oreo.
Click to expand...
Click to collapse
How you root your MIUI 10 Oreo,which recovery you flash? thank you
钱八斤 said:
How you root your MIUI 10 Oreo,which recovery you flash? thank you
Click to expand...
Click to collapse
https://drive.google.com/file/d/1-8lZA1zUrur_PT5AvRkd8eKrz8rVTzv7/view?usp=drivesdk
sjcbank said:
Firmware taken from the latest global firmware HM5AGlobal-V10.1.1.0.NCKMIFI-7.1 and HM5AGlobal-V10.1.2.0.OCKMIFI-8.1
TWRP in the archives PE-RecoveryProject-3.1 (for the recovery we say thank you Zikiel )
Switch from 7 to 8, Flash Archive Firmware-8.1 RecoveryProject-3.1-Oreo from the recovery; reboot into the recovery; clean up the corresponding sections and install the firmware, root and patches according to your desire; and in the same order from 8 to 7, flash Firmware-7.1 RecoveryProject-3.1-Nougat reboot in recovery cleaning and installing firmware. It is better to stir archives on a memory card and for features and differences in Firmware recovery for 7 does not see the date section from 8
A backup is welcome, for its restoration it is recommended that how it was made !!!
[drive.google.com/file/d/16DuYSRZIJGy94fcgAnHC3Bp5xgS7PM3L/view?usp=sharing"]Firmware-7.1+RecoveryProject-3.1-Nougat.zip[/URL]
[//drive.google.com/file/d/1FrznxeTnAob-Ai0ye_ZKHHj9Zl1c35wP/view?usp=sharing"]Firmware-8.1+RecoveryProject-3.1-Oreo.zip[/]
Click to expand...
Click to collapse
What is this?
Please, what I must used to downgrade in fastboot? MIUI ROM Flashing Tool? Or can you please send me, how I downgrade it? Thank you.
Why are these custom ROMs not compatible with Oreo Firmware??
Edit: I am planning to compile a ROM for the first time. All I have ever done is to compile recovery(For Redmi 5A) where they are compatible with Oreo firmware(just like other recoveries).
akil777 said:
Why are these custom ROMs not compatible with Oreo Firmware??
Edit: I am planning to compile a ROM for the first time. All I have ever done is to compile recovery(For Redmi 5A) where they are compatible with Oreo firmware(just like other recoveries).
Click to expand...
Click to collapse
Nobody has worked on the oreo sources yet so...
@sunnyraj84348 might be working on it, I don't know, I'm just assuming. Maybe he's focusing on Android 10 ROMs more than Oreo kernel.
NaAnBcEhEuL9A8K7 said:
Nobody has worked on the oreo sources yet so...
@sunnyraj84348 might be working on it, I don't know, I'm just assuming. Maybe he's focusing on Android 10 ROMs more than Oreo kernel.
Click to expand...
Click to collapse
okay, thanks.
Working on a custom rom is very time consuming. Till now I am still trying to create a device tree for my Mi cc9 so that I can make a ROM alongside with the sources provided.(I'm new to things like compiling roms)
akil777 said:
okay, thanks.
Working on a custom rom is very time consuming. Till now I am still trying to create a device tree for my Mi cc9 so that I can make a ROM alongside with the sources provided.(I'm new to things like compiling roms)
Click to expand...
Click to collapse
Good luck with your project ?
[ i'm noob ] Does orange fox recovery working properly on miui 11 ? Unfortunately,i was update my riva to miui 11,succed to unlock bootloader but not with twrp,when i was flash twrp via fastboot,twrp just show up red screen then dim to black screen & only vibrate when touched. I was forgot to add command delete recovery from fastboot,before flashing twrp. Please help,any suggest to proper twrp at stock miui 11 global stable ? Sorry for bed english.
Not work properly when downgrade from MIUI 11 Oreo,now i experience messed up with stock miui rom,try to reverse back with flash full recovery rom from twrp,succed to flash,but when boot into setup wizard,error message appear,eg; "miui daemon has stopped,under that pop up,again error pop up "google service framework has stopped" > "xiaomi service framework has stopped" > "setting has stopped" & bla...bla..bla...! I can't pass setting wizzard,can't continue to normal screen. Then i flash pixel xperience rom 9.0,flawlessly boot until setting wizard done,run smoothly without error. Usually i like to change between custom then stock rom from twrp when i was bored with 1 rom. But now i'm stuck on pixel experience 9.0 (caf) & no twrp working properly when want to flash stock miui oreo.