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.
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!
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 .
I am really confused with this. What actually android wipedata/reset means ?. Is there any problem if i select wipe data factory reset...? if i select this option, is there any chance of losing my internal memory datas like messages, contacts, etc ?
sareeshmnair said:
I am really confused with this. What actually android wipedata/reset means ?. Is there any problem if i select wipe data factory reset...? if i select this option, is there any chance of losing my internal memory datas like messages, contacts, etc ?
Click to expand...
Click to collapse
The wipe data and factory reset option will wipe the /data partition which includes application data, any apps you've downloaded, pictures, music, messages, and contacts that are not stored on your sd-card. In addition to wiping the /data partition it also wipes the /cache partition which mostly contains your apps temporary files, and other system related temporary files. Your contacts can be backed up to your Google account, messages can be backed up with SMS Backup +, and for your other data I would recommend taking a look at My Backup it doesn't require root, if you are rooted Titanium Backup is a very handy tool for backing up your device.
help me as you can please
My phone it doesn't work already and and i don't want to lose any of my data because its really important to me and i didn't do the back up before …..what can i do ? …… pleas help me
problem
meshalSM said:
My phone it doesn't work already and and i don't want to lose any of my data because its really important to me and i didn't do the back up before …..what can i do ? …… pleas help me
Click to expand...
Click to collapse
problem???
gohel.vishal said:
problem???
Click to expand...
Click to collapse
i have the cyanogen room and it was working well…and then,they create a new update for the room…when I'm install it .. the playstore it doesn't work anymore .. so i tried to return to the old version by the sitting > about the phone … when i did it .. the phone restart it self and sticking in the welcome screen for the cyanogenMod…and i don't have any back up before…and i have a lot important emails and numbers that i don't want to lose it what ever it happens…..please help me with this brother
meshalSM said:
i have the cyanogen room and it was working well…and then,they create a new update for the room…when I'm install it .. the playstore it doesn't work anymore .. so i tried to return to the old version by the sitting > about the phone … when i did it .. the phone restart it self and sticking in the welcome screen for the cyanogenMod…and i don't have any back up before…and i have a lot important emails and numbers that i don't want to lose it what ever it happens…..please help me with this brother
Click to expand...
Click to collapse
Just to clarify do you mean it's gets stuck on the Cyanogenmod Bootanimation or the Setup Wizard welcome screen when you first setup the phone after wiping it or installing a new ROM? Do you have adb debugging enabled (Under Developer Options in System Settings)? Because if you do then you can use that to pull files from your device. Otherwise what you try doing is booting into recovery and trying ADB through recovery to see if you can access it that way, another suggestion would be in recovery mode to do a NANDROID backup of your current setup and then transfer the backup to your computer, extract the userdata.img from the NANDROID backup, and then use Linux to view the content of the userdata.img file (This would be a decent place to start). Otherwise I'm afraid you may be out of luck.
Hi folks.
I've just acquired a Xiaomi Redmi Note 3, and I have officially unlocked the bootloader, and installed Redwolf Recovery, Magisk, and the Pixel Experience Oreo ROM, and the phone was working for a few days without issues.
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Is there any way to solve this issue, as this is the first time I have experienced this?
Thanks.
aha360 said:
Today however, whenever I boot into my phone, force close errors pop up at three errors per second, and when I try to perform a factory reset and reinstall a ROM, the current, yet corrupt installation remains, and I cannot get rid of it.
Click to expand...
Click to collapse
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
k23m said:
Hi, you need to do advanced wipe in recovery and wipe /system, /data, /cache, /dalvik, /ART before installing a new ROM.
Should your preferred ROM still produce this issue, please try for a quick test https://download.lineageos.org/kenzo
You don't need Magisk to root LOS.
:good:
Click to expand...
Click to collapse
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
aha360 said:
Thank you very much for that. I actually did that before you suggested this to me, and I'm back up and running now.
However, one thing I have learned is that you shouldn't add any files to internal storage AFTER doing a full, destructive wipe and AFTER installing anything from there, as those files will disappear while the storage gets occupied in the process, so I ended up having to repeat the process, but with the required files ON THE microSD CARD.
Another thing I have learned from this is to not install a custom ROM on encrypted storage and double-check the encryption status BEFORE flashing a ROM as I now know that some stock ROMs automatically encrypt the /data/ and /data/media/ partitions, which is a huge pain in the backside.
Lesson of the day: even if you think you're familiar with custom ROMs and installing them, there are times whereby you'll end up hitting brick wall dilemmas like this one.
Click to expand...
Click to collapse
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
naik2902 said:
U only need to do format data option if u come from miui rom. Coz miui encrypts the data and internal sd. So format data option is must.
Moving from one custom rom to another u dont need format data. Only wipe data reset is enough.
If u have any important document . keep it in external sd. If something goes wrong or custom rom cant boot then we use format data option which erases ur internal sd too.
No need to encrypt the device. Just install the rom which comes with selinux enforcing which is enough to protect ur userspace.
Click to expand...
Click to collapse
Muchos gracias.
Also, I have a microSD card for that very reason, which is to keep all my files that I want to keep separate and safe from destructive deletion, and I have now learned that stock ROMs like the MIUI ROM encrypt the data and internal shared storage partitions, and that I have to do a full, destructive, internal storage wipe whenever I migrate to a custom ROM FROM a stock ROM.
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
aha360 said:
Also, I frankly don't give a two sh!ts about storage encryption and SElinux policies as they're far too inconvenient for the trade-off in terms of technological security versus technological freedom, so I installed The SELinux Switch app from here, and I intend to leave the device decrypted for the aforementioned reasons.
Click to expand...
Click to collapse
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
k23m said:
Exactly. When we unlock bootloaders and root our devices we choose freedom and the remaining constrictions like SElinux and encryption are, in this context, completely useless shackles. Furthermore, encryption contributes to NAND flash wear and premature device failure.
:highfive:
Click to expand...
Click to collapse
Not only that - SELinux, when set to Enforcing, restricts certain simple commands and shoves them unnecessarily behind root privileges, like "reboot bootloader", or "reboot -p", or "reboot fastboot", or "reboot recovery", or "reboot". I'm not going to wait 60 seconds for a device to reboot into recovery - screw that.
Hell, even having SELinux set to Enforcing can interfere with or block infrared beam access. Stupid crap I tell ya.
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)