yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5a] simplepinoi177:
That's why I suggested uBreakiFix if it's in the area and/or maybe ship it to them if need be; unless that's whom he spoke to -- but, again, like your opinion, I don't understand why they wouldn't with that reasoning so maybe he can try a different uBreakiFix shop...
[Google Pixel 5a] niscy:
Just for context, I mentioned earlier that the device would freeze and go blank randomly before it bricked ... this happened quite often, and after rebooting I typically noticed that some data was missing (e.g., the most recent messages in IM conversations). I assume that the last time it froze, some chunk of the boot image got corrupted.

The official Google repair shops won't do mobo replacements for out of warranty devices, apparently ... company policy. So would have to find some mom & pop shop. BTW, they confirmed that the data would be lost.

@V0latyle think that didn't work:

% fastboot --set-active=a

Setting current slot to 'a' FAILED (remote: 'error getting device locked state Not Ready')

fastboot: error: Command failed
[Google Pixel 5a] simplepinoi177:
I still might call and actually talk to some various, random uBreakiFix to see if they might not necessarily follow the "company policy"....but then, again, thinking about it, I don't know how they would order the proper parts without following it; maybe they find ways....

That, or order another 5a from Swappa for parts and see if they would perform it if you brought the replacement part/own hardware...
[Google Pixel 5a] niscy:
To be honest, I was most worried about the user data ... given that I'm going to lose the data anyway, I think I'll just disassemble the hardware (and probably destroy it in the process) to learn more about how modern phones are built, lol.
[Google Pixel 5a] fjm568:
I hate to jump in on someone elses post, but I'm kind of having the same problems.

First off, Pixel 5a 5G, stock, and locked bootloader bought carrier unlocked through Google.

Still on Android 11(because it worked fine for me until now, lol)

I restarted my phone one night this past week while it was charging, and when it rebooted, it got stuck on the G logo screen. I could get it to restart by holding the power button, but it still got stuck on the G logo screen. By using the power + vol down, I can get it to the fastboot screen. I can also cycle through and go into recovery and rescue screens.

I have tried to use the pixelrepair.withgoogle .com (no space) to check for updates and do its thing. Hooked up and was able to run it through the process and complete it (according to the website) successfully, But when it reboots, it still gets stuck on the G logo screen. I've tried it several times, same outcome.

Next thing I've tried is to sideload a slightly newer version of Android 11 using ADB, it gets through verifying update package and installing update...step 1 and step 2 and on the phone screen it ends with "Install from ADB completed with status 0." On the computer command prompt screen it gets to ~94% and has "adb: failed to read command: No error" and a new command prompt line. When I restart the phone, like before, it gets stuck on the G logo screen.

I've also tried to sideload the latest Android 13 ota, same results.

When I go into the Recovery screen, it is still showing my original version of Android 11.

Even though I've been poking around with rooting phones ever since the OG HTC Incredible, I don't know much about the technical stuff you guys know about when doing this kind of stuff. As long as someone gives a step-by-step guide on how to do this, I'm kind of lost. Except for 2 app backup files(not games), a wipe wouldn't bother me much, but I'm hoping to be able to save this.

I really like this phone, but if only phones still had a removable sd card, I wouldn't be so mad right now. This is also the first phone that I didn't unlock my bootloader, which probably will end up biting me. From what I've read over the years, I would have more options to fix my problems right now.

One other thing, and I don't know if it means anything, but every time I've checked the fastboot screen, it always shows boot slot: a

Thanks for any help or ideas any of you can give on my situation.

Jim
[Google Pixel 5a] fjm568:
So...am I screwed, or do I have any more options before I try a factory reset or warranty repair? I would like to hopefully save some data, if possible.

Thanks for any help or suggestions.
[Google Pixel 5a] fjm568:
Well...this is a first.

Been a member of this site for almost ten yrs. I don't make many posts, but I wasn't expecting to not get at least a reply to a question. At least to say, "yup, you're screwed" or "maybe try this", or to at least ask for more info on the problem.

