Database Info

[Guide] BQ Aquaris M10 (freezerhd) twrp & root

Hi,
as I did not find an English guide for rooting a BQ Aquaris M10 tablet and had some problems when trying to root my tablet, I want to post an guide how to root this tablet.
First of all:
- This guide is just from my experience and is not thoroughly tested. It's on your own if you risk bricking your device.
- If you get stuck in the process, in nearly all cases you can revert to stock with the MTK flash tool (can be found on mibqyyo.com) and the images provided by BQ on their website.
- I could not unlock the bootloader with the 1.X-Images (Lollipop), as the VolumeUp-Button didn't work in fastboot-mode and you need this button to confirm the unlock.
- Booting into recovery from start with VolumeUp and Power-Button. This doesn't work with the 1.X-images, too.
- This guide is not intended for users without experience in unlocking/rooting a device. If you don't know how to use adb, fastboot, recovery and things like that, don't try it!
- You will loose all your data during this process!!
Guide:
Modify boot.img, flash new firmware
SuperSU in systemless mode doesn't work on stock image, as the SuperSU installer can't extract boot.img. You have to repack boot.img.
I tried a SuperSU installer without systemless-mode, but device didn't even boot anymore afterwards.
This guide is derived from a Spanish tutorial on the HTCmania-forum ("Root M10 HD Marshmallow") by yquepongo. Thanks to him!
Get a firmware for your device from the BQ-website (should be Marshmallow, see above) and unzip it to a directory.
Extract the boot-verified.img in the firmware directory with a bootimg-extractor. There are various tools available.
I used bootimg.exe, because this was explained in the mentioned thread and I even used it with wine on Linux and it went well.
Search for cpiolist.txt in your extracted boot-verified.img and delete the first two lines:
mode:mtk
mtk_header_name:ROOTFS
Repack boot-verified.img and put it back in the firmware directory.
Flash the modified firmware with the MTK flash tool according to the tutorial on .mibqyyo.com (Title "Hard Reset for the smartphone range Aquaris and Aquaris E"). In short: Disconnect device, start Tool, load scatter file from firmware directory, choose firmware upgrade, start download, connect the device in power off state, download will start automatically.
This will delete all your data and put the device back to factory rom (hard reset)!!!
If you don't want to flash the complete firmware, you can flash only the boot-verified.img with "Download only" in the flash tool. I didn't try this and don't know if this is working.
Start your device, don't activate any security settings to prevent encryption of data partition.
Unlock bootloader, flash TWRP, install SuperSU
Enable developer settings on device and activate "OEM unlock" in developer settings.
Reboot into fastboot (adb reboot bootloader) and unlock bootloader (fastboot oem-unlock).
This will delete all your data!!! Reboot your system afterwards to make sure everything is still ok.
Do not activate any security settings and make sure your data partition is not encrypted!
The existing TWRP-image can't handle an encrypted data partition, you will end in a boot loop and have to start the whole process again!
Double check, your data partition isn't encrypted. (Settings - Security)
Reboot into fastboot (adb reboot bootloader) and flash the TWRP-image from the TWRP-site (fastboot flash recovery twrpxxx.img)
After reboot TWRP should start.
If you have checked that everything is ok (I would recommend a reboot into normal mode), you can install SuperSU with the standard-installer-zip in TWRP.
If you didn't modify your boot.img, the installer will give a warning that it cannot extract boot.img and you will not find any SuperSU on your system.
If you get stuck in bootloop afterwards you can start anew and try it with another image flashed with MTK flash tool. (Firmware 2.2.0 from December 2016 for freezerhd worked in my case)
Maybe some steps could be shortened, but I haven't tried it.

hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers
Supplied image: unlokied-new.img
Setting up work folders . . .
Splitting image to "/split_img/" . . .
Android boot magic not found.
Error!. . .
Click to expand...
Click to collapse
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless

i opened a separate theme for this : https://forum.xda-developers.com/android/general/root-help-to-root-twrp-recovery-bq-t3536170

dreas74 said:
hi zrfl,
i have a bq aquarius m8 with mm os.
the m8 has the same resolution (1280x800)
can i try the twrp recovery from the m10?
i will also root my m8 but i cant extract the boot-sign.img.
all tools fails.
have you any ideas?
update:
yesterday i opened the bootloader. the volume button works in fastboot-mode.
also i can unlock the boot image with the tools from: https://forum.xda-developers.com/showthread.php?t=2073775
but the unpack fails:
i think this bq boot image use non-standard header. any ideas how to root this bq aquarius m8?
i buyed this tablet only to can use xposed.
i think, any android without root or xposed is useless
Click to expand...
Click to collapse
Sorry, but I can't help you there, as the M8 seems to be too different to the M10: I didn't have to unlock the boot.img, it was easy to unpack.

