Develop Bugs

"Encryption Unsuccessful" Boot Loop after installing TWRP.

So I decided to take my first steps to rooting, custom recoveries and ROMs and followed a stickied thread on the OnePlus forums here.
I firstly downgraded from Nougat to Marshmallow using the official Stock ROM. Afterwards, I flashed the recovery.img for TWRP from the official TWRP site. All is good.
I boot into TWRP and it asks me for a decryption password, I enter it and get "Incorrect Password". I try to boot normally and the same thing happens - weird. One member on another forum, from another question, suggested to wipe data through TWRP, and so I did. This cleared the decryption message through TWRP but then I got a boot loop with a simple message of "Decryption Unsuccessful". I press reset and the phone repeats everything.
Anywho, I flashed stock recovery and a fresh Marshmallow ROM which sorted my phone back to safeland.
Question is, how can I bypass all this? I followed the guide to the tee but no mention of this. I'm a n00b to flashing and only really know as far as the instructions on the OnePlus support page for flashing a stock ROM.

Use TWRP 3.0.4-1, it has decryption support.
If you are planning on rooting with SuperSU, use v2.79, not the first one that pops up when you Google "SuperSU". Not sure why, but the first link that pops up on Google directs you to an older version on Chainfire's site, which causes bootloops if you flash it on Nougat.
Other than the versions of the above files, the steps in rooting are the same as in the original guide.
I personally keep my phone decrypted, since I don't have anything super important on it. Not only do I not run into any encryption issues, the phone boots faster is decrypted. Decrypting does have its downsides though (you have to wipe your phone, also less security), so I would recommend that you research about it some more prior to deciding. There are methods of decrypting without losing all data though.

Anova's Origin said:
Use TWRP 3.0.4-1, it has decryption support.
If you are planning on rooting with SuperSU, use v2.79, not the first one that pops up when you Google "SuperSU". Not sure why, but the first link that pops up on Google directs you to an older version on Chainfire's site, which causes bootloops if you flash it on Nougat.
Other than the versions of the above files, the steps in rooting are the same as in the original guide.
I personally keep my phone decrypted, since I don't have anything super important on it. Not only do I not run into any encryption issues, the phone boots faster is decrypted. Decrypting does have its downsides though (you have to wipe your phone, also less security), so I would recommend that you research about it some more prior to deciding. There are methods of decrypting without losing all data though.
Click to expand...
Click to collapse
Thanks for the reply. I agree with you, I'm not fussed about Encryption and would rather have my device decrypted, the problem is I'm not sure how to decrypt it, or if it would be possible to revert and re-encrypt afterwards. As far as I know, Encryption is enabled by default on anything Marshmallow. In addition whether Decrypting would cause further issues down the line.
My reasoning for reverting to Marshmallow was Xposed and is the main reason I'd like to root with the possibility of flashing a new ROM.
In reply to your other points, I used the official TWRP from here if that makes a difference or should I be using the build you provided, surely if I can decrypt my device it makes it pointless for something with decryption support, yes?
Nonetheless, appreciate the reply!

The TWRP build from the official site is a little outdated, it is known to have decryption issues. Try the one from the XDA page.
To decrypt, you have to either root or flash a dm-verity-no-encrypt.zip that is floating somewhere around on XDA, there's probably a copy of it in the root guide in your first post. If you have no data on your phone that you mind losing (after saving a copy somewhere off your phone), the easiest way to decrypt is to go into TWRP and wipe your /data partition. If your phone is rooted or flashed with the no-encrypt.zip, the /data partition will not be encrypted the next time you boot.
There is a way to decrypt while maintaining your data, you can follow this guide. It involved saving a nandroid (saves all info in /data partition except /data/media, where all your media files and certain app data is stored). You can then save anything in /data/media by transferring it to your computer prior to wipe. You can actually restore a nandroid from an encrypted phone onto the same decrypted phone without having all your files encrypted. You can then transfer all your files from the /data/media folder back to your phone, though you'll need to give all the files and folders the proper permissions.
Once decrypted, you phone will remain decrypted until you flash OOS again, such as when updating. To prevent the phone from automatically encrypting its /data partition, you'll have to flash SuperSU or the no-encrypt.zip immediately after flashing an OOS ROM everytime you flash it.
If at some point down the road, you'd like to encrypt your phone again, that's really easy. You can go into the settings app -> secuity -> scroll to bottom to "encrypt". Clicking that option will encrypt your phone without data loss.
I personally have not had any issues after decrypting my phone. I can't speak for others though.

