[Q] TWRP + CM10.1 + Encryption = invalid password - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

Ok, I'm drawing a blank on this...
I have Encryption Enabled in CM10.1 on my GSIII
The problem is that when I reboot to apply an update it fails due to not being able to decrypt the mmc.
TWRP acknowledges that it's encrypted and asks for the password (a PIN that I set up)
but every time I try it tells me it's a bad password.
Am I missing something, some setting somewhere?
The work around is rather annoying, it just involves me copying the zip to the external SD card and installing from there.
Does CMUpdater support storing the zip on the sd natively that'd be a great work around for this as well? I can't find that setting anywhere.

Have you been able to resolve this? I'm running in a similar issue.
Company policy demands encryption and today, suddenly out of the blue, it reboots and asks for decryption password.
When I enter it, devices says it's invalid... no way to boot into recovery or into flash mode.
Device is a samsung galaxy s3 mini
Thanks,

Me too!
glennexpert said:
Have you been able to resolve this? I'm running in a similar issue.
Company policy demands encryption and today, suddenly out of the blue, it reboots and asks for decryption password.
When I enter it, devices says it's invalid... no way to boot into recovery or into flash mode.
Device is a samsung galaxy s3 mini
Thanks,
Click to expand...
Click to collapse
This is really strange, I'm getting this too. I also have to have my device encrypted for my work's MS Exchange access
I'm using latest TWRP 2.6.3.3 and have had no issues with my encryption password not being recognised with this version of TWRP before.
Device details - I'm using an international (GSM) HTC One. Recently I have upgraded to Android 4.3/Sense 5.5 via Telstra OTA update. The ROM is entirely stock from Telstra, just unlocked/rooted. Super user is via SuperSU v1.80

walleyeuk said:
This is really strange, I'm getting this too. I also have to have my device encrypted for my work's MS Exchange access
I'm using latest TWRP 2.6.3.3 and have had no issues with my encryption password not being recognised with this version of TWRP before.
Device details - I'm using an international (GSM) HTC One. Recently I have upgraded to Android 4.3/Sense 5.5 via Telstra OTA update. The ROM is entirely stock from Telstra, just unlocked/rooted. Super user is via SuperSU v1.80
Click to expand...
Click to collapse
Hi, I haven't had an HTC since the first "desire" and before that I had an HD2 for over 5 years...
So, if you are able to access TWRP you can get around this by fully formatting all your encrypted partitions and installing your custom rom again.
If that doesn't work you can try to restore the device with proper HTC tools, like Kies for Samsung devices. It fully resets the device back to stock recovery and stock rom.
I've found no way to restore any of my data. Luckily I had a cloud back-up with Titanium Back-up pro.

Related

[Q] Device Encryption + TWRP?

So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
maxawesome said:
So I was forced by my employer to enabled Device Encryption on my Gnex. Not a huge problem, as we already had to enter a PIN/Password to access company email. Fine.
So then I decide to switch ROMs from CNS 1.5.1 to AOSP r7, and lo and behold, when I flash, everything on my sdcard has been devoured. I did not select any options to do a full wipe, and as I would come to find out later, I couldn't have if I wanted to, since even the latest version of TWRP doesn't know how to correctly decrypt using the supplied PIN.
So here I am with my thumb up my ass wondering how to prevent this from happening again. I'm also considering decrypting my device, leaving it decrypted, and just using the web interface for my work mail.
Is this expected?? I'm reading in other threads for other devices that TWRP and CWM both don't know how to decrypt Samsung phones.
Say it ain't so....
Click to expand...
Click to collapse
what version of twrp are you using? the newest version supposedly fixed decrypting.
simms22 said:
what version of twrp are you using? the newest version supposedly fixed decrypting.
Click to expand...
Click to collapse
The very latest version that can be downloaded via GooManager. I always update it before flashing any new ROMs. This was done last night, so the very latest version GooManager installs as of around 9PM PST yesterday. 2.3.2.1 I suppose?

