yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] lchiocca:
It's a message that tells you that you really know what you are doing. This post-boot script checks if the user is insane enough to install a twrp version on another phone than intended. The error code represents the insaneness-level.
[ONE Original Android Development] NHOman14:
But i download the image from here https://dl.twrp.me/yuga/. its for sony xperia z.
[ONE Original Android Development] Formhault:
You're in the OnePlus One thread.

Your phone appears to be a Sony Xperia - if your signature is correct, which I'm pretty sure it is.

Learn to read. For your own good.
[ONE Original Android Development] Lanchon:
guys! don't reset the phone when it's writing to the emmc!! you might actually break your phone for good!!!

twrp 3 is probably doing the right thing and using secure erase to wipe the partition.

not all wipes are created equal. its not the same thing to say:

-dear emmc, im not interested in this data anymore. please remember that, and whenever you need free space you can recycle that. also try to sort of hide it from me because i really don't want to know it's all there still

than saying:

-hey emmc, i really need all this data gone, and i need to know for sure when everything is gone for good. so don't do anything else besides this until you finish. if some useful data is in the same erase block with part of the data i need gone, well bad luck, do something! move stuff around, do garbage collection, copy data somewhere else, i don't care. but in the end of your work i need every single bit i marked for discarding gone for good

one operation can be done in seconds, the other might take a loooooong time, and it's not twrps fault! just get a phone with a faster emmc if you want faster wipes.

agreed that TWRP could have both, fast and secure, wipe options.
[ONE Original Android Development] jukyO:
Tried that, no problems observed. Wipe done momentarily. Used unofficial one though.
[ONE Original Android Development] mustang_ssc:
Yes, i partially knew that but it was taking so many time (quite minutes) that i thought it will never end, and that was i turned off the phone. May be i should have been more patient.

Thanks for the explanation.
[ONE Original Android Development] RBwai:
Same here with 3.0.0-0. Wiping cache and dalvik cache was blazeing fast.
[ONE Original Android Development] Bassick:
official or unofficial?
[ONE Original Android Development] RBwai:
From twrp page: https://dl.twrp.me/bacon/twrp-3.0.0-0-bacon.img
[ONE Original Android Development] girishb:
Just wiped dalvik & cache using 3.0.0. The wiping dalvik cache part was pretty quick but it took a little over 5 minutes at "Formatting Cache using make_etx4fs". Not sure if this was a first time thing. Need to run it again to be sure.
[ONE Original Android Development] djha53k:
Can the v3.0.0.0 flash FW ?

If yes, then finaly I could move on from v2.8.6.0 ;)

Thanks for info.
[ONE Original Android Development] AcmE85:
If you don't use encryption or F2FS, do yourself a favor and just stay on 2.8.6.0.

There is nothing to gain for you with 3.0.0.0 except odd behaviour if you check the recent posts.

I am still on 2.8.6.0.6 materialized and it gets the job done without any issues.

To answer your question, yes it does flash the firmware and baseband.
[ONE Original Android Development] Renosh:
Stick to 2.8.6.0 for now I've been having issues switching ROMs with 3.0.0-0 it gives me a status 7 error about incompatible data even though I wiped everything. Some people are reporting it taking 5 mins to wipe some partitions that used to take a 2 seconds. Odd behavior with connecting a USB to transfer files etc.

2.8.6.0 does everything perfectly so keep using it
[ONE Original Android Development] jgcaap:
2.8.6.0 was the best version for bacon and stable. Why don't the devs build a 3.0 based on settings of the past? Is fast reliable...
[ONE Original Android Development] CBpbxEcmecmBeH:
I think because it's build/developed for multiple devices, maybe?
[ONE Original Android Development] x.0ni.x:
Idk what the hell I did but version 3 is working beautifully now!! Damn it's wiping it all faster than any version of TWRP to date!! I'm a happy camper. ?
[ONE Original Android Development] geowolf1000:
Not only

i think boot faster

Backup faster

Restoore faster
[ONE Original Android Development] x.0ni.x:
Haven't done a backup or restore yet but I will soon.
[ONE Original Android Development] jgcaap:
Building for different devices ... sure.. but if there are problems i think it shouldnt be released. I had many users as also myself got into problems because of some of TWRP releases. I know is part of development, but should not ignore the problems which exist.
[ONE Original Android Development] gparmar76:
I think the new version works slower with Android M vs Android L...also, I had to wait several minutes to do a full wipe too...but upon doing a 2nd flash of the current CM13 nightly, it went much faster...not as fast as people were used to but much much faster...if 3.0.0 can flash firmware, I'd say upgrade...can always go back if needed.
[ONE Original Android Development] ThePrutser:
When I do a backup using the new TWRP 3.0.0-0 I get some errors during the backup (see screenshot). Is this something I need to worry about?

