Database Develop

[Q] Pattern lock -> Too many tries

I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?

Do a hard reset / wipe. That's my suggestion.

Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .

I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.

Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?

I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it

So what happens when you power on?

Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.

Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App

okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.

After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.

Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.

PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))

All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App

Can't enable USB debugging when phone can't be turned on at all.

danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.

danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem

danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )

What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse

distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....

Stuck at padlock screen then reboots into recovery

i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.

prelude91sit said:
i have a note 3 that is boots up to the unlocked padlock screen gets stuck there then boots into recovery mode. it even gets stuck in like a bsod mode where i cant see nothing or get it to respond to buttons. the only way I can is if i open it up and disconnect all ribbons(havent tried pinning pointing one yet) after i do that and reconnect them i can get the phone in download mode or recovery mode. i tried the restore with title wifi fix. to no avail. the only thing i know about this phone is supposedly it was working then they guy tried to do the update since then stuck. he said he sent it to samsung and they wouldnt fix it because it supposedly had a custom rom flashed. which im sure it had something done because of the unlock padlock/bootloader sign. any help would be greatly appreciated.
Click to expand...
Click to collapse
Dear Brother !!
This same thing happened to me!!
I looked everywhere for an easy solution BUT THERE IS NONE !! Yet.
The reason why is because there are no easy "Odin back to stock files" yet is because at&t is a fn a-hole and locked the bootloader !!
I brikt my shıt about 4 days after I brought it home from costco.
I combed through the interwebs for the 48 hrs straight like a mad tweaker!! because of course this is our 800 dollar babies we're talking about !!
I kept getting the same error message as you are mentioning about the kies update connect your pc blah and so I tool it back to costco and played dumb and said that I got a notification to update and clicked ok and it did some stuff and "now its stuck on this screen with some error??" .. the lady at the kiosk looked it up and down and said someone else had come in last week with the same error message . LoL !!
I walked out of there with a brand new baby !!
Maybe you can do the same thing? Just hoping you are within your return timeframe.
your last but definitely not last worst case scenerio option is to stick your sim card in another phone and wait till someone from our awesome family here finds away around/through that damn bootloader and drops the beautiful Odin+files to give new birth to your 5.7 beast of an angel !!
Hope this helped in any sort of way. Good luck dear Brother!!
Please let us know how it goes. I think there are many brothers on here in the same predicament.

[Q] Why does My HTC One M7 Turns Off After Factory Reset?

Hey guys. I'm planning on selling my HTC One M7 since I recently upgraded. I did a full data reset to bring it back to how it was out of the box. I then SIM unlocked it with my unlock code and currently don't have a SIM sitting in it.
When you turn it on it'll bring up the Get Started/Emergency screen so you can begin to set up your new phone. Everything looked good, so I let the screen timeout. A little while later I come back and find the phone turned off on it's own. I power it back on and see it still has a lot of battery left. I leave it alone again and about 2 hours later I find it turned off again.
Is something wrong with the phone? It was working great up until I did the reset and now this happens. Or is it maybe some sort of power mode thing that shuts it off on it's own after a while since it hasn't been set up yet. I've tried to Google for answers, but come up with nothing.
Help! Thanks!

thegreatmikesby said:
Or is it maybe some sort of power mode thing that shuts it off on it's own after a while since it hasn't been set up yet. I've tried to Google for answers, but come up with nothing.
Click to expand...
Click to collapse
probably, only way to know is to go trough the setup and see if it reboot again, then you could factory reset the phone again.

alray said:
probably, only way to know is to go trough the setup and see if it reboot again, then you could factory reset the phone again.
Click to expand...
Click to collapse
Thanks. That did the trick. Once the phone was setup, no more problem. I guess it must be a power saving thing while still in fresh out of box mode.

No Sim detected, No Wifi

A few hours ago my phone lost signal, I thought nothing of it at first as there is a dead spot close to my home.
Now I noticed the WIFI is also not working, and I cant switch it on, the toggle just jumps back to off.
I reset the phone, removed and changed sims, and did a factory reset. Nothing fixed it.
The phone wasn't dropped or anything.
Any ideas?

Cyclone101 said:
A few hours ago my phone lost signal, I thought nothing of it at first as there is a dead spot close to my home.
Now I noticed the WIFI is also not working, and I cant switch it on, the toggle just jumps back to off.
I reset the phone, removed and changed sims, and did a factory reset. Nothing fixed it.
The phone wasn't dropped or anything.
Any ideas?
Click to expand...
Click to collapse
And now I cant set it up again because I cant connect to wifi
If I hold power+ up I get a message saying "no Command" but I cant do anything.

Did you try the test mode : *#*#4636#*#*
to test some functions ?

cyrillem28410 said:
Did you try the test mode : *#*#4636#*#*
to test some functions ?
Click to expand...
Click to collapse
No, I cant get past the setup screen after the reset, as I cant connect to anything.
I think the only way to fix it is to flash it somehow. I guess the radio is part of the kernel, does anyone know where I can get the stock kernel to flash?

Why don't use the warranty ?

I bought it off gearbest, so think the warranty is going to take a long time.
But maybe it is the best option. I'll at least find out what the procedure is.
Sent from my SM-G903M using Tapatalk

I'm not sure but maybe you can ask to gearbest and to xiaomi directly in your country before any other modifications on your phone

Same here straight out of the box in Sweden global version ?

It usually is a kernel problem. Flash trough fastboot the rom if you can and see if it fixed.

Maybe your persist pertition got corrupted you have to flash it manually. Or if you have warranty then just claim it.

I'm having the same issue :/ Any update on this topic?

Samsung Galaxy A71 died after updating to Android 11

Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.

You probably done it.But have you plugged it into A computer to see if the computer can detected it?

Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.

BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.

Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.

I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!

BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?