Database Users

Help downgrading from Nougat to Marshmallow and/or getting rid of System apps in N.

I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.

are you root? if so, i've had luck modifying system with Root Explorer. (not sure which explorer you were using)

tysoncrypto said:
I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.
Click to expand...
Click to collapse
I've had luck removing system apps with FX explorer, but I had to remount system R/W before it would let me. Also I'm rooted.

I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.

tysoncrypto said:
I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.
Click to expand...
Click to collapse
If you wish to get rid of system apps, simply flash via recovery, the lastest supersu vip; system[less], whichever your preference. If you haven't already flashed twrp after flashing Nougat, do so first.
Install Titanium Backup, and you're all set; I've done it myself and works as it should.
If you were trying to downgrade to Marshmallow, you'd need to do a backup + full wipe, and install the M bootloader, boot, system, etc, then you could restore a custom ROM backup, if you had one.

Heisenberg said:
I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.
Click to expand...
Click to collapse
At this point i would wait unless he signs up for the beta. Dozen of us have restored our phones
We flashed that it's over custom rom/ wrong steps to upgrade.

rbouza1 said:
At this point i would wait unless he signs up for the beta. Dozen of us have restored our phones
We flashed that it's over custom rom/ wrong steps to upgrade.
Click to expand...
Click to collapse
So can i downgrade to MM again? I'm on beta N7.0 ... No root.. No unlocked bootloader.. everything stock.. What do you think i should do to get back?? Can i root and flash MM over it..idk
Thanks in advance!!!

RidinNerdy said:
So can i downgrade to MM again? I'm on beta N7.0 ... No root.. No unlocked bootloader.. everything stock.. What do you think i should do to get back?? Can i root and flash MM over it..idk
Thanks in advance!!!
Click to expand...
Click to collapse
With out unlocked bootloader I don't really know. I guess you might be able to run a factory image . The latest from googles developers site .

spunks3 said:
are you root? if so, i've had luck modifying system with Root Explorer. (not sure which explorer you were using)
Click to expand...
Click to collapse
Thank you all for your answers. I didn`t bother trying another root explorer as i thought they`re all the same, but i will try the ones suggested here. And yes, the phone is of course unlocked and rooted with the latest twrp and supersu installed.

teh roxxorz said:
If you wish to get rid of system apps, simply flash via recovery, the lastest supersu vip; system[less], whichever your preference. If you haven't already flashed twrp after flashing Nougat, do so first.
Install Titanium Backup, and you're all set; I've done it myself and works as it should.
If you were trying to downgrade to Marshmallow, you'd need to do a backup + full wipe, and install the M bootloader, boot, system, etc, then you could restore a custom ROM backup, if you had one.
Click to expand...
Click to collapse
Thanks. I flashed the latest twrp and supersu before upgrading to Nougat, and they both made it through, so it`s all set up.
I think i`ll try to downgrade since i don`t see the big Deal with N as of now + i have a much worse mobile data signal after updating to it. It`s almost constantly on H instead of 4g /LTE.
If someone is interested in downgrading, here`s an exact instruction that i found here on XDA:
"Download the MM stock firmware and extract all of it to a folder. Then open a cmd/terminal in the download folder (shift and right click in windows I believe, just right click and there will be a option in linux).
Then do these steps in order BACK UP YOUR APPS!!"
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
The names will be a little different, and if you want twrp put it in place of the stock recovery!
PS: Don't flash userdata
If that fails, i`ll install titanium backup to at least get rid of all the google stuff, like music, photos etc.

Heisenberg said:
I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.
Click to expand...
Click to collapse
@Heisenberg Do you know of a safe way to downgrade our 6p from Nougat 7.1.1 on Pure Nexus to Marshmallow?

jt1998 said:
@Heisenberg Do you know of a safe way to downgrade our 6p from Nougat 7.1.1 on Pure Nexus to Marshmallow?
Click to expand...
Click to collapse
When I got my phone back after RMA from the BLOD it was on 7.0 and the first thing I did was flash a 6.0.1 factory image. I picked the same build number as the last Pure Nexus build in MM. I don't think flashing factory images through fastboot is a big risk as long as you are paying attention and following a good plan. Any other opinions are welcome.
Sent from my Nexus 6P using XDA-Developers Legacy app

tysoncrypto said:
Thanks. I flashed the latest twrp and supersu before upgrading to Nougat, and they both made it through, so it`s all set up.
I think i`ll try to downgrade since i don`t see the big Deal with N as of now + i have a much worse mobile data signal after updating to it. It`s almost constantly on H instead of 4g /LTE.
If someone is interested in downgrading, here`s an exact instruction that i found here on XDA:
"Download the MM stock firmware and extract all of it to a folder. Then open a cmd/terminal in the download folder (shift and right click in windows I believe, just right click and there will be a option in linux).
Then do these steps in order BACK UP YOUR APPS!!"
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
The names will be a little different, and if you want twrp put it in place of the stock recovery!
PS: Don't flash userdata
If that fails, i`ll install titanium backup to at least get rid of all the google stuff, like music, photos etc.
Click to expand...
Click to collapse
Dude, does it fixes your lte issues? Because i am facing the same problem with my nexus 6p + android 7.1.1.

