[MODIFIED][RECOVERY] TWRP 3.2.1 for OnePlus 5 [OSS Clang Kernel][Enhancements]

Search This thread

xdvs23

Senior Member
Apr 11, 2015
1,054
1,925
23
Bavaria
xdevs23.me
UNOFFICIAL TWRP 3.2.1 (modified) for OnePlus 5

twrp-cheeseburger2.png


If you don't know how to return back to a working state if something is broken, please think twice before flashing this.

Everything seems to be working so far, if not, please report to me!
Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring. There seems to be an issue which causes a bootloop after restoring data partition at the moment.
I'm not responsible for any data loss, bricks, or whatever went wrong on your device. I can try to help you but I won't pay your RMA just because you decided to do this to your device.

Working
  • Everything except what's not working, see below

Not working / issues
  • Restoring data partition from backups will lead to boot issues on some ROMs (including OOS) if FBE-encrypted. It's not a TWRP issue but rather a side effect on how FBE works.


Download latest working image here (twrp-3.2.1-cheeseburger-127-20180106-190542-CET)
Download previous working image here (twrp-3.1.1-cheeseburger-84-20170820-194433-CEST)


While this TWRP is now very similar to codeworkx', it's a completely different source base and is independent from him.
This variant is a bit more bleeding edge and contains changes that are not available in TWRP images built from the official repositories.
If you want ultimate stability, consider using his TWRP instead.

Supported ROMs (encryption support):
  • OxygenOS 5.0.1
  • Android 8.1 ROMs (tested: halogenOS)

Please let me know in this thread whether it works for the ROM you are using.

Logs

Code:
adb pull /tmp/recovery.log
adb pull /cache/recovery/last_log
adb shell dmesg > dmesg.txt
And send me the last_log file, recovery.log file as well as dmesg.txt

Device tree: https://github.com/xdevs23/android_device_oneplus_cheeseburger-twrp
Kernel: https://github.com/halogenOS/android_kernel_oneplus_msm8998
Source tree: https://github.com/mintwrp-extended/
 
Last edited:

matssa

Senior Member
Jan 8, 2015
1,817
1,898
teamwin-recovery-project-twrp-logo-jpg.500302


Long story short: I am working on TWRP as well as halogenOS for the OnePlus 5.

To speed it up, I'll need a few experienced testers. PM me for more.

I'll use this thread to post a link to the working TWRP when it is done, and until TWRP for OP5 is official this thread should be kept alive (used as a placeholder for now).

Hey,

Heads up, seems that TWRP is already made in China: https://xdaforums.com/oneplus-5/dev...nlock-bootloader-intall-t3626122#post72778203

Btw, placeholders aren't a big thing in XDA ;)
 

xdvs23

Senior Member
Apr 11, 2015
1,054
1,925
23
Bavaria
xdevs23.me

matssa

Senior Member
Jan 8, 2015
1,817
1,898
It's not open sourced, is it? And it's chinese.
I guess we want something working and open to anyone.

Of course this thread can be closed if anyone does it before me.

True, but I dunno maybe the .img file already had some info that could help you out :)
 

fmotta

Senior Member
Jan 15, 2004
299
55
Just received the OP5.
Very experienced.
If you Need some testing... here I am.
 

Fentadroid

Senior Member
Jan 23, 2014
579
121
47
Turin
Just got my OP5, if you need to test something, i'm in.
Unlocked bootloader, all i need is to flash a working and trusted TWRP :)
 

saccentekennedy

Senior Member
Nov 15, 2012
361
141
I installed that TWRP and when I booted straight into it, it worked. Then I just tried to reboot to recovery again, and it looks like the old recovery patched itself?! TWRP was gone
 

santa leone

Senior Member
Nov 12, 2016
65
17
HEIDELBERG
OnePlus 8T
Google Pixel 6
TWRP für Oneplus 5

Hallo,

ich würde das gerne machen. Ich (eigentlich die Ehefrau) habe im Augenblick ein OP3 mit TWRP und 4.16. Aktiv benutze ich ein OP3T mit Lineage (Dianlujitao) Das Oneplus 5 ist heute gekommen. Und ich will nichts damit machen, bevor ich nicht ein lauffähiges TWRP habe.

Angst vorm Brick habe ich keine, denn es läßt sich immer alles wieder hinbiegen.

Kalle
 
  • Like
Reactions: Helle8855

HatRiGt

Senior Member
May 28, 2013
980
608
Chennai
Hallo,

ich würde das gerne machen. Ich (eigentlich die Ehefrau) habe im Augenblick ein OP3 mit TWRP und 4.16. Aktiv benutze ich ein OP3T mit Lineage (Dianlujitao) Das Oneplus 5 ist heute gekommen. Und ich will nichts damit machen, bevor ich nicht ein lauffähiges TWRP habe.

Angst vorm Brick habe ich keine, denn es läßt sich immer alles wieder hinbiegen.

Kalle

kindly use English This is international forum bro .
Using English makes others to understand what you r saying.
 
  • Like
Reactions: xdvs23

xdvs23

Senior Member
Apr 11, 2015
1,054
1,925
23
Bavaria
xdevs23.me
Hallo,

ich würde das gerne machen. Ich (eigentlich die Ehefrau) habe im Augenblick ein OP3 mit TWRP und 4.16. Aktiv benutze ich ein OP3T mit Lineage (Dianlujitao) Das Oneplus 5 ist heute gekommen. Und ich will nichts damit machen, bevor ich nicht ein lauffähiges TWRP habe.

