Database Users

Can I make use of Nougat's automatic updates and have/keep root? TWRP ver. to use?

Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?

EvanVanVan said:
Right now I'm on 7.0 DP5, unencrypted with root. I'm willing to enable encryption if it means I won't have to constantly manually flash the security updates and keep root. Is that what the "system-less root" technique is for? (and is it still a thing?)
Should I use the lastest TWRP 3.0.2-2 to flash N factory images? I'm guessing 3.0.2-1 bug is less serious now that there's a vendor.img available, but the last I had read from the dev team was that -2 was still untested and 3.0.2-0 was still the safest bet. I'm just not sure it's compatible with N?
Click to expand...
Click to collapse
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk

ultyrunner said:
You can't have root or custom recovery and take OTAs, but you can have an unlocked bootloader. Otherwise stock only. I am pretty sure systemless appeared when people were trying to keep using Android Pay. As for TWRP, I have had no problems using the latest, just don't restore / backup between MM and N.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.

+1 Flashfire

Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?

EvanVanVan said:
Cool thanks for the suggestion, I actually saw something about FlashFire this morning but haven't had a chance to look into it yet. Do I need to be encrypted for it to work? And I'm assuming it's not entirely compatible with N's update system, it still takes some interaction to flash?
Click to expand...
Click to collapse
The other issue with TWRP was backing up and restoring the EFS partition, it seemed that 3.0.2-1 corrupted it on restore which would be a problem. They did have a work around. They suggested using -0 would be fine. I have -2 and did a N to N restore with no issue, but I did not restore EFS. I'm always extra careful with new versions, I tend to backup my data and backups off-phone just in case.

dratsablive said:
If you are rooted and have TWRP installed, you can use FlashFire to install the OTA and keep root and your custom recovery.
Click to expand...
Click to collapse
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK

smallvan said:
My situation is that my 6p is rooted , TWRP installed and with custom kernel. I have searched quite a bit and cannot make sure which is the best way to update from MM to N. My thought is that:
1. FlashFire wipe system data n cache;
2. FlashFire MM stock boot image;
3. FlashFire N ota;
4. FlashFire custome kernel; and
5. Reboot.
The above steps to be done in one sequency. Please comment n million thanks.
CK
Click to expand...
Click to collapse
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.

dratsablive said:
Put this in wrong thread and want to delete it.
That's a bit too complicated. Connect your phone to a Mac. Open a terminal and
adb devices (To see if your phone is recognized. If so continue, if not fix and then continue)
fastboot flash boot boot.img
fastboot reboot bootloader
fastboot flash system.img
fastboot flash recovery stockrecovery.img
fastboot reboot
That should unroot your device.
Click to expand...
Click to collapse
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?

smallvan said:
Thanks. And I will have a total experience of returning my 6p back to stock boot, stock recovery n no root. What about vendor.img?
Click to expand...
Click to collapse
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.

dratsablive said:
You don't need vendor image unless you are flashing a different boot/system from what you currently have. But it also can't hurt as long as it's the correct version.
Click to expand...
Click to collapse
I believe I am looking for a suitable way to upgrade my 6p from MM to N that I have explicitly stated at my wrong thread post. This is absolutely not my intention to return my 6p back to stock of MM. And there is every reason to upgrade to N, thus, vendor.img is no doubt a must for an amateur like me.
Nevertheless, thanks for dratsablive kind suggestions.

Return to Stock Question

With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk

cas239 said:
With the impending release of the stable Oreo build, I have a question on how I will update. I'm currently on the NMJ51B build, rooted with Magisk and Unlocked Bootloader. I'm under the impression I won't be able to OTA Oreo when it's released, so what will my process be?
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.

tech_head said:
If you have stock recovery you should be fine.
Magisk should not stop the OTA, but you will need to re-root.
Otherwise use one of the stock installs in the ROM section.
Click to expand...
Click to collapse
I flashed TWRP Recovery when I rooted the phone