Anova's Origin said:
The TWRP build from the official site is a little outdated, it is known to have decryption issues. Try the one from the XDA page.
To decrypt, you have to either root or flash a dm-verity-no-encrypt.zip that is floating somewhere around on XDA, there's probably a copy of it in the root guide in your first post. If you have no data on your phone that you mind losing (after saving a copy somewhere off your phone), the easiest way to decrypt is to go into TWRP and wipe your /data partition. If your phone is rooted or flashed with the no-encrypt.zip, the /data partition will not be encrypted the next time you boot.
There is a way to decrypt while maintaining your data, you can follow this guide. It involved saving a nandroid (saves all info in /data partition except /data/media, where all your media files and certain app data is stored). You can then save anything in /data/media by transferring it to your computer prior to wipe. You can actually restore a nandroid from an encrypted phone onto the same decrypted phone without having all your files encrypted. You can then transfer all your files from the /data/media folder back to your phone, though you'll need to give all the files and folders the proper permissions.
Once decrypted, you phone will remain decrypted until you flash OOS again, such as when updating. To prevent the phone from automatically encrypting its /data partition, you'll have to flash SuperSU or the no-encrypt.zip immediately after flashing an OOS ROM everytime you flash it.
If at some point down the road, you'd like to encrypt your phone again, that's really easy. You can go into the settings app -> secuity -> scroll to bottom to "encrypt". Clicking that option will encrypt your phone without data loss.
I personally have not had any issues after decrypting my phone. I can't speak for others though.
Click to expand...
Click to collapse
Brilliant. On a side note, I'm sure I did a /data wipe, which caused the boot loop I was having - weird. Anywho, I'll try the TWRP build you mentioned and see how I get on. I did watch one video which suggested to use the fastboot erase userdata as another way of unencrypting the phone.
Either way I'll give it all a try!

Anova's Origin said:
The TWRP build from the official site is a little outdated, it is known to have decryption issues. Try the one from the XDA page.
To decrypt, you have to either root or flash a dm-verity-no-encrypt.zip that is floating somewhere around on XDA, there's probably a copy of it in the root guide in your first post. If you have no data on your phone that you mind losing (after saving a copy somewhere off your phone), the easiest way to decrypt is to go into TWRP and wipe your /data partition. If your phone is rooted or flashed with the no-encrypt.zip, the /data partition will not be encrypted the next time you boot.
There is a way to decrypt while maintaining your data, you can follow this guide. It involved saving a nandroid (saves all info in /data partition except /data/media, where all your media files and certain app data is stored). You can then save anything in /data/media by transferring it to your computer prior to wipe. You can actually restore a nandroid from an encrypted phone onto the same decrypted phone without having all your files encrypted. You can then transfer all your files from the /data/media folder back to your phone, though you'll need to give all the files and folders the proper permissions.
Once decrypted, you phone will remain decrypted until you flash OOS again, such as when updating. To prevent the phone from automatically encrypting its /data partition, you'll have to flash SuperSU or the no-encrypt.zip immediately after flashing an OOS ROM everytime you flash it.
If at some point down the road, you'd like to encrypt your phone again, that's really easy. You can go into the settings app -> secuity -> scroll to bottom to "encrypt". Clicking that option will encrypt your phone without data loss.
I personally have not had any issues after decrypting my phone. I can't speak for others though.
Click to expand...
Click to collapse
Thought I'd post a little update, I managed to install TWRP and Root. I used fastboot erase userdata which fixed my decryption issue - everything was working! Back to stock Nougat now but am going to be trying Magisk.

[UNOFFICIAL][ARM64] TWRP 3.2.3-2 with decrypt [cedric]

