yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] asapmoola310:
Here is the correct way!

package_extract_file("NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/apnhlos");

package_extract_file("modem.bin", "/dev/block/platform/msm_sdcc.1/by-name/mdm"); :good:
[ONE Android Development] dlhxr:
I don't think so…since there's no apnhlos or mdm partition for oneplus one…don't know where you find such code
[ONE Android Development] MoistPicklez:
Any stable versions round' here? Been reading a few pages,

and wondering if the EFS backup option is worth the headache.
[ONE Android Development] renaltosonylevi:
I would go beyond that and say it is mandatory. It has saved my bacon a couple of times.:)

Edit. I use 2.8.6.0.6 and had no issues.:thumbup:
[ONE Android Development] AcmE85:
Yes, if you are using the ext4 filesystem,

2.8.6.0.6 is the best version in my opinion.
[ONE Android Development] MoistPicklez:
Cool thanks guys. I read a bit about F2FS and EXT4, but can't really grasp their differences in daily usage / speed. From what I have read EXT4 seems to be the way to go.
[ONE Android Development] AcmE85:
I'm on F2FS right now but will switch back to ext4 next time I do a clean flash.

Do not really see or feel a difference, also I don't care about benchmark scores.
[ONE Android Development] MoistPicklez:
So when you make the switch to F2FS, TWRP wipes all your data correct? Does it also wipe internal storage?
[ONE Android Development] gyakusetsu1215:
Yes
[ONE Android Development] MoistPicklez:
Well I am using 2.8.6.0.6 materialized now on F2FS (I assume.) and made a backup, flashed H²OS, then restored my backup. All is working so far! Thanks very much guys! This TWRP looks amazing!
[ONE Android Development] ketut.kumajaya:
I just found why my build of TWRP 2.8.7.0 fail to flash modem partition and restore firmware backup. Updated version ready for download http://goo.gl/rqjprv as img file, you can flash it using existing TWRP. Device, kernel, and upstream TWRP changes included, no update from my side except above derp :(
[ONE Android Development] MoistPicklez:
Edit: Failed to restore on 2.8.7.0.4.img [MENTION=4021423]ketut.kumajaya[/MENTION]
[ONE Android Development] fmc000:
So, just to be clear, this latest version is as safe as your 2.8.6.0.6 wrt backups and restores? In other words, why an absolutely satisfied user of 2.8.6.0.6 should update his or hers recovery to 2.8.7.0.4 ?
[ONE Android Development] renaltosonylevi:
Was the back you are trying to restore created using 2.8.7.0.4? Through experience I have found that it is not a great idea to restore backups with a different twrp version. In fact that has been the cause of most of my near disasters.
[ONE Android Development] MoistPicklez:
Yes it was a 2.8.6.0.6 backup, so perhaps that 2.8.7.0.4 image works after all. Gonna sit on the older build until it's confirmed working.
[ONE Android Development] fmc000:
Same for me.
[ONE Android Development] ketut.kumajaya:
TWRP's tar rather stupid to handle vfat filesystem, try to preserve files properties and quickly fail when not satisfied with the root of filesystem property. Proper fsflags make my TWRP build fail to restore previous version of firmware backup, improper fsflags fail to restore 2.8.7.0.4 backup. Busybox's tar working on both conditions, a life saver command:

cd /firmware
tar -xvf <backup directory>/firmware.vfat.win
[ONE Android Development] randallstevens:
Hello, thanks for the modem flash fix. I've confirmed it works by rechecking the md5 sums of the flashed partitions.

Could you please share what was changed to make this work? The same fix can be used for the multirom twrp. Thanks.
[ONE Android Development] ketut.kumajaya:
Remove fsflags option https://github.com/kumajaya/android.../blob/cm-12.1/recovery/root/etc/twrp.fstab#L9

