yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] TheArchersNest:
its off topic but can anyone tell me about this one

"flash_image /dev/block/platform/msm_sdcc.1/by-name/reserve4 /dev/zero process ended with error=255"

while i tried to format data in twrp-2.8.7.0.7-bacon-materialised.img
[ONE Android Development] GasLoop:
Thanks! I'll give it a shot right now. :good:
[ONE Android Development] fmc000:
I wonder why there was no announcement by [MENTION=4021423]ketut.kumajaya[/MENTION] for this release.
[ONE Android Development] xlollomanx:
Maybe he simply can't because is busy.

Sent from my Oneplus One
[ONE Android Development] paarkhi:
[MENTION=4021423]ketut.kumajaya[/MENTION] TWRP 3 is released and the team is asking the developers to help them in building and maintaining the devices, TWRP team only has 3 members at present, so it may take some time for the official release to come for OPO, if you can help them with it for OPO then we will get the update early.

Thanks
[ONE Android Development] Phate00:
+1
[ONE Android Development] P1nGu1n_:
For everyone wondering what's new in 3.0.0: Android Police Article

To clarify: this version is not released yet, there's no official and no unofficial release.

Edit:

Official TWRP announcement: twrp.me

Thereafter, the TWRP's Jenkins started building. Bacon built successfully, I was not able to find a download link yet though.
[ONE Android Development] Phate00:
https://www.androidfilehost.com/?w=files&flid=30332&sort_by=date&sort_dir=DESC

Unofficial build
[ONE Android Development] usvimal:
Deleted :(
[ONE Android Development] Phate00:
Its there not deleted https://www.androidfilehost.com/?fid=24399994186369589
[ONE Android Development] usvimal:
New version works well and flashes firmware :good:
[ONE Android Development] deepaklunked:
Thanks a lot for the link. Downloading now.
[ONE Android Development] fmc000:
My goodness, that's what I call "amazing support". Than you very much [MENTION=4021423]ketut.kumajaya[/MENTION] .
[ONE Android Development] danieldmm:
Working good [MENTION=4021423]ketut.kumajaya[/MENTION] , you should go to maintener of official TWRP :)

Cheers and great work.
[ONE Android Development] ketut.kumajaya:
It's my pleasure to help you :good:
[ONE Android Development] deepaklunked:
Really good job [MENTION=4021423]ketut.kumajaya[/MENTION]. You should actually become the official maintainer of our bacon, but still produce unofficial builds (for the extra support). ;)
[ONE Android Development] TonySuperPony:
Thanks, will it be easy to make a materialized, modded version?

Or has there been a lot of changes?

Also, does this one have efs support?
[ONE Android Development] P1nGu1n_:
Yes, EFS is supported. Don't know about the theme related stuff.
[ONE Android Development] fmc000:
EFS backup vwas the first thing I did after flashing this new release.
[ONE Android Development] :
Thanks for this build and supporting the community!!

I'm having problems to enable USB-OTG, I can't mount an usb stick - what I'm doing wrong. Anybody with the same challenge??
[ONE Android Development] david72262:
Works fine. Just did a backup to otg-usb.
[ONE Android Development] :
Thanks for your quick feedback, but ... strange: with 2.8.6.0 and 2.8.7.0 otg-usb was/is working fine and without any problems. 3.0.0.0 doesn't recognize the USB device (led doesn't flash).

I'm a bit lost. Any ideas?
[ONE Android Development] david72262:
Works as expected for me. Bad flash? Check file md5? Did you mount otg?

Edit

Second time in I had to unplug and replug otg to get it recognized.
[ONE Android Development] maikvitesse:
This is great! thanks!

keep up the good work!
[ONE Android Development] 2384315154:
HW decryption failed on Sultans CM13 for me, had to go back to 2.8.7.1

