Database Info

OP6 stuck in bootloop - how do I fix this?

Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.

LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.

lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
PhilGizzle said:
Hello!
I seem to only post on this homepage whenever I f*** up, and so here I am...
I'll try to explain this as best as possible.
I decided I wanted to root my OP6 so I could cheat in PoGO since the weather turned bad.
I followed a guide precisely - https://oneplus.gadgethacks.com/how-to/root-your-oneplus-6-with-magisk-beginners-guide-0185541/ - this one specifically.
So my phone is now rooted and I've got Magisk and TWRP, everything seems fine. I go to download the Root Checker and it gives me an error that it's not compatible with my device.
I freak out and try out various things inside Magisk Hide to make it work. It eventually works out and "YAY MY PHONE IS IN FACT ROOTED". Although the SafetyNet thing gives me an error.
Okay, I Install PoGo, go to Magisk Hide and select it. Start it up, log in.... Failed.... "Oh no". Failed... Failed... Failed...
Urgh, whatever I think. Let's just get rid of the root and TWRP then. Can't be too hard? Oh Magisk has an uninstall feature, let's hit that up. Uninstalled. Huh? PoGo still not working.
I've spent a few hours now trying to get this to work, my phone is wiped and not really useful. Let's remove TWRP then right? Right??! Steps are simple.
Wipe Phone, get a stock OP6 rom thing.
Press the install button. Nothing happens, wait for 10 minutes. It now asks me to reboot, no errors show up.
Good, it's booting. It's been twenty minutes, still booting... 30 minutes, still booting...
I'm stuck.
I know I screwed up somewhere, but does anyone know what I can do?
I can reboot to recovery, which is stock recovery now.
EDIT: Okay, so I couldn't idly sit by, so I went into recovery and wiped data yet again. It booted up this time and is now asking me to update my OS!
One problem resides, I can't download Netflix, which means I'm tripping the safetynet thing. Is it because my bootloader is unlocked? If so, how do I lock it again?
EDIT2: I really can't sit still. Googled, found out how to lock bootloader. Let's see if Netflix works.
EDIT3: Netflix can be downloaded, so I think everything works as it should again. I'm now installing official updates to my phone. If it breaks, I'll be here again.
Click to expand...
Click to collapse

thefallen924 said:
lol, glad you have everything up again. I remember when i used to go through these scenarios on the regular. Do you want root for any specific reason? i only ask because after years of being rooted, i really feel that the pros no longer outweigh the cons. Once the whole A/B partition thing was introduced (i believe it was in Nougat?), it opened up the doors to a lot of possible issues with softbricking, etc. I'm still here on xda to see if there's anything that will bring back the itch for tinkering/rooting, but for the time being, you can find just about any nonroot alternative to what you might need.
Click to expand...
Click to collapse
It is just different.
You have to forget the "old way" and then you don't face any problems.
Same with encryption that wasn't present before.
I still can't live without root.
Too many missing functions (xpsoed edge, titanium, afwall, xprivacy, gravitybox).
And the newer rom system by just applying a magisk module is pretty cool.

pdppdp said:
LOL.
At least you have a working device again.
Once you unlock your bootloader your widevine level goes to 3 (level 1 is default meaning bootloader locked). There are people reporting to get netflix working but HD streams seem to be broken then so just SD quality.
I guess you messed up with your a/b partitions. This happens when you don't install twrp properly to both slots. Installing means to boot twrp with fastboot and install latest twrp.zip.
After that you flash magisk. Right now to keep dm verity you need to flash magisk 16.0 (stable). After rebooting your system, open magisk switch to beta channel and install latest version (16.7) directly through the magisk app. After reboot you should have dm verity ticked.
For safety.net passing: magisk needs an update due to api changes from safety.net/ google.
If my rom doesn't boot I just reinstall latest oos build, boot twrp and flash twrp.zip, then magisk.
Click to expand...
Click to collapse
hey, i rooted my device yesterday on 10.3.3, all was good until i got into a bootloop after installing busybox from the magisk repo. i keep going back to the fastboot mode, i still have access to twrp but sadly i didnt make a nandroid backup. i really dont know what to do now and i know this is not the relevant thread to ask this question. im sorry, but if anyone knows a method to solve this please let me know. thanks

I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.

pdppdp said:
I would make a nandroid (just in case) now and then flash the full firmware again, reflash twrp and then xxx. This keeps your data and you should have a working system.
Click to expand...
Click to collapse
Make a nandroid of the Bootlooped system? Is it OK to flash the full firmware without performing a factory reset? Thanks...
EDIT- thanks a lot for this method Bro. .worked like a charm and now I'm back into system. .reflashing twrp and magisk now..thanks again

You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'

pdppdp said:
You're welcome.
Nandroid of your data in case something goes wrong and wipes the device. System is 'replacable'
Click to expand...
Click to collapse
Yup that's a good precaution to take in case things go south. Anyways i was reading your earlier post on how unlocking the bootloader sets the widevine level to 3 and causes some problems to use netflix. I was unaware of this issue before i rooted. It's really a bummer, soon after reading your post i realized that netflix was missing and i went to play store to download. I couldn't find the app,then i downloaded the app from apk mirror and after installation i had this error that the device is not supported by the app. I did some research on the issue and on a OnePlus forum i found a solution, i went to the netflix website and logged in with my account, then i tried playing something which indicated me to download the app from play store and viola, the app got downloaded and works perfectly fine, it's kinda surprising. Thought I'd share this here if in case it might work for someone else...

Coming Over From Rooted Marshmallow Galaxy S7 - What Do I Need to Know?

I've got a rooted S7, apps backed up with Titanium Backup, etc.
Is there anything I need to know about getting this transferred over to a Pixel, which will presumably be running Oreo or Pie? I'd certainly like to take the opportunity to upgrade; I'm still on MM on the S7 mostly because it's just hassle to reflash the ROM (running Superman ROM, not stock).
I assume Nova Launcher will come across okay? What about things like Good Lock? It presumably won't work, but will it break anything or will I need to remove it from my backups before restoring?
Titanium allows me to create a zip of all my backups. Do I just flash that in TWRP? I don't think it's used from within the app itself, is it?
Any ROM recommendations? I use GravityBox so something AOSPish would be ideal, Pie would be awesome but I'd settle for Oreo. I'm not sure what Pie's release status is at the moment - I didn't think it was out yet but it seems to be. This is a very rushed thing (the S7 just stopped working and will be too expensive for repair to be worthwhile), so everything's very scrambled in my head at the moment and I'm just throwing thoughts out there, largely. EDIT: Actually, I assume Xposed and such aren't set up for Pie yet? If so Oreo would be the way to go.
Since I have GMail and such installed as user apps, not system apps, and backed up as such, I'm assuming I'll need to find a way to arrange the same with the Pixel? Superman ROM offers the option to install those apps or not through the Aroma installer.

Does anyone have any input on this?
I'm also curious as to the differences between rooting with/without tripping SafetyNet. I'm assuming there are some, or everyone would do the latter?

Do you have your Pixel, yet? Unlock the bootloader, install the latest factory image, use the latest TWRP & Magisk (do it properly, & a SafetyNet check will pass). When your phone is booting up fine and rooted, we can talk about transferring data.

I don't, but it should be arriving today. I like to be prepared, rather than getting into a situation where I have the phone and want to get everything sorted immediately, only to end up rushing and causing issues. I think I was reading and asking questions about two weeks ahead of my purchase of the S7. As I said, I'm replacing the S7 due to a fault, and I've been without it for a couple of weeks now, so the more I can get my head around before it arrives and I get all "OMG do everything immediately", the better.

If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key. I would just transfer your entire backup directory to the backup directory on your new phone, then use the app to select which apps to restore. Do the app restores in waves, to help you narrow down a problematic restoration.
Even if you already have the latest version of Android installed on the Pixel, download the full factory image so that you can extract the boot.img file from it. Flashing the stock boot.img can get you out of most bootloops. Here's some reading material to help you understand what has changed.
Personally, I'm happy with the stock ROM, rooted. I suggest you look at Tulsadiver's mod. It has some sorely needed customization options.
:good:

post-mortem said:
If you really need Xposed, you can install a Magisk version of Xposed. Personally, I am no longer using Xposed; Magisk gives me root, and I can install all the modules I need.
Click to expand...
Click to collapse
So Xposed modules work in Magisk? Or....? I have GravityBox for notification control, as I find the default LED blink speed too low and like to change the sound/LED colour on a per-app basis far more than the apps themselves allow, along with Unbeloved Hosts, MinMinGuard, Airplane Mode Helper, Screenshot Delay Remover, Secure Settings, XToast and YouTube AdAway.
Do you have the Pro version of Titanium Backup? You have to jump through some hoops to get it to recognize your Pro key.
Click to expand...
Click to collapse
I do. There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
EDIT: Which guide do I follow to install TWRP and Magisk? I thought this would be the go, but reading through it requires a custom ROM to begin with.

I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page.
If the enable OEM unlocking option under developer settings remains grayed out, you might have to get out of the settings and reenter them, restart your phone, or even reflash and start all over. For some reason, a number of people have reported that executing the command am start com.android.chrome in a terminal or adb shell allows the OEM unlocking options to become toggleable.

post-mortem said:
I followed this guide. I really don't know if it's actually necessary to uninstall com.android.phone, though I did it. The command you'll want to use to unlock the bootloader is fastboot flashing unlock, as stated at the top of this Google page
Click to expand...
Click to collapse
Why "flashing" and not "oem"? And then how do I install TWRP? The page you linked to has "install" zips and normal zips, not sure which I'm meant to download.
EDIT: Phone arrived, and is running 7.1.2.

Read the top of the Google page with the links to the Factory Images.
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> . Once you're in TWRP, you install the TWRP installer zip like any other zip. So the .img file stays on your computer (fastboot will load it onto your phone and boot into it), and the .zip goes on the phone so that you can install the TWRP installer.

post-mortem said:
TWRP is temporarily booted using a PC with fastboot boot <TWRPfilename.zip> .
Click to expand...
Click to collapse
Should that be the .img file, not the .zip file? Just guessing from context, otherwise you're using the zip file twice and the img file never.
So:
Unlock bootloader
Flash TWRP
Use TWRP to flash TWRP
Use TWRP to flash Magisk
Yes?
EDIT: Wait, that doesn't include flashing the system thing. When and how do I do that?

Unpopular opinion, but...
If I were you I would just use the phone as it is for at least a couple of days.
I don't want to sound like a Pixel fanboy but I'm liking the stock firmware much better than any custom ROM on this phone.
Of course I'm rooted and running a custom kernel, but I'm positive that Magisk will have the answers to most of your modding needs.
You got a new phone, why go out of your way and risk messing up stuff just to make it feel like your old one?

I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.

koberulz said:
I mean, I'm cool with stock in theory, I just liked the debloated ROM I had last time because, well, debloating. And GMail and YouTube and such are now user apps on the S7, so my backups treat them as such.
Where do I find the drivers? I installed an "adb setup" thing that claimed to have them, but my PC isn't recognising the Pixel. Google's links to OEM drivers include a bunch of brands that aren't Google, so I'm not sure what to download.
EDIT: Okay, got it. Now running Android 9. When I'm installing TWRP, do I need to wipe anything? I miss the S7 forums and their one clear rooting guide that went step by step through everything.
Click to expand...
Click to collapse
No. just fastboot twrp img > flash zip via booted twrp. Reboot to system. That's all you gotta do

How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?

koberulz said:
There's an option to just create a flashable install of Titanium, and to back up its settings, which is what I've always done in the past. Is this different now?
Click to expand...
Click to collapse
Okay, this seems not to work. I've tried flashing it and there's no sign of the app at all.

koberulz said:
How do I boot into TWRP once installed? And come to that, what's the point of installing if I can boot to it regardless?
Click to expand...
Click to collapse
Doesn't the command fastboot boot twrp.img just boot it?
It does that for me, then I just have to flash twrp pixel installer.zip and it sticks.
I do this every time I update my factory image (which resets recovery to stock)

Anyways, I'm in. Had to manually install TB, then restore all my backups...and it screwed everything up big-time. Contacts are horribly broken; they initially kept crashing and now it says there's no contacts app installed. GMail crashes every time I open it. And the vibration has been replaced with a quiet beep.

