Database Users

[GUIDE] Root Huawei Honor 5C and install TWRP custom recovery (EMUI 5.X)

Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.

working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view

Voutsjude said:
working twrp on NEM-L21 https://github.com/OpenKirin/android...0-2-hi6250.img
working supersu on NEM-L21 https://drive.google.com/file/d/0BxW...9ZRGxBTUE/view
Click to expand...
Click to collapse
Page not found for first and file not found for 2nd.
The links and the files mentioned in this thread will work on any honor 5C and are live files.

Nice and Thankssss
shashank1320 said:
did not find any post mentioning rooting for 5c on emui. If there are any, let me know and i will take down this thread.
note-
applicable for windows 7, windows 8 and windows 10
similar steps are applicable for emui 4.x as well but twrp file will change.
saw many user on honor 5c fb page and on xda struggling to get root working on emui 5. Most of the cases i saw, were for emui 5.x. I followed the steps mentioned or as applicable for any devices and i did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working twrp issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
prerequisites-
enable the developer option in settings-
go to settings--> about phone-->tab build number 7 times to enable this setting.
go back in setting page, just above system update, you will see a new menu as -developer options
scroll for the debugging section and enable the usb debugging
you will be prompted for the confirmation with rsa key, just accept it.
enable oem unlock in developer options (just above the usb debugging option) – most probably this option will not be there on emui 5.0 (only few have seen on emui but it was there on emui 4.1 for all but rarely on emui 5.0 or may be because i have used dload most of the time which grayed out this)
installation of required drivers.
connect your phone to pc and install hi suite on pc and it will additionally install all the necessary drivers to pc and hisuite on mobile.
download and install adb from link
accept all the prompts and install adb drive system wise.
once installation is completed, if default options are chosen, it will be under c:\adb
downloading the necessary files.
download twrp from link thanks to @olddroid for his original thread . Rest of the contributor and credit in original thread by olddroid.
move the downloaded file under c:\adb or wherever you have installed the adb.
download the supersu file from this link and put it in sd card or keep handy on pc so that you can copy to internal memory later.
get the unlock as mentioned in this thread
actual procedure
unlocking the bootloader-
backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
on windows machine, go to folder c:\adb or wherever you installed the adb drivers.
press shift+right click together and select open command prompt here
run - adb reboot bootloader (this command may prompt for acceptance of rsa key if not already accepted)
this will boot the phone into bootloader mode.
run - fastboot oem unlock <16 digit unlock code- put your actual code you obtained from huawei site > (this step will unlock the bootloader and will erase all your data)
phone will restart automatically.
installing twrp
once on the system, open the powershell or command prompt again in adb folder (can use the previous instance as well)
run - adb reboot bootloader
once in bootloader, run - fastboot flash recovery twrp-3.1.1-0-venus.img (this will install the twrp recovery for emui 5.0 on your phone)
once done with the flashing the twrp, run - fastboot reboot
rooting
once booted to system, open the powershell or command prompt in adb folder (can use the previous instance as well)
run - adb reboot recovery
and your phone will boot into the twrp recovery.
copy the superu file downloaded to sd card or internal memory.
install the supersu zip.
reboot and enjoy.
Happy flashing.
Click to expand...
Click to collapse
works perfect at me , thank you so much
here is my phone model and android version

