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.
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!
How am I able to properly upgrade a ROM if the phone is encrypted? Or would I always have to save all data to an external drive, reformat my SD-Card and do a completely fresh install? Recommended HowTo's?
If people with encrypted phones read this, I'd like to know about your experiences: Do you feel safer with an encrypted phone? Ever lost one or had difficulties with the encryption preventing getting back into your phone?
SecUpwN said:
How am I able to properly upgrade a ROM if the phone is encrypted? Or would I always have to save all data to an external drive, reformat my SD-Card and do a completely fresh install? Recommended HowTo's?
If people with encrypted phones read this, I'd like to know about your experiences: Do you feel safer with an encrypted phone? Ever lost one or had difficulties with the encryption preventing getting back into your phone?
Click to expand...
Click to collapse
Ok, so got the phone to start encrypting itself... it's still not done after 10 hours (leads me to believe that it's broken in DT 0.2.0). As best as I could find the phone only encrypts the data partition, which pretty much means that you should be able to update the rom with no probs (just updating the same rom should work fine with the same data; and changing roms requires a datawipe anyway) or at least that's how i understand it.
as far as security goes the only means (that i know of and have tried) past a standard lockscreen is through adb (or the "i forgot my password" method which requires you to log into your google account) so in this respect encryption would be an improvement.
as far as getting into the phone goes, a factory wipe should eliminate that problem (along with your data )
dessolator666 said:
As best as I could find the phone only encrypts the data partition, which pretty much means that you should be able to update the rom with no probs (just updating the same rom should work fine with the same data; and changing roms requires a datawipe anyway) or at least that's how i understand it.
Click to expand...
Click to collapse
Thanks for testing. If the phone is fully encrypted and the SD-Card is taken out, is it still encrypted? I've read of a case where thieves tried to get into the phone and they couldn't because it was fully encrypted - can someone confirm or deny this information, please?
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
I have a OnePlus 3 and I was thinking of encrypting it for additional security & privacy reasons. But since I flash various ROM level mods / use xposed modules on my phone, I was wondering about the negative consequences I have to face after encrypting an android phone.
I have a few doubts which need to be cleared.
1) Since my android phone would be encrypted, would I absolutely not be able to flash any new files/make nandroid backup from the recovery?
2) If 1) is true, which means, let's say I install an xposed module which causes a bootloop. Now I would have no way to disable all the active xposed modules from recovery since the files are encrypted, which means I would have to restore everything from scratch?
3) Is there absolutely no known way of decrypting android/access files unencrypted from recovery if we know the master PIN/password?
Can somebody who has dealt/dealing with an encrypted android phone please answer these questions? Thanks.
Deleted
Hi, thanks for your reply.
Just Passing By said:
1. When you access recovery on an encrypted phone, you have to decrypt your phone. After that, your recovery can do anything it normally could do. This would of course include flashing ROMs, zip files, and making nandroid backups.
.
Click to expand...
Click to collapse
2 things to say about that.
1)Decrypting just to flash files is a huge problem. TWRP/CWM should have a feature when it asks for the master PIN/password on the recovery, then after I enter it, it should decrypt the data on the fly and then mount the system and data partitions unencrypted so that I can flash files without going though all the decryption process.
2)Correct me if I'm wrong, but all android decryption processes I read online require wiping all data/doing a factory reset. That's again a huge problem. Why? In case I flash a mod/install a xposed module which causes a bootloop, I would have no way to decrypt my data, even if I have my master password. Which would mean I would lose all my files which I haven't backed up.
Problems like these could be avoided if TWRP provided permanent decryption/on the fly decryption using the master PIN. Comparing this with veracrypt on windows for e.g. , let's say my windows is encrypted with veracrypt and a hardware failure occurs at some point in the future & windows refuses to boot, but I'm able to load a live ISO. In this case, veracrypt offers a rescue ISO which I could use to decrypt the data without losing all my files after I enter the master PIN. So in this case, I can have security of encryption & also the convenience of decrypting it without losing all my files with the master password in case my main OS refuses to boot.
If I can't decrypt android from the recovery using the master PIN, that would mean in any case my android refuses to boot, I have lost all my files.
3. I'm assume you meant to say "... If we don't know the master PIN/Password?" And the answer to that is yes. If you can't decrypt your phone, you'll lose everything in it, so making periodic backups is a must. Otherwise, there'd be no point if you could just decrypt things right?
Click to expand...
Click to collapse
No, I did not say that wrong, sorry if I wasn't clear enough on my first post. I just wanted to know if there was a way to permanently decrypt android from recovery using the master PIN so that i would be able to recover my files to a USB in case my android refuses to boot.
Deleted
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.