I expected that... Just reflash latest factory image

Look, don't restore any apps, yet, especially any apps made by Google. You shouldn't need to restore any data, as all Google info is in the cloud, anyway. Just launch the app and log in to your Google account.
You don't need to "permanently" install TWRP if you don't want to.

I don't use Drive, so no it isn't.
I've managed to get everything over except my contacts. They killed it last time so I'm disinclined to try again. Not sure how else to get them over though.
My S7 had an "only display contacts with a phone number" option, does Pixel have an equivalent?
Since I don't have Xposed, I don't have any of my ad blockers. Are there options available?
I also had a lock screen with a tray of apps I could drag up to unlock straight into that app, the clock on the right instead of the left, and a percentage instead of just a battery icon on the lock screen and without swiping down. Any way I can set that up?
I tried Light Flow, but it doesn't seem to be working, I'm not getting any LED lights. It was working fine while I was setting up last night, but I unplugged the phone to go to bed and it's stopped.
I've looked at that Pie Aroma Mod Installer thing, but there's three files offered for download and I'm not sure what they are?
Is there a way to stop the screen turning on and the phone making a sound when I plug/unplug it?

Bricked my OP7P - Can't decrypt data partition anymore

Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.

the.cybertronic said:
Hey Guys,
this could propably be posted in r/TIFU as well since I think I screwed up big time today -.-
I basically just wanted to update my rooted OP7P to 10.0.5 (EU) using the latest OTA - so I followed the usual steps as always:
Uninstall Magisk
Install OTA - No Reboot
Install TWRP retention script in Magisk
Re-Install Magisk
Reboot
This procedure worked fine the last 2 times an OTA was released but this time I'm not able to boot into the system anymore. TWRP is still in places but won't read the data partition anymore - it also doesn't ask for my pattern to decrypt it. Problem is that idiot-me of course didn't do a backup before (yea, I know -.-) and obviously doesn't want to loose the data on it.
I of course checked the forum and googled my ass of trying to find a non-destructive way to access the system but couldn't find anything fitting my scenario. So my last resort is to ask you guys directly: Did anybody ever encounter such a situation and if yes, how did you resolve it? Right now any support would be much appreciated
//Edit: Symptoms and current behaviour:
Boot into system (partition A) ends in the OP logo cirling endlessly
Boot into system (partition B) sends me directly to TWRP
TWRP doesn't ask for encryption pattern
The answer to TWRP's initial question (Keep System r/o) is not persisted
Fastboot/ADB are working (but obviously w/o access to /data)
I'm technically running a stock OxygenOS with Renovate ICE. I know technically its instuctions say to install the OTA directly from within TWRP and and then re-flash TWRP and Magisk but that wasn't neccessary the last times... one idea of mine is to just do that now and see where it leads me but I really don't wanna risk my data.
Click to expand...
Click to collapse
The bad news is once twrp loses access to data. The only fix is to format data and everything will be fixed.

So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)

the.cybertronic said:
So... you're basically telling me I ****ed up completely and my data is gone? Never was a profile picture more fitting than yours right now :/
What I'm wondering is that, from a technical perspective and on a working phone, the decryption takes place not during the boot but only after you've entered your code/passphrase/pattern on OS level. Meaning the system should theoretically be able to boot up to there without /data access. TThat's why I had the idea to flash a clean stock Oxygen from TWRP (no root), boot the system and hopefully be able to access the data this way. Respectively any encryption can be broken somehow, can't it? Even if it might take quite some time to do so this should theoretically be possible...
I mean... I definetly don't know enough about Android internals to understand its encryption mechanics completely but from a technical perspective it should be possible.... like the saying "there is no such thing as 100% security"
Click to expand...
Click to collapse
The reason that format is the only answer is because when twrp does not ask for password. It believes you are unencrypted. What has happened is the file that store your password and encryption key is corrupted so any answer you give is wrong.

There's nothing you can do but format data. I've encountered this issue already.

You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?

