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.
Related
Can TWRP backup encrypted phones?
Because since it has been encrypted, it is failing. I'd like to make a backup before I try installing a new ROM.
automatism said:
Can TWRP backup encrypted phones?
Because since it has been encrypted, it is failing. I'd like to make a backup before I try installing a new ROM.
Click to expand...
Click to collapse
Same here. TWRP cannot access /data
Would it be possible with CWM recovery?
If encrypted, you need to make sure you enter your encryption password right when it asks in TW recovery. This will allow TeamWin to decrypt the drive and be able to back it up.
thehayk said:
If encrypted, you need to make sure you enter your encryption password right when it asks in TW recovery. This will allow TeamWin to decrypt the drive and be able to back it up.
Click to expand...
Click to collapse
It's never asked me for a password
automatism said:
It's never asked me for a password
Click to expand...
Click to collapse
It depends on which TWRP version you have.
Sent from my GT-I9001 Gadget of Mass Destruction with CM11 using XDA Developers App.
What version of TWRP would I need? I have v2.8.1.0 and I've never been asked for the password.
hnkotnis said:
It depends on which TWRP version you have.
Sent from my GT-I9001 Gadget of Mass Destruction with CM11 using XDA Developers App.
Click to expand...
Click to collapse
Mersine said:
What version of TWRP would I need? I have v2.8.1.0 and I've never been asked for the password.
Click to expand...
Click to collapse
At backup screen where you select the partitions (system, data etc). There is options called as encrypt backup.
This is available for TWRP v2.8.1.0 on my Samsung Galaxy S Plus GT-I9001.
Press Thanks if helped.
Since Googling "twrp backup encrypted phone" puts this thread as the number one result, I'd like to offer up that this doesn't work. The encryption password looks to me to be for encrypting the backup file itself, not for decrypting /data. As near as I can tell, the only way to back up /data is to use a tool such as Titanium Backup, although I haven't tried that yet myself, I am about to.
hnkotnis said:
At backup screen where you select the partitions (system, data etc). There is options called as encrypt backup.
This is available for TWRP v2.8.1.0 on my Samsung Galaxy S Plus GT-I9001.
Press Thanks if helped.
Click to expand...
Click to collapse
This is NOT what OP requested. He (we) want to backup an encrypted device, that is our /data is encrypted and twrp is unable to mount it (confirmed by the dev themselves.) to be clear: there is no twrp or cwm version able to mount encrypted /data so far.
Is this available?
Stopgap ways of backing up encrypted phones?
So I've been researching this problem for some time now, and I've got a couple suggestions.
CAVEAT: I haven't tried any of this yet.
First, there is Online Nandroid Backup. Since it backs up while the phone is running, the encrypted partitions should be available to it. But I suspect it restores while the system is running, which kind of defeats the purpose -- with a Nandroid backup, you can take a non-working phone and flash it back to the same condition when it did work. That's the whole point of wanting it, because testing ROMs is a lot easier.
Second, I'm experimenting with a way to do this with a dd command in an ADB shell. Basically you would execute a command like this:
dd if=/dev/block/mmcblk0p32 of=/storage/sdcard1/userdata.img
Then that could, theoretically, be flashed back using fastboot flash userdata userdata.img. This is tricky, though, because you have to manually find your partitions and their equivalent names, etc. Also, fastboot doesn't work on all phones....
The one thing that is certain: CWM/Philz/TWRP all fail at event mounting the /data partition, much less backing it up. And (I think) an ADB backup is not going to work because it only applies to apps and their data, not the system itself, or its settings.
It makes you wonder how people with encryption make whole-phone backups in case something goes wrong (or if they do it at all). Sure, there's Titanium Backup, but that's one app at a time. Anyway, if I find out anything more useful while testing these ideas, I'll post it here.
Thanks for pointing me in the right direction. I just did that in the TWRP console.
You can find out your device partitions with
Code:
cat /etc/fstab
.
Then use dd as previously specified, but use an external sd card as the target:
Code:
dd if=/dev/block/mmcblk0p36 of=/external_sd/userata.img
.
This will take a while. Depending on the size of your /data partion quite a while. And there is no progress indicator.
Edit: Actually you can monitor the progress over adb. Just open an adb shell and do a
Code:
ls -al /external_sd/userdata.img
. The current size of the file gives an indication for the progress. In the end the file will have the same size as the data partition.
You can also enter the commands through adb to begin with... makes typing much easier.
I'll get around to testing these idea at some point, but for now I've had to (re)build this phone 4 times since August... so once it started looking solid again, I decided on Online Nandroid as my solution for now. It should give a workable restoration no matter what (but it will need a full wipe to clear encryption beforehand).
I'm curious as to what will happen when you fastboot flash that image file back on to the phone, though. I wonder if it's still encrypted and works, or isn't encrypted and works, or doesn't work at all.
There's also the disparity between the state of the filesystems on /system and /data if they're backed up at times too far apart. That one won't be apparent until something breaks, I think.
via XDA Mobile (D415)
I haven't gotten around to restore the image yet. I don't know whether this will work through fastboot, but it should definitely work with dd again from the recovery, this time from the image to the /data partition.
And the file system is certainly still encrypted, it wasn't ever decrypted.
I have to go back to the stock ROM on my phone for a moment, I'll report back if I could restore the dd image file.
BubuIIC said:
I haven't gotten around to restore the image yet. I don't know whether this will work through fastboot, but it should definitely work with dd again from the recovery, this time from the image to the /data partition.
And the file system is certainly still encrypted, it wasn't ever decrypted.
I have to go back to the stock ROM on my phone for a moment, I'll report back if I could restore the dd image file.
Click to expand...
Click to collapse
Theoretically, a dd image is an exact copy of the partition, and can just be dropped right in there. So yes, it should still be encrypted... unless flashing it back somehow munges the footer on /userdata, which the phone needs for encryption (I've seen this happen, and it actually caused a bootloop; thankfully, I was able to fix it). But I am hopeful it works when you try it.
Also, I spoke to a guy today who said his phone has no problem backing up encrypted partitions. In fact, his recovery asks for a password before running. I had him specifically confirm that his whole phone is encrypted, not just the backup file. He says his version is 2.7.1.0 running on a Nexus 4 (mako).
So now I've gotta find that version, and I think it has to be customized for the L90 too. I'll post request in that thread and see if I can get ahold of it.
via XDA Mobile (D415)
Bump
Last post in here made it seem like yes for some phones, and no for others. I'd love to encrypt my phone, but not if it means I can't make a nand backup in TWRP. Anyone want to chime in and see if this answer has become more definitive in the last 9 months?
jfsat said:
Last post in here made it seem like yes for some phones, and no for others. I'd love to encrypt my phone, but not if it means I can't make a nand backup in TWRP. Anyone want to chime in and see if this answer has become more definitive in the last 9 months?
Click to expand...
Click to collapse
I have Cyanogenmod cm-12.1-20150901 and TWRP 2.8.5.0
Once I encrypted the device, TWRP prompts for a password when it starts. However, when I type the passphrase, it says:
Password Failed, Please Try Again
forrestgump2000 said:
I have Cyanogenmod cm-12.1-20150901 and TWRP 2.8.5.0
Once I encrypted the device, TWRP prompts for a password when it starts. However, when I type the passphrase, it says:
Password Failed, Please Try Again
Click to expand...
Click to collapse
Did you ever find a solution for/to this?
Nandroid backups using TWRP Works with Nexus 7
I had an issue with this, too. I'm using CM 12.1.
First, make sure that you've flashed the latest TWRP for your device.
The issue was that the whole disk encryption is tied to the lock screen password/PIN/pattern.
So, I changed my lock screen to a password ensuring that it must also be used to start up Android. This changed both the lock screen and the whole disk encryption password to the same password. Now, when I reboot into recovery, TWRP requests a password and I supply the password that I changed my lock screen to. This allows /data to be mounted. A backup can be done on the internal storage or you can mount a USB storage device backing up the Nandroid images there instead.
Hope this helps.
****Confirmed this works with Android 6.0 from Google.
cableghost said:
Did you ever find a solution for/to this?
Click to expand...
Click to collapse
Nope. But I also don't use an Android phone anymore, so I haven't been looking.
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 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 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)
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
tzagaritos said:
Is there anything way that i can disable data encryption? Both TWRP and orange fox not allow me to install anything and asking for password, i tried both lock password and mi password but nothing. I am trying to root my phone, i also tried to make a patched boot image with magisk manager but not install button was showing up.Any solution?
Stock rom with miui global 10.3.1.0 version
Click to expand...
Click to collapse
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
SubwayChamp said:
Don´t waste your time trying to decipher the password, they´re advanced algorithms that Android uses to make the Encryption-By-Default to protect data user not a personal password that can be easily decoded.
You can flash any zip using adb sideload through Advanced options in recovery, the problem would be trying to boot up due to AVB implementation, I never cared about format data when is needed so my important files I ever have on my external SDCard.
Some members refer that such recovery can decrypt data or not, this is not a problem by its own but the ability to boot. The simple way to decrypt data is formatting it.
As a side note decrypt data will be required just in some cases like when you unlocked for first time, when you are coming back to a Miui upgraded rom then to an AOSP one but most of custom roms based on Miui don´t have encryption like ROS, Xiaomi.eu or Mi-Globe.
Click to expand...
Click to collapse
thanks a lot , i did not know that i could flash zip files in that way, you saved me thanks again
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
borg4571 said:
use the custom TWRP by wzsx150, decryption is working with that one https://forum.xda-developers.com/mi-8-Lite/development/mi-8-lite-twrp-t3850019
Click to expand...
Click to collapse
Is possible to send me the img file through Google drive or anything familiar;its a mess trying yo download from the Chinese site
I have Android pie