hi zrfl,
thanks for your reply. i contacted the developer osmOsis from the android image kitchen.
he will implement the bq specials in his tools.
more in the AIK thread: https://forum.xda-developers.com/showthread.php?t=2073775&page=108

this is the only way to root this device !!
thanks a lot ...

Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks

ZazOufUmI said:
Thanks for this tutorial.
I've followed all the step, I'm able to flash the new recovery from the TWRP website but then I do a
Code:
fastboot reboot-bootloader
but the device reboot normally, just with a warning message during boot saying something like "This device is unlock and can't be trusted, it will boot in 5 seconds".
So I'm unable to access TWRP recovery, I guess when the device reboot it override the recovery partition because if I do a
Code:
adb reboot recovery
I end up in the Android recovery not TWRP.
Any idea ?
Thanks
Click to expand...
Click to collapse
Sorry, I have done this a long time ago and don't know what could be wrong:
You have the correct message, so unlock was successfull
You try to reboot in fastboot, so you flashed TWRP correctly in fastboot-mode
And I don't have the device at hand to try it myself. But I do have a few suggestions, what you could try:
Don't try to shorten procedure with unlock and flashing of TWRP at once. I'm not sure, but I think I had problems when I tried this. So do a normal reboot after unlock, before booting again into fastboot and flashing TWRP. (Now you have done this already )
I don't remember the proper boot command after flashing of TWRP. But
Code:
fastboot reboot-bootloader
doesn't make sense: You are already in bootloader.
Is there a boot-option in the bootloader where you could choose recovery?
Otherwise better power off and use the key-combination for booting into recovery: VolumeUp+Power.
I think, you have to repeat the procedure, as recovery seems to be overwritten: Boot into fastboot, flash TWRP, reboot into recovery. And avoid normal booting before first boot into TWRP!
Did you use the newest TWRP 3.1.0 from March 8th? I haven't tried this yet, so there could be the problem. You could try the previous one: 3.0.2 from last year.

Thanks, I succeed with the combo key (power + vol up) directly after the reboot process

Perfect it's working great now !

I did exactly what you wrote but SuperSU won't install because it cannot extract the ramdisk...

Hi @zrfl
Thanks for your posting!
I did as you suggested and successfully unlocked bootloader and installed TWRP 3.1.1. Your hint to modify the boot-verified was extremely helpful, as I wouldn't be able to unlock the bootloader otherwise.
However, I did not manage to install super su. And boy, I tried many different versions od regular/system/systemless supersu, each flashed according to the respective how-to.
I ended up either in a bootloop, or get stuck on the Android logo at boot.
Flashing goes well until this step:
"Decompressing ramdisk
--- Failure, aborting"
I checked ramdisk compression of boot with Carliv image Kitchen and it tells me that it already is set to "gz" and not another compression TWRP can't handle.
Please help me on how to flash SuperSu.
Thanks and best
Tom

There is something wrong: TWRP does not need a modified boot.img.
Maybe newer ROM-versions are different.

Solution for geting root on BQ M10 FHD on stock rom 2.6.2: Start with a fresh system and install magisk beta (not stable), reboot and root is granted!
tanks a lot to @scafroglia93!

Are there any Custom ROM's
For this Tablet like CM/LineageOS AOSP etc?
Googling reveals nothing and Considering all the kernel mods like hardcore and Ubuntu touch I find it hard to believe that nobody has built one of the later.

I've been searching for custom ROMs too. Apparently, there are none available at present. However, I'd highly appreciate lineage rom.

twrp & Root & Mod for Ulefone Mix

Support page for ulefone Mix User-
we Need Some files to Root Ulefone Mix.
1. SP flash tools- https://spflashtool.com/
2. twrp Recovery- https://romprovider.com/2017/11/ulefone-support-twrp/
3. SuperSU- https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
other Support File-
Official Firmware- mod edit - link removed
no-verity-opt-encrypt-5.1.zip - https://androidfilehost.com/?fid=673368273298927206
Instructions-
First of all Flash twrp using SP flash tool
Don't Switch on phone flash no-verity-opt-encrypt-5.1.zip
then flash SuperSu.zip
Reboot System Now.

Is the 1st step not disabling oem lock in developer settings?

HypoTurtle said:
Is the 1st step not disabling oem lock in developer settings?
Click to expand...
Click to collapse
you can unlock with fastboot-
For new devices (2015 and later):
Code:
fastboot flashing unlock
For older devices (2014 and earlier):
Code:
fastboot oem unlock

