Related
If one enables full device encryption in Ice Cream Sandwich, am I correct in assuming that that the internal SD of that device is now not going to be available in the CWM recovery mode? And even if it was, the root fs would not be available? If so, this pretty much would make CWM flashing your device near impossible?
Does CWM even work if you use FDE? Or is it planned/
The question I guess is, when do you input your encryption password? Is it some pre-boot step?
I really want to enable device encryption but I can't find enugh details on how it works.
I did read this post on it., but it doesn't really answer my questions. And it is unclear if it encrypts the internal SD, or just the root FS?
http://source.android.com/tech/encryption/android_crypto_implementation.html
No one knows anything about this?
I got a Gnex today from Verizon in the US and I encrypted my phone after I unlocked the bootloader but before rooting. As a result I don't think I will be able to root because it doesn't seem that the modified boot.img that the instructions tell me to use can mount the encrypted system (it sat at the Google logo w/ the unlocked icon for 10 minutes before I pulled the battery and let it boot the stock boot.img) which came up fine.
It seems the only way to decrypt the phone is by doing a factory reset.
That's all I know. That being said, while a custom recovery may work for wiping partitions (such as cache), it would probably be mostly useless until the custom recovery is updated to support the encrypted file systems. I'm a *NIX user and an engineer, but don't have a lot of experience with Android's internals, so take all that with the appropriate sized grain of salt.
Regards,
Chris
Bump.
Anyone experimented with full device encryption / ROM flashing / SD Card? I'm curious about this as well, but not curious enough to experiment.
I dident try it myself, so i dont exactly know, how this works. But i think device encryption shouldent completly block clockworkmod recovery.
I think it could be a problem to make a backup while your device is encrypted. But i think it shouldent be a problem to recover a old system over an encrypted one. Encryption keeps people without the key away from reading data. This dosent mean you cant wright something over it and replace the locked data with some new one. But then you defenitly loose the old data. I dont think you can flash a new ROM or a recovery without a full wipe. You probably gona loose all the data you had on the old system.
But i general i think this is anyway a good think to do when you flash a new ROM.
I think you could give it a try, without briking your phone. But i dident try it, so i cant take any responsibility.
Would any of you happen to know how to get to the diagnostic mode?
ryfly65 said:
Would any of you happen to know how to get to the diagnostic mode?
Click to expand...
Click to collapse
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Sent from my HTC Desire HD using XDA App
Hilmy said:
I sonst exactly know hat diagnostic Mode you mean. Depends hat Diagnose you want to run. Do you want to read the logfiles in your phone, wher you can see what ist doing? You could use the app alogcat. An other way would be to run logcat over Eclipse.
Click to expand...
Click to collapse
I need to edit modem information and enable a diag port for QPST, essentially allowing me to flash it to another carrier.
Is there any new information on this? Any help would be very appreciated!
Sent from my Galaxy Nexus using XDA App
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
nevarDeath said:
I encrypted mine after flashing the stock ICS 4.0.3 image and rooting. CWM still loads, but when I try to use USB mass storage, windows tells me it needs to be formatted before the SD card can be used.
You can use titanium backup to make backups of your stuff, and restore them to a non-encrypted phone. I have found no other way to unencrypt the phone than factory reset either. When you encrypt, then go to settings > security > encryption, it just has a greyed out area saying "Phone is encrypted", which is stupid and needs to be fixed.
Click to expand...
Click to collapse
So if I factory reset the device from CMW I will not loose my pictures or TB in the internal SD?
What about flashing a new ROM?
Thanks!
I have been playing with ICS + FDE for several days doing different things. First off this is:
Nexus S 4G, running Pete's crespo4g OTA ROM
I flashed with CWM which is still on there and runs fine.
However: /data and /sdcard and /system (?) are encrypted and CANNOT be mounted.
To restore you have to 1) make a full backup over USB to a PC of the whole SDcard (or at least the important folders).
2) wipe and reformat everything. This isn't just a factory reset, this kills the sdcard as well.
3) mount (hopefully) the newly reformatted /sdcard and blow your backup from the PC onto the /sdcard
4) use CWM to restore a previous ROM.
That's pretty much it, give or take. Not for the faint of heart. However, if you are concerned enough to want encryption, you don't want to just say reboot recovery and voila all your files are belong to us, right?
---------- Post added at 03:58 PM ---------- Previous post was at 03:34 PM ----------
Also, the backup to PC part is just your sdcard. It doesn't back up the whole system. There might be a way to do that via adb, I don't know.
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Pete's to CM9 - still encrypted
IT does indeed take a fairly long time to encrypt. If I understand correctly it will build the encrypted partition on a loopback (or something like) before erasing the original (by overwriting?).
I've got more to report. I followed my plan (couple posts back) for unencrypting and reflashing my phone. (Nexus S 4g).
The first bits of this worked fine. I was able to flash CM9 onto my phone (works like a champ btw). While the phone was in recovery I mounted the SD and copied my backup back onto it.
However...
When CM9 booted I STILL got the "unlock your device" screen, still the same password, and it decrypted and booted. That was surprising, but not as much as when I looked for the SD card, it said it was incorrectly formatted! The only thing to do was reformat and copy with the phone on and unlocked.
So lessons learned: 1) a factory reset from _inside_the_ROM_ doesn't remove the encrypted partition at all and
2) As far as I can tell, the SD card _is_ encrypted along with /data
I'd be very interested to hear other's experiences, especially someone who can remove their SD storage.
Undoing FDE
First off - Lacking a device with removable storage to test with all I can tell you is that the sdcard is not accessible by any normal means after FDE is enabled without booting into the encrypted system.
"Removing" FDE required three steps beyond normal:
-Factory reset from within the ROM
-factory reset/wipe at recovery and/or format /data
-once into a running ROM, reformat the sdcard
Once all that is done (in addition to normal setup for ROM) you should be able to operate normally again.
problem with encryption on sgs2 with android 4.0.3
I really want to enable my device encryption too, but I can't !!!
the phone start encrypting after he ask me for a new secure password, rebooting and asking again for my password and surprise!!!.... the password is not match ?!?!
I repetead these steps for 3 times but the same result...the password does not match!!! ?
Please, if someone found a trick to repair this inconvenient, tell us in this post steps to be followed.
Regards!
SGS2, Android Icecream 4.0.3
leech2082 said:
So i am running rooted runnig miui.us rom. I just tried to encrypt phone.. It ran for 2 and a half hours and I got impatient. thinking maybe i shouldnt have done it... Then after a little bit of panic i said **** it if i lose data i lose data... so i powered off and back on hoping i didnt and the rom booted back up with all my data intact..... •••••• Wish I had more to report but im not doing that again until someone can confirm that it works fine...... I have tried booting into cwm yet.. If i have an issue when i need to boot illl report back but if you dont hear from me here then assume I was able too.
Click to expand...
Click to collapse
I did exactly what you did, and so far everything seems to be intact Thanks!
Hello people. I have a 32 GB Wi-Fi only Tab, running seraphimserapis' CM9 preview kang.
I'll dive right into things here. Earlier today, I flashed the above ROM, everything went perfectly, booted up just fine, and got all my apps back up and running. I was using my tab fine for the entire day with no problems to speak of. Later in the day, I began transferring some misc. files (documents, music, etc) to my internal SD card via MTP USB transfer. After the transfer was complete, I unplugged my tab, and went on my merry way. The next time I booted up, everything began FCing on me, and nearly every app I tried to open immediately FCed. Thinking it was a temporary bug, I rebooted my tab, but the same problem persisted, multiple different processes fced upon boot, and almost all my apps would fc as soon as I opened them. After trying a few more times, I gave up, and booted back into CWM (which I can do perfectly fine), cleared cahce and delvik cache, and did a factory reset. This however,seemed to only augment the problem. Upon booting up (after doing that initial tab setup), trebuchet FCes (in a "FC loop", as it continually tries to open), and the tablet is completely unusable. I have tried wiping cache, reformatting and rebooting several times, each time with the same result
I am able to get into settings however, by plugging in the tab, and clicking USB debugging (for whatever reason, settings does not FC), and am able to connect to my internal memory via MTP. When the tab pops up in my computer, it says I have 25 GB out of 28 available GB, but when I click on the folder, it is completely empty. If i try to move files over to my tab, or even create a new folder, I get an error message saying "the device has stopped responding or has been removed". (Pictures below)
http://img141.imageshack.us/img141/9855/75464072.jpg
http://img190.imageshack.us/img190/3395/61277691.jpg
I do not believe this is a problem with the rom for two reasons. (1) no one else has had this problem (to my knowledge), and (2) it was working fine the whole day, until i did that file transfer (that being said, this is my own amateur opinion, which you may choose to completely disregard it in your diagnosis). I am 99% sure I didn't unplug the tab while files were still transferring, but I did not unmount the storage or eject it or anything fancy of that nature before I unplugged it.
My question is, is there any way I can somehow reformat the internal memory of my tab? Otherwise, is there some other possible fix you experts may possibly have? Or am I screwed?
I apologize in advance if you ask me to try something and I cant respond promptly. Its 3AM here and i need to wake up early tomorrow. Thank you in advance
Edit:
I am quite convinced there is some kind of internal memory corruption problem here, but I really am not an expert enough to know for certain. The tablet still boots up fine, but is completely unusable as trebuchet fc loops 90% of the time i reboot the tab. Obviously, the entire thing isnt trashed as it appears to boot and get into the system fine, but I it's still completely unusable from that point on.
I have tried formatting the /data and /cache partitions of the internal memory to no avail. I would try formatting /system, but from my understanding, thats only advisable if you are able to flash a new rom after formatting, but if i cannot write into my internal memory, then there's no way i can flash a new rom. Conveniently enough, I deleted the .zip file for the rom off my internal sd, and i cannot access my clockworkmod recovery from CWM (gives an error, I don't think that would have worked anyway) since the internal sd is (i believe) corrupted. I also tried mounting as USB from CWM, and that also gives an error...
I am clean out of ideas. I'm not sure if this is a completely unfixable problem, or if self repairing is well within the realm of possibility. If someone can shed some light on me that would REALLY be appreciated. Otherwise i might have to send it back to sammy (still under warranty), which i dont mind doing, but if they boot it to find an ICS rom, they probably wont be so keen to repair it...perhaps there's a way to brick it further so they can't tell?
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
.......HOW??
brennanyama said:
UPDATE 2:
Problem fixed! I still don't have a clue as to what the problem was, but thankfully I managed to escape out of this one. I tried pushing a new ROM via adb, and it worked (apparently), but this just forced me into a boot loop (never hit the homescreen).
As a last ditch effort I pushed the stock ROM, and completely removed root, and it worked. I can now boot up past the spash screen without all all my processes crashing. Really a strange issue, I have my theories, but they're probably blatanly wrong so I'll just keep them to myself. Im just glad I don't have to send it back to sammy... I plan to re-root shortly. I am confident I will get no further issues.
Even though no one helped me directly, it was thanks to the plethora of information available on this forum that I was able to resolve my issue...and for some reason, making a thread where I'm just talking to myself helps a bit too...maybe im just weird. Anyway if anyone's reading this, thanks again xda
Click to expand...
Click to collapse
I'm hoping you see this reply as its been quite a while since you've had the issue. I'm working with a Galaxy S2 Skyrocket with the same intenal memory corruption/ files system corruption you were facing. I followed what you did regarding push a rom thru adb and that worked for me, but my question is, how did you get the roms to successfully write if you couldnt write to internal memory? My system is mounted as read only apparently and locked itself with whatever I had on there on August 28th. No matter how many times I format, erase, or wipe it, it returns to the same state as if its a deep lock on it.
Hi, my device is running a CM10.1 nightly. After encrypting it, TWRP 2.4.2.0 is not able to decrypt the /data partition when I enter the password. So I updated to 2.5.0.0 using the Goo Manager thinking it will fix this issue. 2.5.0.0 seems to accept the password but burps a" 'unable to mount /data' message when I try to access data storage. TWRP seems to see /data as the entire size of the internal storage too. Then I flashed 2.5.0.0 with ODIN, to exclude any problems related to local installation, and still the same issue is there. From what i read TWRP should support encryption, these bugs show that there are serious issues, how would I go about reporting that to them? Also is there a way I can resolve this without tearing down this setup?
Another issue is that my file manager cannot access my /data partiton any longer. Everytime it comes up it hangs and crashes without showing any directories. Maybe this issue would go away with a firmware update but I can't get that going because of the issue above.
you can also try CWM touch recovery if that doesn't work. just flash it from odin and install another custom rom. good luck.
-------------------------------------
please let me know if i'm wrong and CLICK thanks if i help
SRIRAM
sent from my GT-I9300 running CM10.1 RC4.4 by Temasek
Do you have a similar setup to mine I want to confirm that this is a general bug rather than an issue with mine specifically. If you are anyone else let me know I'd appreciate it. From what I have researched CWM does not support encryption so it would be a non-starter.
Hi,
I own a rooted Lenovo P780 that was bought as a gift. The phone was pre-rooted (the bootscreen mentions lenovo-forums.ru, I think it's a worldwide ROM that's installed). It's been fine for a year, but in the last few days, the internal storage has maxed out, causing problems with updates.
Yesterday, I tried something as an experiment without really thinking through the full consequences.
I had busybox and terminal emulator installed so I made a copy of the /data/dalvik-cache in the built-in SD card (since it's always present and I have an external one for all my regular data), renamed the existing dalvik-cache directory to dalvik-cache-bak (as a precaution before outright deleting, lol) and created a symlink to the new location. Everything was fine, until I restarted...
I'm not sure if the permissions are invalid or the internal SD card is not mounted early enough in the boot sequence but now the phone is basically crippled. It's not outright bricked; it does progress so far into booting, then opens many requesters about all the stock applications failing. It basically gets stuck trying to restart them.
I've not really used ADB before, but I assume that it should be possible to mount the /data partition, remove the symlink and rename the dalvk-cache-bak to dalvik-cache and at least get the thing working before resorting to some sort of factory reset.
I feel completely nubular for having to ask, but the question is, what exactly do I need to do to get into the device?
kdkc said:
Hi,
I own a rooted Lenovo P780 that was bought as a gift. The phone was pre-rooted (the bootscreen mentions lenovo-forums.ru, I think it's a worldwide ROM that's installed). It's been fine for a year, but in the last few days, the internal storage has maxed out, causing problems with updates.
Yesterday, I tried something as an experiment without really thinking through the full consequences.
I had busybox and terminal emulator installed so I made a copy of the /data/dalvik-cache in the built-in SD card (since it's always present and I have an external one for all my regular data), renamed the existing dalvik-cache directory to dalvik-cache-bak (as a precaution before outright deleting, lol) and created a symlink to the new location. Everything was fine, until I restarted...
I'm not sure if the permissions are invalid or the internal SD card is not mounted early enough in the boot sequence but now the phone is basically crippled. It's not outright bricked; it does progress so far into booting, then opens many requesters about all the stock applications failing. It basically gets stuck trying to restart them.
I've not really used ADB before, but I assume that it should be possible to mount the /data partition, remove the symlink and rename the dalvk-cache-bak to dalvik-cache and at least get the thing working before resorting to some sort of factory reset.
I feel completely nubular for having to ask, but the question is, what exactly do I need to do to get into the device?
Click to expand...
Click to collapse
Hi. Try this: reflash stock 124 ROW firmware, then upgrade to KK.
Look in my posts for Stock 124 Firmware and how to root.
4GB: https://drive.google.com/folderview?id=0B2ORIgaV4iacaVNmUWEzcDh2Nzg&usp=sharing
8GB:https://drive.google.com/folderview?id=0B2ORIgaV4iacbmZrcWN1WEZDYlU&usp=sharing
Good luck.
Sent from my Lenovo P780 using XDA Free mobile app
Thanks for the post. However, I really don't wan't to reflash the phone just yet as there is data (contacts etc) on there that aren't synced yet and I don't want to lose. Also, reflashing the phone to fix a basic filesystem issue seems like using a nuke to crack an egg.
I need to be able to boot the phone into recovery mode, but I can't seem to find any option for that. The only key combination that does anything different than a regular boot is holding power & volume down which boots into "meta mode", which doesn't seem to be useful.
Is there some special trick for this model to get into recovery mode?
kdkc said:
Thanks for the post. However, I really don't wan't to reflash the phone just yet as there is data (contacts etc) on there that aren't synced yet and I don't want to lose. Also, reflashing the phone to fix a basic filesystem issue seems like using a nuke to crack an egg.
I need to be able to boot the phone into recovery mode, but I can't seem to find any option for that. The only key combination that does anything different than a regular boot is holding power & volume down which boots into "meta mode", which doesn't seem to be useful.
Is there some special trick for this model to get into recovery mode?
Click to expand...
Click to collapse
Did you tried key combination like: power + vol up and down pressed together?
Sent from my Lenovo P780 with TWRP 2.7.1.1
I´ve tried to find any specific info on the subject for this phone but found none.
Maybe someone can help.
All was good on my phone when using Havoc custom rom. Yesterday I tested an android 11 custom rom on the device but decided to go back to 10. Orange Fox recovery restore gets stuck in the boot process. When using TWRP it can´t acess Data partition, so I´m unable to make any backups of data partition with it.
I´ve tried two diferent versions of either, and on TWRP after formating data the partition is once again acessible, but as soon as I flash a custom rom (tried two diferent one´s), boot to it and then reboot to recovery the Data partition is once again unacessible (encrypted) showing "0 MB".
Orange Fox recovery allows to access the data partition and so allows for backups to be created, but the restore process always ends up suck at boot (odly enough when enabling MTP on Orange Fox and connecting the phone to my Windows 10 machine two internal storage partitions appear in Explorer along side the SDCard one - all with the same content exactly). Something weird is going on here.
I´ve tried the steps on this post regarding DM verify (I do not know if it has got something to do with it) but it did not work (the fstab file already shows decryption on its entries):
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
Has anyone had similar problems or knows what might be going on on my device?
Is the internal flash memory going bad maybe? I´m at a dead end here.
Apreciate any idea.
Thank you.