| || |
Nexus S locked out - cannot login to Google, WiFi is OFF
Using a Samsung Nexus S with Android 4.1
So the other night someone down the pub decided to try and unlock my phone, and apparently got the pattern wrong so many times it's now requiring me to enter my Google account details.
Fine, I enter the username / pass, only it says they're wrong - I know they're correct because I've just confirmed they are by logging into Gmail. It says they're incorrect so quickly that I suspect it's not even connecting to the web to check. The icons at the top imply there is signal, but it looks as though 3G / data is off, and there's no WiFi icon even though I'm sat next to my wireless router. Ideally I just want to somehow turn on WiFi / 3G & data so it will accept my Gmail details and unlock the phone - but I can't find anyway to do this. Seems totally bizarre that Android is requiring me to validate my identity online yet not allowing me to turn on anything to let me connect. I did try going into and then out of aeroplane mode to see if this would re-enable any settings like WiFi or data, but no luck.
Looking at various other forums people have suggested a hard reset - I really want to avoid this as I'll lose all the data, but can do so as a last resort. Anyway, I tried a hard reset (phone off, hold down the Volume Up button, press the power button) but it just boots up normally and takes me to the "Too many pattern attempts" screen again. I tried as well with Volume Down rather than Up, same thing, then again with both Volume buttons, same. So now I can't even seem to do a factory reset!
Other things I've tried:
- USB Connected to a PC - the device doesn't show up, presumably because USB is not enabled
- Using ADB (Android Debug Bridge) when the device is connected by USB and calling "adb devices" - lists no devices
- Making a call to the phone works - and I can even get to the text message app by going "custom message" rather than answering the call, but I can only send a reply and see the messages sent to/from that number - can't get to the main text message app menu or anything
Any help would be most welcome - as I say, ideally I want to avoid wiping the phone, but at this point if someone can tell me a successful method of factory resetting I'd probably take it!
[UPDATE] - So I just managed to get into Fastboot Mode (not sure what I did differently - only thing I can think of is the phone wasn't connected to the PC by USB this time). Anyway, I selected Recovery, saw the screen with the Android lying down and the red exclamation mark, then the phone booted - but nothing has changed! I'm still on the 'Too many pattern attempts' screen, and it looks like the device is still remembering my Gmail details since after powering on I get a notification that I have unread mail (presumably from previously when I did have 3G / data on). Is there anything else I can do in Fastboot Mode? Load a different version of the OS for instance that would allow me to enable WiFi / USB debugging / etc?
[UPDATE-2] - Have installed fastboot:
[How To] Root Nexus S on Jelly Bean or Ice Cream Sandwich (Android 4.x) | dotTech
[Android] Downloads links for USB (adb and fastboot) drivers for Windows for all Android phones and tablets | dotTech
How To: Install ADB and Fastboot on your Windows computer for use with your Android phone | dotTech
When I run "fastboot devices" I can see the phone listed, however bizarrely "adb devices" lists nothing.
"fastboot oem unlock" seems to work (the phone prompts me to confirm I want to give root access & delete all user data). I haven't done this yet as I want to see if I can save my data somehow using adb or fastboot commands, but I suppose this is one way of factory resetting if I need to. If anyone knows much about fastboot / adb and knows how to copy / backup files using it, the help would be very much appreciated!
[UPDATE-3] - From what I understand you can't copy files off the phone using fastboot commands, but can using adb (push / pull commands) - so a few questions:
- Does anyone know why adb wouldn't see my device (when I run "adb devices") but fastboot does (note that I'm on the fastboot screen)?
- Does adb require debugging mode to be on?
[UPDATE-4] - Still can't get adb working, suspect it's because USB debugging isn't enabled (though not sure how I can check?). I did try using fastboot to erase the /cache partition in case the lockout data was stored in there - but this didn't work unfortunately. Looking likely I'll just have to wipe it with fastboot oem unlock