[Q] How to Root/use Recovery on a fully encrypted International Note 2 LTE?

Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
I think using Exynos Abuse apk will do the work
http://forum.xda-developers.com/showthread.php?t=2050297
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Thanks for the heads up, I'll look into it. But to be clear, that answers question 1, correct?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
pulser_g2 said:
Yes that's a way to root the device.
Regarding encryption, very few people on xda seem to use it. So for that reason you'll have trouble finding out what works... I do use it though through choice so I can help you a bit.
When you encrypt the device, just consider /data to be off limits to anything not booted fully. That's why it asks you for your key in swedish - it can't see what language is in use until you unlock /data.
You will have issues using recovery with the device, since they can't read /data. You can use an external sd to perhaps load data to the device though.
I believe that TWRP might soon support the Samsung encryption on the device, meaning you could use it as recovery. Once you have a recovery that supports Samsung encryption, you should be able to consider it a fairly normal device.
Just be more cautious to backup your data as it is hard to recover if something goes wrong...
Click to expand...
Click to collapse
Fine, I understand. As long as I have a way to recover my data if I need to wipe I'm okay... I just have to hope Titanium backup gives me that until TWRP can manage encruption on the Note 2.
I'm really waiting for a stock rom that boots in English or French now.
Sent from my GT-N7105 using xda app-developers app
vash_h said:
If your using stock rom 4.1.2, exynos abuse method of root will not work. It's been patched
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
frankieGom said:
Not the case with xxdll1. When was it patched, xxdll4 or xxdll7?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
I am on Stock 4.1.2 and Exynos Abuse did work on my device, it's successfully rooted using the Exynos AbuseAPK on 4.1.2 :good:
OK, now I have been experimenting a bit with backups and upgrade and have trouble restoring my device fully. Let me explain...
I got hold of a TWRP build that seems to handle Samsung encryption fine through one of the TWRP devs (thanks!), so I decided to go back and try to update my device.
Current ROM: N7105XXDLL1_N7105TLADLL1_N7105XXDLK7_HOME.tar (obtained from Samsung Updates)
New ROM: N7105XXDLL7_N7105OLBDLL2_N7105DXDLL1_HOME.tar (obtained from Samsung Updates)
First I performed a complete Titanium Backup on the device and pulled the files to my laptop using ADB.
Then I restarted into TWRP 2.4.0.0 (got a prompt for my password), performed a full backup and pulled the files to the laptop using ADB.
(for some reason, I could not install the new ROM from TWRP (unable to open ZIP), but the ZIP looked OK, as well as after a second download which TWRP since did not like, so I had to use Odin instead).
Next, I flashed DLL7 with Odin. It worked, asked for the password at boot, but the device was unrooted at this point (I expected that).
Then, I flashed CF-Auto-Root-t0lte-t0ltexx-gtn7105.tar from Odin, but the boot up password would not be accepted anymore as I already knew.
Tried to flash DLL7 again from Odin, same thing
Flashed TWRP back on recovery partition, but on startup it would not ask for password anymore and the external sdcard looked empty to it.
I then copied my backup to a different, non encrypted sdcard and could restore from TWRP but the password would still not work after reboot.
I did a factory reset, restored backup, same result.
At this point I decided to factory reset, wipe Dalvik and format /data. The format did the trick and after TWRP restore of my original back up the device booted up, did not ask for password and all my data was there. Except the Exchange account I use for Corporate email wants me to restore encryption in order to work (I expected that too).
Back at DLL1, so I flashed DLL7 again with Odin (OK), rooted the phone, triangled away the flash counter and reflashed TWRP to recovery.
I was where I wanted to be except for one thing: I need to restore Corporate access. But when I let it encryp the phone it does nothing. I let it through the night and nothing). And if I reboot the phone no password is needed at boot time, yet the phone seems to behave as if it thought the device was still encrypted...
I reflashed my original, full, backup (i.e DLL1) succesfully but Exchange still wants to encrypt my device. Isn't restore supposed to restore the encrypted /data I backed up?
At this point I'm left with possibly tryinjg to go back to full factory settings, not use the backup at all, encrypt the device then restore my data from the Titanium backup I made.
Is there a better option?
[edited jan 18 - TWRP/TB behaviour]
My comments apply to encrypted devices only! I am not trying to talk down TWRP or TB here, as they provide splendid performance on non encrypted devices. I have come upon hard time trying to upgrade/restore an encrypted device using thoise tools, that's all
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
[edit]
Clarification: The TWRP build I use, 2.4.0.0 is an alpha build and I was not current when I restored my backup. I so happens that it was overwriting the encryption header on the partition, which messed things up bad, and had issues writing back the data partition, ending up in a factory reset status!
Using the latest drop as of today (jan 27) I was able to restore my original backup and am now back to my original state. All is well.
[/edit]
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
[edit]
this behaviour is probably linked to encryption. I know for a fact that TB works very well on non encrypted phones. The 20h figure is overall, not just with TB.
[/edit]
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do! If you do, be prepared for some rough times...
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
frankieGom said:
For those considering upgrading & re-rooting encrypted devices, don't!
I am finding the hard way that this is a one way street. At this point, my TWRP made full backup does not restore the device to the expected status. Each time I apply it, subsequent bootup takes several minutes and I end up going through the initial setup procedure. It seems the device for some reasoin goes through a complete reset procedure.
Titanium Backup is none better. It keeps telling me that my Android ID has changed, a host of system applications start to fail when I try to restore and generally speaking I have now spent between a good 20 hours trying to simply restore my data.
The end story is: root before you encrypt, and either don't upgrade or don't re-root if you do!
Unless someone has a cleat idea of how to do this properly without losing all your data, that is.
François
Click to expand...
Click to collapse
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
pulser_g2 said:
I have had no issues despite doing upgrades, with and without wipes.
Titanium is fine, just stop restoring system app data. Seriously, what data do you have in a system app that you want to restore.
Restore your user apps, their data, and the xml based call, sms, Wifi backups. It will work fine.
Device ID isn't a problem - it's just trying to help you.
Click to expand...
Click to collapse
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
frankieGom said:
Sorry if I came across dissing Titanium Backup and/or TWRP. This was not the intent... I am sure both tools work real nice in general cases (and I have had success restoring data on a Jetstream before).
My main issue here is _full device encryption_ enforced by my company's corporate IT to allow me on the corporate exchange server. Do you have full device encryption on?
On my device, even after a full wipe and flashing a fresh stock rom Titanium Backup just did not work as I hoped. When I had to confirm individual popups of apps closing unexpectedly while it was proceeding and got nothing back in the end, what was I supposed to think? It could be that I don't understand how TB works... I was neither able to restore missing apps after the flash (missing apps: 0) nor installed apps data (they would close unexpectedly when started after restoring the back up). So I say: until full operation of TB on encrypted devices is documented, I will stay away from it, even though I am a registered user (and I do not plan to seek reimbursment)!
Anyway, I got to a belated happy ending (previous post edited).
Click to expand...
Click to collapse
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
pulser_g2 said:
Yup I use device encryption Enabled manually, but it's the same encryption.
You should find that titanium shouldn't even be aware of it - the encryption is transparent!
I wonder... I'm sure lenny had that issue on a recent 4.1.2 "stock" ROM... And he doesn't use encryption...
I personally have had no issues with titanium on an encrypted device anyway
I notice you were using the newest rom - that's the one lenny had issues on.
Click to expand...
Click to collapse
Exactly like I thought, encryption should be transparent to Titanium Backup since it runs within the OS.
I have had problems restoring into 4.1.2 DLL1 (the build I came from) and DLL7 (the one I was trying to go to)
The point is moot anyway since the DLL7 I tried was actually branded (Singtel stuff all around the launcher) and did not include French, which is why restoring my TWRP backup was a tempting proposition.
Good to know TB runs fine with encryption as well. What ROM are you running?
François
frankieGom said:
Hi all,
I recently got a HK N7105 and because it lacked the possibility to use a french keyboard I upgraded to a stock unbranded ROM from Sweden (XXDLL1) and succesfully rooted with the relevant CF_autoroot through Odin. Also installed TWRP 2.3.3.1.
Then, I connected the Note 2 to my corporate exchange server which enforced a full encryption policy (device and external SD card) so I had to type in a password at each boot time (with a "nice" swedish prompt that took ma while to decypher), plus a password to unlock the screen. All was well as the root survived the process.
Next I upgraded to a later stock ROM from France (XXDLL4 from SFR) to try and get rid of the swedish prompt. That worked fine (and root was loast in the process, as expected) but I hated the branded stuff so much I reverted to XXDLL1 until a proper unbranded "english" or "french" ROM is available.
At this point I decided to root again. I was running XXDLL1 like the first time and used the same autoroot tar from Chainfire. Except my Note 2 was still encrypted and after that it would not accept my boot password (a four digit PIN) anymore so I was guted and had to factory reset and root then reinstall everything before reconnecting to the exchange server.
Question 1: Does anyone know of a safe, proven way to root a fully encrypted Samsung device so I can go another upgrade without having to wipe the device first?
Why reinstall everything? Why not backup everything first so you can restore after the wipe? Well, it so happens that no recovery (at least neither CWM or TWRP) can read any encrypted media on the Note 2 at the moment. And no Recovery can actually fully backup the device as well.
Question 2: Does anyone know of a proper way to handle this situation with minimum hassle?
So far, the best I can think of is doing a Titanium backup and FTP the files to my NAS so I can retrieve them later. But (Question 3) will this be enough to restore my phone to the expected state after a stock firmware upgrade?
Thanks in advance,
François
Click to expand...
Click to collapse
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
pat357 said:
About a backup : have you tried Online Nandroid (Playstore) (or similar, based on Onandroid) ? This makes a CWM or TWRP compatible backup while the device is running (everything should be unencrypted at this moment).
See http://forum.xda-developers.com/showthread.php?t=1620255
About rooting : you can try the same trick as above, by using ADB-shell and pushing the needed files to root to the device while it is running.
For my S3 there is a Toolkit that automates all this (http://forum.xda-developers.com/showthread.php?t=1703488), maybe there is something similar for your device ?
If not, you should still be able to do it using manual ADB-pushing.
I'm sorry I can't give you detailed instructions about the rooting as I'm not familiar with your device. Search here on XDA and you'll find more details.
Click to expand...
Click to collapse
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
frankieGom said:
Thanks for the suggestions, and no I had not tried Online Nandroid as I was not aware of it. Anyway, my main issue is now resolved since TWRP has include support for Samsung TouchWiz based encryption in 2.4 and that works well.
For those interested, the only remaining issues I have with TWRP regarding encryption are that if you want to format /data from TWRP (say, to remove encryption) it will fail unless you _do not_ enter the password at boot, and the TWRP formated /data cannot be re-encrypted (you must use stock recovery to factory reset/wipe the device or else the encryption step will sit deat in the water doing nothing). I suppose the second one is a bug that will be fixed in a later version.
I will check Online Nandroid out anyway, being able to make a backup from a live system sounds good!
François
Click to expand...
Click to collapse
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
ludovicianul said:
I have a similar issue. I had the device encrypted and decided to ROOT (using CF-AutoRoot). Unfortunately I cannot bypass the password screen now, although I know that I'm entering the right password. You are saying that if I flash TWRP everything will be fine?
Click to expand...
Click to collapse
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
frankieGom said:
Two separate things:
Root messing up encrypted touchwiz devices and twrp not handling touchwiz encrypted partitions properly.
The 2nd one, as much as I can tell, is fixed since before 2.5 so if youwork with the latest (2.6) you should be fine.
The first one I haven't played with in a while, but my finding is that you don't want to root a device once it's been encrypted. I've tried several different methods including rooting as you flag as is possible with twrp and all end up the same:the password is not recognised anymore!
The only thing that works for me is rooting before encrypting or only flashing pre-rooted ROMs.
Click to expand...
Click to collapse
Yes - I had to factory reset the phone and format the SD Card. Never root AFTER encryption :silly:

[Q] TWRP 2.4.1 Encryption

I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
webstas said:
I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
Click to expand...
Click to collapse
I had the exact same experience on CM10.1 on the Sprint S3 with the newer TWRP 2.4.3 as well. I pinged the devs in the IRC channel about this and they offered little assistance. They basically said the Nexus devices would have the highest level of TWRP encryption support. I am a bit disappointed about this. This is a feature I definitely need.
same same
swiggs98 said:
I had the exact same experience on CM10.1 on the Sprint S3 with the newer TWRP 2.4.3 as well. I pinged the devs in the IRC channel about this and they offered little assistance. They basically said the Nexus devices would have the highest level of TWRP encryption support. I am a bit disappointed about this. This is a feature I definitely need.
Click to expand...
Click to collapse
Hi, tried it too today with the twrp 2.5.0 and have the same problem.
webstas said:
I was reading that the new TWRP revision supports decrypting aosp and twiz encrypted partitions, so i made an attempt to try it with CM10.1 Build 2/19/2013 and TWRP can see that its encrypted but it cant decrypt it, it just keeps saying invalid password.
So i changed my cryptfs password thinking the pin password was messing with the twrp backend or something, but still no love with the new password.
Has anyone else tried this?
Click to expand...
Click to collapse
I've had this trouble on a custom rom as well. Encrypted my phone for work and now I can't get decrypt my device for TWRP (v2.5). Now I can't even wipe my phone to permanently decrypt device lol. Guess the only choice is to ODIN back to stock and re-root?
EDIT: Just deleted the account that forced the encrypt and restarted. Now have the ability to decrypt device in Security settings. Would much rather have that freedom with my device than be stuck encrypted and have company access haha.
I use CM 10.1 and unfortunately I have the same exact issue. I wish I could find out what the problem is and help them fix it.
Same problem on SGS3 LTE with TWRP 2.5.0.0 and CM10.1. Can't update it anymore :/. Too bad since I'm used to update daily.
In case you are not aware, 2.6.0.0 has been out for a week or two. Give it a try. Probably won't do much better but you don't know unless you try it.
Sent from my SGH-T999 using xda premium
Tryied 2.6.0.0 just now, still the same -- "Password Failed, Please Try Again", all the time.
Ahh well, worth a try...sorry.
Sent from my SGH-T999 using xda premium
On CM site, I found a page (/blog/security-and-you) with the following remark:
"Warning for emmc only users – encrypted /data means recovery will be non-functional."
Click to expand...
Click to collapse
which apparently means we're stuck don't know whether we can do anything about it. First thing is to figure out why so....
Actually, TWRP claims that it can decrypt partition decrypted by both Samsung stock and AOSP firmwares. There're issues opened on their GitHub for several Samsung devices.

[Q] Recovery and outdated device questions

Hello,
I got my Htc One on Day 1 that Verizon released it and rooted it using rumrunner, for both S-off and root access with no problems. I have since to update my phone. I would like to update my phone to the latest radios and firmware, and start flashing custom roms.
My problem is I cannot make a backup from TWRP, my company required me to encrypt my phone to get work email but I have since had them remove the encryption but it seems that TWRP is still requesting a password to decrypt my data. I use the same password that I was using to encrypt my device but it says that it is wrong. I was thinking of factory resetting my phone but since there is no SD card will all the data that I have on my internal storage, i.e. the different backs ups I made from various apps still be on the internal storage or will they be deleted too.
Also once the encryption problem is resolved what is the best way to update my phone
Thanks
geterdone11
geterdone11 said:
Hello,
I got my Htc One on Day 1 that Verizon released it and rooted it using rumrunner, for both S-off and root access with no problems. I have since to update my phone. I would like to update my phone to the latest radios and firmware, and start flashing custom roms.
My problem is I cannot make a backup from TWRP, my company required me to encrypt my phone to get work email but I have since had them remove the encryption but it seems that TWRP is still requesting a password to decrypt my data. I use the same password that I was using to encrypt my device but it says that it is wrong. I was thinking of factory resetting my phone but since there is no SD card will all the data that I have on my internal storage, i.e. the different backs ups I made from various apps still be on the internal storage or will they be deleted too.
Also once the encryption problem is resolved what is the best way to update my phone
Thanks
geterdone11
Click to expand...
Click to collapse
Everything you need is in this thread -
http://forum.xda-developers.com/showthread.php?t=2485319
Just download the newest rom, download the newest firmware package. Put the rom on your SD card, put the firmware in your adb / fastboot firectory etc.....instructions should all be on that page.
Flash the firmware first, get the newest version of TWRP from the original development section here, flash it next, then flash the new sense 6 / 4.4.2 rom from recovery. Profit. You are s-off, so should be easy. I don't think your encryption glitch will even effect the process. And if you mess something up, since you are s-off you can just RUU back to stock. Hope this helps.

Lineage/CyanogenMod requires password on boot

Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
EDIT:
I've solved the issue. After re-flashing the RUU, flashing TWRP, and re-rooting over and over, I figured out what seemed to be going on.
In case anyone else has the same problem as me, here was my solution:
Starting from stock, I went ahead and flashed my phone with the latest TWRP compatible with N (3.0.3.0 at this current time). Afterwards I flashed LineageOS and GApps. As usual, upon reboot, the phone needed a password to get in. So, I rebooted to Recovery, which also required a password. I hit cancel, wiped the phone with a factory reset, formatted all data, and restarted. This did the trick, and I've been running LineageOS 7.1 with no problems whatsoever!
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
Hello all!
So I've been rooting and installing custom ROMs on my Android phones since getting started on my Galaxy S2 back in the day, and as it stands I've never encountered such an annoying roadblock as I've been forced to deal with over the past few days.
I just got a new HTC 10, and quickly went ahead and rooted my phone to get a custom ROM on there. The ROM seemed to boot fine, but the home button wasn't working and I had forgotten to download and install GApps. The other problem was, upon flashing the new LineageOS, TWRP would not recognize any files whatsoever on my device--including the backup I had made. So, I went ahead and flashed the latest RUU and returned to stock. After realizing the RUU is Nougat firmware, I got the latest TWRP and went ahead to try and reinstall Lineage again.
This time, however, the phone decided to stop on a screen asking for a password before it fully boots. I've tried this with every ROM I've installed and every time it will ask for a password. Boot into Recovery, and it will ask for a password there and have all my files hidden, keeping me from doing anything short of a re-flashing my RUU to return to stock. I know these ROMs evidently encrypt your phone during first boot, but I'm at a loss for info on what I'm apparently doing wrong to cause this issue.
Is this an Android N issue? On M, I was able to boot into Lineage, though TWRP still had the file issue. Anyways, whatever help would be fully appreciated. Since I'm a new user I wasn't able to inquire directly on the LineageOS thread, and so deferred to Q&A.
Click to expand...
Click to collapse
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
5m4r7ph0n36uru said:
Which version of TWRP are you using at the moment. If you're on N firmware I'd recommend to use 3.0.3-0, that is to be found on the download tab of the TWRP thread.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
dladz said:
Installing cm will encrypt your device, was you encrypted previously? Then you would have created a password to access your device.
In my case, I formatted data and then flashed my sense rom (venom) I chose not to encrypt, cm doesn't give this option when you flash it so you have no choice at the time. So if you don't have the password and the device has been encrypted you'd have to format data, don't jump into that just yet though.
Unless someone else knows a way around that, personally I couldn't. However I did have a rom installed so I could boot the rom and back up my data once in the OS. Then format (not wipe) and then reinstall the rom.
Sounds confusing, to be sure we need more info from you.
Do you have an operating system at the moment? If you do then back up your data so that's safe.
Do you know the password to decrypt your phone??
Click to expand...
Click to collapse
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
dreDREb13 said:
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
Could have thought of that myself. Encryption used by Cyanogen/Lineage is different to HTCs encryption used on Sense based ROMs. Thanks for your feedback.
Sent from my htc_pmeuhl using XDA Labs
dreDREb13 said:
I'm running 3.0.3.0. I had a problem after re-flashing my RUU where TWRP wouldn't boot, but I quickly realized this was due to using an M compatible TWRP with the new firmware.
Turns out formatting the data was the solution. Thankfully this phone is brand new, so there was no data to lose.
As for why Cyanogen and Lineage automatically encrypt without giving some sort of default password, I have no idea...
Thanks for the help, though!
Click to expand...
Click to collapse
There is no password and I've had it out in the cm thread, apparently it's common knowledge, which we've both found out its not, there is no password either so you did what was required.
Also, click thanks instead of saying mate [emoji6]
Glad you're back up and running.
thanks had same issue when installing Lineage 14.1 nightly on my HTC 10 today, which already had twrp on it and the stock rom - your solution worked.
i.e.
turn off device
hold volume down while pressing power for few seconds
choose reboot to bootloader from menu
choose boot to recovery mode
hit cancel when prompted for password
choose wipe from twrp, use default options
reboot
no more password prompt.

Categories

Resources