Wrong PIN - Pixel C Q&A, Help & Troubleshooting

Pixel C now states wrong pin!
Nothing has changed to my knowledge, worked one evening and six hrs later Wrong Pin appears after trying to bring up the tablet.
Any ideas?

Related

[Q] screen on my tilt 2 froozed

MY touchscreen has become unresponsive. I now how to flash on my tilt but my tilt 2 I have never tried anything on it. It was working fine days ago, they key board still works its just the touch screen. Would flashing a differnt rom would help?
You can certainly try, but I seriously doubt it. Most of the time this is a hardware issue.
Have you put a new screen protector on recently? Is there anything stuck between the screen and bezel? Some have said sliding something thin along the side of the screen has helped - just be very careful, as you could damage the phone even more if you press too hard!
Thanks , the only thing i did that was different was I put in a password. but I don't think that could do it. I done so much with my tilt 1 never did anything to this phone . Don't know how to flash on this one.
Valencia123 said:
Thanks , the only thing i did that was different was I put in a password. but I don't think that could do it. I done so much with my tilt 1 never did anything to this phone . Don't know how to flash on this one.
Click to expand...
Click to collapse
Might want to start on this section then...
http://forum.xda-developers.com/forumdisplay.php?f=490
Read, read read read read...
Thanks so much for tellng me where to start. Like I said before with my tilt 1 I flashed but when i got this tilt2 i did nothing to it just put it where I had to put a password in to get to use it and it was working well untill 3 days it just froozed I tried to hook it up to my computer, try to save my pictures and things but when I tried to do with the computer it told me to enter my password but it did not show me a box where I could type in my password. I remember this site so i thought maybe I could learn how to flash my tilt2 thinking it will might help. but again thank you I will get to reading lol

Enter PIN/password to Decrypt???

Hi everyone. I know that there are several posts about this issue, but I believe mine is unique on its own...
First off, I bought my G3 with the 2 year plan at T-Booth (like Best Buy Mobile) in Ontario, Canada, with Rogers Wireless as the provider. It is not stolen as some people pointed out in other threads.
I was using my phone casually, then closed my QuickCircle cover lid, and put it in my bag as I always do. After I drove home and pulled my phone out, I had this blank screen that read, "Enter PIN/password to decrypt", "30/30 attempts remaining", and with an input box where I can type in my password. After this screen stays on for too long, it starts making clicking sounds.
I have NEVER encrypted my device. I didn't even know about this feature until this happened tonight. I tried all the pw/pin I usually use and it doesn't work. I tried a hard factory reset and it still shows up with the same screen. I also have never unlocked/rooted/flashed my device. It's only been 3 weeks since I got this phone, and while I love my G3, this is really disappointing. I have no idea how and why my phone suddenly decided to lock itself, especially when it was just sitting in my bag.
If there are any solutions (other than taking it to a Rogers store and sending it in for a repair), I would really appreciate it. Thanks in advance.

Bricked Cubot X15... seeking fix (?)

Hi all,
I bought a Cubot X15 as a gift for my wife. She used it for a few days without a SIM card (just WiFi) and when we put a SIM card on it the phone thought it was stolen (?) and asked for a pin code we never set up.
I googled around and seemed to me that the only way to unlock it was to flash a new ROM, so I downloaded a ROM I thought it was correct, flashed it following the instructions and the phone seems dead.
The only glimpse of life is when a cable is when the laptop is connected to the phone and I press "down" and "power", the laptop makes the noise that USB is connected and then, around 5 seconds later, sound of USB disconnection... other than that NOTHING.
No other combination of "up", "down" and "power" does anything, no Chinese characters, no noise, no screen... absolutely nothing. And I am 100% sure the battery is almost full.
I would like:
1) Confirmation (as best as you can, with the information given) if I need to get a new phone or
2) Help to resuscitate the Cubot... in fact, I would prefer if I can ship the phone to somewhere in Australia and someone fix it for me (willing to pay if successful).
Thanks in advance
i need answer too, i have the exactly same problem... :crying:

Nexus 5x shut off and won't turn on

If I posted this in the incorrect place or there is something related to my issue, I apologize in advance.
I've been searching here and all over the internet and no progress yet so I decided to make a new account here just to see if anyone can help me because I'm out of ideas right now.
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas. I just want to at least recover some pictures and information I have in it that isn't backed up, if anyone can help me I would greatly appreciate it.
Thanks in advance
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
At this point, I'm willing to try anything. Thanks
driss.sadok said:
Just boot to bootloader (fastboot) then unlock it and flash a factory image... u can find many guides to this operation on the XDA
Click to expand...
Click to collapse
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
PennyScissors said:
If it's a hardware issue like sfhub suggested, I don't think this will fix it.
Click to expand...
Click to collapse
Same here... cannot enter recovery mode, so flashed new rom stock rom.
The flashing was fine but it didn't help.
guys if u can get to the bootloader, sure it can be fixed.. everything is possible with the fastboot, u can fix any issue. if it's a hardware issue the bootloader wouldn't work as well.
Re Nexus 5X won't turn on - I've had same issue
PennyScissors said:
This morning my Nexus 5x (Non-rooted Nougat) woke me up like every morning, after dismissing the alarm I left it on my bed and when I came back to grab it later I noticed it shut off.
Here are the facts and what I have tried so far:
- Battery level was almost full
- I tried to turn it on but nothing happened, not even the Google logo
- Connected it to power and no icons or any response at all
- Left it connected for like an hour and tried to get it into recovery mode
- I was able to get into fastboot mode a few times but after electing "start" or "recovery mode" the Google logo comes up and then shuts off again right after.
- Tried getting into recovery mode after leaving it charging for a while again but I couldn't even get into fastboot this time, no signs of life at all.
- Disconnected the battery for a few minutes and tried to get into fastboot mode again, this time it worked but same thing happened. (Google logo then shuts off)
- Tried connecting it to my PC but doesn't show up on Linux nor Windows, on Windows it makes the sound like I connected a peripheral but that's pretty much it.
- I have USB debugging enable but never accessed my stuff through usb connection because I have had this issue before where it is connected but it won't show up or it shows up but won't let me access the files even though the phone is unlocked.
At this point it just won't do anything and I ran out of ideas...
Click to expand...
Click to collapse
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
danielledowns01 said:
I've had the same problem with my 5X, except my alarm didn't even go off! I woke up 15 minutes late to see the boot screen "enter your pattern to start Android". I entered my pattern and it looked like it was going to boot up but when I went back to it it was blank. Tried again, got to the Google loading dots and it switched off again and I haven't been able to power it up since. No bootloader, nothing. Tried all the troubleshooting steps on the Nexus Google Support pages (I did post a link but because I'm new it won't show, so just Google "Nexus Support") and nothing worked. I also knew the battery was fully charged because it had been on charge overnight and when I did get to the 'enter your pattern' screen, the battery icon in the notification bar was full.
I requested a call back from Google and nothing happened so I tried the chat and they said it sounded like a hardware issue and are sending me a replacement device within the next 3-5 working days. Good that they're replacing it. Bad that it happened on a device less than a year old and they only offered £10 Play Store credit by way of compensation, when I've had to spend £15+ on a PAYG sim card to use in my old phone in the meantime because the nano sim in my 5X was too small and I've spent over an hour and half this afternoon wasting my time with troubleshooting and waiting for a call back... Not really the customer service I expected from Google for what appears to be a hardware issue. If you bought the phone from Google, my advice would be to get in touch with Google Support and they should replace it under warranty.
Click to expand...
Click to collapse
I contacted Google and they didn't help me at all because my warranty expired last month, they literally just told me to put in a repair request at the LG repair webpage....this sucks
My experience exactly...
My wife's Nexus 5 exhibited the exact same symptoms this morning. It's been running perfectly for 20 months and today it died, and we're unable to even get into the bootloader screen or power on the phone.
Taking your advice, we put it in the freezer for 15 minutes and were able to perform a factory reset wiping all data from the phone. We are going to take advantage of Google's Christmas 2017 promotion and return the Nexus 5X and buy a Moto 4X. They require you perform a factory reset before returning the phone in order to receive a credit for the returned Nexus 5. Thank you so much for the help!
Dennis
sfhub said:
It sounds like you might have encountered the hardware bootloop issue. This is theorized to be caused by bad solder for the eMMC chip or bad eMMC chip. This was an acknowledge problem on a related model LG phone, but hasn't been acknowledged for N5x.
If you are under warranty, you should start the replacement process before it runs out.
If you want to try something that sounds crazy but has worked for some people, put the phone in the freezer for 15 minutes then see if it boots. If it does, quickly back up as much data as you can, then wipe the phone in preparation to RMA exchange.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-5x/help/help-nexus-5x-lg-off-to-t3729739
I've just posted this thread overlooking yours. I think this is becoming another common issue. Has the freezer trick worked with anybody else?
I am having the same issue described here. My Nexus 5x went into a Bootloop about one month ago, but I was able to get it working again by going into Recovery Mode. About 4 days ago it went into a constant Bootloop, just showing the Google screen, and I couldnt get back in to recovery mode. I ordered a new phone on Tuesday (Pixel 2) and as long as I am able to do a factory reset I should get a $150 credit when I send this phone back. So, in desperation, I took a chance on the 15 minute freezer trick, and it worked! I was able to get into recovery mode (power + volume down, select Recovery Mode, little dude on his back came up, pushed power + volume up once) and cleared the cache and applied the factory reset. Ridiculous that this phone only lasted 18 months, but if I get the $150 credit I will be happy.
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
d_ckhole said:
Same problem here -- just froze for a few seconds, powered off, and won't turn back on. Not a boot loop issue as there is no response at all from any buttons. Swapping the mainboard from a working phone powered up without a problem, but obviously that's the other phone's emmc.
I tried the freezer thing and it sort of worked- LCD powered on for a couple seconds, but then shut back off again and even that only happened once. That's progress over the usual absolutely no response though... Anyone have insight into why the temperature would matter? something is overheating that this gives a bit of wiggle room since it starts much colder than usual? maybe a more complex analog electronic situation?
I would happily pull the flash chip off and put it in a emmc reader, but I think I'm out of luck because from what I've read the dm-crypt key is generated from some data stored in in the processor's trust zone thing. I know the "password" but if that's only part of what makes the key and the rest isn't on the flash chip I suppose there's no point in going that route.
I don't care about the hardware surviving; mostly just looking to recover my data. Anyone have suggestions? Hardware debugging direction? I'm willing to buy some electronics test equipment (within reason of course; not picking up a 10000USD rework station for some old photos and contact list...)
Click to expand...
Click to collapse
The only way to connect that buddy to PC is to get SoC (CPU) working, so theoretically you can go towards reballing the chip. But I guess it's not an easy thing for such a little chip. Also u will need kinda plate for balls, i think there are no common ones, so u can make it yourself if have a technical education.
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
orcgoblinsupply said:
Another way is to connect memory right to PC without a phone but with some connector. IDK if there are any available, but this looks much more simple. I actually got the same happened, and tried to heat the plate, but with particular success.
IMHO
Click to expand...
Click to collapse
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
d_ckhole said:
Here's the reader
https://www.amazon.com/ALLSOCKET-eMMC169-Programmer-Kingston-Interface/dp/B06Y55DKND/
But I assume the problem is I will not be able to generate the encryption key because part of it is in the processor.
If someone has tried this and it definitely works, I'll give it a go. Just don't want to buy the emmc reader and heat gun this chip off if it's certainly a waste of time.
Click to expand...
Click to collapse
I've seen a post of a guy who sent his motherboard to china and got reballed it and gained 4gb of ram. Can be wrong, but it was around $50 and a month of time.
---------- Post added at 04:46 PM ---------- Previous post was at 04:40 PM ----------
Actually found the post itself: https://4pda.ru/forum/index.php?showtopic=722679&st=3440#entry68093395 (it's in russian, so u're welcome at translate.google.com) In short - a guy fount a Chinese service and men in the middle who could resend his motherboard to china, it cost him $100