/firmware vfat /dev/block/platform/msm_sdcc.1/by-name/modem flags=mounttodecrypt;backup=1;display=Firmware
[ONE Android Development] deepaklunked:
Hi [MENTION=3814731]katinatez[/MENTION]. I have a request. Can you please release a twrp 2.8.6.0 recovery with the new GUI? It looks really cool. But I feel that 2.8.6.0 is really stable..

#staySlim
[ONE Android Development] djha53k:
Yes please!
[ONE Android Development] renaltosonylevi:
You should try 2.8.6.0.6

It will do all that twrp 2.8.6.0 will do and it has that modern material look that everyone likes. It also enables you to backup firmware, efs, trustzone etc.
[ONE Android Development] deepaklunked:
I am using that. But I asked for the new GUI that we have in 2.8.7.0.3.

#staySlim
[ONE Android Development] djha53k:
Where can I get it? I google it, but found nothing :( thank you
[ONE Android Development] renaltosonylevi:
Did you try

Young people. Bah
[ONE Android Development] MoistPicklez:
No respect! *shakes cane*
[ONE Android Development] AcmE85:
[MENTION=4021423]ketut.kumajaya[/MENTION]

Flashing a Nightly takes much longer on your recent 2.8.7.0.4 compared to 2.8.6.0.6.

Is this a known "issue"?
[ONE Android Development] djha53k:
Got twrp-2.8.6.0.6-bacon-materialised-signed.zip now. :good:

Strange that it didn´t find before :(

Thank you.
[ONE Android Development] renaltosonylevi:
As I understand the rules of XDA it is all right to be helpful as long as you are grumpy as you do it.:rolleyes:
[ONE Android Development] ashok:
Guys. please help. My twrp is showing unable to mount storage. when ever i try to backup in twrp
[ONE Android Development] Adduu:
It's right there in the first post mate. You didn't have to Google.
[ONE Android Development] Holymartyr:
Just wanted to add, this is also my issue, been trying every version I can find to try getting this to work. Official TWRP 2.8.7.0 does in fact load up, and the latest Unofficial TWRP 2.8.7.0.4 Bacon Materialised appears to load, but the mkfs-f2fs operation to wipe the cache hangs.

Anyone else?
[ONE Android Development] KaZo58:
yes i though the same, but it's not hanging, it took longer (than 2.8.7.0.3) to wipe.
[ONE Android Development] Holymartyr:
I never tried the 2.8.7.0.3 build, I was using 2.8.6.0.6 for the longest time, until just today when TWRP wouldn't load past the main logo startup screen. (As described earlier in this thread)

I let my OPO sit for about 10 minutes and nothing ever changed. Thought it was hung, though wasn't completely sure since the lock button would still do the TWRP lock screen, and all 3 softkeys were still giving haptic feedback. Boy I'll feel silly if I really didn't just wait long enough, but even then - 10m+ to 'wipe' a 500mb partition? Something feels wrong O.o
[ONE Android Development] KaZo58:
oh lol okay. maybe try 2.8.7.0.3. are you pressing wipe caches after flashing rom or wiping under wipe menu? try to change partition to ext4 and then back to f2fs.
[ONE Android Development] Holymartyr:
Amazingly 2.8.7.0.3 doesn't load for me either. I was trying to wipe under the wipe menu, it would freeze during wipe, and trying to change the partition to ext4 and back threw an error as well.

Edit: 2.8.7.0.3 did work for me, but somehow ended up loosing all the restores on my device. Thankfully I had backups on my comp. Trying to restore one of those backups through 2.8.7.0 official...not having fun =(

Edit2: Good grief! Tried moving a restore from my computer to my OPO via MTP built into TWRP, shows the file on my computer, doesn't show the file on my device. When I reboot back into TWRP, it no longer shows the file on my computer, still doesn't show up in TWRP - yet my computer reports that an extra 3gb of space is now occupying my OPO (the size of the restore I moved). I have no idea what's going on. I ended up fully wiping the data partition, making a backup of a blank cache to have TWRP make a new backup folder, moving my good restore to that folder, and finally using 2.8.7.0.4 to do the restore. We'll see if the restore works (hope to god it does z.z)
[ONE Android Development] KaZo58:
i found something on other threads. type this in adb shell:

su
busybox dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/cache
[ONE Android Development] Holymartyr:
I understand that'l wipe my cache, I think - but I'd rather have TWRP do it lol - I finally sorted my issues out, but have gone back to the official 2.8.7.0 TWRP for now until this version gets an update for w/e f2fs bug is plaguing it >.<
[ONE Android Development] SubNoizey:
Where can I see the changelog? what's new in 2.8.7.0.4 ??
[ONE Android Development] zBear:
http://xdaforums.com/showpost.php?p=63300937&postcount=718
[ONE Android Development] DjDiabolik:
Hey boys... i have read whit this unofficial twrp it's possible, respect the original project 2.8.7.0, flash the baseband included into rom and similar....... now on my opo i have the original project... it's safe to be replaced whit this or not ?

I thinks i can use flashify whit root access...... i ever used this for flash or upgrade the twrp right ?
[ONE Android Development] @punto:
can the twrp 2.8.7.0.4 flash modems?
[ONE Android Development] AmyClaraRose:
do any of these versions work with aroma packages
[ONE Android Development] zBear:
author said it does
[ONE Android Development] deepaklunked:
Nope. The last one that does, AFAIK, is 2.8.4.0, or maybe even older.

#staySlim
[ONE Android Development] hb17:
I've had no problems flashing firmware with this version.

私のベーコンから焼けるように暑いです
[ONE Android Development] g-oleg:
Aromafm works fine for me with 2.8.7.0.4

Отправлено с моего A0001 через Tapatalk
[ONE Android Development] Ejvyas:
author?
[ONE Android Development] deepaklunked:
He meant the developer, [MENTION=4021423]ketut.kumajaya[/MENTION]

He didn't mean AromaFM. Aroma installers, like OpenGApps aroma package, don't work with the new TWRP.

#staySlim
[ONE Android Development] dlhxr:
finally we get the fix...I reported several times that modem flash has problem......and you all say that it's my own problem...

Anyway thanks for the developers' effort. We appreciate a lot~
[ONE Android Development] DjDiabolik:
Because someone can't upgrade the fist page whit latest version?
[ONE Android Development] Ejvyas:
But its not [MENTION=3814731]katinatez[/MENTION] build. Its from a different member
[ONE Android Development] DjDiabolik:
Ah interesting... And there's used same thread.. Ok.. Thanks for info...
[ONE Android Development] Ruvy:
I have a question. Just finished flashing 2.8.7.0.4 and came here to read few of the last pages. Surprisingly few of the guys are facing problem with it. Just to be sure, is anyone with EXT4 also facing problems or is it only those with F2FS ?
[ONE Android Development] lukazaz:
where can I get an aroma compatible copy I hear the 2.8.7.0.4) does work with the gapps aroma version but I can't seem to find it please help me - for the Note 4 (N910F) trltexx
[ONE Android Development] YamazakiRobert:
hello the last version 2.8.7.0.4 always give me a error regarding the reseve4, this is a recovery or a phone issue?

thanks
[ONE Android Development] deepaklunked:
Aroma zips do not work with the newer versions of twrp. If I remember it right, then the last twrp that flashes aroma is 2.8.3.0, I guess.

Tapatalked through VM-ed Bacon
[ONE Android Development] katinatez:
I think it's twrp_2.8.6.0 that supports it. Will also be updating op to reflect the most current build v2.8.7.0.4 from [MENTION=4021423]ketut.kumajaya[/MENTION]
[ONE Android Development] deepaklunked:
No bro. I have tried Open GApps Aroma package with twrp 2.8.6.0 (tried it before maybe 3 months). It never worked, neither with the official nor with the unofficial.

Tapatalked through VM-ed Bacon
[ONE Android Development] AmyClaraRose:
2.8.1.0 is only version working with aroma packages for me

---------- Post added at 17:20 ---------- Previous post was at 17:19 ----------

This is wrong thread this is for one plus one this recovery won't work on your phone
[ONE Android Development] pijas82:
hi, twrp 2.8.7.0.4 had efs backup?

thanks
[ONE Android Development] fmc000:
It should have it.
[ONE Android Development] ketut.kumajaya:
Materialised latest TWRP (android-6.0 branch) available for download http://goo.gl/rqjprv
[ONE Android Development] drishd:
Thanks. No flash-able zip?
[ONE Android Development] trascendence:
Thank you very much. Does it work for LP? I ask because I don't really understand the meaning of 'android-6.0 branch'. Currently I'm on CM 12.1.
[ONE Android Development] AcmE85:
Could you please specify what changed compared to the previous version?
[ONE Android Development] ketut.kumajaya:
No, you can flash using your current TWRP.

TWRP developers maintain recovery compatibility to 2 or 3 Android version.

Just Materialised theme adaptation on top of latest TWRP source https://github.com/kumajaya/android_bootable_recovery/commits/android-6.0-materialised Almost no changes from my side except a small fix for Materialised text placement, device tree, kernel, and upstream CyanogenMod update.
[ONE Android Development] AmyClaraRose:
Could you try to fix aroma packages not working pls
[ONE Android Development] ketut.kumajaya:
Aroma framebuffer driver not working properly on our Qualcomm framebuffer, I have reported this to Aroma developer and no response so far. I have tried to build Aroma inside cm-12.1 source tree but failed with a lot of strange errors.
[ONE Android Development] AmyClaraRose:
Oh OK :( I hope there's a fix soon
[ONE Android Development] pijas82:
hi, i use 2.8.7.0.4 and katinatez rom,

i made one backup(efs) if i want to change to oficial twrp , can i restore efs?

another question, i made a backup 4 months ago(cm12.1 rom) with oficial twrp

can i restore with your twrp?

thanks
[ONE Android Development] Ejvyas:
Does this flash firmware properly unlike 2.8.7.0?
[ONE Android Development] katinatez:
Did you update adb binaries to 1.0.32 like op says?

Edit: never mind I thought you saying sideload would not work.

Don't run into many fellow arch users. I run arch also.

Enjoy
[ONE Android Development] diegocr:
To work mtp on ubuntu need to add the following entry to /lib/udev/rules.d/69-libmtp.rules

ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess"

test adb version with "adb version"
[ONE Android Development] Criton30:
found the solution.
[ONE Android Development] katinatez:
I will be updating recovery on my weekend to address reboot.
[ONE Android Development] Criton30:
fastboot erasing/formating recovery drive has resolved my issue! after this I have clean installed you recovery and now no issue ! - no random reboot!!!!
[ONE Android Development] katinatez:
Never thought of that, going to try myself and test for a few days. Thanks for the tip.
[ONE Android Development] Criton30:
noob question, sorry....
[ONE Android Development] tobitege:
Put the zip onto your phone and flash it in recovery via Install like a rom archive. :)
[ONE Android Development] Criton30:
The recovery install it manual, so we dont need the zip file.
[ONE Android Development] tobitege:
I was replying to the question in your previous post regarding SuperSU, sounds like we are talking about two different things? :silly:
[ONE Android Development] Criton30:
I talk about SuperSu too :) If you reboot the recovery , it asked you to install SuperSU, and if you click on it, it will install the newest 2.40.
[ONE Android Development] tobitege:
Oh, ok. I've been flashing 2.42 beta since it came out and from today on v2.43 beta, only needed the recovery to do it for me one or two times.
[ONE Android Development] Criton30:
reboot issue is still existing.... if I want to restore nandroid backup and md5 is checked then in the verifying process the phone rebooted... same issue in the original twrp 2.8.3.0.... :(

[MENTION=3814731]katinatez[/MENTION]: do you have checked in my last post the log file? it is very annoying, because with the twrp 2.8.1.0 I can not copy my nandroid back and with the newest recovery I have random reboots.....
[ONE Android Development] tobitege:
I always check the md5 on my PC, never on the phone (saves time), transfer via Wifi/MTP onto phone never created a corrupted file here. I also never download roms on the phone itself, only PC (matter of taste).

The question here is: does your recovery still reboot when md5 checking option is disabled?

Simple workaround: to get your nandroid back to your phone first flash K's twrp 2.8.3.0, copy the files to your phone, then flash again 2.8.1.0 version. The newest version has the file transfer fixes included so that 1GB+ files can finally be copied via MTP.
[ONE Android Development] Criton30:
without md5 check no problem.... but this is not a workaround....

other question: nandroid backup saves my radio/modem file too? what is with philz recovery? could it recover my nandroid backup? or nandroid backup is only for twrp?
[ONE Android Development] tobitege:
Not a workaround, but it narrows down the actual error source so that K actually knows where to look. Before it wasn't clear to me that the MD5 check was an issue at all. :)

K's recovery can backup/restore modem partitions, labelled as "EFS" in the recovery. Can't answer anything about philz as I never used it, sorry.
[ONE Android Development] Criton30:
ok thanks, and EFS will be automatically saved in the backup or I should check it for saving?
[ONE Android Development] tobitege:
You have to check it explicitly when doing a backup, yes (it should remember your selection next time).
[ONE Android Development] Criton30:
TWRP backed up /boot /system /data nothing else, therefore is my question modem is also saved? because this efs I did not see.... :(
[ONE Android Development] tobitege:
I'm referring to this thread's TWRP 2.8.3.0 version only.
[ONE Android Development] DjDiabolik:
You can use flashify.... It's perfect 4 img file...
[ONE Android Development] drishd:
I know! 1 can flash images thro TWRP also.
[ONE Android Development] AcmE85:
I tested it today and it runs fine so far. The only thing I already noticed on previous 2.8.7.0.X versions

ist that it takes noticeably longer to flash for example a nightly update compared to 2.8.6.0.6.
[ONE Android Development] DjDiabolik:
Absolutly right :) :thumbup:
[ONE Android Development] Ejvyas:
Is twrp-2.8.7.0.5 compatible with f2fs?

Does it flash modem?
[ONE Android Development] cristianvaz81993:
perfect thanks
[ONE Android Development] BoboBrazil:
Thanks for this. Is there a reason you don't put the full version number in TWRP? I was trying to make sure it took my flash of .05, but I can't find the .05 of the build number in the header of twrp or in the about info.
[ONE Android Development] ketut.kumajaya:
Did you mean https://github.com/omnirom/android_bootable_recovery/blob/android-6.0/variables.h#L20 ?
[ONE Android Development] ketut.kumajaya:
Ext4 mount flags from normal boot applied to TWRP 2.8.7.0 . So, default ext4 flags way faster?
[ONE Android Development] BoboBrazil:
Yes.
[ONE Android Development] ketut.kumajaya:
I even don't understand why no revision version from upstream TWRP :confused: So, .5 specific for bacon for my own build. I have a different name convention for a different device target :(
[ONE Android Development] Phate00:
Is this new version is MULTIROM supported? Also am i be able to flash firmaware with latest twrp ver becuaseany time ROM flashing gives error which is solved by using twrp 2.8.6
[ONE Android Development] AcmE85:
:confused:

I went back to 2.8.6.0.6 and it flashes faster than 2.8.7.0.5. I'm on ext4 btw.

What I mean is, when flashing a nightly for example, "patching system-file unconditionally" is displayed longer...

(2.8.6.0.6 used to freeze on splashscreen while I was using F2FS)
[ONE Android Development] Ejvyas:
bump
[ONE Android Development] fmc000:
It has been reported for the official versions too and not only for the modded ones.
[ONE Android Development] katinatez:
All you have to do is read the github to see that f2fs is supported on data/cache for v2.8.7.0.5

For full f2fs support in all 3 partitions, the kernel needs f2fs commits. If ketut compiled with latest cm-12.1 commits then f2fs is supported in kernel also.
[ONE Android Development] gravin:
TWRP version 2.8.7.0.5-materialised, flashing modem????
[ONE Android Development] Ejvyas:
well...I asked this 3 times . still waiting for answer..:D
[ONE Android Development] marco2012:
Encryption

Hello, this unofficial version of TWRP is awesome, but I have one doubt:

Does it work well with an encrypted OnePlus One??

I've read here and here that the official 2.8.7.0 had problems with encryption.

Are this problems fixed on this unofficial build ?

Thanks :)

EDIT: I tested it myself and I can confirm it is working well with encryption and decryption.
[ONE Android Development] danieldmm:
Trying to make system partition format in f2fs over updater-script installing rom.

run_program("/sbin/mkfs.f2fs", "/dev/block/platform/msm_sdcc.1/by-name/system");

Missing something? Or TWRP don't support this command? It's always in ext4 and must format manual.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] cloudx720:
This twrp is awesome! btw if I extracted the recovery.img from stock cos12.1 and flash it via flashify, anytime I receive an ota update would the ota work? Thanks.
[ONE Android Development] danieldmm:
If you don't touch the system... Yes...

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] cloudx720:
Well I used twrp to get root with latest supersu and also to flash boeffla kernel. I also use the app bootunlocker highly recommended app works with opo, you can unlock and relock your bootloader on the fly from within android without the need to wipe the device. ?
[ONE Android Development] ketut.kumajaya:
Thanks for your confirmation. I can't check it since have no plan to encrypt my device.

