Database Develop

deploy xap issues

hey guys, ive a lumia 625 and ive developer unlocked it, ive been searching the web all day on how to deploy xaps, ive been to site after site and they all reccomend different apps to do this, i've literally tried them all and i keep coming to one of 2 problems.
1- i cannot target/choose my fone to deploy too
2- i get a microsoft error (this only happens wif the offical deployer from the sdk.
just wondering if anyone has come accross this issue before and if there is a way to make any of the apps reconginse my phone?

Could you be a little more vague about that error? I mean, you told us it pertained in some way to the company that made the software. That's clearly way too much info... </snark>
If you were able to dev-unlock your phone (presumably using the Developer Registration tool from the SDK), you are able to deploy apps (using the Application Deployment tool from the SDK). They connect the same way. If you get some error when doing so, tell us what the error is. Also, try obvious and simple fixes like restarting the PC and/or phone, making sure the phone is connected correctly (i.e. you can browse it via MTP, it's charging, etc.)

{
"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"
}
yeah my phone is developer unlocked, above is the error i get from the Application Deployer from the SDK instalation, and yes i can still browse my files and charge my phone, its just this error happens when i opened the program.
above is 2 images in one, the first is the error i get when opening xap deployer 2.0, the 2nd half with the black circle shows there is no target avaiable.

Have you tried rebooting both systems? The other things you might try are removing the WP8 drivers (which may also require a reboot before they work again) from Device Manager, and using a different USB port.

GoodDayToDie said:
Have you tried rebooting both systems? The other things you might try are removing the WP8 drivers (which may also require a reboot before they work again) from Device Manager, and using a different USB port.
Click to expand...
Click to collapse
i have rebooted both systems, i haven't tried removing drivers or a different port, I'll try those tomorrow and hopefully one will work

Good luck. This is an error I haven't seen before. You may also want to search around more online in case anybody else knows anything. The only times I've seen comparable problems, the phone wasn't really connecting at all (not visible to the registration tool or MTP clients).

Thanks.
tbh id an issue wif one usb port not reading my fone, but the one I've been using since i got the fone installed has always worked for copying files and stuff.

hey ive tried what youve suggested but im still getting the same errors, is there another app you know of that may work? ive searched the web and the only other person who seems to have come accross this error said he updated his visual studio to update 3, i just downloaded the most up to date version of visual studio yesterday so i dont think it would be that?

All the apps work the same way, they just wrap the same functionality of the official app in a more user-friendly package (the official tool is pretty bare-bones). Some of them have better error handling (telling you useful information) than others, but if they just do not *work* then you're probably SOL... is there another computer you can try using, to see if it's a problem with the phone instead of the SDK tools? Also, are you sure you purged all the phone drivers? Un-installing the SDK and purging all the drivers, then rebooting the PC and starting from scratch, *might* work. It'll take time but I don't know what else to recommend right now except trying on another PC or trying with another phone.

I did a fresh install if windows 8 and that's sorted the problem, not sure wat was wrong, but thanks for the help guys.

Syraphin said:
hey guys, ive a lumia 625 and ive developer unlocked it, ive been searching the web all day on how to deploy xaps, ive been to site after site and they all reccomend different apps to do this, i've literally tried them all and i keep coming to one of 2 problems.
1- i cannot target/choose my fone to deploy too
2- i get a microsoft error (this only happens wif the offical deployer from the sdk.
just wondering if anyone has come accross this issue before and if there is a way to make any of the apps reconginse my phone?
Click to expand...
Click to collapse
I am facing the same don't know y help pls!!

kk18 said:
I am facing the same don't know y help pls!!
Click to expand...
Click to collapse
hey, are u trying the trick for 32 bit? That's wat didn't work for me, i had to reformat to 64 bit and then id no problems.

]
same error I get

kk18 said:
]
same error I get
Click to expand...
Click to collapse
I have gotten this error when installing the WP8 SDK on Windows 7 64 bit. Try applying any WP SDK updates starting with 7.1.1. I think the 7.8 update is the one that fixed it for me...

I have a wp8 and windows 8 64bit and I have tried several ways I don't get the target option in deployer!!pls help!!!

I had that same problem multiple times, always when the internet connectino went offline and the installer couldn't finish. I had to completely uninstall the SDK and install it again, you have to let it download the emulator images aswell. Good luck!

Brick Fix?

Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!

pleckers87 said:
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
Click to expand...
Click to collapse
Tell details. What's your phone model?
Do you have download mode?
What's the error you getting?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app

Model is D950. Originally had 4.4.x. I can enter download mode no problem. I don't have adb commands. When I type adb devices, it shows a blank space.
LG flash tools gives me a "device model different. Check device model". Mind you, tried flashing the stock TOT with the d950dll and also tried the generic dll that G2 users were using. I'll post a pic in a little bit of the error I get....

{
"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"
}
[/URL][/IMG]

[/URL][/IMG]

pleckers87 said:
[/URL][/IMG]
Click to expand...
Click to collapse
Lols..
How did you bricked your set? I am just curious to find out..
What on screen If You normal start?
Try to connect your Phone with PC in normal mode.
Whats the Windows version?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app

Alright, here goes...
Started when the volume buttons stopped registering pushes. I replaced the clickers (for lack of better term) but problem did not go away. I then attempted a backup restore via TWRP but Flex powered down (battery level was above 90% prior to restore). I then connected to computer (then running W8) and it showed up as qual_blahblah. I d/l factory partitions and followed a guide to fix partitions...well the guide did not work out in my favor because after reboot, device would show LG splash, go black and show LG splash again, followed by an android guy on his back with the yellow triangle above him. I will note that that is the only thing (android guy on back) I see when I try a normal boot up/power on.
I am running W10 on my PC currently.

First of all why did you try to restore your partitions if you had twrp and a saved backup. That should have solved any issue there. The volume buttons going bad wouldn't have been a software thing unless you used some mod that could have disabled them. Then that can be fixed via factory reset. Or restore backup.
OK so to fix your FLEX just plug it up in download mode and to your PC with lg's PC suite software installed on your PC. Not sure if windows 10 is supported for PC suite or not or if this works on win 10. May have to try someone else's pc. And make sure you have internet service on that PC.
At the top of the PC suite program window there are several options to choose from. Not sure off the top of my head what they're called but there is an option some where up there to restore from bad update or recover from bad update. Something like that. I wrote a tutorial about a year ago on how to do this. It should be in the general section. Try that out.
Back to the volume buttons or clickers as you call them. The ones that you replaced them with may be defective. If you bought some cheap Chinese BS then it could possibly be for be made as more of a universal off brand made to work in a lot of lg's but for some reason not compatible with the FLEX. I've bought a new sim card /sd card ribbon for an asus zenfone 2 before that was that very issue. Speaking from experience.....spend the extra dough and get the quality parts not Chinese sweat shop BS.
And good luck

[Unlock.io] Not able to receive OTA-Updates after Sim-Unlock

Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
{
"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"
}
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)

