Hello,
My phone gets automatically encrypted which forces me to delete all the data and flash rom via sidelod,
Even after doing that on fresh install it gets encrypted.
I found a guide on youtube but it is for android N but i'm using OB25 Oreo
please help me to decrypt my phone. so that I can easily flash other roms
That is what we call force encryption. Magisk and SuperSU both disable this by default. But it really shouldn't be a problem to flash a rom while being encrypted. Are you on the latest Bluspark TWRP? When switching roms it is always recommended to fully clean install anyway.
Encryption is not a problem with custom roms: a data wipe from TWRP can't remove it because the recovery delete content instead of doing a format, like happens in other partitions (i.e. /cache).
Just to keep encryption.
In fact if you choose to require pattern at bootup, even after a clean installation that pattern will be required with every rom.
If you want to remove encryption the solution could be a fastboot format userdata command via PC, or going to TWRP > Wipe > Advanced Wipe > Repair or change filesystem.
But OOS forces encryption at first boot, so to solve it, you need to install OOS together with Magisk.
I suggest you to install Magisk v14.2 beta, because v14.0 has systemless hosts issues with OxygenOS.
As recovery, nowadays only TWRP blu_spark v47 and upper version is compatible with OB25.
Oxygen OS encrypts the phone.
On Settings > Security, allways show me <phone encrypted> , on my phone. Never got pin or pasword.. My phone works with no restriction.
Device: XiaoMi Mi 6
ROM: MIUI 9 China Developer 8.3.15
State: Unlocked + USB Debugging
So I tried to install TWRP 3.2.1.0 Sargit + OpenGApps ARM64 8.0 Micro + MagiskSU/SuperSU into the device
From all four of those, I only successfully installed TWRP but not really usable
******no-verity-opt-encrypt-5.1.zip is longer usable for the new update (tried to install and failed)
Here is the problem I'm facing:
1/ TWRP is installed, Format Data helps the Internal Storage to be usable but it keeps go back to 0MB after a reboot to the system then back to TWRP again, causing this to be impossible to flash anything after a system reboot without a Format. Tried Wipe Cache, System (re-flash ROM, stupid me), Data, and the rest, changed File System to EXT4 and the EXT3 and still did not work. And this is what I received when trying to install something if Internal Storage is 0MB.
HTML:
Could not mount /data and unable to find crypto footer
Unable to mount storage
Failed to mount '/data' (Invalid argument)
2/ Used TWRP and ADB (Format everytime so I could not put anything into the storage) to flash OpenGApps and the outcome is it booted into the system and 5 seconds later, it shows something similar to 'com.systemui has stopped working', should be the Google framework. Booted back into TWRP, performed a Format Data and the same thing happened. (so, re-flashed ROM)
3/ Installed MagiskSU or SuperSU (followed instruction step-by-step) through TWRP and ADB and System won't boot up through Power button, Reboot System of TWRP. MagiskSU led me back to TWRP after Boot and SuperSU simply bricked my device. (re-flashed ROM again)
So clearly, I have Root access from the China Dev ROM itself, but it does not really do the job.
I am in China so I want to use some China ROM's features and apps which cannot be downloaded from any appstores I can find from Global ROM.
I have not tried Rooting the Latest Global ROM, yet. So I don't know the result but I'm sure want to use China ROM instead!
Have not tried wipe system and flash official ROM zip from MIUI with TWRP but I guess it won't change.
And lastly I have data in Google and I need Google services so I can access those apps.
If anyone knows how to perform a fix for any of the above, I would be very appreciate!! I had spent a whole day trying to deal with this but it seems like!!!
1, I guess you installed wrong TWRP, you should donwload TWRP from here https://forum.xda-developers.com/showpost.php?p=75326288&postcount=90, this one can de-crypt Oreo Data partition.
2, Don't flash opengapps on any China rom, just download all needed apks from apkmirror and install them. If then you see play service FC, try to disable MIUI Optimization from Developer Options and set Selinux to passive mode. You can also flash xiaomi.eu rom, they are based on China rom but have gapps embedded. BTW, xiaomi.eu 8.3.15 beta and 9.5.3.0 stable supports xposed Oreo beta2.
Today I tried something new, and that was to flash a GSI image onto my Moto Z2 Play 01 variant. Everything flashed fine without errors, but the issue came up when trying to boot...
Steps I took:
1) Flash Treble TWRP Recovery
2) Advanced Wipe (Dalvik / ART Cache, System, Data, Internal Storage, Cache)
*Everything wipes fine
3) Flash RR-O-v6.2.1-20190112-albus-Unofficial.zip, which allows Treble support
*The ROM can boot on its own
4) Flash either of these GSI images (Resurrection Remix Android 9(I tried both the arm64-aonly... & arm-aonly...), SYBERIA OS Android P, Havoc OS, Lineage OS 16 as the System Image )
*Wiped cache/dalvik
5) Flash boot-radium-fpkeys.img, which was used as the Android 8.1 Kernel... as Boot
6) Reboot System
After the boot animation plays I either:
- Get a screen that asks for a password and then says "Decryption Unsuccessful The password that you entered is correct, but unfortunately your data is corrupt.", even if I just put in random characters.
- Immediately get a screen with the same above message without the screen asking for a password
After reading the replies for all the other GSI's I have come to the conclusion that nobody else is having this issue.
Wondering if anyone would have a fix or know what would be causing this.
Obviously I've had this problem at first. But I had set up the wrong 8.1 ROM. I fixed this and format data in TWRP and solved this problem
BeeTLeApp said:
Obviously I've had this problem at first. But I had set up the wrong 8.1 ROM. I fixed this and format data in TWRP and solved this problem
Click to expand...
Click to collapse
What do you mean by "set up the wrong 8.1 ROM"? Could you tell me which ROM your used originally and which one fixed it?
Dubstepwolf123 said:
What do you mean by "set up the wrong 8.1 ROM"? Could you tell me which ROM your used originally and which one fixed it?
Click to expand...
Click to collapse
first used pixel experience,it was wrong for me. you have already used treble rr. Try Format Data in TWRP. if it doesn't work,you can try another ROM if you want
https://download.mokeedev.com/?device=albus
Fixed
Found out that all I had to do was:
1) Enter TWRP
2) Press 'Wipe'
3) Press 'Format data)
4) Type 'yes' and then hit enter
Encryption was removed and all booted well!
Recently any ROM I use and set a password on when I restart my phone the password will no longer work.
Then I have to reflash. So currently not using any password protection.
Again. Thus happens on every ROM for me
Anyone?
deltadiesel said:
Recently any ROM I use and set a password on when I restart my phone the password will no longer work.
Then I have to reflash. So currently not using any password protection.
Again. Thus happens on every ROM for me
Click to expand...
Click to collapse
Have run into this as well a number of times on H812 UsU device with LineageOS 15.1 installed
No need to re-flash the rom (initially) to be be able to disable the password lock screen. Manually boot into TWRP > Advanced > File Manager > Data > System > delete locksettings.db (the only one present in my installed rom) - some roms may have additional files present: refer to https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008 (omission of these, possible reason why this might be occurring ... ?).
Something to try remember is to remove your password before backing up the rom in TWRP or flashing a new rom or a new version.
@steadfasterX
Note: A clean install (wiping Cache Dalvik cache, System and formatting data) doesn't seem to help overcome this issue in the long run, so I suspect the issue resides in the latest version of the roms as it didn't appear in earlier versions.
sdembiske said:
Have run into this as well a number of times on H812 UsU device with LineageOS 15.1 installed
No need to re-flash the rom (initially) to be be able to disable the password lock screen. Manually boot into TWRP > Advanced > File Manager > Data > System > delete locksettings.db (the only one present in my installed rom) - some roms may have additional files present: refer to https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008 (possible reason why this might be occurring ... ?).
Something to try remember is to remove your password before backing up the rom in TWRP or flashing a new rom or a new version.
@steadfasterX
Note: A clean install (wiping Cache Dalvik cache, System and formatting data) doesn't seem to help overcome this issue in the long run, so I suspect the issue resides in the latest version of the roms as it didn't appear in earlier versions.
Click to expand...
Click to collapse
Definitely a ROM bug...that file must go corrupt
Thanks now I don't need to reinstall all the time
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but nothing has worked for OOS 12. I am able to extract the OOS 12 stock recovery.img with Payload Dumper, and am able to create a basic TWRP device tree for android 12.1 using the official TWRP 12.1 Github manifest, but I'm not able to find a good guide to create a TWRP-ready device tree from my stock recovery.img I mentioned earlier. I've tried updating to OOS 11, and using the twrp-keep module on the magisk modules github to keep the official TWRP installed. (It support OOS 11, but not OOS 12). I've also tried flashing the unofficial build made by Mauronofrio, but none of the specified methods have worked. Can someone please either make a OOS12-compatible version of TWRP for the OnePlus 7T, or if they can't do that, guide me in a step-by-step process on how to do i myself? Any help would be greatly appreciated.
Oos12 does NOT support twrp nor does A13
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
I just flashed it, and it booted successfully! I'll let you know if I can format /data.
Format /data works.
For confirmation, I flashed the .img of the OOS12 version to the recovery partition.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
SiegeDaBoss said:
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
Click to expand...
Click to collapse
I just tested the non-OOS Android 13 TWRP file, and it has the same issue.
Can u back up all partitions except data? At least that would be helpful
HueyT said:
Can u back up all partitions except data? At least that would be helpful
Click to expand...
Click to collapse
Nope. Even when I de-select Data, and select everything else, it still fails with the "Failed to mount /data" error.
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
HueyT said:
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
Click to expand...
Click to collapse
I mean, at least both of them boot.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Thank you for testing the builds and for the feedback . I've been on oos11 for a long time, but today I'm going to flash oos12. Because i would need recovery log files to fix errors.
I don't have no time for some fixes, i will try to fix errors whenever possible.
did you not ttry to use the twrp and the twrp installer builds that are on official twrp site for one plus 7t
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Hi again, i updated my repo and download links.
-OOS12 decryption working.
-Flash zip working . "I installed with zip by the Magisk and copy partititon, i flashed los20 & stock oos12 .)"
-Adb sideload working, i tried stock oos12 flashed successfully.
-Format data working.
-Mtp working.
-Otg working.
-Adb working.
-Vibration working.
* Backup data working, but restore data on oos bootloop
* i use swift backup instead of nandroid backup
When i have free time, i will work on twrp a13 fbev2.
mrk2815 said:
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
Click to expand...
Click to collapse
Every ROM comes built-in with its own recovery. So you'll have to flash the ROM via that recovery's ADB Sideload feature.
lets hope you can get a working twrp going for both andrid 12 and 13 .as my one plus 7t is just been put away in my drawer after seeing that one plus has given up on these older devices. when there is a working twrp i would probably want to flash something down the road. my primary driver unfortunately is a samsung S21 plus .
rabilgic said:
Hi again, i updated my repo and download links.
OOS12 decryption working.
Mtp working.
Adb working.
Vibration working.
I installed with zip by the Magisk and copy partititon.
Backup/restore boot.img working.
I haven't tested: flash rom, format data, needs some testing
When i have free time, i will work on twrp a13 fbev2.
Click to expand...
Click to collapse
All works until I tried to restore. Then it got stuck at red dot going around in circle. When I tried to go back in twrp again to format data, it won't mount data after that. Ended up having to restore all over using msmtool.
It mounted data fine before I tried to restore the data part, then it messed up decryption of data despite not having a lock code, no fingerprint, no pattern-lock, or lock screen enabled.