OTG is also working, I used it to flash back to 2.8.7.1 - plug it in when you're booted into TWRP and not before
[ONE Android Development] Dr.Now:
Connect to your USB stick only on when the One in recovery is . In my USB stick 128GB exFAT4 works! Properly
[ONE Android Development] Phate00:
Try official version...I never tried encrypt or decrypt
[ONE Android Development] counterfeit187:
What's different between official 3.0 and the linked unofficial one?
[ONE Android Development] Anghirrim:
Seems the unofficial has correct efs backup.
[ONE Android Development] robuser007:
Backup/restore for EFS and other partitions (& maybe something else).
[ONE Android Development] Anghirrim:
Hey, I am questionning myself...

I am currently under the latest COS firmware/modem.

I tried to flash the latest CM13 official nightly on the top of it to see whether TWRP 3.0.0 was able to flash correctly the modem.

And.... And /system is flashed correctly but when it comes to all the other files (non-hlos, logo, etc...), TWRP says they are all up to date and does not flash them.

I have the same behavior under official TWRP 2.8.6.0 and materialized TWRP 2.8.7.0.5. Modem version never changes.

Any idea why this happens?

Thanks
[ONE Android Development] AcmE85:
The latest cm13 nightly has the same firmware which is used by cos right now, that's the reason.
[ONE Android Development] funCrash93:
what about f2fs? Official? Unofficial?
[ONE Android Development] DjDiabolik:
[MENTION=4021423]ketut.kumajaya[/MENTION] it's time to change the title of thread :)

Great work on 3.0.0.0 unofficial.......... tomorrow i upgrade on my :)
[ONE Android Development] Anghirrim:
Ah.... Ok thanks. So the real test will be H2OS or other...
[ONE Android Development] fmc000:
So it seems that neither 3.0.0 official nor 3.0.0-0 materialized are capable to decrypt CM13-based ROMs /data partition. My question is: has this ever worked for anyone? I read on the official thread that the "unreleased" 2.8.7.1 was capable of that but I don't use encryption, so I can't confirm.
[ONE Android Development] funCrash93:
latest twrp-2.8.7.0-bacon-20160130.img should be able, no?

there was a discussion on this some pages ago, there were users saying it worked if I can recall correctly :)

give it a search here ;)
[ONE Android Development] fmc000:
I already tried and I haven't been able to find a single user who said that he or she was able to successfully decrypt a CM13 /data partition. CM12-based systems are known to work, I'm talking about fresh CM13 encrypted installations.
[ONE Android Development] funCrash93:
dunno then :)

what about Philz Recovery?
[ONE Android Development] flyfire04:
So after all this talk here in the thread about encryption with twrp I thought it might be easy so I gave it a shot with sultans rom and the newest unofficial build of TWRP 3.0. The ROM did not accept the PIN I set and twrp was not able to decrypt the data partition. So i downgraded twrp to diffrent builds of the unofficial version all with the same result. So I was lucky to have a backup.. No more encryption for me.
[ONE Android Development] enkidu70:
Hi all,

for a long time I stayed with 2.8.6 without any problems. Now I tried 2.8.7.* and 3.0 but adb does not work. First I got "unauthorized" after flashing different versions ecc, now I get offline!?

Flashing back to 2.8.6.0.6 still shows offline. What happened!?!?!?! (Also flashing back to original CM recovery and flashing back to twrp did not solve my problem.)

Need help please!

$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device.

$ adb shell
error: device offline

$ adb devices
List of devices attached
8a0d654d	offline

$ adb version
Android Debug Bridge version 1.0.31

Tnx in advance,

Enkidu
[ONE Android Development] cg6ry79m@gmail.com:
I have used multiple TWRP versions including 3.0.0.0 to update/flash Cyanogen 13.x versions on my encrypted phone. Seem to work well with Cyanogen builds including 13. Backup and restore of an encrypted device running Cyanogenmod nightlies seem to work well for me.