Thank you so much... Love ya for this! I wish u all the success for future works..
shashank1320 said:
Did not find any post mentioning rooting for 5C on EMUI. If there are any, let me know and I will take down this thread.
Note-
Applicable for Windows 7, Windows 8 and Windows 10
Similar steps are applicable for EMUI 4.X as well but TWRP file will change.
Saw many user on Honor 5C FB page and on XDA struggling to get root working on EMUI 5. most of the cases I saw, were for EMUI 5.X. I followed the steps mentioned or as applicable for any devices and I did not face any issue so though of compiling this guide for new users who may have faced issue or not able to root the phone. (may be mainly because of correct and working TWRP issue) . I will just simplify the steps so that any new users can do this without any problem and without any prior experience to rooting, it may be long but will be the simple enough for all the users.
Prerequisites-
Enable the developer option in settings-
Go to Settings--> About Phone-->Tab build number 7 times to enable this setting.
Go back in setting page, just above system update, you will see a new menu as -Developer Options
Scroll for the debugging section and enable the USB Debugging
You will be prompted for the confirmation with RSA key, just accept it.
Enable OEM Unlock in Developer Options (just above the USB debugging option) – Most probably this option will not be there on EMUI 5.0 (only few have seen on EMUI but it was there on EMUI 4.1 for all but rarely on EMUI 5.0 or may be because I have used dload most of the time which grayed out this)
Installation of required Drivers.
Connect your phone to PC and install Hi Suite on PC and it will additionally install all the necessary drivers to PC and HiSUite on Mobile.
Download and Install ADB from Link
Accept all the prompts and install ADB drive system wise.
Once installation is completed, if default options are chosen, it will be under C:\adb
Downloading the necessary files.
Download TWRP from Link Thanks to @OldDroid for his Original Thread . Rest of the contributor and credit in original thread by OldDroid.
Move the downloaded file under C:\adb or wherever you have installed the ADB.
Download the SuperSU file from this Link and put it in SD card or keep handy on PC so that you can copy to internal memory later.
Get the unlock as mentioned in this thread
Actual Procedure
Unlocking the bootloader-
Backup all your data as unlocking the bootloader will reset the device and all your data will be erased.
On windows machine, go to folder C:\adb or wherever you installed the adb drivers.
Press shift+right click together and select Open command prompt here
Run - adb reboot bootloader (this command may prompt for acceptance of RSA key if not already accepted)
This will boot the phone into bootloader mode.
Run - fastboot oem unlock <16 digit unlock code- Put your actual code you obtained from Huawei site > (This step will unlock the bootloader and will erase all your data)
Phone will restart automatically.
Installing TWRP
Once on the system, open the PowerShell or command prompt again in ADB folder (can use the previous instance as well)
Run - adb reboot bootloader
Once in bootloader, Run - fastboot flash recovery twrp-3.1.1-0-venus.img (This will install the TWRP recovery for EMUI 5.0 on your phone)
Once done with the flashing the TWRP, Run - fastboot reboot
Rooting
Once booted to system, open the PowerShell or command prompt in ADB folder (can use the previous instance as well)
Run - adb reboot recovery
And your phone will boot into the TWRP recovery.
Copy the SuperU file downloaded to SD card or Internal memory.
Install the SuperSU zip.
Reboot and enjoy.
Happy Flashing.
Click to expand...
Click to collapse
Thank you so much... Love ya for this! I wish u all the success for future works..

tahahaiyat said:
Thank you so much... Love ya for this! I wish u all the success for future works..
Click to expand...
Click to collapse
Thanks for lovely wishes

Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks

outcastWBC said:
Hi all.
I need help with installation ADB. Download file, start installation, accept all the prompts but 0 files copied and dont have file under C:\adb.
What is wrong? How install ADB?
Thanks
Click to expand...
Click to collapse
Method is same as given in instructions. It shoukd install without issue buddy

Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-venus.img
target reported max download size of 471859200 bytes
sending 'recovery' (24464 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.734s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.2.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21972 KB)...
OKAY [ 0.672s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.672s
D:\Android\platform-tools>fastboot flash recovery D:\Downloads\twrp-3.1.1-0-nemo.img
target reported max download size of 471859200 bytes
sending 'recovery' (21918 KB)...
OKAY [ 0.641s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.656s
Click to expand...
Click to collapse
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice

Fr33L4nc3r said:
Hello,
I had the NEM-L51 from my mother running EMUI 4.0x, and decided to upgrade it to the latest version.
It was unlocked, with TWRP as recovery, and rooted.
I did flash back the stock recovery (from HuaweiUpdateExtractor/Update.app), rebooted the device, and applied the OTA (B350 first, then latest B357).
Until then everything is fine, but when I try to flash the TWRP recovery, it doesn't work :
Neither the recommended Venus one, or the current / previous nemo one can be flashed.
Phone and FRP status in fastboot mode both shows Unlocked / Unlock, and the OEM Unlock option in EMUI Developper Settings is also enabled (I toggled it just to be sure).
I'm not sure what's wrong.
Would the update mess with the OEM unlock (by relocking and showing a wrong status) ?
I'd rather not try fastboot OEM unlock with the code (still have it somewhere) and lose data.
Thanks for any advice
Click to expand...
Click to collapse
This should work fine but if not, can try Hassan's recovery

shashank1320 said:
This should work fine but if not, can try Hassan's recovery
Click to expand...
Click to collapse
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
D:\Android\platform-tools>fastboot flash recovery D:\Android\HuaweiUpdateExtractor_0.9.9.5\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35570 KB)...
OKAY [ 0.932s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.954s
Click to expand...
Click to collapse
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
Hisuite can be used for back.. reliable one but not same as titanium backup. Backup WhatsApp on local and g drive. Zip the WhatsApp folder in internal memory and then copy to pc.
Rest other apps, via hisuite (can backup WhatsApp as well here).

Fr33L4nc3r said:
Before trying that recovery, I just tried to flash the stock one from NEM-L51C432B357 full OTA package, and it doesn't work either
So it's not a recovery issue.
How useful is the HiSuite backup ?
If I make a backup with it, will it be able to restore most user app's and system's data ?
I'd rather not re set everything up, and I'm afraid I'll have to retry to OEM unlock the device (so force wipe), even if it says it's unlocked (which it should have remained in the first place)
Click to expand...
Click to collapse
You file should be in path D:\Android\platform-tools\ and not D:\Android\HuaweiUpdateExtractor_0.9.9.5\
I hope adb is installed under D:\Android\platform-tools\, if not, it will be udner C drive as C:\adb\
copy the recovery file whereever the adb is installed and then run the command
fastboot flash recovery twrp-3.1.1-0-venus.img (replace name with your actual file name)

Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)

Fr33L4nc3r said:
Ok, so in fact fastboot OEM unlock status was not accurate, and something I didn't notice was the absence of dm-verity warning when booting (showing when it's actually unlocked)
Click to expand...
Click to collapse
May be. try moving the files and then flashing from that folder and see if it works.

