Database Users

Nexus 7 too many pattern attempts Locked!

I got my N7 Last week. My sister Locked it by too many pattern attempts. Now it asking to enter my gmail username and password.. I entered it bt not worked. I googled and find for solutions. I dint get a working solution.
Then i tried to Hard Reset the device. I followed all instructions given by google. But it freezes while Going through Recovery mode. I waited about Hours for a response. after that I tried Hard Reset by connecting USB Cable to PC. It Freezes at the menu itself.
Then I Installed SDK (4.1), ADB, FASTBOOT and Drivers from Nexus 7 toolkit by XDA.. still not working..
please Help Me to Solve this.
My device is UNROOTED.
Wi-Fi is OFF!
USB DEBUGGING is OFF!
I cant acces non of above because its locked.. please please help!

Finally got it!
When I Installed the drivers and Rebooted my device the Hard reset Worked Finely.
Ensure that..
1. USB Cable plugged in or not.
2. Necessary drivers installed or not.

That is funny because that's exactly what happened when I had my og droid. Except I was the one who locked myself out of my phone. Good job on getting this resolved.
Sent from my DROID3 using xda app-developers app

how to install SDK
sajjadpazhayillath said:
I got my N7 Last week. My sister Locked it by too many pattern attempts. Now it asking to enter my gmail username and password.. I entered it bt not worked. I googled and find for solutions. I dint get a working solution.
Then i tried to Hard Reset the device. I followed all instructions given by google. But it freezes while Going through Recovery mode. I waited about Hours for a response. after that I tried Hard Reset by connecting USB Cable to PC. It Freezes at the menu itself.
Then I Installed SDK (4.1), ADB, FASTBOOT and Drivers from Nexus 7 toolkit by XDA.. still not working..
please Help Me to Solve this.
My device is UNROOTED.
Wi-Fi is OFF!
USB DEBUGGING is OFF!
I cant acces non of above because its locked.. please please help!
Click to expand...
Click to collapse
This is my first post on this forum. Since the N7 is locked (I have one in the same condition), how did you install anything on it?
TIA
now_john

now_john said:
This is my first post on this forum. Since the N7 is locked (I have one in the same condition), how did you install anything on it?
TIA
now_john
Click to expand...
Click to collapse
Adb etc are PC installs not on the N7
Sent from my Nexus 7 using xda app-developers app

Google Nexus 7 Tab unlock
Hi ,
Tried so But failed to unlock my tab..its so painfull and very sad to state that google has no support..Can you help me out with step by step process to unloack my nexus 7 tab from " too many patterns tried "
thx

Sounds like Google should have put some more thought in the feature. Give the users a way to lock themselves out - and they will.
At least the "too many attempts" screen should tell the user to log in with the Google ID and password the device was registered with.

Can't help but think... Stolen.

Geesh, isit so hard Tod remember Gmail info so you can back in?
Sent from my Nexus 7 using xda app-developers app

mustbepbs said:
Can't help but think... Stolen.
Click to expand...
Click to collapse
Can't help but think - Dang - little sister got my Nexus again...

[Q] waiting for you device to finish booting back up...

Nexus 7
Android 4.1.2 JZ054K
using Nexus Root Toolkit v1.5.5
I've done: 1. Initial setup- full drive installation
2. backup
3. Unlock
everything went as expected according to the procedure.
4. the Root, it went through it procedure until it got to:
--waiting for your device to finish booting back up...---
been waiting on this screen forever, the Nexus 7 screen shows the android w/ the "Start" tab.
done this procedure several times w/ Nexus Root Toolkit v1.5.4 and several time w/
Nexus Root Toolkit v1.5.5
nothing has changed, don't know if my Nexus 7 is unlocked or rooted.
pls help. any ideas, suggestions...
thanks in advance

Try to reset the device to factory and try again. Take it slow and make sure you're following each step.
If all else fails, Google, Google, Google...
Good luck

I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.

zombiest said:
I had this same issue today when rooting my new 32gb Nexus 7. Wug's tool wasn't autoselecting the right version (4.1.1 when I had 4.1.2) and it was doing the same thing, hanging on the "waiting for your device to reboot" message. Make sure the firmware version on the Nexus matches the version Wug's tool is detecting.
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod

No success on this issue!!
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.

Same Issue
mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.

mike_24_11 said:
I did the same but my Nexus4 can't be booted up by the NRT v1.6.3!!
It stays on "waiting for you device to finish booting back up"
Pls somebody help..
Thank you.
Click to expand...
Click to collapse
So.....you come into the Nexus 7 forums to try and get help with your Nexus 4......OK
ananiah2011 said:
I have been trying the NRT 1.6.3. The issue of Waiting for your device to finish booting back up.... repeats.
No solution yet.
Click to expand...
Click to collapse
Dont use a toolkit, its that simple. In the amount of time you have wasted on that toolkit, you could have learned the manual method and realized it wasnt as hard as you thought

Booyah
zaphodmuc said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
HTH.
Zaphod
Click to expand...
Click to collapse
Thanks!!! worked like a charm

Bohefus said:
Thanks!!! worked like a charm
Click to expand...
Click to collapse
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough

ibbeebee said:
In case somebody finds this thread, I resolved this problem by setting the USB connection from MTP to PTP (in the messages dropdown), then it was recognized properly by the Nexus Root Toolkit.
Where do I change the USB connection from MTP to PTP . I mean where do I find the dropdown on the device or on in the program?
I can't find any USB settings. I will probably feel a little stupid when I'm told where to find these settings but I'd been knocking my head against the wall long enough
Click to expand...
Click to collapse
kind of like the one located in Settings>storage>menu>USB Connection?

Pirateghost said:
kind of like the one located in Settings>storage>menu>USB Connection?
Click to expand...
Click to collapse
Well I probably would never have found the setting without help, I couldn't find anything called menu so I tried the 3 dots next to the search button, Bingo the jackpot!. Now to see if I can back up the device .
I may be back but let's hope not
Well I'm back!!
I have been through the driver config Guide & the new drivers seem to be installed But I can't see my tablet in explorer anymore & my Device is open in a screen I haven't seen before
A big button at the top of the screen
START
then an up & down arrow
FastBoot Mode
Variant -flo32C
HW VERSION -rev_e
BOOTLOADER VERSION - FLO-04.04
CARRIER INFO - NONE
SERIAL NUMBER -07e1eda6
SIGNING -yes
Secure BOOT - enabled (in green)
LOCK STATE - unlocked
& I'm rather nervous about touching any of it
I'm about to start the driver process again but will wait for some advice
OK I did not follow my own advice & have rebooted the device & it has loaded normally& is now viable on my computer again .
I will wait for some feedback before proceeding Thanks in advance for any assistance Regards Beebee

Hi I repeated the process & have success at last.
I have backed up the device & am about to root it.
What are the advantages & disadvantages of ticking Custom Recovery . I've done a Google search but I finish up being sidetracked for hours when I do that So will just ask you

[Q] Nexus 7 stuck on bootloader/google screen

