[CLOSED] [RECOVERY] [UNOFFICIAL] [TWRP] [OnePlus 8T] [OOS13] [3-28-23]

Status
Not open for further replies.
Search This thread

apophis9283

Forum Moderator / Recognized Developer
Staff member
Everything should mount. Sorry the OP isn't all flashy. Should be able to do everything with OOS13 F62 firmware.

Please fastboot boot twrp.img to make sure it works before you permanently flash it.

twrp flashable zip link = https://www.androidfilehost.com/?fid=4279422670115731395

##### STOP HERE FOR DRAGONS BE AHEAD #####
THIS BUILD IS FOR PIXEL EXPERIENCE DUE TO ENCRYPTION DIFFERENCES!!!

twrp-pe flashable zip link = https://www.androidfilehost.com/?fid=4279422670115731408

device tree = https://github.com/APOPHIS9283/device_oneplus_kebab_twrp

Kernel source = https://github.com/APOPHIS9283/Singularity_Kernel

It's a stripped down version of my kernel.

Huge thanks to Team TWRP
@bigbiff
@Captain_Throwback
 
Last edited:

parag0n1986

Senior Member
May 3, 2015
373
100
38
LG V20
OnePlus 7 Pro
I have only tested this on OP8T with EROFS. Everything should mount. Sorry the OP isn't all flashy. Should be able to do everything with OOS13 F15 firmware.

Kernel source = https://github.com/APOPHIS9283/Krieg_Kernel

It's a stripped down version of my kernel.

Please fastboot boot twrp.img to make sure it works before you permanently flash it.

Huge shout out to Team TWRP and @AnierinB for being a great guy.

Link = https://www.androidfilehost.com/?fid=4279422670115709558
This work on custom ROMs with EROFS? I will definitely test if you aren't sure. 😁
 
  • Like
Reactions: apophis9283

BillGoss

Senior Member
Sep 2, 2010
5,884
5,215
Sydney
OnePlus 8T
Google Pixel 8 Pro
There's a bug in the latest version (230118 build). When copying the recovery log to sdcard it's created with the wrong attributes (see screenshot 1).
Which means that once the system is booted the file cannot be opened, renamed, or deleted (screenshot 2)
 

Attachments

  • Screenshot_230118-1.png
    Screenshot_230118-1.png
    26.9 KB · Views: 121
  • Screenshot_230118-2.jpg
    Screenshot_230118-2.jpg
    262 KB · Views: 124

apophis9283

Forum Moderator / Recognized Developer
Staff member
There's a bug in the latest version (230118 build). When copying the recovery log to sdcard it's created with the wrong attributes (see screenshot 1).
Which means that once the system is booted the file cannot be opened, renamed, or deleted (screenshot 2)
Probably something that got pulled in during the repo sync
 
Status
Not open for further replies.

Top Liked Posts