stopin phone
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:

please help me, my device is Huawei GT3 (honor 5c) (NMO L31) it was unlock bootloader before i bought it and now i want to install twrp, so i have to learn a lot of website and Follow me, I downloaded and installed Adb, installed the driver, then downloaded the twrp version with nemo honor for honor 5c, then open CMD or powershell to write commands like adb reboot bootloader then adb fastboot flash recovery twrp.img is under the writing that says Failed (remote: image verification error), I previously copied the twrp 3.0 file ... into the adb folder and renamed to twrp. Now I have to do to install twrp on my device. Please help me.

Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to @shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to @shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.

tanhoang1702 said:
Hello, I have an NMO_L31 (honor 5c - huawei gr5 mini) device and I have experienced a Failed (remote: image verification error) error when installing TWRP while my phone was unlocked before. have searched from a lot of technology pages to find remedies but all failed. But my God, Jehovah listened to my plea and brought me to Shashank123, I contacted him through XDA and I got him a phone number to make friends on the telegram, he helped me out I and I have overcome the above error. I would like to explain how to overcome the error that I tried. First, I went back to emui 4.1.2 (you can see the instructions then allow OEM unlock, then I update the OTA to emui 5, allow usb debugging when the update is complete. Shift + Right click on CMD (or powershell) and enter "adb devices" to see the connected device, then enter "adb reboot bootloader" then enter "fastboot oem get-bootinfo" To check if the bootloader has been unlocked, then enter the command "fastboot oem unlock (code)" to unlock if the relock bootloader, then if the bootloader has been unlocked then the purpose of the command to factory reset. If that is the case, then go to the phone and see if factory reset is complete. Then develop and reconnect to adb, check the device connected to the "adb devices" command then go to the "adb reboot bootloader" command to get to the fastboot and then use the command "fastboot flash recovery recovery_name.img" (for example : Twrp) "Finally, if the word OKEY appears, you are successful. If you can not solve this problem, please send a message to Shashank123 in XDA and ask for his phone number to make friend through telegram and regular help message because he does not often use XDA. Thank you very much Shashank for helping me. Thanks be to my god JESU CHRIST and JEHOVAH.
Click to expand...
Click to collapse
No problem at all mate. Helping through telegram was quick in real time rather multiple post or message and then waiting for response from each other. Due to time crunch, I opted to quick help rather keep you waiting all day long
Good you got your phone as per your requirement and able to do what you wanted. Thanks and Enjoy.
You can edit your comment to say "@shashank1320" (use without double quotes) rather Shashank123 as users may send message or qoute him and get no response as that user may or may not exist :silly:

grand.mohammad said:
hello.please help me.last night i unlocked my gt3 and reseted factory data.but after these my phone stopped in page that typed "your device is booting now..." . but nothing going change.
when i hold power key or power key with volume up down , my phone get restart and show huawei mark and after that show the pervious page that i stoped in it and nothing change again.what can i do? :crying::crying::crying::crying:
Click to expand...
Click to collapse
Boot to bootloader again and see the bootloader state if locked or unlocked. Try unlocking it again.

P9 lite brick? @transition Nougat-MM. PHONE locked, FRP unlock

Hi, second post on the forums, I'm in bigger trouble now.
I unlocked my bootloader and then rooted my VNS-L21 so I could edit my hosts file. I tried going back to official and unrooted firmware afterwards, but something went wrong along the way.
The stages:
-OFW VNS-L21C432B504, obtained bootloader code through DC-unlocker (developer options on, OEM unlock on, debug usb on)
-unlocked bootloader with SRKtool using this method get-instant-huawei-bootloader-unlock-code/
-rooted using Magisk and made a full backup through Revolution Recovery using this method https://ministryofsolutions.com/2018/05/huawei-p9-lite-root-for-nougat-new-method.html
- some tinkering here but don't remember exactly plus I guess it's not that relevant ; I think I got rid of root here
- downgraded from Nougat to MM using dload method according to this thread https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 (first flashing rollback package from C432B504 to C900B300, then flashing C432B160 - full)
- everything went fine, bootloader relocked; but I was unable to upgrade to Nougat/B504 - settings-update showed "no updates available", putting update.app in dload folder (obtained from firmware finder, TeamMT, full B504 file) didn't work, pressing three buttons resulted in error (the version not compatible or sth)
-tried dload with previous rollback file
...and now I'm here:
- phone constantly stuck at boot screen (red Huawei logo)
- dload not starting by pressing three buttons
- recovery not starting by pressing volume up
The only thing I can get is white fastboot screen when connected to PC. It says "phone locked" (bootloader) in green, "FRP unlocked" in red. As usb debugging/oem unlock were not enabled this time, platform-tools/adb with command "adb devices" says nothing is connected, similar goes for SRK
Is it hopeless and my phone is thrash or is there anything I can do? Please help!
PS. All I wanted to do with my root was to change hosts file and then unroot/relock phone, seems like it wasn't worth all this work ( https://forum.xda-developers.com/huawei-p9lite/help/retaining-modified-hosts-file-unrooting-t3868641 )
Update: "fastboot devices" in adb directory resulted in detecting my device, next I found and tried command "fastboot oem [PASSWORD]", now there's a change: "This device cannot be trusted" is showing again, in fastboot I see "PHONE Unlocked" in red now. So time to flash some firmware with a command? But which firmware and how exactly to do that?

You have again unlocked your Bootloader? I suggest you flash a Nougat Compatible TWRP and then from within TWRP make wipes. After that use Hurupdater to flash Nougat firmware. First flash TWRP. If it boots into TWRP then format data and then wipe Dalvik/Art Cache, Cache, Data, System and Internal. Next download Hurupdater and stock Nougat Firmware. You need to download three ZIP update.zip, update_data_full_public.zip and regional update file. Next rename them as suggested in Hurupdater thread. Finally place all four files in same folder in SD card and then install and select only Hurupdater.zip to flash. After it complete reboot to stock recovery and factory reset. If all goes well you will be on Nougat.

Thank you so much, HuRU update method was what finally got me from Marshmallow to Nougat

So. I take it your phone is working now? Glad to know and be of help. If you need help with anything then just ask

Yes, it is, I'm currently struggling with systemless hosts on my Magisk rooted Nougat but other than that - everything works fine. Turns out that most of the recoveries I found then were meant for Nougat, only one recovery file worked on Marshmallow (and I've tried quite a few of such files and they were hard to find).
________________
After flashing TWRP recovery, updating Magisk to 17.3 beta and installing newest (4.0.10) version of Adaway - the problem is gone. My guess is that the fault was on Magisk's side as after updating it the "systemless hosts" function in Adaway was no longer grayed out.

