yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] indian84:
Let me explain you better,

Clean wipe means wipe everything except internal storage. If you want to wipe internal storage, you will loose the downloaded ROM and GApps.

If you do clean wipe including internal data, you can connect reboot in TWRP and connect your phone to your PC, It will be detected as storage. Copy ROM and GApps and you can flash.
[ONE Original Android Development] VercettyEdits:
AROMA is not working on the latest version TWRP 3.0.0-1 for me, maybe its just my device.... :confused:
[ONE Original Android Development] btrex_07:
:o:o:othanks:D:D:D:good::good::good:
[ONE Original Android Development] kanyazsombor:
Flash drive through usb otg cable. Or there are flash drives with micro usb interface also. TWRP can handle it

1+1 DirtyUnicorns M + LightningKernel (cm)
[ONE Original Android Development] kvaju:
or Google sideload adb, and flash that way.

---------- Post added at 09:02 PM ---------- Previous post was at 08:56 PM ----------

since i use bacon, on most threads all developers reccomended 2860, now im trying darkobas, and on op of his page, says dont use 2860, so is there any newer version that i can use and dont have to thing about firmwares not flashing properly?
[ONE Original Android Development] ReVo_007:
Did the bug regarding modem flash get fixed on this new release ?
[ONE Original Android Development] TonySuperPony:
Did you try to read the last posts of this thread?
[ONE Original Android Development] ReVo_007:
Obviously not and rather than being so smart you could have just answered me. I did go through last 2 or 3 pages didn't find anything related to modem, all were relating to lock and cm13 or 12. Now if you would like me to keep going through 144 pages on my phone then thank you for the help. And a simple search on the thread didn't return any results for modem so I asked if anyone has tried or not.
[ONE Original Android Development] TonySuperPony:
You have to excuse me, I thought this was anothet thread (from the unofficial builds).

Everything should be working in the last version (3.0.0-1)
[ONE Original Android Development] Renosh:
Yes it's fixed everything works on 3.0.0-1 [emoji4]
[ONE Original Android Development] ReVo_007:
Thank you and sorry for posting like that. I do look around as much as I can before posting hence. Anyway kudos and thanks. Time to upgrade :)
[ONE Original Android Development] nsmart:
In case anyone is interested in device encryption with current cm13 snapshot:

I clean flashed cm-13.0-20160316-SNAPSHOT-ZNH0EAO1QB-bacon.zip with open gapps micro with twrp 3.0.0-1 and enabled device encryption (using a pin). Device encryption itself is working, but twrp is unable do decrypt data partition.

I did not play with different modems, so baseband was DI.3.0.c6-00241.
[ONE Original Android Development] EchoDevv:
TWRP devs are aware of the decryption issue with CM13. They said the problems will be fixed in the next TWRP build but they didn't give an ETA for when it will be out.
[ONE Original Android Development] pbeckmann:
I encrypted the phone with pin. Then i changed the pin with, after that decyrption worked und er TWRP 3.0.0-1.
[ONE Original Android Development] Boia11:
TWRP 3.0.0-1 decrypt with CM13 not work
[ONE Original Android Development] pbeckmann:
It dies just set your password/pin again.
[ONE Original Android Development] Gold Ribbed:
I do not seem to be able to upgrade from 3.0.0-0to 3.0.0-1. I have tried using TWRP, the TWRP app and flashing. The app says unsuccessful and within TWRP installed but my version remain at 3.0.0-0. Any ideas what the issue could be please?
[ONE Original Android Development] bombadier:
Look in /cache/recovery and get the logs, have you tried fastboot ?
[ONE Original Android Development] Gold Ribbed:
What am I looking for in the logs?

Any reference to TWRP is 3..0.0-0
[ONE Original Android Development] bombadier:
Someone else can confirm but I am sure that 3.0.0.1 just shows 3.0.0.0

Edit I have just flashed twrp-2.8.7.0.7-bacon-materialised then rebooted and flashed twrp-3.0.0-1-bacon.img, recovery shows version as 3.0.0.0 but has been updated
[ONE Original Android Development] pbeckmann:
It's a bug in the twrp version. The string wasn't updated.
[ONE Original Android Development] ORUAM:
GOOD AFTERNOON

I try to install the rom 2.0 oion but twr the following error message: Process Updater ended with error: 7

Error Installing archivo.zip

sialguien know how to fix it I would appreciate .
[ONE Original Android Development] kewinhdorff:
hey i just flashed the cm13 snapshot and it is running super good :)