Experiencing a bad Marshmallow update here, device repeatedly sudden reboot randomly, official CyanogenMod.

Unlike the current available version, I will rebuild TWRP inside cm-13.0 device tree later today. I hope encryption still working.
[ONE Android Development] marco2012:
Unofficial TWRP 2.8.7.0

My OnePlus is working well with latest unofficial TWRP and marshmallow, but I'm running AOSP based rom SlimSaber.

Just a heads up: upgrading an encrypted device from lollipop to marshmallow will corrupt the encryption, therefore data won't be accessible anymore. Hence, encryption should be removed before upgrading, by performing a factory reset.
[ONE Android Development] ketut.kumajaya:
The flashable system image in ext4 format, so system partition always overwritten to ext4, updater script change not applicable. You can backup system partition, format system as f2fs, and than restore back your backup. Make sure your kernel support system as f2fs or not boot at all. In my opinion, as read only partition, no much benefit formatting system as f2fs.

EDIT: Just finished, default the new theme:

EDIT2: Qualcomm crypto daemon still running, all known crypto driver get loaded, I hope encryption support still working but please check comment above me.

EDIT3: The new version twrp-2.8.7.0-bacon-20151227.img, built inside cm-13.0 source tree http://goo.gl/rqjprv
[ONE Android Development] nolsen311:
Sorry if these have been covered repeatedly, but I can't figure out how to get Tapatalk to search just this thread.

Couple things:

1) device encryption CONFIRMED working on cm13 nightlies for bacon?

The HW encryption has been problematic on every major version upgrade since ICS. Not anyone's fault, just happens.

2) modem bug? Does this version of TWRP suffer from inability to properly flash modem/baseband?
[ONE Android Development] danieldmm:
But my rom zip its using old style and not the system.dat style.
[ONE Android Development] deepaklunked:
[MENTION=4021423]ketut.kumajaya[/MENTION]

The latest twrp looks awesome. Thanks for the update..

Sent from my OmniBacon
[ONE Android Development] Ejvyas:
LOL..thanks for asking the question. 4th time now. Try Philz meanwhile
[ONE Android Development] ketut.kumajaya:
If you don't want to check it, maybe someone else will confirm it for us.

No problem for me but much fair if someone else also confirm it.
[ONE Android Development] ketut.kumajaya:
Recovery log will help us what exactly happened.