XN Logos said:
you can unlock with fastboot-
For new devices (2015 and later):
For older devices (2014 and earlier):
Click to expand...
Click to collapse
For some reason no need to oem unlock (bootloader not locked properly??) so have twrp without needing to wipe data, but now remains the encryption problem as this trwp doesn't support it, I have compiled twrp for mtk in the past with encryption support but doubt I can recall what needed to be done

TWRP not working
When I install the TWRP recovery and start the phone with this mode to install the two files
1) no-verity-opt-encrypt-5.1
2) SuperSU-v2.82-201705271822
the phone does not see them and it is impossible to proceed further.
Furthermore, the operating system does not even start, so the original firmware must be replaced with the flash tool.
Has anyone found a solution to this inconvenience?
Thank you

mingariedd said:
When I install the TWRP recovery and start the phone with this mode to install the two files
1) no-verity-opt-encrypt-5.1
2) SuperSU-v2.82-201705271822
the phone does not see them and it is impossible to proceed further.
Furthermore, the operating system does not even start, so the original firmware must be replaced with the flash tool.
Has anyone found a solution to this inconvenience?
Thank you
Click to expand...
Click to collapse
1. Userdata is encrypted, and the TWRP here isn't compiled to be able to decrypt it. So you'll need an sdcard with those zips on it
2. The os won't start if it deems its been altered - that's partly what zip 1 is for.

Is there any custom roms for Ulefone Mix?

Qaaqqu said:
Is there any custom roms for Ulefone Mix?
Click to expand...
Click to collapse
No custom ROMs - I think there is a clone device [Panasonic Eluga C] so we have another stock ROM from them.
I haven't attempted porting anything yet, let alone building anything from source [a source built twrp should be trivial] - i've lost yet another hard-drive recently so light on diskspace & sdcards so not able to do much atm.
For completeness: stock ROM > http://ulefone.com/download/mix.html [newer than the one on needrom]
OTA > http://hwfotadown.mayitek.com/ota/r...NE_N_V0.6.9.1_S1712221514261911507/update.zip

Is this root method working?
Stock rom is located here Stock Ulefone Mix 4G Rom

when (android 8) Oreo for ulefone mix?

twrp and now?
Hello,
i have an old ulefone mix mt6750t with the screen damaged but still 90% working, i thought i would use it on android auto but i needed rooting.
So I informed myself a bit, go unlocked developer mode and usb, downloaded adb and twrp and magisk etc ...
I unlocked the bootloader from the settings then used adb and installed twrp which starts but asks me for the pass to decrypt, then I swipe and delete the encrypted data.
Then with adb sideload I install magisk 20 and check opt encript, but the phone always goes to twrp, it does not restart ... mmm and the orange mode message comes out but it should be normal ... someone knows how to go on to restart it normally and not with twrp?
Thank you

TWRP, Magisk, & Xposed for the NX619J

This is a translation and rework of youyim2's executable. I've rewritten some of the batch file to make things more streamlined, as well as translated the whole thing into English. I am not the device maintainer. If you have questions, I'll help as best I can. This is only for getting TWRP, Magisk, and Xposed. You should be able to flash Open GAPPs if needed with no issue once you've got TWRP installed.
Download the zip file. Extract the contents. Run the *.bat file. Follow the instructions.
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
TWRP:
To get TWRP into English (or your language of choice), boot to TWRP recovery. When it shows up, slide the bar to the right to unlock it. After that, tap the button second from the bottom on the right column. This takes you to the Settings menu. In here, tap the globe icon in the top right tab. Choose your language from here.
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB

Thanks, I can't flash twrp is fail

decscomputer said:
Thanks, I can't flash twrp is fail
Click to expand...
Click to collapse
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.

Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.

decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
If you read Chinese, you could try the tool in this thread. It's what mine is based on, and may be better suited to the Chinese version.

Added options to reboot into recovery and bootloader as well as some more translation and other text adjustments.

decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
OEM unlock has to be switched on in developer options do you have that switched on?

cajunflavoredbob said:
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.
Click to expand...
Click to collapse
Yes, I did the bootloader Is unlocked and I did the fastboot unlock but when I try to Flash twrp Is fail with a message exceded limit Max AND too password Is error or something like that. I try with the .exe AND directly with adb but it has the same result.

