Long story short. I got in a bootloop cause I think the rom I tried to install is failing. Now I'm into the recovery and can't do nothing cause the TWRP won't let decrypt my data. I already type the password and it shows "password incorrect"
So, I can't boot my phone and am not able to decrypt the data for me to back it up.
Is there any way to bypass encryption or delete the file which saves the PIN CODE? I already tried using DFE but it stuck in the logo.
PocoF3 said:
I already tried using DFE but it stuck in the logo.
Click to expand...
Click to collapse
why DFE? that is only for one purpose - disable forced encryption. it helps to stay unencrypted after formatting.
you messed up everything so you probably already destroyed encryption. your data is lost.
encryption depends on files from /system and /vendor, you could try to restore exact ROM version from your backup like it was before. even then your encryption keys might still flagged as invalid meanwhile because of rollback protection.
learn your lesson to use TWRP for what it is intended - **BACKUP YOUR DATA**
aIecxs said:
why DFE? that is only for one purpose - disable forced encryption. it helps to stay unencrypted after formatting.
you messed up everything so you probably already destroyed encryption. your data is lost.
encryption depends on files from /system and /vendor, you could try to restore exact ROM version from your backup like it was before. even then your encryption keys might still flagged as invalid meanwhile because of rollback protection.
learn your lesson to use TWRP for what it is intended - **BACKUP YOUR DATA**
Click to expand...
Click to collapse
DFE is needed to flash after installing ANY ROM to KEEP the system "unencrypted". That's what I keep doing since many rom updates ago, and always work without any issue.
The point of the thread is strictly aimed to TWRP and its decrypting process, not "what I should have done with my data" or "asking for lessons/advices". Let's keep that false condescension away from the thread.
The problem with decrypting in TWRP is well known, had it like twice, the first solution is what you said, trying to find an exact ROM to flash it over it but the thing is there's no "exact ROM version" atm, so I need to find another solution via TWRP if possible.
your question was about "decrypt the data for me to back it up"
Related
Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
paulyz said:
Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
Click to expand...
Click to collapse
I've got a feeling it's because knox has been tripped.
---------- Post added at 10:16 PM ---------- Previous post was at 10:09 PM ----------
paulyz said:
Does on custom ROM works encryption? I tried a couple ROMS, but encryption never works. Always starts encryption and after a a couple seconds phone reboots, do not encrypted. I tried encrypt after fresh install, but always unsuccessful. I googled, some peoples with other devices encrypt their devices. If I remember good, my nexus4 on paranoid was encrypted. Maybe this problem only on s6?
Click to expand...
Click to collapse
Actually just saw this:
http://forum.xda-developers.com/galaxy-s6/general/device-encryption-root-t3400259
@sofir786, thanks. I checked my logs, the phone always reboots, because he can't unmount files. I found information how temporary disable root, but no succes.
yes encryption works on any rom you just need to unroot ,encrypt ,and root .
1. unroot your phone from su app ( or try to perform a factory reset and wipe Dalvik cache in TWRP )
2. encrypt your phone
3. your phone is now encrypted try flash "CF-autoroot"via odin .
ok, encryption worked, but after encryption boot loop (stuck on samsung logo) Why?
Second time I tried fast encryption, but same end, won't boot, stuck on samsung logo.
booted to TWRP, but can't decrypt or enter to any partition.
so, guys, does somebody has encrypted s6 with custom rom? Always after encryption I get bootloop, but after unrooting device boots without problem. And, after encryption TWRP do not show encrypted partition, do not ask for key or etc.
paulyz said:
so, guys, does somebody has encrypted s6 with custom rom? Always after encryption I get bootloop, but after unrooting device boots without problem. And, after encryption TWRP do not show encrypted partition, do not ask for key or etc.
Click to expand...
Click to collapse
Twrp won't recognise the partition from what I've read that's why you don't see it, have a little Google it seems it's a common issue with twrp and encrypted partitions
sofir786 said:
Twrp won't recognise the partition from what I've read that's why you don't see it, have a little Google it seems it's a common issue with twrp and encrypted partitions
Click to expand...
Click to collapse
I googled, but no 100% true information. But if I understand good, the problem is with samsung encryption and TWRP.
So, if encryption + TWRP do not work, so custom rom with encryption bad choice, because you can't update your rom, make backup or flash new after encryption. Yes, is one possibility, to decrypt, but for this need a lot of time (if I remember good, 24+ hours).
Got my brand new U11+ today, applied november patch update, but now even with latest TWRP the phone keeps encrypting data. Any tip?
Sadly it looks like this device forum is poorly attended. Just so few U11+ out there? Really a shame
Please have a test and give me a feedback
https://www118.zippyshare.com/v/hUetNmUq/file.html
Please help me, somehow your version encrypted my phone.... What is password?
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Glower said:
Thank you so much!
Just to give you feedback, here is what I did (and what happened):
- Reverted back to stock with RUU
- Applied OTA, security patch 2018 11 01
- Flashed according twrp
At first boot encryption occurred again and in security options I could read 'phone encrypted'; still I could enter recovery and normally see data. No request to decrypt, data perfectly accessible and I've been able to flash magisk from internal storage. This was all I needed. Yet, out of curiosity, I tried to wipe data to decrypt the phone. TWRP read something like 'unable to wipe data, you should reboot recovery to access data again'. And then data were gone. No mount, no access.
Once selected reboot to recovery, the phone rebooted system instead. This time there has been no encrypting message, but the phone was wiped. And again, reading in security options, it was encrypted. Going back to recovery I had exactly the same situation as before wiping data: I could see them and normally flash zip.
Even with this weird behaviour, so far I'm satisfied with the result, so again thank you very much!
Click to expand...
Click to collapse
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
sabpprook said:
Okay, seems it works in a right way, I will post it to U11+ TWRP released page.
Click to expand...
Click to collapse
How can I get my phone decrypted? Why was it encrypted?
drtopjoe said:
How can I get my phone decrypted? Why was it encrypted?
Click to expand...
Click to collapse
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
sabpprook said:
You must flash the TWRP recovery which security level is the same as your current android system, otherwise you will get phone encrypted after reboot to android system or TWRP's data decrypting do not work.
Click to expand...
Click to collapse
TWRP says decrypted successfull with default password. In twrp I can see all my apps, but when reboot I cannot see.
Ehat version of twrp Shoul I use? Or which security patch should I flash?
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
MetroWestMA said:
So I did what I thought was a routine thing, trying to restore system, boot, and data like I have on many phones before only to ended up in a bootloop or bootloader only not even able to boot a TWRP from fastboot.
After several hours of trying just about everything I finally faced the fact that I was not going to be able to restore any NANDROID backup I had do to A/B, encryption or the latest Android security patch?
However, you can get you phone running again quite easily with this thread: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 and using the flash-all option from a WIndows 10 VM (I am a Mac/Linux guy, but this does work from a Windows VM and is quick).
Before I re-installed anything I wanted to just verify that I could do a simple NANDROID backup of an empty phone with twrp / blu_spark and I can't under any case. Here's what I tried (with latest stock TWRP and latest Blu_Spark TWRP):
1) simple restore of data, system, boot -- > boots only to fastboot, need to recover with thread above
2) Recover with thread above, re-root (Magisk 18.1) and reinstall TWRP, boot ROM, then try restoring just data -- > same as #1
3) Recover using thread above, re-install TWRP, restore NANDROID, and re-run Magisk (suggest by a few) --> same as #1
My device is encrypted, and I could turn off encryption, but that is somewhat scary on a daily driver.
So has anyone successfully restored a NANDROID on a 9.0.4 rooted phone with the latest Android security patch and if so, what's the trick?
Thanks,
MW
Click to expand...
Click to collapse
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
perhaps some remarks:
if your' phone is "empty" as you stated i recommend to first install factory image / stock rom latest OOS, i.e. 9.0.4
make nandroids of each partiton speparately and also restore them separately while don't nandroid the images, and cerrtainly don't restore those, only common partitions like system, boot, vendor, data.
system and vendor are present as normal partition as well as image partition, don't touch the later in any way.
all this only works if you restore on a phone that was bootable before you restore, for restoring to empty phones there are other procedures via fastboot commands and or stock rom via stock recovery if it's on device, else ADB comes in handy.
last but not least if you restore you have to restore everything, not only one partition especially not only system partition, won't work well or not at all depending.
1. Modem if corrupted, else not needed
2. EFS if corrupted, else not needed
3. Vendor start here if the previous rom was running well and make sure it's not been altered or you have to correct vendor backup in case you have more than one
4. System
5. Boot
6. Data
good luck
magnamentis said:
apparently is not matter of factly, i do nandroids and have restored from them various times with only 2-3 settings that i had to reset my way thereafter, hence it's apparently worth to retry, it works.
sometimes it helps to know that things are possible to put some more effort into something, knowing it can be worth it in case of success.
good luck
Click to expand...
Click to collapse
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
MetroWestMA said:
OK -- do tell, what settings did you use? And you have done this on OOS 9.0.4 with encryption, or did you disable decryption?
I'll happily delete or edit the post...it seems many are having problems with few solutions starting with 9.0.4...
Thanks,
MW
Click to expand...
Click to collapse
the last restore i did on 9.0.3, since then i gave up on custom roms since OOS rooted + a few useful apps make OOS close to perfect for me
i'd not delete the thread, many reported issues with nandroids because the normal procedure to take one single backup and restore from twrp to an empty device does not work, one always need to first flash stock OOS to a clean slate before installing anything else or restoring anything.
and backups should be in increments not one single backup like it was possible on single slot devices.
restoring one single partition usuelly ends up in a mess except boot partition, boot, efs and modem can be restored as standalone restores without issues in most cases while flashing a kernel + magisk is still easier and safer than restoring a boot partition.
as to setttings i dunno what you mean, exactly and as to encryption, my device is and has bee encrypted at all times.
it's most important to use twrp- recovery by blue_spark, official standard recovery has issues ( at least always had as long as i tried using it) especially with verification in TWRP on encrypted devices. there is a risk to end up encrypted without any way to boot back into system or into twrp menu, hence use blue_spark's and all is well, user error exempt of course
Since reinstalling everything is going to take forever (at least another 4 hours)...I am going to disable encryption and do some more testing. I am now more certain than ever, no-one has successfully restored a NANDROID on an encrypted OOS 9.0.4 phone ever.
I am going to disable Force Encryption and AVB 2.0/dm-verity and try my restore again -- maybe then I can use one of my NANDROIDS. But doing this on an encrypted phone seems impossible. I guess if you use a screen PIN you files are still vulnerable to someone that knows bootloader and / or recovery, but I'll have to live with that.... Not being able to NANDRIOD restore is a killer...
I know is an old discussion but I believe we still have this issue. I have a 6T, oos10.3.6 and neve succeeded to restore a nandroid backup. Does anyone found a working solution?
Thanks
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.
Hi everyone,
So I know I probably ****ed up but I had to ask.
Recently the touchscreen on my OnePlus 5 stopped working out of nowhere.
Now I bought a new phone but I still wanted to try to recover some data.
I had to disable my lockscreen because I was unable to unlock the phone, which I managed to do by deleting some files with TWRP.
Now here is where I think I messed up. Without knowing what it was for I deleted locksettings.db which I later found out stores the keys needed to decrypt the data partition.
Is there anything I can do to recover some data?
I know I should have made a backup, or instead of delete the file rename the file but I am past that point now.
Things I have acces to:
adb
Touch screen by mirroring to pc with vysor
TWRP
Edit: phone is rooted with magisk
If there is anything I can do any help would be greatly appreciated.
If not, so be it.
Regards,
Bart
If phone's bootloader is already unlocked, crypto-footer is present in EFS/metadata and userdata is encrypted with "default_password", so it is possible to decrypt from custom recovery TWRP without locksettings.db at all (except Samsung)
xXx yYy said:
If phone's bootloader is already unlocked, crypto-footer is present in EFS/metadata and userdata is encrypted with "default_password", so it is possible to decrypt from custom recovery TWRP without locksettings.db at all (except Samsung)
Click to expand...
Click to collapse
Hey, thanks for the reply!
My bootloader is unlocked, however default_password does not work as far as I've tried. I was able to unlock my data before I deleted locksettings.db with my screen pin. I know what the pin is still but it also does not work anymore. Also I do not know how to check if the crypto-footer is present in EFS/metadata.
I forgot to mention also that the phone is rooted with magisk, if that makes any difference. What should I do/try?
Regards,
Bart