yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] C4SCA:
system will be fine
[ONE Android Development] Kutep0v:
Works now. I need time for testing.

Tested with PIN and Pattern (3x3). Works fine.

P.S. 3.0.3-K3 uploaded. Waiting for feedback about decryption.
[ONE Android Development] shuini:
Thanks for your multi-language support
[ONE Android Development] fmc000:
Thanks. Will try in the next few days and report back.
[ONE Android Development] ShouriX:
I have not tested out your TWRP. Both the official TWRP and tugapower TWRP, however, have problems formatting to F2FS.

They would format just fine in the recovery, but when I flashed and booted the ROM (Nitrogen OS), the partitions would be formatted back to EXT4.
[ONE Android Development] deadlyindian:
Its a problem with the ROM itself not recovery, ask the NOS maintainer to fix the issue.
[ONE Android Development] GXGOW:
That's because the ROM you're using does not support f2fs. You could ask in the ROM thread if the maintainer could implement it.
[ONE Android Development] ShouriX:
It works fine with official TWRP 2.8.6.0

It does actually. using TWRP 2.8.6.0
[ONE Android Development] Gawd:
Any plans of upgrading to 3.1.0-0?
[ONE Android Development] blinoff82:
I think this is bad idea - ask such questions. This is the same as asking about ETA ;)
[ONE Android Development] Kutep0v:
Already :)
[ONE Android Development] Gawd:
Aren't you the best :D
[ONE Android Development] Mr.Ak:
I think he was just trying to say/hint the OP that 3.1.0 is officially released for bacon.
[ONE Android Development] counterfeit187:
No it isn't. it's asking if he will support the next version of twrp or only maintain 3.0.3. No part of it was about time or date. It's a simple yes/no question.
[ONE Android Development] Setting.Out:
Let's not clog the thread, let the dev update as they choose. No more, no less..
[ONE Android Development] fidanzata:
Beast twrp, thanks dev!
[ONE Android Development] david72262:
Did you finally update from 2.8.6.0? Me not yet but thinking about it finally.
[ONE Android Development] Setting.Out:
I was thinking about it.. Like the looks of this one, but I'm still stuck in the past.. :)
[ONE Android Development] david72262:
Me too this one does look promising.
[ONE Android Development] jangralsaab:
I have tuga power twrp now ,,,now I want to flash twrp K1 so can u tell me what is the process to install this twrp
[ONE Android Development] aqilsoomro:
Through twrp select install then select install image rather than zip and select partition recovery, then swipe to install afterwards reboot into recovery. That simple.
[ONE Android Development] jangralsaab:
Ya I already tried that but after successful install it will stuck in opo logo and after that nothing happened
[ONE Android Development] aqilsoomro:
Try fastboot method
[ONE Android Development] jangralsaab:
U mean by cmd
[ONE Android Development] aqilsoomro:
Yes
[ONE Android Development] jangralsaab:
U mean by CMD
[ONE Android Development] xlollomanx:
You can use Flashify also, downloadable from play store.

Sent from my Oneplus One
[ONE Android Development] jangralsaab:
I tried many times with flashify but not successful
[ONE Android Development] xlollomanx:
Strange on my device it works perfectly. I'm on RR 6.0.1

Sent from my Oneplus One
[ONE Android Development] jangralsaab:
I'm on oxygen 3.1.4
[ONE Android Development] Kutep0v:
As far as I know, you need patched TWRP. It's associated with firmware used in your ROM. At least that's how it was before.
[ONE Android Development] jangralsaab:
So what is the process to flash and where to download patched twrp
[ONE Android Development] Kutep0v:
Obviously not here. Most likely, patched/ported TWRP in archive with your ROM. You need to ask about this in OxygenOS 3.1.4 thread.
[ONE Android Development] jangralsaab:
OK thank u I will try at there
[ONE Android Development] storm119:
[MENTION=7296006]Kutep0v[/MENTION]

Hi...i try to unpack and repack to change the splash screen using AIK but getting error while flashing back the image...(see ss attached). But it doesn't happen with official TWRP image...any idea what could be happen...?.

TIA
[ONE Android Development] Kutep0v:
After switching to LineageOS 14.1 source, recovery image size increased by 1 MB (15.4 MB total). I think, after repack the size of image has become more than a partition. Partition size is 16777216 (16 MB).
[ONE Android Development] engsaad:
twrp-3.1.0-0-bacon.img

Is available officially

Link:

https://dl.twrp.me/bacon/
[ONE Android Development] Kutep0v:
We know. He is still almost 3x slower than mine.
[ONE Android Development] engsaad:
You know,

