I've searched and haven't found the answer to this, typically I can figure these things out but I'm at a loss.
About a month ago my 4 year old daughter dropped the tablet (inside poetic smart case) face first on a concrete floor, about a 2.5ft fall. The device was on at the time, but upon picking it up off the floor to survey the damage, cosmetically there was none but the tablet was dead. I could not get it to turn on or boot into the bootloader with several attempts.
A few days later, I took the back cover off and disconnected the battery ribbon for a few minutes. Once put back together, I plugged it into the charger and the LED light flashed as it would when it had a dead battery. After a few hours of charging, still would not boot. I then attempted to try booting to the bootloader and got that to work. However, from there any selection you make, reboot bootloader, recovery mode, start, etc... the device simply turns it self back off. Only once have I got it to go into the first recovery mode screen but then it turned off after making a selection there.
With 5.0 dropping today, I thought I'd give it a shot to see if adb and fastboot commands would recognize it. This is where things get weird for me.
adb devices show nothing listed, if I do fastboot -s XXXXXX devices it will then make some sort of connection. From there if I do fastboot reboot-bootloader it simply turns off again. The bootloader has always been locked and even says so on the device. However, if I do fastboot oem unlock it tells me the bootloader is already unlocked. When I tired fastboot oem lock, it took about 90 seconds and said it couldn't lock it.
I then downloaded 5.0 factory image, attempted to flash the 04.04 bootloader and is says FAILED Remote: bootloader is locked. Attempting to unlock again tells me it's already unlocked. See attached photo of Terminal and device bootloader screen.
Anyone have any ideas here?
So.... just because, I took the whole device apart and then back together again. Held down power button and the thing booted into the OS. However, the touchscreen is not responsive. Looking into that now.
Looks like I got teased.... ever since it fully booted (without touch response) I've yet to manage to even get it to boot into the bootloader.
Not much help going on here, the more I've read the more it looks like a motherboard replacement is what's needed. I'm out of warranty by a couple months, so I guess I'll be looking around the web to see what I can find as a replacement.
Related
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Saenchai said:
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Click to expand...
Click to collapse
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
hkgrob said:
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
Click to expand...
Click to collapse
No, because i thik i have to unlock the bootloader fist to do that, or not?
Edit: Yes it is like that. Cannot flash roms without unlocking bootloader first. It gets stuck and command line shows error after "boot" command > bootloader locked.
I cannot do anything in ADB, only fastboot-menu (Advanced Utilities > Launch). But btw, i found this here, im just a bit afraid to use it. Rooting/flashing Roms WITHOUT unlocked bootloader and ADB
http://forum.xda-developers.com/showthread.php?p=43993722
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Pandae said:
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
Click to expand...
Click to collapse
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
xdhall said:
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Saenchai said:
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Click to expand...
Click to collapse
That confirms it. You're beyond my help. I'm fairly certain there's a way to unbrick from where you are. You'll just need someone with more experience than I have.
Sent from my Nexus 6 using Tapatalk 4
Saenchai said:
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
Click to expand...
Click to collapse
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Pandae said:
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in abother post here there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Saenchai said:
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in this post (and a few others) there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Click to expand...
Click to collapse
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
GSLEON3 said:
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
Click to expand...
Click to collapse
Thank you very much for this tip. I heard of it but was afraid that it would break seals. I will keep this in mind should i have another problem like this.
The device is now send to repairs. i hope to get it back soon...
Good luck! Sorry we couldn't give you a working remedy to do yourself.
Dear Nexus 5X users,
I would like to share my success story to booting up the bootlooped Nexus 5X. My phone was bootloader locked when the bootloop happened. After searching threads for hours, I found out I had to unlocked the bootloader. And the only way to do that is to go to the developer's option and change the OEM bootloader setting. But, it seems impossible to do that when I am having the bootlooping.
From one of the thread, I saw that one person used a hair dryer to heat up his phone, then the phone booted up normally. So, I also tried to heat up my phone. Following is how I did that. It only took ~10 minutes.
I put my phone on top of my electric radiator. The phone has a cover, so it kinda helps not to burn my phone. After 5 min later, I turned on my phone. It rebooted 2-3 times, then magically it booted up normally. So, I quickly activated developer's option and switch on the OEM bootloader unlock option.
Now, I just installed TWRP and one of the 4core kernel. It is booting normally. I hope this is helpful for someone who is in my position.
If this is not an appropriate new thread, or there is a better thread I can post to, let me know.
Man, I am in a somewhat similar situation. Was running PureNexus ROM, when suddenly got BLOD. In my desperation, I wiped data clean as soon as it booted into TWRP after a million tries. Now device won't go beyond Google logo, and the bootloader (fastboot) mode is not being detected in PC
I tried all driver installation methods, but the culprit is incorrect device ID being shown to my PC - USB\VID_0000&PID_0002\5&ECB7860&0&9 (unknown usb device - device descriptor request failed)
What do I do? I can heat up the phone but will have to continue doing it till the first boot after data wipe finishes, which can be like 10-15mins, which sounds risky.
UPDATE:
My situation was peculiar, because I had wiped the /data partition when the device was already bootlooping (managed to boot into TWRP after cooling the phone and wiped /data in my infinite wisdom). After that, I was still stuck in BLOD, except one change - PC was no longer recognizing the device in fastboot (see the hardware ID I mentioned above).
How it fixed it:
Removed the case, and heated up my phone with a hair dryer for 5min
Booted it up, it was stuck on Google logo for a fairly long time before bootlooping, as compared to earlier. My guess - it was trying to load system files, which wasn't happening when the phone wasn't heated up.
Now I booted into bootloader and PC was able to recognize the device in fastboot mode.
Finally I was able to flash the moded boot.img files to disable bigger cores and my 5X is back to being my daily driver.
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
Okay. To start I am definitely still learning. I am usually very careful to make sure I know through through research what Im doing. I just started with this device 42 days ago. I loaded aicp 11 on it. Today however I went and downloaded the Factory images from Google for Android 11 the last frimware I was on. Verified it's the correct image for my device. However to my horror when the device booted as yes it booted. Android 8.0.0 was actually what flashed. I checked the log and what I flashed was not named anything other than Android 11 file name. I confirmed by downloading again the same from googles site. Somehow today I was subject to a error. Not sure who's. Don't care. My device is under warranty as I bought new from Amazon. I was told since it booted stock frimware it should be fine to replace. However I more or less would like to know as I am trying to learn. In the state of my device. Is there anything I can do.
----Situation----.
After booted
-imput - Adb reboot bootloader. fastboot boot TWRP.img. In twrp backed up. Never flashed.
Reboot bootloader
---screen remains black. I forced reboot pwr key-Vibrates. White line indicator that power is off. "flicker?" Not sure how to describe that better. Device no longer responds to key command to bootloader. Device is not recognized by Device-Pc-Tablet when I connect it using Adb fastboot PC and Bugjbugger fastboot app. I also tried to get chrome to recognize it. Nothing. Not even unknown device. I tied a string over power key to help battery die. Once I plugin to charge vibrated. Screen flicker again. Nothing boots.
--no adb -- no bootloader- no display- no usb- no screen failure as device never tried to boot-- I know I'm new to this device. I would never knowingly flash to stock from 11 - 8.0.0. Is there something I can do at home to force fastboot/bootloader as it vibrates and tries to boot--.
Did you solve it?
I fear it may be a hardware issue. It doesn't sound like you did anything that should cause the phone to brick.
The flash chip on the phone can wear out - that might have just randomly happened when you backed up data in TWRP. But that's just a wild guess.
I'm not really sure either. I cannot get any usb connect. I have Qualcomm drivers as well. Nothing shows up. Not even unknown device. I'm mailing it in on my warranty. I was going to take it in to UbreakIFix store. However that's 50 miles from me. In the city thats a trip.
Jovize87 said:
Okay. To start I am definitely still learning. I am usually very careful to make sure I know through through research what Im doing. I just started with this device 42 days ago. I loaded aicp 11 on it. Today however I went and downloaded the Factory images from Google for Android 11 the last frimware I was on. Verified it's the correct image for my device. However to my horror when the device booted as yes it booted. Android 8.0.0 was actually what flashed. I checked the log and what I flashed was not named anything other than Android 11 file name.
Click to expand...
Click to collapse
You probably picked the FIRST file in the list instead of the LAST.
The file name has "opd1" in it, right?
What you want is the LAST file in the list with "rp1a" in the file name.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Jovize87 said:
I confirmed by downloading again the same from googles site. Somehow today I was subject to a error. Not sure who's. Don't care. My device is under warranty as I bought new from Amazon. I was told since it booted stock frimware it should be fine to replace. However I more or less would like to know as I am trying to learn. In the state of my device. Is there anything I can do.
----Situation----.
After booted
-imput - Adb reboot bootloader. fastboot boot TWRP.img. In twrp backed up. Never flashed.
Reboot bootloader
---screen remains black. I forced reboot pwr key-Vibrates. White line indicator that power is off. "flicker?" Not sure how to describe that better. Device no longer responds to key command to bootloader. Device is not recognized by Device-Pc-Tablet when I connect it using Adb fastboot PC and Bugjbugger fastboot app. I also tried to get chrome to recognize it. Nothing. Not even unknown device. I tied a string over power key to help battery die. Once I plugin to charge vibrated. Screen flicker again. Nothing boots.
--no adb -- no bootloader- no display- no usb- no screen failure as device never tried to boot-- I know I'm new to this device. I would never knowingly flash to stock from 11 - 8.0.0. Is there something I can do at home to force fastboot/bootloader as it vibrates and tries to boot--.
Click to expand...
Click to collapse
Sounds like you could have a dead battery? Or it just booted into a strange state. Keep trying.
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.
dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.