cajunflavoredbob said:
Hello friends. I have a problem and I can not find the solution .. in the magisk manager some modules are not shown when looking for them, like pix3lify, google framework, camera2api y more. The first time I rooted my nubia and installed magisk manager, the modules were shown and I could install them and they worked, but then I gave a full reset to red mars and since then I have not seen the modules never again. I have already reset the nubia more than 10 times, changed the language, installed other magisk manager apk, and nothing.
this magisk manager does not let me install modules from github and if I download and install a thirdparty zip from the web, magisk installs it but the module does not apply or is not installed for some reason.
Is the same in twrp:crying:
I do not ask for support, but if someone knows how to solve it or gives me any suggestions? please
Thanks
Click to expand...
Click to collapse

I have a problem with the bootloader
when i try to bootloader my nx619j , the bootloader failed and the message is "command write failed((too many links))" can u help me pls?

cajunflavoredbob said:
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB
Click to expand...
Click to collapse
One thing that I have found rather disappointing with all of the "guides" (that can only be loosely called such) is that nobody has explicitly mentioned HOW you have to unlock the bootloader on Nubia devices without downloading something.
In fastboot mode, after toggling Bootloader Unlock in developer settings, one must type:
fastboot oem nubia_unlock NUBIA_NX619J
THEN you can do: fastboot flashing unlock
Flashing a boot image may require you to redo the bootloader flashing unlock to bypass the "This device is corrupt" screen.
Packed up Windows executables aren't exactly helpful for those of us using Linux or MacOS based systems. Even then, the Red Magic Mars packaged bat files/tools didn't install correct drivers for me on Win10. Could never get the device recognized within Fastboot on my Win10 Intel desktop after updating and reinstalling drivers.
There is also another quirk with the Nubia devices that I ran into that I have seen mentioned only once on another device's forum.
If you're running a Ryzen/AMD based system, you may have to issue the fastboot commands on an Intel based system instead.
Why? Beats me. It makes no sense, but after hours of pulling my hair out, I happened to come across a post suggesting it and gave it try.
Typing in the same commands with fastboot in the same OS (xUbuntu 20.04) with the same exact versions of every tool used... failed on my Ryzen desktop but worked fine on my Intel laptop. Had I known, it would have saved me several hours of swapping cables and reflashing software.
Also, for those (like me) who don't exactly like blindly trusting software found on forums.
You can download the official system images here:
REDMAGIC Mars
VERSIONS Europe & Asia: V207 North America: V111 LAST UPDATED 10/28/2019 DOWNLOAD V207: Download V111: Download Go to flash instructions UPDATED AND ADDED FEATURES Game Space: Call...
help.redmagic.gg
Pull boot.img from the update archive and use another device with Magisk installed to repackage the boot image for the Mars to flash yourself.
fastboot flash boot modified_boot_image.img
And done.
Due to the risk of bricking the Red Magic Mars within TWRP, I'd rather avoid using it entirely... so I only flashed a boot.img modified with Magisk instead.
One nice thing of note about the Red Magic Mars. It has an actual recovery partition and doesn't use the clusterfluck that is the A/B partition scheme.

Can i just go back to how it was?

I don't even know why I wanted to root my phone. I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img and the twrp installer .zip, I get this message saying
"Unmodified System Patition
Keep System Read only?
..."
and I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Have I bricked my phone? Is there any way for me to go back?
Thanks for the advice.

That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock

scp-507 said:
I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Click to expand...
Click to collapse
You cared enough at one point to start the process. Whether to root or not is a personal decision, based on what types of added modifications of features you want out of root, and how important those are to you. Maybe you have changed your mind to that point. And I am biased to my own opinions. But that opinion would be to go ahead and finish the job, since you got this far. Nothing wrong is going on really, you just got stuck, not knowing what to do next. It does happen from time to time, when modding these devices. And nothing to get discouraged about. You did the right thing coming onto the forum and asking before doing something you were unsure about.
scp-507 said:
Have I bricked my phone? Is there any way for me to go back?
Click to expand...
Click to collapse
This is pretty hard to brick. Unlocking the bootloader, flashing TWRP, and root likely will not result in a real brick. Even if you brick the phone, there is an unbrick tool that will mostly likely get it up and running again.
scp-507 said:
I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img
Click to expand...
Click to collapse
It's not necessary any longer to flash the patched boot.img in order to root. Follow the "Recommended" install method from the TWRP thread, which is simple and straightforward. It's pretty much what the previous response outlined above.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
The method you are following (flashing a patched boot.img) does work. But it has more steps. And you have to be careful to flash the correct boot.img for your OOS version. Otherwise, you may have some issues. So going with the easier method is better, in my opinion.

djsubterrain said:
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
Click to expand...
Click to collapse
Is that true for all phones?

If you have the Global OP7Pro and not the T-mobile variant you don't have to be afraid of bricking the phone. The MSM unbrick tool can bring your device back to stock if its bricked or even if its not. I am not sure if the MSM tool works on the T-mobile variants, but it might.
I've hard bricked this device and successfully used the tool to recover it.

