Develop Bugs

Weirdest issue ever seen - endless reboot to "OTA updating", stuck at 53%

I'm a computer science student, so assume me with required ability.
Also I've searched this issue for a whole afternoon, I'll list the methods that I tried below.
Environment:
M8 android 6.0, s-off, unlocked bootloader, rooted, twrp recovery
Some modification to system partition(hosts, busybox, bloatware removed)
Set-up before applying an small ota(~89mb):
Since it's a trivial update, I didn't bother reflash all the system image - and I can't find one for my country(TW)either.
I documented every change in system partition, so I did the following steps to prepare.
1. removed xposed framework
2. unrooted by supersu built-in function.
3. put deleted bloatware back to /system/app, /system/priv-app .
libRSSupport.so and librsjni.so under /system/lib/ have been modified and I don't know why - whatever, I replaced them with the stock one.
4. reflashed stock recovery
I DID NOT(forgot to) uninstall busybox and revert the changes of hosts file, if this matters.
/system/bin/app_process32, boot partion and Supersu modified files are "likely" to be restored to stock.(I have no way to confirm.)
Problem:
Applied OTA, it rebooted to a green spinning circle with progression bar- regular OTA procedure.
But, it stuck at 25% for seconds(guess it's system partition integrity check), and progressed to 53%, stuck at 53% for about 10s.
And then it rebooted, entered OTA update mode again, and so on. I STUCKED AT OTA LOOP.
Methods that I've tried:
Pressed pwr+up under light for 10+ seconds - phone won't accept power button input during OTAs.
Pressed pwr+down / down only when reboot - can't enter fastboot, still OTA updating.
Connected to PC - adb devices not found, fastboot reboot recovery no response.
The current method that I figured out:
I'd like to wait until it drained out, check if charging it shows the normal charging mini kernel.
If so, try button combination into fastboot.
Guess if xda can't help, I'll have to ask for htc... : (

Unrooting the ROM doesn't work; you need full stock ROM to OTA.
But having a non-stock (unrooted) ROM will usually result in an error, and no OTA installation. So I agree this is a big weird.
29988122 said:
Pressed pwr+up under light for 10+ seconds - phone won't accept power button input during OTAs.
Click to expand...
Click to collapse
Try holding power + vol up for 30 seconds or more; even up to a minute (if there is no change). I'm not sure if updating OTA will impact this, but that button combo will force a reboot in every other situation I've seen when the screen is on.

Quick followup:
After battery depleted and complete shut off, I tried reboot to fastboot(by pushing power+down / down only)
No avail.
Even by charging only, it would immediately enter OTA.
I guess htc's OTA would write itself into bootloader, and thus I WON'T be able to enter the normal bootloader/recovery until OTA's completed.
But in my case, OTA's got error so....I got stuck at OTA loop!
The encryption key of my sdcard(adopted storage) was still inside phone's data partition....
Do I really need to give up?
: ( ....

29988122 said:
I guess htc's OTA would write itself into bootloader, and thus I WON'T be able to enter the normal bootloader/recovery until OTA's completed.
Click to expand...
Click to collapse
What is happening, is that the bootloader is designed to automatically look for an update file and install it, before it gives you the other bootloader options.
I've seen another with the similar problem. I couldn't think of anything in that case either. You really can't do much if you can't get to fastboot or delete the OTA file (and I can't think of any way you would do either of those, that hasn't already been tried).
What happens if you remove the SD card? Does it still try to install OTA?

redpoint73 said:
What is happening, is that the bootloader is designed to automatically look for an update file and install it, before it gives you the other bootloader options.
I've seen another with the similar problem. I couldn't think of anything in that case either. You really can't do much if you can't get to fastboot or delete the OTA file (and I can't think of any way you would do either of those, that hasn't already been tried).
What happens if you remove the SD card? Does it still try to install OTA?
Click to expand...
Click to collapse
Ya, still installing OTA.
Someone has told me a way to bypass OTA, somehow it worked. I'll post it here in case someone faced the same situation as I did.
1. let it do the OTA loop until power automatically shut down.
2. take out both sim and sdcard.
3. MANUALLY boot, let it auto shut down, repeat until it can only boot for few seconds or less.
4. plug in charger, check if charging mini kernel appeared or not. If not, repeat step 3.
5. it is told that the bootloader has some kind of low battery protection mechanism that it would skip OTA's under extremely low battery condition. Therefore after 30s or a little bit more charging, pull the plug(essentially shut it down), then magically you can now boot into bootloader via pwr+down.
Of course you'll wanna charge until about 30% or more, then reflash twrp and system partition... : p
Thank you xda and redpoint73, you just made my day!

HTC One M9 Stuck on splash screen after attempting update

My phone's bootloader is locked, never messed with it at all.
So about a week ago I get a prompt on my One M9 for an update. I download it without problem, however while installing it gets stuck at 25%, and gives me a red ! in a triangle, then it reboots. I try to redownload a couple times with no luck. For a couple days I just click don't install after it downloads (why isn't there an option to just not download from the start?) and finally I try it again on Friday morning. This time the HTC One splash screen comes up, and it freezes. I research for a couple hours with no luck. I have a wedding out of town I need to go to, so I decide to wait until I'm back home today to work on it some more.
Today I get back home about 6 hours ago and all I'm trying to do is recover my data, specifically pictures from my wedding. I thought I had it set to auto backup, but I guess that was my One M8 I did that to. I look into TWRP, which won't work because of the locked bootloader, various programs to recover data that won't even work on old phones that I have, as well as "adb -d pull sdcard/ C:\RecoveredData". When I attempt to do that it gives me the error: closed, even though when I type in ADB devices, my phone shows up, although it says sideload next to the SN. I looked up how to fix the error: closed (update adb.exe), but I get the same result, or it freezes (I've left it up for awhile just to make sure it wasn't copying the files)
The only way I can get the ADB commands to work is if I go into the Android Recovery and select "Apply update from ADB". I'm wondering if that is why it says sideload next to my phones SN and why I can't pull the files off of the phone.
I'm wondering if I apply the update that the phone was trying to get via ADB, if that would allow my to keep my current data. Looking at the page
ok, so I can't post URL, but if you google "Flashing a stock Android image without wiping user data", its the first post.
It appears that I should be able to. My problem is that I'm terrified of wiping my pictures out if I do it incorrectly.
I'm on Sprint, and the newest version is 3.41.651.13. I'm pretty sure my phone had 3.41.651.4
I just want to make sure that if I follow that post, with the correct files from sprint, that it would work.
Any help at all would be wonderful.
Edit: I did have USB debugging active before all this happened as well

If I was to install the current version of the OTA on my phone via ADB would that work to get it up and running again? That way I the image would match what the phone is looking for since I can't update it because the bootloader is locked.

NGalaxyTimmyo said:
If I was to install the current version of the OTA on my phone via ADB would that work to get it up and running again? That way I the image would match what the phone is looking for since I can't update it because the bootloader is locked.
Click to expand...
Click to collapse
flashing stockrom should not wipe internal sd-card
can you connect via adb? (if the phone is in recovery mode)

The only way I seem to be able to flash anything is through the adb menu. I found the current update, but because I can't flash the system img files due to it being locked, it fails at around 47%.
I've been looking for the current version for a few days now with little luck.
When I type adb devices, the serial number comes up, with sideload next to it. I'm assuming if I find the right files it'll work

[STOCK ROM][PERRY][MetroPCS.XT1765]A8M'S XT1765 STOCK ROM April 14th, 2018

The original thread was closed...sorry guys I've been busy. Link to the rom has been updated!!!!
Eureka! After two days of trials, tribulations, and extreme reading, I have been successfully able to create a flashable, working Stock Rom for the MetroPCS XT1765. And yes, I figured out how to get root working on it too (albeit experimental)!!!! This has been something visibly lacking in our E4 community, and since its the phone I have, I felt it was a necessity since once you unlock the bootloader or ever took an update its impossible to get the original .xml back on the phone.
Disclaimers Before You Begin:
This tutorial is for people like me that wanted a flashable stock rom for the Moto E4 XT1765 Metro PCS Qualcomm/Perry Variant running on stock Nougat 7.1.1 Please follow the guide carefully. Cutting corners and skipping steps could have MAJOR CONSEQUENCES.
For everybody with other Perry variants, I don't know if this rom will work or not, so if you're feeling frisky try at your own risk as this has only been tested on the XT1765.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
Introduction
The A8M'S METROPCS XT1765-PERRY STOCKROM PROJECT was created from the Motorola PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml firmware, straight from their official site. This was not made from a backup, but from extracting the firmware files itself, and compiling via Assayyad kitchen. Nothing was removed from the firmware on this build, but you will have to flash Open Gapps and add it during installation, as well as No-Verity. Outside of that, it's a virgin rom slightly removed.
Preparation
1. READ EVERYTHING IN THIS GUIDE BEFORE STARTING! This variant can tear you a new one, so get a handle of what you're working with on this.
2. This is only for people that have bootloader unlocked their phones, and can successfully use TWRP on their device. I highly recommend @squid2's TWRP (which is in my download files list on this guide). I can also only give support for those using his TWRP, as that is the one I used flashing this rom.
3. Backup all your data if you want - the phone has to be wiped clean for this to work right as a dirty flash won't cut the mustard. It's not hard exporting your contact list, or using SMS Backup Restore for your call log and text msgs to your SD card. This helps putting back your phone exactly how you had it before this. Takes a second (but be sure to uninstall SMSBackupRestore when you've successfully restored your stuff unless you like it).
4. Download all the files from the list below,and put all of them but the boot.img on your SD card. That is the Stock Rom, the noverity.zip, the magisk.zip, superuser.zip, rootchecker, and opengapps.zip. Make sure the file sizes are correctly matching and that there are no errors in your transferring.
***NOTES SO YOU DON'T FREAK OUT***
Once you flash the rom its going to take 3-5 minutes to boot the first time. It's normal. If you see the "Hello Moto" constantly repeat, that's a bootloop, and you need to wipe and reflash again (even though this did not happen to me). Also, if you see a Bad Key black screen and it doesn't boot, you've made a mistake by not flashing no-verity after flashing the rom. It isn't a brick, you just need to go to recovery and flash it again.
Files Needed:
Download and add these to your SD card. These are the exact files I used on my phone. ***NOTE*** My file share service says they will delete these June 14th, so if you know of a fast share site that's free and can handle big files, please let me know.
Mod Edit: If / When you update these links, PM @Az Biker to reopen this thread.
1. My Flashable Stock Rom: https://drive.google.com/open?id=1ScvA3zO6qHY4mhMtaM4aDajx9ZH6CpYj
2. OpenGapps Nano: https://drive.google.com/open?id=1x3Uz_sia1N3OYPGrdEwJ7TBeSmyiDlEZ
3. No Verity Opt Encrypt.zip: https://drive.google.com/open?id=1FqcpWgYJ16HYjIzZgIlHEZOlKJPjaorM
4.Superuser-r259.zip: https://drive.google.com/open?id=1iFswMvZ2vycIrQ4tK7nTWZAG7zktrPH2
5. Magisk v14.0.zip: https://drive.google.com/open?id=1wyV5EJe2wtSIadFNZsbJQOfGrsNQzG4p
6. Root Checker (Playstore)
7. Boot.Img file in case you make it to the bonus round: https://www45.zippyshare.com/v/Uhru1YeL/file.html
Additional Software: you may need Minimal ADB and Fastboot in case you don't have TWRP installed already for the rooting part or if you run into problems trying to gain root; you'll have to search XDA for that one .
Part I - Installation:
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. As soon as you flash the stock you'll see the phone trying to push an update, as it auto turns on your data if you choose not to set up wifi (which you shouldn't do just yet).
3. Boot into Recovery TWRP. (If TWRP isn't installed, see 3A and skip this part.) If TWRP is installed you can power the device off and then hold the Volume Down plus the Power key to get into fastboot, and with the volume rocker select recovery and then hit the power button to boot. If you have unlocked the bootloader you will see N/A black screen in this process.
3A. If you do not have TWRP installed, With the phone on, run the command in Minimal ADB and Fastboot "adb devices" without the quotations. You should see your phone ID and device. Next, turn the phone completely OFF. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY). Connect device to PC via USB cable. Then open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your recovery image file is in the Minimal ADB directory or it won't work; the type "fastboot boot thenameofyourrecoveryfile.img". This should boot you to the TWRP.
4. Once booted into TWRP, tap Wipe, then Advanced Wipe; check Dalvik/ART Cache, System, Data, Cache ONLY, then swipe to wipe. Just to be on the paranoid safe side, click back (triangle pointing left) to the main menu, go back to Wipe, Tap Format Data, Type yes and wipe. Click back to main menu after - do NOT reboot.
5. Click Install; install A8M'S-METROPCS-XT1765-PERRY-STOCKROM-PROJECT-04142018.zip. Afterwards, go back to main menu.
6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
7. Click Install; install open_gapps-arm-7.1-nano-20180331.zip. Note: This takes 3-5 minutes. You will see a warning that StockRom Gapps is installed. That's okay - ignore it, its necessary. Click back to main menu after.
8. Click Install; install no-verity-opt-encrypt.zip. Click back to main menu after.
If you don't want root, hit Reboot, then System. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed. Congratulations, welcome to your brand spanky new stock rom flashed phone.
If you do want root don't reboot, keep reading the next section.
Part II - Rooting:
Okay, this section might be challenging, but hopefully this will ease your nerves as you walk through the ever so daunting task of rooting. It has some of the same challenges that rooting the .xml had (refer to my "The Complete Noob Guide to Rooting MetroPCS XT1765 Qualcomm Variant" guide for such challenges). This might feel totally redundant, and to a lesser degree it is, but it will pay off in the end. And remember, if at first you don't succeed, wipe clean and flash again!
9. In TWRP, click Install; install Magisk-v14.0.zip FIRST - very important. Do not install supersuser first. Afterwards, click back to the main menu.
10. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
4. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
5. Disable Updates. This thing will race you to that. On initial launch, you should not have the wifi connected. As soon as you put your Sim card back in, IMMEDIATELY cut off your data until you disable updates.
Bonus Round - In Case Of Error -1 Issues:
Hopefully, the first two parts got you straight, and you're playing on your stock rom now. However, this variant is challenging, and getting root could be a pain in the android ass. If you installed either superuser.zip or magisk.zip and got an Error -1 for either or both, this section is for you.
Unfortunately, the boot.img getting corrupted probably is the main culprit. Don't freak, it was a problem with the original root method on this variant straight out the box. Also, if you have been flashing/re-flashing a lot, sometimes it just makes it funky. But its a fix with a little patience.
1. Turn your phone on, and let it boot.
2. Go into your phone settings, and activate developer options (you know, hitting the build number 7x).
3. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below). Very Important. Also uncheck "Verify Apps Over USB", but only if you having probs with fastboot in ADB. You can recheck it later.
4. Make sure you've enabled Allow installation of apps from Unknown Sources (its in the Security section of Settings).
5. Turn your phone completely off.
6. Plug your phone via USB cable into the computer.
7. Press Volume Down and Power to boot into fastboot mode.
8. Open up Minimal ADB and Fastboot command prompt on the PC (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory (same place you see recovery.img that boots/installs TWRP) or it won't work. Download it from the files list above.
9. In Minimal ADB command prompt type "fastboot erase boot. " It might say permission denied, and that's okay. Keep going.
10. In Minimal ADB command prompt type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And no, you don't have to reflash the stock rom after this either.
11. Reboot into recovery - make sure you select READ ONLY when it launches.
12. 6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
13. Click Install; install Magisk-v14.0.zip FIRST - very important. Afterwards, click back to the main menu. It should be successful.
14. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
15. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
If you're still having problems after flashing the boot.img, start all the way over from the beginning wiping everything clean. That should correct the problem and let you install without trouble or needing to flash the boot.img again.
Bonus Round - In Case Of No Root After Root Issues:
As soon as the little bugger tried to force the update via my data when I stuck my Sim Card in, it messed with my root, even catching and cutting it off as quick as I could and not doing a full update. When I rebooted, I lost root. This has happened off and on every other flash - so your root may stick or it may not. If it doesn't, either you can 1. wait for a better method, 2. reflash, 3. live without it for now. This is still kind of experimental for me, as I had to wipe and reset to get root back. Still trying to figure out a more perm way for this like on the .xml.
Enjoy Everyone - I'm learning, taking it one android day at a time but I'll help when I can. It's an awesome day to be a nerd!
Sincere Thanks:
The devs that created a method of root for various variant E4's that sent me on this journey, I love you guys!
The devs behind Magisk, Superuser, and No-Verity!
@squid2 for the TWRP recovery that helped A BUNCH!
@ASSAYYED for the beautiful kitchen that forced me to keep learning.
@Al936 for the beautiful tutorial that helped me figure out how to extract the files needed in the journey.
@MotoJunkie01 for giving me the inspiration to try it on my own.
@madbat99 for the small, but powerful words of encouragement.
And to the community at large that let me ask questions to the point of getting on their nerves. Thank you!!!

[REPOST][ROM][PERRY][MetroPCS.XT1765][STOCK] A8M'S XT1765 STOCK ROM April 14th, 2018
Reserved.

Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.

ilanor said:
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
Click to expand...
Click to collapse
Everything is stock. Just as it was on a complete fresh out the box setup. You will find all the metropcs apps there.

How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.

Moto_E4_xt1765_metroPcs said:
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Click to expand...
Click to collapse
you install ADB and fastboot on your computer then open the folder that contains those. Put the boot image in that folder
Pretty sure this guy that is extremely outdated though

this flashed fine and magisk and superuser flashed fine booted actually a little faster than normal. I don ' know how but it say no service though and it throws an error "error occured could not search" or something similar . how can i get my radios back

Previous Root on Stock + TWRP + Magisk + OTA update needed + Stupidity + Sultan

OK, so I've been getting the August OTA nagging for a bit, and I finally decided I needed to read some instructions on things and get it on my already rooted phone.
I started with...
1. Unlocked bootloader
2. Root on the stock ROM
3. TWRP 3.3.0-0 recovery installed
4. Magisk 19.3 (19300) installed
5. Windows installed platform tools/drivers/etc
What I did...
1. Downloaded the factory image
2. Removed the "-w" from the fastboot update image line in the batch file
3. Ran that batch file... the 1st bootloader bit went fine, but the reboot seemed to not reconnect the phone via usb
4. Unplugging the usb and replugging it successfully seemed to trigger the 2nd radio update bit, and again the reboot left the batch file hanging
5. Unplugged and replugged and the final fastboot update for the image fails saying something about memory (I didn't save what was on screen because CMD.exe closed when I pressed a key).
6. I try to reboot and it gets in a boot loop. Bootloader unlocked screen to all white G screen and back again.
I figured I'm screwed. Might as well give up and do the Sultan ROM...
7. Launch recovery and get into TWRP
8. ADB Push the most recent Sultan Kernel to the phone from my PC
9. Flash Sultan in TWRP
10. Flash TWRP in TWRP
11. Flash Magisk in TWRP
12. Reboot
And here I am looking at my original setup, with all my apps and data. I still have root. No August patch installed, but my Kernel is 4.4.169-Sultan. So....
I have so many questions.
What went wrong?
What went right?
Sultan doesn't seem any different at all... is that part not right?
What do I do now?

boneriffic said:
What do I do now?
Click to expand...
Click to collapse
You can try using a different cable or USB port to see if that takes care of the flashing issue. Sometimes that's all it takes.
I would also double check your fastboot/adb files to make sure they are the latest from Google.

Question Can't access recovery mode and have infinite boot loop

I Have a pixel 6 pro that I have rooted. I was going through the process of installing the latest update, (May 2022), via ADB. I have done this several time with success and no real issues. This time, just as I was on the last step of the update, (what's highlighted in yellow),
(This below is from notes that I've created for myself that I follow along with a YouTube channel)
-Execute the below command and directly flash the magisk patched boot.img file to your device
~ fastboot flash boot AND NEW magisk_patched-.img ~
-Restart the phone
my cat walked on my keyboard, and I think might have caused things to go bad.
Now my phone is stuck in a boot loop. I would like to do a factory reset but any time I can get to the Fastboot menu, (by holding down power and volume down), and select the Recovery Mode, it just sends me to the screen that says that I have unlocked my Boot loader and restarts the phone and continues the boot loop.
I have gone back to the CMD in ADB and have done some of the step over again in the updating process to no avail. I've done the googles with all of the results being the same telling me to factory reset the phone, which I would like to do but can't, so I'm reaching out to here, hoping to find an answer.

How about Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)? Make sure and kill ADB in Windows Task Manager first.

Draco3X said:
I Have a pixel 6 pro that I have rooted. I was going through the process of installing the latest update, (May 2022), via ADB. I have done this several time with success and no real issues. This time, just as I was on the last step of the update, (what's highlighted in yellow),
(This below is from notes that I've created for myself that I follow along with a YouTube channel)
-Execute the below command and directly flash the magisk patched boot.img file to your device
~ fastboot flash boot AND NEW magisk_patched-.img ~
-Restart the phone
my cat walked on my keyboard, and I think might have caused things to go bad.
Now my phone is stuck in a boot loop. I would like to do a factory reset but any time I can get to the Fastboot menu, (by holding down power and volume down), and select the Recovery Mode, it just sends me to the screen that says that I have unlocked my Boot loader and restarts the phone and continues the boot loop.
I have gone back to the CMD in ADB and have done some of the step over again in the updating process to no avail. I've done the googles with all of the results being the same telling me to factory reset the phone, which I would like to do but can't, so I'm reaching out to here, hoping to find an answer.
Click to expand...
Click to collapse
In addition to what @roirraW "edor" ehT said (), you may want to try to just flash the stock boot image first to see if it gets you out of the bootloop instead of going into recovery mode to do a factory reset, since it appears you can get into fastboot mode.
Is it also possible that you may have some Magisk mods installed that need updating that may be causing the bootloop?

Did you try disabling Magisk modules? This might work:
As the phone boots, hold down the volume button to get into safe mode. This will trigger Magisk to disable modules when you reboot. Reboot as normal.
For me the culprit was Addon Features for Pixel Devices.
Otherwise, as the posts above say: flash the factory image or boot.img.

Thanks @roirraW "edor" ehT. That was a pain in the butt suggestion, but the advice worked. Now I'm going and doing a full restore.​
@Lughnasadh, I did what you suggested before I even posted, hoping that it would work but it just sent in into bootloops.​​@peabody42, When I was in the Fastboot menu, I could select all of the options but with the exception of the serial number option, all other options would just send me back to the beginning, starting the bootloop.
Thank you all for the suggestions and help.
​

Draco3X said:
Thanks @roirraW "edor" ehT. That was a pain in the butt suggestion, but the advice worked. Now I'm going and doing a full restore.​
@Lughnasadh, I did what you suggested before I even posted, hoping that it would work but it just sent in into bootloops.​​@peabody42, When I was in the Fastboot menu, I could select all of the options but with the exception of the serial number option, all other options would just send me back to the beginning, starting the bootloop.
Thank you all for the suggestions and help.
​
Click to expand...
Click to collapse
Great to hear it helped. Good luck!
FYI, tagging users doesn't work if you copy/paste the username link in a post - that's just a link to their user profile. Tagging users only works if you paste as value (in Google Chrome and some other things, Control-Shift-V). i.e. if the username is already a link, then the "@" symbol before it won't help anything, and we won't get notifications that you tagged us.