Related
This is the same as any other Nexus device.
WARNING. As is normally the case, this WILL factory reset your device.
Install the Android SDK (and Google USB driver).
Android SDK
Google USB Driver (Windows)
Enable USB debugging on the Nexus 7.
Unlock Developer Options by going to Settings > About Tablet and clicking on the build number seven times.
Go to Settings > Developer Options and check USB debugging. Click OK on the warning.
Connect the Nexus 7 via USB and reboot the Nexus 7 into the bootloader.
Note: Users have reported failures and "Access is Denied" errors when connected via USB 3.0 ports so use USB 1.1 or 2.0 to be on the safe side.
Open a command line / terminal and navigate to your SDK platform-tools directory.
Enter
Code:
adb reboot bootloader
and hit enter.
Once the Nexus 7 boots to the bootloader, unlock it
At the command line / terminal enter
Code:
fastboot oem unlock
and press enter.
On the Nexus 7, use the volume up button to select 'Yes' on the 'Unlock bootloader?' screen.
Press the power button to save your choice and verify on the next screen that you see 'LOCK STATE - UNLOCKED' at the bottom.
Use your volume keys to select 'Start' and click the power button to factory reset and reboot.
Enjoy your unlocked bootloader!
Do you have the usb drivers installed? That happened to me ("old" n7) when I didn't have the usb drivers installed.
may need to update your drivers for it to be able to see the device.
when you try adb devices while it is on does it kick back the device id number?
i haven't tried yet as i knew the drivers out currently would be an issue.
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
gksmithlcw said:
Any ideas? I tried I tried the ol' fastboot oem unlock command and it just sits there with the < waiting for device > message.
Click to expand...
Click to collapse
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
mrancier said:
Perhaps it needs new adb/fastboot drivers ? I'm still charging mine, so I haven't tried. Sorry. Maybe the new driver comes with the 4.3 SDK ?
Click to expand...
Click to collapse
I updated my SDK when 4.3 dropped but I did have to go snag the Google USB driver and install it to get the N7 to be recognized.
ATGAdmin said:
First off (don't mean to be a d!ck) but this thread belongs in "General", or "Q&A", because you haven't posted a development thread.
Second, unlocking the boot loader is just as easy as the first Gen Nex7. I had mine unlocked within 5 minutes of getting it home.
As others have said, make sure your drivers are installed, or ADB won't even recognize the device.
Click to expand...
Click to collapse
1. You may be right (as far as my posts go) but how am I to ever make a dev post if I'm not allowed to make a first post in a dev forum?
2. This /is/ a dev-related post.
3. My feelings wouldn't be hurt if the mods felt the need to move the post.
Yeah I had to install the google usb drivers from the SDK in device manager of Windows to get the n7 recognized.
Thanx. Just got home with my new nexus 7....bootloader now unlocked :highfive:
Nevermind it literally is that as the command.
Sent from my Nexus 7 using Tapatalk 4 Beta
keynith said:
Can you update it with the commands? So people don't have to search
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The commands are there...
Also, unlocked mine not 5 minutes after opening on Ubuntu 13.10.
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Worked great thanks!
---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------
smirkis said:
no idea why my device won't be read by adb. but i manually rebooted to bootloader and fastboot oem unlock took care of that. time to wait for root/recovery
Click to expand...
Click to collapse
Make sure you update your files from the SDK Manager. It had updated USB driver which from there it would install the proper drive and then it worked form me.
The trick, as stated in the Nexus Toolkit after driver install, is that you need to change the tablets usb settings from MTP to PTP. Tablet was immediately seen using "old" nexus toolkit universal usb drivers (old = i did not download the new SDK). I choose toro 4.2.2 (because it doesn't matter for unlocking) and then told it to unlock. worked like a charm.
Now the question is ... how long does it take to reboot cause mine is taking forever!!!
OK it booted. So yeah the Nexus 7 Toolkit ver 5.0 worked just fine to at least unlock. I did not root (4.3 still too buggy) or install a custom recovery yet.
Stock recovery, pretty please?
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
My body and my 7 are ready for a recovery!
Thank you!
treoo0_1 said:
My dumbass flashed TWRP for Grouper. Wouldn't boot, so I tried erasing the recovery in hopes it would self-restore. No dice. Can't seem to find recovery-from-boot.p either. No boot and still no custom recovery for this puppy. :crying:
Would someone be the kindest person on earth and pull & post the stock recovery...or tell me how to find and flash a back-up copy already stored on my nexus? Google hasn't even posted the img files yet. My new toy is borked and Daddy wants to play tonight!
Thank you!
Click to expand...
Click to collapse
I'd be happy to, but am having a hard time finding the correct ADB command.
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
adb pull
jc monkeyballs said:
I'd be happy to, but am having a hard time finding the correct ADB command.
Click to expand...
Click to collapse
Can you use
Code:
adb pull %PATH TO BE PULLED FROM% %PATH TO PLACE PULLED FILE%
Example:
Code:
adb pull /system/recovery.img C:\Android\Local
Thanks for offering to help!
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
Lpuboy87 said:
isnt the new N7 files called Razor instead of grouper ? or is that just what the device was called prior to launch
Click to expand...
Click to collapse
Yep. Razor.
Branch = Razor
codename = Asus flo
Wifi Model: ME371K
followed the first post and it worked....used this for the commands
ADB Commands
---------- Post added at 11:12 PM ---------- Previous post was at 11:10 PM ----------
treoo0_1 said:
Yep. Razor.
Click to expand...
Click to collapse
yeah thought so. :good::highfive:
Unlocked the bootloader no issue, even got the newest TWRP on there. But when i try to flash superSU the file... Is just not there.
Ive tried an OTG, with a usb drive, put that stupid file in every folder imaginable. TWRP will just not see it.
On top of that TWRP is... The aspect ratio is so off the majority of the screen is cut off. Making things all the more frustrating.
Thoughts? Anything? Please?
Saddly i have probably invested about 15-20 hours on this. Have been rooting phones singe the HTC Desire days (G1) and never had frustration like this... On a f&#='n media player LOL.
Sent from my SM-N910W8 using Tapatalk 4
I rooted 6.0 using this post and it worked fine:
http://forum.xda-developers.com/showpost.php?p=62412232&postcount=3
Hope that helps, because I am of no help haha
yldaedroid said:
I rooted 6.0 using this post and it worked fine:
http://forum.xda-developers.com/showpost.php?p=62412232&postcount=3
Hope that helps, because I am of no help haha
Click to expand...
Click to collapse
Yes I followed that thread to a tee, however when I try to flash the Super su zip file in TWRP the recovery does not see the SuperSU file. No matter what folder I keep it in, whether i use the OTG cable the device will just not recognize the SuperSU file.
Infuriating.
Im outta ideas, was hoping someone on here would have experienced something simaler and be able to help. Thank you for your response.
Nevermind, Moderators please close this thread.
Following this procedure on a computer monitor is very different from a 1080p television.
Basically I am an Idiot and it is in fact rooted.
celkin said:
when I try to flash the Super su zip file in TWRP the recovery does not see the SuperSU file. No matter what folder I keep it in, whether i use the OTG cable the device will just not recognize the SuperSU file.
Click to expand...
Click to collapse
Here is what I did. Turned the device on normally with USB debugging turned on. I put the SuperSu zip file in the platform-tools folder, and for ease of typing the commands I renamed it to SuperSU.zip. I then used the following commands to push it to the root of the device storage:
cd Desktop/android-sdk-windows/platform-tools
(To the correct location of your platform-tools folder if you have not done so already)
Then
adb push SuperSU.zip /sdcard/
It should tell you that it was successful. Afterwards I booted the device into recovery mode. In TWRP I selected the option to install zip. I found and selected the SuperSU.zip file I put on the devices sdcard folder. Then Rebooted.
Hope that helps! Please post screen shots if you are still stuck.
---------- Post added at 10:10 PM ---------- Previous post was at 09:59 PM ----------
Haha took long enough for me to write that last post that I didn't see your latest response. Glad you got it figured out! Let me know what kind of issues you see with 6.0. I want to see if my issues are specific to me or not.
The isue was totally with the resolution of the moniter i was using. And not realizing this version of twrp is "dual pannel".
Really my oun stupidity.
Problem now is finding an older version of cyanogenmod that does not crash the system every time you plug in a mouse and keyboard lol.
This thing is the most frustrating android anything ive ever worked on lol
Sent from my SM-N910W8 using Tapatalk 4
If anyone has a cm12 version (or knows where to download one) from june-july i would be eternally great full
Sent from my SM-N910W8 using Tapatalk 4
celkin said:
If anyone has a cm12 version (or knows where to download one) from june-july i would be eternally great full
Sent from my SM-N910W8 using Tapatalk 4
Click to expand...
Click to collapse
DHacker29's Android File Host folder. Just google it.
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
Assuming that the ROM is still there, you can dirty flash the ROM zip over it, and see if it works. There's no harm in trying that.
But "No OS Installed" simply means that your /system or /boot parition are not detected (means, they are empty). Now of course, the last resort is to flash the ROM all over again.
Krooked22 said:
I left my phone charging and came back to get it. It was stuck on the google logo, I am able to boot into recovery but it says No Installed.
Is their anything else I can do other than flash it again.
I was thinking maybe the wrong partititon was checked, but everything looks fine.
Click to expand...
Click to collapse
You need to provide more information. Are you on the stock ROM or a custom ROM? Stock recovery or TWRP? Had you made any changes to the device recently?
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download any ROM ( like pure Nexus) and gapps
You can use USB otg to flash the ROM using twrp or transfer the ROM file from your PC to your phone in twrp (it supports mtp)
Simply flash ROM and gapps and viola
Sent from my Nexus 6P using XDA Labs
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
StormCell said:
Someone please help. I just rooted my 6P. Did a little bit of doing. Phone would never boot just the round circles. So went into TWRP and tried to wipe to start fresh, not it says no OS installed. I have no ROMS's on the phone. No boot images. Been a while since I've done this. Really need help on this one. Thanks.
Click to expand...
Click to collapse
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
i42o said:
Download the dp3 , boot into bootloader, connect to PC run installer script after you unzip the factory image " flash all" sit back and wait for phone to reboot.
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
It's that simple.
Click to expand...
Click to collapse
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
StormCell said:
Ok, I'm gonna tackle this tomorrow. Any recommendations on a good ROM and Kernel (Verizon). I made nice donations long ago to Franco and ROM Manager.
Thank again, everyone!
Click to expand...
Click to collapse
Please continue the discussion in the other thread that you posted this question in, as I said, let's not create duplicate discussions.
StormCell said:
Hey thanks a lot. Couple things, and I apologize in advance for not knowing this already.
1) what's dp3
2) how do I run installer script?
I know I shift right click and open a cmd window within fastest - where I'll unzip the file - and I know how to get the phone into Bootloader.
Again, sorry for asking for simple explanations.
Click to expand...
Click to collapse
Developer preview 3 is a Android N preview and it is very fluid, battery life is good on stock and reason I recommend this because it is simple to do, gives you good options within the ROM and is good overall but that's just my opinion.
---------- Post added at 12:35 PM ---------- Previous post was at 12:32 PM ----------
Heisenberg said:
Why are you telling him to install the Developer Preview? He wouldn't want that unless he's actually asking for it, which he isn't.
Click to expand...
Click to collapse
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
i42o said:
Dude, I'm trying to help. Beats what you said, you going detective mode on him while I'm just giving him an easy solution. Read a book or something
Click to expand...
Click to collapse
Lol. Maybe you missed the title under my name.
The dev preview isn't what he asked for, it isn't an easy solution, it isn't easy to come back from if he doesn't like it, it isn't even remotely what he needs. What he's looking for is a simple way to get his phone booted up and working again (a very simple request), and what you're suggesting is he install a beta OS (a complicated "solution").
If you really have a problem with a moderator requesting that a member posts in one place at a time (as per our rules), then I'm gobsmacked. If you'd care to look at the advice I gave him in the guide thread where he also posted you'd notice that I gave two solutions that:
A) Actually address the simplicity of his problem.
B) Give two simple, easy to execute, solutions that are the most common solutions you'll ever see anyone give a member in his situation. Solutions that don't involve having to install a developer preview that he never asked for.
I get that you're trying to help him, but the "solution" you provided him isn't right for his situation at all. There was no need to become defensive and aggressive when this was pointed out.
Vishal Vignesh said:
Download the required ROM and gapps, connect your phone to pc , type in google, Mini adb and fastboot, a page on XDA itself will come, download it, its small and install.
Then copy the ROM and gapps package to the location of the installation of the application.
Now open your recovery and tap on adb sideload, and swipe(twrp)
Go to your PC, open adb application a cmd will appear, type adb devices, it will start a daemon then will give you your device number, a number should appear. Then type
Adb sideload """"name of your ROM package""".zip
It will start installing, wait for few minutes.
Do the same for gapps
Adb sideload " name of gapps package ".zip
Then reboot
Its fixed
NOT Sent from my GT-N7100 using the XDA-developers mobile app
Click to expand...
Click to collapse
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
StormCell said:
I'm copying files over to my Nexus now using MTP from TWRP. Can't I just copy evrything over and flash that way? Man, this seems so much more complicated than back in the day. Thanks.
Crap, wrong thread! Sorry! Got confused.
Click to expand...
Click to collapse
Sure, this method is for those who do not wanna copy the zip package to the PC/don't have it
Sent from my GT-N7100 using XDA-Developers mobile app
Hey peoples, just curious.. I've seen some people saying they unlocked the Bootloader, I've checked lg's site, Googled, done everything possible to find a step by step guide but can't seem to figure it out.. Was wondering if someone who has done this successfully could post a how to or link me to where I could figure it out..
Sent from my LG-H918 using XDA-Developers mobile app
Edit..nvm..figured it out
Turn on usb debugging and run the command adb reboot bootloader.when yours in fast boot run fastboot oem unlock
mr turtle droid said:
Turn on usb debugging and run the command adb reboot bootloader.when yours in fast boot run fastboot oem unlock
Click to expand...
Click to collapse
I did but unfortunately it just hangs on waiting for device and does nothing..tried to download android studio to update my sdk but windows won't open the .exe for me to do so..uggh
Sent from my LG-H918 using XDA-Developers mobile app
Yea odly enough the exact same thing happened to me..but only after i unlocked the bootloader.not sure why it does this tbh..i tried all drivers. But it still hangs at any command i git anymore..the most i got out of it was the oem unlock command
---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------
Do you have oem unlocking ticked in dev options?
Yessir..
Sent from my LG-H918 using XDA-Developers mobile app
Yep im having this problem as well
A few people have said if you use straight up Linux, without any VM, it works fine. Drivers in Windows can be pretty screwy.
It just doesnt make sense how i was able to run it through oem unlock ?maybe its got somthing to do with usb 3.0 again ill test in a few
---------- Post added 26th October 2016 at 12:13 AM ---------- Previous post was 25th October 2016 at 11:46 PM ----------
so i give up...even if your in the bootloader it says try fastboot reboot...that does nothing neither does any other command..so i have no idea how i got it to oem unlock without saying waiting for device...
rbox said:
A few people have said if you use straight up Linux, without any VM, it works fine. Drivers in Windows can be pretty screwy.
Click to expand...
Click to collapse
Unfortunately I have an older pc and not enough space to install Ubuntu so that isn't an option..
mr turtle droid said:
It just doesnt make sense how i was able to run it through oem unlock ?maybe its got somthing to do with usb 3.0 again ill test in a few
---------- Post added 26th October 2016 at 12:13 AM ---------- Previous post was 25th October 2016 at 11:46 PM ----------
so i give up...even if your in the bootloader it says try fastboot reboot...that does nothing neither does any other command..so i have no idea how i got it to oem unlock without saying waiting for device...
Click to expand...
Click to collapse
I just updated my sdk this morning, reinstalled lg drivers and tomorrow I'm reinstalling java(had previously removed all my dev stuff to save space.) gonna see if that helps.. Maybe if it does I'll post a how to with all the links to necessary files to help people do this a bit easier.
Sent from my LG-H918 using XDA-Developers mobile app
I know this thread is old, but it's worth noting that switching the USB connection mode to PTP instead of MTP will most likely cause the device to be recognized be ADB when it doesn't otherwise. Not sure what causes it, but that's what I had to do.
Hello all, hope you're all doing well. I've come across some problems when trying to unlock the bootloader on the Nexus 6P. Whenever I execute
Code:
fastboot flashing unlock
in the bootloader, my command prompt stays at
Code:
< waiting for device >
and never seems to progress after that. I have also tried
Code:
fastboot oem unlock
, but it still stays on
Code:
< waiting for device >
. I have already done some research on this problem and I have tried to troubleshoot by checking if I have the latest SDK update, and I do, but still no luck. My main purpose of doing this is to install the official 7.1.1 factory image. How can I fix this problem?
Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device
I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?
Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said
Thanks for reaching out and taking time to try and help out everyone.
dontbeweakvato said:
Does it say anything in cp when you type devices? Is there a serial number that returns
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
It's either driver issue or maybe you don't have usb debugging checked. Cause it can't see your device
Click to expand...
Click to collapse
I've forgot to mention that when I run
Code:
adb devices
when the operating system is up, ADB recognizes it. However, when I'm in bootloader, like you mentioned, it doesn't see it. I've tried switching off and on the "OEM unlocking" and "USB debugging" in the "Developer options", however the problem persists.
tropical cactus said:
I know that in the beginner's guide, we are told not to use minimal adb. Unlocking bootloader is the first step. Even though my device was recognised, bootloader just simply refused to unlock. I had latest SDK tools installed and everything. So, I resorted to minimal adb and bootloader unlocked without any fuss. For everything else that followed, I used normal fast boot.
You can try this at your own risk. It worked for me. Just sharing.
Edit: if you haven't done anything to your phone, can't you just check for update and install 7.1.1 the normal way, since this is all you want?
Click to expand...
Click to collapse
Doubt minimal adb will fix this, but worth a try. I'll also try running ADB on a different computer if that might help. Also, the reason why I want the official 7.1.1 release is because my device is currently running the developer's version. In addition I tried checking for update; no use.
dontbeweakvato said:
Yeah and also if what your using is not up to date (previous adb) you can have problems with that just like that guy up there said
Click to expand...
Click to collapse
Yup. I did mention that my SDK tools are the latest release in my first post.
Edit: Never mind everyone I've found the solution! For some reason the device didn't have the Google USB drivers installed when the device is in the bootloader screen. After days of researching and trial and errors, here is the article that helped me:
http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/3/
Note: If you're experiencing this similar problem with the "< waiting for device >" message in the command line, you must acquire the Google USB driver .zip file.
Thanks to everyone that offered help!
Yep driver issues. Classic.