I didn't say that you don't

I just want to share information and not to compare your version with the official one...
[ONE Android Development] GXGOW:
Damn. Kudos for getting such a increase in speed.
[ONE Android Development] storm119:
Yes that make sense...your TWRP version seems larger compare to official one but the good news is after compressing the png image and delete some which not need it anymore since i'm using the custom splash image finally i can cut down the image size and flashed with no error anymore. They look pretty awesome with my twrp theme... :victory:

Thank you
[ONE Android Development] aqilsoomro:
Please share your theme and how to apply.....
[ONE Android Development] storm119:
Click my sig...its will bring you to the twrp materialised theme thread...you can find the download links there (make sure to download the correct one since i made for TWRP ver. 2.8.7.X to 3.1.0.X). The correct theme version for TWRP 3.1.0-K1 is 310X_V1...

Ps- To apply the theme for the first time just flash on recovery and its detect automatically and apply the theme...the theme doesn't include the splash screen tho and for the splash screen you need to unpack/repack the TWRP image...
[ONE Android Development] aqilsoomro:
I downloaded theme but I like your splash very much but may mess up things while unpacking and repacking, if it is not asking too much would you please share the modified version?
[ONE Android Development] storm119:
Sure...if op [MENTION=7296006]Kutep0v[/MENTION] dont mind i will upload the TWRP 3.1.0-K1 image with custom splash screen to my AFH...and share the link here :D
[ONE Android Development] joemilan:
For change splash need only unpack with aik, replace splash png and repack again?
[ONE Android Development] Kutep0v:
Of course. I have nothing against modifications. ;)
[ONE Android Development] storm119:
Haha...thank you mate. I only changed the png image and edit the xml file and NOT by any chance to alter the codes and preserve the original image... :D

[MENTION=7281085]aqilsoomro[/MENTION] here the link TWRP with custom splash ...choose the twrp-3.1.0-K1-bacon-teal (for the power of Kutep0v version) and the other one is official twrp :good:

Edit: Important

1- Please re-download the twrp image....im uploading the new image which fixed the error "font/splash failed to load"...and also adding new custom deep orange splash screen.

2- The error that folks getting is my mistake but i hope i'd fixed it...sorry guys :o

3- Theme also updated to V2
[ONE Android Development] :
[MENTION=7296006]Kutep0v[/MENTION], been on your recovery since k-1 and I have to say, I trust you and your project more than anything here.

As a human to human, I really like you.
[ONE Android Development] maikvitesse:
This really is the most optimized version of TWRP.

Now i stand for a choice.. i want to keep using this recovery, but i also want to use multirom.

difficult..... :eek:
[ONE Android Development] :
Should I be worried?
[ONE Android Development] GXGOW:
Reboot back into the system, then reboot back to recovery. It should be gone then. This happens sometimes, nothing to worry about.
[ONE Android Development] Meikk99:
Hey there this is an awesome recovery, when I use it with efidroid however I run into a bit of a problem when I try to boot to recovery on the latest 3.1.0-k1 it gives me the following error:

Can't allocate kernel boot memory at 8000 size 6212096.

The 3.0.3-k3 version works fine as does the official twrp 3.1.0 however the 3.1.0-2 from tugapower gives a similar error. Does anyone know what causes this? I realise this may not be a problem with the recovery however I thought this would be the best place to ask.
[ONE Android Development] Kutep0v:
Something strange. I think this is somehow connected with the latest changes in ROM. Your "solution" only confirms it.

There are only there possible causes.

First - switching to LineageOS 14.1 source, and therefore the kernel uses another.

Second - EFI bug.

Third - last commits in TWRP.

We'll go through the options below.

Let's think.

1) 3.0.3-K3 compiled with LineageOS 13.0 source, and 3.1.0-K1 with LineageOS 14.1.

3.0.3-K3 uses my cm-13.0 kernel with all CVE fixes, doesn't lag behind cm-14.1. (except 9 commits below)

In cm-14.1 kernel was added 9 commits. Also, other changes besides the kernel are not excluded.

Switching to LineageOS 14.1 source broke EFI?

2) Just a bug in the EFI, which will some day be fixed.

3) In the gap between 3.0.3-K3 and 3.1.0-K1, 3 commits for TWRP were added.

Nothing important, but let's not forget.

Which option do you like more? Now I don't know the solution.