The only issues I have had are related to encrypting a backup using that encryption capability within TWRP. That seems a little flakey.
[ONE Android Development] fmc000:
Did you encrypt with CM13 or with CM12 and then upgraded?
[ONE Android Development] jukyO:
Not related with recovery. You need to have screen on, while adb shell, so you'll see dialogue on the phone .
[ONE Android Development] tiny4579:
Encrypted on which nightly? 2.8.7.1 worked until they changed firmware recently. 3.0 should be the same as I believe it would use the same exact blobs.
[ONE Android Development] enkidu70:
Does TWRP use my Android (CM13) settings? Well, I can connect via adb if my system is up!

Btw, where can I reset ADB allowed devices list in CM13/MM?
[ONE Android Development] cg6ry79m@gmail.com:
I did a clean build from bare metal when I moved to Cyanogen 13 back when it came out and then reencrypted the device if I remember correctly. If that's what you are asking.
[ONE Android Development] fmc000:
Ok, this explains everything I suppose. Thank you.
[ONE Android Development] pbergonzi:
I'm not sure, but maybe the "unauthorized" means you have to disconnect phone from PC, go in Developer Settings and "Revoke USB Debugging Authorization", and reconnect to the PC.
[ONE Android Development] wahuka:
When an unofficial release of version 3?

Thanks
[ONE Android Development] infatality:
Already released.. Search a few thread back
[ONE Android Development] PlasmaPump:
I just flashed TWRP 3.0 Unofficial from Feb 6 and when I try to boot into TWRP is reboots and goes into CM11s. I used Flashify to get Official TWRP 3.0 in and it boots into TWRP no problem. Do I need to have the latest firmware in to run the Unofficial version? Hmm I had the Unofficial 2.8.7.0 form Jan 11 and it booted into recovery no problem. I also tried the Unofficial 2.8.7.0 form Feb 4 and that won't boot either???

Any clue why the Official TWRP 3.0 boots and the Unofficial won't???
[ONE Android Development] arh2o:
What's the difference between the official 3.0 found on TWRP home page and the unofficial one you made ketut.kumajaya? Thanks!
[ONE Android Development] Genericxx:
The official one is an official one, while ketut's one is an unofficial one :D

Joking aside, i guess ketut's twrp builds are able to backup efs partition. But i have not personally checked. I've tried unofficial twrp-3.0 and it gaves trouble while flashing slimsaber omni based builds, so i downgraded to 2.8.6.0.
[ONE Android Development] funCrash93:
what about f2fs?

OTG NTFS? :)
[ONE Android Development] Genericxx:
f2fs works, dunno about otg, because i'm not using it
[ONE Android Development] david72262:
Otg works good
[ONE Android Development] cloudx720:
How come official twrp doesn't backup efs and others like in unofficial twrp? ?
[ONE Android Development] fmc000:
Because it was designed that way.
[ONE Android Development] Wisiwyg:
And that's one of the several reasons people like and use unofficial twrp!
[ONE Android Development] josera06:
I try to install a theme materialised 287X_v2_1080_play.zip with the TWRP-28707-bacon-materialised.zip but i can't.

I get a error: String resource theme_ver_err not found. using defalult value. theme version does not match twrp version. using stock theme.

What i doing wrong?
[ONE Android Development] funCrash93:
on FAT32 USB Drive?

what about on NTFS Drive?
[ONE Android Development] PlasmaPump:
Anyone using 3.0 on a kitkat or cm11 rom? Works?
[ONE Android Development] RBwai:
This theme problem is due to new theme concept and new functionalities. There is no custom themes for 2.8.7. X for now.
[ONE Android Development] storm119:
New commits changed the structure of the theme + its bring new features like multi-language and true terminal emulator that will brake the custom materialised theme because the theme isn't support that features yet...but if you planing on using custom materialised theme you can choose TWRP version 2.8.7.0 up to 2.8.7.0.5 (unofficial).