Bump
Sent from my PH-1 using Tapatalk

I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.

bjs339 said:
I'm in the same position as you, rooted on NMJ51B and planning on updating to the official Oreo release. This is the path I plan on taking:
Download the Full Dump (back to stock) zip from here: https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681. Run flash-all.bat. This will take you back to stock on your current build.
Take the OTAs to update to Oreo.
Follow the rooting instructions for Oreo from the rooting guide here: https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
There may be another way, but reading through the forums I expect that to be a safe path that should work.
Click to expand...
Click to collapse
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.

tech_head said:
That is the correct path.
If you are on a stock ROM and running TWRP, you can also just flash the stock boot after uninstalling Magisk.
Click to expand...
Click to collapse
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?

bjs339 said:
So I can flash the stock Oreo boot image from within TWRP after uninstalling Magisk? And then I would flash Magisk again from within TWRP before booting? Just making sure I understand correctly, as I'm actually considering doing this with the Beta 3 just released. And TWRP would not remain on the device, correct?
Click to expand...
Click to collapse
No.
I was just talking about back to stock.
You would need to flash Oreo B3 separately.
You could just connect to a computer and flash Oreo B3 without going back to stock.
The fastboot flashable ROM is in the ROM section of the forum.

I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.

bjs339 said:
I've gotten most of the way there. Went back to stock on 51B, then sideloaded OB3. Now I need to root with Magisk, but it just won't work. I followed the instructions for Oreo in the rooting thread, but TWRP won't accept my passcode. I've tried it several times, making sure to press the right buttons, but TWRP keeps telling me the passcode failed. I've also tried patching the OB3 boot image with Magisk and flashing that, but the spinner keeps spinning and doesn't boot.
I get the feeling that the only way I'm going to get root is by wiping userdata and starting with a clean factory reset. I'm just trying to find a way to avoid that. Does anyone have any idea what's wrong? I really appreciate the help I've gotten so far.
Edit: Even when I remove the pin and flash the boot image and Magisk in TWRP, it's still not booting. I don't think decryption is the problem, but I'm not sure what is. I'm following the same instructions that many have used to root successfully.
Click to expand...
Click to collapse
TWRP has a screen image offset.
Look very carefully at the passcode as you enter it.
I have a failure rate of about 50% due to the misalignment.

I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!

How did you "return to stock"? Using what method and files? From what are you returning?

drumrjoe said:
I just tried returning to stock on my Essential PH-1 and when it reboots, I have no way to interact with the screen.. Side buttons work great, but can't move past the first "Let's get started" screen... no touch? Please help.
thanks!
Click to expand...
Click to collapse
Which version of the stock ROM?

It originally came with 7.1.1 NMJ32f/436.. which upgraded to the latest version of pie... 9 something.. I have tried using the .bat file on both stock files, NMJ32F_back_to_stock and PPR1.180610.091_BACK_TO_STOCK_OTAFILE with the same result.. see vid please ... https://photos.app.goo.gl/XRUScdV9UYDnx5dn9
Thanks in advance for any help.
DJ

So I've had the idea and its probably been discussed to death because I'm slow. But say now I have pie running on partition a, what stops me from swapping to slot b in fastboot and installing a stock oreo or say custom rom? I've already bricked one essential so I'm gunshy to do anything. But luckily it worked out because I'm sure the one I had before was a sprint "unlocked" one everyone is having issues with.

Stuck in TWRP after pushed upgrade 28s

This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.

Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium

mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?

Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.

In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658

marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium

No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that

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

Phone booting back to TWRP

Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.

PapaMag said:
Same happened to me a few days ago and had to reflash full rom. PC still recognized device so I placed os on root of device and flashed. Unfortunately it wiped the device but at least it worked.
Click to expand...
Click to collapse
So you had to wipe everything?