Joker123## said:
Dude try flashing the stock rom from twrp onto both slots by mounting an otg drive..or adb sideload(very slow I think..still worth a try if you don't wanna lose data)..stock rom can manage the encryption I suppose.
Encryption is an issue when you flash different roms(I think so..I am no expert,just my experience so far).
Breaking encryption is not like what you think..it might take ages to break using brute force (again from what I heard..I lost my data a lot of time flashing roms without twrp backup..nowadays I just backup my apps using tb coz restorings the apps is really a pain in the ass process)
Click to expand...
Click to collapse
vegetaleb said:
You can try to salvage personal photos and videos using an otg drive (external ssd, hdd, sd card reader...), also back in 6t days I had this encryption problem twice, I remember that one time flashing the stock rom from the otg fixed it but I don't remember if I rebooted to recovery of the other slot.
Anyway, for the others, if he used DM verity removal and so decrypted data, he would have never face this problem again?
Click to expand...
Click to collapse
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
Zhuang zhuang said:
There's nothing you can do but format data. I've encountered this issue already.
Click to expand...
Click to collapse
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.

the.cybertronic said:
I just tried flashing the stock Oxygen yesterday but to no satisfying result... afterwards it just showed a clean default-structure on the SD. Long story short: I accepted the fate that my data is gone and learned a valuable lesson... first thing I installed after rooting was Titanium^^
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
For future reference, brick means a brick. Like, can't boot to fastboot/twrp/or use msmtool

the.cybertronic said:
As hard as it is to admit, you were completely right... I just lost 6 months worth of photos incl. my last vacation in Vietnam - fml.
Click to expand...
Click to collapse
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue

Zhuang zhuang said:
In the recent OS (10.0.5 & beta 13) I think Oneplus they add something that prevent user from using the TWRP retention script. I always use this solution for lower version and have no issue but with both 10.0.5 and beta 13 have the same issue
Click to expand...
Click to collapse
damn, good to know if I ever install OOS again - I now switched to Havoc... even though I had to skip rooting it all together after I couldn't get Magisk running with the latest safety net changes (thanks Google -.-)

I used a magisk module that I can't reverse even with a full wipe

I downloaded a Magisk module to test out that purported to bypass DRM of netflix, Amazon, and a couple others and it put my phone into a boot loop. I installed a recovery magisk module zip for recovery that allowed me to disable the module from TWRP but it didn't matter because it just stopped the module and didn't replace the changed DRM file. After that I just gave up and fully formatted my phone with the All in One tool using "Decrypt phone / erase all data" and then installed a fresh stock ROM image via fastboot. The problem is, even after doing all of this, the DRM file that this module changed is still changed and I can't use streaming services and my phone is incredibly unstable. When I open Netflix for instance, it says I need an update and when I go to the play store it tells me "Netflix is not compatible with your device". Also, even after a full wipe, Nova launcher is still installed, and it's not supposed to be, I have no clue how these files are persisting through a full wipe. I've been tinkering with my phone for over a year now and this is the first problem I've found that not even fastboot can seem to fix. I'm on Tmobile and originally was able to unlock my bootloader by flashing Android 10 Developer preview 3, which they accidentally allowed you to unlock the bootloader with. I did that to unlock my bootloader then rooted and I've been using international ROM's ever since. I'm worried if I have to go back to Stock tmobile ROM I won't be able to get my bootloader locked again, and I still have no clue if this will even fix the issue. Does anyone have any clue how to fix this? If you search "drm" on magisk modules you'll find two things, one that removes all drm, and one from 2019 that attempts to bypass it. (I figured I'd test this out to see if I could watch Netflix in 1440p with my bootloader unlocked and didn't expect it to work, just didn't expect it to find a way to soft brick my phone) I'm using the 2019 one. Is it possible if I re-root my phone to somehow aquire the original DRM files this thing changed and replace them? Are these not included as part of a stock ROM? I don't understand how I can't fix this. My last plan is to reinstall TWRP and wipe literally every option on there then flash a ROM via fastboot, but I doubt it's going to work if formatting the entire phone doesn't work
Edit: Installed TWRP, wiped literally every option so I didn't even have an OS anymore, used fastboot to decrypt / erase all data then when installing stock ROM I chose again to wipe all data. If nova launcher and the changed DRM persists through this I'm going to be completely stumped. The only thing I can conclude is that somehow my phone is not actually fully wiping itself even though I'm using 3 different methods to do it
Edit 2: This still didn't work. I think I'm gonna have to use the MSM tool and go back to tmobile stock. If I flash far back enough I should in theory still be able to flash Android 10 DP3 and unlock my bootloader again, it's just gonna be an unexpected pain in the ass task to deal with today
Edit 3: Thank god for modified msm tool, I didn't know they were able to modify it to convert your tmobile phone to international and unlock the bootloader. This is going to be much easier than anticipated as long as doing this actually fixes my drm files and really wipes everything
Edit 4: Even using MSM tool to install a factory international ROM fixed the Netflix issue but somehow Nova Launcher is persisting through every single kind of wipe I've done lol. Despite the bootloader being locked (wasn't supposed to be) after this update, Netflix still wouldn't play in HD which is kind of odd. I'm now going through the process of installing Android 10 DP3 and unlocking my bootloader then downgrading back to pie to root and install TWRP again. I'm just going to have to accept that Nova Launcher is a part of my phone now lol

Maybe I'm wrong but didnt op7 pro have an irreversible e-fuse that once triggered with root it wiped out the ability to see HD forever ? Something to do with downgrading widevine drm levels if I remember correctly... The nova thingy I cant explain but hey it could be worse you could be stuck with Microsoft's launcher [emoji1787]
Sent from my GM1913 using Tapatalk
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Just a thought that crossed my mind, could it be that Nova is surviving as a system app in A or B slot? Are you sure you are wiping system in both slots?
Sent from my GM1913 using Tapatalk

Relock bootloader, not lose data

Hello all.
*** TLDR: I downloaded boot.img from Google servers and flashed it , then rooted via magisk the patched boot.img. Now I wanna unroot and relock my bootloader but don't wanna lose my app data (and also not brick of course!). Is it possible? ***
Explaining better:
My unrooted pixel 3a was having issues with charging, it pretty much seemed like software related, as I have seen other people with similar problems.
Anyway, before opening the phone (which on the end I did, and exchanged the usb port), I decided to do a factory reset. I did back up, but one app, which is not available anymore lost its data.
Since I have a rooted Samsung and the same app there, I used Titanium Backup there, and flashed the stock boot.img and rooted my pixel 3a with Magisk, then restored the data on my pixel.
This worked wonderfully, and I was going to keep it rooted, but I'm failing safetynet, can't access banking apps, and it's been too much work lately for me to go deeper into it.
So, I was thinking of unrooting my pixel, and relocking the bootloader.
Can I do this without 1. Losing my data and 2. Risk bricking it?
I have installed the boot.img file from Google servers, and just flashed the magisk patched boot.img.
Thanks
EDIT: typos

KreGgiants said:
Hello all.
*** TLDR: I downloaded boot.img from Google servers and flashed it , then rooted via magisk the patched boot.img. Now I wanna unroot and relock my bootloader but don't wanna lose my app data (and also not brick of course!). Is it possible? ***
Explaining better:
My unrooted pixel 3a was having issues with charging, it pretty much seemed like software related, as I have seen other people with similar problems.
Anyway, before opening the phone (which on the end I did, and exchanged the usb port), I decided to do a factory reset. I did back up, but one app, which is not available anymore lost its data.
Since I have a rooted Samsung and the same app there, I used Titanium Backup there, and flashed the stock boot.img and rooted my pixel 3a with Magisk, then restored the data on my pixel.
This worked wonderfully, and I was going to keep it rooted, but I'm failing safetynet, can't access banking apps, and it's been too much work lately for me to go deeper into it.
So, I was thinking of unrooting my pixel, and relocking the bootloader.
Can I do this without 1. Losing my data and 2. Risk bricking it?
I have installed the boot.img file from Google servers, and just flashed the magisk patched boot.img.
Thanks
EDIT: typos
Click to expand...
Click to collapse
Sorry, cannot answer you question.
Just want to say you should try customer kernel to get rid of the charging bug. One option could be paid app EX kernel manager.