If this is the first option, then we must revert commits, which is stupid, or write a feedback to EFI devs.
[ONE Android Development] Gawd:
I have faith in you and your recovery, [MENTION=7296006]Kutep0v[/MENTION]
[ONE Android Development] Meikk99:
I don't know a whole lot about this but the first option sounds the most plausible, I suppose I will ask about this in the efidroid thread as well, thanks.
[ONE Android Development] GXGOW:
I guess it has to be a widespread issue on Lineage or TWRP, since I've seen it happen on my G Pad 8.3 too, ever since the release of CM14. It's not that big of an issue, unless you're trying to backup your current ROM. Then you're going to encounter that error again and the backup process will be aborted. But yeah, that 'solution' always works.
[ONE Android Development] Kutep0v:
I reworked the AROMA hack. At the moment, more AROMA archives are supported (including based on 3.00b1). So, rebooting with the second flash still is not fixed.

Need testers. Who wish - AFH. Thanks.

CAUTION: not recommended for inexperienced users.

Testing is over, but the link will be live until the stable version is released. Have fun.
[ONE Android Development] aqilsoomro:
Welcome back mate Good to see you back in action.
[ONE Android Development] tamboli007:
Thanks for this amazing recovery. It works with Android N encryption . Easily decrypted while none other recovery worked .:svetius:
[ONE Android Development] deepu458:
Hi Dev,

Definitely a gr8 piece of work. This version is so fast when compared to any other versions. The only thing i noticed was when i enable compression for backup the speed is slow and almost same as any other.

If i just disable tht option and take a backup its very fast.

So kindly try to see if u can make compression backup any faster
[ONE Android Development] Kutep0v:
I think this is impossible, speed of compression depends on CPU performance.
[ONE Android Development] deepu458:
I totally understand buddy, thx for replying.
[ONE Android Development] simow:
do i download K2 beta or wait for u to release a stable version of it?
[ONE Android Development] jhedfors:
3.1.0-K1 is very stable from my experience.
[ONE Android Development] Kutep0v:
K2-aroma (beta) was compiled only for testing of the reworked AROMA hack and is not a stable release. If you really need support for new AROMA archives based on 3.00b1, then use the "unstable" K2-aroma version. If not, then stay on the K1.

K2 will not be released in the near future, since there was no change in repository since the release of the previous version.
[ONE Android Development] bdwilk:
K1 is a beast !! Respect.
[ONE Android Development] Gawd:
Would like to try it. I bet it'd be flawless just like your recovery.

Can you open a thread here on XDA or link me to that thread in the forum, in which you posted it?

Many thanks, your work is greatly appreciated!
[ONE Android Development] digitalpig82:
Just curious, did you ever compare your version to the official TWRP 2.8.6.0? This is the version which is still being used by some of us (including me), just because it is much faster than the (official) TWRP 3.x releases.

Just wondering whether your 3.1.0-K1 brings back the speed of the good ol' 2.8.6.0... :cowboy:
[ONE Android Development] bdwilk:
One way to find out. Personally 4+gb backup 160 sec. Same for restore.
[ONE Android Development] Kutep0v:
Thank you for attention, but I think this is no more flawless than other. I threw only really important changes, no useless optimizations, just support device tree and kernel in "up-to-date" state, because the "official" cm-13.0 branch haven't been updated since the release of 14.1.

I was not going to distribute it here, since there is already one unofficial LineageOS 13. Besides, this doesn't make sense, Marshmallow is starting to become obsolete.

Speed ​​is approximately equal. All within the margin of error.
[ONE Android Development] pk5720:
That's a real blazing fast..

Thank you for this..Amazing stuff!!
[ONE Android Development] Stephen:
Moderator Information,

Thread has been cleaned at OP's request. This is a development thread, please keep posts on topic about this recovery only. Talking about other recoveries is disrespectful to the dev.
[ONE Android Development] Kutep0v:
Guys, I'm not against a small deviation from the topic, but the discussion of the compilation process of TWRP, and especially for another device, shouldn't be here, for this there is a special thread. Thanks for understanding and support.
[ONE Android Development] Timmmmaaahh!:
Did a speed comparison with 'another' unofficial TWRP, K1 wins by respectively 2MB/s and 1MB/s. Maybe not all that spectacular but nicely done anyway! What I find more interesting is that it added two things in the backup: fsg & fsc. What are those and why doesn't the other one handle it? Selected for backup: Data, System, Boot & EFS.

Sizzled with Bacon
[ONE Android Development] Kutep0v:
The focus was on increasing the speed of restore, not backup.