I'm currently using twrp 2.8.6.0 and i just saw that the twrp was updated to 3.0.0.1

is twrp 3.0.0.1 better than 2.8.6.0 or should i stay with 2.8.6.0 ? ^^
[ONE Original Android Development] Pietia10:
Guys bump this regarding encryption on our oneplus devices maybe devs will take a closer look at this;

https://github.com/TeamWin/android_device_oneplus_bacon/issues/10
[ONE Original Android Development] danieldmm:
Still a mess this encryption thing, latest comment say did not worked.

"Pin decryption in twrp doesn't works for me I just flashed latest cm 13 from 31/03/2016 and TWRP 3.0.0-1."
[ONE Original Android Development] Pietia10:
Yeah thats why we have to bump this topic and confirm that it isnt working so developers will take a look at this I suposse ...
[ONE Original Android Development] danieldmm:
They are aware for this problem. Don't think they are not but they did not managed yet a fix for cm13 although did read something that in a future update it will be fixed.
[ONE Original Android Development] danieldmm:
Anyone tested encryption with TWRP 3.0.1-0 and CM13 lattest nightly ?
[ONE Original Android Development] sToRm1nG:
Encryption works with 3.0.0-1 (Sultanxda's Stable CM13) but does not with 3.0.1-0.

This seem to be a general issue. My Nexus 6P (Pure Nexus ROM) and HTC One M7 (CM12.1) have the same issue.
[ONE Original Android Development] kewinhdorff:
does the baseband/modem firmware flashing work in 3.0.1-0 ?

it was broken in 2.8.7.0 right ? is it fixed now in the latest ?
[ONE Original Android Development] sToRm1nG:
It was already fixed in 3.0.0-1. Do not use 3.0.1-0 because of the encryption issues.
[ONE Original Android Development] kewinhdorff:
so i should revert to 3.0.0-1 ? i don't encrypt my phone anyways hehe. well i do use signal and protonmail but they aren't affected by the recovery.

and one more thing. i just noticed the new system read only setting hehe. since i didn't use the 2.8.7.0 version. what was the default setting in 2.8.6.0 ? cus when i installed the 3.0.1-0 version i slided to let the system to be modified.
[ONE Original Android Development] sToRm1nG:
I would stick with 3.0.0-1 just for now. I am sure Dees_Troy and the TWRP team will do their best to fix this.

Not sure regarding the read-only setting. When using a custom ROM you would want your system partition to be RW as you most likely want to flash GApps.
[ONE Original Android Development] kewinhdorff:
okay, thank you :)
[ONE Original Android Development] silvagroup:
Thought i'd try new version....Couldn't flash anything successfully. Spend hours messing with firmware, sims, gapps packages. Tried CM and asop stock based ROMs on my one plus one.

Finally reverted back to 2.8.6.0 and things started working again.

P.S.

After got the ROM all set up with 2.8.6.0 and working went back and flashed 3.0.1.0.

ROM working fine so far. See an update for ROM is up will venture to see how it flashes with 3.0.1.0..
[ONE Original Android Development] kewinhdorff:
when u first installed the 3.0.1-0 did u swipe to let system be modified or did u out it to read only ? maybe that has something to do with it?
[ONE Original Android Development] Don Kingkong:
Soooooo which should I pick, the unofficial one from ketutkumajaya or the official one?
[ONE Original Android Development] silvagroup:
No I let it modify.

Only have one system with unmodified twrp 3.0.1.0 so can't test the other option. Once I get the wife's phone working again can't touch it for a long time !!!!! And mines using multirom not on current twrp yet.
[ONE Original Android Development] iamelton:
flashed v3.0.2-0 and did a recovery backup without issue..
[ONE Original Android Development] danieldmm:
The big question. Is encryption working on latest nightly CM13 on the 3.0.2-0 ? Anyone tested?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] pbeckmann:
I was able to successful decrypt cm13 hacked by SultanXDA... But it was just a short reboot and I'm using pin, not pattern.

Hope that was helpful :)
[ONE Original Android Development] Pietia10:
Latest cm13 nightly twrp 3.0.2-0 pin and pattern still doesn't works.
[ONE Original Android Development] TonySuperPony:
Have you tried changing the pin?
[ONE Original Android Development] Pietia10:
yes
[ONE Original Android Development] Gobbenobber:
Everything seems to work here with 3.0.2 build; only thing I experienced was that flashing the IMG through 3.0.1 didn't work and softbricked the recovery, but a fastboot flash of the same exact file totally worked. :) !

