[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project

[takui]

hello, hope someone could help me...

I had to rollback from that crap of android 12 to android 11, all worked fine till I had to install twrp. After it, in the OS I got a bunch of system app crashing: bluetooth (which doesn`t even start), dolby atmos, system messages, system update, choosing the launcher don`t save any option...etc)

I` ve tried to clean their data and cache, nothing. It happened only after twrp. I` ve tried the last 10.0.9.1 both for global and EU, also I` ve tried an older release, same problems.
I` ve also tried to unstall twrp but wasn`t a solution, system keeps crashing.
Also i` ve tried restoring original boot.img or also to flash a patched boot.img from trwp app, nothing.

Any ideas? I need it to hide root from bank apps otherwise they won`t work...thanks guys

 

[theslam08]

On LineageOS 20.0 (A13) both fbev1 and fbev2 do not boot (stuck on "Fastboot Mode" screen after "fastboot boot twrp.img")

Had same issue while on the new crDroid 9 (A13). This ROM is based on OOS 12, which required me to flash the OOS 12 firmware in order to be able to use the crDroid 9 ROM.

So I think the culprit here is if you've flashed OOS 12 firmware, TWRP 3.7.0 does not work - even if you're not on OOS 12 now. Because I believe I read that the new lineageOS A13 is rebased on OOS 12 now. Which would make sense why you and I are having this same issue.

Was very scared at first with that screen. I held the power button for like 1 minute nothing happened, held both vol- and vol+ with power button for like 30 seconds and it finally turned off. Then it wouldn't turn back on. Had to fiddle with button combinations. But afer more testing, I found it's just a simple command: fastboot reboot bootloader and bam the phone is fine. Wooo. Had me bugging for a min. Never had that happen before.

So forewarning to anyone trying this. Dont use TWRP yet if you've flashed OOS 12 firmware. It doesn't seem to work yet.

///Unless fastboot boot twrp.img isn't the correct command anymore? Maybe it needs to be just flashed? Like
fastboot flash boot_a twrp.img?
fastboot flash boot_b twrp.img?

IDK but I'm not trying that, sorry someone else can confirm if that is a yes or no.

 

[Bleuzen]

So I think the culprit here is if you've flashed OOS 12 firmware, TWRP 3.7.0 does not work - even if you're not on OOS 12 now. Because I believe I read that the new lineageOS A13 is rebased on OOS 12 now.

Could be the problem. I also have OOS 12 firmware installed.

Was very scared at first with that screen. I held the power button for like 1 minute nothing happened, held both vol- and vol+ with power button for like 30 seconds and it finally turned off.

Try fastboot reboot bootloader, worked for me without holding any buttons.

 

[theslam08]

Could be the problem. I also have OOS 12 firmware installed.


Try fastboot reboot bootloader, worked for me without holding any buttons.

"Try fastboot reboot bootloader", yup I actually figured that out at one point. What a relief lol. Thought it was stuck on that screen at first. Always nervous doing something different first time around. Then once you know it's like oh okay no biggie.

 

[Styrke]

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

I confirm this method works for upgrading to A12 while keeping root. Couldn't believe that with this, the official twp 3.6.2 for A11 stays working on the A12 after the upgrade.
Just for info, booting unofficial twrp 3.6.2 for A12 also didn't work for me. Phone got stuck in fastboot logo.

Edit: If you add a password or fingerprint the storage get encrypted and twrp will be unable to decrypt. It seems its a known bug in a12

 

[Alfotiney]

I confirm this method works for upgrading to A12 while keeping root. Couldn't believe that with this, the official twp 3.6.2 for A11 stays working on the A12 after the upgrade.
Just for info, booting unofficial twrp 3.6.2 for A12 also didn't work for me. Phone got stuck in fastboot

Watch this video from my device

 

[ckom26]

Anyway, I typed this in terminal with su and Bluetooth is working again:

chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0

Relatively unrelated: my bluetooth (Poco X3 Pro, latest CrDroid 11, TWRP 3.6.2) stopped working suddenly and logcat revealed an error accessing /data/user_de/0. Executing this chcon command (having added a couple of missing /'s) fixed it. Thanks, buddy!

 

[cousinit99]

@Nebrassy FBEv1 build appears to be unable to decrypt data for OOS11.

 

[khalisz]

@Nebrassy FBEv1 build appears to be unable to decrypt data for OOS11.

Yes and neither OOS12.
Use 3.6.2 for OOS11.
No TWRP working for OOS12 actually.

 

[cousinit99]

Decryption for OOS12 is working for me on 3.7.0_12.

 

[Pjotrofsky]

New unofficial builds are up

Android 13 support
fbev2 now working

Note that fbev1 build is untested, test fastboot boot and report

I tried both the https://www.pling.com/p/1835156/ and the https://eu.dl.twrp.me/guacamole/ but both .img lead me or to a "fastboot mode" logo which hangs or to a TWRP instance which won't let me decrypt my filesystem

And/or when I try to install TWRP-3.6.2-guacamolev2-Nebrassy-02-10-22.img via fastboot flash recovery TWRP-3.6.2-guacamolev2-Nebrassy-02-10-22.img I get this:

target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.502s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.508s

So do I need to downgrade to oos11 for TWRP/magisk/adblock support?

 

[varunpilankar]

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:

chcon u:object_r:system_data_file:s0 /data data /data/misc/profiles/cur/0 /data/user/0 /data user_de/0

I have similar problem on my phone.. Bluetooth and system settings not working..

Issue fixed by using the right command (missing few forward slash).

Thank you

chcon u:object_r:system_data_file:s0 /data/data /data/misc/profiles/cur/0 /data/user/0 /data/user_de/0

 

[varunpilankar]

Watch this video from my device

How come you don't have a bootloader unlock warning?

 

[Alfotiney]

How come you don't have a bootloader unlock warning?

Of course Bootloader unlock and rooted but in android 12 you didn't see wearing

 

[nity]

hi, can I know what is the difference between FBEv1 and FBEv2?
currently, im and oos11 and I wanted to flash evolution x (android 13)... which one should i use?

 

[khalisz]

hi, can I know what is the difference between FBEv1 and FBEv2?
currently, im and oos11 and I wanted to flash evolution x (android 13)... which one should i use?

FBEv2 is ONLY for custom rom.

 

[nity]

FBEv2 is ONLY for custom rom.

Oh I see, can I just install FBEv2 on oos11 and thn flash custom ROM? Does that work?

 

[varunpilankar]

Oh I see, can I just install FBEv2 on oos11 and thn flash custom ROM? Does that work?

I would consider something like this:

1. Download Latest TWRP FBE v1 and V2 (img and installer) along with your rom files
2. Install TWRP FBEv1 (which is for stock rom)
3. Reboot to recovery and take a nandroid backup / full system backup
4. Once backup is completed. Install TWRP FBEv2 and reboot to recovery.
5. Now follow your rom installation guide.


Note - if things go south, at least you have a restore point to go back to.

 

[nity]

Does this latest TWRP support android 13?

 

[khalisz]

Oh I see, can I just install FBEv2 on oos11 and thn flash custom ROM? Does that work?

No you can't, it will not work.
Install FBEv2 only if you will install a custom ROM.