yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] juvezavala:
Hey everyone! Looks like decryption and mounting /data isn't working again. I'm on the latest CyanogenOS build, SU'd and running TWRP 3.0.2-0 but can't seem to decrypt and mount /data. The only recent change I can think of on my setup is allowing that new Google 2 factor "Google Prompt" feature to run on my A0001. Thanks!

Edit: Nevermind, I already asked Dees about this one before on Google+. I forgot: Go under Lock Screen Settings and make sure you check "Require X to start device". Hope it helps someone.
[ONE Original Android Development] speakxj7:
hrm. i'm on a cm13 nightly from the last week or so and twrp 3.0.2 and i require my pattern to start. decrypting still fails.

will read back through the thread for clues.
[ONE Original Android Development] Signor Rossi:
Hi, I restored a Nandroid Backup and now my PIN is no longer accepted. Any ides ?
[ONE Original Android Development] danieldmm:
It depends the baseband you have prior to restore. Maybe you need different baseband firmware.

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Signor Rossi:
Same Baseband
[ONE Original Android Development] danieldmm:
You are saying your pin it's not accepted or SIM card not detected?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Signor Rossi:
To give everyone some more background.

I did a Nandroid backup using TWRP Official.

By mistake I did a Factory reset, when I wanted to do a wipe cache/Dalivk.

Did boot up and realized I did the wrong wipe.

Booted into TWRP and restored the Nandroid Backup.

Booted into CM and realized CM is not accepting my PIN (SIM Card is not detected)
[ONE Original Android Development] danieldmm:
Re-flash full cm rom, check if sim card it's working, then try restoring only the data backup partition.

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Signor Rossi:
Thanks, I did something similar.

Full wipe, flashed CM + root + gapps and restored from Titanium Backup.

Gesendet von meinem OnePlus 3
[ONE Original Android Development] danieldmm:
And SIM Card is detected?

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] Signor Rossi:
Yes, I believe I know where this is coming from.

When I first switched from stock to CM I did not wipe system.

I believe, because of that, I only had to type in the system PIN after the SIM PIN has been entered,like it is in Stock.

Now after a wipe of system, CM stops booting asks for the System PIN and keeps on booting once it's entered. Then the launcher starts and asks for the system PIN. Like normal in encrypted CM.

I believe, that because of the moment when I enter the PIN something got corrupted when doing the Backup.

Hope this makes sense?

Gesendet von meinem OnePlus 3
[ONE Original Android Development] Stephen:
Moderator Information,

Thread cleaned, please keep posts on topic regarding this thread only.
[ONE Original Android Development] fmc000:
Why? You can't read, as you don't even know which forum you have to go for your device, so every hint would be pointless.

Inviato dal mio A0001 utilizzando Tapatalk
[ONE Original Android Development] tyoeinstein:
Sorry bro, , i am a newbie, maybe , you are have twrp for my device, but if dont have is okay, forgive me for my mistake ,, wrong quoted to forum device,, peace bro:fingers-crossed:
[ONE Original Android Development] tropicanapure:
Found via Google (search term "Nokia x2 twrp recovery")

http://xdaforums.com/showthread.php?t=3111434
[ONE Original Android Development] tyoeinstein:
Thanks ,, bro,,
[ONE Original Android Development] phenom69:
Hey guys I have a problem, I'm using rooted LG G3 d851 and when I tried to reboot to recovery, it stays stuck on the TWRP logo screen and doesn't open recovery. I tried reflashing recovery but it's the same results. Any help or tips? Thanks.
[ONE Original Android Development] unavix:
This is a recovery for OnePlus One!

Touch 1+1
[ONE Original Android Development] Anupam Mahato:
How to fix OTG Not detecting problem on TWRP 3.0.2.0??? I am not able to mount the otg also..

Any fix..???
[ONE Original Android Development] fmc000:
Works fine here. Please be sure to plug the OTG drive after TWRP has successfully booted, otherwise it won't be recognized.
[ONE Original Android Development] Formhault:
You're in the wrong thread. You should join the discussion here.
[ONE Original Android Development] suaverc118:
Is there a way to make backups that don't take a lot of space? Also my last nandroids took 15 minutes to restore. Any tips would be appreciated
[ONE Original Android Development] SimonTS:
No there isn't, and deal with the time taken - it's a lot of data.

If you can't spare the time then stop wasting your time flashing ROMs
[ONE Original Android Development] AZGeek:
Unable to read USB-OTG

