Database Info

[Q] No cellular signal & etc (dead Moto G?)

Hi guys,
My Moto G (bought in nov. 2013) just started to behave very strangely - network signal suddenly disappeared and doesn't come back, some minor graphical artifacts appears (can be seen in the video).
https://www.youtube.com/watch?v=vWARkgTBWxE
Also, i can't copy anything to internal storage via USB - i keep getting this error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried reinserting the SIM, factory reset and reflashing the ROM.
I'm using 5.0.2 Lollipop Brazil Optimized v1.1. (the ROM worked fine until today)
Any suggestions how to fix these issues? Or is it HW issues that aren't reparaible? :crying:

I would try formatting internal storage. NOTE: This will erase all data.
TWRP > Wipe > Format DATA > yes​

I would also try re-flashing the stock firmware.

I formatted data, and now i can at least transfer files to the device. I've reflashed the stock firmware, but i still get no signal. Minor graphical artifacts are still peresent

Lauriz7 said:
I formatted data, and now i can at least transfer files to the device. I've reflashed the stock firmware, but i still get no signal. Minor graphical artifacts are still peresent
Click to expand...
Click to collapse
Seems to be a bootloader issue ?

What's the solution then? flash another bootloader via fastboot (if yes, which)?

XT1032 Retail Brazil Firmware Image includes motoboot.img - that is the only 5.0.2 XT1032 Bootloader available.

When you flash the ROM, doesn't it also reflash bootloader? Or do i have to do it manually via fastboot?

Lauriz7 said:
When you flash the ROM, doesn't it also reflash bootloader? Or do i have to do it manually via fastboot?
Click to expand...
Click to collapse
You gave to use fastboot.

Lauriz7 said:
When you flash the ROM, doesn't it also reflash bootloader? Or do i have to do it manually via fastboot?
Click to expand...
Click to collapse
The bootloader will not flash if you are trying to flash an older bootloaer than the one on the phone.
I believe the latest bootloader for the xt1032 is 41.18 (lollipop).

I flashed firmware manually in fastboot mode, and now i have bootloader v.41.18. I still don't get any signal
Also, i was trying to connect to mobile network (In Settings) and I saw "E" (edge) icon with roaming icon, and exclamation mark afterwards. It lasted for about 15 secs and i have never been able to connect to any network since.
Completely dead radio?

Does you phone have the correct imei? Use the dial pad to check by dialling *#06#.

Yes it does. I also confirmed that other SIM cards don't work.

Did you flash stock 4.4.4?

Can i downgrade to 4.4.4? I've heard some issues about bootloader and etc. and risk of bricking it.

@Lauriz7 - did you do the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​

Lauriz7 said:
Can i downgrade to 4.4.4? I've heard some issues about bootloader and etc. and risk of bricking it.
Click to expand...
Click to collapse
You can downgrade, you just can't flash the motoboot file.

lost101 said:
@Lauriz7 - did you do the following fastboot commands:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn​
Click to expand...
Click to collapse
audit13 said:
Did you flash stock 4.4.4?
Click to expand...
Click to collapse
I performed the commands. And i have also flashed stock 4.4.4 now - No signal. Screen flicker is still present.
https://www.youtube.com/watch?v=hlIfQqpwhLE

Screen flicker will always be present unless you flash a stock lollipop ROM.

Well, the screen flicker was also present in the stock ROM, and it's also in the recovery sometimes. But regarding the radio issue, has anyone else experienced sudden loss of network signal? I suppose it's hardware failure...

Downgrade CM13 to stock failed