I'm pretty sure my phone isn't bricked, but I don't have the technical knowledge to be able to know if my only option now is to try to factory reset. I don't want to try that yet, because I would like to make sure that I haven't exhausted all my options to try to recover some data, but I definitely need some help here. At least for someone other than Google whose answer to everything is a factory reset, even when there might be another way.

Thanks.
[Google Pixel 5a] niscy:
The other 2 guys here clearly know much more about this than I do, so I won't be of much help.

My only (not very helpful comment) is that yes, backups are critical. I kept pushing it out because I thought I couldn't find a satisfying backup solution.

Luckily, I was at least very aware of the lingering, unavoidable risk. Thus, I kept only very little data stored on the device, but regularly uploaded important stuff to encrypted cloud storage (basically a poor man's backup).

However, properly setting the phone up again with all your apps and settings can easily take a day, so I want to avoid that pain going forward.

Good luck, hope someone else can help you.
[Google Pixel 5a] fjm568:
Bueller? Bueller?

Wonder if someone will answer before the 7a's get released?
[Google Pixel 5a] sampathjanitha:
No one has an answer for bricked 5a's bro. 😟
[Google Pixel 5a] simplepinoi177:
Unfotunately, an "a" phone from two versions ago with a locked bootloader doesn't have many options. You've already done what we would give for as advice; trying to sideload an OTA. Supposedly with the Pixels & A/B slotted devices, the second slot is supposed to be a fallback for when updates crap things up; so I suggest maybe changing the active slot, but so far it's never worked with anyone I've seen it suggested in dire circumstances -- I'm not even sure it's possible on a locked bootloader, but maybe.

I might've suggested that you try and unlock the bootloader through a fastboot command, but that would entail you unticking "OEM unlock" in Developers Mode prior to the bootloop.

I am also curious as to why it states when you attempt to sideload the OTA why it states" failed to read command: no error". Maybe you are loading a bad OTA.zip? Try redownloading it from the Google Developers Factory Images page and make sure to compare the checksums to confirm it is a full and complete copy of the image file/zip...

Sorry we haven't been able to help much, but you seem to have exhausted most of the options/suggestions you would nominally get; as well as this being a device that not many of the experts have or worked on...
[Google Pixel 5a] fjm568:
Thank you for the response. Really appreciate it.

So...at the command prompt, I would type this in...

fastboot --set-active=b

And then see what happens? Since I'm showing slot -a as being active currently? I'm assuming I would need to try and reboot if the command is successful, or would it do it on its own? Or if it's successful, will it just give me another command prompt and do I try to sideload the OTA again?

Again, I'm a noob at all this, so if I don't have it right, please tell me.

I would think most Pixels would take the same troubleshooting commands/instructions for similar problems.

Thank you very much.
[Google Pixel 5a] fjm568:
Here are pics of my laptop screen and the phone screen when I tried to sideload the OTA. Tried it on a newer laptop as well, same results. Gets to 94%, and then goes to command prompt with the same message there and on the phone.

These are from the attempts earlier this week. I will have to try the set active slot command later this evening when I get home.
[Google Pixel 5a] simplepinoi177:
Sorry, I haven't been able to get on a computer yesterday and today...

for setting the active slot, I believe that should/would work; I believe there's another variation where you can just put "other" somewhere in the syntax, but I'm too lazy to go find it. In any case, I saw on your previous posts that you figured out and confirmed you were on slot_a, so manually changing it to slot_b should work out the same. Remember, the few times I've seen it suggested here for this type of problem, I've never once seen it work, but supposedly it's there to help as a fallback when an OTA breaks something, so in theory it might/should help when one would seek similar goals...

If I recall correctly, I believe you're supposed to load up and sideload the OTA in Recovery Mode. I've only done it once myself back on the Pixel 2/Android Pie, so it's been a long while and/or it might be different now; but IIRC, you go into Recovery Mode and there should be a selection along the lines of "update OTA via zip" or something (again, rather lazy to check it exactly), and that's when you run the adb command -- or I know that other recoveries and/or Android Recovery Mode enables adb commands once you're in the mode, so maybe running the command just like that will work (again, sorry for being too lazy to check and confirm). I had initially thought you were updating via OTA this way to begin with and not from Bootloader/Fastboot Mode...that's why I was rather confused as to the error code you were receiving. It just occured to me that you had posted the cmd output with the output on the device -- meaning you were already doing it from Recovery Mode. Also, again, it would be good to confirm the checksum, just in case that's why it was failing initially at 94%...

The only other advice I can think of is that some of these random issues of flashing not working happens when the platform-tools is not the most up-to-date; make sure you are running the most up-to-date one from the Google Developers website

AND NOT

one that is a "minimal-adb & fastboot (platform tools)" or a platform-tools package of some kind....

You haven't updated since yesterday morning, so I'm hoping you got it working and worked out, but it's understandable if not because these are rather long shots....hope it all works out! Good luck!
[Google Pixel 5a] fjm568:
I tried earlier today to change slots. It wouldn't let me because of the locked bootloader. I did notice something while trying different things...I'm going to try something that I haven't seen anybody mention, but I don't think anybody had done what I tried when I noticed it. Kind of cryptic, eh!? Ha! Can't hurt it more than it already is. I couldn't do it earlier because I didn't have internet access, but now that I'm home, I will try it out and report back within the next hour or two. Hopefully it'll do something.

Thanks for looking in, and check back when you can to see if I was successful. I'll explain what I'm going to try in my later post.

I appreciate your suggestions so far.
[Google Pixel 5a] fjm568:
Ok...update...

I won't go into too much detail as to how I did what I did since it didn't really work completely and the outcome was a failure.

I did manage to get the slot changed to b, but in the process, managed to make it so that I was unable to sideload any OTA's past 47% after that and it failed installing. I could still boot into the fastboot page, recovery page, rescue page, etc...and scroll through the menus and select lines, but it just wouldn't let me sideload OTA's anymore.

So, in the end, I went ahead and tried the wipe data/factory reset option, and it succeeded, and I was able to reboot and it started the new setup steps.

Now, I don't really understand why I couldn't get past 94% on my earlier sideloads and be able to boot normally, but by doing a sideload of a slightly newer build than my original(still Android 11) and getting it to switch slots to b, and then trying to sideload an even newer build, it wouldn't go past 47%. After that, I was stuck. Every time I rebooted and went into the boot screen, it now showed that I was in slot b and on the recovery screen, it showed my newer sideloaded version, but it never booted past the G logo when I restarted it. So, I just finally said, screw it, and tried a factory reset/wipe to see if that would work, because if that didn't, I was going to try and see about getting a warranty repair done to it. My warranty actually was up on Jan 23, 2023, but I had called Google on the 19th, to go through some troubleshooting steps with them, and to get it on record that I was having problems. Hoping that if I wasn't able to fix it before the 23rd, that I could still possibly have it warranteed soon after.

I haven't finished doing the setup steps on it yet, but I damn sure am going to unlock the bootloader this time.

Thanks again for your suggestions and taking the time to read through this. I appreciate it.

Jim
[Google Pixel 5a] fjm568:
Last update, after doing a factory reset, I sideloaded the very latest Android 13. I tested it out for a couple of days before I finally did a copy from my old phone to my new phone and swapped in my SIM card and did some final minor setup tweaks.

So far now, after a couple days of normal, every day usage, the same as before the bootloop, I haven't had any issues pop up...yet. So, apparently, my issue wasn't hardware related(or it hasn't reared its ugly head yet), but a software hiccup.

Thanks to those who've responded.
[Google Pixel 5a] drtweakllc:
Jim, like you I don't want to hijack this thread but I'm having a very similar issue as you. I have GrapheneOS on my phone but can't boot, I can only get to fastboot, recovery etc. I can sideload an OTA update which I have done but my phone boots to Graphene and when I try and log in it restarts. I haven't gotten really any help from GrapheneOS's own forum so I figured I would ask here since I usually get great help here. My question is how did you switch your phone to boot from slot b, what adb command did you use? Thank you
[Google Pixel 5a] fjm568:
Are you saying you tried to sideload a factory OTA? I don't think you can do that with a custom OS and bootloader. Hopefully, someone will correct me if I'm wrong, but I think you would need to factory reset back to stock OS and bootloader, and then follow the steps to get your custom OS back on, but that will wipe your phone. Unless you try to sideload the latest custom OS(without doing a factory reset), which should be doable, which I don't think will wipe it.

There is an adb command switch slots. I don't recall what it is, but since your bootloader is unlocked, you should be able to use the command to do it. My bootloader was locked, so the way I did it probably isn't a good way to do it. I didn't have a choice. I could've bricked my phone worse. It didn't help me at all. Since I was stock/unrooted/locked at the time, I was very limited in what I could do. In the end, I factory reset, sideloaded the latest 13, unlocked and have actually taken the latest OTA with no issues.

Since you are running a custom OS, you should be able to do more than what I was able to do. You have more options since I wasn't unlocked.

I believe if you look into like the Pixel 5(or any of the latest Pixels that are more popular than the A series for modding) groups and search for the adb command to switch slots, something should come up, or just search for that adb command in general.

The way I understand it, when you sideload an OTA(or a custom OS), it loads into the other slot not being used, and when finished installing, it boots from that slot.

I really don't have any more technical, how-to answers to give since I'm really a noob at all this and just follow written guides and instructions on how to do this stuff. I wish I could help you more.

Someone jump in and correct me if I'm wrong.
[Google Pixel 5a] drtweakllc:
Jim your reply is greatly appreciated. To give you more information, I sideloaded the latest OTA from GrapheneOS and it went through optimizing apps then booted to the OS start screen, when I tap start it goes into a boot loop back to the start screen. GrapheneOS is designed to be secure so it relocked my bootloader after flashing it, otherwise I would be OK if it was unlocked. My thought is that if I can boot to the b slot as you did I could get back into my phone and unlock my bootloader and reflash. I will search around d and see if I can find the command. If you have any other questions or suggestions please post. Thanks
[Google Pixel 5a] drtweakllc:
I started a new thread here https://xdaforums.com/t/pixel-5a-with-grapheneos-crashing.4562159/
[Google Pixel 5a] leech1980:
I'm in a similar situation. pixel won't accept my pin, rebooted and now stuck in fastboot mode. When i connect my pixel to my PC adb doesn't detect the device. Google driver is installed already. Any help is appreciated.
[Google Pixel 5a] dcarvil:
fastboot --set-active=a

Or sub a for b etc depending on which slot you want
[Google Pixel 5a] drtweakllc:
Thanks, I found that command but it didn't work since the bootloader is locked.
[Google Pixel 5a] sampathjanitha:
the same thing happened to me two days ago, pn went into a boot loop while transferring some files via nearby share. it had the latest update of android 13 with a locked bootloader.

i tried flashing ota file via adb and it stopped at 94%, done a full reset via recovery but nothing changed except now it hangs on the android logo.

when you have time, let me know how did you solve this and how did you change the a/b slots.
[Google Pixel 5a] fjm568:
See post #49 above this...should have quoted you and replied...
[Google Pixel 5a] sampathjanitha:
Thank you very much for your fast and detailed response. I will get back to you once I try this. :)
[Google Pixel 5a] sampathjanitha:
Hi, I tried this method in a different way,

1. Installed the OTA while i was on active partition A.

2. Switch back to the fastboot without restarting.

3. In this moment active partition changed to B,

4. Then again flashed the OTA.

This solved the problem of hanging @ the google logo. But the phone keeps bootlooping.

I think this is a hardware fault, just like happened to the LG phones previously.

Phones that have loose connections in cpu may lead to black screen of death and the one's that have loose connections in ufs may lead to the bootloops.

Mine was doing a heavy file transfer when the bootloop happened. So i think its the ufs chip. Even though i assume this i don't have any technical knowledge in regarding this.

So if im wrong pls correct me someone.

I will try few more time to flash the ota, if it fails,

then i will find a technician to reball the chips if possible.

Sorry for the bad English too. 🙂
[Google Pixel 5a] fjm568:
Instead of doing your step 4, try to do a factory reset at that point. If that works, then sideload the latest OTA. That seems to be the only difference between what I did and what you tried, you just condensed it down to 4 steps, I wrote a novel, 🤣.

Mine would just hang on the G logo, but it was not bootlooping.

It seemed to me that mine was a software glitch. I don't know, since I don't really understand everything that's happening, but maybe when I tried restarting, the new software overwrote the bad, glitchy software on those partitions. It seems that the restart after the first OTA install, and the factory reset seems to be the only difference. My way worked for my issue.

I don't know. Maybe I was just lucky and this issue will appear again. But as of right now, I haven't had any issues at all since then.

How did you switch back to the fastboot without restarting?
[Google Pixel 5a] sampathjanitha:
oh, I forgot to mention, I did the factory reset thing also. but no luck here.

also after 94% is done in the ota flashing process, it finishes the flashing process and shows Total xfers 0.00x at the end of the adb cmd window. I don't know what that means.

after that phone goes back to the recovery window, that's how I went back to the fastboot menu without restarting the device.

I think you are the only person who was lucky enough to recover the 5a without replacing the mobo. 🔥
[Google Pixel 5a] fjm568:
Interesting.

Good luck to you.

In my case, like I said, it just seemed to me that mine wasn't a hardware issue and it seemed the symptoms were different than what everyone else was experiencing. Also, having a locked bootloader limits the options for recovery. I was lucky. My bootloader is unlocked now, just in case.

I hope you get it figured out.

Do you have the warranty replacement option available?
[Google Pixel 5a] sampathjanitha:
Thank you for the support given.

No i dont have any way to get a warranty replacement since i live in sri lanka. There is no authorize dealer/repair center for google here.

Like you did, i will try all the possible ways before giving up. 😉

My bootloader is locked too, not unlocking it was the biggest mistake i did. 😔
[MTCD  Android Head Units Q&A] teknodetay:
Hi, the sound is very detailed and loud when listening to mp3 with the px5 device's own application, but it sounds low when listening with the youtube application.

What could be the problem. ?

It's very good and loud when streaming audio even over Bluetooth, but low in pre-installed apps.

I increased the sys setting in the voice menu that opened by entering the password 126 from the factory settings, but there was no difference.

View attachment 5751917
[Introductions] Drpto:
Hi Guys,

I'm Dr.Opto from india. I'm a beginner Custom rom maker.
[Off-topic] johnny13oi:
Happy Thanksgiving Everyone!!!!
[Off-topic] Kraize:
Happy Thanksgiving. Althought I don't celebrate it. But to what I do celebrate. Happy EARLY Black Friday everyone!
[Off-topic] TheChampJT:
Happy Thanksgiving! Can't wait to be with family and feast :D!
[Off-topic] P1Tater:
Family, friends and great food. What more could one ask for?

Well, some TUMS would be nice now. I think I have gained a minimum of 5 lbs. in less than 12 hrs.
[Off-topic] TheChampJT:
LOL! Men's Health says you have to jog 8 miles a day for the next week!
[Off-topic] egzthunder1:
Or you can simply accept the fact that you just stuffed half a turkey in your stomach and be happy about it (I know I am :) )

