Develop Bugs

Does the unlocked Bootloader help unbrick the Pixel C with corrupted hard drive?

So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?

randy6644 said:
So the issue can be referred to :http://forum.xda-developers.com/pixel-c/help/corrupted-hard-drive-dead-pixel-c-t3290331
https://productforums.google.com/forum/#!topic/nexus/xoaMSAa8yC8
I bought the Pixel C few days ago. I'm in China , I haven't got it yet. It's till in transit. I have read some people have this issue. It really worries me because I don't get to RAM it since I'm in China. If anything like this happens then I will have a bricked device.
My question is if I unlock the bootloader as soon as I get it. If this issue occurs, am I able to sideload the factory image to unbrick it?
Also , I would like to know if the latest batch(the ones you can get with the developer discount) have the wifi issue or are they of the same batch as the previous ones?
Click to expand...
Click to collapse
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.

If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.

charesa39 said:
For every Nexus device I purchase, it's standard practice to unlock it before completely setting everything up. So right after opening it, I'll do a quick setup and use a couple apps to check for things like dead pixels or lightbleed. Then, if everything checks out, I'll unlock the bootloader and flash the latest factory image to make sure I'm getting a fresh start from scratch. I've never seen a reason NOT to unlock the bootloader first. It helps get you out of trouble if something were to go awry on the software side. I've never encountered an issue that flashing a factory image couldn't fix.
While I can't attest to anything regarding the original batches, I can tell you the device I received with the dev discount has been perfect. No issues so far after using it for 2 weeks. I believe it was manufactured in January 2016 if the serial number naming scheme is the same as other Nexus devices.
Click to expand...
Click to collapse
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.

brando56894 said:
If you have a dead HDD, nothing can fix it other than replacing it. I'm not sure if that's a software or hardware error, if it's software, reformatting the drive may help, if it's hardware, you're obviously screwed.
Click to expand...
Click to collapse
I think the problem mentioned should be a software issue. As in those two threads , they are not able to boot up the device simply by factory resetting it. And they failed to flash the factory image to the bricked device since it's locked.

randy6644 said:
I've bought lots of nexii devices ,say, Gnex, nexus 7 , nexus 6 and 6P. I used to do a lot of flashing just like you do, the first thing I did was unlocked the BL and flashed a new ROM, kernel and maybe did some tweaking. But I haven't messed with my 6P cause I don't wanna unlock the BL for security reason. With an unlocked bootloader, just think about it, if you lose your phone, anyone can do whatever they want. with it That's not cool at all. So I'd rather keep it the way it is.
Glad to know that you don't have any issue with your device. I hope it's the same in my case. Thanks for the information.
Click to expand...
Click to collapse
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk

brando56894 said:
While this is definitely true, your average cellphone thief is about as tech savvy as a wet piece of leather hahaha I've had this concern myself but then realized that maybe 2% of Android owners know how to get to the recovery, hell most reps at cell phone stores don't even know how to do it, even the ones that are "techs"!. When I had my S4 rooted and stupidly let it slip that the phone was rooted, next time I came in the rep looked over the phone and called out a tech who looked at the phone for 30 seconds then said "do you know how to get to the recovery on this???". A simple pin/password/pattern lock will thwart about 90% of phone thieves out there from getting access to your data, they're most likely just going to wipe it anyway. They couldn't care less about your data, they can't sell or use that as easily as they can the device itself.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .

randy6644 said:
Well, usually thieves might just wipe everything. But still, there are risks. There are certain ways to go around the locked screen if you got a unlcoked BL and rooted phone. I've got all my photos( No nude pics ) stored on Google, and also all my contacts, whom wouldn't be happy to share their information with a thief, and some notes, payment apps as well as some important emails. There's too much going on and I don't wanna take risks. Also, if my phone got stolen, I'll have make sure the SOB got a brick ,nothing more. Sure they can tear it apart and sell some parts of it, but they don't get a phone.
I still flash roms and stuff on my oneplux which i got few days ago since my nexus 6 went dead, I do that because it's not my main phone and I don't have a lot of personal information stored there unlike on my 6P. For a tablet, maybe I would do that since I'll put it home usually .
Click to expand...
Click to collapse
In that case, Android Device Manager comes into play and allows you to beef up your security.
Sent from my Pixel C using Tapatalk

Unlocked HTC 10 Random Reboot

Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?

Highlyanimated said:
Hi all, I have a HTC 10 unlocked version which is running Android 7.0, Software version 2.41.617.3.
I've owned the phone since October, around November it started randomly rebooting. It occurred maybe once every few days or once a week and the frequency increased.
I sent the phone to HTC for repair earlier this month, and they sent it back saying they couldn't reproduce the error.
I had thought the issue was my SD card, so since receiving the phone this week from HTC I have not installed my SD card. The phone worked 3 days before randomly rebooting an hour ago.
I've sent all the crash log files to HTC, and now realize that I might have not sent them at all.
I know others have had this issue with their HTC 10, has anyone figured out a cause?
Also, is the replacement phone from Uh-Oh protection new in box or a refurbished phone?
Click to expand...
Click to collapse
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.

xunholyx said:
Did they send it back in the same condition, or did your phone come back with all of your apps and data still intact?
You could try to run the US Unlocked RUU to see if that fixes it ( it should), and run it without restoring any data.
Click to expand...
Click to collapse
Thank you for the suggestion.
I went through all of the standard troubleshooting before they escalated me to repair status.
First I did safe mode, after it rebooted in safe mode I did a factory data reset. After the reset I did a cache wipe and that didn't work. I also did a cache wipe, and factor data reset. Finally, I installed the RUU from their webpage and the problem persisted.
I wiped the phone and set it back to them, they were unable to get the phone to reboot during the 2-3wks they had it.

Any other suggestions, or answers to the question about Uh-Oh protection?

Highlyanimated said:
Any other suggestions, or answers to the question about Uh-Oh protection?
Click to expand...
Click to collapse
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.

auggie721 said:
The replacement phone can be either refurbished or new, according to the ToS from HTC.
I just received my Uh Oh replacement from HTC the other day, and it looked new but was not in a retail box. It was shipped by Ingram Micro which is a wholesaler.
Too bad my replacement is doing the exact reboot thing you described, which is why I am reading the forums tonight. Sigh.
Click to expand...
Click to collapse
Sorry to hear that Auggie,
For the past 9 days I haven't had any reboots. Solution, turn off 4G LTE and use only GSM/WCDMA. Perhaps give that a try, if the same thing happens, then I think it means there's an issue with the radio (firmware/hardware).
Sucks, because service here on AT&T in LA is worse than when I lived in NYC and no LTE is like torture.

Thanks, this workaround solved my HTC reboot issue, keep using 3g is a pain but at least no need to buy a new phone. HTC supports or technicians really don't understand and know how to solve the issue

Pixel 2XL Call Sending and Receiving Issues

I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?

if they wont RMA for that issue, then id call and just say you have burn in or the screen is very blue. should get an immediate RMA. They never questioned me when i got mine swapped

redman1982 said:
I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?
Click to expand...
Click to collapse
I too am on big red, using an unlocked phone from google, not the Verizon variant. If you've done 3 factory resets, and still having the problem, then I'd say it's either a hardware, or sim card issue. Since you can't unlock the bootloader to try a different radio, or flash a factory image, I'd definitely lobby hard for a replacement. That's just not right. Certainly hope you get it figured out though.

redman1982 said:
I am running the security patch dated January 5, 2018 and Android 8.1.0. Probably two weeks ago, I started having problems making and receiving phone calls and went back to the Verizon Store. At first Google and Verizon thought it may be a hardware issue, but had to do a factory reset to rule that possibility out or in. Today I started having similar issues and brought it back to the store. Since I rely on the phone for my business, factory resetting, even once per month is unacceptable. I called Google from the store and all they could offer was that this is a known issue and I will need to do another factory reset. I am in the process of completing this right now. Has anyone else had similar issues? I bought the phone since I want as close a pure android experience as possible, but I can't run my business with an unreliable phone. Are there any ROMs out there that are stable and don't have this issue?
Click to expand...
Click to collapse
Redman1982 .. I had the exact same issue after installing the January Security Patch .. after calls to both Google and Verizon, took back to Verizon store and they switched it out for a brand new sealed one.

