Hello everyone, it's very much time that I want to know the speech about decrypting my Nexus 5X. Now I'm stay with PureNexus and ElementalX, but if I go on Security > Cryptography, my phone is encrypted even if when I flash TWRP 3.0.0 , appeared decrypted.
Now I don't know if my device is decrypted or not. There is a detailed guide that I can follow so that I can permanently unlock my device?
Thanks to all
If you see in settings - security that your device is encrypted, it is... If you want to decrypt it you have to format /data and your internal storage.
1. Backup all your data
2. Dowload FED Patcher here and copy the zip to your device
3. Reboot into recovery
4. Wipe system
5. Reflash your rom, gapps and the fed patcher.zip
6. Do a factory reset and (!) format /data.
Reboot your phone, et voila, you are unencrypted.
Be sure to reflash fed patcher every time you update your rom, otherwise it will be encrypted on first boot without fed patcher.
Donald Nice said:
If you see in settings - security that your device is encrypted, it is... If you want to decrypt it you have to format /data and your internal storage.
1. Backup all your data
2. Dowload FED Patcher here and copy the zip to your device
3. Reboot into recovery
4. Wipe system
5. Reflash your rom, gapps and the fed patcher.zip
6. Do a factory reset and (!) format /data.
Reboot your phone, et voila, you are unencrypted.
Be sure to reflash fed patcher every time you update your rom, otherwise it will be encrypted on first boot without fed patcher.
Click to expand...
Click to collapse
When you flash ROM , gapps and patcher , and then do a system reset and format / data , the system does not start or not? But then formatting / data is getting through TWRP ? Thank you
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Vitriol_Drinker said:
Well simply, can it be done ?
I'm currently running 3.2.8 with root & twrp with partitions encrypted.
I want to upgrade to 4.0.1, convert to F2FS, keep root & twrp and still be encrypted.
I've read that a new version "blu spark" of the recovery has been released, is this the key to what i want to do ?
If you could provide a foolprof how to, this would be amazing.
Click to expand...
Click to collapse
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
let92 said:
I also want to flash OOS 4.0 based on Nougat, but I want to do a clean flash and change the file system to f2fs (I come from OOS 3.2.7 rooted with official TWRP 3.0.2-1).
So, what I have to do is:
1. make backups of files and apps (I will move files and backup apps with Titanium Backup on my PC or a USB stick) and nandroid backup for evenience (move also it on PC)
2. wipe all (with TWRP or adb?)
3. flash OOS 4.0 Nougat (adb?)
4. flash last stable version of Supersu
5. flash latest TWRP by @eng.stk (with adb?)
Is it correct? The only thing that I can't understand is if I have to use adb or TWRP for flashing, I heard that when you flash the full update the recovery will be replaced with the stock one...
Please help me, I'm looking for trying Nougat
Click to expand...
Click to collapse
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
All right, I'll try this weekend and will post here the result
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery and update through the official OTA Then flash the recovery and root again :good:
Click to expand...
Click to collapse
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
hiredantispammer said:
Flash stock recovery from OP site and flash rom. Don't relock the bootloader. then flash twrp using fastboot and flash supersu. Will require backing up too tho. I tired the method I gave you and it worked well. F2FS is really worth the effort.
Click to expand...
Click to collapse
It seems more simple the @Viper The Ripper's method: in that way I only need to flash the stock recovery, boot the phone (I think the phone will boot on OOS 3.2.7, my actual version), then download OTA (using a VPN to Germany because the update hasn't begun in Italy ), factory reset (will the phone keep Nougat or come back to manufacturer Marshmallow version?), flash recovery by @eng.stk and root phone.
Correct?
AlkaliV2 said:
It cannot.
The switch to F2FS requires wiping of the data partition including internal storage. You might be able to get around this by staying on ext4 when flashing the update, but the newest recovery by eng.stk won't decrypt ext4 from what I've seen in the forums which means you won't be flashing anything afterwards. Also, root won't be kept because it will overwrite the kernel which you'd have to boot back into TWRP decrypted to flash a fix for and so on. Also, f2fs is showing to be much quicker with UFS storage on the OP3/T so you'd be using a slower file system just because you don't want to lose user data. Get a decent backup app, copy your backups to your PC, wipe and install the new OS CLEANLY, put your backups back on internal storage once you are back logged in again, and restore.
tl;dr no.
Click to expand...
Click to collapse
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Viper The Ripper said:
Or... unroot your phone, flash the stock recovery (fastboot mode) and update through the official OTA Then flash the recovery and root your device again :good:
Click to expand...
Click to collapse
Will this work for me ? Applying the OTA won't relock bootloader will it ?
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
sahed01 said:
titanium backup that I took on 3.2.8 isn't restoring on 4.0.1. because F2FS maybe? any solution?
Click to expand...
Click to collapse
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
let92 said:
What do you mean? Titanium give you an error when you try to restore some apps? Or you don't find the backups on your phone?
Click to expand...
Click to collapse
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Only suggestion that i will give is what worked for me. So here is what i did and successfully upgraded from 3.2.8 to 4.0.1 OOS without losing data and keeping encryption on ext4 /data.
1. Keep full OTA zip, and SuperSU latest in the folder or Stable, whatever you want, and the latest recovery by eng.stk v11.
2. Remove security from your phone (pin/password/fingerprint), and Go to recovery flash v11 recovery by eng and reboot to recovery.
3. Wipe system, cache, and dalvik.
4. Flash full OTA, flash TWRP recovery img again. If on rebooting, you find stock recovery, just flash v11 from fastboot again.
5. Don't reboot into system, reboot into recovery again, flash SuperSU zip and make sure SuperSU flashes properly. You need to read the installation process and determine that it flashed properly.
6. Reboot to system, you will have all of your data safe and the way it was in MM.
7. Be careful, the moment you assign pin/pattern/fingerprint security to your device, TWRP would ask for a pattern in recovery and it won't decrypt your data. (Works fine if you are on f2fs). If you are like me and don't flash zips that oftenly, it's good to go.
I hope this method helps. Be sure to remove security from phone before flashing and rebooting as recovery won't work if you have security applied. It's a cheap workaround but it works nevertheless.
sahed01 said:
.
no nothing like that. it's just when I'm restoring any app, it's like titanium backup freezes. *restoring app* for like hours. but nothing actually happens.
Click to expand...
Click to collapse
Maybe Titanium wants the storage permission even if it doesn't ask for it
Try to give it, delete app cache and restart the phone.
Then try to restore one app.
let92 said:
All right, I'll try this weekend and will post here the result
In order to unroot the phone what do I have to do? Also re-lock the bootloader?
Click to expand...
Click to collapse
Go to Supersu apk and choose the option in settings to unroot completly your phone
---------- Post added at 10:07 PM ---------- Previous post was at 10:05 PM ----------
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Will this work for me ? Applying the OTA won't relock bootloader will it ?
Click to expand...
Click to collapse
If you apply the official OTA you won't lose nothig from your current rom
Yes it'll work and nope, applying the OTA won't relock your bootloader :good:
Vitriol_Drinker said:
So people with full stock unrooted/without twrp have to lose all data when upgrading ?
Click to expand...
Click to collapse
People that want F2FS will lose their data converting their filesystems unless they back it up; no method listed in this thread gets around this. All the options listed keeps the users on ext4 because the official OTA does not convert your /data partition to F2FS as shown in the updater script code below from official 4.0.1 full firmware and update file.
Code:
getprop("ro.display.series") == "OnePlus 3" || abort("E3004: This package is for \"OnePlus 3\" devices; this is a \"" + getprop("ro.display.series") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.050000, 10);
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing static_nvbk image...");
package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk");
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak");
package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfgbak");
package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak");
package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
set_progress(1.000000);
You can see that all it does it overwrite the system partition with the new changes, writes the radio file, and flashes the extra firmware to bring you up to speed with nougat. If you want to do this right and be on F2FS you have to do it manually.
Viper The Ripper said:
Go to Supersu apk and choose the option in settings to unroot completly your phone
Click to expand...
Click to collapse
Thank you! I'll try your method so!
hiredantispammer said:
Use Titanium backup or any app of you choice, then move the backups and any internal storage files to a PC. Go to TWRP. When you go to the Wipe section, choose "change or repair file system" and convert data to F2FS (will wipe all data and even internal storage). Copy SuperSU 2.79 stable and ROM zips, and this TWRP IMG to phone from a PC, then flash 4.0.1 zip, SuperSU, and TWRP, and reboot to recovery. Make sure you can decrypt data then reboot to system. Then move back your internal storage files and backups.
Click to expand...
Click to collapse
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
I've managed to do all this and end up wit 4.0.1 with F2FS and no encryption. If I encrypt the phone, it changes the format of the data partition and TWRP won't decrypt it. If I understand this thread, this is to be expected. There is no way to end up with encrypted F2FS that TWRP can decrypt?
Revolised123 said:
Sounds like good plan, but I have one question. Do you need to disable security (fingerprint, patern or code) on forehand to make sure the data can be decrypted?
Click to expand...
Click to collapse
I didn't. Just boot back to recovery after flashing everything. With this TWRP data can be decrypted.
Hey,
I'm new in this kind of stuff but need help as fast as possible. So I tried to root the phone but let me tell you something else. When I enter TWRT (boot into) and try to install the .zip file it shows weird folder names that I can't see on the computer. I have Win10 if this matters and Android 8.0 or 8.0.1. The folders are:
acct
boot
cache
config
cust
data
license
mnt
and it goes like that. The problem is that about 85 or 90% of these folders aren't visible on my computer when I plug in my phone... The System is mounted in TWRP and everything is mounted. I tried wiping all the data. I have unlocked bootloader. Also when I go to some of these folders I see REALLY strange folder names like: 671hnsuh1b%nqjus Or something like. I've found out that it's encrypted but I just want to root the phone and find the .zip file. Also can someone explain me these acct, boot, license, vendor, version and other folders that aren't visible on my PC? Please help. I'm so confused, not clue what's going on...
You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.
kksnis said:
You need to use the format data option to decrypt the internal storage. Better use SD card or USB OTG to flash the root file. Anyway don't wipe the oeminfo or vendor partition in any case and take a backup of all partition beforehand.
Click to expand...
Click to collapse
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1
Aspect13 said:
Well, I already used this option. The format data option and it's still the same. Maybe the version of my twrp helps: 3.1.1-1
Click to expand...
Click to collapse
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers
kksnis said:
Strange. What is the android version?Did you had any lock screen set before formatting? Can you please share a screenshot or log during formatting, if you have any. Anyway you can use adb sideload to flash the .zip file.Cheers
Click to expand...
Click to collapse
My android version is 8.0 so it's oreo. I've also noticed that the 3.1.1-1 version of twrp is the only one from what I tried that I can install the newer versions gave me an error. I had lock screen and it was code not a fingerprint but I wasn't prompt for a code after booting into twrp. Adb sideload seems to fail all the time so I can't do it :/.
The logs from wiping data are:
Updating partition details...
..done
Full SELinux support is present.
MTP Enabled
Starting ADB Sideload feature...
Starting ADB Sideload feature... (And it failed now wipe logs.):
Fomatting Data using mkfs.f2fs...
Done.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
...done
So yea I'm so sad tbh with this... I'll try to install new twrp after the wipe if the wipe didn't help and will tell you if I get an error when I try to boot into NEW twrp.
EDIT: Ye still an error.
Maybe you have a link to the newest working twrp?
Nevermind got it. Downloaded the modded twrp by TEAM MT I guess from here: https://forum.xda-developers.com/honor-8-pro/development/wip-twrp-3-1-1-0-duk-t3625798 Works perfectly and SOLVED!
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.
reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.
reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work
loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?
reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes