yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] Kutep0v:
https://xdaforums.com/showpost.php?p=77193992&postcount=2

Now used toybox with busybox. This should solve the problems with busybox-binded scripts. Toybox remains the main "environment", busybox adds the missing tools (like awk, unzip and etc). I think this is the right solution, just better than making you rewrite scripts.

[MENTION=7471495]LPW00[/MENTION] about magisk again.

Updated without problems with the latest (16.7) beta.
[ONE Android Development] LPW00:
With the 3.2.3 it did for me too, the 3.2.2 however didn't.
[ONE Android Development] xange:
anyone here using this recovery with LOS + Magisk + encryption? Just want to verify the problem i'm getting whether is it just me or otherwise. I have problem to boot into system after update through OTA (the official method to update LOS every monday), after done update in recovery, the phone will boot into LOS boot animation (short while) > decrypt > boot animation (about 2 minutes) > automatically reboot into TWRP with "RescueParty" line on the log.
[ONE Android Development] Kutep0v:
[MENTION=4832634]xange[/MENTION] I'll try to find out what the problem is. For the first time update went well. When I restored the backup and tried again, I got a "rescue party".
[ONE Android Development] Loriot:
I had the same problem. I restored my backup, load the build from LOS Downloadpage and flushed it manually.

That works
[ONE Android Development] LPW00:
Question: busybox 1_29_2 is 13 days old. (Okay, I do realize that's not a question)

U also may wanna take a look at this https://github.com/osm0sis/android-busybox-ndk, I don't know what this is but I have a feeling that it could be useful
[ONE Android Development] Kutep0v:
[MENTION=7471495]LPW00[/MENTION] LOL :laugh:

I was talking about the bionic version of busybox for Android. Of course, the usual busybox is updated. Repository that you gave can't be compiled with TWRP.

I can add the prebuilt busybox that will complement the toybox. BTW, I already did this in the previous version.
[ONE Android Development] LPW00:
Hm. Okay, thanks for answering.
[ONE Android Development] Kutep0v:
One more thing about this.

I've done my repository with the new busybox a few days ago, but I couldn't compile because of the outdated configs in the TWRP. Busybox doesn't contain selinux tools, so it must be used through the toolbox or the toybox. When compiling, TWRP tries to refer to the system/core/toolbox, but there are no necessary files, since some of the tools were moved to the toybox in the Oreo.

I don't want to rewrite toolbox/toybox configs in the TWRP, so I didn't find any good solution except adding prebuilt busybox that will complement the toybox.
[ONE Android Development] Kppqju77:
Hello everyone, [MENTION=4832634]xange[/MENTION] I have the same setup as you, without Magisk, and the same problem on OTA updates (mine seems stuck on LOS animation though...).

[MENTION=7296006]Kutep0v[/MENTION]: thanks for looking into it, if you want any logs or whatever just ask

[MENTION=7839632]Loriot[/MENTION]: does it mean that now you are able to perform OTA updates through LOS updater or just that you flash them manually?

EDIT: It boots on rescue party for me too.
[ONE Android Development] Kutep0v:
[MENTION=6180909]Kppqju77[/MENTION] Thank you, I don't need logs.

You can restore a backup and install zip manually to prevent 'rescue party'.

As far as I understand, the problem is related to encryption. When you install through the Lineage Updater, recovery skips decrypting (commit), so some scripts can't be executed correctly. For example, 99-magisk.sh refers to /data/adb/magisk/addon.d.sh which is simply not available without decrypting. Or if there is not enough space in the /tmp, 70-gapps.sh creates a folder in the /sdcard, which is also impossible without decrypting.

I need more time to figure out what the problem is. I think there is something else.
[ONE Android Development] Kppqju77:
[MENTION=7296006]Kutep0v[/MENTION] OK, thank you, I do have OpenGApps installed (the micro package) so you might be right...

I don't care about having to decrypt the partition for each update, anyway i'll let you time to investigate.
[ONE Android Development] Loriot:
LOS updater didn't. I flashed it manually.
[ONE Android Development] user334:
Hey [MENTION=7296006]Kutep0v[/MENTION]!

Maybe it's too early to ask this but will your recovery support Pie? I'm pretty sure someday it's gonna be ported to One :)
[ONE Android Development] Kutep0v:
https://xdaforums.com/showpost.php?p=77193992&postcount=2

I uploaded the third test version, now there are no problems when using the Lineage Updater.

Wow. Thanks! I feel so much calmer now. :laugh:

Должно, но что будет с шифрованием - понятия не имею, сейчас оно не работает и на пикселях.
[ONE Android Development] LPW00:
It does. There's no reason why it suddenly wouldn't work on P.
[ONE Android Development] Kppqju77:
Your 3rd test version worked beautifully with yesterday's update. Thanks.
[ONE Android Development] user334:
It's offtop here but

bacon never die!

OnePlus One, OnePlus 5, and OnePlus 5T get Android Pie ports

[ROM][9.0.0_r3] POSP v2.0 - BETA [OFFICIAL]
[ONE Android Development] ValiumKnight:
Hello! I used T3 on an encrypted phone to update from Tugapower 24 to 25 and got the Rescue Party loop.

Any suggestions for fixing this? I didn't think about making a backup :(
[ONE Android Development] ConnerJSP:
I am trying to solve some issues I am having.

Using the T3 TWRP, I flashed idprophecy's ROM, Open GApps, and Magisk. The bugs or issues seem to be google related: face unlock doesn't appear in smart lock, can't use voice match in assistant to unlock device, and google play music glitches sometimes when starting a song then reboots the phone.

What would be causing this, seems like the GApps package but should I re-flash with the stable TWRP?

Confirmed Google (not Open GApps) issue; last couple of pages discuss some of these problems: https://xdaforums.com/android/software/pa-gapps-continuation-t3098071/page567
[ONE Android Development] zaska_:
Nandroid backup encryption not working?

Hi all!

I've tried to use encryption option for nandroid backups but it seems like it isn't working. Android is not encrypted. I choose partitions first, rename the backup, type encryption password and run backup.

Should it ask password when restoring? Am I missing something? :confused: I prefer encrypting backups because I upload them to my cloud storage.

Thank you Kutep0v for your work!
[ONE Android Development] tofu:
On encrypted android Pie TWRP offers "pattern unlock" despite I'm using pin. Then you can click cancel--> advanced--> terminal and type "twrp decrypt yourpasswordhere" and it decrypts the phone successfully.
[ONE Android Development] bmark240:
[MENTION=7296006]Kutep0v[/MENTION] thanks for the continued builds to support Oreo & Pie. I cannot help but have a scare every time that I use a new or beta version of your TWRP builds. I know I have had a few teething problems with errors & failed backups in the past, but your builds are my goto even before official versions.

Looking forward to the 'soon to be released?' New version.
[ONE Android Development] xange:
I think he went on hiatus for quite some time. Try reach him using telegram, username is the same with his profile name here. Well, you can click on his profile to see when is his last login... The telegram thing was mentioned on his profile in 4pda.ru
[ONE Android Development] hyewiz:
Im on "Cyanogen OS 13.1.2-ZNH2KAS3PO-bacon" how can I flash this?

Please help
[ONE Android Development] LPW00:
There are like 5 thousand guides on how to root ur bacon already, I don't see how using a newer twrp would require a new tutorial. Sorry, but please use Google. http://bfy.tw/KUPs
[ONE Android Development] sachin karinki:
Add Toggle to Automatic reboot to system after the completion of restore
[ONE Android Development] Kutep0v:
Hello,

I apologize for my long absence. I'm still alive. Until November I was in some kind of depression, I was not interested in the development... and everything else at all. I'm fine now, just doing other equally interesting things. By the way, TWRP development also slowed down the pace, the last major change in the omnirom repository was in August, more than 100 days ago. I can compile new 3.2.3 with the "stable/K" tag, but I'm not think that it will be better than the current test version. Write under this post all the bugs that you found, I'll try to figure it out for the next version (3.2.4 or 3.3.0?).

Thanks for remembering me.
[ONE Android Development] :
There's nothing to apologize!

Welcome back!! And good to hear you're fine now. Take care of yourself!!
[ONE Android Development] Mr.Ak:
He is only developing and maintaining unofficial and modified Twrp builds. The feature you're asking for can only be done by Twrp itself, if they want or see the feature usefull.

---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------

+1!
[ONE Android Development] Gawd:
This ain't no Google+ bruhh
[ONE Android Development] Kutep0v:
Done.
[ONE Android Development] Gawd:
I guess you forgot to upload the latest build. Thanks for implementing the thing you hate.
[ONE Android Development] Kutep0v:
I'm testing. It will soon be uploaded.

Uploaded. I hope everything is fine.
[ONE Android Development] iRhyiku:
Subtle way of asking for an ETA haha
[ONE Android Development] GXGOW:
I noticed that there is another option available in the backup section. You have the choice between backing up System and System-image. Is there any difference between the two, apart from the 200 MB size difference?
[ONE Android Development] PlasmaPump:
It has been said already...

System is a "file by file copy" type of back-up -- files will restore in sequence to the same folders but maybe not be in same physical location in system partition.

System-image is a "snap-shot" type of back-up -- files will restore to the exact same physical location in system partition.
[ONE Android Development] GXGOW:
Oh, my bad. I must've missed that post. Thanks for the answer!
[ONE Android Development] natheux:
Wah thank you for this project !
[ONE Android Development] RazerSharp:
Wow! this is so fast, much better than official twrp recovery.
[ONE Android Development] Mandrake2010:
Hi, i want try this recovery , i have a backup with last tugapower twrp stabile, can i restore it with this recovery?

Can i use materialized theme on it?
[ONE Android Development] Kutep0v:
I have backup from old 3.0.0 version, restore works fine. So, I think it will work.

Wow. I've never tested themes, and I didn't know about their existence for 3.0.x TWRP.
[ONE Android Development] rshbhghelani:
Just dropped in to say Thanks A TON. This recovery is blazing fast.

Why did we not have this before :eek: We were missing out on A LOT.

Loved this work. Thank you very much.
[ONE Android Development] PlasmaPump:
Yes, the ones for 3.0.3 work. However you will first need to edit the ui.xml file inside the theme zip.

Find the line:

<themeversion>1</themeversion>

change it to:

<themeversion>2</themeversion>

Enjoy ;)
[ONE Android Development] shuini:
Thank you ,Can keep multiple language support?
[ONE Android Development] Mr.Ak:
Can custom themes for TWRP be used with this recovery? [MENTION=7296006]Kutep0v[/MENTION]

Edit: check below quote for a working procedure to theme TWRP.

---------- Post added at 06:43 AM ---------- Previous post was at 06:41 AM ----------

Why do we need to make these changes? Do we also have to make changes like these for official TWRP.

P.s. I'm trying to use the theme for first time on TWRP. :P

Edit: thanks man! It worked!
[ONE Android Development] Kutep0v:
Hmm... Currently supports 17 languages. If necessary, I can include extra languages ​​as Chinese (both) and Japanese in the next version.
[ONE Android Development] fmc000:
Any news about /data decryption?
[ONE Android Development] PlasmaPump:
TWRP source has changed on Jan. 18 that requires <themeversion> 2 to be accepted.

No official TWRP released since 3.0.2 so no themes updated to <themeversion> 2.

This TWRP, which is awesome BTW [MENTION=7296006]Kutep0v[/MENTION], is built on current source so it needs it.

The change does not mess anything up and themes should still work.
[ONE Android Development] Tomoms:
Hello!

First of all, thank you for your work :)

The current 3.2.3-T3 release is great, the only "bug" I've noticed is that the recovery takes quite a lot of time to load, i.e. the TWRP splashscreen is shown for several seconds, while on my other phone, an old Sony Xperia SP, the loading phase is way shorter (the splashscreen is only shown for a few instants). I'll grab some recovery logs in the next days and send them to you, if you think they could be useful. I'm using f2fs for /data and /cache, if this matters.
[ONE Android Development] Kutep0v:
It matters. When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage.
[ONE Android Development] user334:
Do you recommend to use ext4 or f2fs? I see some polarised opinions about that.