Twrp 3.0.0-0 does not recognize 128gb USB OTG drive. I have toggled MTP without success. TWRP file manager reads /sdcard/usbStorage/sda1 as empty. CM13 file manager reads device ok. I have already reformatted device to fat32.
[ONE Original Android Development] fmc000:
Be sure to attach your OTG after your device has finished booting.
[ONE Original Android Development] AZGeek:
Thank you. That solved my problem.
[ONE Original Android Development] VSPAIRTEL:
TWRP 3.0.2 recovery will work for samsung GT-I8262?

plz tell
[ONE Original Android Development] Lupin The Third:
This is for another phone. You can't use this!!! Keep your device as it is, it's better in your case.
[ONE Original Android Development] 290u4we:
MTP does not work in 3.0.2.0

...or the five versions before that. Everything works as it should in the main OS, what's wrong with TWRP?
[ONE Original Android Development] counterfeit187:
Why no more updates for OnePlus One? Unofficial builds work so, it's possible.
[ONE Original Android Development] Bitcloud30:
After i installed 3.0.2 it keeps on going back to recovery, any work around on this one?
[ONE Original Android Development] andip71:
[MENTION=912474]Dees_Troy[/MENTION]:

Do you have any clue why backing up CM14.1 with TWRP and restoring a backup afterwards leads to losing some settings of the rom?

It seems like CM14.1 has some trouble once a TWRP backup gets restored.

This happens on all devices I was able to test, by the way. Really puzzles me.

Thanks for shading some light into that, if possible.

Andi
[ONE Original Android Development] fmc000:
Happens on other ROMs too, at least it happened to me with Slim7 ( developer options, hardware keys bindings, battery indicator and probably more ).
[ONE Original Android Development] andip71:
Yes, it seems to be an Android N issue. So all roms using Android 7 seem to have it.

But I really would like to understand why... I suspect something with encrypted files etc. But this is really only my personal suspicion so far. I would like to hear from someone who knows about the real background. Hopefully someone can jump in.

Andi
[ONE Original Android Development] :
Do you know if this restore issue has been fixed in twrp 3.0.3?
[ONE Original Android Development] andip71:
I try to avoid any restore these days, so I don't know.

But I would doubt...

Andi
[ONE Original Android Development] :
Where do you find the 3.0.3 version?
[ONE Original Android Development] :
Not out for this device. I was just asking in general.
[ONE Original Android Development] counterfeit187:
http://xdaforums.com/oneplus-one/development/unofficial-twrp-3-0-x-tugapower-t3398366/page1
[ONE Original Android Development] mustang_ssc:
In my case, using TWRP multirom (i don't remember the version :rolleyes: ), I've been facing this issue with every Nougat rom as well.

Today I've discovered that, instead of restoring all the backup partitions, if i flash the nougat rom with all the partitions cleaned and then restore only the data partition from my backup the options are not reseated.

I don't use any encryption option, so i don't think that could be the problem.
[ONE Original Android Development] Lex1888:
Was it ever discovered why TWRP started to freeze GAPPS AROMA installer ?
[ONE Original Android Development] Gawd:
Yes. Use TugaPower recovery, it's based off Omni tree and it doesn't freeze in Aroma installation.
[ONE Original Android Development] deadlyindian:
Its not fixed yet, all devices running Nougat are affected afaik.

It seem to be a problem on bacon only, aroma behaves well with TWRP on other devices.

It doesn't on first try, get ready for a reboot on second.
[ONE Original Android Development] Gawd:
Reboot to recovery after trying one time ?
[ONE Original Android Development] deadlyindian:
Yeah that's a temporary solution.

Still needs to be fixed.
[ONE Original Android Development] christantoan:
Sorry. Wrong thread.
[ONE Original Android Development] lazychai:
My OPO bootloader has been unlocked but not root and is still running on cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot-76d803f730.zip and cyanogen recovery. I have tried to flash TWRP 3.0.2, 3.0.1 and 2.8.7 but unfortunately all there version doesn't seem working although fastboot cmd result show OK! after reboot the phone to recovery, it is still cyanogen recovery. Please help, i am running out of idea.
[ONE Original Android Development] Gawd:
Disable auto update CM recovery in Developer options :)
[ONE Original Android Development] störte:
For me is important to fast reboot and efs backup. Find that very handy
[ONE Original Android Development] real_sl4cker:
Sorry guys, I hate to quote myself but I haven't got a reply until now. Can anybody tell me what might have gone wrong? I never had problems restoring backups created with online nandroid backup on other devices, only on the OnePlus One. Is this a recovery or online nandroid backup issue?
[ONE Original Android Development] störte:
Never had that problem. Did you store the backup on the internal SD or OTG ?

