Database Info

Stuck in Boot Loop w/ No Backup

Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.

stealth0wnz said:
Hey guys, flashed this camera mod http://forum.xda-developers.com/showthread.php?t=2516061
and am now stuck in a boot loop. my huge mistake was i didn't make a backup on CWN when i installed it, since i'm a massive noob.
I'd post this in the thread for the mod, but new accts can't post in developer forum (to prevent threads like these, probably).
anyone know a quick solution to this? i've dalvik wiped, factory resetted, wiped cache partition.
edit: i also don't know how to get the stock camera ROM back on the device since it doesn't show up in my windows explorer. if i knew that, it'd be easy to go back to stock.
Click to expand...
Click to collapse
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
Here is a link showing how to adb push - http://forum.xda-developers.com/showthread.php?t=1667929
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.

speedbal said:
If you can get back to the boot loader (hold down power button and volume down) and recovery (choice in bootloader menu), you are fine. I did the same thing. you can adb push the stock file (in his developer thread) and then flash it with custom recovery.
If that doesn't work, you can always flash back stock...... Unfortunately have had to do this more than once and have learned my lesson on backups.
Speedbal
Hope that helps.
Click to expand...
Click to collapse
I guess you gotta learn this stuff at some point, thanks for your help! i forgot that you could push files!

now a brand new issue is that anytime i flash ANYTHING to the phone, adb doesn't see the device anymore.
anyone know what's up with that?

URGENT
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore

SteveRogers1776 said:
I did the camera mod too and happened to kill my phone trying to get a camera back on it. It boot loops bc now there is no os. Tried installing Cm-12.1 on my N910P and its now getting a "Error updating binary zip" on TWRP. I have no idea what to do. I have wiped the phone several times. Tried using odin and it failed when the phone was up and running, now it still fails any rom. Please help. I have pushed thru adb, odin, im out of options on my end. no backup either. Looking for a stock twrp recovery file for any note4 dont care anymore
Click to expand...
Click to collapse
New nightlies of CM12.1 needs the bootloader to be updated to newer version (HHZ12H).
Following the link to flashable zip of new bootloader: https://www.androidfilehost.com/?fid=23991606952613145 (Credit to @mo976)
Flash it in recovery
Wipe the cache
Reboot into bootloader and select recovery.
Flash CM12.1 rom.

I just tried what you recommended . Maybe I'm doing it wrong but I'm still getting "error updating binary zip" when trying to load anything on twrp

IT WAS THE FINAL STEP... and it did not work. (Stuck on boot loader warning screen)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Original post:
SHORT VERSION:
My god this has been one crazy root journey.
I have done absolutely EVERYTHING I could pull up on google to fix my phone, and what seemed to be the final piece to the puzzle, still has not fixed anything.
My phone is bricked, and i would really appreciate help at this point.
The current problem:
When I turn on my phone, it vibrates, and displays the WARNING BOOT LOADER UNLOCKED screen, and stays there forever.
I can access my boot loader, and recovery, but I dont know what to do at this point.
I tried a quick flash stock recovery kit kat with moto tool AIO, and it didnt help.
Any ideas?
LONG VERSION (backround info may help to understand the current issue)
Now, if you want to know what began all of this, continue reading, otherwise the above is my current issue.
After successfully unlocking and rooting my phone
I downloaded SWITCHME, an app that lets you create multible users on the phone. the instructions say that you can use a sub account to test and mess around with anything because you can simply go back to the admin account that has everything untouched.
That was a lie.
1.I deleted .setup, along with a few other things THAT WHERE NOT FLAGGED AS IMPORTANT, assuming the phone would still work. and my phone went bonkers, displaying this infinite message: UNFORTUNATELY, SETUP HAS STOPPED. It was impossible to use the phone, and I could only access bootloader.
2.After endless googling, driver downloading, xda mod installing, I managed to set up my boot loader to do the guide restore stock firmware:http://forum.xda-developers.com/showthread.php?t=2542219
Sadly, I flashed the wrong model number package, I was flashing x35, when I later discovered that my phone is x45.
Flashing the x35 firmware bricked my phone further, to where it would "fail to boot up" and would only display bootloader over and over after attempting to turn the phone on.
3. Simple, I realized I flashed the wrong thing, so I downloaded the x45 firmware from the firmware teem on this website, flashed all of the commands, and bam, the phone starts up with the boot loader warning, and DOES NOT get stuck in the previous boot loader issue I had.
But now the phone wont get past that warning screen so... now im pissed.
Please, if anyone can help me I would greatly appreciate it, Im so close to getting my phone back...
EDIT 2: Looks like the phone wont stay shut down, I realized that if I dont open up boot loader, it will turn itself on and display the warning message.
EDIT:
The stuffs I have, ready to try anything:
CWM touch mod
Moto Tool AIO
Minimal ADB and Fast boot
RETUS x1045 factory firmware
All directories, folders, cmd commands are set up and working properly between all of the programs.
The phone appears to be responding to all cmd commands properly.
I also have the windows one touch super boot root method. (he superboot-windows.bat )
Im afraid to try anything major after freshly flashing the x45 firmware that seemed to bring me one step closer without the help of someone else.