Only TWRP starting with 2.8.7.0.6 (unofficial) up to 3.0.0.0 is NOT compatible with current custom materialised theme...but the themes will works/compatible with TWRP 2.8.7.0 - 2.8.7.0.5 (unofficial build by ketut)
[ONE Android Development] thegiolly:
wipe system doesn't work on 3.0.0-0
[ONE Android Development] maxed4901:
Love the twrp theming. Any chance u guys might work on twrp3?mumtirom is now in twrp3
[ONE Android Development] cloudx720:
Yeah it does, well for me at least ?
[ONE Android Development] Zwenk:
i flashed 3.0 and it cant decrypt my partition. with 2.8.7.0.7 i have no issue
[ONE Android Development] GasLoop:
It appears to me that I can't decrypt the data partition when I encrypt my current files. If I wipe the phone, flash the new rom and encrypt it, everything appears to be fine. Any ideas?
[ONE Android Development] AcmE85:
2.8.6.0(.6) does not support encryption as far as I know. Neither does is support F2FS btw.
[ONE Android Development] Uqbar:
v3.0.0-1 is available with a whopping 13 MB image!
[ONE Android Development] funCrash93:
so in theory fixes hardware decryption? (as git commits suggest :confused: )
[ONE Android Development] Tajnymag:
Does it flash modem even though it's official?

Odesláno z mého A0001 pomocí Tapatalk
[ONE Android Development] Uqbar:
v3.0.0.0 did. I would be surprised if this very one failed!
[ONE Android Development] danieldmm:
All the mess continues. The new one is still same version on TWRP. They did not uptake the version. Also is strange because on github don't find nothing new submited to our device.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] anagramgenius:
That's because of new font type DroidSansFallback which is 3.6MB!

And 3 new languages.
[ONE Android Development] funCrash93:
you could check the build log and spot the differences

2.8.7.0 : https://jenkins.twrp.me/job/bacon-prod/2/consoleFull : Jun 20, 2015

3.0.0-0 : https://jenkins.twrp.me/job/bacon-prod/3/consoleFull : Feb 5, 2016

3.0.0-1 : https://jenkins.twrp.me/job/bacon-prod/4/consoleFull : Feb 17, 2016
[ONE Android Development] Renosh:
You should check the Gerrit instead of blabbing things you don't know

https://gerrit.omnirom.org/#/q/project:android_bootable_recovery+status:merged

There are changes and everything works that I had issues with before
[ONE Android Development] danieldmm:
You did not understand. How the hell new official build was made if in source there is no change? Is this the question.

Enviado do meu A0001 através de Tapatalk

---------- Post added at 11:24 AM ---------- Previous post was at 11:22 AM ----------

Why are you liking to ominrom gerrit? Oficial twrp is here:

http://gerrit.twrp.me/

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Renosh:
Shows how much of a noob you are if you can't tell why I linked that particular Gerrit. Look at it and look at the changes above 3.0.0-0 that's what's new
[ONE Android Development] danieldmm:
You pick the wrong guy, you still don't understand my question. Don't add answers relative to my question please. If you don't know just be quite.

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] funCrash93:
even AROMA now works?
[ONE Android Development] danieldmm:
Never the less also this is the wrong thread to ask my question. Some mode please clean this, will make the question on the appropriate thread. Though was on official twrp thread...

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] Renosh:
He works from Omnirom Gerrit, is that so hard to understand. That's why you see no changes in github or wherever you looked yet he bumped up the version with the minor changes. You're the one who doesn't know and I gave you the changes so you educate yourself.

Never used Aroma on OPO so no idea its been years since I last used it lol
[ONE Android Development] funCrash93:
Open GApps has AROMA version, quite handy ;)
[ONE Android Development] Renosh:
Yeah I've seen it but I just use the gapps-config.txt and delete whichever files I don't need from ROM and gapps. Thanks
[ONE Android Development] cg6ry79m@gmail.com:
So I don't know what happened but neither 2.8.7.0 Bacon nor 3.0.0.0 Bacon work on my encrypted phone. Each build gives me password failures when opening TWRP. It started a couple weeks ago I guess. Not long after 3.0.0.0 came out. 2.8.7.0 was working on my encrypted phone and 3.0.0.0 worked for a minute too.

