I read the other topic in here about a Pixel 6 (or maybe 6a) stuck at the Fastboot mode screen. Unfortunately, I couldn't actually tell is any of the recommending things did anything. Actually, I couldn't even figure out what most of them WERE.
So, I have a FIVE DAY OLD, Visible Pixel 6a stuck at the Fastboot mode screen. I've tried all the combinations of power button, with and without volume buttons, changing the button to be Power Off, Rescue Mode, Recovery Mode and Restart bootloader. I've WASTED an hour and a half on the "chat" with Visible "support", which is without a doubt the most utterly useless excuse for support ever conceived.
{
"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"
}
Can someone provide simple, idiot-proof, easily understandable instructions to get this total POS to boot? And remember this is the ONLY screen I have, so whatever I'm going to do it either HAS to happen here or you have to tell me HOW to get to where you want me to be... I don't really have a WEEK to wait for another phone to get here - that's AFTER I BUY a replacement while they process the return... So, anybody knowledgeable who knows how to fix this?
Talked to google support. After a half hour of doing the same things I've been doing for the last half day, she said it's DEAD and dumped me off to contact Visible for a replacement. I don't think the replacement will be a Pixel.
Have you tried using the Android Flash Tool?
I'm not familiar with that tool. What can I do with it that will unbrick the phone?
GracieAllen said:
I'm not familiar with that tool. What can I do with it that will unbrick the phone?
Click to expand...
Click to collapse
Google is your friend.
Since this phone is only a few days old, having watched the video, I THINK I'd be better off returning the phone to Visible and finding something from a different manufacturer.
So lets back up a second.....what were you trying to do when this happened? What exact steps did you perform?
ctfrommn said:
So lets back up a second.....what were you trying to do when this happened? What exact steps did you perform?
Click to expand...
Click to collapse
Agreed. Op needs to give more info. Phones don't just decide to be stuck in the bootloader for no reason. We need the whole story
Phone was sitting on the desk. Doing nothing. Been sitting for hours. Sitting. Picked it up and it was on the Fastboot mode screen. Wasn't there when I set it down, as far as I know, several hours before.
OP has no more info to give. Phone DID "just decide to be stuck in the bootloader for no reason". That IS the whole story. Phone has now left the building so it no longer matters to me.
GracieAllen said:
Phone was sitting on the desk. Doing nothing. Been sitting for hours. Sitting. Picked it up and it was on the Fastboot mode screen. Wasn't there when I set it down, as far as I know, several hours before.
OP has no more info to give. Phone DID "just decide to be stuck in the bootloader for no reason". That IS the whole story. Phone has now left the building so it no longer matters to me.
Click to expand...
Click to collapse
Do you know if the battery happened to run out while sitting on your desk? If I remember correctly, I've seen a few other people who had this (NOS Production: error! Device State: error!) when their battery died.
It's possible. Phone sat there a few hours. I noticed in the 3 days it worked, that it had to be charged more frequently than the old phone.
The idea that a cell phone from what SHOULD be a reputable company will turn itself into a brick because the battery went dead is pretty appalling. Even if it's only once in a hundred times or a thousand times...
Thankfully I saw this. I also have left my Pixel 6a in fastboot mode for hours.
I've just turned it off. Phew.
At least yours would TURN off... Mine just immediately cycled back to the Fastboot mode screen.
Related
I have no idea why, it was working fine, until a few mins ago, but the battery was sort of running low, and I didnt charge it. The next thing I know, the phone is off and it wont start up again...
the pc wont recognize the phone when i plug it in, and when i try to charge it, it wont light up.
with the battery inside, when i hold the on/off key, it does vibrate, but it still doesn't turn on.
I didnt drop it, and its never been in water or anything... it just suddenly refuses to turn on...
any suggestions?
(btw, I'm on a 3 plan, and I've modded the phone, so I don't think I have warranty..)
oh, and its been about 2 weeks since my last mod from xda def, and have had no problems up till now.
any suggestions?....
thanks
pull out the battery and put it on the wall charger?
Then put the battery back in?
Just a thought.
syntrix said:
pull out the battery and put it on the wall charger?
Then put the battery back in?
Just a thought.
Click to expand...
Click to collapse
yeah tired that, but still wont work
oh, and btw, the phone keeps on making noises (melodies???) after it vibrates when i try to turn it on..
The startup sound when the 3G flies across the screen?
I wonder if you can touch areas and get a click. One thought. Once you think it comes up (2 1/2 mins I have heard in worst case), play with the volume button up and down.
Is it making noises? If so, then perhaps the screen is not working. Just a thought, but wouldn't hurt to try.
As it turns out, as long as the phone wont turn on, they wont know the phone is hacked
so I went to the 3 store, and they advised me to go to a service center nearby, they had no idea and they repaired it under warranty for free.
the problem was the LCD and the ear piece. thanks syntrix for bothering to reply
I had Similar problem
Interesting has my Touch Pro is new -- 1 week old -- and yesterday the battery was getting low. Next time I looked, it was off. Wouldn't turn on. So, I figured the battery had died -- very disappointing as I hadn't even left the office -- so it didn't even make it through first "work" day. When I got home I tried hooking to charger. No response. So, I popped the battery out and then back in -- everything back to normal. I haven't made any changes to the phone YET -- -- planning to install WDE in just a few minutes. Wonder if this isn't a bug in device?
Anyway -- my first post here at XDA -- "hey" ;-)
My pro started doing this today. Soft resetting won't turn the device back on either. I have to literally pop the battery out and back in.
Keyboard is also acting like it can't keep up with me and screen is very wiggly. WOndering if I got a dud.
(no startup htc touch pro) Depends in Haad image only
{
"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"
}
Looks like you have the Sprint version, have you checked in the CDMA forums?
htc touch pro t7272
No It's only picture I have htc touch pro t7272
Help Me Please my brother
Have you tried the following?
egzthunder1 said:
You probably had a bad flash. Follow the procedures on the OP and make sure that the files that you get (the roms) are not corrupted.
Click to expand...
Click to collapse
Hi Guys
On a stock Nexus 5, not rooted or anything.
Phone started factory reset without my help…
All three events happened while the phone was in my gym shorts front right pocket, upside down, screen facing me.
I was doing dead lifts or squats – the shorts were preset pretty tight around the phone.
I’m lost, since all official factory reset method are too complicated for this scenario.
Any idea what happened? Can it be a long press on buttons or the repeating body/phone movements?
Appreciate the help.
Aviram
you can factory reset while accidentally pressing a single button.
and question go in the q&a threads, not in general.
{
"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"
}
Your phone unlocked, went into settings somehow, scrolled down to the backup and reset option, clicked on it and clicked factory reset all from inside your pocket?
That has to be the most random thing a phone can do in a pocket without being touched.
jsgraphicart said:
Your phone unlocked, went into settings somehow, scrolled down to the backup and reset option, clicked on it and clicked factory reset all from inside your pocket?
That has to be the most random thing a phone can do in a pocket without being touched.
Click to expand...
Click to collapse
na, bare skin, or sweaty(moist) skin/cloths can make it get into places you never thought possible. while accidentally unlocked, i had moist cloths/skin get my phone to places that i never thought was possible. especially while moist, it can open weird places so fast..try using really wet hands on your screen. you csn try opening things, but other things will open.
simms22 said:
na, bare skin, or sweaty(moist) skin/cloths can make it get into places you never thought possible. while accidentally unlocked, i had moist cloths/skin get my phone to places that i never thought was possible. especially while moist, it can open weird places so fast..try using really wet hands on your screen. you csn try opening things, but other things will open.
Click to expand...
Click to collapse
That's still pretty random. The only other thing I could think of is that someone has access to his Android Device Manager and hit the wipe device button? From a tablet he may have or something. I don't know if you need a password for that since I have never done it.
while it is random, its not as random as you think. as ive found my phone(s) in open in random places on many occasions. it is rather unlikely that it reset the phone, but it is more than possible for it to happen, just by chance.
simms22 said:
while it is random, its not as random as you think. as ive found my phone(s) in open in random places on many occasions. it is rather unlikely that it reset the phone, but it is more than possible for it to happen, just by chance.
Click to expand...
Click to collapse
I guess this is possible, and today my Nexus 5 (only rooted) did a factory reset by itself for the second time.
The first time it was in my jeans pocket, no moisture. Now the second time, some moisture due to me cycling and keeping it in my cycling jersey, but seriously? Confirming and all that ****? Also, I guess it went into bootloader and the volume/power buttons where pressed to reset it. I can't imagine it would go through my menues for the second time around
Use a Lockscreens with pin
Hi all...
I think my N5 is buggered.
I was at a festival this weekend and my phone battery ran out so I left it in my bag for more of the weekend. On the drive back it was working fine as I was using GPs, making calls, using Gplay without any problems. As my GF wanted to charge her phone mine ran out again by the time I got home and I went to charge it as it was down to 2% but when I plugged the charger in it would not charge. It would start charging for a second then stop for a second and then start again. So I unplugged it and went to give it a re-boot and the screen came back on corrupted like this -
{
"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 have holding the volume down and power button to get to the fast boot menu and the screen does the same thing but this time while i'm holding it the screen with turn on and off wile vibrating 5-6 times before turning off.
I have even tried using fastboot to flash the recovery image onto the phone and it says everything has worked but again I get the corrupeted screen when I reboot.
Anyone seen or know of this problem? Or is it what I expect and it's got a hardware issue and needs to get repaired?
Thanks in advanced for any help or suggestions.
sn8f1st said:
Hi all...
I think my N5 is buggered.
I was at a festival this weekend and my phone battery ran out so I left it in my bag for more of the weekend. On the drive back it was working fine as I was using GPs, making calls, using Gplay without any problems. As my GF wanted to charge her phone mine ran out again by the time I got home and I went to charge it as it was down to 2% but when I plugged the charger in it would not charge. It would start charging for a second then stop for a second and then start again. So I unplugged it and went to give it a re-boot and the screen came back on corrupted like this -
I have holding the volume down and power button to get to the fast boot menu and the screen does the same thing but this time while i'm holding it the screen with turn on and off wile vibrating 5-6 times before turning off.
I have even tried using fastboot to flash the recovery image onto the phone and it says everything has worked but again I get the corrupeted screen when I reboot.
Anyone seen or know of this problem? Or is it what I expect and it's got a hardware issue and needs to get repaired?
Thanks in advanced for any help or suggestions.
Click to expand...
Click to collapse
It's a problem with the flex cable, the screen, or possibly the motherboard.
A few people have had this issue.
http://forum.xda-developers.com/google-nexus-5/help/nexus-screen-colored-pixel-snow-t2809802
http://forum.xda-developers.com/google-nexus-5/help/screen-scrambled-t2821507
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-screen-colorful-static-t2600032
Lethargy said:
It's a problem with the flex cable, the screen, or possibly the motherboard.
A few people have had this issue.
http://forum.xda-developers.com/google-nexus-5/help/nexus-screen-colored-pixel-snow-t2809802
http://forum.xda-developers.com/google-nexus-5/help/screen-scrambled-t2821507
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-screen-colorful-static-t2600032
Click to expand...
Click to collapse
Lethargy,
I had a feeling it was going to be a hardware issue. Thank you so much for the help... I'll get it sorted under my insurance then and get myself a temporary phone until then.
Cheers
{
"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"
}
Any hint about this issue? can't access anything else, the phone is stuck on that screen shape and mode. Tried to reboot and wipe cache already...
Edit: the image is not loading, here's the link: ibb.co/jAmesa
Did you ever figure this out? I have a customer's Honor 8 in my repair shop, and it did this as soon as I put the new screen on, and I haven't gotten it out of this mode since, even with the old screen. I've been looking everywhere, but it seems to be a somewhat uncommon problem.
Mydnytefantasy89 said:
Did you ever figure this out? I have a customer's Honor 8 in my repair shop, and it did this as soon as I put the new screen on, and I haven't gotten it out of this mode since, even with the old screen. I've been looking everywhere, but it seems to be a somewhat uncommon problem.
Click to expand...
Click to collapse
Yeah, I couldn't find anything about this issue on honor 8. I did find people with a similar problem on Galaxy S7 and they said that was because there is a magnet on those smart flip covers and if you're using a fake one or a bad quality one, the magnet might mess up some connection or the sensor under the display... but it sounds very unlikely to me, because any other stronger magnet would be able to cause the same issue then... like even something on your purse/backpack.
Well, but coming back to my device, for some reason the screen is normal again today. I woke up this morning and it was working normally. I called huawei support today because the phone is on the warranty period and had just came back from a screen replacement. So I figured this screen issue was in fact related to some bad connection after the screen replacement. But after I reported them the whole story, I was instructed by the Huawei support to use it and test it during the weekend, because it doesn't sound like a bad connection or malfunctioning since now it's working fine.
What I did yesterday was to turn the phone off (btw, while I had this screen issue, I couldn't actually turn it off... everytime I tried it, the phone rebooted automatically)... so... I turned it off and on again but on the safe mode (press and hold volume down as soon as you see the "H" from honor). I tought the safe mode could help, but it didn't change anything on the screen. Then, still on the safe mode I plugged the phone on my laptop to do a backup on HiSuite and then be able to do a factory reset... I thought this was another option to solve the screen issue, but I never concluded this operation because my laptop was also having some problems (not a lucky day for me hehe).. so in the end I just left the phone on safe mode and connected to the laptop to charge over night... I woke up a few hours later, the battery was on 100%, the safe mode was on, and also the screen was on and on full mode - showing the last notifications from apps... I went to the configurations immediately and turned off the smart cover mode. All my apps icons were disorganized... I organized everything again and decided to turn on the smart cover mode to try it out... it happens it's working fine since this morning even on the smart cover mode.
I really don't know what happened and neither how it got fixed..
The only reasonable thing I can consider to have caused this issue besides the magnet sensor or a software bug, is that I had some lock screen wallpapers saved to my SD card, which is slow speed. That might have caused some conflict when I opened the flip cover. When you open the flip cover, one of the wallpapers should appear, so maybe the phone had a hard time trying to read the file from the sd card and the screen was stuck... I did try to solve the issue by removing the sd card but nothing happened, so I honestly don't know...
Actually i had a different issue about the flip cover. When i was calling someone, even when the call was closed, the status bar remained Green with the call screen still open. Now after a reset the bug is gone. The strange thing on your problem is that's caused by the Honor cover and not by a chinese one..
I have a stock Google Pixel 6a, which is not and has never been rooted. USB debugging is not turned on and the bootloader is locked. The phone turned off while taking a photo. The power button had to be held down a long time to power back on, at which point it was in a boot loop. Phone battery was mostly full at the time this happened and there was plenty of storage space left. It should be noted that this was not the first time the phone restarted on its own, I just didn’t think much of it at the time. The phone was not dropped, exposed to water, or abused in any way. It just inexplicably turned off mid use. Which is when I realized my cloud backup never actually saved anything from this new phone. Ouch.
The phone was only 4 months old at the time it entered the boot loop (April 8th) , which is still well under warranty, so I contacted Google, who sent me their designated repair shop. The shop told me the motherboard was bad and would need to be replaced, but the photos would be safe. An internet search and call back to the shop confirmed all data would be wiped and I would have to get it off myself before the repair.
I tried everything I could find online to get the data. All the data recovery programs require USB debugging, which I never even knew was a thing, so was still off. There are a ton of solutions for rooted phones, but mine is not. Bootloader still works, so I tried to sideload the factory firmware from April 2023, which did nothing. There was a beta version at the time, which I also tried to sideload. This resulted in the phone only showing the “Google” load screen and not alternating to the “G” one. I reloaded the non-beta version and was back to alternating between the two. At this point I started trying the less conventional methods of repeatedly pressing the power button in case it was stuck and even putting the phone in the freezer. That didn’t help either.
Having run out of ideas, I decided to pay the fee for stupidly not having my stuff backed up and sent it to one of those data recovery places, figuring since there was no damage to phone, it should be an easy, albeit expensive fix. They were unable to recover any data. The diagnosis was:
“Our engineers observed there is a corrupted system partition. To put it simply, we are unable to access any point of the phone, even directly through the memory chip due to this logical failure.”
I don’t understand why the sideloaded firmware didn't fix this though. Could the hardware that stores the system partition have failed? And is that the same part that stores the photos? Could a chip swap to a new motherboard fix this, or is the chip that stores the system partition part of what is encrypting the photos? I’m just confused and want to make sure I have exhausted all possible ways to recover these photos before I turn my phone over to be wiped. At this point, I have accepted that all the photos and videos of my daughter’s first four months of life are probably gone, but am hoping someone more knowledgeable than I can either confirm or offer another idea.
HerdingCats said:
photos and videos of my daughter’s first four months of life are probably gone
Click to expand...
Click to collapse
Oh noes!
Had a similar thing with my wife's samsung on stockROM. Tried some things but in the end we/she had to accept it:
{
"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"
}
Backups are unbeatable - either be safe or sorry.
Still, I hope just like you that some saviour comes in here
PS: Shouldn't google backup the photos in your account?
SigmundDroid said:
Backups are unbeatable - either be safe or sorry.
Click to expand...
Click to collapse
Yep, I definitely knew better too.
SigmundDroid said:
PS: Shouldn't google backup the photos in your account?
Click to expand...
Click to collapse
Ah, that is what I thought. Apparently, the Pixel phones up to the 5 series would keep backing up all photos at a slightly lower resolution even when Google drive is full. The storage saver benefit was removed for the 6 series and on.