Here a Picture of the Device with the Error Message and Software Version

What version of phone do you have 973U? What carrier do you have?

highaltitude said:
What version of phone do you have 973U? What carrier do you have?
Click to expand...
Click to collapse
G973F
A1 Austria

Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
There's another similar post that you may find helpful.also might be try asking unlock io and see what they say. Let us know.
https://www.reddit.com/r/galaxys10/...date/?utm_medium=android_app&utm_source=share
Sent from my SM-G975U using Tapatalk

Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .

i already tried a hard reset, did not solve the problem.
i will try smart switch and let you know

Rexton270 said:
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .
Click to expand...
Click to collapse
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch

Proxolin said:
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch
Click to expand...
Click to collapse
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...

Rexton270 said:
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...
Click to expand...
Click to collapse
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.

AHE_XDA said:
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.
Click to expand...
Click to collapse
thank you for that explanation.
i will first try to update the phone with smart switch as soon as there is a newer version for my phone, atm it says im up to date (i hope that is true) maybe it solves itself when i start an update with smart switch, if not i will follow your steps
thank you very much.

because there was still no update in samsung smart switch i flashed it with odin.
problem solved.
thank you.
for other users: if you want to unlock your phone, use the samsung database instead of the cheaper version.....

Excellent news. Glad to hear it all worked out.

Pixel 4xl bricked itself

Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.

You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.

So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.

sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.

Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"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"
}

You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.

#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com

#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .

My phone is FUBAR'D

Wrote this message to Google support. I don't suspect I'll hear anything from anybody but I'll post here for my fellow Pixel brothers and sisters that perhaps may experience something similar. I'm disappointed. I know the phone is relatively inexpensive (cheap) and you get what you pay for (?) but this points to bad hardware, simple and plain. How does my 2019 LG G7 on android 9 (!!??) outlast a 4a5g?? I expected more but, alas it is what it is. Peace out, Pixel 4a5g.
"Over my time since I've been on Google Fi I've used and bought a few devices. I started out with a Pixel 4a, then upgraded to the 4a5g and now I'm on the 6 Pro. I love Google phones and have always been a fan since days of the Nexus devices. I was disappointed when my 4a5g started bootlooping 2 months ago. It has never been unlocked or have I attempted to flash ROMs on it. It would eventually stop and boot back up, last for a week or so then bootloop again. This time around it continued for a longer period of time. When I went to try to do a factory reset it is stuck in Fastboot saying "no valid slot to boot." Based on the research on this issue I realize the phone is pretty much dead, even though I can use Google's own Flash tool to flash factory images for it. The phone is no longer under warranty and your support doesn't give any other options than paying for repair upt to $350, which is beyond the worth of the device. I am disappointed that the phone bootlooped to the point of death after only owning the device for LESS THAN 2 YEARS. (Nov 2020). My previous device, a LG G7 that I previously had on Verizon lasted longer, and my dad still uses that phone to this day. I purchased that phone in March of 2019. I know this post will only fall on deaf ears and no one can do anything about it but for the first time in a long time I'm disappointed by a Google phone."
{
"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"
}

Why not reflash since those ROMs are easily available? You have access fastboot, no?

Kaynejulian said:
Why not reflash since those ROMs are easily available? You have access fastboot, no?
Click to expand...
Click to collapse
I've been flashing and re-flashing this phone for 2 days.

What's the output? What is error code? What commands are you using? What does fastboot getvar all show?

I'm using the android flash site to flash the phone with a stock image from Google. It goes through the process with no errors, then it acts like it's going to boot, bootloops twice then goes to the pictured fastboot mode showing "no valid slot to boot." Fastboot shows the build number (android 11 or 12 depending on which I've flashed) but when i try to wipe data i get /system/bin/tune2fs is missing.

I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org

Thordim said:
I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org
Click to expand...
Click to collapse
Thanks for trying, I get file format is not recognized error message. I tried manually installing the Pixel Experience ROM and even got that ROM's recovery to flash, and flashed the ROM, all went well exactly as the website said but then it said that the phone is corrupted and bootlooped. Flashed the stock 12.1 image using the Android Flash Tool, back to above error message after 2 bootloops.

Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.

smokejumper76 said:
Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.
Click to expand...
Click to collapse
What confuses me is that even when I manually flash a custom ROM or stock image it goes through the process just fine, no error messages. It boots up, does the little G circle animation and right as it's about to go to the next screen.. bam, it reboots. Does it a second time, then immediately goes to the above-mentioned screen shot. So I think somewhere the hardware or storage drive or whatever you want to call it is broken. I wonder if I triggered it when I tried to enter fastboot during one of the times I tried to factory reset it. I dunno... I'm attempted to let the battery die then recharge and try again or something.
It's ok, I'm sort of over it.. my feelings are hurt at this point. I've been Rooting and Romming since the days of Moto Droid X2, Galaxy Note 2 (before vzw locked their bootloader) and the Nexus 6, so when I got into the Pixel phones I was relieved when I didn't feel like I didn't have to do all of that just to get the phone to feeling like it's working smoothly. I have a 4a that has a broken screen, this one and a 6 Pro (factory), so I've really liked the Google Pixel devices and the software experience. So for this to start bootlooping even without me tinkering with it for over a year is just a disappointment.

If anyone can understand it, here are screenshots of the recover.log file from the recovery screen.

Tried flashing the first Android 11 OTA image from the Google Images site, A4 October 2020 as it's a unlocked Google purchased phone. I noticed it goes through the motions but says status 0 then further that system/bin/tune2fs is missing so nothing is being written. This must be happening every time I try to flash but I'm not actually seeing that nothing's happening on the Google flash website.

Have you already tried the Android Flash Tool? Given the circumstances I would recommend checking the Force flash all partitions box.

yeah, that was the first thing i did, tried 11, 12, 13 beta, 13 official... nothing. Lineage too.