When on OTG then it might have been some corrupted Data
[ONE Original Android Development] real_sl4cker:
I stored it on internal memory.
[ONE Original Android Development] chikimonke:
Hey [MENTION=912474]Dees_Troy[/MENTION], I just flashed 2.8.0.0 through fastboot on my 1+1 and the phone doesn't seem to want to go past the 1+ boot screen when I try to get into recovery. Just hangs out there. Not really sure how long I should wait for it to boot into recovery (is it possible the first time just takes a while?) or if something is borked and it won't ever get there. The phone boots up fine otherwise. Let me know if there's a log I can grab or something (not sure if anything is possible, considering where it's hanging)
[ONE Original Android Development] Pseud0logik:
Yup, same problem here. I can't get into 2.8.0.0 at all.

edit: Flashed 2.7.1.0 in fastboot and I can get into recovery again.
[ONE Original Android Development] MrMarkEdward:
+ ONE AS WELL Used flashify to flash 2.7.1.0
[ONE Original Android Development] DerRomtester:
Same problem for me also flashed fastboot in ubuntu.
[ONE Original Android Development] störte:
Oh then i will wait a little till it is solved. Like to try
[ONE Original Android Development] seth.i.simmons:
It's also ~3MB smaller than the other versions, so it looks like it might have been a bad upload unless they cut down on size quite a bit.
[ONE Original Android Development] störte:
Strange. I downloaded 9.9 Mb but on the Server it is 9.44 Mb

http://techerrata.com/browse/twrp2/bacon
[ONE Original Android Development] chikimonke:
Yeah, I just noticed that too when I went to flash the previous version. I think you may be on to something there too, as the Hammerhead imgs are very similar in size.
[ONE Original Android Development] Dees_Troy:
Bacon should be working now and this latest update should have decrypt working again after the fiasco that occurred at the 1+1 factories that broke it in the first place. MTP also seems to be working.
[ONE Original Android Development] nazfalas:
Confirmed working, thx!
[ONE Original Android Development] störte:
Confirm also.

I just see that my otg stickis not detected. :(
[ONE Original Android Development] katinatez:
Any new commits to device tree that fixed decryption?
[ONE Original Android Development] MrMarkEdward:
Be nice if there was efs backup.

Gonna go back to the unofficial 2.7.1.0
[ONE Original Android Development] dictionary:
Just be aware .. That several of us who have actually restored our EFS via that recovery, and ended up with lost modems. It's a headache to get it back if the simple flash of coloros doesn't work, or the reflash of recovery. It's great to be able to back up, but I did it once, and then use the official. If they get a working restore, I'll gladly go back to unofficial to flash it.
[ONE Original Android Development] Vortex1969:
Yeah I was reading about some of you guys that had lost there EFS. I have a backup on my laptop so I can get it back if I really have to. I've never had to in years nock on wood but then I have learned a lot more.
[ONE Original Android Development] dictionary:
Agreed. I've got one on the laptop and one on my drive. That being said that, since the restore function doesn't work, I don't see a point in using the older unofficial anymore. Especially with the looooooong boot times.
[ONE Original Android Development] cramcrx:
Twrp 3.0.2 no efs partition

Hello, i would like to backup Efs but i can't find it in the partition list. I just have these :

_ boot

_ cache

- data

- recovery

- cust

What's Cust ?

Thank you
[ONE Original Android Development] CBpbxEcmecmBeH:
By default the recovery does not back up anything else but system + data partitions. You need an

UNOFFCIAL

recovery.

In fact, you need to use your google skills and find out how to do it the proper way -- via ADB
[ONE Original Android Development] cramcrx:
Twrp is not the official phone recocery ! I installed it with adb...
[ONE Original Android Development] fmc000:
UNOFFICIAL twrp is what you have to look for.
[ONE Original Android Development] errollgarner:
I know it has been a while, but [MENTION=5427631]Vonnegut[/MENTION] you posted something two years ago on how to get modemst1 and modemst2 data back in the case of the absence of a proper backup.

I just tried it but it doesn't seem to be working. Is there a way I can get information on what is going on? a way to see why it isn't working?

Thank you in advance!

E.

(by the way I am new, so apparently I can't post the original message...)

("New users need to send at least 10 replies before they can post outside links.")
[ONE Original Android Development] errollgarner:
Hi again,

Nevermind yesterday's question! I am not sure exactly how, but I got things fixed.

Cheers,

e
[ONE Original Android Development] praveen4u13:
hi i am hit with boot loop recently. and tried installing old backup using twrp 3.0.2-0 but while restoring backup within less than 10% restore the twrp restarting to bootloop. ending no restore. anyway to fix this issue.

I don't have adb access from windows system only fast boot. And need to take data backup taken by titanium. pls help me guys. I am in terrible situation.
[ONE Original Android Development] Anghirrim:
Did you try re-flashing your twrp.img using fastboot?

Or just fastboot boot recovery.
[ONE Original Android Development] gm0:
nvm, wrong thread
[ONE Original Android Development] Gawd:
Why are you posting about it in Bacon thread though
[ONE Original Android Development] gm0:
good question, I googled the thread and must have clicked the wrong result without noticing. sry about that, enjoy your bacon ;)
[ONE Original Android Development] Lex1888:
Aroma Installer kinda seems to work with 3.1.0-0. because it runs itself and the backgroud. The twrp log text is laying above. Hard to see what's going on but not impossible. TugaPower is still the preferred recover for this task
[ONE Original Android Development] Jan_aus_Berlin:
Trying to download twrp-3.1.0-0-bacon.img. Always getting "GiroCode-File are incomplete".
[ONE Original Android Development] crisis_trustee:
What about unofficial twrp 3.1.0-0 for bacon with efs backup?
[ONE Original Android Development] MMWolverine:
I really don't understand why wasn't this fixed by now?!
[ONE Original Android Development] Gawd:
My guess would be that because apparently AROMA development/ update/ maintanence is aborted and you need to hack it in.

You might want to take a look at this unofficial recovery :)
[ONE Original Android Development] MMWolverine:
Thanks, I'll give it a go.
[ONE Original Android Development] syedyasin:
Does it will support installation of zip for the secondary ROM from recovery ?
[ONE Original Android Development] keen36:
does this mean that certain settings aren't reset anymore after a restore? that bug is so disconcerting, it makes the phone feel dirty somehow :cyclops:
[ONE Original Android Development] adithya2306:
[MENTION=912474]Dees_Troy[/MENTION]

I'm currently running COS 13 on my bacon.

While taking backup of system, data, cache and boot, I get these 2 errors:

Unable to locate '/modem_st1' partition for backup calculations

Unable to locate '/persist' partition for backup calculations

But the backup gets completed successfully.

And while taking adb backup (adb backup --twrp) of system, data, cache and boot, the phone reboots in between the backup process.

Reboot to recovery doesn't work too. (I have seen this bug in many other devices)

Hope you'll fix them. Thanks.
[ONE Original Android Development] keen36:
that looks like you previously used an unofficial twrp build which has efs backup. try using a file manager to delete the .twrp file in the twrp folder on your sd card. this will reset your settings in twrp but should fix your problem. :fingers-crossed:
[ONE Original Android Development] adithya2306:
OK Thanks

Anyways I dont have any issues now cuz I've succesfully flashed RR-N and now everything's fine. :)
[ONE Original Android Development] gil80:
Hi.

Getting two issues since updating to latest TWRP.

I'll start by saying that I have formatted my /data and /cache to F2FS. My /system is EXT4.

After flashing the latest TWRP build these two things happened:

1. Rebooting to recovery takes 3 minutes. From the moment the TWRP screen is up, till I'm actually seeing the GUI, it takes 3 minutes. Previously it was 20 seconds.

2. Backup doesn't seem to work. I get an error message about 'cannot run another thread' but it seems to do something in the background because I need to click the cancel button. I think if I'll leave it running, after few minutes the backup will start.

Is this a TWRP issue?
[ONE Original Android Development] :
Out of the official TWRP thread for OnePlus 3:

WHY DOES F2FS MAKE TWRP SO SLOW?

When TWRP boots up or wipes partitions and a few other scenarios, it checks each partition to see how much disk space is used. Ext4 handles disk usage calls quite efficiently and will finish this very fast. F2FS on the other hand is very slow when it comes to checking disk usage. We're unsure why this is. Every file on the F2FS formatted partition adds a little more time, and a device that is 30 GB full could take up to 10 minutes to boot TWRP!

I suggest switching your data partition to ext4 - all the f2fs hype is merely from benchmarks that don't actually represent real world use (ie. you're not writing thousands of files per second)

