Database Develop

Phone became problematic and asking to decrypt data!

Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?

Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?

thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!

Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk

Flash oxygen os 5.0.5 on OP3T with magisk using TWRP ??

Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..

I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??

Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??

2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)

deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk

RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.

I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!

OnePlus 3t with lineage os encryption doesn't work

Is it just me with this issue? Any known fixes or something? I'm using lineage os version 15.1 with latest update that released today.

i got it too. i always encrypt on lineage OS and omni, today i don't remember what last build i was on but i cleaned my phone and installed latest LOS, after that i can't encrypt my device anymore. even i tried older builds of LOS, NLOS and also OMNI. i can't encrypt my device anymore.
I formatted Data many times and formatted everything but still can't encrypt. anyone can solve this issue?
---------- Post added at 03:45 AM ---------- Previous post was at 03:10 AM ----------
just figured out the problem, problem was in TWRP 3.2.3-1. please install 3.2.3-0, and problem solved

I also have this issue on 15.1-20190127-NIGHTLY-oneplus3, has anybody got a fix yet?

Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Here's what I would do in your situation:
0. Take a backup of your current rom and internal storage and save it on your PC.
1. Try a different rom to see if it can encrypt your phone, eg Los 16 beta from https://androidfilehost.com/?w=files&flid=285406&sort_by=date&sort_dir=DESC
See: https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post78144505
If that works, you're done and can restore your backup. If not ...
2. Do a clean install of OOS 5.0.8 full zip from https://www.oneplus.com/support/softwareupgrade
Don't flash Magisk or custom kernel. Let the phone reboot normally. Check that the phone is encrypted.
OOS forces the storage to be encrypted. It will also replace TWRP, but you can flash it (use the version mentioned in the next step) after the phone has booted.
If this doesn't give you an encrypted phone then:
3. !!!This step will complete wipe your data partition (including user storage)!!!
Use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112 and tap the Format Data button under the Wipe menu. Do not use the Advanced Wipe option.
This should give you a properly formatted data partition with the correct encryption space.
I would flash stock OOS 5.0.8 at this point and boot it to get a properly encrypted phone (I did this when I was testing this version of TWRP and it works).
You can then restore your data backed up in step 0. Also restore TWRP (the version mentioned above) and restore your backed up rom.
For discussion and info on this version of TWRP see https://forum.xda-developers.com/on...ial-twrp-touch-recovery-t3742894/post78661632
You could just do steps 0 and 3, but that's a fair bit of time and effort, which is why I suggested steps 1 and 2.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.

da_n said:
Appreciate your advice appreciate, not sure what the OP would think but I wish I didn't have to flash different image and/or wipe, will see how I get on though.
Click to expand...
Click to collapse
At this stage I trust OOS more than the custom ROMs to correctly encrypt my phone. Once it's encrypted I'm happy to use custom ROMs.
Also, this is my personal view, so others may have different views.
You could, if you wanted, just install a custom rom after formatting the data partition and see if that works.
Sent from my OnePlus3T using XDA Labs

[Guide] Decrypt OnePlus 7 Pro

In this guide I will show you how to decrypt this phone
You might be asking:
(What are the advantages of decrypting?)
Well, it is much easier to switch between custom roms when you are decrypted and you don't have to wipe internal storage everytime you flash a new rom and there may be a performance increase (Maybe).
(What are the disadvantages of decrypting?)
If your phone gets stolen.. The stealer can access all of your data and can even remove the pattern by just rebooting to twrp and deleting a few files so your phone will not have any protection whatsoever.
Downloads:
Disable Dm-Verity
Magisk
Instructions:
1- You have to be on clean oos without any mods or kernels.
2- Reboot Recovery
3- Format data (Go to wipe - Format data and click yes)
4- Reboot Recovery
4- Flash No Verity Mod
5- Flash Magisk
6- Reboot System
Now you are decrypted!!
Keep Decrypt between OS updates:
-Reboot Recovery
-Flash FULL ZIP in TWRP
-Without booting the OS: Flash TWRP Recovery, reboot recovery, Flash No Verity Mod, Flash Magisk, Reboot System.
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
Credits:
@topjohnwu
@Zackptg5

How would I know if I'm decrypted or not?

mlock420 said:
How would I know if I'm decrypted or not?
Click to expand...
Click to collapse
Settings, security, down towards the bottom it tells you

OK so I'm encrypted... Am I secured somewhat from theft correct? And yes I know it's not 100% but it is safer than decrypted?
Another question let's say I don't mind being encrypted because I have a flash drive with otg and all that... Is that good enough? Or should I go decrypted all the way so I can start backing up on twrp and restoring twrp without errors which would mean no use for flash drive...
I know it's my choice just trying to make things easier and to understand a little more