How do i root my Mi 9T Global Version?

Hey Guys,
Today I tried to root my new MI 9T. Since my phone is not the Pro version I had problems to find a guide.
I then found a guide and there as described the boot loader opened and then tried via Fastboot to flash on TWRP.
I get no error message so I thought everything would be successful. I then tried the mobile with "fastboot boot recovery.img" to restart.
From there I was stuck in the bootloop. I was able to successfully save the Mi 9T by editing the complete system with MiFlash.
The phone is back to normal, but the bootloader is still open. Can someone please give me a description of how I can root the phone successfully?
I would like to use Magisk so it would be nice if someone could help me flash recovery and root the phone without flashing the OS again. (Softbrick)

Hello
It's nice if you already opened/unlocked the bootloader of the phone.
You got a bootloop after flashing TWRP, it generally means you flashed an incompatible TWRP for your MIUI version/phone model.
Download "Latest stable" Magisk version => https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip
Copy this "zip" file on the root of your phone.
See this topic to check and download TWRP => https://forum.xda-developers.com/mi-9t/how-to/twrp-versions-xiaomi-mi-9t-t3955946
After flashing a correct TWRP image => "fastboot flash recovery <twrp_file_name>.img", don't do "fastboot boot recovery.img" but instead do:
Keep pressing "Vol+" button on your phone and write "fastboot reboot", wait until TWRP is launched before releasing "Vol+".
Use your PIN/Password code used for unlock your phone to decrypt data => always keep system "read-only" => Install => Flash "Magisk-v19.3.img" => Reboot.
Voilà!

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!