Btw glad to see you again :)
[ONE Android Development] Timmmmaaahh!:
In my experience and according to [MENTION=3292224]franciscofranco[/MENTION] (esteemed kernel developer) in [url="www.xda-developers.com/interview-francisco-franco-kernel-1/amp/" ]this article[/url] (well, more like a Google engineer than Franco) ext4 has way more advantages over f2fs. I'd have to dig deeper to find out if that still is the case in modern phones but for Bacon ext4 is your best option, especially if you're flashing Oreo and above.
[ONE Android Development] Tomoms:
But... I'm using f2fs on my other phone as well! Could the reason be that the kernel sources you use to build your TWRP have got a very old version of f2fs, which handles those operations slowly?
[ONE Android Development] Kutep0v:
EXT4, at least for bacon. I agree with [MENTION=4841620]Timmmmaaahh[/MENTION]

Speed may also depend on the occupied space. Previously checked when using f2fs.

Maybe. Built with stock LineageOS kernel without any changes.
[ONE Android Development] portfolio:
I personally stay with EXT4, it is much more uncomplicated when flashing forward and backwards such as one likes to try and flash different roms once in a while... and I believe from all my experience, any speed advantage a F2FS might have, in daily usage of our OPO it can be neglected
[ONE Android Development] bmark240:
I also agree with f2fs being terrible on the OnePlus One. The hardware isn't as compatible with the file system as say OnePlus 3 and above. Samsung has optimized its devices well using its bespoke file system (but not its Touchwiz UI)....
[ONE Android Development] Diniodoc:
Does anybody know if there is a TWRP version with working decryption for Andriod Pie ?
[ONE Android Development] 1plus:
I second that.