Hi,
i tried to downgrade CM 13 to the Stock Android 5.0.2 and relock it (I know that Motorla has the unlock indicator, but this doesn't matter here).
So I tried the following steps as descripted in a lot of posts, but every command failed:
Code:
fastboot oem lock begin //success
fastboot flash partition gpt.bin // Preflash validation failed ->version downgraded for primary gpt
fastboot flash motoboot motoboot.img // Preflash validation for tz -> version downgraded for tz
fastboot flash boot boot.img // Preflash validation failed -> version downgraded for boot
So how can I solve the problem? I think it has something to do with downgrading

You may need to use mfastboot.
However, if you have updated your Bootloader; you may no longer be able to flash a firmware image older than Android 5.1. If that turns out to be the case flash the latest 5.1 Factory Firmware Image for your model using Fastboot. If this is not successful, it would help to see a log of the flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219

Unfortunately it makes no difference, same errors.
I already flashed this stock image some time before and it works. And the bootloader is on 41.18.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try with the firmware files in the same folder as mfastboot.exe.
mfastboot flash partition gpt.bin​

Nope, same error

You could simply skip that command. And there is always the option to flash the Stock ROM via TWRP.
[ROM][FALCON][5.1][STOCK] Stock Motorola Lollipop ROM Collection​[ROM][FALCON][6.0][STOCK] Identity Crisis 6​

The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.

Waishon said:
The problem is that all commands failes (including boot.IMG, which is obviously needed). TWRP would be possible, but then I can't relock it.
Click to expand...
Click to collapse
Flash ROM via TWRP, then relock via fastboot. I would expect it to work.

Does relocking work with a custom recovery? Interesting

Waishon said:
Does relocking work with a custom recovery? Interesting
Click to expand...
Click to collapse
I'm not aware of any relationship between recovery and relocking - but I have no personal experience. If you did need to flash the Stock Recovery, this can be done via TWRP.

[Firmware] 8.1 official Moto Z3 Play [BECKHAM]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO Z3 Play
Download Moto Z3 Play Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
adb fastboot
fastboot flash partition gpt.bin ( not mandatory )
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot erase modemst1 ( not mandatory )
fastboot erase modemst2 ( not mandatory )
fastboot reboot
Click to expand...
Click to collapse
Thanks to Motorola firmwares.
Password:
MotorolaFirmwaresLB
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
-DRIVE
-AFH

Will this work on the Amazon version?

Hello, it should work

I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.

twelfth said:
I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.
Click to expand...
Click to collapse
This firmware is for XT1929-4 and no mention is made in the topic....

GuzXT said:
This firmware is for XT1929-4 and no mention is made in the topic....
Click to expand...
Click to collapse
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.

there is this https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
we just have to wait for OTA i guess
also there is this if you google beckham_opw28.70-25_subsidy-default_regulatory-default_cfc.xml.zip but they ask for money
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=19944
search for 1929- on https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2634

Here in free access all the same))
https://mirrors.lolinet.com/firmware/moto/beckham/official/

Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.

driverdis said:
Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.
Click to expand...
Click to collapse
magic works quite well if you patch the boot normally, with check marks.

Willy33 said:
magic works quite well if you patch the boot normally, with check marks.
Click to expand...
Click to collapse
Thanks, this did the trick. I was able to download use the boot.img from the lollinet mirror firmware zip. It does require both force encrypt and verity enabled before patching it or it will boot loop.

---REDACTED---

Will this work on the Moto Z3 (XT1929-17)?

wanb1i said:
Will this work on the Moto Z3 (XT1929-17)?
Click to expand...
Click to collapse
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device

darkdaemon32 said:
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device
Click to expand...
Click to collapse
Found the original vzw firmware on Moto's site.
Thanks!