ETA: Not using pattern encryption so I can't vouch for that!!
[ONE Original Android Development] Pietia10:
Are you sure you are using original cm13 nightlys? or some other custom rom ?
[ONE Original Android Development] Gobbenobber:
Hey :).

I haven't been on the official CM13 for some time - actually, I'm on an AOSP build ATM.

I'm sorry if this confused anyone. :o

Just wanted to give my feedback on the latest build... :)
[ONE Original Android Development] counterfeit187:
Flashing image worked fine for me, but updating from 3.0.0.1
[ONE Original Android Development] riazsgs2:
Is the new version slow?

On 3.0.2. Backup and restore takes forever.. 3.0.0 -1 was very fast

Took 822 secons to restore backup of 4gb
[ONE Original Android Development] fmc000:
Haven't tried a restore but it took me 680 sec to backup 3.4 GB on a very old USB-OTG pendrive. That doesn't look slow to me.
[ONE Original Android Development] mejack03:
twrp cant decrypt COS13 and soft bricks the phone

I have installed twrp 3.0.2.0 recently i updated my OPO to official COS13. When i reboot phone into recovery i get wrong pattern error. Once i click on reboot system phone reboots and stucks at the cyanogenmod MOD ready screen.
[ONE Original Android Development] chenrp:
same issue here!
[ONE Original Android Development] idefix3500:
Reverted my Oneplus One to completely stock COS 12.1 and updated to COS 13. To be sure did factory reset.

Encrypted device from within COS 13 and set a pattern lock. Everything playing nice!

Installed TWRP 3.0.2 but unable to decrypt device using TWRP (no problem booting OS). Even did another complete reset and set a pin lockscreen, but still unable to decrypt using TWRP 3.0.2.

Anybody else having any luck with above versions?
[ONE Original Android Development] Szambodi:
I'm running MM and want to make a baxkup. Whats the difference between backing up "System" and "System image"? Is at also possible to restore backups of LP and MM on the same phone?
[ONE Original Android Development] :
I can't decrypt my phone in TWRP i tried many versions and tried all passwords associated with decrypting and unlocking my phone to no avail. my rom: http://xdaforums.com/oneplus-one/development/rom-cm-12-builds-t3045053 the only thing that works was a unofficial version but it wouldn't mount the /data
[ONE Original Android Development] chenrp:
I have installed twrp 3.0.2.0 recently i updated my OPO to official COS13. When i reboot phone into recovery i get wrong pattern error. Once i click on reboot system phone reboots and stucks at the cyanogenmod MOD ready screen.

same issue here!
[ONE Original Android Development] kewinhdorff:
hey everyone :)

with the encryption option within TWRP and in the rom itself does it make it double encrypted? i know that if you encrypt within the rom itself u need to type in the right password/pattern to get into the phone at boot. (i haven't tried this but i might do some day) but what does the encryption option in TWRP do :eek: ? and how does it work and what is it made for ^^thnks
[ONE Original Android Development] z31s1g:
The option will encrypt the file that is the backup of the data partition.
[ONE Original Android Development] kewinhdorff:
okey :) im just trying to figure out how these thing work hehe. so the encyption in the rom just encrypts it so no one with the right password can enter the phone on boot? how does it work when i have decrypted it after a boot? then some one can access everything right?

and the twrp data encryption encrypts the data partition so if some one would steal my phone and try to get the data from it can't do it? did i understand what meant?

also will i be unable to change my lockscreen password if i want to or even enable swipe to unlock after encrypting my phone ?
[ONE Original Android Development] danieldmm:
No, TWRP only encrypts the backup file if you choose to encrypt. Nothing more.

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] kewinhdorff:
okay thanks :)
[ONE Original Android Development] tofu:
I'd like to report that I cannot decrypt Sultan's CM13 rom with twrp 3.0.2. Any fix in the near future?

EDIT: Actually it is impossible with all the versions of twrp since 2.8.7.0
[ONE Original Android Development] klubipiff:
Hi,

I cant restore any backups as it says system is read only. What to do?
[ONE Original Android Development] z31s1g:
In TWRP go to "Mount" and uncheck "Mount system read-only".
[ONE Original Android Development] anthony.wang:
Hey, could you please clarify if you mean that v2.8.7.0 CAN decrypt Sultan's CM13 rom? And are you using the official v2.8.7.0 or a materialised version, or something else?

Thank you!
[ONE Original Android Development] tofu:
2.8.7.0 doesn't work.

