Database Users

USA band selected and now no network

By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device

s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
hi, i also experience the same problem as u. what i did is i flash breadcrust's mm firmware and nuclea rom. it fixed the problem

But I am unable to connect via adb and fastboot to!
can you give steps to do that?

jflee said:
hi, i also experience the same problem as u. what i did is i flash breadcrust's mm firmware and nuclea rom. it fixed the problem
Click to expand...
Click to collapse
Can you give me steps or links to install correct drivers and all that stuff?

s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
You can also flash stock rom. Follow the steps:
Prerequistes :
1) Install ADB and Fastboot drivers. Instructions in the following link
http://forum.xda-developers.com/showthread.php?t=2317790
2) Download Stock rom from "cyngn.com/support"
cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
3) Enable USB Debugging in Developer options and connect your phone to pc. Grant your pc, the permission for USB Debugging.
4) Enable "Advance reboot" in Developer options.
5) Now reboot your phone into bootloader.
5) Extract the contents of " cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip" to the ADB and Fastboot folder.
6) Open command prompt in the ADB and Fastboot folder.
7) Execute the following commands one by one:
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash reboot
8) Now you are in stock rom.
Please confirm your doubts before you proceed.

akvpappan said:
You can also flash stock rom. Follow the steps:
Prerequistes :
1) Install ADB and Fastboot drivers. Instructions in the following link
http://forum.xda-developers.com/showthread.php?t=2317790
2) Download Stock rom from "cyngn.com/support"
cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
3) Enable USB Debugging in Developer options and connect your phone to pc. Grant your pc, the permission for USB Debugging.
4) Enable "Advance reboot" in Developer options.
5) Now reboot your phone into bootloader.
5) Extract the contents of " cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip" to the ADB and Fastboot folder.
6) Open command prompt in the ADB and Fastboot folder.
7) Execute the following commands one by one:
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash persist persist.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash reboot
8) Now you are in stock rom.
Please confirm your doubts before you proceed.
Click to expand...
Click to collapse
Unfortunately, none of the solutions listed in any place worked for me (permanent solution). What I mean by that is, the airplane mode got turn off somehow while playing with safe mode. But after a couple of restarts, the airplane mode gets turned back on.
As mine is still under warranty took it to a Lenovo Service center and checked with them. They confirmed that this is a motherboard issue and it will have to be replaced. I got mine during the first flash sale in May 2016 and looks like this problem is there with that batch of phones.

Try opening *#*#4636#*#* and changing band ti your native country. I know you would have already tried it.. Just in case you forgot or it helps. ?
Sent from my ZUK Z1 using XDA-Developers mobile app

I flashed cm13 and the problem was solved!

s k said:
By mistake I selected USA radio band from the options in *#*#4636#*#* and now I am not getting networks!
Can anyone suggest any fix?
I tried to connect phone via adb and fastboot but adb is not recognizing the device
Click to expand...
Click to collapse
---same thing happening by me, i have gone to service center but they guys say it's motherboard issue, please let me know if you have fixed this problem?

dharam29 said:
---same thing happening by me, i have gone to service center but they guys say it's motherboard issue, please let me know if you have fixed this problem?
Click to expand...
Click to collapse
Ah long ago, flashed another rom. It will fix.
I don't have that device now, I sold it

s k said:
Ah long ago, flashed another rom. It will fix.
I don't have that device now, I sold it
Click to expand...
Click to collapse
Thanks for your quick response, what's the steps for flashed another rom?

Please help!!! Want to completely un root zuk z1

Hello,
I rooted my phone from the guidance provided here on XDA and it was very easy.. I unlocked bootlader installed TWRP recovery and now I am using custom roms such as nuclear nougat rom. Now I want to sale my phone and sadly people here in Multan, Pakistan are scared to buy a rooted phone even shops as well. So I thought is there any way to fully unroot and get this device into its stock shape with Cyanogen OS with lollipop , locked bootlader and that normal recovery which is there?
I have searched but no proper way is available, can anyone please guide me step by step or provide me a step by step link.
It would be much appreciated

Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk

Nobody wants to buy that phone with cos 12.1 when you can have it with LineageOS 7.1.2:laugh:

Nizamani said:
Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk
Click to expand...
Click to collapse
can you please provide a step by step procedure of that? I have never used all in one toolkit

