Ended up with an encrypited device on PE, how to get to a dycripted state. - Xiaomi Poco F1 Questions & Answers

I got my F1 this morning and followed everything in the pixel edition guide. After first booting my phone I saw that I lost access to my PC connection (thought the drivers went bad but that wasn't the case) and my storge seem to be completely inacccessable from TWRP (but SD card was recognized). On the device itself I can't access the zip files that I had on preboot or anything the camera shoots. I did flash the Disable forced encryption and the Magisk Zips so I'm not sure why my device got encrypted anyway!
Where do I go from here to get back my file access and (presumably) dycript the device? My theory is that I should place all the files I need to do a clean install on the SD and wipe everything. But I'm not sure if that'll prevent encryption because it didn't the first time. Also, I'd be thankful if you pointed me to which zip files combination is the most functional since there's just so many different versions of everything!

Try format data then mount your local storage from twrp (you should see your storage pop on Windows) put your rom inside and flash it again

Format data not in advance wipe and then flash dfe.

SamyakJ said:
Format data not in advance wipe and then flash dfe.
Click to expand...
Click to collapse
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check

Abd121 said:
I've don't that, now how do I know that I got access to my files? Can't test on the what I had before since they all got wiped and The device is definitely not encrypted now but when I take photos they still don't show up anywhere. This could be a bug in the pixel camera and not file access but IDK. Is there a way to check
Click to expand...
Click to collapse
In twrp you can't see anything except zip files but I think can see in file manager of twrp(haven't tested this)

Related

[Q] Ice Cream Sandwich Full Device Encryption and Flashing

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!

[Q] Please I really need help with locked s2

Hey everyone .
I have a problem here ...
My little sister was trying to unlock my s2 and tried too many times.
Thing is that the Google account i used on the device is very old and I have no clue what is the username.
I was thinking if maybe there was a third party app or software (PC) to use in order to access my data from the PC without having to unlock the phone so that I can back up my data from the internal storage and wipe my phone to use it again.
I have documents I really need on the phone . Please help !
- Kevin
KBoutros101 said:
Hey everyone .
I have a problem here ...
My little sister was trying to unlock my s2 and tried too many times.
Thing is that the Google account i used on the device is very old and I have no clue what is the username.
I was thinking if maybe there was a third party app or software (PC) to use in order to access my data from the PC without having to unlock the phone so that I can back up my data from the internal storage and wipe my phone to use it again.
I have documents I really need on the phone . Please help !
- Kevin
Click to expand...
Click to collapse
How on earth can you have a google account assigned to a active device but not remember the email address of it?
I cant really see how that could happen, especially on a active device that has important files on. Also why didnt you simply store the files on external or make backup copies manually or automatically?
If the files you need are in custom folders on internal card (you created the folders yourself) then you don't need to worry. Simply reboot into recovery mode and use the wipe data/factory reset option.
WARNING: Do not do above if the device is currently on Samsung Android 4.0.4/kernel.
If you have a custom kernel installed you can simply reboot into recovery and use the mass storage option to mount cards to PC. You may be able to do this in stock kernel aswell, not sure as haven't ever really used stock recovery. Alternatively you could put a signed cwm zip on your external (via a card reader) and then flash it via stock recovery to get CWM recovery temp so you can mount drives or wipe data/factory reset.
TheATHEiST said:
How on earth can you have a google account assigned to a active device but not remember the email address of it?
I cant really see how that could happen, especially on a active device that has important files on. Also why didnt you simply store the files on external or make backup copies manually or automatically?
If the files you need are in custom folders on internal card (you created the folders yourself) then you don't need to worry. Simply reboot into recovery mode and use the wipe data/factory reset option.
WARNING: Do not do above if the device is currently on Samsung Android 4.0.4/kernel.
If you have a custom kernel installed you can simply reboot into recovery and use the mass storage option to mount cards to PC. You may be able to do this in stock kernel aswell, not sure as haven't ever really used stock recovery. Alternatively you could put a signed cwm zip on your external (via a card reader) and then flash it via stock recovery to get CWM recovery temp so you can mount drives or wipe data/factory reset.
Click to expand...
Click to collapse
Yes I know that was very stupid of me . Thing is my main phone is an htc sensation xe which I use more often.
The files aren't supposed to be on custom folders since I never created any folders on it .
I'm using the stock kernel by the way . I guess I'm really screwed .

Problems with storage not recognized