I restored stock to my phone using this link yesturday http://www.ibtimes.co.uk/how-restore-motorola-moto-g-stock-firmware-1447290
it may work for you

I have almost the same problem as if the fastboot not install anything despite not display errors

great that you got it done.
maybe my few cents about my "bricking" story. (xt1032 moto g)
yesterday i wanted to change the rom from cm11 nightly to another custom rom like ehndroix/carbonrom...
first i thought that will be done in a few mins, after having already flashed a custom rom.
then the story began, getting adb work, but, 2weeks ago everything was setup and went fine. dunno why my laptop lost the "drivers".
thats the link which solved that problem: tinyurl . com / kgffjh4 [sorry cant post links outside of xda yet, spam protection]
so after a few hours of getting that fixed i, i began flashing.
suddently i got stuck in bootscreen (ehndroix logo for example)...
then i wanted to go back with my previous backup made internaly of clockworkmod. though i couldnt restore my backup because there was an error message while restoring /data of my backup
also when restoring to factory/wipe in cwm there was that error message about clouldnt "touch" /data, i dont remember the message exactly.
after thinking i bricked everything, i though lets wipe my internal sdcard, maybe that causes the /data error.
then i restarted the device and went for a shower... after 15min i came back and my device was "started".
now i dont know that exactly helped, maybe wiping all data on my phone, or just letting my device boot for a "long" time...
so, thats my yesterdays brick story.

do a factory reset if the bootloader has that option.. otherwise install or run/boot a custom revovery, then either
try the factory reset option there and reboot or..
wipe everything and install a rom

Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!

