"Unable to mount storage" with encrypted partition

[StephenKing]

I have encrypted my system in CM13 (build from march) and decryption fails in TWRP (2.8 to 3.0.2) with error "Unable to mount storage". Thus, I cannot upgrade my CM.

I already tried the custom test build by @Kra1o5 from TeamWin/Team-Win-Recovery-Project#699, which however also does not help.

Here are my recovery logs from stock 3.0.2-0 and @Kra1o5's build.

[Kra1o5]

Hi @StephenKing ,

Can you try to mount system and firmware partitions in twrp before try to decrypt?

Greetings

[StephenKing]

Hi @Kra1o5, thanks for your quick reply.
when I cancel the initial decryption dialogue and go to the Mount menu, I can select firmware and System partitions, but can continue only using the Decrypt Data button (where I enter the PIN, which again fails resp. hangs in the test build). Not sure, if I'm correctly following you.

[Kra1o5]

Yes, this is the correct process.

[Bondarz]

hey @Kra1o5

what should i select if i want to flash the image?
"System Image" "Boot" or "Revovery"?

by the way: there is no "firmware" partition.

Thanks

[Bondarz]

any ideas @Kra1o5 ? ;)

[Kra1o5]

Hi @Bondarz ,

Sorry for the delay, Im busy atm.

I refer to this partitions in my test build in "Mount" .

Greetings

[Bondarz]

Ok, installed the image now via "boot" and "recovery"

first boot aber choosing "boot": entered my PIN, still wrong password
second boot after flash as "recovery": entered the PIN, than a loop for minutes, trying to decrypt after entering my PIN...

"data" still with 0mb inside twrp

now i can`t boot into my android, think "boot" was the wrong choice? ;)
flashed CM13 and the gapps again, this fixed my boot problem.

log (with your image): http://pastebin.com/0V1ngmd0
hm..befor the image it was at 3.0.2-1, after flashing the image its 3.0.2-0
old log: http://pastebin.com/Eig9DFp3

[Kra1o5]

Hi, thanks for logs! I will check asap (Probably weekend).

Greetings

[compiaffe]

@Kra1o5 and @StephenKing I experience the same issue on my BQ Aquaris M5 with both
twrp-3.0.2-1-piccolo.img
twrp-3.0.2-0-piccolo.img

[stucki]

@Kra1o5 Any update here?

[Kra1o5]

Hi @stucki ,

Im very busy atm but im checking it now.

Sorry for the delay!

Greetings

[Kra1o5]

Hi @stucki ,

I cant get it working, it stuck in eternal loop at decrypt page.

[Kra1o5]

Hi @stucki @compiaffe @StephenKing @Bondarz ,

Sorry for the big delay!

I think is now fixed, someone to test it?

Here the image: https://s.basketbuild.com/filedl/devs?dev=Kra1o5&dl=Kra1o5/bq/piccolo/Test/TWRP-piccolo_decryptt2.img

Greetings

[StephenKing]

Thanks for the build, @Kra1o5. Unfortunately, it still fails to decrypt.

[Bondarz]

Ok, looks like i can decrypt :) @Kra1o5., thanks

Before:
twrp-3.0.2-1-piccolo.img
FirmwareMM_v4.1.0_signed.zip
cm-13.0-20160725-UNOFFICIAL-piccolo.zip
gapps

now: twrp-3.0.2-0 (piccolo_decryptt2.img) (why 2-0 instead of 2-1?)
installed the image as "recovery" inside from TWRP twrp-3.0.2-1 and restarded my phone.

backuped my whole phone after decrypt my m5-> works with my normal decpryt PIN.
the twrp interface is now german -> i think before it was english?

new log: http://pastebin.com/qVrj2n3t

[Kra1o5]

Hi @StephenKing ,

What is your configs?

@Bondarz Yeah dont worry about -0 or -1 because is device specific so are the same version.

[StephenKing]

@Kra1o5 not sure what config you mean. I've booted the image via fastboot boot, have a number-only PIN.

[Kra1o5]

@StephenKing Yeah I refer to method, PIN in that case.

You refer to fastboot flash recovery TWRP-piccolo_decryptt2.img ?

[StephenKing]

No, I booted it from the bootloader via USB and fastboot boot TWRP-piccolo_decryptt2.img. But I can just try to flash it to recovery. Gimme a sec..

[Kra1o5]

@StephenKing

Is better flash the image to get it working proprerly.

[StephenKing]

Flashed on recovery partition does not work either.
Here's the content of /cache/recovery/last_log.

[Kra1o5]

@StephenKing Seems like it not getting flashed, its show 3.0.2-1 not 3.0.2-0 .

[StephenKing]

Don't scroll to the very top. These are the logs I linked previously, I'm only grouping them in a Gist. See here.

[Kra1o5]

You try to update firmware to 4.1.0?

Here the zip: https://s.basketbuild.com/devs/eloimuns/bq/piccolo/

[StephenKing]

Umm.. what's that? How do I flash that?

[Kra1o5]

In theory you can flash it from twrp, because it not use data partition.

[StephenKing]

But.. that's the original Aquaris Android version? Or what's that? Can I flash that thing, if I can't decrypt my System partition (I mean.. I can't update CM because of that).

Is there maybe any way to revert the encryption? Maybe updating and then encrypting again picks some different algorithm or so.

[Kra1o5]

One thing is OS and another firmware, this flash some partitons to update firmware not to update OS.

You cant flash CM because it use data for somethings.

Encryptation only do this on /data partition not /system or others.

[StephenKing]

That (installing the firmware ZIP from recovery) helped! I was now able to update to latest CM (had to flash TWRP once more as it somehow completely vanished).

Thanks a lot @Kra1o5 and @stucki!

[Kra1o5]

@StephenKing Glad to hear that 😁

Greetings

[StephenKing]

How can I donate?

[Kra1o5]

@StephenKing thanks! but you dont need to ☺

[StephenKing]

Thank's. I'd be happy to do, if you send me a paypal address or so. You made me able to install updates on my phone again!

[Kra1o5]

@StephenKing You can find it here: http://www.android-hilfe.de/thema/rom-6-0-cyanogenmod-13-0-fuer-das-bq-aquaris-m5-weekly.735689/

Regards

[StephenKing]

Thanks for your help and keep up that good work!

[stucki]

@Kra1o5 What did you change to make this work? The image that you published in #1 (comment) is newer than the latest image at https://dl.twrp.me/piccolo/. Can you somehow update it?

[Kra1o5]

@stucki Here the changes: 259bd41

It will be fixed in next twrp release.

Greetings

[stucki]

Great, thanks!