I should note that I've had serious issues with this phone for the last two months. Touch, reboots, everyhting, boot loops, everything. Only flashed CM because Oxygen stopped working. CM was running sort of ok after the touch boot.img fix but worked something like 10 hours only with no changes to phone at all.
Running CM12.1 yesterday phone crashed, completey wiped, restored. Still issues. Ran the persist partition fix "make_ext4fs /dev/block/mmcblk0p15" (using latest twrp) and it worked.
Today crashed again, started into CM a few times, crashed a home screen or lock screen, then refused to boot, crashing at the OnePlus logo, sometimes turning off. It now crashes from recovery too, sometimes not even being able to enter recovery.
I've made a paypal dispute now, this is insane, no phone has ever caused me this much trouble, even after soft bricks they've been easily fixable. I'm out of patience now. I hope to find some sort of answer or explanation for this.
(sideload doesn't work)
Managed to get it into recovery, adb push worked after some issues, installing CM 12.1 latest nightly now. Will report back.
Edit: Phone returns to bootloop while installing. Will flash new TWRP from Fastboot.
Edit 2: Phone is now seemingly booting into CM.
Edit 3: Phone crashes at "enter wifi password"...
Flash the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
Heisenberg said:
Flash the stock images with fastboot. See section 8 of my guide:
http://forum.xda-developers.com/showthread.php?t=2839471
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
Thank you, pushing ooold recovery now and will test, will do yours if that fails. Which it probably will....
Followed your steps : Booted, crashes when signing in to google... FFS now when starting. AAAAAAAAAAAAAAAAAAAAAAAAARGH
Related
Hi all,
I need the pros here. It's NOT the regular wipe/clean/factoryreset bla bla issue.
received OPO from china with colorOS. Having the strangest behavior ever! I just can't install cyanogenmod 44S.
First I'll describe what I did:
unlock bootloader + TWRP with root + installed 44S using that comes prerooted from here: http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-4-4-4-xnph44s-t2932551
device stuck on boot (powered by android msg)
wipe dalvik/cache didn't help.
wiped again ((format dalvik cache data system) and installed using fastboot official 44s from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
eventually after almost having a heart attack and trying all the permutation of wiping/installing official/unofficial cyanogem 44S - I thought installing an older version.
I can'ts emphasize how many times and effort I put into installing 44S.
I then wiped everything again (format dalvik cache data system), rebooted to recovery and installed 25s official.
It's working!
now I try to update but OTA doesn't find anything. tried reverting to cyanogenmod recovey also but that didn't help.
so I thought installing the zips one by one (the OTA ones) but that doesn't work because I get error executing updater binary in zip and something with apache.xml
In addition, I hate the fact I don't have native OTA...
Please help me upgrade to 44s and if possible - restore OTA functionality. I have this strange feeling that I destoryed something in the device internally or something. I don't see a reason why 44S won't work on my device after having full wipe....
I love you all please help!!! Thanks!!!!
p.s - One time I did succeed booting to 44S but when I reset the device (after factory reset) It was stuck again in boot screen.
Exactly what happens when you flash the 44S fastboot images? Can you please copy/paste the text from the command prompt here?
Transmitted via Bacon
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
ron.r said:
I can flash using fastboot 44s without any issues. But after that I can't pass the "developed by android" boot screen...
Just tried again and this is the fastboot log: http://pastebin.com/TyaBn85F
Everything seems ok.
Does the fastboot zip that comes from cyanogenmod download page includes the stock kernel as well?
Click to expand...
Click to collapse
Yes it does, that's the boot partition.
Transmitted via Bacon
ek69 said:
Did you wait enough time for it to boot? I find initial bit after a flash takes quite a long time. Sometimes up to 5 min
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
i'm 20 minutes since installing. still boot screen.
I suspect it's something to do with either Color OS that came with my device handles file differently and left some buggy stuff that cyanogemnod can't handle OR cyanogenmod changed the ROM in 44s to raise somekind of a flag for china OPO (however with 25 I still can't use OTA or manual OTA zip)
It really sucks...I don't know what else to do.
Is there a special cleaning methodology I can use? (except format system/data/cache/dalvik from TWRP) to make the device as clean as possible before installing using fastboot?
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
ek69 said:
Try reading the color os thread. There has to be someone who wanted to go from color os to another os and maybe there's a different way for that
Sent From Lollipopified Bacon Goodness!
Click to expand...
Click to collapse
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
ron.r said:
Actually Iv'e been stuck on google (xda especially) trying to find answers for the past two days...and nada...
Click to expand...
Click to collapse
Go back to Stock Color Os and try this. Might just work.
https://forums.oneplus.net/threads/oneplus-one-coloros-to-cm11s-the-right-way.77361/
and no I am not a pro
Thanks. Saw that link. Just thought it's usless to go back to Color OS and do the whole process again...
UPDATES:
was able to install 33R using fastboot and everything works amazing including OTA...
BUT - after updating to 38R I have the same issue again. The device doesn't pass the boot screen.
UPDATE 2: After going to sleep frustrated with the device Off I woke up and tried to turn it on - and - it's working. how weird is that?
UPDATE 3: with 38R working (I really don't know how) I got OTA to 44S. I gladly updated. after pressing 'Install Update' the device turned off and didn't show the regular update script running in TWRP. Now the device stuck on boot screen again...so i'm back to square one.
Could it be that cyanogen changed something to block china versions?
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Ok. I know what's happening but I can't explain that.
Unless the device is powered off and after 30 seconds turned on - there's no way to pass the boot screen.
Restarting normally from working state doesn't work, restarting from recovery, power off and power on immediately doesn't work as well.
The ONLY way for me to pass the boot screen is to power the device off completely, go drink a small beer, come back (30 seconds is enough) and turn the device on.
Any advice???
ron.r said:
UPDATE 4: turned the device in recovery mode and the update script (from 38R to 44S) ran immediately and when it's done it restarted the device.
The device is now back on. seems to be working with 44s. I'll do some more tests and if everything is fine i'll mark as solved.
BTW - the magic was probably installing 33R and from there start updating using OTA. However I don't know how to explain that after 38 OTA and short night sleep the device decided to wake up and work...
Click to expand...
Click to collapse
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
gioninardo said:
Hello RON,
I'm in the same situation; did you solve the problem?
Briefly follows my tests:
- after updating from OTA to 44S the opo stuck at logo.
- reflashed the stock 38r...
- Applied 44s update from recovery but after restart the system stuck.
- installed the calkulin 44S and radio file from twrp... the opo stuck at logo "1"
- FLASHED stock 44s and new kernel from https://cyngn.com/products/oneplusone/ : stuck at logo.
Click to expand...
Click to collapse
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
ron.r said:
reboot to recovery
it should install the 44s update
then restart normally.
if stuck on boot - turn the device off. after 30 seconds turn it on.
that worked for me.
Click to expand...
Click to collapse
thank you.
Already done... but without result!
Just flash the 44S ROM using fastboot. You can find them on the forum.
Why flash an old ROM and uwe OTA if the most updated ROM is available...
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.
Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Change the battery. U are not only one... There are lots of people had this issue after 2.5+ year including me. I changed battery two days ago (not original) now its work normal.
https://forum.xda-developers.com/showthread.php?t=3565871
https://forum.xda-developers.com/showthread.php?t=3610933
Sent from my A0001 using Tapatalk
naeem76 said:
I had been using Sultan's 6.0 ROM for a long time now. but it was causing issues and I wanted to try something new. I downloaded Tugapower (7.1) which I used before, and stock OxygenOS 2.1.4 flashable.
I did a nandroid backup of Sultan's ROM, I installed 7.1 which worked fine, and then wanted to test OxygenOS, which didn't boot, and then i proceeded to restore the backup. I left the phone to charge during restore, and I came back to see the phone massively hot and won't boot, not even into recovery. I checked fastboot and that worked.
I've tried a lot of stuff but none failed to boot.
Things I've tried:
1. Fastboot restore of CM11S - gets stuck at rom boot animation first try then bootloops at boot.
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
3. Fastboot restore of CM11s and then CM13 snapshot by recovery - bootloop
Recovery does not work by Power-UP-Vol. Only works once after flashing TWRP via OnePlus One Toolbox. and then bootloop if i try again.
ADB works in TWRP, i can also see my internal storage
4. Tried re enabling /persist partition using make_ext4fs
5. Tried MSMDownloadTool, drivers are fine, it flashes fine, but still says a lot of .img like recovery persist system userdata64 failed.
6. Tried Qualcom QSIF tool to restore ColorOS, same, flashes correctly, but still ROM does not boot.
7. Tried MiFlash to restore ColorOS, same as above.
Is my beloved OPO really gone? Or can i fix this somehow without taking it to Customer Care?
Fastboot works perfectly, also recovery works well when ColorOS is flashed. But just nothing makes the ROM boot. Also sometimes the battery starts counting down from 0 to the exact battery percentage
Click to expand...
Click to collapse
Did you tried flashing stock Cos13.1.x through fastboot?
Mr.Ak said:
Did you tried flashing stock Cos13.1.x through fastboot?
Click to expand...
Click to collapse
Yup I've tried that
naeem76 said:
Yup I've tried that
Click to expand...
Click to collapse
So,what happens after that? Does it boots?
Mr.Ak said:
So,what happens after that? Does it boots?
Click to expand...
Click to collapse
2.Fastboot restore of OxygenOS/CyanogenOS - same as above. Once it booted after i "Fixed Selinux" thingy from TWRP because I remembered that was an issue when i went back to 6.0 from 7.1 a few months back, but mobile data didnt work and it rebooted and started boot looping within seconds.
Here this one, it was weird, it never booted afterwards
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
Device works fine when it is in TWRP? Like,no reboots or power off(s) whatsoever? Battery works fine in TWRP? Like,charging and stuff? If it does,then this is unlikely a battery issue,however,I would suggest you to remove battery(go through tutorials on youtube) and attach it again.
This has happened to me before,like if I'm not able to flash anything from TWRP then I just change/update recovery to unofficial/newer versions of it(did you tried this?) or,I just flash Cos13 through fastboot then it boots up fine and I flash TWRP again and boom,everything is back to normal.In cases where I'm even fail to flash Cos13(shows system error/system partition corrupt) or I'm not even able to boot to fastboot i.e.,hardbrick,I just use Cm11S restore tool(modified version of color os toolkit,you can find on general thread) and it flashes perfectly fine and boom,device is back!
I hope it helps!
Ps- This is the tool I'm talking about,
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
I always use this because after flashing from color os tool,I used to get bootloop,though fastboot mode was accessible then so I could just flash Cos13 through fastboot and I no longer get any system errors and it boots up fine.
naeem76 said:
Bump.
Update: The phone doesn't reboot anymore constantly, it just powers off after the initial oneplus logo
twrp sometimes shows symlinks error, and won't reboots if i Flash anything, cwm flashes fine but no system is booted
Click to expand...
Click to collapse
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
It happened to me once. I had to erase every partition via fastboot, not only system data and cache, but also modem, efs, recovery ecc. Then I flashed stock COS13.1 partitions images and it worked. Just remember: do NOT turn off or reboot your phone between the erase and the flash, it could hard brick the device!
edit: You should also backup your existing efs partition via recovery.
Fixed my device. For future reference, it was a battery issue, Just couldn't retain enough charge, enough to boot into recovery but not enough to boot any ROM, Changed battery and everything is back to normal
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
naeem76 said:
Fixed it Guys, Battery issue, had enough charge for recovery, but just couldn't boot a rom. Changed battery and everything's fine now
Click to expand...
Click to collapse
@psxda97
Mr.Ak said:
@psxda97
Click to expand...
Click to collapse
psxda97 said:
I think it's a battery issue. There are so many people facing the same issue. Trust me,just change your battery.
Click to expand...
Click to collapse
psxda97 said:
Click to expand...
Click to collapse
My trust on you
naeem76 said:
My trust on you
Click to expand...
Click to collapse
LOL!
I'm glad it worked
I got my OnePlus 7 Pro today and tried to install Magisk by patching the boot.img. After trying to flash the patched image, I now have an issue where rebooting the devices leads me straight back to the bootloader. Trying to enter recovery also leads me straight back to the bootloader. I tried flashing the original boot.img I extracted from the OTA update file provided by OnePlus, but it still isn't working. I do not have TWRP or any custom recovery installed. Any help would be much appreciated. I noticed similar threads, however they all installed twrp, though I haven't yet as trying to run "fastboot boot twrp.img" always resulted in it booting to a screen saying "fastboot mode" which wasn't terribly helpful.
Edit: Its not the tmobile/5g/carrier version. I purchased it through OnePlus' website though I forget the exact model number.
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Faith1105 said:
Well, "fastboot boot twrp.img" does not work on all devices, sometimes you have to use: fastboot flash boot insert_twrp_img_name_here.imgLearned that the hard way, also use the unofficial twrp from mauronofrio.
Had the same problem as you have, and fixed it with that unofficial twrp.
Click to expand...
Click to collapse
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
mnbvcxzl90 said:
Did you need to completely revert to stock after the issue, or did flashing twrp fix the fastboot loop?
Edit: Trying to flash the stock fastboot rom currently as flashing twrp did nothing probably because me trying to fix it broke everything. Hopefully the stock rom will get everything back to a working state where I can try again, just this time flashing twrp.
Also using windows this time instead of linux....
Click to expand...
Click to collapse
Ok, so, trying to restore stock seems to have failed miserably.... any advice is most welcomed qq
OK.... so trying to unbrick the device using the msm stuff, I couldn't even make it to the downloader screen. After holding volume +/- and powering off, my screen is now black HOWEVER the phone gets detected by windows when I plug & unplug it. I have no idea what to do anymore. Someone please help
Figured I'd give the solution here in case someone else is in the same exact problem as me:
Follow the instructions over at https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595
I tried to de-brick it using the fastboot roms and all that, no dice. The only thing that seems to have worked was following the above and using the msm tool. Everything wiped, but hey, at least the phone is bootable again and now I have a way to fix it should this happen again. Yay for happy endings.
Edit: Also, following Faith1105's advice, flashing twrp to boot instead of trying to just boot it first worked successfully and from there I was able to install magisk.
Edit 2: Now wifi isn't working.... why life, why...
Edit 3: OK: EVERYTHING IS GOOD NOW. Twrp ran into a boot loop issue, used twrp to flash the most recent android 10 zip, rebooted and was greeted by stock recovery, then used that to wipe absolutely everything and reboot. After skipping through initial setup and making use wifi was working I rebooted again and this time tried booting twrp the way the usual instructions say to, this time it worked for whatever reason so once that started I used twrp to flash twrp's installer and magisk. It looks like everything is working correctly now. If you have the same issue maybe this stuff will work for you or maybe not: I don't know, and honestly I'm now brain dead lol.