Finally left Windows Phone for Pixel... which let me down a month later.

Keeping this concise. Background:
I've been using Windows Phone devices for 8 years. My original 8yr old Samsung Focus is still kicking.
I figured it was about time to jump to Android and picked up a "used for 3 months" Pixel XL. Originally purchased from the Google Store. (purchaser forwarded his receipt).
Bought first week of November, didn't use for a month as I didn't have a case, then used on WiFi but didn't have a sim in it until December 20th or so.
It had been running great. Now that I think of it, it had shut off twice from ~30% battery but in extreme cold. Thought it was cold related.
Two nights ago I set it down to go to sleep. I woke up, it did not.
At first I thought the screen died. I would get the odd vibration when long-pressing power for example, but never anything on the screen. The power + vol brought up the quickboot/recovery but:
"start" results in a blank screen
""restart bootloader" goes to blank screen
"Recovery mode" flashes a white screen with the Google logo for half a second then blank screen
"Barcodes" displays barcodes
I recently picked up a USB C > USB 3 cable and plugged it into my Win10 PC. It showed "Android Device Ready" but I expected to see some removable drive show up (dunno, had never hooked it up to my PC before to know what the usual behaviour should be).
Today, when trying to start it again it flashed the battery/charge icon for half a second, then blank screen.
I had a chat with a Google support agent who got me to try a remote erase which, I'm guessing, hasn't been received by my phone.
So my Android experience thus far has been: spending more than I've ever spent on a phone for a device that I accessed wifi on for a few weeks, then started to set up as my daily driver for a few weeks, just in time for it to seemingly die. Oh yeah, and of course, it's out of warranty. This world is new to me. Google's suggestion was to send it in to a partner for repairs (who knows how much that will cost). I'm hoping there's something else I can try before resorting to that.
Originally I was hoping to get some data off it. I'm not familiar with what Google backs up within Android (I had those settings checked, but no third party backup apps). I guess my photos should be backed up which would have been the biggest thing. Now I'd just like to recover the device without having to spend more money!
Oh, previous owner had Oreo 8.1 on it.
Any guidance would be most appreciated. Back to my trusty 5+ yr old Lumia 1020 in the interim!
tyyan said:
Keeping this concise. Background:
I've been using Windows Phone devices for 8 years. My original 8yr old Samsung Focus is still kicking.
I figured it was about time to jump to Android and picked up a "used for 3 months" Pixel XL. Originally purchased from the Google Store. (purchaser forwarded his receipt).
Bought first week of November, didn't use for a month as I didn't have a case, then used on WiFi but didn't have a sim in it until December 20th or so.
It had been running great. Now that I think of it, it had shut off twice from ~30% battery but in extreme cold. Thought it was cold related.
Two nights ago I set it down to go to sleep. I woke up, it did not.
At first I thought the screen died. I would get the odd vibration when long-pressing power for example, but never anything on the screen. The power + vol brought up the quickboot/recovery but:
"start" results in a blank screen
""restart bootloader" goes to blank screen
"Recovery mode" flashes a white screen with the Google logo for half a second then blank screen
"Barcodes" displays barcodes
I recently picked up a USB C > USB 3 cable and plugged it into my Win10 PC. It showed "Android Device Ready" but I expected to see some removable drive show up (dunno, had never hooked it up to my PC before to know what the usual behaviour should be).
Today, when trying to start it again it flashed the battery/charge icon for half a second, then blank screen.
I had a chat with a Google support agent who got me to try a remote erase which, I'm guessing, hasn't been received by my phone.
So my Android experience thus far has been: spending more than I've ever spent on a phone for a device that I accessed wifi on for a few weeks, then started to set up as my daily driver for a few weeks, just in time for it to seemingly die. Oh yeah, and of course, it's out of warranty. This world is new to me. Google's suggestion was to send it in to a partner for repairs (who knows how much that will cost). I'm hoping there's something else I can try before resorting to that.
Originally I was hoping to get some data off it. I'm not familiar with what Google backs up within Android (I had those settings checked, but no third party backup apps). I guess my photos should be backed up which would have been the biggest thing. Now I'd just like to recover the device without having to spend more money!
Oh, previous owner had Oreo 8.1 on it.
Any guidance would be most appreciated. Back to my trusty 5+ yr old Lumia 1020 in the interim!
Click to expand...
Click to collapse
Factory reset.
Sounds like a hardware problem. Most likely a motherboard issue. Try flashing the official 8.0 factory image first though.

Categories

Resources