twelfth said:
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.
Click to expand...
Click to collapse
So I have a Verizon Moto Z3 (Brand New XT1929-17, NO XDA Thread yet) I found the firmware off the Motorola site at this link https://androidfilehost.com/?w=files&flid=279604 (last file). I unzipped it, copied the boot.img to my adb folder and executed fastboot boot boot.img and this is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.622s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
My goal here is to modify a boot.img so I can root with Magisk without unlocking the bootloader. (Verizon devices don't allow unlocking the bootloader)
Any help would be appreciated.

wanb1i said:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
Your bootloader is locked. Being a Verizon device, it's likely not unlockable.
You have to have an unlocked bootloader before you can boot and flash in fastboot.
This is why people buy unlocked devices.

Xt-1929-4 opw 20.70-31
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Android FileHost[https ://drive.google. com/open?id=1KAMijX1W2HQx69mDhZ294tp51vtAoo0E[/URL]

Can someone provide a system dump for Moto Z3 Play..
Edit: Done

Hi, my Z3 play has a Bootloop I tried with hard reset and still not working. It's XT1929-6 dual SIM, can someone help me ? Please

[GUIDE] SIMPLE STOCK FLASH AND DOWNGRADE MOTO G6 ALI

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JOIN MOTO G6 GLOBAL GROUP ON TELEGRAM
https://t.me/Moto_G6 ​
Be sure backup yout own files phone will be erased.
Downgrade can be cause lose ril and IMEI be 0
To recover Empty IMEI and signal read this thread:
(1) [GUIDE] IMEI RECOVERY STOCK & CUSTOM ROM | XDA Developers Forums (xda-developers.com)
> If you don't have download and install drivers and ADB:
Motorola Drivers: https://support.motorola.com/us/en/drivers
ADB WINDOWS https://dl.google.com/android/repository/platform-tools-latest-windows.zip
ADB MAC https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
ADB LINUX https://dl.google.com/android/repository/platform-tools-latest-linux.zip
Download the stock ROM of your own area like RETAIL RETEU RETIN RETAR, from lolinet source and extract and please, don't download from another site or it won't work.
These two ROM work in the most of cases.
RETAIL 9.0 Pie
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RETEU 9.0 Pie
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Lolinet Official Motorola Ali Source
https://mirrors.lolinet.com/firmware/moto/ali/official/
1. Now start terminal/pront on ADB folder.
2. Extract files from stock rom.
3. Copy files inside ADB mixing.
4. In terminal copy and paste line per line.
4.5. You can copy code in a txt file and make a bat file too.
5. Just wait phone turn ON alone, first boot leave around 10 minutes
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

Do not downgrade firmware with a locked bootloader, it may make the device unusable.
These commands need to be changed from time to time.
If you want to know the correct flashing command open the servicefile.xml
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com

sd_shadow said:
Do not downgrade firmware with a locked bootloader, it may make the device unusable.
These commands need to be changed from time to time.
If you want to know the correct flashing command open the servicefile.xml
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Click to expand...
Click to collapse
This is the order what work on moto G6 ali guy, we use these too much times on telegram group and works fine, and with lockedboot loader only can be loose ril, justing flashing non--los again you recover it.

brunogroa said:
This is the order what work on moto G6 ali guy, we use these too much times on telegram group and works fine, and with lockedboot loader only can be loose ril, justing flashing non--los again you recover it.
Click to expand...
Click to collapse
Ok but your original post doesn't warn about that, nor how to fix it.

sd_shadow said:
Ok but your original post doesn't warn about that, nor how to fix it.
Click to expand...
Click to collapse
sure, thx i'll put it on XD is my first time posting, and i read a lot of others to make this better, thx guy

I successfully flashed my RETLA Moto G6 but im getting a security patch update notification from 2019 which is obviosuly older than the Stock ROM I flashed. If I try to install this update the update will fail and the phone start again normally. Is there any way to solve this and let the phone "know" the latest version is installed so that I dont get this notification anymore? thanks

how do i downgrade back to android version 8 and relock the bootloader there?

smartasiankid said:
how do i downgrade back to android version 8 and relock the bootloader there?
Click to expand...
Click to collapse
You shouldn't downgrade then lock the bootloader.
You may brick it, if you manage to do it correctly, it will just try to reupdate.

sd_shadow said:
You shouldn't downgrade then lock the bootloader.
You may brick it, if you manage to do it correctly, it will just try to reupdate.
Click to expand...
Click to collapse
oh ok thanks for the warning.

Question need a little information

Moto G stylus 5G Denver build I had TWRP installed and majisk installed I wanted to install a ROM during insallaion i was having issues and needed 2 set my device down for a few minutes and take care of like regular life problems. Anyways my kid get ahold of my phone and did god-knows-what but he had enough time to wipe everything but my external USB drive. i have the full stock file i downloaded to pach wih magisk i have the twrp file as well.i had my backup on my sd card which was erased. so my question is his, where do i go from here? how do i use files in the picture recover back to I guess a stock
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
. Version of Android
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome

tommy2tones1990 said:
also doing all his thru bugjager and im sure more then one guide explaining what to do but i need o be at work in 2 hours and so alink in thr right direction would be awesome
Click to expand...
Click to collapse
In my opinion I would just restore back to stock. Basically, using bugjager, make sure you have the stock rom downloaded and unzipped. Now you'll want to probably copy and paste these commands but you'll reboot your Stylus 5G into fastboot mode and once its connected to the second device with bugjager on it, start going down the list of flashing the partitions back... Here are commands you can copy and paste:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear

I basically spent a hour trying random things on bugjaegar I honestly have no ideal how I didn't brick this phone seriously but then I flashed vbmeta boot and vendor boot and restarted. It took a long time to start then a msg popped up for half a second and the phone rebooted and then I went thru the whole Google startup process and when I got there I rebooted back to bootloader and flashed the magisk patched img and so far everything seems to work
.. thanks for your help.. I'll probably go ahead and wipe everything and start over using your guide. Then go get everything back to how I had it before and and make multiple backups on at least 2 different micro sds then retry the to install ROM

No worries Just saw your post and figured I'd offer some help.. I personally love the bugjaeger app. I use it all the time... it definitely helps if I'm without a computer and got my tablet lol.. and my handy dandy USB-C to USB-C cable lol...