Hello
This is a TWRP recovery for Motorola Moto G5 Cedric for arm64 ROMS, with encryption support, backup support for persist and efs partitions and possibility to flash/backup logo boot image.
I need review and test, especially for the storage decryption and/with LineageOS fingers-crossed. I was able to test it on my device (XT1676 3Go).
It is my first ROM so it is possible that there are bugs.
- Be carefull, there are problems with the backup system :
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
- freeZbies
Click to expand...
Click to collapse
Changelog
TWRP 3.2.3-2
add sdcardfs
add FB2PNG for screenshot
fix brightness path and define it at 160
fix time zone error
fix incorrect lun path for USB
You can download it here :
TWRP 3.2.3-2 (md5: 0dbd3846593ae907d3391596876c1f35)
TWRP 3.2.3-1 (md5: 404b54d27653b5a1ec5b59023f53d3cb)
TWRP 3.2.3-0
Sources :
https://github.com/Akipe/twrp_android_device_motorola_cedric
https://github.com/Akipe/twrp_android_device_motorola_msm8937-common
Manifest :
https://github.com/Akipe/android_development_manifest

Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95

Guttergorm said:
Would it be possible for you to compile a version capable of backing up all partition, including persist and efs? see here: https://forum.xda-developers.com/showpost.php?p=78695191&postcount=95
Click to expand...
Click to collapse
Hi!
Sorry for the delay, I added the functions you wanted. Can you try and tell me if everything is ok?

Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort

mikefive said:
Hi,
tested your recovery image with my installed LOS 15.1. (32bit) Device: XT1676 16GB P5
- storage decryption: OK
- backup support for persist and efs partitions and possibility to flash/backup logo boot image: OK
nice work, thx for you effort
Click to expand...
Click to collapse
Thx for testing :good:

Akipe can u help us to build treble rom for cedric???

Works nicely, thanks.
I just tested it and it decrypts my internal storage normally.

Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.

freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
Hello ! Thank you for your test and sorry for your backup
I will test the backup system and add a warning

freeZbies said:
Just wish to come here and tell you guys to AVOID using this recovery, it seems to have a serious bug.
I just backed up my entire data partition (and enable digest verification) and restored the partition afterwards and the phone didn't boot.
Then I tried restoring it with verification enabled and the hashes didn't match.
In other words, for some reason, the generated backup was corrupt.
Of course I could make another test but it'll take just a long time to backup everything again, so if anyone wants to test it, feel free, but beware, you could have a hell of a headache finding out the backups you made were useless.
Click to expand...
Click to collapse
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test