Like others have said, after multiple factory resets on a locked device, you should demand Google replace your $900 flagship device that is not working properly after 3 factory resets, and nothing you can do to it (it's locked) could make it not work, so it's obviously a faulty device issue.
I would certainly try to get Google to send you a replacement, as several folks who had VZW locked devices have said when getting Google replacement devices, they were sent unlockable Google variants instead of locked Verizon variants.
It might be a long shot, but if you go into a VZW store, you have a 100% chance of getting another locked device
Either way, don't stop bugging them until they replace your device!
Good luck!

Az Biker said:
Like others have said, after multiple factory resets on a locked device, you should demand Google replace your $900 flagship device that is not working properly after 3 factory resets, and nothing you can do to it (it's locked) could make it not work, so it's obviously a faulty device issue.
I would certainly try to get Google to send you a replacement, as several folks who had VZW locked devices have said when getting Google replacement devices, they were sent unlockable Google variants instead of locked Verizon variants.
It might be a long shot, but if you go into a VZW store, you have a 100% chance of getting another locked device
Either way, don't stop bugging them until they replace your device!
Good luck!
Click to expand...
Click to collapse
Yeah .. I tried doing that .. problem was, I walked into a Verizon store that had stock of the Pixel 2 XL Black 128GB version .. I was like .. ****tttt .. LOL

LordGeek said:
Yeah .. I tried doing that .. problem was, I walked into a Verizon store that had stock of the Pixel 2 XL Black 128GB version .. I was like .. ****tttt .. LOL
Click to expand...
Click to collapse
Update. I continued to have issues which began to include a loud screech when the other party answered. I went back to the store about two weeks ago and they gave me a new sim card. This worked about a week and began having problems again. I called Verizon Saturday night as I was unable to work. After about two hours of troubleshooting, the rep conceded that I should get a new phone which arrived yesterday. I hope this one works out.
Sent from my Pixel C using Tapatalk

redman1982 said:
Update. I continued to have issues which began to include a loud screech when the other party answered. I went back to the store about two weeks ago and they gave me a new sim card. This worked about a week and began having problems again. I called Verizon Saturday night as I was unable to work. After about two hours of troubleshooting, the rep conceded that I should get a new phone which arrived yesterday. I hope this one works out.
Click to expand...
Click to collapse
Keep us posted on your progress.
I wonder if it is a common problem

I've been having this same issue since the March update. I make calls and I don't get the ringing tone and when the other person answers the call there's no audio. I've already done a factory reset and this is already my second Pixel 2 XL. This sucks.

brazcub said:
I've been having this same issue since the March update. I make calls and I don't get the ringing tone and when the other person answers the call there's no audio. I've already done a factory reset and this is already my second Pixel 2 XL. This sucks.
Click to expand...
Click to collapse
Did you have any Bluetooth connected? I have Gear S2 smarwatch connected and I had to switch off call forwarding to get rid of that issue

Question Pixel 6 refurbish check

I'd like to know is there any possibility to check if pixel 6 phone is repaired/refurbished?! I've bought p6 pro today but can't make fingerprint to work (FOTO in attachment). I saw that other people have same problems when phone turns off by self (battery goes to 0% and buy) but after hard restart everything works again...not in my case. Seller told me that his wife used telephone for just few days and decided to stay on iPhone, but I'm start to thinking that I'm scammed; under display on small plastics antenna line I see just a little scratch so I'd like to ask is there a chances that screen is replaced. All other looks like 100% new phone.

Sounds like it may have been opened. During factory assembly it's very unlikely for this to happen.
It may actually be a mark from a plastic pick used to disassemble it and not a scratch.
The display is replaced as are internal components from the front I believe.

blackhawk said:
Sounds like it may have been opened. During factory assembly it's very unlikely for this to happen.
It may actually be a mark from a plastic pick used to disassemble it and not a scratch.
The display is replaced as are internal components from the front I believe.
Click to expand...
Click to collapse
Since the OP states that he bought the phone used, it's more likely that the person previously in charge of keeping the phone, damaged it/scratched it. Plastic is ridiculously easy to scratch, even a grain of sand in your pocket can be enough.
Proday said:
I'd like to know is there any possibility to check if pixel 6 phone is repaired/refurbished?! I've bought p6 pro today but can't make fingerprint to work (FOTO in attachment). I saw that other people have same problems when phone turns off by self (battery goes to 0% and buy) but after hard restart everything works again...not in my case. Seller told me that his wife used telephone for just few days and decided to stay on iPhone, but I'm start to thinking that I'm scammed; under display on small plastics antenna line I see just a little scratch so I'd like to ask is there a chances that screen is replaced. All other looks like 100% new phone.
Click to expand...
Click to collapse
If the phone was properly cleaned and re-packaged and not damaged, there is no way for you to find out if you received a refurbished phone (phone that was sent back by the original customer without damage, return window or something). At least not from a "software" perspective. You as a perceptive human can always try to see if there is dust residue, fingerprint signs or anything "physical" like that on the phone/inside the package, but there is not much more than can help you to decide that (except asking Google, you could hit them up with the phone IMEI and tell them that you bought it used and want to know if it ever got officially repaired/replaced, but I have no idea if Google would even bother giving you a decent answer).
Concerning repair (phone being opened by a repair technician to fix stuff inside) - other than physical markers (prying a phone open can cause damage to the chassie), there is not much that you can find out about that. There is no way to get the specific part IDs with software and even if that was possible, it wouldn't help your cause since Google would only use genuine original parts to repair a phone.
Concerning the "plastic under display" part, I do not follow here. What plastic under display? The display is not transparent, you can't see the phones interior through it. Can you make a photo of your observation?

Proday said:
I'd like to know is there any possibility to check if pixel 6 phone is repaired/refurbished?! I've bought p6 pro today but can't make fingerprint to work (FOTO in attachment). I saw that other people have same problems when phone turns off by self (battery goes to 0% and buy) but after hard restart everything works again...not in my case. Seller told me that his wife used telephone for just few days and decided to stay on iPhone, but I'm start to thinking that I'm scammed; under display on small plastics antenna line I see just a little scratch so I'd like to ask is there a chances that screen is replaced. All other looks like 100% new phone.
Click to expand...
Click to collapse
Most likely the battery died resulting in the FP Sensor getting disabled. A Factory reset and/or full flash to latest image should always be done when buying a phone (especially when it's used). This will fix your issue also (using the flash.android.com tool) along with the calibration tool at the bottom of this page: pixelrepair.withgoogle.com/carrier_selection -- 99% a factory reset/wipe, flashing to the lastest build and using the fingerprint calibration tool will fix your issue. If not, you can get a replacement by telling google you did all of these things and they'll send you a phone (usually an advanced RMA if you show you've done everything previously mentioned).
The "Flash Tool" will update your Pixel to the latest Android version, along with an option to "Wipe" the device (make sure to hit the edit pencil and pick "Wipe Device" & "flash all partitions" ; if its a VZW model, updating in Android System in settings and factory reset in Recovery will be good enough, along with the calibration tool): flash.android.com/back-to-public
If it was refurbished by Google, you can put your IMEI# in the official Pixel Repair link below, and it will tell you some information (for example if its Unlocked, "Pristine or Refurbished" etc - it's a pretty great way to find out some info about a pixel (didn't know about it until recently). If the screen was replaced by UbreakiFixit for example, it probably won't show up as refurbished. it has to go through Google to probably be changed in the system, but I am just speculating.
Code:
https://store.google.com/repair

@Proday Can you return it? That would be the way I'd go initially. You got sold a phone that is defective hopefully it was through either ebay or Swappa with some guarantees.

At first, thank you all for helping.
@Alekos Last night i did install last (Dec) update with adb fastboot; found it here on xda (because google pull it back from servers) but as i sad, problem is still here/same. From some reason repairmypixel with google doesnt work; I put telephone in right mode, google chrome finds it, but when I start procedure it goes and goes and ~5min later Telefon restarts by self and Im getting disconnect error/try again msg. Ill try this link now to see what happens with imei, thanks one more time.
@bobby janow I've got a bill brom google store, but im going back in my country in a few day and don't have enough time to "play" with warranty procedures
Btw I've made a Foto of "under display scratch" the best I could; for me it is out of mind that someone opened display on anthena line but who knows

Proday said:
At first, thank you all for helping.
@Alekos Last night i did install last (Dec) update with adb fastboot; found it here on xda (because google pull it back from servers) but as i sad, problem is still here/same. From some reason repairmypixel with google doesnt work; I put telephone in right mode, google chrome finds it, but when I start procedure it goes and goes and ~5min later Telefon restarts by self and Im getting disconnect error/try again msg. Ill try this link now to see what happens with imei, thanks one more time.
Click to expand...
Click to collapse
There are two separate things being talked about. @Alekos said to go to https://store.google.com/repair and you might find out if it was refurbished or not (not necessarily). Should look similar the the following once you enter your IMEI in the site:
Click to expand...
Click to collapse
And then there is Official Google Pixel Update and Software Repair, which I suspect is what you're talking about didn't work for you, but please confirm. I know over the last two months, some others have occasionally checked Official Google Pixel Update and Software Repair and found that they hadn't updated it for the Pixel 6/Pro yet, so maybe that's still the case.

I've understand what he sad. Imei checked, results below...
And attach with pixelrepair that doesnt work (pop up blocker turned off)...
And I can try with Official Google Pixel Update and Software Repair, but I'm certain that it is the same as factory image installed with adb command, that I did (although I've put dec update not nov).

Proday said:
I've understand what he sad. Imei checked, results below...
And attach with pixelrepair that doesnt work (pop up blocker turned off)...
And I can try with Official Google Pixel Update and Software Repair, but I'm certain that it is the same as factory image installed with adb command, that I did (although I've put dec update not nov).
Click to expand...
Click to collapse
Thanks, are you using the OEM USB-C cable? At least half a dozen users in this section didn't have success getting their Pixel 6 Pro working using the factory image zip, but Official Google Pixel Update and Software Repair got their phone restored to stock and fixed their issue. It really seems to have been a lifesaver for some.

Yeah, I'm a little bit experienced
I'm going through this Official Google Pixel Update and Software Repair, see results soon. And I'm thinking that I know where is problem with pixelrepair.withpixel...didn't kill adb command; this flash tool tould me that i have to do first becouse adb is already in use...can be sam problem.

Proday said:
Yeah, I'm a little bit experienced
I'm going through this Official Google Pixel Update and Software Repair, see results soon. And I'm thinking that I know where is problem with pixelrepair.withpixel...didn't kill adb command; this flash tool tould me that i have to do first becouse adb is already in use...can be sam problem.
Click to expand...
Click to collapse
Ah! Hopefully, you'll have the solution soon.

So, I did all as @Alekos sad in another thread:
edit-- sorry, didn't realize you already posted separately. I commented to your post anyhow.
Did you figure this out yet? I would try wiping the phone, installing the latest build from the flash tool website (specifically this link: flash.android.com/back-to-public), on that page, edit the options for "Wipe" and "Flash all partitions". After it's done, run the Calibration tool (bottom of this page: pixelrepair.withgoogle.com/carrier_selection ) - this should work, if not my guess is there's a bigger issue.
Still same problem with fingerprint...now I'm certain that's the hardware problem; or screen is replaced or FP sensor is dead
Anyway, I want to thank you all 9ne more time, I've learned something new yesterday and today!!

Proday said:
I'd like to know is there any possibility to check if pixel 6 phone is repaired/refurbished?! I've bought p6 pro today but can't make fingerprint to work (FOTO in attachment). I saw that other people have same problems when phone turns off by self (battery goes to 0% and buy) but after hard restart everything works again...not in my case. Seller told me that his wife used telephone for just few days and decided to stay on iPhone, but I'm start to thinking that I'm scammed; under display on small plastics antenna line I see just a little scratch so I'd like to ask is there a chances that screen is replaced. All other looks like 100% new phone.
Click to expand...
Click to collapse
That message is so familiar to me and i'm frightening of it
For the last month I've been in possession of 3 (three!) p6p. The 1st one was received from my carrier and it burned out while updating to December software being only 2 weeks old, no sign of life, dead while charging etc.
Google shipped another one stating it is Pristine which means Like New condition. It came in a refurbished white box, much smaller than the original one and there was a tiny dent - almost like yours but located on top of the screen. What is the most important - I was getting that message "Enrollment was not complete..." Flashing at flash.android.com did not solve anything but was successful. Google support representative advised to get into safe mode, try to configure fingerprint again and it didn't work as well. Calibration tool was not offered as an option at all.
Now it's on the way back to google. The 3rd one I'm owning now is a new phone with no issues so far.
So my advice is to return your faulty phone to the seller if you are still able to. Getting a replacement from Google is tricky as you may get another pristine p6p with the same or other issues. Or you are lucky and you will get a good one but it's a lottery anyway. So it's up to you.
Good luck!

@asdor I was with seller right now, he brings me my money back...end of (sad) story There are still good people!

Question *Urgent Help* Bricked Pixel 6 Pro

I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.

Tombo12 said:
Ahhh I'm from the UK. I only got the phone just a month ago too and now this has happened. I checked on the their Uk site i can take it to a local mobile carrier and they've stated that they will do the repair next day. I might just do that tomorrow if not then I'll speak to Google.
Click to expand...
Click to collapse
Good luck! Let us know how things go.

roirraW edor ehT said:
Good luck! Let us know how things go.
Click to expand...
Click to collapse
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.

Awesome news! There are at least a handful of other users who have reported getting bricked since Android 13 came out August 15th, and I believe all of them reported good news from Google for repairs, but I don't have any idea if any of them were in the UK, so glad it's going to work out there too.

Tombo12 said:
Some News for everyone!
So I spoke to Google and they was fine about it phone not working went through some troubleshooting tricks neither of the options worked. The rep on the phone gave me two options Send it into Google for a repair and they'll send me over a replacement 6 Pro whilst its being worked on. If they can't fix it they'll let me keep the phone but if all is well with the phone then I'll need to return it back otherwise I'll get charged for it.
The second option is sending it in for a repair at a local authorized repair center. Luckily there is one 10-15 minutes away from me but the annoying thing is all bookings are available during my working hours but the place has 5* reviews and can get the phone repaired within the same day.
So I might just go for my second option tbh seems alot more convenient and less hassle of having to send a phone away to Google and wait 10 days for a repair which can be done within a day by a repair center that is less than 10 mins away from me and has all parts available to hand out.
Btw the repair center near me is called Ismash. There's one nearby me in London.
Click to expand...
Click to collapse
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!

Lughnasadh said:
Great to hear! If you end up taking it to the repair shop, please let us know what repairs they did (I'm guessing replacing the motherboard) and what they said was wrong with it (e.g. If it was an eFuse problem). Thanks and good luck!
Click to expand...
Click to collapse
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.

2015Ducatimulti said:
My 6 pro did this last weekend, when I was rooted I decided to flash a file to change the font and I missed the part it would work on 13 as long I deleted a certain file for the lock screen, it boot looped a few times, apparently it tried to load from slot B where android 12 was still flashed, and it hard bricked, no button combo would work, completely bricked, it was fully charged when this happen, so I RMA`d with google and my old device is suppsoed to be delivered to Texas today, then hopefully tomorrow my if I`m lucky that my replacement gets shipped.
Click to expand...
Click to collapse
Great. If you try again to be on the safe side, download this app and install font manager
GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
A module manager for Magisk because the official app dropped support for it - GitHub - Fox2Code/FoxMagiskModuleManager: A module manager for Magisk because the official app dropped support for it
github.com
Just use termux and type
Code:
su -c manage_fonts
Tbh I'm not 100% it works on A13, but I tried it on the a13 beta and it worked.

verszipo said:
i am also very curious if it actually needs a motherplace replacement or simply a reflash using a JTAG (or similar specialized tool) to get it out of the bricked state.
Click to expand...
Click to collapse
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.

96carboard said:
I can almost 100% guarantee that they fix it through the USB port. When its going into the bricked mode, it is no doubt going into a special recovery mode that isn't documented publicly.
Click to expand...
Click to collapse
bro any idea how to alive again with usb port even hard brick and show only usb serial port

Any update? I have the same issue, anti-rollback has caused my phone to become soft bricked and experiences WebView crashes, along with other problems.

Lughnasadh said:
I assume you didn't flash, at the minimum , the A13 bootloader to both slots or sideload the OTA after updating to A13 before doing this? If not, sounds like your device may have reverted to the A12 slot and ended up a brick due to the new ARB/eFuse shenanigans. The symptoms you describe are what happens when this occurs.
Luckily, it sounds like Google has been good at replacing devices that have encountered this so I would RMA it.
Click to expand...
Click to collapse
What does RMA stand for??

liammmmnnnn said:
What does RMA stand for??
Click to expand...
Click to collapse
Return Merchandise Authorization.

Tombo12 said:
I'm kinda screwed here and I really really need some help.
So I basically rooted my Pixel 6 Pro just out of boredom and wanted to tweak some stuff with the rooted version. In the end, I decided that it wasn't worth rooting as most things i can do i could already do on stock like customization and other things. Anyway long story short I've tried to Use the google flash recovery tool I wasn't looking where i was clicking and ended up flashing 12 by accident It *Was on 13 at the time* had it got near to the end but it kept booting me to this one section called "fastbootd" I hit factory reset and from there it done the reset and now the phone no longer starts or doesn't even displays the charging percentage.
I've plugged it into a computer nothing pops up no noise from my computer to say it has connected.
I've also tried to use power + down for 30 seconds - didn't do nothing.
Has anyone got out of this issue? Is this a Hard Brick?
I've plugged it into a charger and will see what happens tomorrow. I genuinely think its the battery has fully drained.
Cause I've ran out of ideas to try things and I need your expertise on this guys.
Your help will really be appreciated.
Click to expand...
Click to collapse
When I bricked my device, I had to hold power + down or up, I don't remember, for like two minutes straight while it was connected to my pc, try