However, on darkobas 3.0.2 works (haven't tried other twrp versions)
[ONE Original Android Development] hammer-is:
Just did a backup (to /media/data) and then tried a restore. The restore took 800+ seconds (can't remember the exact number but it was between 800 and 900). Reverted to twrp-2.8.6.0.6-bacon-materialised and tried restoring the same backup. This time it only took 202 seconds so 3.0.2 was 4 times slower!
[ONE Original Android Development] pbeckmann:
But the question should also be, is faster better? Cause if the restore is more buggy on 2.8.6, I would rather wait more than be unsure If the restore was incorrect
[ONE Original Android Development] Gawd:
I just flashed sultanxda's ROM with TWRP 3.0.0-0 and it just did fine!
[ONE Original Android Development] djha53k:
And do you have crypted filesystems?
[ONE Original Android Development] pbeckmann:
That is a bit problematic. Some people can decrypt the data partition with twrp some not. But flashing via adb sideload always worked for me. Even with twrp 3.0.2.
[ONE Original Android Development] Gawd:
No.
[ONE Original Android Development] tofu:
Looool

"Decryption with twrp doesn't work"

'My twrp works'

"Are you encrypted?"

'No'

....
[ONE Original Android Development] :
u left something as this didn't came out as joke or brief narration
[ONE Original Android Development] jcustodio:
Hi

Can I use TWRP 3.0.2-2 to flash OxygenOS 2.1.4 over a OxygenOS 1.0 without losing my radio and modem?

Thanks
[ONE Original Android Development] kewinhdorff:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/

i would follow this :)

---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------

hey im using the latest 3.0.2-0 version of twrp

and i was jsut wondering if it works to encrypt my phone from within sultan xda cm 12.1 rom. i read some earlier posts but i dont quite understand if they meant the data encrytion or the encryption made inside the rom :). so my questions does it work to encrypt sultanxda rom 12.1 and 13.0 with twrp and does it decrypt correctly :) thanks
[ONE Original Android Development] nolsen311:
Great question!

Does full disk encryption work on cm13 derivatives yet? I don't want to go through another unnecessary wipe.
[ONE Original Android Development] danielferratti:
Maybe it is a dumb question... or simply a wrong placed question but anyways...

I can't use Aroma Open Gapps with TWRP 3.0.2.. It worked some versions before (I can't confirm the one, maybe 2.8.4?).

Any ideas if in the near future we will have this option again? For now it only freezes TWRP.

Thanks!
[ONE Original Android Development] danieldmm:
Long time this is broken mate...

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] tofu:
This guy says that this issue has been fixed, but not yet released. So he made an unofficial build. See here: http://xdaforums.com/showpost.php?p=66681410&postcount=13691

I haven't tried it though, but if you will, let us know if it works.
[ONE Original Android Development] mammenj:
Wrong thread, deleted.
[ONE Original Android Development] EchoDevv:
People are reporting this version of TWRP works fine with an encrypted Oneplus One and CM13.

https://www.androidfilehost.com/?fid=24521665358595401

Taken from here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/596#issuecomment-215315628
[ONE Original Android Development] NetDwarf:
Ok, found the bug regarding FDE. If your password only consists of 0-9a-fA-F it will be decrypted. If your password has for example a "G" in it, it won't decrypt with TWRP it seems. Passwords are ofc decrypted fine on the OS side (CM13 encrypted with cryptfs).

Also note, that this seems to be an input limitation of TWRP and not just a conversion from hexadecimal input, because decryption works for example for a password like "abcdef" and it is also case sensitive, so decryption with input "ABCDEF" won't work for this password.
[ONE Original Android Development] Sun Shower:
Thanks, does the latest version 3.0.2.0 support to backup EFS ?
[ONE Original Android Development] wollah_91:
I've got backup problems with the TWRP 3.0.x

it can't find multiple objects like; canot find modem_st etc.

Restoring a backup also goed wrong.

Im back on 2.7.8.0 now

Does anyone got any ideas?
[ONE Original Android Development] fmc000:
You went from an unofficial version to the official one I suppose. If this is the case you have to delete the .twrps file.
[ONE Original Android Development] wollah_91:
Thank you for the reply.

Im sorry but where can i find that file?

thanks in advance

Edit: found the location but no .twrps file.

Will keep looking for a solution, thanks!
[ONE Original Android Development] fmc000:
sd card\TWRP
[ONE Original Android Development] as9333:
Does this recovery work with cm12 .0-YNG1TAS213 (unrooted)

Or should i flash the old recovery
[ONE Original Android Development] wollah_91:
solved

i solved my problem by doing the following:

1. flash the latest twrp 3.0.2.0