Happy Thanksgiving to all!!!
[Off-topic] johnny13oi:
I just took in an amazing amount of food. Trying to stop myself from eating more.
[Off-topic] _fm:
Happy thanksgiving to all of you !! :D

Indonesian doesnt celebrate it, but i want to say that for you who celebrates it,.

hehe,. :D
[General Topics] dferferfer:
Hello, I have been trying to disguise my GPS for some time.

I have tried different apps from the PlayStore but always had the same result, that result is always the same. I get a notification:

"FAKE GPS creates a false location

Location services not available"

I have unfortunately found absolutely nothing on this subject. I always just come to the same pages that explain to me how to do what I do but so far. Without success.

Is it possible at all without root?

I found it but currently i have no access to rooted device

How to Fake your Location on Android using GPS Spoofing

If you want to fake your location on any app or game on Android, here's how you can use GPS spoofing and fake your real-time location.

www.xda-developers.com

Maybe anyone can help me

ot:

8 wow since 2014 im here....i didt know that :D

Years of reading :D
[General Topics] Arealhooman:
Hmmmm not sure how huewais work, but did you pick that apps to spoof location in devoloper settings?
[General Topics] dferferfer:
Yeah I do but didn't work 😓 I love my p30p but I think I need a new device because Huawei block my future using:/ no bl unlock, no future for old phones :(