mlock420 said:
OK so I'm encrypted... Am I secured somewhat from theft correct? And yes I know it's not 100% but it is safer than decrypted?
Another question let's say I don't mind being encrypted because I have a flash drive with otg and all that... Is that good enough? Or should I go decrypted all the way so I can start backing up on twrp and restoring twrp without errors which would mean no use for flash drive...
I know it's my choice just trying to make things easier and to understand a little more
Click to expand...
Click to collapse
If you are really concerned about your data and you are OK with wiping internal storage, then I don't recommend decrypting and just leave it encrypted.

I have oos decrypted via disable force encrypt!
Today I went through the following process to update to the latest version of OOS.
1. Flash full oos & twrp
2. reboot to recovery
3. Flash magisk
4. flash disable force encrypt
5. reboot
rebooted, but back to TWRP,,,
there was a "0" directory in sdcard and inside it my data was in it.
Do you know the solution?
thx

download link is not working for the file.

cylent said:
download link is not working for the file.
Click to expand...
Click to collapse
XDA thread:
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Downloads:
https://zackptg5.com/android.php#disverfe
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_12.27.2019.zip

Hi omar2005
May i ask you a quetion?
I just will get my oneplus 7 pro.
Under android 10.
During first time rooting and twrp install. Should i reboot recovery and flash decrypter or first finishing rooting than rebooting system and than do the steps like you said in your Instructions?
Thank you for orientation and greetings ivifly

You have to flash dfe before booting system. Once system boots, you'll be encrypted

Avril09 said:
You have to flash dfe before booting system. Once system boots, you'll be encrypted
Click to expand...
Click to collapse
What is DFE?
Sent from my OnePlus7Pro using XDA Labs
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Is there a way I could reencrypt(due to security concerns) without having to wipe my data? The option in security is greyed out :/.
Thank you
Sent from my OnePlus7Pro using XDA Labs

fp1707 said:
What is DFE?
Sent from my OnePlus7Pro using XDA Labs
---------- Post added at 09:18 AM ---------- Previous post was at 09:17 AM ----------
Is there a way I could reencrypt(due to security concerns) without having to wipe my data? The option in security is greyed out :/.
Thank you
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
DFE is Disable Force Encryption also known as dmverity in some cases.
And yea you can reencrypt without losing data but it takes time depending on the size of files you have.

omar2005 said:
In this guide I will show you how to decrypt this phone
You might be asking:
(What are the advantages of decrypting?)
Well, it is much easier to switch between custom roms when you are decrypted and you don't have to wipe internal storage everytime you flash a new rom and there may be a performance increase (Maybe).
(What are the disadvantages of decrypting?)
If your phone gets stolen.. The stealer can access all of your data and can even remove the pattern by just rebooting to twrp and deleting a few files so your phone will not have any protection whatsoever.
Downloads:
https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Instructions:
1- You have to be on clean oos without any mods or kernels.
2- Reboot Recovery
3- Format data (Go to wipe - Format data and click yes)
4- Reboot Recovery
4- Flash No Verity Mod
5- Flash Magisk
6- Reboot System
Now you are decrypted!!
Keep Decrypt between OS updates:
-Reboot Recovery
-Flash FULL ZIP in TWRP
-Without booting the OS: Flash TWRP Recovery, reboot recovery, Flash No Verity Mod, Flash Magisk, Reboot System.
Keep Decrypt between Roms:
-Wipe Data only in twrp!!! (NEVER WIPE SYSTEM OR - VENDOR ON OP7P)
-Flash Rom
-Flash TWRP
-Reboot Recovery
-Flash any other zips you want like Gapps-Kernels- ex.....
-Flash No Verity Mod
-Flash Magisk
-Reboot System
Credits:
@topjohnwu
https://forum.xda-developers.com/member.php?u=4470081
@Zackptg5:
https://forum.xda-developers.com/member.php?u=6037748
Click to expand...
Click to collapse
can we use this method for boot dual os (oos+custom) , when we install dual os twrp by @Zackptg5 we face problem with encryption and password protection on one of the os.
is it possible this method help this problem???

This does not work for my OP7Pro, when you say boot into Recovery and wipe data. Is that the stock recovery or TWRP? When I try decrypting using the instructions using TWRP, when I reboot the phone, it boots into the boot animation. But the animation is slow and the phone just gets stuck there and won't boot any further. Trying to decrypt so it's easier to get LineageOS installed. My phone seems to have problems when on the B partition reading the internal storage.

Scotsman828 said:
This does not work for my OP7Pro, when you say boot into Recovery and wipe data. Is that the stock recovery or TWRP? When I try decrypting using the instructions using TWRP, when I reboot the phone, it boots into the boot animation. But the animation is slow and the phone just gets stuck there and won't boot any further. Trying to decrypt so it's easier to get LineageOS installed. My phone seems to have problems when on the B partition reading the internal storage.
Click to expand...
Click to collapse
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.

H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
No, my phone was on a main build. Just wasn't having any luck and gave up. I'm on LineageOS now but spent an entire day trying to get that installed and working properly. Something was weird, slot A could read my internal storage, but when I switched to slot B the internal storage just disappeared. Once I got TWRP and LOS installed on both slots, the problem disappeared. But I still haven't attempted to decyrpt for fear of messing up my current setup.