Akipe said:
I have backup up data partition from my TWRP, reboot one time to recovery, restore the data backup with digest verification, and reboot to LineageOS, with no problem (my rom is LineageOS 16.0 without encryption.)
I think there may be 2 errors (maybe more) :
1) There is a problem with data restore when encryption is enable. I can not test this scenario for now, but i will do it as soon as i can
2) Was your backup stored on your SD card? if so, it is possible that the sd card may be damaged, because it is too old or of poor quality (more info here : https://photo.stackexchange.com/questions/40489/what-causes-an-sd-card-to-go-corrupt )
if you have other information or other ideas, do not hesitate to share it!
if people want to participate, try to save the data partition and restore it, especially with the encrypted partition :good::good:
be careful, make a backup of your data before test
Click to expand...
Click to collapse
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.

freeZbies said:
I agree it may be any of the 2 problems.
My data partition was indeed encrypted, and yes, my SD card is not what I would call genuine, though I think that's not the case since the card is relatively new and I never had any problem related to data corruption.
Anyways, thanks for your effort.
Click to expand...
Click to collapse
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?

Akipe said:
I have test backup the data partition with encryption on LineageOS 16 (arm64), backup and restore work without issue
What ROM did you use when you made the backup, and with what arch (arm or arm64) ?
Click to expand...
Click to collapse
I was on stock oreo, so its arm, not arm64

freeZbies said:
I was on stock oreo, so its arm, not arm64
Click to expand...
Click to collapse
Oh ok, there are chances that's why the backup did not work .
This recovery is mainly intended for arm64 rom !

Just wanted to say that everything worked well for me in backing up and restoring the OmniROM, on both decrypted and encrypted phone.
Thanks @Akipe for the great job

Can you update it to latest TWRP?
Sent from my cedric using XDA Labs

forgot password to decrypt??
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus

nurvus said:
hi,
first, sorry if this is the wrong place to post this. right now, when i install the 64 bit twrp i am asked for a password to decrypt my data. i have tried some passwords i think i would have used, but those don't work and i get a message also saying that the default password didn't work - i haven't typed a default password, though, so i assume there is a default one that twrp tries automatically. in the past, i did try a rom requiring 64 bit twrp and i am guessing i set a password other then the default to encrypt/decrypt, but i went back to stock without issues so have not thought about the password and cannot remember what i would have used. i wanted to try dotos on my phone, which i assume requires 64 twrp because i got error 255 when i tried to flash without twrp64. so i installed twrp64 but cannot get any further. so here are my questions:
is there any way to decrypt the data if i forgot my password?
if not, can i format the data while encrypted to install the new rom? if i can do that, what should i back up? i have pictures and other necessary files backed up, so i am not worried about completely wiping the phone to start over. however, should i back anything else up before formatting? do i need to worry about losing imei or losing any partitions that would make phone inoperable or not have any signal? should i back up with twrp64 or the non-64 bit twrp currently installed? any help or point in the right direction is greatly appreciated.
tia,
nurvus
Click to expand...
Click to collapse
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings

TheFixItMan said:
You need to format data
Push back button when it asks for decrypt
Goto wipe and select the option on the right to format data
This will erase everything on internal storage so copy any files you want to keep to pc first (pictures music etc)
Once formatted data restart back to recovery to check encryption has been removed and data partition is mountable
TWRP backups do not save personal files (pictures music etc) They only backup data and system files (and other named partitions)
Once you have flashed a new rom you can encrypt again if you want to via the security settings menu in phone settings
Click to expand...
Click to collapse
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus

nurvus said:
thanks for the quick response! and just for clarification and for me to be sure, should i back up any partitions before formatting? right now i have 32 (or non64 i guess) bit twrp installed, stock rom and bootloader unlocked. do i need to take any precautions with data/imei/signal before reinstalling twrp64, formatting data, and installing a new rom? if it matters any i have the international version of the moto g5. thanks again!!
nurvus
Click to expand...
Click to collapse
Backup efs if you want to preserve your current emei state or need to restore it in future

(solved - don't know how) how decrypt phone encrypted by 9 ROM

EDIT 3-11-2019: Know that RSDlite-ing a stock ROM will give you an encrypted system.
EDIT Never mind - I solved it though I don't know how - it kept telling me that it couldn't mount Data. Took 2 RSDlite's of 8.0.0 and a few fastboots of 3.2.3 . at one point I tried a adv wipe of everything except internal and SDcard, and LO it formatted the Data . So then I could just nandroid restore my previous one (Alberto 9 64bit)
I'd love to know how to avoid it, though.
was on alberto 9
1.82 bootloader
did full clean wipe and installed this
https://forum.xda-developers.com/moto-z-play/development/rom-aosip-9-0-beta-t3859578
on first boot it asked for password which of course I didn't have.
back to twrp but when I try anything it says busy.
RSD lite rafikowy's 8.0.0, but it auto encrypts on first boot.
Help!
Thanks!

I tried about "ten times" with rafikowsky rom, I did all tricks mentioned in xda and it encrypts each time I boot it. No way to get rid of encryption

hamudistan said:
I tried about "ten times" with rafikowsky rom, I did all tricks mentioned in xda and it encrypts each time I boot it. No way to get rid of encryption
Click to expand...
Click to collapse
yeah.
each time I rsd'ed 8.0.0, I then flashed twrp 3.2.3 (twice) and booted to twrp and tried to format Data. The problem I kept having was that Data wouldn't show as mounted. Then at some point in there I clicked on mount (data was checked), backed out,
clicked on wipe, advanced and checked dalvik/art,data,system, and slid the slider and NOW it wiped AND formatted. Don't know why.
You have to format Data (in TWRP) to get rid of encryption.
Then I just restored a nandroid that I took before I started playing yesterday and voila, back where I was.

Yeah I know.I somehow managed to mount and format data and when I boot to system afterwards - it starts encrypting again.

hamudistan said:
Yeah I know.I somehow managed to mount and format data and when I boot to system afterwards - it starts encrypting again.
Click to expand...
Click to collapse
Now THAT's interesting.
In my case I
rsdlite'ed 8.0.0
flash twrp from laptop(I do it twice in a row)
boot to twrp
managed to format data somehow,
immediately nandroided a non encrypted rom (alberto's aosp 9 64bit)
and haven't been bothered by it again.
I gotta say, this makes me more than a bit afraid to go flashing 9 stuffs other than what I've been flashing. even flashing Alberto's 32 bit scares me as this came out of the blue.
At least in worst case I can always go back to 8.0.0 and let that update as much as it can and just run that. I was hoping for a security current updated ROM which was why I was going with Alberto's 64 bit - which is no more.
Before I did any of this I went to twrp and backed up and then plugged to computer and copied internal and SDcard to my computer since I knew I would lose internal (that's where my TBPro bakup is!!!!) and wasn't sure about SDcard.

read this one - to format DATA change to ext4 and then back to f2fs.
https://forum.xda-developers.com/moto-z-play/help/twrp-3-2-3-wipe-format-data-break-phone-t3892745

new guide:
https://forum.xda-developers.com/editpost.php?do=editpost&p=79070724

for folks who read that last post and link, I just completely re-wrote it.
RSDlite-ing a stock rom will give you an encrypted phone.

How to decrypt your OP3(T) device with custom rom?

A question about decrypting your device, in this case Luisrom Android 10, but would most probably count for other roms too.
Did not try it already but would like to decrypt my device and would like a confirmation if the following is the right procedure without doing a new install:
Boot in recovery
Make a backup of /data to internal storage with TWRP
Make a backup of internal storage to my pc
Format data in TWRP
Copy internal storage back from pc to OP3(T)
Restore backup from /data with TWRP
Reboot with decrypted phone
I could do a dirty flash afterwards ofcourse, but because /system is not touched I think the steps above should be enough.
Could someone confirm if this is right?

Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!

Johan2020 said:
Just tried what I described above but seems not to work.
After reboot, phone is starting again with encrypting and after next reboot everything is encrypted again.
It also seems as if Android 10 (read it somewhere) is using file based encryption, so not only on a higher level...
So for now, I only see a fresh install as the solution.
Would someone know another solution to keep your data without doing a fresh install it would be nice to know.
Any input is welcome!
Click to expand...
Click to collapse
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based

nvertigo67 said:
First of all: decrypting is what happens on each reboot if data is encrypted. Decrypting is making something encrypted readable again. Removing encryption is something completely different.
For your question: which rom are you booting? This sounds like you are using a rom with forced encryption enabled. Dosable forced encyption in fstab before first system boot.
You can't use fbe with op3/t. No blobs, no twrp... Either you havn't read closly enough or you belived some ignorant not reading closely enough: g requires new devices shipped the first time with q to use fbe. All devices shipped originaly with fde can still use fde with q.
Reference: https://source.android.com/security/encryption/file-based
Click to expand...
Click to collapse
I am using CrDroid 6.4 Luisrom which is not enforcing encryption, just as most other custom roms.
I had enabled encryption though after installation to see if encryption was working already for installing CrD Luis on my work phone (where I want encryption).
After that I decided to go back to unencrypted, following the procedure above, which did not work.
Did not make the link between fbe and file based encryption, but ofcourse this is the same and not available on op3/t.
Must have been sleeping when I wrote that.
Based on what you wrote and my missing knowledge;
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?

Johan2020 said:
After encrypting, is fstab changed also and would the solution have been to change fstab back also before rebooting after restore?
Click to expand...
Click to collapse
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.

nvertigo67 said:
No. fstab isn't changed during encryption, neither for forced encryption nor for "voluntary" ( ) encryption.
Maybe the problem is the restored data itself: the rom setting for encryption is restored as well if you restore the data unconditionaly... Perhaps this way the reencryption is triggered. Did you try to boot the rom without restoring data? If it's unencrypted on a clean boot, but is (re)encrypted after first boot after restoring the backup, you have the answer. If it's encrypzed on a clean boot, formating to remove the enctyption has failed.
Click to expand...
Click to collapse
Good point, did not try that unfortunately and just did a fresh install so.... not really eager to try it now
But I think indeed reencryption was triggered because of also restoring the encryption settings.
Will try it when I have some spare time and want to take the risc of a fresh install again

Is my encrypted data lost forever after the Android update?

Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.

reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.

So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?

reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.

reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work

loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?

reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray

loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?

reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)

loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?

reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes