Database Develop

[Q] Newbie to Moto X/ Android - 4.4.2 issues

Hi All,
I'm lost, so hope you chaps can help.
Have just purchased a Verizon Moto X developer phone X1060 - its from the USA, I'm in Hong Kong and obviously not using a Verizone sim card - further, I'm a iMac user, so Android is new to say the least to me.
My MX is already "rooted" so want to upgrade to latest 4.4.2, obviously I have to do this via boot loader - big difficulties encountered having download all necessary files and cannot "hard" reboot as getting Andy with Red Triangle - I take it some issue with fast boot or whatever, but after 12 hours effort, absolutely stuck and getting annoyed.
So, time to hit boards and get expert advice me thinks?

I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515

Many thanks, but
djlucask said:
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!

editor1 said:
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
Click to expand...
Click to collapse
Oh i forgot the iMac issue, I never saw tutorials for OSX, maybe the best choice here is to make an Windows VM, or an Linux, that way would be always easy to mod your phone.
Sorry I don't have any other possible solutions for this

Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.

jasoraso said:
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
Click to expand...
Click to collapse
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.

Republic Wireless Moto X Moto G Discount Code Link URL
$25 Republic Wireless credit at checkout with purchase of your phone using this discount link

editor1 said:
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Click to expand...
Click to collapse
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2

imparables said:
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.

Now upgraded to 4.4.2
editor1 said:
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Click to expand...
Click to collapse
Thanks for the input, after two days of hell, I'm now fully upgraded to KitKat 4.4.2, my Moto X1060 Dev phone is working as it should be, I've unlocked it, am able to do side-loading, have TWRP installed - a bigger pain as caused a continually boot loop, erased, re-installed all from Moto and re-cracked it.
So it works, and I did all this on a iMac and in terminal, which I don't often use!
Not bad for someone fast approaching 50 - and yes, this is a kids game I'm afraid to say.

Can't Sideload March OTA Security Patch in NRT

I did Search and Did not find a solution.
Locked Bootloader (NRT says it can sideload OTAs with a locked Bootloader)
In NRT I selected Advanced Utilities
in Advanced Utilities I select Sideload Update
Clicked OK on First Screen
Browse to my downloaded OTA file
Click NO I am not unlocked
Get The Android With Exclamation Point Screen
Below it is the Text "No command"
NRT Tells me to Power Volume Up (obvious error I power Volume up and down).
It tells me I should Have an option to "apply update from ADB", but it doesn't exist as an option (i just get the normal Bootloader options and nothing more)
What Am I missing?
EDIT:
The Problem was I was Holding Down Power and Volume UP at the same time and not letting go and that was the problem, when that didn't work I assumed it was a mistake in the documentation.
I needed to just push power then while holding quickly press Volume Up
Windows 10 Pro

I started to write a brief script, but without knowing how much you know it's pointless.
As a first step I suggest that you invest time in reading instead of using toolkits (though I'm a big fan of NRT myself). Start with learning to flash a recovery - TWRP is popular and easy to use, and it has a big button titled "Sideload" for when you're ready to try the OTA.
Or you could try this:
https://www.youtube.com/watch?v=5Fl3Vg0ALYw
But NOT using the toolkit...

Ive done tons of rooting and flashing but always on an rooted phone with unlocked bootloader. This time I actually reverted back to stock to get back to 7.1.1 and Was hoping to stay OEM Locked and unrooted for a change.
Unfortunately I have the Horrible Speakerphone issue and since clicking on Check for Update does not find the March Patch I thought id try to sideloaded it.
I imagine the patch is probably a slow roll-out??
So i guess NRT cannot flash an OTA to stock as advertised.

I think the general attitude here (forgive me if I've misread, people) is that there's no point in playing with a Nexus if you just want to keep it stock...
The whole point of owning a Nexus is the flexibility to play without too much risk, since with an unlocked bootloader and TWRP you can usually recover from any mishap.
"Check for update" has never worked for me on any Nexus. It always waits until I'm looking the other way and then sneakily downloads it. I got tired of that and just started to flash the factory images when they appeared, and since Google started making the OTAs available for sideload there's really no reason not to use them.
The latest N6F26U OTA has fixed the speakerphone, and Google have somehow backed out the Android Pay problem it introduced, so personally I'd go back to rooting and flashing rather than waiting on Google's whims.
And don't rely on NRT, excellent though it is...

dahawthorne said:
I think the general attitude here (forgive me if I've misread, people) is that there's no point in playing with a Nexus if you just want to keep it stock...
The whole point of owning a Nexus is the flexibility to play without too much risk, since with an unlocked bootloader and TWRP you can usually recover from any mishap.
"Check for update" has never worked for me on any Nexus. It always waits until I'm looking the other way and then sneakily downloads it. I got tired of that and just started to flash the factory images when they appeared, and since Google started making the OTAs available for sideload there's really no reason not to use them.
The latest N6F26U OTA has fixed the speakerphone, and Google have somehow backed out the Android Pay problem it introduced, so personally I'd go back to rooting and flashing rather than waiting on Google's whims.
And don't rely on NRT, excellent though it is...
Click to expand...
Click to collapse
The Problem was I was Holding Down Power and Volume UP at the same time and not letting go and that was the problem, when that didn't work I assumed it was a mistake in the documentation.
I needed to just push power then while holding quickly press Volume Up

So have you managed the sideload then?

YES and it fixed the Speakerphone
dahawthorne said:
So have you managed the sideload then?
Click to expand...
Click to collapse
YES and it fixed the Speakerphone

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!

I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?

Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.

cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done

Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution

cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644

Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...

Locked bootloader after installing Magisk / boot problem, can't boot and can't unlock

Hey everyone!
First posting here, long time reader. So, I just f***** up big time. I tried to install the YT Vanced modules for my X4, realized I had to get rid of the stock YT app first, installed Terminal Debloater and at that point my device stuck during boot. To make things infinitely worse, I then proceeded to re-lock the bootloader cycling through the last commands issued. That was dumb, yeah.
Now I get the "device corrupt" message when I try to boot normally and fastboot won't let me flash again saying I need to enable USB debugging, which I can't because the system won't let me boot.
I have a severe feeling I'm screwed with nobody but myself to blame, but I'm also aware of the godlike knowledge in these boards so... can anyone point me in a direction here? Damn I like that phone and have zero funds for a new one right now :/
I can still get into the Power+Down menu, the stock recovery gets me nowhere though. Oh, and it's the Euro Model, Motorola Moto X4 XT1900-05, running the Oreo OTA update.
Cheers people,
grslbr

You need to flash the original official firmware that came loaded on your device but good luck trying to find a copy of that. With the bootloader locked, you're screwed.

Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/

FI stock roms seem to be located at https://firmware.center/firmware/Motorola/Moto X4/Stock/ Have not tried them myself and not sure you can flash with a locked bootloader.

You should be able to flash a stock ROM pretty easily. From what I've seen, you should be able to install any retail stock rom without unlocking the bootloader.

grslbr said:
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
Click to expand...
Click to collapse
Hold Vol+ and Power buttons. Phone will try to reboot several times and then boot normaly. Go to developer options and tick allow factory unlock and USB debugging. Then you just unlock bootloader as usual.
This procedure helped fix the same issue with my xt1900-7 reteu.

Lost system on A partition, how to get back?

Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?

Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,

V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it

xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.

I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,

Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.

V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)

Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.

Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?

How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.

Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.

V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones

@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.

For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.

@Chr1stOnABike just checking in to see if you were able to get your problem resolved?