For someone who doesn't do lots of write access to their data partition, ext4 can actually be advantageous (it has faster access times and reads!)
[ONE Original Android Development] andip71:
I can only second that. F2FS is the most useless addition to Android world for year (in my opinion).

I switch everything to ext4 first thing when I get a phone = never any isues, data loss, performance issues whatsoever.

Andi
[ONE Original Android Development] :
To be honest, I've never experienced any issues, data loss, ... with F2FS on my OnePlus One and 3.

I'm running F2FS since the devices were released (OnePlus One: Summer 2014, 3: Summer 2016). Flashing more or less daily the latest cm/LineageOS and OpenGApps. No issues at all at least for me (the TWRP starting delay with F2FS is not really an issue for me)
[ONE Original Android Development] Tuang:
3.1.1.0

https://dl.twrp.me/bacon/
[ONE Original Android Development] JSB72:
Installed about one month ago... I did not get root at that time... Any way to get it now?
[ONE Original Android Development] real_sl4cker:
The recovery already has root access, that's why you can alter system files, firmware etc.

If you, on the other hand, meant you installed a ROM a month ago and now you want to get root access there it's easy. If it is not a pre-rooted ROM you can simply flash Magisk, SuperSU or any other root option you like.

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] nitanshu.vzard:
I have a nandroid backup using twrp version 3.0.2-r4. Will doing a restore also restore my EFS ?

Does twrp backup EFS ?
[ONE Original Android Development] CBpbxEcmecmBeH:
this is the official recovery.. there's no option for EFS!! you have to use a modified one...
[ONE Original Android Development] arjun:
[MENTION=912474]Dees_Troy[/MENTION] the latest twrp 3.2.0-0 is not able to restore the backups. Anyone else faced this issue?
[ONE Original Android Development] danieldmm:
Faced the same issue right now, was trying new twrp for a spin.
[ONE Original Android Development] navinthomas:
Is the changelog in OP correct? It seems to be outdated or some typo is there.

Where can I find the latest changelogs?
[ONE Original Android Development] arjun:
Commit history on GitHub.
[ONE Original Android Development] navinthomas:
Thanks for the suggestion. I had a look and it's a bit difficult to infer what I want to know from it.

I am currently on 3.1.0.0 and I just wanted to know what are the changes since then (till 3.2.1.0). The first post in this thread has changelogs till 3.1.0.0, then it shows 3.0.2.0. I just wanted to know whether it meant 3.2.1.0.
[ONE Original Android Development] arjun:
What's new in 3.2.1-0:

minui fixes (cryptomilk) * Better android-8.0 compatibility in ROM trees (Dees_Troy)

Fix missing library in android-8.0 (nkk71)

Fix inconsistent SDCard naming (DevUt)

Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)

Source : https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html

What's new in 3.2.0-0:

Allow restoring adb backups in the TWRP GUI (bigbiff)

Fix gzip backup error in adb backups (bigbiff)

Fix a bug in TWRP's backup routines that occasionally corrupted backup files (nkk71)

Better support for installing Android 8.0 based zips due to legacy props (nkk71)

Support vold decrypt with keymaster 3.0 in 8.0 firmwares (nkk71)

Decrypt of synthetic passwords for Pixel 2 (Dees_Troy)

Support newer ext4 FBE policies for backup and restore in libtar (Dees_Troy)

v2 fstab support (Dees_Troy)

Bring TWRP forward to android 8.0 AOSP base (Dees_Troy)

Various other minor bugfixes and tweaks

Source : https://twrp.me/site/update/2017/12/01/twrp-3.2.0-0-released.html

Does this help ?!

Change log from the official site.
[ONE Original Android Development] navinthomas:
YES! It never occurred to me to check there. Thanks for the help :)

---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------

Did you guys face this issue in 3.2.1.0 also?
[ONE Original Android Development] arjun:
Restore issue is fixed in 3.2.1-0, have a look at the changelog.
[ONE Original Android Development] giaur:
TWRP does not check md5 checksums any longer. Please fix that, I have my own builds for Lineage, it automatically generates md5. Please drop digest support which nobody uses and bring back md5 support
[ONE Original Android Development] tofu:
decryption doesn't work on Android 8

Latest TWRP 3.2.1-0 cannot decrypt Android Oreo roms. Any fix available for bacon? It seems it has been fixed on some phones: https://twrp.me/leeco/leecolemax2.html
[ONE Original Android Development] patp:
Just replying to bump the request to fix Oreo decryption.