Red Magic 5G Bootloader Unlock Guide: OR get ROOT & TWRP without unlocking the BL!!!
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
WARNING: ANY BOOTLOADER UNLOCK METHOD INVOLVES THE RISK OF BRICKING YOUR DEVICE PERMANENTLY. WHILE THERE IS USUALLY A WAY TO RECOVER, DO NOT ATTEMPT THIS PROCEDURE IF YOU DO NOT KNOW WHAT YOU ARE DOING. BAD THINGS CAN HAPPEN. YOU HAVE BEEN WARNED!!! YOU MAY BE LEFT WITH A USELESS BRICK!!! READ ALL FURTHER WARNINGS EXPERIMENTAL METHOD IN ORIGINAL DOWNLOAD FILE WORKS, I'M USING IT
If you want a NOOB guide look at this post: https://forum.xda-developers.com/nu...beginner-tutorial-unlock-bootloader-t4131585/
Also note a user has managed to fix the FP sensor post BL unlock, see this post here: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
Still, I suggest root bypass it's better.
MegaNZ Link for Root without unlocking the Bootloader, and without breaking the FP, also includes instructions for installing BlackMagic5G (explanation below), adding HD VOLTE, how to restore from a brick, and some other cool tricks: https://mega.nz/file/igphSCTD#OybJo9t1zwvJ0bdbAcN2BCqxWXAfHdhk3JFB4_5xkVc
I suggest you flash my BlackMagic5G and don't unlock your bootloader at all - just root. It's CN 2.52 ROM based. You'll get VOLTE, , GApps installed, Rooted with Magisk, TWRP, debloated, YouTube Vanced, AdAway, SmartPack Kernel Manager, etc. - looks like the Global / NA variant of the ROM. Almost perfect except still uses Messages and Phone from Nubia. Plus you will enable Face Unlock not available in the Global or NA versions of the ROM, and FP will still work! Click on the Google Search bar widget and the mic icon takes you to the Google Assistant, the left icon is Google Feed, type in the middle bar for a Google Search. Has 1Weather Free weather widget that looks great, and Google Calendar widget for your whole month of activities. Translate, Lens, Chrome, all the Google Apps are there. And the Chinese Nubia apps are nearly all GONE!
MegaNZ Link for BlackMagic5G Beta - IT'S ONLY THE DATA PARTITION + ROOTED KERNEL + NA SPLASH SCREEN, you NEED to 1) install the Red Magic 2.52 ROM below FIRST 2) Root using the first link posted above 3) Flash restore this from TWRP: https://mega.nz/file/r9hF2BwS#RrAXiFWSBNX8dLqfrH8nNHo_uigPC8uYXonwhALhGbo
MegaNZ Link for the Red Magic 5G CN 2.52 ROM: https://mega.nz/file/aoxBFAqY#EDt2OZBGTME4ZGKnERKpK_t-aJT_rWgD0aqBFkilRcY
*** NOW THE BOOTLOADER UNLOCK INSTRUCTIONS ***
Go to Settings / About phone / Build Number (NX659_J_ENCommon_V3.08 on North American Variant), click 7 times, Now you are a developer message appears, go back a menu to Settings / Other system settings / Developer options.
Enable:
OEM unlocking "Allow the bootloader to be unlocked"
USB debugging "Debug mode when USB is connected"
Install Minimal ADB and Fastboot (Windows 10 in this example): https://www.androidfilehost.com/?fid=746010030569952951
Default install path is:
C:\Program Files (x86)\Minimal ADB and Fastboot\
Go to the Search button on the bottom on Windows 10, type cmd, Command Prompt will appear in the menu. Right click it and Run as Administrator. All commands to be typed will be run in this Command Prompt window (referred to as terminal) unless otherwise stated to run on the phone.
Now Terminal window appears (it says Administrator: Command Prompt in the heading):
Text displayed is:
Microsoft Windows
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>
Typed in terminal:
cd "c:\Program Files (x86)\Minimal ADB and Fastboot"
I now connected the phone to a USB port on the PC.
On the phone, a Window appeared:
"Allow USB debugging?"
The computer's RSA key fingerprint is:
[36 digit code] Example:
C8:A17:E2:01:F6:A1
:368:10:E8:33:20:FB:
93:7D
Always allow from this computer (it's my computer so I clicked it since I trust the computer)
CANCEL / ALLOW (I clicked ALLOW)
Typed in terminal:
adb reboot bootloader
The phone reboots. Once the phone screen boots, in the center it says: Now you are in fastboot mode.
From the terminal I typed:
fastboot oem nubia_unlock NUBIA_NX659J
The terminal now displayed:
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) START set state to 1 ok!!!
In the terminal I typed:
fastboot flashing unlock *** DO NOT TYPE THIS IF YOU WANT TO KEEP A WORKING FP!!! READ TOP OF POST!!! AVOID THIS WITH THE EXPERIMENTAL METHOD OF ROOT WITH NO BL UNLOCK ***
Now a screen appeared on the phone with a big <!> red icon in the left corner. The rest in white text is a warning message. "By unlocking the bootloader, you will be able to install custom operating system on this phone. A custom OS is not subject to the same level of testing as the original OS, and can cause your phone and installed applications to stop working properly-
Software integrity cannot be guaranteed with a custom OS, so any data stored on the phone while the bootloader is unlocked may be at risk.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data on your phone.
Press the Volume keys to select whether to unlock the bootloader, then the Power Button to continue."
I selected UNLOCK BOOTLOADER and my device was completely erased. The factory OS loaded then. This process takes some time to complete.
Now the device rebooted with a warning message, and a big <!> yellow icon in the left corner.
"The boot loader is unlocked and software integrity cannot be guaranteed. Any data stored on the device may be available to attackers. Do not store any sensitive data on the device.
Visit this link on another device:
g.co/ABH"
Now the device reloads the firmware apparently and wipes all user data. Upon setting up the phone, the fingerprint display registration comes up and asked to place my finger on the back of the phone. There is no fingerprint sensor on the back of the Redmagic 5G! It is under the screen! So this step must be skipped. The ROM setup is corrupt or incomplete, a beta possibly. I setup the phone then went into Settings / Security to try to add a fingerprint. The button to add fingerprint then appears. Once I click the button, I get this error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nuia after-sales service via
4007006600
See the XDA post for recalibrating the FP: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
ROOT FOR ALL DEVICES:
(These files are included in the tools download zip, Magisk 20.4 and MagiskManager-v7.5.1.apk, but this is the official source as updates post): Go to XDA and Download Magisk Manager and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power, release the power button once the screen shows it loading, hold the volume up down until you see TWRP pop up). Flash Magisk from TWRP Install / Zip / sdcard / Magisk.zip reboot and you'll have root.
BL unlock first method was tested on North American variant and it works. But it breaks your FP sensor and gives you an annoying boot prompt.
If at any time you want to remove the OEM Bootloader unlock, you plug into the PC, go to the terminal for Minimal ADB and Fastboot, type:
adb reboot fastboot
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing lock (screen will prompt to relock BL, choose to Relock)
The phone should reboot and install the original software. BUT...
If it says you are corrupted well, you have more issues.
You'll have to reflash the stock recovery.img, reboot to stock recovery, wipe data, wipe cache, and flash the CN update.zip rom to a flash drive FORMATTED TO FAT32 (annoying as hell) But you NEED a USB-C to OTG Adapter to attach a Flash Drive / SDCARD this way). If you don't have one, you better reflash TWRP using the prior instructions and flash the update.zip from there. Install, select the update.zip, flash. Wipe Data, Cache, ART/Dalvik. Reboot.
Now it should WIPE the entire phone and be back to normal Android 10 setup non rooted, no unlocked bootloader. Always beware of data loss doing root functions!!! Always be prepared to setup your phone entirely over again. Google Backup is very good to turn on before you do any of this stuff if you have already installed apps.
*** WARNING - THIS BYPASS METHOD COULD GO AWAY AT ANYTIME. IT SHOULD EVENTUALLY BE FIXED BY NUBIA ***

mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse
You were able to actually install TWRP? Not just boot it? I thought A10 devices cant have twrp permanently installed?

That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.

mslezak said:
That is a very good question my friend. I had to reflash it several times while rooting so it appears you are correct.
Now a window when I FIRST installed popped up and said make Recovery read only so a system update. can't overwrite it, to this I didn't even pay attention. So assuming that question does lock down recovery, it should stick.
Click to expand...
Click to collapse
So its not permanent? Thats what I thought.

Well it could be permanent...
VZTech said:
So its not permanent? Thats what I thought.
Click to expand...
Click to collapse
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.

mslezak said:
What I was trying to say is that I've never had a phone where I had to select "prevent recovery from being overwritten" so I just clicked off the message. Had I selected "keep TWRP from being overwritten" then possibly it sticks. It's just a matter of making the recovery partition READ ONLY.
Click to expand...
Click to collapse
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe

Can anyone send me backup of the super partition?
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)

Future updates...
VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
Yes what I've been told by prior Redmagic Users 3 and 3S is the ROM is released, as long as your boot.img is not patched with Magisk, it can be installed through the menus in Settings / About Phone / Update or someplace like that. You just download the ROM to the appropriate folder on the phone.
So far I have 1 link to a China ROM update here: https://ui.nubia.cn/rom/detail/65
Now on how to install the ROM, I use the Chrome browser set to autotranslate webpages. Most of the Chinese will be translated from here: https://bbs.nubia.com//thread-1136030-1-1.html
Basically it's going to wipe your device clean, and you can use a Nubia backup tool which will save all your items to a folder. Which then you should copy to your PC before installing the new ROM. Then it gives you instructions to get that data back onto your updated device.

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.

