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....

Phone "works" but need help to re-stock it.

So my phone technically works but everything force closes the second I get into the OS so its basically inoperable.
I know exactly what caused the issue, I was rooted and I saw a service that an app called myscript had installed, even after I had un-installed the app itself. I figured I'd kill it, and it caused my phone to have pen input seizures every three seconds. Reinstalling the app, and factory resetting did not help. I have tried to recover the phone but all my efforts have failed thus far (including kies 3 emergency firmware recovery).
Reference for my original problem:
http://forum.xda-developers.com/showthread.php?t=2469681
So I need to get back to stock by following this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
but I can't get past the "detect phone" step. Heimdall keeps crashing despite having correctly installed the drivers. I made a post in that thread but I doubt that will garner any help at all, so I figured I'd make a thread begging for help. I've had this phone a scant few days! Please help!
Any other known method of getting back to stock would be acceptable as well.
-Luceid

Luceid said:
So my phone technically works but everything force closes the second I get into the OS so its basically inoperable.
I know exactly what caused the issue, I was rooted and I saw a service that an app called myscript had installed, even after I had un-installed the app itself. I figured I'd kill it, and it caused my phone to have pen input seizures every three seconds. Reinstalling the app, and factory resetting did not help. I have tried to recover the phone but all my efforts have failed thus far (including kies 3 emergency firmware recovery).
Reference for my original problem:
http://forum.xda-developers.com/showthread.php?t=2469681
So I need to get back to stock by following this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
but I can't get past the "detect phone" step. Heimdall keeps crashing despite having correctly installed the drivers. I made a post in that thread but I doubt that will garner any help at all, so I figured I'd make a thread begging for help. I've had this phone a scant few days! Please help!
Any other known method of getting back to stock would be acceptable as well.
-Luceid
Click to expand...
Click to collapse
I read about another guy who just did the same thing, but all is not lost.
He sold his N3 on the interweb for "parts" last Monday and got $110 and his deductible was $200 so it only cost him $90 to get a new one, so don't fret.

XiphoneUzer said:
I read about another guy who just did the same thing, but all is not lost.
He sold his N3 on the interweb for "parts" last Monday and got $110 and his deductible was $200 so it only cost him $90 to get a new one, so don't fret.
Click to expand...
Click to collapse
Eh I'd rather just get my "like new" replacement for free. Everything is still official and knox is 0x0. Still I'd prefer to fix this is anyone knows how.

No Screen after rooting and regional unlock

Hi Guys. I got my note 3 recently (4 days ago).
Anyway i did my research here in the forum to root it and to use chain fire regional unlock. My note 3 came with 4.3 and mj5. I used Kingo App and later i used "regional lock away" because i'm in DR. The regional lock, i think it didn't work because i was getting sim unlock code and then i waited 60 sec as the instructions said and i restarted the phone. And i got the message again but i didn't care because it was too late. I did this at midnight.
So i decide to use the phone but then i was so tired that i prefer to stop and do it at morning so i put the cellphone on the table and i went to sleep. Today i woke up to check the phone and i can hear everything but the screen is not working is all black. I don't know what happened i need some help. I don't know if i brick the phone because it was working so good yesterday. It came with s view case i don't know if is original but it was working really nice with it just to add some information .
i tried pulling of the battery, wait a long time and nothing the screen is just black. I would think the lcd is broken. But it didn't fall and it was working yesterday so i don't get it.
Now i check with kingo app in my pc and it says it's not rooted the phone. wth?. Do you think the rooting process mess up my phone or the regional lock away?

D415 won't turn on

I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.

rft2149 said:
I use ClockworkMod's RecoveryInstaller, ran the .apk, installed it then opened it. There was a large button labeled "flash recovery" and when I pressed it, the phone turned off and won't turn on.
I plugged the phone into my computer and it continuously plays the "plugged in" sound. If I hold down the volume down and the power button, the "plugged in" sound plays more often and has another sound playing right after it, but the phone won't turn on.
I haven't unlocked my bootloader, but I have rooted the phone.
I believe it is in a boot loop or something, because the "plugged in" sound keeps repeating itself, or something like that.
I have an SD card if that is required in fixing the device.
I can't boot into recovery at all, screen keeps black.
Click to expand...
Click to collapse
Try this

SubliemeSiem said:
Try this
Click to expand...
Click to collapse
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.

rft2149 said:
I've been trying that, but I can't access my IMEI to get a KDZ file, and I've tried my IMEI on that thread before, and I didn't get any download. I've gotten an IMEI for my model from another thread, but that thread you sent me needs for my phone to connect to my computer, which it can't.
Click to expand...
Click to collapse
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.

SubliemeSiem said:
Right, you already said that, sorry. In that case I'm afraid there's nothing else you can do, that phone is dead.. I do believe other users who had this kind of problem had to rely on the warranty to get a new phone, so you should go back to the store. And from now on, don't use one-click solutions to do this kind of stuff, the process isn't that hard and there is less risk involved when you just follow a step-by-step guide.
Click to expand...
Click to collapse
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.

rft2149 said:
I am sending this phone in for a warranty repair. But since I rooted the phone, will they accept it? Keep in mind, I have rooted it with TowelRoot, but I haven't unlocked the bootloader.
Click to expand...
Click to collapse
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!

SubliemeSiem said:
Not sure, in theory they wouldn't have to, since trying to install the bootloader caused your problems in the first place. But I've also heard of other people who did the same kind of thing and could still use the warranty. I just wouldn't tell them how it got bricked, play dumb and say the phone suddenly wouldn't boot up any more Best of luck, mate!
Click to expand...
Click to collapse
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.

rft2149 said:
The main issue I told them, was that it wouldn't boot or turn on. Somehow, battery issues played into it, but I told them that the MAIN issue was that it wouldn't turn on. I don't think they can turn it on if I can't. They have the money and power to try, but I'm pretty sure they're not going to spend a load of time trying to figure it out.
Click to expand...
Click to collapse
They can easily find out is it rooted or not....................?
If u connect ur phone via usb by pressing vol down button..
U'll enter into download mode..
It clearly says ROOTED.........
But instead u have to try to update phone using B2CAppSetup.exe (official software update tool)

I have a lg d415 it just cut off yesterday n won't turn on i have no clue what to do

PLEASE HELP.. Phone Doesnt do anything

i bought a used samsung galaxy s6 (G920T), now i went to my local place and asked the person working there if he could unlocked it for me so i can use any carriers, so he said yes, then after 3-4 hr he called me back and said the phone was ready to pick up so i went ther to pick it up and the phone was working fine until i tried to login the phone booted, so i try turning it on but the phone wont it starts to boot up then on the top screen it says (KERNEL IS NOT SEANDROID ENFORCING, Custom binary blocked by FRP Lock) then automatically turn off, so i went back to the store and give them the phone back so they can fixed but the man working there say that he will charge me for puting a new software in it so i asked him what did he do so he said he unlocked it using an octplus box so i said well i wil take the phone with me and try to do it myself and i went home with the phone and do some research and installed a new firmware (G920TUVU3DOI1) using odin V3.10.7 then it proceed all good but when it finished the phone doesnt come far than the samsung logo screen boot up and it stays there for i think till the battery dies .. and now i dont know what elese to do an i even went back to the store so they can fixed it for me but the call me later saying they couldnt do anything with it please help.. i would put some pictures but since im new the site doesnt let me post other links