I really need help. Major problem.
My storage is not working at all (external-SD card one). I'll try to give all the info about the problem and how it appeared:
My One X+ was on CM 10.1.3 with BLADE kernel 3.1.10 #201305062233 (I didn't use the included kernel in the ROM.zip, used an older version instead). Yesterday I tried to update to CM 10.2 Nightly (I think it was 20131105) but through the CM Updater. It downloaded the ROM and I updated it without flashing the boot.img previously and the phone rebooted and got stuck at bootscreen but, ok, than I tried to flash the kernel through the One X+ Toolkit and it failed. From this point, I may have made some stupid things but here's what I did:
I forgot to clean cache and dalvik cache and since I couldn't flash new kernel I decided to go back to the previous ROM 10.1.3 and after I did it (without wiping data) it rebooted and acted weirdly so I went back to recovery and cleaned cache, dalvik and did a SD card format(!) Reason I did it was cause it didn't recognize anything on SD card when connected to PC via USB, but DID recognize everything in CWM recovery under the Flash new zip - menu. After that, I got lost. One more thing I also forgot - Google apps. I did not flash the zip and now it was deleted from SD along with ROM.zip and other stuff. I thought of bringing it back to SD, but... all I'm getting is this( image one) its emty and when I open properties it shows this (image two). When I try to copy anything on it it doesn't allow me. In phone's file manager I can access internal memory (system, sys, acct, data, rfs, root...) but inside storage-folder is only folder-emulated. No sdcard0, sdcard, legacy and that kind of stuff and if I try to crate them they disappear after reboot. Long story-short, now I can't do ANYTHING! Cant copy stuff to SD, can't flash kernels and ROMs, can't install RUU (i tried that one too-no results, and yes, I did re lock the bootloader), cant't swap recovery, can't use my phone for anything except for calling, texting and searching in the browser (but cant download anything). Another bummer is that I can't access Gapps.
So, to sum up: no way of using SD with phone or PC. I hope there is a way for using my storage again but I can't think of any.
PLEASE help if anyone knows the answer. I'll appreciate it. Thanks in advance. Any other info, just ask.
hey man i know this is a very old post but i have the exact same problem, did you find solution to this problem ?

[Q] Doubts about android 8.1

Yesterday I installed a ROM (Unofficial Resurrection Remix) thanks to EndLess and it seemed great, really very good work with the system. But when I went to restore the original rom of the phone "TWRP" asks me for an unlock pattern, after putting it and restoring the original system image, I am ready to boot the system. The system starts well, but asks me for the same pattern to start the boot. Then the loading process continues and I get to the part of setting the unlock pattern to start Android. Here's my problem, the pattern I used is the same one that I used the previous 2 times and it does not work.
Therefore I have 4 questions:
1- Is it possible to delete the encryption of the phone and leave it as it was before installing Android 8.1?
2- Is it possible to access my previous system?
3- I noticed that this room does not come with root activated, is it possible to root the ROOM?
4- If I put a new unlock pattern, will the current one be overwritten in the encryption or will the phone simply not find a way to boot and I will have a beautiful paperweight?
Thanks in advance.
Please forgive my English, it is not my native language
brito9112 said:
Yesterday I installed a ROM (Unofficial Resurrection Remix) thanks to EndLess and it seemed great, really very good work with the system. But when I went to restore the original rom of the phone "TWRP" asks me for an unlock pattern, after putting it and restoring the original system image, I am ready to boot the system. The system starts well, but asks me for the same pattern to start the boot. Then the loading process continues and I get to the part of setting the unlock pattern to start Android. Here's my problem, the pattern I used is the same one that I used the previous 2 times and it does not work.
Therefore I have 4 questions:
1- Is it possible to delete the encryption of the phone and leave it as it was before installing Android 8.1?
2- Is it possible to access my previous system?
3- I noticed that this room does not come with root activated, is it possible to root the ROOM?
4- If I put a new unlock pattern, will the current one be overwritten in the encryption or will the phone simply not find a way to boot and I will have a beautiful paperweight?
Thanks in advance.
Please forgive my English, it is not my native language
Click to expand...
Click to collapse
As it seems that you encrypted your device somehow by chance.
1. Before installing any rom you have to format your data First. That'll Remove the pattern.
2. Accessing the old system depends upon your access. If you are now encrypted then no actually.
3. Yea just flash magisk zip and the rom will be rooted.
4. Expect an out of the world paper weight.
MyNameIsRage said:
As it seems that you encrypted your device somehow by chance.
1. Before installing any rom you have to format your data First. That'll Remove the pattern.
2. Accessing the old system depends upon your access. If you are now encrypted then no actually.
3. Yea just flash magisk zip and the rom will be rooted.
4. Expect an out of the world paper weight.
Click to expand...
Click to collapse
Thanks for the quick response, would you be so kind as to explain to me what do you mean by "format your data first"?
You mean to delete all the partitions of the phone and install everything from 0 ??
How am I supposed to do that? I have a save from the previous system, I told "TWRP" to save all the partitions in my phone. If I restore that backup, will my device be decrypted?
brito9112 said:
Thanks for the quick response, would you be so kind as to explain to me what do you mean by "format your data first"?
Click to expand...
Click to collapse
Boot to TWRP, and select "Format data". You will lose all your data, plus the contents of your internal SD - but the encryption will be gone. You should back up your internal SD (either to an external SD drive, or your PC, etc) before trying any of this. I hope you have backups of your data.
DarthJabba9 said:
Boot to TWRP, and select "Format data". You will lose all your data, plus the contents of your internal SD - but the encryption will be gone. You should back up your internal SD (either to an external SD drive, or your PC, etc) before trying any of this. I hope you have backups of your data.
Click to expand...
Click to collapse
Thanks for answering, i will try your method in a few minutes, by the way, with format you mean wipe data partition, right?
brito9112 said:
Thanks for answering, i will try your method in a few minutes, by the way, with format you mean wipe data partition, right?
Click to expand...
Click to collapse
When you select "wipe" on main menu. There will we two options at bottom. One will say "Format data" and another will say "Partition" select format data. It will open a new screen saying that format data will delete all the data and Remove encryption. Type yes and continue. However backup your data before doing this. Better copy the files using mtp from recovery or system.
MyNameIsRage said:
When you select "wipe" on main menu. There will we two options at bottom. One will say "Format data" and another will say "Partition" select format data. It will open a new screen saying that format data will delete all the data and Remove encryption. Type yes and continue. However backup your data before doing this. Better copy the files using mtp from recovery or system.
Click to expand...
Click to collapse
I saw that option later, thanks to all who help, my system was recover. The only strange thing was the lock pattern. I delete from /data/system/ this 2 files, "gatekeeper.password.key" and "gatekeeper.pattern.key". Use TWRP as file manager and my phone good as new.

