Related
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....
Hi All,
Sorry if this info is somewhere already but I just couldn't find it (I think my search string was too long)
I had a Z3 and the power was not working correctly so I got it replaced on the warranty (its works phone) now I had downloaded hundreds of apps and it comes pre loaded with a load of apps.
I was hoping with the replacement to have a bit of a fresh start on the phone and not install all the bull crap apps I did before... but as soon as I am out of the setup of the phone it is already downloading every stupid app I ever downloaded.
is there a way I can stop this, I don't mind factory resetting the phone.
it depends on what version of android you have but there should be an option when you are setting up the phone that says something like "restore from backup." do a factory reset and then uncheck that option.
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Remove your google account before the factory reset??
holeindalip said:
Remove your google account before the factory reset??
Click to expand...
Click to collapse
Will that help?
Won't ask for the previous google account on login from factory reset
holeindalip said:
Won't ask for the previous google account on login from factory reset
Click to expand...
Click to collapse
Really? I'm going to have to try this. Would save a huge headache; I'll report back.
stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
I searched a bit and found this:
http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
If that article is correct, the "chance" isn't something random, it is caused by changing your google account password. So to avoid, don't factory reset within 72 hours after changing your google account password.
http://forum.xda-developers.com/showthread.php?t=3104504
As long as you do a full device wipe before flashing you are fine. I have never had this pop up. Just properly format system, data and both caches then flash. Simple and the only real way to flash a rom.
Tried to disconnect the account, doesn't work.
Matter of fact I did change my google password recently, maybe that's why I can't do ****.
stevew84 said:
Matter of fact I did change my google password recently, maybe that's why I can't do ****.
Click to expand...
Click to collapse
That would be it.
zelendel said:
That would be it.
Click to expand...
Click to collapse
I did that on the 10th, so one more day.
stevew84 said:
I did that on the 10th, so one more day.
Click to expand...
Click to collapse
Nothing to do but wait and see. Mind the swearing. The stars dont prevent infractions. Friendly warning.
stevew84 said:
I know I'm not the only one that experiences this as I've seen other users just accepting that issue.
As some of us know, when we flash from one ROM to another, there is a CHANCE where we'll get the login screen which says "The device has been reset...", which normally is followed by "Please login with the device administrator account", or something along those lines.
I've talked to Google, and I know others have also, and we're told that there is a 72 hour "security" feature that will not allow you to log into a freshly installed device, even though that device is yours and you were just using it 5 minutes prior to flashing the install.
There is no way to bypass this, at least I don't think, and Google doesn't have a way of resetting.
What I'm trying to find out is if someone was able to get around this, or has a work around because holy hell is it annoying.
Click to expand...
Click to collapse
Leave 'OEM unlocking' enabled in developer options. It disables this feature.
It resets every reboot
holeindalip said:
It resets every reboot
Click to expand...
Click to collapse
No, it's a sticky setting that is saved somewhere else. It even survives formatting of the system partition.
On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0
holeindalip said:
On 5.1 it was just a one time use thing and would reset upon it booting the system,must have changed on 6.0
Click to expand...
Click to collapse
i never knew it other as being sticky. Anyway... leaving it enabled disables the "forced" login to the original Google account. I was locked out once before. When that happened i restored a working TWRP backup. Rebooted and enabled 'OEM unlocking' and never had a forced login again (i flash about 2 or 3 times a day). Also... check the popup when you enable "OEM unlocking".
Yeah all device security goes out the window with it left on
I got bitten by this problem. Until there is a solution I just have to wait the 72+ hours?
Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?
It may be formatting and encrypting your data partition.
Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.
Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???
frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.
I bought a Moto X (2014) with a broken/damaged screen for super cheap. When I bought it, it vibrated and made sounds so I knew it was functional. The next day, the alarm woke me up so I turned it off. The day after it happened again, so I just let it ring under a pillow until the phone died. Yesterday, the screen replacement finally arrived and I performed the switch myself.
When I tested the screen before closing it back up, the phone wouldn't boot, but the screen itself appeared to be functional so I closed it back up. The infamous green light issue was occurring, no doubt due to the fact that I let the battery drain completely then left it in a drawer for about a month, in addition to God knows what the previous owner had done to it.
After several hours of hooking it up to various chargers and cables and computers and performing a seemingly infinite number and duration of button combinations, it finally booted up, and started to charge normally.
Only then I realized it was still protected by the pattern code from the previous owner. Due to fear of FRP, I kept trying to crack the pattern code to no avail. Eventually I said frick it and went into bootloader mode to try and unlock the bootloader, but it turns out that adb is not enabled, and neither is the "allow bootloader unlock". So I said frick it and hit factory to reset the phone, but the phone simply rebooted. Odd. Alright, so I hooked it up to a computer in bootloader mode and performed fastboot erase userdata. Upon reboot, FRP had kicked in.
Hours of searching yielded various methods of bypassing this, none of which worked. However due to the blessing/curse (more on that later) that it's on Marshmallow, I was able to use a Google Assistant loophole to access pretty much the entire device (minus Google apps, including the play store). This included the settings app. To my dismay, I'm unable to activate dev options and the reset button is greyed out, no doubt due to a group policy preventing these functions until the owner's Google account is entered.
I came across a method that showed a lot of promise. Through the use of an app called Quick Shortcut Manager, it allows you to log into any Google account and once you reboot afterwards, FRP is no longer an issue. However in my case, since I seem to be exceptionally lucky, during the sign in process, the phone reboots unexpectedly. How very odd. Retried several times under various conditions, including Force Stopping all Google apps (which returns the navbar buttons, without function, and also the notification tray but not quick settings).
Alright. I installed Telegram via apk and logged in. As soon as I logged in, the phone reboots unexpectedly again, which leads me to believe that this random reboot occurs whenever ANY account is added to the device (because Telegram accounts are saved under Settings > Accounts).
Knowing I'm stuck with a locked bootloader and no way of unlocking it without accessing dev options which I'm unable to do, I decided to try flashing an earlier build. I downloaded 4.4.4 and 5.0.1 factory images and proceeded to try flashing 4.4.4, to no avail, since apparently downgrading is also impossible with a locked bootloader. Most commands returned a "remote failure" response. I continued anyway and upon reboot I discover that nothing has changed. I've tried this with both system images.
I tried RSD Lite as well but it won't even detect the phone in fastboot/bootloader mode (on Windows 10 Insider Preview). Tried with admin privileges. The "fastboot flash" option in the Config menu was greyed out for some reason.
I've hit a roadblock. I'm so ready to just toss this phone out the window but I decided to come here and ask for help first. Please, XDA. Do not fail me.
P.S. I've lost contact with the owner because I bought the phone on a local equivalent of Craigslist so neither the ad nor my communication with him still exists. And even if by some miracle I managed to find one, it would do me no favors if he would remove the account via Google Device Manager because I've already reset it. The only thing he can do for me is log into the phone using his email and password and then reset it, which would require going somewhere with WiFi that is also public all the while making sure he doesn't try to steal the phone back now that it's fixed.
Edit 2: Ever since I added the Telegram account, the phone is no longer usable, since it reboots unexpectedly as soon as it connects to WiFi and discovers that an account has been added to the device. I'm going to reset it again so I can continue using it with these limitations.
I remember once on a Samsung device I found a pre-rooted IMAGE file and flashed it via fastboot and that fixed everything. I can't seem to find anything of the sort for this phone though.
I've found instructions on how to convert a ZIP ROM into a system image, but those instructions are only for Linux.