I have a LG G5 H850, with 6.0.1 and stock V10c-EUR-xx.
I disabled disk encryption using the no-verity-opt-encrypt.zip utility by jcadduono.
Now I wiped again using TWRP, but encryption is still disabled as the boot.img/partition still has his modifications to the fstab files (where he does
the change s/\bforceencrypt=/encryptable=/g etc.)
How to I set that back to as it was?
I got into this sitation as I kept finding TWRP could not access the partition - asked for password and there was none.
I do want to use encryption but in my first hour of setting up the phone I had a problem where when I booted into TWRP it would ask for a password and it was not "default_password", and I had not set anything and never used lock screen/pin etc. I tried setting a lock screen/boot screen password - the phone worked but TWRP could not access the filesystem. I tried the cryptfs application and still TWRP was not able to decrypt/access the partition.
Then I tried a terminal with vdc cryptfs changepw command and that just locked me out of the phone completely, as the new or old boot password would not work.
So I went for the no-verity-opt-encrypt.zip solution - but I dont want an unencrypted phone either. Now I want to try encryption and TWRP again - this time setting a pin at the first setup screen opportunity to see if that gets set as the password that TWRP could use. However I can't remove the disable encryption patch!
Ideally I am trying to get to a setup where:
encryption is enabled
I want to be able to boot TWRP and access the encrypted filesystem and install more zip files such as xposed/supersu updates etc anytime in the future.
I dont want to use the "no-verity-opt-encrypt.zip" patch.
I do not want TWRP to be locked out from modifying the encrypted system partition.
Additionally, I havbe not been able to install xposed using TWRP and the zip file (http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip) .
In TWRP it installs, I dont see any errors, but on boot up I have no xposed icon. I have been able to install it by downloading the apk and installing as an untrusted source, not sure if there is something wrong in having to do it this way?
Thanks.
current TWRP build for G5 doesn't support encryption
you can use encryption but in TWRP you won't be able to access some partitions (if I remember right is data partition but I might be wrong here)
in order to do so, you need to restore base firmware with LGUP that will turn encryption back on
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
tomb007 said:
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
Click to expand...
Click to collapse
may i ask how did you root it after that? because everytime i try to rooted while encrypted,i flash the zip in twrp (with no errors) but system still has no root! the only way i could root was to format /data in twrp, hence have a decrypted phone!
I am looking for the same thing as you are : encrypted phone with twrp and root access.
I rooted using TWRP adding supersu at the time of installing the OS before the OS encrypts the partition. Once the partition is encrypted TWRP can no longer access it, and I can no longer install supersu or anything else.
I may have installed root before encrypting, then reflashed the boot partition so that encryption is re-enabled, then ran twrp to reapply supersu - which would fail to put files on the encrypted partition - but this is fine as they were already there, and let the twrsp supersu installation modify the boot partition.
The result is an encrypted phone with root and TWRP. However, TWRP can not access the encrypted partition so I don't think I can update supersu using TWRP, and I dont think I can patch the OS easily without wiping the encrypted data and reinstalling everything due to this. As I am not sure if updating the OS works without wiping data, I have yet to try that.
you shouldnt have to mess with data at all to use supersu while encrypted.
my g5 is encrypted and always has been (besides in various testing) and there's never been an issue of flashing supersu.
though there may be some issues if trying to restore encryption and flashing supersu in the same reboot cycle.
and yes, data partition in twrp cant be accessed in twrp if encrypted.. but you can just push a file to the /tmp directory while in twrp and then flash anything... or enable adb sideload and flash something that way... or use an external sd card and put the file on there. the only thing you really miss out of if using twrp while encrypted is being able to manipulate the data partition... it does not stop you from flashing files or running scripts that modify /system or other partitions (besides /data).
supersu uses the unencrypted /cache/ partition to work in when you flash it while encrypted so an encrypted /data partition should not be relevant.
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
Hi,
So I just unlocked my bootloader, installed TWRP and then I installed the latest TWRP version of MIUI Pie beta.
The setup wizard has firstly asked me for my Mi account password which I provided. But then, right after it asked me if I want to restore from a Google backup, it asked me to "Confirm my password". First, I thought it's asking for my previously used lockscreen password. However, only a numeric keyboard shows up! And my lockscreen password also contained letters.
I tried to wipe data through TWRP and even flash the zip file which removes the lockscreen lock, however the issue still happens. At this point I was afraid I would not be able to use the device anymore, but luckily I went back to MIUI 10 Oreo and completed the setup successfully.
I still want to try Pie. Has anyone else had this issue?
Thanks.
Hi. I had same issue. I needed to format everything. What i did: format system then i flashed the pie rom. When that was done I formatted. Everything else including data and internal storage. This helped.
Make sure you backup your personal data because you will lose everything.
Android P has a handy little thing called Force Encryption. Once you flash it it auto encrypts to protect your data. You can find zips that turn it off or you can use a recovery that has it built in like OrangeFox.
Or it could be asking for your google account password...
Its asking for your mi account password, just upgraded to pie yesterday. Whenever upgrading disable all fingerprint and other lock screen password ,then upgrade to newer build like from oreo to pie and enable them again.
Likely you have to do in Twrp > WIPE > FORMAT DATA, back up your internal storage on pc bcoz you will lose everything
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.
Hello I have a rooted phone with official miui12 rom.
TWRP is flashed but I can also run TWRP using adb.
How can I flash the New miui13 stock version ? Do I use the official Xiaomi flash tool? Or do I use TWRP to flash the stock rom?
iostrym said:
Hello I have a rooted phone with official miui12 rom.
TWRP is flashed but I can also run TWRP using adb.
How can I flash the New miui13 stock version ? Do I use the official Xiaomi flash tool? Or do I use TWRP to flash the stock rom?
Click to expand...
Click to collapse
Through fastboot, you should use the fastboot ROM, and through TWRP, you should use the recovery ROM.
Thanks. A preferred option ?
Using TWRP do I need to erase stuff before or can I install directly the rom and this is all ?
I guess that recovery room is not the one provided officially by Xiaomi, right ? It the same but packaged a different way ?
Do you know if SD card will be erased during the stock rom flashing process ?
I see on official Xiaomi site that official rom is quite old. Miui11 version so I guess I will need to perform a lot of OTA update... Can I trust recovery rom provided on other websites to have the latest stock rom version ?
iostrym said:
Thanks. A preferred option ?
Using TWRP do I need to erase stuff before or can I install directly the rom and this is all ?
Click to expand...
Click to collapse
Normally, you don't need to erase data, as they just update without erase per se.
iostrym said:
I guess that recovery room is not the one provided officially by Xiaomi, right ? It the same but packaged a different way ?
Click to expand...
Click to collapse
As I said you, there are two official versions, the fastboot and the recovery ROM.
iostrym said:
Do you know if SD card will be erased during the stock rom flashing process ?
Click to expand...
Click to collapse
No.
iostrym said:
I see on official Xiaomi site that official rom is quite old. Miui11 version so I guess I will need to perform a lot of OTA update... Can I trust recovery rom provided on other websites to have the latest stock rom version ?
Click to expand...
Click to collapse
The OTA updates come, either in form of fastboot or recovery ROM, when Xiaomi provides an update, you will, also, find the minimal OTA package, yet included in the whole ROM.
In this site, you will find the most up-to-date releases https://xiaomifirmwareupdater.com/archive/miui/joyeuse/
thanks. I would like to be sure that my flashed TWRP will be erased during the process, will both flashing process (fastboot or TWRP) erase all my phone and put in a new "clean" state ? (except maybe for sdcard content)
iostrym said:
thanks. I would like to be sure that my flashed TWRP will be erased during the process, will both flashing process (fastboot or TWRP) erase all my phone and put in a new "clean" state ? (except maybe for sdcard content)
Click to expand...
Click to collapse
Nope, both the processes, don't wipe per se, either through recovery or fastboot, in the Mi Flash tool, there is an option to format data, if you like it, if not, it remains un-ticked.
Sorry to insist but what are you calling 'data' ? Is it the SD card content (I don't think so) or is it the data partition on my internal memory ? So it could be :
Photo taken in internal memory
Data stored by apps like photo from WhatsApp or stuff like that ?
Temp file of each app like settings of app, etc.
Would it be a problem if I erase all my phone and loose all my apps but data off app are still there, it will take space for nothing right ?
What about flashed TWRP? will it be removed by the flashing process ? I think TWRP is flashed in recovery partition but not sure.
As you see I'm not familiar with android partition even if I did several times this kind of process with different phones.
iostrym said:
Sorry to insist but what are you calling 'data' ? Is it the SD card content (I don't think so) or is it the data partition on my internal memory ? So it could be :
Photo taken in internal memory
Data stored by apps like photo from WhatsApp or stuff like that ?
Temp file of each app like settings of app, etc.
Would it be a problem if I erase all my phone and loose all my apps but data off app are still there, it will take space for nothing right ?
What about flashed TWRP? will it be removed by the flashing process ? I think TWRP is flashed in recovery partition but not sure.
As you see I'm not familiar with android partition even if I did several times this kind of process with different phones.
Click to expand...
Click to collapse
Not exactly what I call data, but, what data means in Android World.
Formatting data, it's deleted all the data from apps stored in /data partition, all the data regards settings, all the apps installed by the user, general configurations and all the data stored in internal storage, also the system apps uninstalled by the user can come again.
As per the SD Card, if you have one inside, it is not touched in the process.
If you flash the recovery ROM using TWRP, it won't be overwritten, if you flash the fastboot ROM, you'll lose the access to TWRP.
Thanks. Tell me if I'm wrong but if a choose to flash stock miui 13 version whereas I'm currently in miui12 I should maybe erase data also ? Maybe apps won't works again from 12 to 13 version ? I should be cleaner to reinstall them again don't you think ?
About fastboot stock rom isn't it strange that the official website provides only miui 11 rom whereas your site has miui13 version? How is it possible ? For recovery rom I understand because people can backup their phone and could create a recovery rom like this with miui13 after doing the ota. But for the fastboot rom, if Xiaomi don't provides it and provides only miui11 one, where does the miui13 come from ?
iostrym said:
Thanks. Tell me if I'm wrong but if a choose to flash stock miui 13 version whereas I'm currently in miui12 I should maybe erase data also ? Maybe apps won't works again from 12 to 13 version ? I should be cleaner to reinstall them again don't you think ?
Click to expand...
Click to collapse
It would work even if you don't erase data, but, I personally prefer erasing it, to avoid some lags/bugs in the future.
iostrym said:
About fastboot stock rom isn't it strange that the official website provides only miui 11 rom whereas your site has miui13 version? How is it possible ? For recovery rom I understand because people can backup their phone and could create a recovery rom like this with miui13 after doing the ota. But for the fastboot rom, if Xiaomi don't provides it and provides only miui11 one, where does the miui13 come from ?
Click to expand...
Click to collapse
Firstly, be sure that your device is Joyeuse.
All the updates, either recovery and fastboot ROM, are provided by Miui, all of them are official updates, not uploaded from users´ devices.
It's A12, not A13, I don't think your device see the light on A13.
Yes android 13. But miui 13 comes with android 12 and my current os is miui12 that comes with android11. (If I'm correct).
I have Redmi note 9 pro, M2003J6B2G (photo is 64M). I don't know where Curtana or joyeuse word can be really found in my phone but after some readings I had the feeling that M2003J6B2G = joyeuse version.
iostrym said:
Yes android 13. But miui 13 comes with android 12 and my current os is miui12 that comes with android11. (If I'm correct).
Click to expand...
Click to collapse
Xiaomi also could update the Miui version, so Miui 13 came with Android 11 for some devices, don't stay there, just check the Android version that is specified in a tab, at the download list.
iostrym said:
I have Redmi note 9 pro, M2003J6B2G (photo is 64M). I don't know where Curtana or joyeuse word can be really found in my phone but after some readings I had the feeling that M2003J6B2G = joyeuse version.
Click to expand...
Click to collapse
There are some apps like Device Info and other similar, from Play Store that can tell you, exactly, which your model is, Anyway, Redmi Note 9 Pro is Joyeuse but, be sure, before to proceed, consult some app like the mentioned.
SubwayChamp said:
Xiaomi also could update the Miui version, so Miui 13 came with Android 11 for some devices, don't stay there, just check the Android version that is specified in a tab, at the download list.
There are some apps like Device Info and other similar, from Play Store that can tell you, exactly, which your model is, Anyway, Redmi Note 9 Pro is Joyeuse but, be sure, before to proceed, consult some app like the mentioned.
Click to expand...
Click to collapse
Cpu-z indicate joyeuse-eea. Should be good.
Ok so I will delete the data partition and I will use fastboot flash using Xiaomi tool. I'm not sure to understand your answer about the SD card. Will it be erased during the process ? I know that sdcard are now crypted so that they could be used only by my phone. If the os is modified, maybe I won't be able to read it even if it is not formated. Don't you think ?
iostrym said:
Cpu-z indicate joyeuse-eea. Should be good.
Click to expand...
Click to collapse
Good, then it is the european version.
iostrym said:
Ok so I will delete the data partition and I will use fastboot flash using Xiaomi tool. I'm not sure to understand your answer about the SD card. Will it be erased during the process ? I know that sdcard are now crypted so that they could be used only by my phone. If the os is modified, maybe I won't be able to read it even if it is not formated. Don't you think ?
Click to expand...
Click to collapse
Just to not confuse, sdcard is the internal memory, that is symlinked as /data/media/0, all the internal memory is gone when we format data, some folders are recreated at the first boot, after performing it.
SD Card refers to Secure Digital card, that is an external media storage, it is absolutely excluded to any operation from Android, when flashing, updating the system or formatting data, of course, you should consider that some apps like camera can store its pictures there, previous authorization from user, but they will stay there yet, and some folder can be created too, at the first boot, but nothing that harms.
Just to know, sdcard as internal memory is not encrypted at all, it's accessible for any user, always, that can bypass the locking feature of the choice of the user, i.e. PIN, pattern, etc.
Thanks I didn't know that sdcard and SD card weren't the same. My concern is about external memory card (SD card). If not formated. I'm afraid that it couldn't be used after reboot. Except if the decryption key is linked to my phone (hardware) and not the software part (os) of my phone
iostrym said:
Thanks I didn't know that sdcard and SD card weren't the same. My concern is about external memory card (SD card). If not formated. I'm afraid that it couldn't be used after reboot. Except if the decryption key is linked to my phone (hardware) and not the software part (os) of my phone
Click to expand...
Click to collapse
The encryption is permanent since A6, it remains, at least, you can do something about it, using a custom recovery, a custom module, script, or something, nothing that the end user can worry about, for the normal use of the device.
Trying to guess, you did encrypt your SD card, then the encryption key is linked, only to your SD card, the SD card, specially, in newer Android versions, is treated as a privacy media user concern, so every time more, apps can't access to, as easy as the older times, it is RO by default.
Sorry I have difficulties to read and understand your last message as my English is bad.
Especially the second part... I don't encrypt anything myself. I just now that recent version of Android encrypt the sdcard and it couldn't be used in a computer for instance or another phone. So I think that maybe after new rom flashed. SD card won't be read or write from the phone and I will have to format it myself so that I can read it from my phone. Correct ?
iostrym said:
Sorry I have difficulties to read and understand your last message as my English is bad.
Click to expand...
Click to collapse
Probably my English is worse than yours.
iostrym said:
Especially the second part... I don't encrypt anything myself. I just now that recent version of Android encrypt the sdcard and it couldn't be used in a computer for instance or another phone. So I think that maybe after new rom flashed. SD card won't be read or write from the phone and I will have to format it myself so that I can read it from my phone. Correct ?
Click to expand...
Click to collapse
You are again mixing the terms, in the first part, you're saying "...recent version of Android encrypt the sdcard" and linking to the second part, you're saying "...after new rom flashed. SD card won't be read or write"
As I said to you previously /sdcard AKA internal storage is not encrypted at all, at any time, the fact that you need to authorize the MTP connection within your device and a PC, doesn't change that, if you or anyone else, have access to the Android interface, then you or anyone else, can see all the data/files/pictures/audio/video stored, in the internal storage, by using a file manager app, or a specific app for every file instance/format, i.e. a music player for videos/sounds/musics, a gallery app for pictures/images, and so on.
As per the SD card, the same, if the user (you, in this case), didn't encrypt it, then, Android, also, doesn't encrypt it, so you and anyone else, can access to the data stored in it, either during the OS functioning normally, and/or after the flashing/formatting process.