Device: OnePlus One
[ONE Original Android Development] Renosh:
Why are there 5 partitions being backed up? Normally its only 3 unless you're using the unofficial one. Last time official TWRP backed up additional partitions on its own it corrupted my EFS partition and I had a horrible time fixing it
[ONE Original Android Development] totom96:
My touchscreen isn't working on TWRP since the 33R update... Anyone who know a solution?
[ONE Original Android Development] ak:
I don't know but I don't have problems.

Can you try to reflash recovery with fastboot?

ak@a0001
[ONE Original Android Development] totom96:
Thanks for your reply.

The reflash didnt help, but I resolved by disabling the theme (even if it was a 1080p theme)
[ONE Original Android Development] Natakranta:
Which theme were you using? I'm using dark theme on my N5 with MultiROM TWRP. It would be pity having to go back to bare TWRP.
[ONE Original Android Development] playya:
fyi - in the future please also provide the fact that you are using a theme or any other thing that would be helpful. Your statement may have made others not want to use this version of TWRP because of alleged screen issues. Jus Sayin' Thx for your support :D
[ONE Original Android Development] Stanlehh:
anyone has a mirror for TWRP 2.7.1.1 besides techeratta as I can't seem to download from that site.

appreciate it!

thanks in advance,

Stan
[ONE Original Android Development] srps:
http://xdaforums.com/attachment.php?attachmentid=2875127&d=1406636747
[ONE Original Android Development] SmokinJohnny:
Cannot mount. Possibly decryption issue.

I have tried TWRP 2.7.1.1 as well as 2.7.0.0 and I am trying to prep for a dirty flash by attempting to wipe cache, system, and dalvik. I was on ART runtime and changed back to Dalvik in case that was that was causing this error, but I believe it is the encryption that is causing this as I need to have the phone encrypted for work emails. Also, there is no prompt for the decrypt code when I get in TWRP like I do when I change the runtime.

When I try, I get errors saying it failed with results below:

E:Unable to mount '/data'

E:Unable to mount storage.

E:Unable to mount /data/media during GUI start up.

Full SELinux support is present.

E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.

E:Unable to mount '/data'

E:Failed to wipe dalvik

Updating partition details...

E:Unable to mount '/data'

E:Unable to mount storage.

E:Unable to mount '/data'

E:Failed to wipe dalvik

Updating partition details...

E:Unable to mount '/data'

E:Unable to mount storage.
[ONE Original Android Development] sjhotwings:
i traded my s4 for the oneplus. it came w/ unlocked bootloader and clockwork installed , but i want to install twrp instead. how to remove clockwork and install twrp ?. help pls

thanks
[ONE Original Android Development] SmokinJohnny:
Easiest way is to download Flashify from marketplace. Pretty straightforward.
[ONE Original Android Development] sjhotwings:
thanks for quick reply, will try now . thanks
[ONE Original Android Development] SmokinJohnny:
Also tried 2.7.1.0 just to be complete and it's the same error.
[ONE Original Android Development] playya:
If you click the paperclip next to the thread name you will probably my find a twrp zip file which you can simply flash in recovery
[ONE Original Android Development] TiVON:
Other recoveries do work?
[ONE Original Android Development] SmokinJohnny:
Tried Philz and same thing. Didn't try CWM yet since Philz is based off that.
[ONE Original Android Development] :
twrp shouldn't be the problem at all, I'm using it since the first day of my one without any problems.

Seems to me that the encryption is causing the trouble or maybe the formatting is corrupt.

At the end flashing back the original system via fastboot could be a solution ...
[ONE Original Android Development] SmokinJohnny:
I'm pretty sure encryption is the issue and that the recoveries I've tried aren't supporting it correctly, even though it does say in the change log for 2.7.0.0 -Add 4.4 decrypt support. So might be a bug. I need encryption for my work email or else I wouldn't be using it. I've tried on stock 33R and it currently doesn't encrypt, just shows the encryption screen, but back button works and nothing is performed. It's a known issue as well. I'll try to dirty flash on my GN2 with TWRP 2.7.2.2 and encryption to see if it mounts on there.

