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
Related
First off my device is unlocked and rooted but that is it and I did that weeks and weeks ago when the latest android patch came out.
It has been working fine but I had a sleep over with the kids last weekend and they like to play with it as usual. After they left, hours later I noticed the device showing the google start screen like it was stuck there. I tried to get it into the boot loader or recovery and nothing. Now it appears dead, no lights, etc.
I tried charging and tried using the volume and power thing, etc to no avail. When connected to the pc I am gettng the dreaded QHSUSB_Dload thing.
#First question is there a fix for this? I have searched every where and have yet to find anything substancial other than the volume thing which is not working.
# second question is can I rma this or will it not be accepted due to it being rooted? There is no way I can bring it back to stock without accessing the bootloader.
#last question - If I cannot rms it can I take it apart and do something to repair it or is there anything I can do?
Thanks guys. This really sucks. i have never had an issue up until now and this thing is totally stock besides being rooted and unlocked.
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2381582
That will not work with a hard brick. I cannot get into bootloader or adb.
Sent from my Nexus 4 using xda app-developers app
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Thanks for the outpouring of support here. :banghead:
I think it is clear I'm screwed.
Pretty unbelievable as I'm all stock except for recovery.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
Bump
Do you guys think I can do an RMA?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd try to send it back for repair. What do you have to lose?
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I understand that, but right now you have a $200 paper weight. So why not gamble on the s/h for the rma?
I think you are misunderstanding what I am saying.
Google basically makes you pay for a replacement. Upon inspection they refund the money. If they do not refund the money then I am out the full cost.
I could find that reasonable if I was playing around or something but I have kept my devices all stock ever since the latest version came out except for unlocking and rooting.
I guess the other option would be to find someone to do a jtag repair and I could only find one guy and I don't think he touches Nexus 7s. Not sure though but waiting for him to reply. This sucks! My device was perfect and I loved it.Great battery, no touch screen issues. Not a single issue and then all of a sudden this. i really cannot understand what caused it.
Thanks for the reply. I really figured there would be others this happened too but everyone gets Hard Brick mixed up with soft brick and every hard brick post I read is not a hard brick. Hard Brick = F#cked :crying:
I gotcha. I thought you paid to send it back & then you had the option to pay to fix it if it wasn't covered by warranty.
That could be through Asus directly but not sure.
I think though if they go to repair it they will see the unlocked boot loader. That voids the warranty
Sent from my Nexus 4 using xda app-developers app
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
dkryder said:
If it was mine I would take the back cover off and unplug the battery and let it sit for ~5 min. If there is a physical reset plug then push that in a couple times.
Click to expand...
Click to collapse
Yeah, if you know an RMA is a very very very poor shot / don't want to try it. I guess a tear down is your second best bet.
You should check out Adam Outler's tear down videos if you feel you might be able to take this on. I'll link Outler's videos below. They MAY help you in deciding if you want to go through with it (and what you may expect to see).
http://www.youtube.com/watch?v=RMzi4K_PwPs (Transplant Nexus 7 Boards)
http://www.youtube.com/watch?v=QOFpY1nXFew (Nexus 7 Unboxed the XDA way)
Thanks guys.
I finally got an email back from those guys that do Jtag repairs and he said it was a hardware issue but I am not sure if he understood my issue.
I do not think taking it apart and unplugging the battery will work here if the bootloader is corrupt. I am going to try to let the battery go completely dead though and then try to do the volume/power key thing to see if there is any chance.
I do not know much about this but what I read is that if the bootloader is stopped somehow while loading it can become corrupt in some cases and you cannot do anything without it and there is a device specific key involved. That is why only someone with some specific software can fix it. I thought this key as called Jtag but again, I do not know much about this. The Jtag guy said it was hardware.
Man, I have an Hp touchpad that I got years ago. I installed Android on it years ago and have it overclocked it to over 1700mhz and that thing is still going strong. The kids even dropped it and it has a crack in the screen and it still will not die. Here I have a Nexus only a few months old fully stock except for root and unlock and it is dead. Kills me especially after the way I always stand up for the Nexus line. Still loving my Nexus 4 though and it is well over a year old. Oh well, if that one goes like this one I am jumping off a high bridge. :laugh:
Richieboy67 said:
What I have to lose is money. If I RMA it is possible for Google to keep the payment and I'm not about to buy another unit because one fails through nothing I did.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
whoamanwtf said:
I am confused as to why you are so sure what is wrong with it, how do you know the bootloader is corrupt if you claim no wrong doing. Also technically speaking you did do something to begin with, you knew full well that you would be voiding the warranty by rooting and installing a custom recovery. More than likely if kids messing with it actually did end up with it how it is now they probably accepted an OTA and it corrupted the boot, on the LG G2 they have figured out how to delete the FOTA information that it continuously tries to boot from and return normal boot sequence.
But I reiterate you cannot blame this on anyone but yourself right now, being angry with ASUS or the kids will do you no good. You knowingly voided your warranty now it is time to put your nose down and see if you can fix it, there are a lot of resources here to do such.
Click to expand...
Click to collapse
First off, I am not sure what is wrong with it which is why I am posting here. I stated numerous times that I do not know much about this.
And yes, I know this that rooting and unlocking voids the warranty. I also know that it is my fault for doing it but I have been doing it for around 3 years now and have used various roms and kernals in the paqs and have never had an issue. Perhaps it is a hardware issue. I just do not think this issue was caused by me.
In terms of the kids playing with the device. They play games, things like that. The desktop is locked and they have no access to settings or anything. When I said messing with it I just meant playing games though sometimes they open new games and leave the old ones running. I do not know how that would cause this.
There was no ota or update.
I am not sure what you are saying about LG.
And again, I am not angry with Google or Asus. My point was that this issue was most likely not caused due to rooting or unlocking and an ota would not cause a dhsusb issue even if it did go bad.Lets try to remember that nearly everyone here roots, unlockes and installs roms, etc. I have done so as well but not on this device. This one I wanted to keep pretty much vanilla but I wanted to be able to use Titanium back up, etc. And also, I rooted and unlocked months ago when I first got the device and had to root again when the latest version came out which was awhile ago.
In terms of fixing I have not found a solution for this. I do not know if it is a hardware issue or a software issue. That is why I am posting here. I am looking for some information from people who know this stuff. I know nothing but what I have read and so far I have read many different things. I am here to learn.
OK so here is what I meant with the G2..
I had a stock/rooted/TWRP G2 and half asleep accepted an OTA Update, when it does this it downloads the update into a partition that the device checks before booting. Because I had the custom recovery obviously the update failed but it left that code in the boot partition that would now allow me to even get into download mode. See this post here for how it was fixed http://forum.xda-developers.com/showthread.php?t=2582142
I am not sure if this would be the same problem or how to go about fixing it because of the device difference, but maybe it could help? I didn't mean to come off as a ****, just far too many people like to get into their devices and void the warranty then blame everyone else.
It is really not difficult to pull the back cover off and unplug the battery, I suggest doing this it could very well help just be careful not to crack the back while pulling it off, a credit card/ID and a butter knife should do the trick without leaving marks.
No worries. I appreciate the help.
I agree with you totally.
Sent from my Nexus 4 using xda app-developers app
Hello,
Recently my Nexus 7 (2013) battery ran out because I forgot to charge it. Since then, it won't boot back into Android when it's turned on - all I get is the black screen with "Google" written on it. I have searched all over the internet for the past few days, but I'm unable to find a solution. I'm hoping that someone here can help me, because the tablet's warranty has expired and I'm completely out of ideas. Here are the things I've tried or noticed:
I can't boot into Android. The tablet gets stuck on the black screen with "Google" written on it.
I can access the bootloader and interact with the tablet via fastboot.
The bootloader is locked. Trying to unlock it via fastboot oem unlock displays the "Unlock bootloader?" screen on the tablet. After I select "Yes", the command line output on the computer shows the following output, but doesn't get any further:
Code:
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Trying to boot into recovery mode from the bootloader results in the tablet being stuck on that black screen with "Google" written on it.
I have removed the back cover from the tablet and reconnected every exposed connector. I couldn't take the battery out because I don't have the appropriate screwdriver. Doing this changed nothing.
Any help would be sincerely appreciated. At this point I'm worried that it is a hardware issue, but I'd like to exhaust all options before declaring it as such, as it would essentially mean the tablet is going in the garbage bin.
How long did you let it sit at "erasing userdata"?
I don't recall specifically on my N7 but I know when I unlocked the bootloader on my 2013 Moto X it seemed like an eternity, which was mostly because there is no progress indicator, it just said "erasing userdata" and sat there for a while. Probably like 5-10 minutes.
fury683 said:
How long did you let it sit at "erasing userdata"?
Click to expand...
Click to collapse
It'll be around 2 hours now.
Wengard said:
It'll be around 2 hours now.
Click to expand...
Click to collapse
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
fury683 said:
Well that is surely too long. Not sure what else to suggest. Someone else with more experience might able to help.. It sounds like your partitions may have been messed up somehow, which I have seen others post about recently with the updates. I'm not sure what causes this or if there are any fixes, but I know there are threads about people being stuck on the Google screen and having issues after the update to 5.0/.1/.2.
Click to expand...
Click to collapse
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
mo123456789 said:
Hi,
i had exactly the same problem. I tried everything to fix it and no luck. I had to resort in sending it to Asus for repair. Unfortunately my warranty has expired. I just got a quote from them saying the motherboard has gone and it will cost me £250 to repair!!!!! I almost fell off my chair. A brand new 32gb tablet will cost be around £180. This is surely a joke? I will be giving them a call tomorrow to complain!
I hope yours is still under warranty because it is most likely your motherboard that has gone. I've read a few others having the same issue and its been the motherboard.
Mo
Click to expand...
Click to collapse
Thank you for your response.
I'm sorry to hear about what happened to you. I've been reading around and guessed it's probably a hardware problem based on other people's similar experiences. Unfortunately my tablet is out of warranty as well, and I'm definitely not going to spend more on the repairs than I would on a brand new tablet. I regret purchasing the tablet in the first place, I really expected it to last longer than a year.
If you can, please let me know what ASUS says about this, if you intend to call them. They don't have a subsidiary in my country, but if you get lucky, I might press my chances as well and perhaps I can get this repaired for a reasonable price.
Mine has lasted 5 years more but my Nexus 7 has ended its days the same way as yours. Stuck at google when switched on, and stuck at bootloader when triying to flash it.
Time to go, it seems.
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Since this is apparently a defective hardware issue, they shouldn't care. My first HTC 10 was broken (vibration didn't work), and it took me 6 weeks of going back and forth with them to get it replaced and it was completely unmodified. I would say you shouldn't have any issues getting a replacement, because only the software was modified, and you returned that to complete stock, then the issue with the screen spot occurred.
I agree, just returning it to stock should be enough. From what I remember they don't specifically say that unlocking the bootloader completely voids the warranty even for hardwaee issues.
I say send it in and let them replace the screen.
taker714 said:
Hi! So, a couple of months ago I bought the HTC 10, and it's safe to say that I love the phone, the only thing I wasn't a big fan of was Sense OS, so I decided to fire up Lineage OS into the phone and lo and behold, the perfect phone was born. It was beautiful, and the customization I could do was on another level, not to mention performance. Until I decided to tinker a bit with the phone's look and then the problems started.
I was prompted to update my OS which I gladly do every week, but I hadn't customized the software that much before, so when I flashed the update, I was stuck in bootloop. I flashed the zips that supposedly uninstalled everything I did to the phone and was still stuck in bootloop, did a wipe, still bootloop, it wasn't until I did a complete factory reset when I got my phone back. But then, I saw something.
After booting up, I saw a tiny bright spot under the lower left of the screen, I barely noticed it, but it was there. I decided to go back to stock, and it was still there. Looked into the problem and apparently it's a hardware issue. Called HTC and they told me that they could come for the phone on Tuesday, but the thing is, my phone's status is "modified" I try to lock the phone again and it changed from "unlocked" to "relocked", I'm afraid that these guys might have something to say about that and they'll give me back my phone with no repair at all...
So, what do you guys think? Do HTC care if the phone was unlocked and rooted once before, or that the software status is modified? How can I change those things? Is it really worth it to send my phone for repair? (the spot is really small and not that noticeable, but I'm scared it might get bigger over time)
Sorry for the lengthy post, hopefully you understand. Thanks in advance!
Click to expand...
Click to collapse
If your that worried about it, doing a ruu to get completely back to stock should fix the modified message
First of all, I want to thank everyone who answered this post, really appreciate your opinions.
So, quick update, after I sent my phone, literally got a call the next day telling me that the software was modified and it breached HTC's guarantee. So unfortunately it's a thing... I'm probably going to ignore the issue with the screen since for now it's not that big of a deal, but I have a feeling that I'll have to buy a screen replacement and try and replace it myself down the line. Kinda bummed, always been a Nexus guy but loved and admired HTC's phone designs and quality, so when my Nexus 5 died earlier this year (After three years of abuse, Android bless his soul), I thought that it was time to get "HTC's comeback phone", since the Pixel was so expensive and hard to get. Not saying I regret buying the 10, still is a joy to hold and use, and in my opinion, a lot more better looking and manageable than the HTC U11, but still, had my expectations just a tiny bit higher... I guess that's what you get when you try out new ROMs haha.
Thanks again to everyone who responded this post, hopefully this helped someone.
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
johnnyman25 said:
So even you return your htc 10 back to stock and relock bootloader phone is not under warranty?Wtf?
Click to expand...
Click to collapse
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
taker714 said:
Ikr? The thing is that even if you flash with RUU and lock the phone, the system doesn't change to a "locked" status again, but it changes to a "relocked" status... And while it's that way, the system will appear modified in the bootloader. And any modification to software goes against HTC's guarantee because they basically blame your hardware issue on you tinkering with the software. Pretty funny if you ask me, but oh well xd
Click to expand...
Click to collapse
But I read the htc accepts phones with stock software and relocked bootloader. It's a lie?
HTC 10 Matte Black Power
I mean, it probably depends who takes the phone and how they check for faults... Maybe I was flat out unlucky
Okay, I guess it's been a while since I played with flashing ROMs etc, but I didn't know this was possible. I just flashed Colt OS on my Pixel 2 XL, everything was going fine. I've been having issues with a few apps not allowing me to proceed because the bootloader is unlocked/phone is rooted. So I figured I would lock the bootloader to see if I could get around it. Rebooted to fastboot, did "fastboot flashing lock" and followed the onscreen prompt.
Phone rebooted: Cannot find a valid OS. Device will not start.
Ah crap. Booted back into fastboot, assuming I'd just unlock it and if needed wipe the phone. However, when I type "fastboot flashing unlock" I get the heart-stopping message:
Code:
FAILED (remote: Flashing Unlock is not allowed
)
Finished. Total time: 0.006s
Trying to boot into twrp using "fastboot boot twrp.img" results in
Code:
Downloading 'boot.img'
OKAY [ 1.659s]
booting
FAILED (remote: Can not boot in Lock State)
Finished. Total time: 1.751s
I've unlocked it before with no issues. Why is it suddenly doing this? I can't get into recovery, I can't boot the device, it's effectively bricked until I can figure out how to solve this. Other fastboot commands work fine, as far as I can tell. I have this huge lump in my stomach right now because I *thought* I was experienced enough to not brick my phone. I don't know how I could have forseen this, though.
Any and all help is appreciated. The "fastboot getvar all" returns this, which I've put in a pastebin: https://pastebin.com/NzwfE67T
I'm on the verge of really panicking here. There must be a way to unlock it, I can't imagine why this would even happen. I am literally sick to my stomach right now, reading that other people had to RMA. I bought this phone used about a year ago, no way it's under warranty and I doubt Google will replace it. I cannot go without a phone, I'm seriously freaking the **** out.
Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.
Sigh...
Sent from my Pixel 2 XL using XDA Labs
ilal2ielli said:
Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.
Click to expand...
Click to collapse
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!
AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Can you get Google to RMA it?
Az Biker said:
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!
Click to expand...
Click to collapse
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.
AirCombat said:
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.
Click to expand...
Click to collapse
If your phone was bought from Google it will still be under warranty. I'm not sure if that warranty transfers when it is bought from a third party though. There website does state that the warranty applies to the US and Canada. Here is the link. https://support.google.com/store/answer/6160400?hl=en&ref_topic=3244667
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!