ledvedder said:
Hi everyone,
I'm rooted. I flashed the Beta 3 rom and TWRP. Then, I rebooted into TWRP and flashed Magisk v18. Now, my phone spins on the boot animation screen for about a minute, then reboots into TWRP. Any ideas what I should do? I've tried wiping cache, but still the same issues.
Click to expand...
Click to collapse
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.

ledvedder said:
So you had to wipe everything?
Click to expand...
Click to collapse
When I flashed 9.0.11 again it wiped the device yes.

_Masked_ said:
I don't recommend updating that way. For me I flashed a patched boot.img from TWRP and it worked.
Click to expand...
Click to collapse
Obviously you are smarter than me. Thanks for the tip

PapaMag said:
Obviously you are smarter than me. Thanks for the tip
Click to expand...
Click to collapse
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.

_Masked_ said:
No problem, happy to help. By patched boot.img I mean the boot.img that was patched by Magisk.
Click to expand...
Click to collapse
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk

ledvedder said:
Where can I get that boot.img file?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.

_Masked_ said:
The stock boot.img file is extracted from OOS and the patched boot.img is after you patch it via Magisk.
Click to expand...
Click to collapse
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk

Use this if you're on OOS 9.0.5/9.0.6/9.0.7, but if you are on a higher OOS then you need to grab your stock boot.img for 9.0.10 from here and 9.0.11 from here, and patch it yourself using the instructions below.
Connect your phone to your PC using the OnePlus Cable
Reboot to Bootloader using "adb reboot bootloader" on PC while your phone is in TWRP
Rename stock boot .img file to boot.img on PC
Use "fastboot boot boot.img" on PC while your phone is in Fastboot Mode / Bootloader
Follow this guide once you are done with the above steps to root your phone with Magisk and actually boot.

I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.

h8Aramex said:
I am in the same situation.
1) Got the phone. Unlocked with out-of-the-box firmware. Put TWRP on it, Magisk. All worked like a dream.
2) Time passed, I tried to play Fortnite a bit, which kicked me out due to root. Had to use Magisk Canary. Still, NO issues, all superb!
3) New firmware. The December one. Kept postponing it, but after like 2 weeks, I was like, meh, why not. Big mistake.
From this point on, I cannot root no matter what I try. As soon as I flash Magisk, it will keep booting back to TWRP.
I have even tried to grab the Canary ZIP to flash. Nothing. Tried flashing back the full base update file from OnePlus, then root. Nothing.
It's like an endless loop.
To be fair, I only use root / magisk because I need call recording. Sadly, it's been killed in Android 9, but OnePlus has a hidden feature for this. Unfortunately you have to use either ADB on each boot, or use Magisk to enable it and save you time, hassle.
Anyone has any idea, shoot.
This is a 100% unbranded, OnePlus-store-bought 8GB/128GB 6T model.
Ps.: IF you ever get stuck in this loop - you can boot your phone by using the original "boot.img".
You can grab it here:
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
To boot it, simply:
1) Enter Bootloader where you can use fastboot (NOT TWRP!).
2) Use `fastboot boot boot.img`
3) Your phone now will boot up.
Click to expand...
Click to collapse
Try this.

ledvedder said:
How do I extract it?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Plug your phone into your PC
Use this command in TWRP's Terminal and type this:
Code:
dd if=/dev/block/bootdevice/by-name/boot of=boot.img
Copy it from your phone to your PC (in the directory your command prompt is in) and use the command:
Code:
fastboot boot boot.img

TWRP doesn't work
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.

dgdeepak000 said:
Hi there,
Just like you I have installed twrp-3.2.3-x_blu_spark_v9.86_op6 TWRP recovery on my phone to flash custom ROM (as recommneded by this ROMs list), however, it doesn't work. Like, no matter whether you I to flash unofficial or official custom ROM, it says that 'Something isn't right'. I think there's some problem within this recovery. Hoping for good.
Click to expand...
Click to collapse
Flash the CORRECT one, for the OnePlus 6T. Not for the OnePlus 6.