Nizamani said:
Try all in one toolkit, flash stock firmware with that, u can also lock bootloader with that
Sent from my ZUK+Z1 using Tapatalk
Click to expand...
Click to collapse
Shaheer12345 said:
can you please provide a step by step procedure of that? I have never used all in one toolkit
Click to expand...
Click to collapse
strongst said:
Nobody wants to buy that phone with cos 12.1 when you can have it with LineageOS 7.1.2:laugh:
Click to expand...
Click to collapse
That is infact true, phone gets 100 times better in every way but when i posted the ad people were like "there must be something wrong with your phone which you are not mentioning otherwise who roots this phone"
and I was like "to make it bug free and better obviously"

Shaheer12345 said:
Hello,
I rooted my phone from the guidance provided here on XDA and it was very easy.. I unlocked bootlader installed TWRP recovery and now I am using custom roms such as nuclear nougat rom. Now I want to sale my phone and sadly people here in Multan, Pakistan are scared to buy a rooted phone even shops as well. So I thought is there any way to fully unroot and get this device into its stock shape with Cyanogen OS with lollipop , locked bootlader and that normal recovery which is there?
I have searched but no proper way is available, can anyone please guide me step by step or provide me a step by step link.
It would be much appreciated
Click to expand...
Click to collapse
STEPS TO FLASH COS12.1 VIA FASTBOOT
1/ Install zuk drivers & ADB fastboot in pc
2/ Then dwnld cos fastboot 1 (https://www.androidfilehost.com/?fid=673368273298936352)
3/ After dwnld complete , extract cos zip file in adb folder (location must be in c drive )
& Connect phn with pc & reboot to fastboot mode / bootloader
4/ Then type all commands 1 y 1
Commands?
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash -S 512M system system.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot -i 0x2b4c flash userdata userdata_64G.img
fastboot -i 0x2b4c flash persist persist.img
These codes will bring you back to stock os .
For locking bootloader: fastboot -i 0x2b4c oem lock

I need help! BRICKED

Hello,
I was playing around with the Mi A1 magisk and i was flashing it. But then i by accident pressed lock bootloader (and confirming because i did not payed attention to what it was saying) and now the phone is BRICKED :crying: Only thing i get is the connect sound when connected to PC, but the phone shows NOTHING , just black and vibrates when i hold power and any other button. (no fastboot or recovery)
I think it is done for :crying: which hurts me to say cuz i got it as gift.
I think it will be expensive to fix in service center..
PLEASE HELP IF YOU CAN AS FAST AS POSSIBLE
Thanks in advance.

Same happened to me. Did you change anything with tools? did you erase partitions? what exactly thing were you doing to brick it? only press the lock cant brickt it. Normally you can just re-unlock it and flash with the stockrom. Just give us more information about the process you were doing

Actually i booted TWRP by mohacm flashed Magisk then i powered off the phone and than it happend. When it locked i turned it on and showed the colorfull bar and Mi logo for split second and turned off every single time. After re-unlocking it was in bootloop so i tried to restore with Mi Flash tool and it showed error at the end (something wrong with partition b flash) So i tried again and it froze so i turned the tool off and it put it the state it is now.
Also the response of the phone happens only when plugged to PC

You've bricked nothing at all, just chill. I suppose you've installed all the drivers for the A1 while installing the Mi Flash if yes then install minimal adb and fastboot tool, paste all the files from the images folder from the firmware file to the directory of the minimal adb and fastboot tool, open cmdhere.exe located in minimal adb and fastboot tool folder, boot you phone into fastboot mode(press and hold volume down and power buttons at the same time till fastboot bot appears), plug the phone to the pc, enter the following commands:
- fastboot devices (You should see your device's serial tex next to fastboot text if you see nothing, install fastboot drivers properly)
- fastboot flash modem_a modem.img
- fastboot flash modem_b modem.img
- fastboot flash sbl1 sbl1.img
- fastboot flash sbl1back sbl1.img
- fastboot flash rpm rpm.img
- fastboot flash rpmbak rpm.img
- fastboot flash tz tz.img
- fastboot flash tzback tz.img
- fastboot flash devcfg devcfg.img
- fastboot flash devcfgback devcfg.img
- fastboot flash dsp adspso.bin
- fastboot flash sec sec.dat
- fastboot flash splash splash.img
- fastboot flash misc misc.img
- fastboot flash aboot emmc_appsboot.mbn
- fastboot flash abootbak emmc_appsboot.mbn
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
- fastboot flash system_a system.img
- fastboot flash system_b system.img
- fastboot flash lksecapp lksecapp.img
- fastboot flash lksecappbak lksecapp.img
- fastboot flash cmnlib cmnlib.img
- fastboot flash cmnlibbak cmnlib.img
- fastboot flash cmnlib64 cmnlib64.img
- fastboot flash cmnlib64bak cmnlib64.img
- fastboot flash keymaster keymaster.img
- fastboot flash keymasterbak keymaster.img
- fastboot flash userdata userdata.img
- fastboot reboot
Done!

But the problem is that i cannot boot into fastboot. The phone doesent respond to any actions. I was writing it on the top of the thread. If could boot into fastboot then i would use Mi tool again.

Also when the phone is connected to the PC and i hold the Power and volume buttons (up or down doesent matter) nothng happens just the PC does the dis and connect sounds

try hold volume and and down and then connect to pc after that hold power button volume +,- in the same time then wait 6sec . check if ur phone detect on devie manager port

The PC CAN detect the phone. The problem is not in PC but in the phone cuz it wont boot or show NOTHING on the screen whatsoever.

The PC recognizes it as Qualcomm HS-USB Diagnostics 900E (COM3)

AND you're dumb enough to not mention that. If so buy a cheap type-c cable that works on your phone, make it a deep flash cable(search on youtube how to make it) and flash the stock rom using it, that's my best bet.

dont get how someone can mess up the bootloader. i think in 10 years of my phonelife the bootloader menu never bugged.

Ok guys,
Thanks to everyone who helped my phone Is Back alive thx to Xiaomi Service center.

Bricked - Don't know what to do

I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!

I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.

Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.

xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.

Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.

Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go

jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.

xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.

Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons

jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.

Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl

jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.

Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot

Download any ROM you want. Extract the payload and put it in the payload input folder.

jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.

Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.

xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w

Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.

jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
pause

wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.

OnePlus 2 Semi Hard-Brick. Stuck on BOOT LOGO.

Hi all,
This is a long shot, I hope there is someone somewhere that can help with this issue. I know it's a fairly old phone now, but if anyone has any knowledge about android recovery, it would be greatly appreciated!
Version: OxygenOS 3.6.1.
Rooted via Magisk and Bootloader Unlocked years ago.
The problem was unexpected. It was suffering battery drains for the past month, and last night, whilst on charge, I noticed it restarted. And now it's stuck on the OnePlus LOGO Screen. D:
I can only access FASTBOOT and NOT RECOVERY mode.
What I've tried:
MSM RECOVERY TOOL (w/ QCOM drivers)
Installing ABD Interface Drivers to try an ADB Sideload (but can't get to recovery)
Fastboot flashing stock and TWRP recoveries (can't boot into it - error dtb not found).
Fastboot flash_Ox211.cmd *
Spoiler: * flash_Ox211.cmd does the following
Code:
rem adb reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
rem fastboot erase recovery
rem fastboot flash recovery unofficial_twrp_2.8.7.0-bacon.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sdi sdi.mbn
fastboot flash pmic pmic.mbn
fastboot flash hyp hyp.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oem_stanvbk static_nvbk.bin
rem fastboot flash userdata userdata_64g.img
pause
rem fastboot reboot
None of the above has worked or has fixed recovery mode.
I want to keep my userdata. Is it possible to access that partition, and/or somehow do an 'adb backup'. It might be impossible without the recovery

To keep documenting my findings on extra things that I have done or will do.
Reseating the battery
I have drained the battery and taken the battery connection out the phone for an hour.
UPDATE: After re-plugging, and putting it into charge, the phone bootloops now instead of staying stuck on the OnePlus/Android LOGO continuously. NO CHARGING INDICATOR.
Replacing the battery
If it's a battery issue, then a replacement might work. I have ordered one.
UDPATE: TBD
Fastboot Flashing other recovery img's
dtb not found (or device tree blob) - was an issue when I tried booting into a flashed recovery (stock or TWRP). According to some forum posts, it may be due to flashing the wrong recovery version on the device.
UPDATE:
stock []
twrp-2.8.7.0-oneplus2 [] - no dtb error
twrp-3.0.0-1-oneplus2 []
twrp-3.0.2-1-oneplus2 []
twrp-3.2.1-0-oneplus2 []
...
↑ Doing a fastboot boot <recovery>.img bootloops the phone.

Try asking in the op2family discord server, there are some pretty knowledgeable ppl there. Also you could try asking _undead, he's the one who made lineage 19.1 for op2, see in Original Android Development on this forum.

Huh, it sounds like you're having a similar issue as me. Except I can access recovery but not fastboot... and sideloading isn't working for me.