Then one day I got that android error "your password was correct but your data is corrupt so go ahead rebuild your device".

Oh great.

So after that I couldn't encrypt because no matter what version of TWRP I used, it would throw password errors.

I finally got situated so I could try some variations but in the end ... No versions of twrp bacon works with phone encryption and it used to work a short time ago.

:(
[ONE Android Development] fmc000:
If you're using CM, I heard that they changed their encryption procedure in late January and so far no TWRP version are able to decrypt. Look at CM13 thread for details, there should be something there.
[ONE Android Development] danieldmm:
Maybe because you encrypted with software at that time. CM on our device changed to hardware encryption. If you encrypted with software you cannot use hardware decrypt and vice versa.
[ONE Android Development] cg6ry79m@gmail.com:
Actually I encrypted the OnePlus 1 running CyanogenMod 13.1 by simply pressing the "encrypt phone" button in settings. Is there some other way that I don't know about?
[ONE Android Development] fmc000:
Have you read my post above?
[ONE Android Development] Sukarn:
It isn't really clear about which situation creates a software encryption and which creates a hardware encryption.
[ONE Android Development] fmc000:
I suspect it's the date you first encrypted your device. If you did it after cm changed from soft to hard you can't decrypt with twrp but only with cm recovery (I hope).
[ONE Android Development] Renosh:
[MENTION=6710766]cg6ry79m@gmail.com[/MENTION]

https://gerrit.omnirom.org/#/c/16940/

Just check the comments by Sultan Qasim. Might be what you're experiencing. So try official TWRP 3.0.0-1 and see if it can decrypt your phone before Kumajaya makes a build
[ONE Android Development] Sukarn:
I'm not the one facing the issue. I was only commenting on the clarity of the explanation :)
[ONE Android Development] cg6ry79m@gmail.com:
Official TWRP 3.0.0-1 also did not decrypt the device. The device has been re encrypted several times so I could troubleshoot it. No TWRP, official or unofficial, decrypts CM successfully it seems.
[ONE Android Development] fmc000:
...as I already told you before.
[ONE Android Development] Renosh:
What nightly did you initially encrypt on before? And which one are you trying to do it on now? I'm suspecting the change by CM is the cause as [MENTION=791219]fmc000[/MENTION] keeps saying hence my suggestion. Also are you sure you're trying the latest TWRP 3.0.0-1 or 3.0.0-0 released much earlier?
[ONE Android Development] cg6ry79m@gmail.com:
I use CyamogenMod (CM) Nightlies ... Each one. As people pointed out ... Around Jan 30-ish all TWRPs stopped decrypting CM nightlies going forward. I know that this is known ... I an just trying to clearly state my observations so Mr Kumajaya, should he need those data points, has them.

I hope we can get back to being able to do nandroid dumps of post Jan 30-encrypted Cyanogen builds ... It is an incredibly useful capability.

Thanks to those who have taken a moment to clarify and help me understand the issue.

Cheers

---------- Post added at 11:32 AM ---------- Previous post was at 11:27 AM ----------

Yes ... I definitely tried 3.0.0-1. I noticed that it does not backup or restore the firmware partition, incidentally (since Mr Kumajaya probably has not done his magic on that release perhaps).

:)
[ONE Android Development] fmc000:
Wait, are you saying that "after Jan 30-ish" TWRP can't decrypt even /data partitions encrypted _before_ that date? I'm not an encryption expert at all but I thought that once the encryption was in place the data format wouldn't have changed by simply upgrading the ROM.