2. try backup - failed

3. went to settings

4. tapped 'use default settings'

5. tried backup again - no errors

6. fixed!

Hope this help someone.
[ONE Original Android Development] fmc000:
More or less it's the same than removing the .twrps file (where the configuration is stored).
[ONE Original Android Development] chaoscreater:
Does the latest TWRP (whether official or unofficial) back up these partitions? Backing up modemst1 and modemst2 isn't enough. This post says it all:

https://forums.oneplus.net/threads/anyone-successful-in-backup-the-efs-imei.91986/page-2

I'm using the unofficial one and while it does offer EFS and persist partitions backup, I don't think it backups all of those 10 partitions mentioned above. Looking at the recovery log, partitions oppodycnvbk, modemst1 and modemst2 are backed up, but oppostanvbk and the rest aren't. I know this isn't the unofficial TWRP thread but EFS/IMEI is so important and I have seen so many posts about recovering it. Just wondering if this is to be implemented or whether there is a reason why it's not? I've used official TWRP 3.0.2.0 for other devices and they provide EFS backup.
[ONE Original Android Development] danieldmm:
Modemst1 and Modemst2 are the only partition needed to backup EFS on OPO, at least it was... Don't think they changed that.
[ONE Original Android Development] chaoscreater:
Don't think that's enough. My OPO lost the EFS partitions and I've made no backups. Someone on XDA posted their modemst1.bin and modemst2.bin files which I flashed, no IMEI. Tried with another set of files that another person gave me, still no IMEI. I've tried a lot of things already, including using the qualcomm msm tool, flashing colourOS and oxygenOS etc. This leads me to strongly believe that you need to restore partitions oppodycnvbk and oppostanvbk as well. This falls in line with the following post below, as well as the posts in my previous reply:

https://forums.oneplus.net/threads/partition-info-and-dd-backup.49114/page-2#post-11417267

In fact, I have read several guides that suggest deleting the modemst1 and modemst2 partitions (fastboot erase modemst1 and modemst2). I have done that and it makes no difference. Here's one of the guides:

http://xdaforums.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Read the bottom of the first post.

There's also this post here:

http://xdaforums.com/showpost.php?p=55543630&postcount=23

"modemst1/2 is NOT the EFS, those are some kind of temp or buffer partitions, present on the Note 3 as well, you can format them, nothing bad happens, they will get regenerated, but if those are corrupt (happened on Note 3), no more IMEI and constant FCs and reboots (on the Note 3)."

This is why some people without any EFS partition, were able to recover their IMEI by flashing ColorOS/OxygenOS or whatever. This never worked for me though. From my personal experience, restoring modemst1 and modemst2 from someone else's backup will not restore their IMEI onto my phone. My IMEI will show as 00 instead.
[ONE Original Android Development] Anghirrim:
oppostanvbk is a part of the officials fastboot COS images.

I don't think this contains anything IMEI related.

What is oppodycnvbk?
[ONE Original Android Development] Timmmmaaahh!:
Hi! I hope this is the right place to post in as I'm running TWRP TugaPower-3.0.2-1 on Bacon.

I sometimes get to see abnormal percentage and transfer numbers (see image attached), stating something like 7211141375271MB of 6740MB, 2147483647% I'm pretty sure it's not copying 7TB but it does have me worried if backup is running as it should in that case.

Backing up to a brand new OTG drive (SanDisk Ultra 64GB) while seeing these abnormal numbers caused my OnePlus One to reboot upon (or nearing) completion. I've now reset settings (cheers [MENTION=6231173]hosseltietjes1990[/MENTION] , leuke naam btw) and backup ran as expected. Anyone else experienced this?
[ONE Original Android Development] danieldmm:
It's not the right place, my recoverys are posted on the unnonficial thread. The answer to your problem it's to updated the TWRP to my lattest build. TugaPower-3.0.2-3

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Timmmmaaahh!:
Cheers for replying nonetheless! I looked for "TugaPower" and seemed to find nothing but ROM threads. Found the right one now via your profile, will follow that one instead. Sorry to bother! :)
[ONE Original Android Development] Anupam Mahato:
yes it's working..tried latest SUPERSU 2.74

---------- Post added at 07:45 PM ---------- Previous post was at 07:42 PM ----------

Hav anyone facing issue in USB-OTG detection on latest TWRP 3.0.2.0??
[ONE Original Android Development] danieldmm:
If you toggle the mtp on twrp and it's connected to Pc? It detects?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Anupam Mahato:
No i havn't tried it buddy..!!