TWRP not reading storage.

After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8).
Now the thing is that everything was working perfectly fine until this latest magisk update. Rom works fine (Havoc OS v2. 5), magisk works fine, root works fine, phone is encrypted just as it was before, everything is fine except twrp and i really need twrp to keep working as it was before.
Now yes, I have removed pin/password and tried to make twrp work, switched from pattern to pin as some solutions out there say that twrp will ask for the pin on boot up and on entering the correct pin it will decrypt the internal storage and all will be fine. But no, it didn't work.
Whatever it is am damn sure its magisk. Rom is the same, kernel is what came with the rom, no magisk modules installed, infact I run magisk in core mode only (yes I have disabled core mode only to see if it fixes the problem). I have attached a screen shot of magisk home screen and you can see that under the advanced settings Force encryption is enabled (just like it was enabled while installing magisk for the first time, I have never messed with those settings) and the other two are disabled. Do i need to check that recovery mode? Whatever the solution is, it is preferable that I don't loose my rom and data. But if there's a 100% working solution which involves wiping everything then please mention that too.
Also some solutions need you to change the file format of the internal storage, and I am a little afraid to try that.
Sorry for the extra long post, Thanks in advance.
ronish.x said:
After the latest magisk update 20.0, twrp (3.3.1-0) asks to Swipe to allow modification or keep read only. I always choose swipe to allow modification as that's what you primarily install twrp for, but even after doing so twrp fails to read my internal memory. Before this magisk update it didn't ever ask me this, except for the first time i installed twrp. Just shows 0MB and fails to mount storage for backing up or repair (Repair file system gives an error code 8)....
Click to expand...
Click to collapse
Check your TWRP logs. They will contain clues as to what might be the problem. Then post the logs in your TWRP forum. You can get the logs via adb
Code:
adb pull /tmp/recovery.log
adb pull /tmp/dmesg.log
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Soojikahalwa said:
Did you try changing the storage type? That helped me once. Also what helped was using the latest or an older version of twrp, you can also try doing this. Let me know what happens.
Click to expand...
Click to collapse
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
ronish.x said:
Changing the storage type would be safer or flashing the same version of twrp on top of it (as I have the latest one) or an older version would be better? I will use the official twrp app for the later.
Click to expand...
Click to collapse
Try using an older version of twrp first. Changing storage type for system or data might lead to data lose. Make a backup in any case.

Categories

Resources