So at least on my GN2, TWRP prompts me for the decrypt password. Too bad it doesn't think it's the right one even though it works during boot up.
[ONE Original Android Development] Euphoria64:
I've experienced a weird error within twrp that appears to be linked to bbs. At seemingly random times when I'm in twrp to flash an update or switch roms, I receive an I/O error that prevents me from doing mostly anything including factory resets, nandroids, and restores. It always points to bbs app data as the problem with this I/O error. Twice now I've lost literally all my data and had to start over. Has anyone come across this before or know if this is a twrp issue or better Battery stats?
[ONE Original Android Development] dinglehoser:
[MENTION=912474]Dees_Troy[/MENTION] Hopefully a new build of TWRP supporting encrypted volumes on bacon is released soon, as I have to encrypt my phone (my IS dept's BYOD policy forces it) and I can't do much of anything in recoveryland until it is. The fix might be simple - see NYZack's and Steve Kondik's comment here: https://jira.cyanogenmod.org/browse/BACON-98:
[ONE Original Android Development] SmokinJohnny:
I'm in the same boat with encryption.
[ONE Original Android Development] ThePrutser:
I downloaded and installed the official one... and during backup I can select 4 partitions, which were automatically selected for me.
[ONE Original Android Development] Renosh:
That looks normal but there is a fifth partition being backed up, that's odd.
[ONE Original Android Development] ThePrutser:
Maybe both things I mentioned are bugs of some kind? No clue how to troubleshoot though...
[ONE Original Android Development] rocketjump:
Encryption support doesn't work for latest CM13. Guys, is it known bug or should I post it to TWRP? Thanks

UPDATED: "TWRP version 3.0.0.0 can now be found on the official site, and it also seems to work in a decent way but full disk encryption in Cyanogenmod 13 is still broken in every build after 29 January 2016"
[ONE Original Android Development] Hzu:
Is there a new secure deletion algorithm implemented in TWRP 3.0 or what? I just want to quickly format my phone, not securely erasing every single file on it.

If there is, there should be an option to change between those format modes.

Ps. I've been waiting for my /system partition to be formatted from 11:04 to 11:16 now. That's a new record!
[ONE Original Android Development] chenrp:
Quote:

Originally Posted by Charlieckips

Formatting /cache as ext4 takes forever ... it's not working... wiping dalvik & cache normally takes a few seconds but that's not the case with 3.0

got the same issue.

using twrp 3.0 and clear cache takes 4ever!
[ONE Original Android Development] sabrefresco:
For me the cache doesn't really wipe with 3.0, maybe I wasn't patient enough. I usually just fasboot and clear it on my own if I am being paranoid. Unfortunately, I am stuck with it, because 2.8.6.0 doesn't seem to be able to decrypt my phone's storage. :mad:
[ONE Original Android Development] w0rinal:
Same here. It even froze once (no animation, no vibration) so I hard shutdown my phone, booted back into recovery and tried to wipe /cache again but it couldn't be mounted, So I downgraded to 2.8.6.0, wiped/formated cache and everything went well.

Wiping cache when being formated f2fs works flawlessly and super fast.

Wiping /system (ext4) appears to work fine
[ONE Original Android Development] :
TWRP Bacon update: https://dl.twrp.me/bacon/twrp-3.0.0-1-bacon.img

Change log: any idea where to find?
[ONE Original Android Development] Striatum_bdr:
Had problem with wiping /system, was stuck forever, cache went well and fast.

Had to reboot in recovery, repair the system partition that was unmountable.

Didn't try to wipe again i flashed directly my Rom.

I just flashed the new version 0-1 of twrp, let's see if it improves that, else I'll stay on rm -rf instead of formatting.

Envoyé de mon Oneplus One en utilisant Tapatalk
[ONE Original Android Development] anthony.wang:
Just flashed version 3.0.0-1 and when I rebooted into TWRP, it still shows up as version 3.0.0-0. I haven't tried to test any functions (especially the cache/Dalvik wiping), but at least it boots up.
[ONE Original Android Development] Renosh:
These should be the latest changes.

https://gerrit.omnirom.org/#/q/project:android_bootable_recovery

Everything works on 3.0.0-1

No issues wiping, restoring backups made by TWRP 2.8.6.0 and its faster with backups.

Highly recommend
[ONE Original Android Development] wbagdon:
Here is the merged changes

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

Can confirm wiping/mounting cache is also working in 3.0.0-1
[ONE Original Android Development] fmc000:
[MENTION=4021423]ketut.kumajaya[/MENTION]
[ONE Original Android Development] drsiddique5700:
tried but there is no files in my internal storage also seen by different file manager.btw i am running stock cyanogen os 12.1 rooted
[ONE Original Android Development] zertyuiop:
Whether the latest version (3.0.0.1) flash radio images correctly?
[ONE Original Android Development] ThePrutser:
I flashed the 3.0.0-1 but the recovery still shows it as 3.0.0-0. Flashed the recovery multiple times using different methods, but the version stays the same. Maybe the version number wasn't updated in 3.0.0-1? :silly:
[ONE Original Android Development] djuliusl:
How about EFS partition? Is it successfully backed up and restored?
[ONE Original Android Development] Renosh:
The official TWRP has never backed up the EFS partition for Bacon. You're probably on Kumajaya's unofficial builds which are the ones which have that. Go check his thread if he's made a 3.0.0-1 build
[ONE Original Android Development] danieldmm:
Why according to the TWRP gerrit and device specific files we don't see no changes? The changes should not be pushed to official twrp github and device specific tree and then build from there?

And [MENTION=5972963]Renosh[/MENTION] spare me your answers and comments...

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Renosh:
I'll answer you one last time since you mentioned me. The devs don't have our device they mentioned this, they are only a few people with few devices. Use some common sense
[ONE Original Android Development] itechy:
My TWRP isn't updating to the -1 version. Tried the app... flashing the image via recovery and erasing and reflashing via fastboot
[ONE Original Android Development] wbagdon:
The version text doesn't display properly (still says 3.0.0-0), but if you can mount/wipe the cache partition you should be updated
[ONE Original Android Development] lou2s:
Just tried a nand backup, it takes more than double of the time 2.8.6.0 used. (13x sec b4 vs 282sec now...)
[ONE Original Android Development] DoppelgängerGER:
Is it possible to use TWRP Holofied in future for this version?
[ONE Original Android Development] sephk:
what do you mean it is broken? Can you please explain? Also, are you able to decrypt using 3.0 now? I am CM13 02-26 build and cant decrypt in TWRP 3.0.0.1 after inputting the right pattern. Thanks
[ONE Original Android Development] Pietia10:
I can't decrytpt either in 3.0.0.1 on cm13 I tried versions below and same bug here is the bug report I think:

https://github.com/TeamWin/Team-Win-Recovery-Project/issues/588
[ONE Original Android Development] EchoDevv:
Yep can confirm decrypting is broken for me too. I enter my password but it just gives an error (Failed to decrypt).

2.8.7.0 worked fine with CM12.1 but is broken for CM13

3.0.0.0 is broken for CM13 (Didn't test CM12.1)
[ONE Original Android Development] nachomagic:
Hi mates, how are you?

First of all THANKS [MENTION=912474]Dees_Troy[/MENTION] for TWRP, I love it

I use to wipe dalvik/chache and you know, you have to go advanced wipe because by default is factory reset.

I wonder if there is a way to change the default wipe, not only to avoid go to adcanced, is to avoid an accident with the default

Specially now that you have a button to format in the main wipe page.

thanks in advance
[ONE Original Android Development] sephk:
I found a way out. Changed the screenlock to pin instead of pattern and that worked with twrp
[ONE Original Android Development] Pietia10:
For me and echodev it didn't worked.
[ONE Original Android Development] EchoDevv:
Yeah pin is dead for me. Tho I should note my lockscreen PIN and encryption PIN are not the same for me, dunno if TWRP can handle that.
[ONE Original Android Development] sephk:
I took a roundabout way to get to this point.

1. First tried resetting the password running the following command in the terminal "vdc cryptfs changepw password newpwd" - here I entered the numeric equivalent of my current pattern as the newpwd

2. After rebooting TWRP asked me for a password instead of pattern.... but it didn't take my numeric equivalent

3. Rebooted to android and removed the lock screen completely and rebooted to recovery. TWRP still asked for password and nothing worked (including default_password)

4. Rebooted to android and changed the lockscreen to pin and disabled secure startup

5. Rebooted to recovery and TWRP took the pin and decrypted
[ONE Original Android Development] rocketjump:
Yes, it asked pattern but couldn't decrypt partition with correct one.

Right now I have returned to good old CM 12.1
[ONE Original Android Development] notanapple:
I have updated to twrp 3.0.0-1 yesterday from materialised twrp 2.8.7.0.5 but I had to come back to materialised cause I had a problem in backup and restore...it said that the recovery was unable to prepare /modem partition to backup (something like this..). Restoring a backup caused in bootloop...i solved flashing back materialised twrp and restoring an older backup...after that i tried to take a nandroid backup with materialised and worked like a charm....do someone has the same problem and how to solve? Thank u!
[ONE Original Android Development] fazreen:
Hey guys, i ran into same sh**storm several days ago when i encrypt my phone. Using sultanxda cm13 7 february build, encryption is flawlessly good. But when i reboot in twrp, i cant decrypt. What i did few days ago is to change password using command, try several different method but still the decryption is a failure untill this morning. I format the data in recovery, after that boot into the system. Encrypt without any lockscreen. After successfull encryption, i set pin and enable safe boot. Reboot to twrp and boom! Decrypt success. Forget to mention that my recovery is 3.0.0.1. All the best, cheers.
[ONE Original Android Development] fmc000:
Materialized versions can backup the firmware and imei partitions. If you select them it will be written in the .twrps file. When you go back to standard twrp, which lacks these two features, you use the same .twrps file which now contains entries that generate the errors you're seeing.

Solution: delete the file and start twrp again.

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

What do you mean with "encrypt without any lockscreen" ? You have to at least set a pin to encrypt your phone. Maybe you meant "encrypt without any lockscreen pattern" ?
[ONE Original Android Development] fazreen:
No pin request at the initial encryption process. Quite positive about it. I set the pin after the encryption done.
[ONE Original Android Development] fmc000:
Every customization you may have made, timezone, vibratory intensity, display timeout and so on. And, of course, the partitions to backup.
[ONE Original Android Development] EchoDevv:
Maybe he used adb shell/terminal to directly input the encryption command (vdc cryptfs etc.)
[ONE Original Android Development] frogger55:
Hi,

I have a conundrum - I have the current release (flashed with flashify ), 3.0.0-1. When first installed it looked fine, but the interface now is not material it's the pre 3.x look.

I haven't done anything I'm aware of that would make this happen. The version is still recognised at the top of the recovery screen as 3.0. I am currently running fusionjack's omni slimsaber.

Any ideas how this happened, or how I can fix?

Cheers,
[ONE Original Android Development] JT1510365:
All Twrp v3.0.0.0 versions are broken and they break my phone. It stays stuck on rebooting recovery so thanks a lot devs for nothing:(

edit: Disregard that previous comment seems like my phone is not downloading the full size of the recovery file thus resulting in stuck on booting to recovery i am sick of this phone having so many issues:(
[ONE Original Android Development] notanapple:
Sorry for my ignorance but where is located .warp file?
[ONE Original Android Development] fmc000:
<internal memory>/TWRP

The filename is .twrps (not .warp)
[ONE Original Android Development] notanapple:
Thank you very much...very helpful!

---------- Post added at 03:26 PM ---------- Previous post was at 02:59 PM ----------

@fmc000 me and my friends have had problems making different warp version read partitions correctly...flashing or backing up/restore were compromised... Would you suggest to delete the .twrps file everytime when updating/downgrading/changing twrp recoveries? Thank you in advance!
[ONE Original Android Development] fmc000:
You should delete the .twrps file every time you move from official version to unofficial versions and back. It shouldn't be necessary removing the file when upgrading official to official (but it won't hurt, it's just a minute of work to reset your own customizations).
[ONE Original Android Development] salomaoa:
Sorry for the noob question but I am lost here and don't know what to do.

I wanto to clean flash my current custom ROM (Darkobas) but would like to wipe everything (I mean all, including SD card, and not only the usual factory reset).

However, if I set TWRP to wipe everything, I will lose my ROM zip file and Gapps, right?

If so, how can I install the ROM if my SD caerd is completely wiped?

Any help will be apreciated.

Salomao
[ONE Original Android Development] SimonTS:
ADB...
[ONE Original Android Development] finistere:
That should probably read more like "fastboot flash $partition $partition.img", don't you think?

Salomaoa, go to your vendor's website, grab a factory image and flash that with the tool at hand. For the Nexus phones Google supplies a shell/batch script that does everything for you via fastboot.