Develop Bugs

How to enter network unlock code on HTC via cable?

I have a HTC Hermes 200 that says something like "you have 5 attempts left. Wait for time out".
Underneith there's a place to enter the network unlock code (i got the code from my carrier), but the OK button is disabled.
So i was thinking it's like Motorola where you'll have to leave the phone on with that message some hours before it will be possible to enter the code again. But i've waited for several days with that screen on, but the OK button is still disabled. Probably a bug?
Anyway, does anyone know if there's any way to unlock it using cable? Via telnet AT commands or something like that? It's possible on most other phones...

same problem here,i am also searching for some other method to enter the codes.

Actually, this problem was solved for me. I've had the phone on for about 2 days when i last checked the screen. Then next time i checked (about 4 days later) the phone was dead because battery ran out.
But after i charged it for about 2 hours, timeout was suddenly over and i could enter the code. So it looks like that time out is just some insane amount of time.

Unlocking Bootloader

So, I had the 2012 version and did it no problem using the Toolkit, I tried using the Unified Nexus Toolkit again and all worked well as far as installling drivers and them being recognized and yada yada.
Point is, when i get to the screen with the warranty warning and the option to select no don't unlock or yes, unlock....i select yes and it just freezes and hangs there...am i supposed to wait for a long time or is it supposed to be instantaneous like I imagine it being?
What am i doing wrong and what can i do to fix this, i searched google and keep coming up with methods of how to unlock and all that but that's not the problem....I have tried two other programs or toolkits what have you, still no success because the issue is when selecting yes and the tablet hangs

ahjee said:
So, I had the 2012 version and did it no problem using the Toolkit, I tried using the Unified Nexus Toolkit again and all worked well as far as installling drivers and them being recognized and yada yada.
Point is, when i get to the screen with the warranty warning and the option to select no don't unlock or yes, unlock....i select yes and it just freezes and hangs there...am i supposed to wait for a long time or is it supposed to be instantaneous like I imagine it being?
What am i doing wrong and what can i do to fix this, i searched google and keep coming up with methods of how to unlock and all that but that's not the problem....I have tried two other programs or toolkits what have you, still no success because the issue is when selecting yes and the tablet hangs
Click to expand...
Click to collapse
How long is it sitting there after you select unlock? I remember when I unlocked mine, it took abnormally long. It sat at "erasing data" for what felt like an eternity. In reality, it was probably like 5-10 minutes.

charesa39 said:
How long is it sitting there after you select unlock? I remember when I unlocked mine, it took abnormally long. It sat at "erasing data" for what felt like an eternity. In reality, it was probably like 5-10 minutes.
Click to expand...
Click to collapse
i waited about 3-4 minutes, but it just hangs on the selection screen highlighted on yes

ahjee said:
i waited about 3-4 minutes, but it just hangs on the selection screen highlighted on yes
Click to expand...
Click to collapse
If I remember correctly, mine hung there first for a bit as well. I would give it like 15-30 minutes or so just to make sure there's an actual issue.

Hi Guys,
Just a point as it happened to me all morning and I was getting frustrated, check that you're not using a usb 3.0 port.
When I switched to usb 1.0, it worked perfectly.
Also, just in case, I made sure I used the cable given by asus.
Good luck hope that works for you as it did for me.

so i did get the bootloader unlocked an ungodly amount of time...literally sat there for about 30 minutes but maybe because it was erasing the games i have cause i have GTA San Andreas and GTA 3 and a handful of other games, some big some small and mad other apps so i am assuming the wipe took some time but now i can't seem to get it to install TWRP...i think i have to reinstall drivers, I know i can get things working at this point once i get the time.
Thanks guys.

Pixel not waking up from sleep

Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc

I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...

I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.

Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).

Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk

I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.

buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.

still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.

Joined beta N program, hopefully this issue is resolved on the Pixel C.

note 2 not waking up sometimes

hi folks
my note 2 doesn't wake up sometimes. it still shows notification LEDs during its sleep, but cannot wake up unless I take the battery out and put it back in. I experienced this on Friday and Sunday, but not on Saturday in between..
I tried the battery on my wife's Note 2, and no problem there...
I tried a different custom ROM, but experienced it there as well.
Is this a hardware issue, or could going back to stock rom solve this? Or is there another way?
Help please!

same issues on mine, the alarms didn't go off this morning because it wouldn't wake up. tried linage and nuclear roms. I just came on to find an answer!
It takes 10 seconds to unlock at the best of times (black screen until then)

Hey, thanks for your answer, but what do you mean
turnah said:
It takes 10 seconds to unlock at the best of times (black screen until then)
Click to expand...
Click to collapse
- did you manage to unlock from the black screen WITHOUT taking out the battery?
Do I just have to wait for it to wake up? But calls are not received and alarms do not sound while it is sleeping.... right?

omermaras said:
Hey, thanks for your answer, but what do you mean - did you manage to unlock from the black screen WITHOUT taking out the battery?
Do I just have to wait for it to wake up? But calls are not received and alarms do not sound while it is sleeping.... right?
Click to expand...
Click to collapse
I heard a call come in but the screen didn't wake up to answer the other day, 8/10 times it eventually unlocks after frantic clicking of the home and on buttons but the only answer is to take the battery out if that doesn't work. Its at least once or. twice a day I end up removing the battery.
Would be great if someone knew of a rom to get around this. initially they work great but get slower after a few hours.

Phone is starting....

I have my phone connected to my watch and utilizing smart lock so I dont need to do pattern or fingerprint unlock. However every morning I need to do pattern unlock and phone will say "Phone is initializing" as if I restarted the phone. Is this normal now on these phones?
Sent from my SM-N975U1 using Tapatalk

Have you set up scheduled reboots in device care by chance? Mine did that this morning but I have it set to restart overnight on Friday mornings.

VeriSkye said:
Have you set up scheduled reboots in device care by chance? Mine did that this morning but I have it set to restart overnight on Friday mornings.
Click to expand...
Click to collapse
Thanks. Weird it was set to reboot on Fridays. I never set that. Wonder if that's a default. And I swear yesterday morning I also had do pattern unlock. Maybe I'm trippin. Anyways, I will keep an eye out tomorrow. And I have changed it to reboot on Sundays.

I know I use to use this with devices and if you didn't use the phone for X amount of hours the phone would lock and require a pin/fingerprint, but that was back when I had the pixel, I stopped using it seemed to make me have to put my pin every time I wanted to use google pay instead of just unlocking my phone and paying.

I get that message when rebooting too. I came from a Pixel 3 and it didn't have that when restarting. Not sure if this is a Samsung thing but it makes startup a bit slow comparatively

bupac said:
I get that message when rebooting too. I came from a Pixel 3 and it didn't have that when restarting. Not sure if this is a Samsung thing but it makes startup a bit slow comparatively
Click to expand...
Click to collapse
it's seemingly to do with Knox and the encryption, seems it is to stop people connecting to the locked phone and extracting data in start up.

If you're referring to the message that says phone is starting after you unlock it you can get rid of that by turning this off.