djsubterrain said:
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
Click to expand...
Click to collapse
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?

scp-507 said:
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
Click to expand...
Click to collapse
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?

Well if you relock your bootloader you won't be rooted or have TWRP... It will also wipe all of your data like starting over when you got the phone out of the box.... If you want to stay rooted and use twrp you will have to deal with the splash screen all of us see it on our phones also. Basically you need to have the bootloader unlocked to keep root and have TWRP

scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
You can't relock your bootloader, you currently do not have the default recovery partition, if you really want to relock your bootloader you would need to flash the stock rom back over itself so it replaces the recovery with the default one. Then you can run "fastboot oem lock" but be aware, as I said before, this will want to wipe your data so the rom will go back to default setup. Remember to disable bootloader unlocking from the developer settings if you do, then you will be back to the default stock rom state.

scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
If you want root, you need to leave the bootloader unlocked. That is normal, and just how it is. The warning screen is just something to live with.
You need to return to full stock (ROM, boot.img, recovery) in order to relock the bootloader (otherwise you will get a bootloop or no boot). Which of course defeats the purpose of rooting the phone. So again, having the bootloader unlocked is the normal and expected state, when you are rooted.

[8 DEC 19] Root Oxygen OS 10.01 for OnePlus 6, No TWRP or Factory Reset Required

I spent all day trying to find a way to root my phone after moving from Lineage OS to Oxygen OS 10.01. Namely, https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853.
The problem is that the information given is out of date as of a few days ago, and installing the patched bootloader broke wifi, calling, and probably all sorts of other things.
I want to make sure this is as simple as possible for people having the same issues!
Before You Download
You MUST be running Oxygen OS 10.01 exactly.
You MUST be on a OnePlus 6 (not a OnePlus 6T)
You MUST have an unlocked bootloader (Google for instructions, "fastboot oem unlock", this will require a factory reset)
Install ADB and Fastboot on your computer (Google for instructions)
Installation Instructions
Make sure you're running Oxygen OS 10.01 for the OnePlus 6. If you're on an earlier version and need to install, download HERE and install it as a local upgrade (Google for instructions).
Download and install Magisk Manager. I'm using Version 7.40.
Download my modified boot image here
Put your OnePlus 6 in Fastboot mode and plug it into your computer (Google for instructions)
Place my boot file, new_boot_image_xda.img, in the same folder Fastboot is running
Run fastboot flash boot new_boot_image_xda.img
Run fastboot reboot or otherwise reboot your phone.
If you want to do this on other devices:
Extract boot.img from your ROM's zip file's payload.bin using Payload Dumper 64 (I can't post external links, Google it)
Place boot.img in your phone's local storage
Open Magisk Manager on Android, then "Install Magisk" -> "Patch a File" -> select boot.img
Move the modified boot image (magisk_patched.img) to your computer
Enter the fastboot commands from above, replacing new_boot_image_xda.img with your modified boot image

May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.

jacdelad said:
May be a dumb question: Do I lose data? There's no step of wiping, but I'm afraid this may be necessary.
Oh, and another question: how about updates? Will I lose my data on further updates?
And I'm sure I need to unlock my bootloader before.
Click to expand...
Click to collapse
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.

mouthofrandom said:
Unlocking the bootloader triggers a factory reset (nothing in internal storage is lost, but you lose apps and settings), and you need to do this before rooting. If your bootloader is unlocked, you shouldn't have to wipe anything unless you miss an instruction or install it on the wrong version. You won't be able to update OTA without losing root.
If you're new to rooting, just be prepared to lose your data no matter what, because it's incredibly easy to follow the wrong advice and end up bricked. There have been times where the only thing my OP6 can do is display a white LED because with the wrong command, I wiped everything from the boot partition, recovery partition, and internal storage. For that reason, you might wait a week or so for more documentation on rooting this phone with this version of OOS.
Click to expand...
Click to collapse
Nah, no problem. I have this phone since it came out and use custom ROMs since then, do not really new. I know that unlocking the bootloader resets my phone. I was just wondering if I can install your image without unlocking, because I'm currently locked (had a problem with the latest Syberia update and choose to stay with OOS). And how to update when OOS 10.0.2 arrives.

I tried it and it worked fine, but today after uninstalling some blotware and rebooting I am stucked on the bootloader warning page which takes me to the fastboot mode after a minute or so (this is what used to happen to me whenever I flash a magisk patch boot file) Now I'm downloading the stock rom to get the stock boot.img.

This one video is for oneplus 6t
Pretty clean guide