Wanted to say thank you very much for pointing me to this! Exactly what I needed! I learned I have to unpack the image and get all of that and now I can customize it however I want UI wise!You might find something here..
Wanted to say thank you very much for pointing me to this! Exactly what I needed! I learned I have to unpack the image and get all of that and now I can customize it however I want UI wise!You might find something here..
Not to my knowledge as the changes are extensive.guys im on PA custom rom and want to flash coloros 12 . can I use this recovery for this?
New unofficial builds are up
Android 13 support
fbev2 now working
Note that fbev1 build is untested, test fastboot boot and report
do you mean fastboot flash boot twrp.img works for oos12?Do any of these versions work with OxygenOS 12.1? I'm on OOS 12.1 beta 2 on my regular Oneplus 7 (GM1900). I couldn't boot using fastboot boot on my fastboot mode, I don't know why but usually I need to flash TWRP in order to get it working.
No it doesn't, I tried fastboot boot twrp.img (not flash) since I didn't want to get stuck in a soft bootloop if something goes wrong. I'm on OOS 12 beta 2 and I have installed and working TWRP 3.6.2 11 without des-encryption ofcourse... I just wanted to update to a newer TWRP safetly.
which version did you install exactly?No it doesn't, I tried fastboot boot twrp.img (not flash) since I didn't want to get stuck in a soft bootloop if something goes wrong. I'm on OOS 12 beta 2 and I have installed and working TWRP 3.6.2 11 without des-encryption ofcourse... I just wanted to update to a newer TWRP safetly.
Hi there, like I put in last message I'm on TWRP 3.6.2 11, but that version can't descrypt data in OOS12. In the main post of this threat there's a telegram link so I would start asking there. Also there are new versions in the TWRP official site (https://twrp.me/oneplus/oneplus7.html) I tried both of them (FBEv1 and FBEv2) but neither of them worked for me.which version did you install exactly?
I'm on OOS12 Stable. and got in a bootloop caused by a magisk module.
I can't boot into any TWRP version that I tried.
is there another way apart from flashing new rom?
(I can connect to fastboot)
chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0
Hello, I saw your answer in the OP 7 Pro thread in Zullip, but this does not solve the problem with decryption on A12) The only way to recover data is to have A11 in a non-active slot, as far as I understandTried 3.7.0 on OOS11. Wasn't able to boot and in TWRP I wasn't able to decrypt data. Went back to 3.6.2. Everything was working except Bluetooth. It start crashing everytime I tried to use it. I tried to found some answers and according to TWRP support forum, it is because there are some changes in SELinux context in data folders. I don't have OOS12 yet, but it should be ok there. Anyway, I typed this in terminal with su and Bluetooth is working again:
Code:chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0
Hi, have you checked what happens to the device when you switch the active slot? (A to B, or B to A)which version did you install exactly?
I'm on OOS12 Stable. and got in a bootloop caused by a magisk module.
I can't boot into any TWRP version that I tried.
is there another way apart from flashing new rom?
(I can connect to fastboot)
You saved me brother. Thank youTried 3.7.0 on OOS11. Wasn't able to boot and in TWRP I wasn't able to decrypt data. Went back to 3.6.2. Everything was working except Bluetooth. It start crashing everytime I tried to use it. I tried to found some answers and according to TWRP support forum, it is because there are some changes in SELinux context in data folders. I don't have OOS12 yet, but it should be ok there. Anyway, I typed this in terminal with su and Bluetooth is working again:
Code:chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0
Had the same problem. Thanks!Tried 3.7.0 on OOS11. Wasn't able to boot and in TWRP I wasn't able to decrypt data. Went back to 3.6.2. Everything was working except Bluetooth. It start crashing everytime I tried to use it. I tried to found some answers and according to TWRP support forum, it is because there are some changes in SELinux context in data folders. I don't have OOS12 yet, but it should be ok there. Anyway, I typed this in terminal with su and Bluetooth is working again:
Code:chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0
So TWRP is still able to restore backups (with encryption?) and you're on A12?I have oneplus7pro 1917 and my problem was that I use cdma and I want to update but after the update the network disappears and there is no code to open diag to modify efs so I did the following downgrade to oxygen 11 and after that flasht twrp 3.6.2 and then install majsk root and then download the following add-on TWRP_A_B_Retention_Script and I did the backup efs via twrp and after that I downloaded the update ota12.1 and after the update did not reboot go to majsk and choose instal to inactive slot and choose reboot and then you will notice that the device has been updated to Android 12.1 and you have root and you also have twrp installed, go to twrp and do a restore and everything is ok
Yes brother, I have oneplus7pro 1917 and my problem was that I use cdma and I want to update but after the update the network disappears and there is no code to open diag to modify efs so I did the following downgrade to oxygen 11 and after that flasht twrp 3.6.2 and then install majsk root and then download the following add-on TWRP_A_B_Retention_Script and I did the backup efs via twrp and after that I downloaded the update ota12.1 and after the update did not reboot go to majsk and choose instal to inactive slot and choose reboot and then you will notice that the device has been updated to Android 12.1 and you have root and you also have twrp installed, go to twrp and do a restore I hope that this experience helped you, and use cdma yemen mobile and everything is goodI have oneplus7pro 1917 and my problem was that I use cdma and I want to update but after the update the network disappears and there is no code to open diag to modify efs so I did the following downgrade to oxygen 11 and after that flasht twrp 3.6.2 and then install majsk root and then download the following add-on TWRP_A_B_Retention_Script and I did the backup efs via twrp and after that I downloaded the update ota12.1 and after the update did not reboot go to majsk and choose instal to inactive slot and choose reboot and then you will notice that the device has been updated to Android 12.1 and you have root and you also have twrp installed, go to twrp and do a restore and everything is ok
Yes twrp 3.6.2-11So TWRP is still able to restore backups (with encryption?) and you're on A12?
On LineageOS 20.0 (A13) both fbev1 and fbev2 do not boot (stuck on "Fastboot Mode" screen after "fastboot boot twrp.img")New unofficial builds are up
Android 13 support
fbev2 now working
Note that fbev1 build is untested, test fastboot boot and report
This is what I did to install the latest version of OOS 11 and keep root and this version of TWRP.I am in the same position as the person above my comment. Can someone please give me instructions?
I am on a GM1917 with OxygenOS 10 Open Beta 19, and I want to jump to OxygenOS 11 Open Beta 5.
Is this instruction my best path? https://xdaforums.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/post-85157715
Any advice from someone that has already updated would be highly appreciated, especially if you have a GM1917.
PLEASE HELP!!!!!!
I installed the OOS 11 OB5 through OTA and then I did not reboot.
Then I installed Magisk in the Magisk app for both the current slot and slot_b.
Then I rebooted.
I was in my phone and nothing was wrong, then I booted into fastboot and I connected my phone to my computer.
Then I installed this version of TWRP just like the original post says.
Then I rebooted.
NOW IT BOOTS ONLY INTO THIS VERSION OF TWRP!!!!
HOW DO I GET MY PHONE BACK??????!!!!