H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
It still works for me to this day tbh, on any rom i flash except some problems with android 11 roms ...

H4X0R46 said:
Are you running an open beta build? OnePlus did something dumb with the beta builds where this no longer works. I've been racking my brain trying to find a way to decrypt a beta too. For now, only the main builds of OOS are decryptable.
Click to expand...
Click to collapse
I'm on OOS 11 Beta 1 and decryption works fine for me. I was on 10.3.7 (decrypted) before.

Do you have to be on OOS? Or could any clean flashed rom work?

who can help. i cant decrypt my op7t pro. Well, let's start with the fact that when formatting dalvik cache and data, I have an error and nothing is formatted. as with (Go to wipe - Format data and click yes). Formatted this data via adb, installed No Verity Mod and now I have bootloop

Bootloop after updating Magisk

I updated my Magisk from 18.1 to 19.3 (got a notification that an update was available) and then installed it, rebooted and then Orangefox (recovery) installed the update if I remember correctly. Then after that I have not been able to get past the bootloop. I've tried to uninstall Magisk but I am still stuck in bootloop everytime. Orangefox says I don't have Magisk installed anymore so why am I stuck in bootloop? What can I do? I don't want to lose any data.
I have a Xiaomi redmi note 7, Android 9

thisfieldismandatory said:
I updated my Magisk from 18.1 to 19.3 (got a notification that an update was available) and then installed it, rebooted and then Orangefox (recovery) installed the update if I remember correctly. Then after that I have not been able to get past the bootloop. I've tried to uninstall Magisk but I am still stuck in bootloop everytime. Orangefox says I don't have Magisk installed anymore so why am I stuck in bootloop? What can I do? I don't want to lose any data.
I have a Xiaomi redmi note 7, Android 9
Click to expand...
Click to collapse
Did you try dirty flashing your ROM zip via recovery? And did you try the latest Magisk Uninstaller zip?
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
Did you try dirty flashing your ROM zip via recovery? And did you try the latest Magisk Uninstaller zip?
Sent from my #FlagshipKiller6T using Tapatalk
Click to expand...
Click to collapse
Yes, I did try the latest Magisk uninstaller zip thru Orangefox and it went fine but still stuck in bootloop.
I haven't done a dirty flash yet (I am new to the custom rom scene), will that keep my data, settings, app data etc?

thisfieldismandatory said:
Yes, I did try the latest Magisk uninstaller zip thru Orangefox and it went fine but still stuck in bootloop.
I haven't done a dirty flash yet (I am new to the custom rom scene), will that keep my data, settings, app data etc?
Click to expand...
Click to collapse
Yes. Just install the ROM zip file again & after that press "Wipe Cache & Dalvik" button and reboot.
Sent from my #FlagshipKiller6T using Tapatalk

DarkSJ1998 said:
Yes. Just install the ROM zip file again & after that press "Wipe Cache & Dalvik" button and reboot.
Sent from my #FlagshipKiller6T using Tapatalk
Click to expand...
Click to collapse
Sadly it is still in a bootloop.... What to do? I did a dirty flash of only the rom (no magisk or custom kernel). What to do?

thisfieldismandatory said:
Sadly it is still in a bootloop.... What to do? I did a dirty flash of only the rom (no magisk or custom kernel). What to do?
Click to expand...
Click to collapse
You need to recall what else you changed when you flashed Magisk v19.3. Otherwise, there's no other way than clean flashing it. You can take a TWRP backup of /data & try restoring it after a clean flash via TWRP or TitaniumBackup allows restoring data from a TWRP backup.
Sent from my #FlagshipKiller3T using Tapatalk

DarkSJ1998 said:
You need to recall what else you changed when you flashed Magisk v19.3. Otherwise, there's no other way than clean flashing it. You can take a TWRP backup of /data & try restoring it after a clean flash via TWRP or TitaniumBackup allows restoring data from a TWRP backup.
Sent from my #FlagshipKiller3T using Tapatalk
Click to expand...
Click to collapse
OK, I did upgrade the custom rom I had (the update worked fine, no problems as I could see) , and then after that I updated magisk.
Which checkboxes should I tick to ensure that I can restore a backup without problems? Mainly hoping to backup app data, settings, app settings etc (photos or music is not needed). Thanks in advance ?

thisfieldismandatory said:
OK, I did upgrade the custom rom I had (the update worked fine, no problems as I could see) , and then after that I updated magisk.
Which checkboxes should I tick to ensure that I can restore a backup without problems? Mainly hoping to backup app data, settings, app settings etc (photos or music is not needed). Thanks in advance [emoji120]
Click to expand...
Click to collapse
Backup /data mainly. That houses all the apps ' their data. After doing a clean flash, you can try restoring /data. If it still causes a bootloop, then you have no other option other than restoring App data individually using TitaniumBackup or any other similar app.
Sent from my #FlagshipKiller6T using Tapatalk