Develop Bugs

RESOLVED-[Q] HTC One M8 (HK)- Help flashing Lollipop

Hello all, I have searched for more than a couple hours and just seem to be getting nowhere. Here's the deal: I have an HTC One M8 with TWRP, root, an unlocked bootloader and S-ON. I want to install Lollipop, but can't take the OTA.
I know a little bit about what I'm doing, I tried to flash a rooted stock ROM but it didn't take. I wiped all directories but the internal storage. Also wiped the Dalvik, `but I could not get the update to take. I tried a few other things but out of fear of bricking my phone I wasn't very adventurous. I flashed the backup I made beforehand and it worked fine.
I think I have the wrong file...? Could my S-ON be the problem?
Sprint HTC One M8 (HK edition)
Android: v4.4.4
Sense: v6.0
Kernel: 3.4.0
Baseband: v1.08.20.0916
Build:3.31.654.2
All I want to do is flash lollipop. Will I have to lock the bootloader and go back to stock recovery to do it? Can I use adb sideload to install it via adb?
Thank you for your time.

http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10

ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
Updating...(0/7)... #(<--- these dots are still in motion like its installing)
Updating the ROM image on your Android phone...
[color=redPlease do not remove the USB connection from the Android phone or launch any programs during the update process.[/red]
Remember, this operation will take about 10 minutes.
Click to expand...
Click to collapse
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.

ckpv5 said:
http://forum.xda-developers.com/showpost.php?p=59071793&postcount=10
Click to expand...
Click to collapse
not_important said:
I'm pretty sure my phone is toast.
PLEASE HELP, it worked just fine before I took your advice...
I relocked the bootloader and verified it multiple times before doing this. I made sure everything was exactly the way it was explained in the instructions, all files were correct.
I put the phone into fastboot, which I verified with adb.
I ran the Sprint_HTC_One_M8_HK_4.20.654.10_RUU .exe file and followed the instructions.
Both the program and pphone are currently frozen. They have been this way for almost 2 hours now.
The phone is stuck at the black HTC splash screen and the installer says
I haven't done anything, its still plugged in.
I don't know what to do, can I just unplug it and flash my bavkup with TWRP?
PLEASE HELP I'M FREAKING OUT.
Click to expand...
Click to collapse
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.

not_important said:
Ok, the phone is not recognized by adb but is still recognized by fastboot, can I reboot it into TWRP by using
Code:
fastboot reboot recovery
then just flash the backup I made before all this crap started?
*EDIT* RESOLVED
Never mind, I resolved it myself. I just typed
Code:
fastboot reboot
and hit enter. It booted right up.
Click to expand...
Click to collapse
I looked through it and all user made folders are gone, but all user downloaded apps are still there. I also noticed that superSU root access was off, but the 'apply on boot' option was turned on, could this be what crashed the updater?

Getting "Your device is corrupt. It can't be trusted and may not work properly"

Getting "Your device is corrupt. It can't be trusted and may not work properly"
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance

docluv01 said:
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
Click to expand...
Click to collapse
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.

Ok, SO teh message is normal?
I flashed factory 8.0.0, and I get the same message,
TheSt33v said:
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Click to expand...
Click to collapse

docluv01 said:
Ok, SO teh message is normal?
After I did a factory reset, I got the message, clicked power when it asked to, then phone just sits at the google screen.
Click to expand...
Click to collapse
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Oh wait, you get the same message if you flash the stock image? Well in that case, I'm not sure what's wrong. You may need to re-lock the bootloader before that message goes away, but make sure you're on 100% stock software before that happens. It might have something to do with the fact that Pixel devices have A and B firmware slots, so if you bring A back to stock, B might still have the Magisk patched image on it. Someone more familiar with Pixel devices should chime in.

TheSt33v said:
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Click to expand...
Click to collapse
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?

docluv01 said:
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
Click to expand...
Click to collapse
I'm thinking so. I'm not sure what the proper procedure is for designating which slot you're flashing to on the Pixel 2's, but it's possible that you now have 1 slot with stock firmware and 1 slot with the Magisk patched image. For the original Pixel devices, the partition names were boot_a and boot_b. So I think, and someone please correct me if I'm wrong, fastboot flash boot <file> will flash the file to whichever slot is active, but using boot_a and boot_b will flash to those designated slots. So to fix your issue, you need to make sure that both boot_a and boot_b contain stock images.
Keep in mind that I've never owned a Pixel before now (although I'm pretty comfortable with flashing other android devices), and I'm not 100% sure about this, so you might not want to take my advice.

relock the bootloader.

Here is what I did:
Fastboot flashing lock
fastboot flashing lock_critical
then tried running the flash-all.bat, got FAILED being it was locked
SO then I ran
Fastboot flashing unlock
fastboot flashing unlock_critical
ran flash-all.bat, seemed to have gone fine. Phone reboots, then after you get the circle, where it says "erasing", after about 10 seconds it reboots and says "your device is corrupt..."
Ughhh, I hope I didn't brick this thing???

sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread

docluv01 said:
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
Click to expand...
Click to collapse
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol

canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
relock your bootloader

canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
Make sure you have the latest version of adb and fastboot from the developer site.
https://developer.android.com/studio/releases/platform-tools.html

I got the message as soon as I unlocked the bootloader. It's normal

I had this issue with old platform tools and could not get my device to boot no matter how many times I flash-all'ed or changed the current boot slot. Upgrade to the latest platform tools and run the flash-all from that directory. If it's still not working, I also unlocked critical: fastboot flashing unlock_critical , so that the flash-all could flash my bootloader as well.

Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.

charesa39 said:
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
Click to expand...
Click to collapse
This is somewhat true. There are 2 different messages. One that says you are running unsupported software and the color is orange. This message pops up on every boot while the bootloader is unlocked. The other message says your device is corrupt, in red. The phone will not boot. I just ran into this issue while trying to flash the november update
EDIT:
I was able to resolve this by updating adb/fastboot. I updated adb/fastboot before but i guess i did it on my other computer.

So was there any way to fix this without having to relook the bootloader? I've already had to set this phone up a second time after the longest marathon session of trying to get both TWRP and magisk to live happily together on this device, so I'd rather not do it again if it's avoidable.
Literally all I did to cause this is press the button in TWRP to switch to slot A, and after rebooting I immediately got the new scarier message that requires a power button press to boot, after which you get the regular nag about the unlocked BL. The device then hung at the Google padlock screen, so I used the buttons to reboot into BL then tried TWRP. TWRP then hung at the splash screen, so I hooked up to the PC and fastboot booted TWRP. When I tried to switch back to B, strangely, it said I already was. I pressed the button to switch to B anyway, then rebooted. The error happened again, but at least the device boots. I tried rebooting again to see if it had cleared up, but unfortunately not.
I would really like to be rid of this without having to start over. I do have a nandroid but I don't even know if I trust a restore to be successful and potentially make **** worse. Thanks in advance!

Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk

matt1313 said:
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.

IrocD said:
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
Click to expand...
Click to collapse
Flash boot.img first. Don't select which slot
Then reboot bootloader and fastboot active slot b
Sent from my Pixel 2 XL using Tapatalk

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?

I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.

stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:

I agree. I got it used tho which is an issue.

Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.

stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.

Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.

Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?

stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.

Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.

I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.

MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:

stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.

smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

Help, might have killed my device

Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?

ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.

like Fury said, your platform tools need to be updated, same thing happened to me.

What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app

fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.

Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.

Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.

Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.

Question Google pixel 6 pro bootloops after root

I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?

webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.

Stupid question also could be the wire your using and usb port

If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .

It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.

fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....

simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards

fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!