I personally have never had lte issues on any build, 6.x.x or 7.x.x on any custom rom or stock.
Sent from my Nexus 6P using XDA-Developers Legacy app

https://developers.google.com/android/images You need a complete factory image flash, including /data.
I had LTE problems from 7.1.2b to 7.1.1 (while I didn't have them on 7.1.1 before switching to 7.1.2b) and they were solved by factory reset.

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.

HELP !!! Bootloop after OTA update.

Hi, I downloaded the last update in OTA but after reboot I'm stuck on the boot animation.
I'm on the stock rom, never updated since I bought the phone in august.
I'm root and of course my bootloader is unlocked. I have TWRP that I managed to reinstall with ADB Sideload after this f***ing update get me back on stock recovery.
Now I keep trying install Roms (Official and customs) via ADB Sideload. Each time it look like the install is successful but then TWRP tell me "no os install, are you sure you want to reboot". Then I'm always stuck on the boot animation (at least it's the animation of the rom I tried to install).
Before I tried to update via OTA the 1st time I made a backup with TWRP but now all my files have been replaced by files with random letters ans numbers, so I can't even restore my backup and I'm affraid I lost everything I had on my phone.
What should I do now ?
Thanks for your help

Simply reflash the rom or do factory reset using pc { adb }

Swarup550 said:
Simply reflash the rom or do factory reset using pc { adb }
Click to expand...
Click to collapse
as i said, after flashing a rom it tell me "no os installed".
by factory reset you mean format hd ? i'd like not to loose everything.

Then you have to format it and then you have to install the stock rom.

Swarup550 said:
Then you have to format it and then you have to install the stock rom.
Click to expand...
Click to collapse
oh no :crying:
well, if i have no choice

Ya you hav to sacrifice your data

i think oneplus could warn you before download update !!!
i just had a message that told me that i was root and i won't be root anymore after updated. nothing about that i'll have to format my phone

It's done. It seems to work fine
Thanks a lot for your help

Kawa Banana said:
It's done. It seems to work fine
Thanks a lot for your help
Click to expand...
Click to collapse
Welcome.But next time if u want to root use adb to flash twrp then flash super su or i prefer magisk module:

Do I have to flash no verity?

I really just want to root stock. I have the Boost Mobile Perry.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).

I really don't care about encryption.

guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.

Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.

guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.

Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img

i have the moto e4 mkt which no verity version do i have to flash ?

Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.

madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome

Unsure what I did

but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?

ms.journie said:
but ....... I am in twrp unable to reboot into my rom. When I click on Install I see all these folders with letters and numbers and what my original folders.
Can somone help me boot into my rom again?
Click to expand...
Click to collapse
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.

Omg this saddens me! So there's no way I am unable to at least retrieve my pictures?
Scott said:
You will more than likely need to format data. This will cause you to loose everything. But that is what you are seeing, those folders, are your data. Just encrypted.
Also make sure you are on the latest version of TWRP. Sometimes the older unsupported version had encryption errors.
Click to expand...
Click to collapse

Have u tested change boot partition ?

yup
J3zz said:
Have u tested change boot partition ?
Click to expand...
Click to collapse

ms.journie said:
yup
Click to expand...
Click to collapse
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code

I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
J3zz said:
Simple test are:
- change boot partition
- reflash system
- Say goodbye too all
Got the same problem, Solved After reboot in twrp and enter the good decryption code
Click to expand...
Click to collapse

ms.journie said:
I'm right in the middle of reflashing. I am trying everything else before I do say goodbye to my pictures! :crying:
How did you figure out the decryption code?
Click to expand...
Click to collapse
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?

Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
J3zz said:
First time entering in twrp after flashing update, I did not get folder to flash magisk, did a reboot and get it, just a bad encryption code I think
Did u flash rom or anything else before getting this problem ?
Click to expand...
Click to collapse

ms.journie said:
Yup, I sure did! 4am couldn't sleep so I thought I would finally put a fingerprint mod on; which I have done this before with no issues. For the life of me, I don't remember which mod I tried to install thru Magisk.
My phone is currently stuck on "Phone is starting"
I also think it's time to look into some sort of automatic back up service..... Got any ideas?
Click to expand...
Click to collapse
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ? Then boot and uninstall the "****in" fantastic module... maybe it works

I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
J3zz said:
Use msmdownloadtool, have u tried using magisk uninstall in twrp with zip file ?
Click to expand...
Click to collapse

ms.journie said:
I did try to uninstall Magisk in twrp using adb shell. I never had any luck with that msmdownloadtool and not only that it relocks your bootloader.
I usually go this route [ROM][STOCK][FASTBOOT][OP6T] Stock Fastboot ROMs for OnePlus 6T https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Thanks for trying to me!
Click to expand...
Click to collapse
Good luck !!

I saw this happen when I used the official TWRP app.
It went away when I used this TWRP. Hope that helps.

I'm glad you already know not to use the MSM tool. Too many people jump straight to this.....
You just need to boot the correct recovery and your data will decrypt, and you will be able to back it up to a PC, then you can reload your ROM via TWRP or Fastboot to get the phone bootable again. So now it's a question of what ROM were you running before. Do you need a recovery with the latest security patch or something older? What TWRP are you running. Try 3.3.1-6 psychen6 linked too first. Boot that image from Fastboot. See if your password/pin will work to decrypt your data.