On many devices, these partitions are associated with EFS... but not on our device, they are empty. :eek: (maybe it's only on my device?)

In K2-aroma (beta), instead of these two added oppodycnvbk. After several tests, I found a connection with EFS.
[ONE Android Development] siddheshvartak:
Recovery was working fine till date...

Now I am getting this error while backing up :

* MD5 Created. I:Partition Backup time: 1 Invalid encryption mode file /data/unencrypted/mode Backing up System... Invalid encryption mode file /data/unencrypted/mode Error opening: '/system/addon.d' (Not a directory) I:Error in Generate_TarList! Error creating backup. I:InfoManager saving '/data/media/0/TWRP/BACKUPS/479ae3bf/2017-04-23--23-22-57_bacon-userdebug_7.1.2_N2G47E_3bfa54adef_rel/system.info' createTarFork() process ended with ERROR: 255 Backup Failed. Cleaning Backup Folder.
[ONE Android Development] Kutep0v:
Something strange. Try to use System Image backup, not usual System. If works fine, then something wrong with system partition. Try to dirty reflash ROM. If it did not help, then make a clean install with all wipes.

Sometimes I saw on other devices when addon.d directory turned into a file, but I have no idea why this could happen. And maybe this is not our case...
[ONE Android Development] siddheshvartak:
Backup completed with system image (system unchecked).

Thanks.

But What could be the problem??
[ONE Android Development] Kutep0v:
I really do not know what happend with your ROM. Possible solutions I wrote above.

Something wrong with system partition. I think, wipe and reinstall should fix it. BTW, System Image backup more accurate than "usual" file method with tar.
[ONE Android Development] Timmmmaaahh!:
Just had some backup issue for /system + /data. It took forever to get from 15 to 16% (not sure how long, was doing something else). Then I kept an eye on it and waited for about 12 minutes, it was still sitting at 16%. Log: http://cloud.tapatalk.com/s/5910d290536ad/recovery.log

Sizzled with Bacon ?
[ONE Android Development] mustang_ssc:
Is your device encrypted, or do you enabled some encryption stuff from the recovery? It seems that the backup process gets stuck after trying to do something related to encryption to a directory of /data, or at least until you manually finish the backup process (yep, 12 minutes :) )
[ONE Android Development] Hunting_Party10:
Did your screen turn off while taking backup and when you checked the progress ,it was stuck ?
[ONE Android Development] Timmmmaaahh!:
No encryption of any kind, I never use that. I took two screenshots, the first when I noticed it getting stuck at 16%, the second just before I canceled manually.

No, my screen is always set to always on in recovery. I want to be able to see what's going on at all times. It did not freeze, it just didn't manage to get any further. I eventually tapped cancel.

I thought it was the theme, honestly, but then I flashed another kernel and backup ran flawlessly.

Sizzled with Bacon ?
[ONE Android Development] gegabit:
Great recovery! Perfect work and fast speed.

Thanks!
[ONE Android Development] Kutep0v:
TWRP 3.1.1-K1

Improved AROMA support. Almost all AROMA archives should be supported.

Improved EFS backup. Don't restore EFS from other TWRP versions!

TWRP version 3.1.1

Fix reboot when no OS is present

Update TWRP to AOSP 7.1.2

Adopted Storage: backup keys but do not wipe them

ADB Backup: fix adb restore issues

P.S. Temporarily I can't verify the decryption, write to me in case of problems.
[ONE Android Development] blinoff82:
Glad to see that you continue supporting of unofficial TWRP bro! :good:
[ONE Android Development] blend800:
I hate this error E3003: Can't install this package (Fri May 12 22:24:14 IST 2017) over newer build (Sun May 14 12:54:24 MSK 2017) by update my Rom. wipe system, cache and dalvik before.

With TWRP 3.0.1-K1 works.

Sorry for my english
[ONE Android Development] Kutep0v:
Recovery newer than your ROM. You can install ROM builded after May 14 or without a strange check as below in updater-script.