Angst vorm Brick habe ich keine, denn es läßt sich immer alles wieder hinbiegen.

Kalle

Ich bitte dich mich privat anzuschreiben damit ich dir weitere Infos geben kann.

Please message me privately so that I can give you further information.
 

rwallhtc

Senior Member
Dec 1, 2013
72
19
london
teamwin-recovery-project-twrp-logo-jpg.500302


Long story short: I am working on TWRP as well as halogenOS for the OnePlus 5.

To speed it up, I'll need a few experienced testers. PM me for more.

I'll use this thread to post a link to the working TWRP when it is done, and until TWRP for OP5 is official this thread should be kept alive (used as a placeholder for now).

count me in. already unlocked, twrp installed and rooted.
 
  • Like
Reactions: HannibalIII

Top Liked Posts

  • There are no posts matching your filters.
  • 99
    UNOFFICIAL TWRP 3.2.1 (modified) for OnePlus 5

    twrp-cheeseburger2.png


    If you don't know how to return back to a working state if something is broken, please think twice before flashing this.

    Everything seems to be working so far, if not, please report to me!
    Warning: Make sure you make a backup of all your important data manually before flashing anything, making any backups or restoring. There seems to be an issue which causes a bootloop after restoring data partition at the moment.
    I'm not responsible for any data loss, bricks, or whatever went wrong on your device. I can try to help you but I won't pay your RMA just because you decided to do this to your device.

    Working
    • Everything except what's not working, see below

    Not working / issues
    • Restoring data partition from backups will lead to boot issues on some ROMs (including OOS) if FBE-encrypted. It's not a TWRP issue but rather a side effect on how FBE works.


    Download latest working image here (twrp-3.2.1-cheeseburger-127-20180106-190542-CET)
    Download previous working image here (twrp-3.1.1-cheeseburger-84-20170820-194433-CEST)


    While this TWRP is now very similar to codeworkx', it's a completely different source base and is independent from him.
    This variant is a bit more bleeding edge and contains changes that are not available in TWRP images built from the official repositories.
    If you want ultimate stability, consider using his TWRP instead.

    Supported ROMs (encryption support):
    • OxygenOS 5.0.1
    • Android 8.1 ROMs (tested: halogenOS)

    Please let me know in this thread whether it works for the ROM you are using.

    Logs

    Code:
    adb pull /tmp/recovery.log
    adb pull /cache/recovery/last_log
    adb shell dmesg > dmesg.txt
    And send me the last_log file, recovery.log file as well as dmesg.txt

    Device tree: https://github.com/xdevs23/android_device_oneplus_cheeseburger-twrp
    Kernel: https://github.com/halogenOS/android_kernel_oneplus_msm8998
    Source tree: https://github.com/mintwrp-extended/
    33
    Ok, kids are in bed :D

    op5-twrp-k3.img

    Changelog:
    Speed up backups over USB-OTG & Internal
    Updated kernel 4.4.74
    Exfat kernel support
    NTFS r/w support
    F2FS support

    https://github.com/katinatez/android_device_oneplus_cheeseburger/commits/android-7.1

    My baseline for comparison is my previous build k2 had 7-12 mb/second usb-otg
    New build k3 is coming at 11-21 mb/second usb-otg
    Remember to set your settings to compression for similar speeds.
    Good Night Enjoy, have to wake up in like 5 hours
    30
    Nice! :highfive: I am ready to try your new TWRP 3.1.1-k2 once uploaded. I'll also be testing it with xXx and Mokee ROMs.
    I can confirm I successfully was on oos 4.5.8 No Limits from @xXx and restores to mokee build date 8-1-17 from the USB-OTG, continued to update to mokee 8-5-17

    No boot loop, data restoration is fine, And no more ugly message
    "No OS your sure you want to reboot?" or something like that

    Here is a direct link of my build I'm running tests on for those that trust me. Also in my signature
    https://www.androidfilehost.com/?fid=889764386195921506

    Now to test restoring back to oos 4.5.8
    22
    @xdvs23
    I figured out the recovery error logs in red print!! Testing new recovery right now!
    I read every line in the recovery.log but found the answer in the kernel.log!
    The problem resulting in all those errors is all the fscrypt: commits in kernel, I just rebased kernel source to this and everything is golden!
    https://github.com/katinatez/android_kernel_oneplus_msm8998/tree/QC8998_N_7.1

    Also your Fix USB-OTG commit does not fix the usb-otg, I believe since the official twrp device tree is using a pre-built kernel. That is why its not picking up the kernel command line. I verified this by compiling official cheeseburger device tree and testing on my own phone.

    I just submitted a USB-OTG fix into gerrit which I compiled and verified it does fix it!
    https://gerrit.twrp.me/#/c/2634/
    21
    New test image (v83)

    Changelog:
    • Sync omni sources
    • Update kernel (rebase) & use linaro 6.3.1 for that (otherwise compilation won't work)
    • Import and patch OOS 4.5.6 crypto blobs
    • Use inbuilt libs only

    I said I would do a hybrid way of using the libs, that is prioritizing system libs and using inbuilt as fallback but I realized it doesn't make much sense doing that so I just decided to use the inbuilt libs only.

    Please test data backup & restore WITH ENCRYPTION (that means you need to be asked for a password/pin/gesture on TWRP start) on this test image! Note that I don't know whether the issue is fixed so that's why you should test it but do not involve your important data in this, make separate backups in other ways first!

    I updated the git repository accordingly, so view it here for further information.