VZTech said:
Your probably screwed. I had this issue on a rm3s. You will need an unbrick tool. It was released for the rm3s about 4 mos after release. NUBIA should have true fastboot images available for download, but they dont.
Click to expand...
Click to collapse
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---

apersomany said:
I accidentally flashed an image to the super partition with twrp thinking it was the system partition (it technically is tho) and it bricked my phone and messed up twrp.
Only stock recovery works but the stock recovery cannot fix it by installing a full ota from a otg drive.
I do have a backup on my phone but it is inaccessable.
Could anyone please send me a backup of the super partition or have any idea on how to fix this?
(I tried to use edl and backup my data to recover my backup of the super partition but it seemed like it needed a programmer binary from qualcomm)
Click to expand...
Click to collapse
You should be able to flash the latest ROM via EDL mode if you've ever used EDL mode before, it usually requires shorting pins together in the device, although some recoveries will let you just boot into EDL mode if the phone still boots. It will be detected. Although on this device with the dynamic partition, I don't know how you would flash these in EDL mode... dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm that do not look like fastboot flashable parts. Possibly the unbrick tool for Redmagic 3/3S could be modified to do this for you.

mslezak said:
That's because of the super (dynamic) partition, see from the latest (and only) ROM:
Excerpt of the ROM installation script where it delineates the dynamic vs non dynamic partitions - you have product w/ a file transfer list, then vendor, system, and odm, The other files (boot.img, dtbo.img, splash.img, etc. and other various files) should be flashable with fastboot.
# Update dynamic partition metadata
assert(update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")));
unmap_partition("product");
block_image_update(map_partition("product"), package_extract_file("product.transfer.list"), "product.new.dat.br", "product.patch.dat");
unmap_partition("vendor");
block_image_update(map_partition("vendor"), package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat");
unmap_partition("system");
block_image_update(map_partition("system"), package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
unmap_partition("odm");
block_image_update(map_partition("odm"), package_extract_file("odm.transfer.list"), "odm.new.dat.br", "odm.patch.dat");
# --- End patching dynamic partitions ---
Click to expand...
Click to collapse
Yes those .img files can easily be fastboot flashed. Unfortunately it wont solve his problem. He needs the nubia unbrick tool, which is tough to get. I dont understand why Nubia makes things difficult. They should provide proper Fastboot files.

I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.

apersomany said:
I already tried edl (not to flash, but to recover my backup of the super partition) but it seems like it needed a firehose binary. I still can use bootloader, fastbootd, recovery. It's just that the recovery fails at assert dynamic partition update thing with a error 7 (probably because my super partition turned into a normal partiton). I tried to flash a super empty image made with lpmake and try flashing the ota but that didn't work. I think if someone gives me a backup of the super partition I could flash that and that could work. I also had an idea of flashing a super partition of another devices factory image to make my super partition a dynamic partition, but I couldn't find any online.
Click to expand...
Click to collapse
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.

mslezak said:
I get a Global Device on Monday. I'll try to use Qualcomm tools to make a brick restore image of Global. If I get one made I'll post all the tools to restore the device on Mega.nz. Because of the super partition it has to be done this way. Not via TWRP as you know. I'm working on Dev tools for this device as fast as possible.
Click to expand...
Click to collapse
Thank you so much!

Okay I can't add anything special but daaamn this community is amazing. So much help I love you all

To relock BL repeat the instructions with 1 different command
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
mslezak said:
{Mod edit}
***Bootloader Unlock Instructions for the Nubia Redmagic 5G + installing TWRP:***
Settings / About phone / Build # click 7 times, now your a dev message appears, good back a menu, go to Additional Settings / Developer Options
Enable:
ADB debugging, + OEM unlock
Connect phone to PC, approve device on phone RSA key for USB debugging
From Minimal ADB and Fastboot:
adb reboot bootlader
fastboot oem nubia_unlock NUBIA_NX659J
fastboot flashing unlock
(approve on phone with volume keys to unlock and hit the power button, now you'll get an annoyng mesage on boot as insecure unlocked BL) *ALL YOUR DATA WILL BE WIPED*
Next:
fastboot flash recovery recovery-TWRP-3.4.1B-0324-NUBIA_REDMAGIC_5G-CN-wzsx150.img
fastboot reboot recovery
Enter TWRP, set to not be removed by updates if prompted.
Boot up the device, setup as a new device. You're on stock ROM / kernel now unlocked.
Once you get up and running you'll want APK Mirror app to install stuff on the China Variant it's in the Nubia Playstore. Gboard download as well and set as default it's a lot easier than the Chinese keyboard that swaps between Chinese and English. Set size extra tall for this huge phone (I prefer anyhow). Chrome go download it from APK Mirror app as well. Then go to XDA and Download Magisk Manager and download it and install the APK. Download the latest Magisk as well from the Manager. You can then reboot to Recovery (volume up + power). Flash Magisk from TWRP reboot and you'll have root.
Note on my testing the fingerprint did not work after unlocking the bootloader. It says to contact Nubia support at some odd number. Hopefully they fix this.
Click to expand...
Click to collapse

Just in case if somebody need a Chinese version of official ROM v2.46 for RedMagic 5G.
Code:
https://mega.nz/file/vc0DiabR#npahTop-JXZ9Mwv-lA7G6DxTG2qqOOAf6AwW8NdEEKw

mslezak said:
Just replace
fastboot flashing unlock
with
fastboot flashing lock
Again you approve to lock on the phone prompt with the volume keys and your phone will be wiped and all will be back to normal, you'll be locked. And back to phone setup.
I'd edit the original post but the moderators took away my rights!!! Because I posted a Telegram link WHY - how do you expect development to get better???
BTW anyone with a NEW phone arriving that can record the FP failures and all errors please contact me so I can send to Nubia. They are waiting for me to reproduce the error but I already setup my new phone... Thinking I wouldn't be the ONLY ONE to contact [email protected] ... Guys you want developer support on this phone or not. Contribute please.
Click to expand...
Click to collapse
we found out that using the cn rom it all works without even unlocking the bootloader, even while oem unlock was disabled in dev options but there is some kind of vbmeta img required. a full guide is incoming.

VZTech said:
The issue with that could be any future updates though. Rm uses there own recovery for that. They don't provide fastboot images either I believe
Click to expand...
Click to collapse
You can flash their NX659J-update.zip files directly from TWRP that's how we restored our bricked devices already. So OTA updates no, but you can download them anyway and flash from TWRP directly. Yes we have to figure out a concrete restore method which isn't 100% working yet. I.e. all your data is lost this way apparently AT THIS MOMENT... MORE TO COME.

[SOLVED] Unable to boot any recovery, stuck with fastboot-screen and unlocked bootloader-warning after trying to run Lineage18 recovery on Android9

I'm trying to boot a Oneplus 6T into linage recovery-mode, so I can install latest version of Linage.
I can boot into fastboot, but I am unable the boot the recovery image (or any recovery, also tired with TWRP). When I run "fastboot boot [recovery-image-nam-and-version].zip", I get no errors, all looks good, but the phone then just immediately reboots/switches into a screen showing the OnePlus logo + "Fastboot Mode", and then just hangs there forever.
If I boot normally I am greeted with the "The boot loader is unlocked" warning-screen. It also just hangs there, nothing happens. Nothing is booted.
I am running latest version of Fastboot. OEM is unlocked. When I boot into fastboot, I get this content:
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [redacted]
SECURE BOOT - yes

Solved. Turned out I was a fool and had somehow missed the big red blinking WARNING only to try to install Lineage on Android 11. (I will never do that again, I promise)
SOLUTION that worked:
Getting out of the fastboot-loop: Seems like everything needed to go back to the outdated Android 9 to work, as this was what was originally installed. So: re-install Android 9, upgrade to 10, upgrade to 11, install Lineage. In more detail:
re-partitioned the device, using this guide (selecting an older version, going back to Android 9. I chose the olderst of the 9s, maybe a newer would have done the trick too): https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/
on Linux I had to poke around in the zip-file a bit, but the quick fix was to copy all the commands in the "Fastboot Partitions" section into a textfile and create a script out of it ("#!/bin/bash" in the top, and search/replace "fastboot" to "~/Downloads/location-to-downloaded-gsuite-tools/fastboot"
first boot launched a very simple recovery system. Chose clear all cache and wipe all. After a couple of failed reboot-cycles, it succesfully booted Android 9
(Unsuccesfully tried to upgrade to Android 10 using system dialogues)
Managed to boot into TWRP recovery after fastbooting it:
From TWRP:
Sideloaded TWRW-install into boot to make it persistent recovery. (Pay careful attention to version-numbers, all you install have to fit Android 9)
Sideloaded "copy-partitions.. .zip" as recommenden by Lineage
Sideloaded Android 10 .zip
Booted into Android 10
ran system update successfully to Android 11 (takes some time, appr. 20)
Booted Lineage recovery via Fastboot, this time it ran
Followed the Lineage install-guide through to sideload Lineage 18
Thanx to the people in Lineage IRC to point a lot of this out.