[MENTION=7296006]Kutep0v[/MENTION]

I'm afraid the situation is same all over again. Like with Oreo, the encryption was changed again in Pie. Currently I have a custom LOS16 and T3 build does not decrypt \data....
[ONE Android Development] Kutep0v:
[MENTION=6258120]1plus[/MENTION] send me the link to your LOS 16 in PM. I'll try to figure out on the weekend.
[ONE Android Development] Peter.Zwegat:
Same goes with Arrow OS - newest version :(
[ONE Android Development] Mustkeg:
In recent LineageOS change https://review.lineageos.org/c/LineageOS/lineage_wiki/+/241437/15/_data/devices/bacon.yml a custom TWRP for bacon is mentioned.

In https://review.lineageos.org/c/LineageOS/lineage_wiki/+/241171 it is stated that "[t]his TWRP can decrypt Pie encrypted data partitions".

So maybe it works for you?

And it seems that LOS 16 is becoming more real every day! :victory:
[ONE Android Development] 1plus:
10x for that obscure link! I'm not even sure who is the developer for that twrp build.

I have just tried this build and it has SUCCESSFULLY decrypted /data in recovery!

upd: the developer's name seems to be TheMuppets.

the direct link to AHD for this twrp is as follows:

https://androidfilehost.com/?fid=1395089523397886136
[ONE Android Development] Peter.Zwegat:
Obscure, yes, but works for me too!
[ONE Android Development] :
Great to hear!

Does this recovery is successful too in decrypting /data Oreo ROM or do we have to change recovery accordingly which Rom (Oreo/Pie) we are using?
[ONE Android Development] spyderchat:
I am having trouble flashing 3.2.1 (from oreo 8.1), I get stuck on the 1+ logo. Can anyone provide a fix?
[ONE Android Development] JoeF2:
TheMuppets are basically the core LineageOS developers. The Github account TheMuppets has the proprietary binaries for devices that are supported by LineageOS.

But unfortunately, this version doesn't work with adb. It says "unauthorized." It should be possible to change the properties file to allow adb in the ramdisk in the image, but so far I couldn't get that to work.

Edit: adb now works for me, based on this https://stackoverflow.com/questions/42765900/adb-devices-says-unauthorized-in-twrp, changing the properties

ro.secure=0
ro.adb.secure=0
ro.debuggable=1
[ONE Android Development] monosoul:
I wasn't able to format any partition using this recovery, it just freezes. Anyone else having the same problem?
[ONE Android Development] Kutep0v:
And again I apologize for my absence. It has already become a kind of tradition. :mad:

I'll try to release at this weekend, if decryption works fine. I have a test build, but now I can’t force myself to backup internal storage and encrypt under LineageOS 16. I need some more time to test.
[ONE Android Development] blinoff82:
Bro, You have made a great contribution to the development of OnePlus. Even now, having OnePlus6, I continue to use your work on OnePlus One. Thank you very much for your work!:good:
[ONE Android Development] Kppqju77:
Thanks a lot for all your efforts!

Just tested the Pie decryption and it works perfectly.

For the one who are trying to test this with "only" fastboot boot TWRP.img the decryption doesn't work, for some reason you have to flash the recovery for the decryption to work.
[ONE Android Development] Beep-Bop:
Wiping as F2FS makes the data partition show as 8GB in Android Storage rather than 54GB something. Official works just fine
[ONE Android Development] :
Has anyone tried an encrypted f2fs /data and /cache with the new TWRP? I'll be editing my post with my results asap
[ONE Android Development] Kppqju77:
Are you talking about the 3.3.0? Is Pie decryption supported in this one?
[ONE Android Development] hellelectrik:
The latest version of recovery 3.2.3-K1 from Kutep0v does not correctly translate the DATA partition into F2FS, the markup changes and the device becomes a 16GB version, does everyone have it?)
[ONE Android Development] LPW00:
Awesome! I thought u dropped the project.
[ONE Android Development] Kutep0v:
[MENTION=7471495]LPW00[/MENTION] I had some free time this week. In the previous version there were several serious bugs, I couldn't leave the project in this state.
[ONE Android Development] user334:
HI!

I see .img now hosts on GitHub instead of your site. May I post a direct link to it on 4pda or should I as always give a link just to this thread?