(!less_than_int(1493029336, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Mon Apr 24 03:22:16 PDT 2017) over newer build (" + getprop("ro.build.date") + ").");

This useless check appeared in March on many 7.1 ROMs. Should prevent users from "downgrading" builds, but instead of checking the build date of the ROM, updater-script checks the build date of the recovery. It works on the ROMs that comes with the recovery, but not in our case. As a result, "downgrading" is still possible, and installation of the ROM, if the recovery is newer than it, is impossible.

Edit: Fixed. This will prevent similar problems in the future.
[ONE Android Development] blend800:
Ahh okay :good::highfive:
[ONE Android Development] tofu:
Decryption works on the latest version. Thanks!

(rom: encrypted slim7)
[ONE Android Development] Setting.Out:
I'm having odd double flashing, on screen it looks normal, but not in the log. Here's a log for you..
[ONE Android Development] Kutep0v:
I confirm, but this is not double flashing, just duplicating ui_prints in the log. This bug exists in all 3.1.1, at least for our device. Nothing serious, there can't be any problems.
[ONE Android Development] deepu458:
Hi Buddy, so this fix is in place for the current existing 3.1.1-K1 build already? or it will be present in the future build?
[ONE Android Development] Kutep0v:
Hi. Problem was on the side of the archives, not the recovery, hence fix was merged into the LineageOS/android_build repository. I wrote about it in detail above. I think many developers of ROMs based on 7.1 have already pulled this change into their repositories, which means that all new archives will be without this check. This change will affect recovery only indirectly. If anything, this problem has affected everyone, and not only specifically my recovery.
[ONE Android Development] tofu:
Just wanted to say thanks for this amazing recovery. Devs like you make it possible to use our phones much much longer than manufactures wish for. There's absolute nothing wrong with Oneplus One - regardless how many new shiny devices pop up.
[ONE Android Development] ConnerJSP:
What would be the incentive to use a custom recovery? I am currently using the official TWRP 3.1.1-0 and have no issues with it. You boast faster restore times and EFS backup, however I am in no need of those features. Often it seems that custom software brings bugs because something is not done right. Example is of danieldmm's recovery which has had major reported issues whereas your's has not had as many. Although I trust the work you've done and would try your recovery, I just don't see why I would. Would you recommend just using the official one if I have no need for any advanced features, or are things like this and custom ROMs worth the "optimizations" they have?
[ONE Android Development] Mr.Ak:
I asked the same ques,see the first page and you'll get your answer.This recovery is way better than official one and you can see the difference in the changelogs.Worth flashing!
[ONE Android Development] storm119:
[MENTION=7296006]Kutep0v[/MENTION]

Hey buddy...

1- I applied you commit bacon: support flashing with new tz on my rom working tree and flash the Hydrogen firmware (which you attached there) but its took an ages (roughly about 20-30 mins if not mistaken) to complete the wiping DDR process before it succeed flash the image radio. Do you aware of this...or any chance to improve the wiping DDR time ?

2- I dunno what it does...LoL im a noob on recovery stuff (except the themes) but are you plans to merge this commit twrpDigest refactor ?

TIA
[ONE Android Development] Kutep0v:
It's pretty simple. If you don't need all this, and the official version suits you, then why go?

I don't know how to fix it. This problem has been going on for about a year. Nobody tried to fix it, maybe it's impossible? :eek:

You can use archives without this wipe, but "Changes in rpm or sbl can have signifigant affects on the memory timings, leading to instability and crashing. Whenever we update either of these partitions, erase the DDR partition which holds the calibration data, triggering a recalibration on next boot." (source)

Yes. I'm going to update the recovery in the near future. Issue #169 that appeared after this change is now fixed.
[ONE Android Development] storm119:
Noted....and since we are seldom to wiping this partition i guess we have to deal with it....no biggy ;)

ahhh...looking forward for the next update...thanks a million :good:

Ps. Issue #169 fixed with this commits backup: fix return handling when no digest is being created
[ONE Android Development] Kutep0v:
TWRP 3.1.1-K2

backup: fix return handling when no digest is being created

libtar: Fix restore of e4crypt policies

Complete support for project pathmap

Fix incorrect 'unlink' return value check

twrpDigest refactor

Fix minui issues for some build trees

ors: Update doc

Improve decrypted partition logging

adbbackup: write smaller reads less than 512 bytes

Fix various memory errors

cryptfs: Remove dm-crypt device on failed table load

etc: remove "." from LD_LIBRARY_PATH

mtdutils: Fix mounting partitions by-name

gui: fix line wrapping in terminal, issue #876

P.S. As always, I can't verify the decryption. Write to me in case of problems. :confused:
[ONE Android Development] storm119:
Just a heads up....if anyone here using Materialised Theme by [MENTION=2719389]z31s1g[/MENTION] or my themes Materialised Black Play Blueish with the latest [MENTION=7296006]Kutep0v[/MENTION] TWRP 3.1.1-K2....you need to use the 311X_V2 TEST since its require "themeversion 3"... ;)
[ONE Android Development] simow:
i tried encrypting the phone and the decryption failed wich forced me to wipe the internal storage , this new version has this problem too or its never been fixed?