Don't know how but I broke my Nexus 7 (2013 LTE) using wugfresh toolkit. I had it rooted and unlocked using the toolkit then decided I wanted to go back to stock. So I used the flash stock + unroot (device on) and oem lock.
Now my Nexus when powered on comes to the bootloader (fastboot mode) screen that has START at the top in green. If I press power to select start it shows Google in white with nothing else on the screen. It will stay like that forever (at least a few hours that I've verified). I also just noticed while it is on the "Google" screen I can press the up/down volume buttons and it gives me the option to start, power off, etc. just like it's still in the bootloader. I'm not really sure what all that means... just trying to give as much information as possible.
I've had no luck finding a solution already on this forum. I haven't even found someone who describes this exact same problem with this particular model Nexus.
In addition to trying to use the Wug toolkit to fix my Nexus I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2381582
I tried following the instructions exactly and the output seemed to report fixing my Nexus but it did not. I'm referring to the output you get when you run the dead nexus bat file. The only bad output it gave me was several messages "FAILED (remote: Bootloader is locked)" However, at the bottom of the output it said my "Nexus has been restored!"
So in summary these two solutions I've tried (wug toolkit and the thread mentioned above) seem to report fixing my Nexus but didn't actually do anything. Also noticed now with the WUG toolkit the driver test fails. I followed all the steps and removed all drivers and did a fresh install. It mentions needing USB debugging enabled but how can I do that since I can't get past the bootloader/google screen?
Any help appreciated!

One other thing I forgot to mention. When it was working after I had rooted/unlocked I installed that multirom app from the app store. I don't see how that could have broken anything.

One last thing I recall. The last thing I did was do a factory reset under settings when everything was working.
I've been trying all these various toolkits and following videos but nothing seems to fix it. One thing about all these help guides out there they all tell you to make sure you're in usb debugging mode... but that isn't possible for me since I can't get past the Google loader. I haven't had much luck finding out what to do in my case.

and I think I just fixed it! I will post what I did if this works...

So all I had to do was unlock my bootloader then do the factory/stock restore. When I tried following every single recovery guide out there none of them mentioned unlocking before doing the 1 click restore/fix. Strange I had to do it this way I guess, but every tool would error out saying the Nexus was locked.

USB connection failed, stuck on boot logo.

Hello friendroids,
First I want to say that I have already searched if someone had the same problem as mine. I cannot guarantee I have been through all the threads already posted but I tried to investigate, finding solutions that were not suitable to my case.
1) Explanation of my problem:
As a good noob I tried for the first time to root my Nexus 4. I am using a Mac Book Pro running OSX 10.9.3.
I have managed to unlock the bootloader but can only run the Recovery mode using ClorckworkMod Recovery v6.0.4.3.
I have already done "wipe data/factory reset" and if everything had went well, the next step was to reboot the system and install "UPDATE-SuperSU-v1.80.zip" using Android File Transfer.
Now this is when I think I did something wrong. I cannot remember for sure but I think I said "no" twice at the screen that said "root[something]", that did not appear in the tutorial I was following. Unfortunately I cannot remember the "something part" because the second time it just rebooted itself and got stuck on the booting animated colored bubbles. So I tried to turn it off but I might have unplugged it before it was off. I could not turn it off straight away (maybe for misusing the physical buttons...) and my screen was saying "DOWNLOAD MODE DO NOT UNPLUG the device until the process is complete." At that time I had my phone plugged again before seeing this screen.
Then I turned it off, booted the recovery mode, and following the Q&A section of the same tutorial, I wiped the cache partition and the dalvik cache (several times).
2)Question.
So now I am stuck on the same booting logo, unable to exchange files between the Nexus and the Mac through Android File Transfer. The good news (if I may say so), is that the battery is still charging through the USB cable when connected on the Mac.
Has anyone any thoughts on how to help me finish to root it, fix the USB connection and install OmniRom (in whichever order you want)?
Thank you very much for reading and for the general purpose of this forum. :fingers-crossed:
PS: Can I put a link of the tutorial I was following for better understanding of my problem or is against the rules?

If you just want to install omni rom then you don't need to root you device. Download the zip file and flash it using custom recovery or sideloading. Since you cannot boot you will have to go with sideloading.
And yes, you can post the link of the tutorial.
Sent from my Nexus 4 using XDA Free mobile app

Nexus 10 - bricked. Black glowing screen

I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks

lejars1 said:
I could with some help please. I expect that the answer is already on the forum somewhere, so if someone could post a link, that would be great.
My Nexus - unlocked and rooted - 5.1 with Wugfresh several months ago, today decided not to boot up.
I get "Google" then it goes to a black/glowing screen and stays there.
With some fiddling around I can get the dead Android and "no command". I can get into the power off/recover/reboot bootloader etc screen.
I have wiped the cache - no change.
I have done a factory reset - wiped all data - no change.
Using Wugfresh, I get - no ADB
I am not able to check usb debugging because I can't get into the device.
The thing is obviously alive (although not as we know it) because windows install a driver for it when it is plugged in to the USB post. However it installs an MTP driver and I am not able to change this.
Any ideas anyone?
Thanks
Click to expand...
Click to collapse
It is possible that your system and/or boot partitions have become corrupted.
If that is the case, you'll need to reinstall the ROM. The best way to do this is to install a custom recovery like twrp or clockworkmod, reformat your partitions, and proceed from there.

Hi - thanks for this.
I got it sorted in the end.
Here's a link to what happened.
http://forum.xda-developers.com/showpost.php?p=60970017&postcount=1597