Anyway, HUGE thanks for so long support! :)
[ONE Android Development] Kutep0v:
Sure
[ONE Android Development] Nicolauser:
Hi, thanks for your great work here!

I've installed latest twrp version and it work perfectly for me.

Just wanna if it is so for everyone or someone is experiencing issues and so on.

Bye
[ONE Android Development] Bittornado:
Awesome work, thank you!

Huge improvement in my short experience with your TWRP release compared to the official biild. No iasues whatsoever and thw Recovery works and behaves exactly as advertised. Great work :)

I have always used your TWRP versions and tbh I've had next to no issues at all whatsoever during all tbis time.

I do understand your shifting interest towards other projects.

Although I wish I could keep benefiting from your great contribution even in the future, but I also would like to offer my deepest apprecition for all your work until now, and good luck in the future...but please come back please for some major improvements in the future if poasible.

??
[ONE Android Development] :
Been running f2fs on argon kernel v14 that includes all the recent f2fs backports, and the wait time has been significantly reduced. No corruption errors so far and I can say it's 100% stable and usable on full disk encryption with /data and /cache formatted as f2fs. Thank you so much for doing this in your recovery. It has made my usecase possible, I can use my phone storage much more efficiently as a cache for videos and pictures now. I still use my OnePlus One with the stock battery as my daily driver with an unlimited data plan. I've even gone so far as to use this phone as my primary internet source. I spoof my PC to look like my phone traffic, route it through OpenVPN on a pfsense VM and achieve port forwarding, and all the bandwidth of a regular landline connection. I get a solid 60ping in bf4.

TLDR; Coming from a OnePlus One user living in a converted van running off of solar energy, and you've kept my primary internet source and phone for everything alive all this time with your recovery. It is very much appreciated. This phone is standing the test of time. ⌛
[ONE Android Development] coderex96:
Really thanks for this work, I keeping alive my friend's OnePlus One with this :)
[ONE Android Development] david72262:
Is the lastest update compatible with the last official cm for bacon CyanogenMod 13.1.2 ?
[ONE Android Development] ze7zez:
Why are you afraid to check it yourself?

You flash, restart and you know it.
[ONE Android Development] :
Post withdrawn by author
[ONE Android Development] ze7zez:
TWRP and Android 10

I recommend this message from [MENTION=912474]Dees_Troy[/MENTION] to everyone who is enthusiastic about Android 10 for OPO:

TWRP and Android 10 :cool:
[ONE Android Development] hanseatic2:
Or you just:

fastboot boot whateverthefilenameis.img

without touching anything
[ONE Android Development] M4Master96:
[MENTION=7296006]Kutep0v[/MENTION] are you planning to release your version of twrp-3.4.0-0-bacon ?

Been using your 3.3.1-K1 so if the development has not stopped, waiting for your next build :)
[ONE Android Development] kryshnakishore:
off Topic but expecting little help:

due to changes i made in build prop, device is not booting into OS, it shows the screen of Bootloader unlocked.... Device is rooted & i have custom recovery installed. unlucky part is my volume buttons are not working. is there a way to get into recovery mode?? at this stage adb is showing No device found.
[ONE Android Development] Mr.Ak:
Yes! They are working, thanks!

And thumbs up to [MENTION=7296006]Kutep0v[/MENTION] for making such fast recovery! :)
[ONE Android Development] jhedfors:
Just. Wow. So fast! On my OnePlus One, backed up 6.58GB in less than five, and restored and rebooted to lockscreen in 5 1/2 minutes!

Thanks a ton! :)

I think you may have typo'd the Release Date (year).
[ONE Android Development] Kutep0v:
Guys, thanks for the support. It's really important to me. :)
[ONE Android Development] imloy:
does it support F2FS ?

Previously TWRP 3.0.3.2 Tugapower gave problems for F2FS support...thats why using 2.8.6.0
[ONE Android Development] Kutep0v:
Sure. Also, I haven't seen any TWRP with F2FS problems.
[ONE Android Development] Gawd:
Formatting to F2FS is generally preferable when done with TWRP 2.8.6.0

At least some devs say so, I'm not sure.

You can have a look at this ROM (Page 39-41), it didn't work on F2FS until formatted using 2.8.6.0. Seemed quite weird to me, but maybe you can enlighten us.
[ONE Android Development] Kutep0v:
It's really weird. Now I checked f2fs formatting, everything went well. Partitions everywhere defined as f2fs. In dmesg /data and /cache mounted as f2fs.

I don't know what the problem is. Maybe they got a broken TWRP 3.0.2-0. Who else can confirm or deny this?
[ONE Android Development] yijinsa:
So should I backup system IMG or just system will be fine ?