I thought that TWRP couldn't decrypt /data partitions encrypted _after_ that date, because CM changed the way the block device is encrypted. I would really like that some cryptography expert would chime in.
[ONE Android Development] cg6ry79m@gmail.com:
Well ... Truth is I only know that no version of TWRP will decrypt my device in the last two weeks in been messing around with it. I don't know that I ever tried but the one time I decrypt a /data that was encrypted before 30 Jan-ish. I it that strange error about "you entered the correct password but your data us corrupt". I figured I had some corruption so I wiped the device and restored a nandroid backup and I have had no love since then.
[ONE Android Development] tiny4579:
This commit fixed encryption on newer TWRPs and it does decrypt fine. Try re-encrypting if you haven't since around the 2/12 nightly.

https://github.com/CyanogenMod/andr...mmit/84e5d10c44e98d23b17f92636982fac3f3ed922a
[ONE Android Development] cg6ry79m@gmail.com:
Nope. Latest nightly (20160223). TWRP 3.0.0-0 Bacon. Wouldn't Mount encrypted partition when booting into recovery.

:(
[ONE Android Development] Renosh:
That's not the recovery with the issue fixed. 3.0.0-1 is the one they fixed hardware encryption on newer nightlies
[ONE Android Development] cg6ry79m@gmail.com:
Thank you. You are correct of course. I guess maybe I an dense or my reading comprehension is lacking ... I think others told me the same thing. ...

I think what threw me is the fact that I saw a bunch of errors during a nandroid backup using 3.0.0-1 because it does not do the firmware partition so I figured it was broken.

Thanks for the info.
[ONE Android Development] cg6ry79m@gmail.com:
I notice that 3.0.0-1 does not have the ability to select the firmware partition for nandroid backup. Can I infer that this version of TWRP does not flash new basebands if one was included in a ROM or a nightly or whatever? Curious.
[ONE Android Development] tiny4579:
Those are unrelated to each other. Plus official TWRP doesn't backup firmware so you are probably talking about the offical 3.0.0-1. This thread is for unofficial TWRP builds but I think official TWRP discussion made it in here. To answer your question 3.0.0-1 will flash firmware. It's just that a new baseband hasn't been released in a while and who knows when it will be.
[ONE Android Development] cg6ry79m@gmail.com:
Understand. Thanks!
[ONE Android Development] funCrash93:
so, no 3.0.0-1 build from [MENTION=4021423]ketut.kumajaya[/MENTION] ? :confused:
[ONE Android Development] danieldmm:
Why not share here also:

For quite some days, messing arround with TWRP.

Here you have my build, is build on top of cm13 source tree and using omnirom recovery tree. It have a few additions.

It can backup/restore firmware parts / EFS / and the habitual parts.

It wipes and flash roms faster, aroma is partially working, can use for example aroma file manager, but when try to use the open gapps aroma zip is a no go.

Cheers

https://www.androidfilehost.com/?fid=24438995911967708
[ONE Android Development] fmc000:
Would you mind telling the differences between your version and the latest official 3.0.0-1 ? Especially with regard to encryption.
[ONE Android Development] danieldmm:
Relative to encryption still a no go, it won't reboot to recovery. Still digging. Relative to change log you can check here:

http://xdaforums.com/showpost.php?p=65572584&postcount=2065

Enviado do meu A0001 através de Tapatalk
[ONE Android Development] fmc000:
Well, 3.0.0-1 works perfectly fine wrt encryption with SlimSaber, OmniROM based, and the changelog doesn't show your two latest versions.
[ONE Android Development] danieldmm:
When at home on pc will tell you the -4 and -5 changelog.

Also the interest is cm13, if it works with this roms -1, mine for sure will also work, Althought did not tested
[ONE Android Development] danieldmm:
here you have:

3.0.0-5

Fixed double restore of firmware backup

Allow setting backup file system from recovery fstab

Don't add subpartitions in firmware to restore list

Unix file endings and remove execute permission

Fix verifier_test build

Revert: WIP: use toolbox for ln instead of busybox

3.0.0-4

Include firmware in ramdisk to avoid touching /firmware

Backup firmware re-added
[ONE Android Development] fmc000:
Backup doesn't work when your phone is encrypted. Decryption works fine but the recovery fails to backup /data .