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

Search This thread

takui

Senior Member
Sep 18, 2013
134
13
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

Senior Member
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.
 
  • Like
Reactions: emam damon

Bleuzen

Senior Member
Dec 8, 2017
108
76
bleuzen.de
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

Senior Member
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.
 
  • Like
Reactions: mikedcarr

Styrke

Senior Member
Jul 16, 2012
438
511
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
 
Last edited:

Alfotiney

Member
Sep 26, 2012
15
4
OnePlus 7 Pro
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
 

Attachments

  • twrp in oneplus 7 pro A12.mp4
    4.4 MB · Views: 0
Last edited:

ckom26

Senior Member
Dec 18, 2014
108
27
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
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!
 

Pjotrofsky

Member
Jan 31, 2011
16
0
OnePlus 7 Pro
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?
 
Last edited:

varunpilankar

Senior Member
Jul 8, 2012
245
66
Sony Xperia SP
Moto X
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
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 😇 👍🏻

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

nity

Member
Jun 10, 2017
8
1
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?
 

varunpilankar

Senior Member
Jul 8, 2012
245
66
Sony Xperia SP
Moto X
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.
 
  • Like
Reactions: khalisz

Top Liked Posts

  • There are no posts matching your filters.
  • 96



    Introduction:

    Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Key Features:

    Touchscreen driven with real buttons and drag-to-scroll
    XML-based GUI that allows full customization of the layout true theming!
    Settings are saved to the sdcard and persist through reboots
    Ability to choose which partitions to back up and which to restore
    Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
    Onscreen keyboard
    Easy selection of internal/external storage

    In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.

    We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.

    Source Code:

    GitHub - https://github.com/TeamWin/android_bootable_recovery

    Gerrit Instance - http://gerrit.twrp.me

    If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.


    Hello, this is TWRP, for Oneplus 7/Pro/5G that supports Android 11
    can be flashed to boot with working decryption on android 11 roms


    bugs:
    backup/restore is unreliable

    Installation:
    1. fastboot boot twrp.img
    2. go to Advanced > Flash Current TWRP
    3. after that is done, if you were using a custom kernel, reflash it now
    4. if you were using magisk, reflash it now

    Updating to a newer build:
    1. download new build to internal storage
    2. go to Advanced > Install Recovery Ramdisk
    4. select the new image
    5. after that is done, if you were using a custom kernel, reflash it now
    6. if you were using magisk, reflash it now

    Send me a beer: Crypto(Preferred) | PayPal

    Trees:
    https://github.com/TeamWin/android_device_oneplus_guacamole
    https://github.com/TeamWin/android_device_oneplus_sm8150-common

    Telegram group: https://t.me/NSSFB

    Download: https://twrp.me/oneplus/oneplus7pro.html

    Unofficial 12 builds: https://www.pling.com/p/1835156/
    18
    new build is up

    fixed decryption on newer roms
    added an option to auto flash TWRP after flashing a rom
    fixed the problem where you needed to refresh sizes before being able to flash TWRP
    14
    this is now official

    12
    Uploaded new build for non FBEv2 fixing backup in most cases, you should still not depend on TWRP backup as the only backup you have as restoring while encrypted can be problematic
    11
    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://forum.xda-developers.com/t/...eamwin-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??????!!!!
    This is what I did to install the latest version of OOS 11 and keep root and this version of TWRP.
    Maybe it will help you.

    1. Install OTA update as a local upgrade but DON'T REBOOT.
    2. Open Magisk and install to direct install DON'T REBOOT.
    3. Open Magisk again and install to inactive slot NOW REBOOT.
    4. After reboot you should still be rooted and have the latest OTA update with stock recovery.
    5. Use phone stock recovery to boot into bootloader mode.
    6. Use your PC with adb to flash nebrassy 2 TWRP image in the phone bootloader mode.
    7. When in TWRP go to Advanced > Flash Current TWRP.
    8. Flash latest Magisk (have this .zip file in download folder already) again to keep root.
    9. Reboot and enjoy latest OOS11 version with TWRP and rooted.