ngr.hd said:
Ok try this, I'm was a victim too:
Relock and unlock bootloader
Download and flash latest Philz
From there format everything...EVERY PARTITION...switch F2FS
After switching wipe every partition again
Select and execute the other 3 wiping option ie., Clean to install new ROM and the other 2 (I can't remember now)
Do this all over again via TWRP too
Now, this is important, don't use the mfastboot for restoring stock...use the one provided by Google for its Android SDK
Flash the stock images
Flash the Moto Razr boot animation and not the one for Moto G to remove the warning sign
I'm 99.99% sure your phone will boot properly
After the phone boots, reflash the Moto G bootanimation
Good Luck!
Click to expand...
Click to collapse
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors

angelgzg said:
I try to flash any recovery but after entering I get an android and says no commands, and installation does not throw errors
Click to expand...
Click to collapse
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.

ngr.hd said:
You're still in stock recovery.
Use fastboot flash recovery xyz.zip to flash philz recovery
Use this when you're in bootloader mode.
Click to expand...
Click to collapse
I flash the recovery but rebooted into recovery, the android keeps popping up (no commands)

FINAL EDIT: FIXED!!! Sparsechunk files 1,2and 3 have to match the exact name with the firmware folder sparsechunk files.
I did not notice that my firmware sparsechunk files ended in .0 .1 .2 and not 1 2 3 like the tutorial had listed, so I was fastbooting the wrong sparsechunk command. That was the final fix that finally worked for me.
Sorry I'm traveling a d couldnt update thread fast enough.

How To Fix TWRP Bootloop

After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.

I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop.

I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.

Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
Download the deodex rom flash it, then flash no_verity , then format data.

Mastajeff said:
Download the deodex rom flash it, then flash no_verity , then format data.
Click to expand...
Click to collapse
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it

frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.

frenize said:
So, I've done those steps and I'm still stuck in a recovery bootloop. I have twrp, just can't seem to get out of it
Click to expand...
Click to collapse
Decrypt data.
As a general statement : Almost all TWRP bootloops are due to users not backing up their data, and then formatting data.
Hardware encryption is not supported.
Decrypt your data, flash a ROM, and if that ROM doesn't have SuperSU, flash SuperSU.
Go flash my v5 MOD ROM.
Decrypt your data! 95% of TWRP loop cases are due to data not being decrypted, or some other step the user failed to follow.
Good luck.
---------- Post added at 04:28 PM ---------- Previous post was at 04:28 PM ----------
Mrsana said:
I'm still in the bootloop. It now says "No OS installed." Any help would be appreciated.
Also, I'm getting this:
"Failed to mount '/system' (Unknown error 150)"
Help, please!
---------- Post added at 12:59 PM ---------- Previous post was at 12:05 PM ----------
I tried all *three* versions. Still on a TWRP bootloop.
Click to expand...
Click to collapse
This is because you went to Advanced Wipe, and formatted /system.
Make sure you are on the latest TWRP, make sure you're data is decrypted, and then go flash my v5 MOD ROM.

For those that are still having troubles. My guide works: forum.xda-developers.com/v20/how-to/how-fixed-bricked-lg-v20-t3501310

Mastajeff said:
After attempting root on my replacement phone, I could NOT boot to system. Each time I rebooted to "System", it would boot straight to TWRP over and over. I tried reflashing stock files. No verity patching.. etc.
The Fix:
Download the latest version of TWRP specific to your device here https://build.nethunter.com/test-builds/twrp/lge/
Flash the file and the device should now be able to boot to system. If that doesn't work try another version.
I spoke to @jcadduono about my problems and he believes there may have been something weird going on in the misc partition. Reflashing TWRP will/should fix the problem.
Thanks @jcadduono for all the support.
Click to expand...
Click to collapse
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you

It's been determined that it does this when it finds an update in the fota and or misc folders. The phone downloads updates even when you tell it not to. It just doesn't install them without your permission.
Easy to get out of with the volume down and power button reset procedure which then deletes the files automatically or you can delete the files in twrp to fix it.

Poda_jj said:
is it possible that the phone bootloops without doing anything like root and custom roms?
asking cz i'm looking to get the LG V20 but don't know about the risk of it bootlooping itself, without rooting or anything like that, like it used
to happen on lg g4 and g3.
Thank you
Click to expand...
Click to collapse
All the bootloops for the V20 so far are all due to modifications and rooting. There are some roms that work for everyone but just refuses to work on my phone and will just bootloop. I doubt that the cause of the software bootloop is fully known. I've followed directions 100% on working romss and it would bootloop but installed a different version of the same rom and it worked. None of the bootloop "fixes" did anything for me. Fortunately, the rom that I installed is still awesome and works great.
LS997 BTW

I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.

bond32 said:
I fought with this for many hours yesterday. I tried everything I could find and got nowhere. Finally ended out holding Volume Up while inserting the cable to computer to put the phone in download mode and was able to use the kdz file to stock restore.
Click to expand...
Click to collapse
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?

dangercl0se said:
my phone is in twrp bootloop as well, mind going into a bit of details as in how you did the kdz restore?
Click to expand...
Click to collapse
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...

twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.

Team DevDigitel said:
twrp boot loops most deffinately happen due to the update package sitting in your misc folder
use twrp to delete the misc directory as well as the fota directory and reboot.
This hasn't happened to me once since i moved to the latest version for my variant, but happens a ton when using the original build that kept dl the update regardless of me telling it to.
This is a common issue with the LG series and boot-loops. They all do this if there is a expected upate in the misc directory. And has been covered many times over the variants and that deleting misc is the only option. Some of us dont have a kdz, or if youve changed your build.prop the kdz wont restore anything since it will see it as a incompatible device.
before rebooting into twrp on a older build make sure you delete the update package if not this will keep happening. once deleted make sure the updater gets frozen so it wont re-download later.
Click to expand...
Click to collapse
Thanks. I suppose deleting those folders isn't possible without root access?

bond32 said:
Thanks. I suppose deleting those folders isn't possible without root access?
Click to expand...
Click to collapse
yeah MISC and FOTA are protected as read only for the user without root.

Mrsana said:
Turn off your phone. Go into TWRP *manually*. That is, press the power off and volume down buttons. Once you see the LG logo, quickly release the power button and press it again. It will ask if you want to do a factory reset. Say "Yes" to both.
Once inside TWRP (*manually*), do a factory reset. You will be rebooted and it will go back to TWRP. Once inside TWRP after the reboot, go to reboot and choose "System". You should know be out of the TWRP bootloop!
It worked for me.
Click to expand...
Click to collapse
Thank you, This Worked for me.

bond32 said:
There's a few guides here on how to do a full restore. Make sure you download the things you need according to your model V20 and make sure you have ADB working and current drivers installed.
http://forum.xda-developers.com/v20/how-to/restore-v20-to-100-stock-bricked-devices-t3524903/page7
I've used the kdz file before without any problems but it began the process from my home screen. I had no idea how to get it to start if you're in a TWRP loop which is where the "download mode" came in.
With the phone completely off, hold volume up a d plug it in the computer.
That will put it in download mode which is what mine needed.
The other mistake I made, make sure you use a USB 2.0 port, not 3.0. I've always had issues with USB 3.0 drivers not working correctly but 2.0 seems to be good.
My one is fully back to stock on Verizon 13a now and works well, except I think something is taking up space on my internal storage. It shows a max of around 50 gb with used some and 44 gb available. That seems quite low like something isn't right...
Click to expand...
Click to collapse
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.

dangercl0se said:
did that, phone works, no more root.... i rooted the phone again, flashed SU and encryption zip. STILL GET INTO TWRP LOOP.
Click to expand...
Click to collapse
Did you try the above where you delete the misc and fota folders?

Moto G bootloop not loading into TWRP, not taking any fastboot flashes

Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.

zroice said:
Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.
Click to expand...
Click to collapse
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.

aha360 said:
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.
Click to expand...
Click to collapse
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,

zroice said:
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,
Click to expand...
Click to collapse
That's massively odd - have you tried unbricking the device by forcefully bricking it then unbricking it here:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If you have tried everything, then I cannot help you any further sadly.

@zroice
try
Code:
fastboot boot TWRP.img
maybe flashed TWRP can't mount /data or other partition

Stuck in a bootloop, please help

Hey,
Quick rundown: Stuck in a bootloop to some sort of empty bootloader screen which has the readout:
"Start/Restart Bootloader/Recovery Mode/Power Off"
"Press volume key to select, and press power key to select"[Regarding above options]
"FastBoot Mode
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [Gonna leave this out for now]
SECURE BOOT - yes
DEVICE STATE - unlocked" [this line is in red]​
Every choice besides Power Off returns me to the same window. What can I do to recover from this?
Background:
So I was trying to update my OP6 to the current OxygenOS while keeping my root using TWRP and Magisk, which I've done in the past without any issue(i.e. go in recovery flash OS, flash current TWRP, reboot back to recovery, flash current Magisk as I understand it). However this time I was running into an issue flashing the Oxygen update getting an error that said it "failed to map file" for the zip. My first instinct was to update TWRP to see if the newest version didn't run into this issue so I flashed that followed by the current Magisk(no reboot in between). After booting back to standard operations everything seemed fine. I went back into recovery and tried the OS update again, but hit the same issue.
I couldn't find anything specific to OP6 with this issue, but similar questions with other devices suggested clearing the dalvik cache, which I tried to no useful effect. Then I came across this thread (forums.oneplus.com/threads/oxygen-os3-i-have-a-problem-please-help.440587/page-2 too new to hyperlink) and did what I think really messed me up which was boldly follow this guy's advice to do an advanced wipe of everything but internal storage(I also left USB storage intact) from TWRP. This failed to fix the issue with the file mapping error when I subsequently tried to flash the update, though I was able to flash TWRP and Magisk successfully again before rebooting and ending up in this loop.
Any assistance in fixing this or general tips on how to not be foolish when messing around with this stuff is greatly appreciated.

Update:
So I followed the advice gleaned from the resourceful person here(https://forum.xda-developers.com/oneplus-6t/help/bootloader-baseband-versions-blank-t3927565) to try working with the device from my computer with fastboot. At first it would recognize the device as "Android" but be unable to find a driver for it and adb/fastboot both failed to recognize it as a device. After installing MiniTool(more as a way to backup what was on the SD card) the proper device driver also got installed and I was able to access it with fastboot; I ran into similar issues as the linked thread above, solved it by switching to b(still failed) then back to a.
Currently I've got it booted into TWRP and I'm working on getting the current Oxygen .zip copied onto the phone storage but the transfer keeps failing after moving a negligible amount.
Update 2:
Via TWRP was able to sideload the current up-to-date standard OS onto it, however my Google backup seems to have decided to disappear on me and the only OP backup I have is ages old. Anyone have recommendations on data recovery tools?

next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.

NickTheHuy said:
next time just dont change the build.prop file.
serious, it just breaks the system.
heppened to me too.
Click to expand...
Click to collapse
Good to know, thanks for the info!
I assume that happened when I messed around with advanced wipe, do you know which of the folders I selected that would have been under? And just for future awareness, would that have not occurred had I just used TWRP's standard wipe instead?

You can run a program that will install 9.0.6 from scratch, running a batch file...
Save my life before yesterday....

Your device is bricked
If able to access the TWRP recovery then boot into twrp and try to get all the data stored in your computer.
Then use the Qualcomm flash tool to completely recover from your hard bricked OP6.
from here https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
Then its easy, again unlock boot-loader flash TWRP and magisk.