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

Search This thread

burcinkarabacak

Senior Member
May 28, 2015
120
3
54
hi everybody
i had a problem about backup. when i want to back up my system. i got an error failed to mount '/system' (structure needs cleaning)

how can i solve. i dont have early back up so i dont want wipe everything. please help me

thank you
 
Last edited:

Stupifier

Senior Member
Jun 8, 2010
1,914
680
hi everybody
i had a problem about backup. when i want to back up my system. i got an error failed to mount '/system' (structure needs cleaning)

how can i solve. i dont have early back up so i dont want wipe everything. please help me

thank you
Uhh... Just go ahead and mount /system..... There is an obvious menu for this in TWRP
 

Pepp671

Member
Mar 31, 2017
20
6
Hello all,

I have a small question regarding openrecoveryscript. I tried to use the decrypt command but it wouldn't work as I was still welcomed with a screen to provide my password. My openrecoveryscript looks like this:

decrypt 0000

Do you know if this is a problem with TWRP (I am currently on Blue TWRP) or if I am writing the command wrong?

Thanks a lot,

Florian
 

jahidinbedod

Senior Member
Apr 27, 2014
292
129

Attachments

  • Screenshot_2017-11-20-17-53-30.png
    Screenshot_2017-11-20-17-53-30.png
    65.2 KB · Views: 1,094

marko94

Senior Member
Jul 28, 2012
2,801
1,273
34
Zagreb
Xiaomi 12X

spysky

Member
May 25, 2009
45
10
Nothing Phone 1
hi everybody
i had a problem about backup. when i want to back up my system. i got an error failed to mount '/system' (structure needs cleaning)

how can i solve. i dont have early back up so i dont want wipe everything. please help me

thank you
I fixed that issue (structure needs cleaning) by dirty-flashing the installed rom, in my case it was OOS.
After being fixed, I was able to backup.
 
  • Like
Reactions: kipue

ulxerker

Senior Member
Jul 6, 2015
4,212
1,107
Samsung Galaxy S23
build today v13
log :
do not need to distinguish between the future whether to use Enable legacy properties for old
zips ps twrp automatically determine Brush or as simple as before!
see :
http://www.shuajizu.cn/forum.php?mod=viewthread&tid=18235&extra=page=1&mobile=2
link :
https://androidfilehost.com/?fid=745849072291690085

Thanks, please keep us updated with new releases.

Thanks.. best recovery for op5 :)

I second that ... very fast, stable and with a cool black theme!
 

smint86

Senior Member
Jul 8, 2011
1,043
714
Dortmund
OnePlus One
OnePlus 7 Pro
build today v13
log :
do not need to distinguish between the future whether to use Enable legacy properties for old
zips ps twrp automatically determine Brush or as simple as before!
see :
http://www.shuajizu.cn/forum.php?mod=viewthread&tid=18235&extra=page=1&mobile=2
link :
https://androidfilehost.com/?fid=745849072291690085

Is there a specific reason why the used TWRP version is 3.1.1-0 while latest official TWRP for cheeseburger is 3.1.1-1 (as seen here)?

How do you get English to stick? I select English, hit OK, then when it finishes decrypting it automatically switches back to Chinese.

You have to flash the whole zip via recovery not just flash the img inside the zip via fastboot. Made the same mistake first.

/edit: Nevermind. Getting the same problem with the chinese language showing up, too.
 
Last edited:

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.