So I don't remember having any trouble at all unlocking the bootloader and rooting my original Nexus 7, but things aren't going so smooth this time. Here's what I've done:
1. Downloaded the Kwongger Nexus 7v3 I found here on XDA, unzipped the folder.
2. Turned on the USB debugging after enabling Developer options on my tablet, plugged it into my MAC
3. Opened a terminal, did "CD" (change directory), dragged the folder over to the terminal, and hit enter, and it switched to said directory(the MAC directory within the Kwongger unzipped folder)
4. Tried "fastboot reboot bootloader", "fastboot devices", all I got was "command not found"
5. Manually rebooted the Nexus 7 into bootloader, tried the previous commands, including "fastboot oem unlock", just keep getting the "command not found".
What the heck am I missing here? The MAC info I have found through searching thus far was written for people much more knowledgeable than me. If anyone can help, please put it in as layman's terms as possible. This Mac I'm using is the same one I used to root my Nexus 10, Galaxy Nexus, and original Nexus 7. I have downloaded the SDK or whatever, but don't know if I need that, or what to do with it.
Sorry for the horribly long post, but I wanted to be as clear as possible. Thanks in advance!!!
Add ./ before all the commands.....for example ./fastboot OEM unlock
Sent from my Nexus 7 using xda app-developers app
OP, see this: http://forum.xda-developers.com/showthread.php?t=2388687
Related
Hey guys, while I'm not exactly new to rooting, it has been quite some time since I rooted my N1 (and that was the only time I've ever rooted anything. I'm now a little lost with the unlock/rooting process. At this point,:
*I have the latest SDK, and I've updated the Platform Tools and added the contents to the Tools folder
*I've connected via USB and I've done the volume-down-power-up combination and have the "Starting Fastboot protocol support" screen.
However, that's all I've been able to do, and I honestly don't know what I'm missing. I can't get the the commands in Terminal to communicate with the tablet. Any assistance that anyone could provide would be greatly appreciated.
THANKS!
You have the Motorola v4.9 USB charging drivers installed?
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Elysian893 said:
You have the Motorola v4.9 USB charging drivers installed?
Click to expand...
Click to collapse
Well I was looking for drivers initially, but then I read in the "how to unlock" thread that someone said drivers werent needed on a Mac. Plus I looked for Mac drivers and couldn't find any, just Windows.
bcgaynor82 said:
When you do "adb devices" in terminal, can you confirm the Xoom is recognized?
If it is, following the guide here on XDA should go swimmingly. If it isn't, something is wrong with your SDK installation.
Click to expand...
Click to collapse
Well I'm not sure I'm opening Terminal in the right location. Entering "adb devices" gives me "command not found.
Ah, Mac, I'm of no use to you then.
Well should anybody see this, I'm still trying to get this to work. I can now confirm that the xoom does not show up after entering "adb devices". Otherwise I think the SDK is set up properly...at least I think it is.
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
joeski27 said:
AH, FINALLY! See, I knew whatever the solution would be, it would be a simple one. Xoom unlocked! Now to move on to root! Thanks a LOT!
Click to expand...
Click to collapse
Set your path. Edit your .bash_profile and you can run commands from anywhere in the terminal. Example:
Code:
export PATH=$HOME/bin/android-sdk-mac_x86/tools:$HOME/bin/android-sdk-mac_x86/platform-tools:$PATH
tanman21 said:
take the file you want to use (adb or fastboot) and drag/drop in to the terminal window. Then just finish typing the command.
Click to expand...
Click to collapse
That makes me a little sad. People should know how to use a command line
Sent from my PC36100 using XDA Premium App
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
neccoguy21 said:
I've got the latest download of CWM Touch for the GNex, but I downloaded it a few days ago and I'm not exactly sure how to go about installing it properly. Googling it or searching the forums brings up a million and 1 wrong/outdated/incomplete links. I don't have nearly as much time to devote to my moding anymore, so a point in the proper direction would be very helpful. Thanks
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Know-Fear said:
This is the way I personally do it.
I use the naked driver set that finds nearly any device I have tried it with and works perfect. (if you have the toolkit installed, you should already have the drivers installed)
Place the new recovery.img in the Toolkit folder
Open the folder that contains the tooklit
Right click and select 'open command window here'
In the cmd window type this:
adb-toolkit devices
Make sure yours is detected
Reboot the phone into the bootloader
then type this:
fastboot-toolkit oem unlock
Follow the prompts on the phone
then type:
fastboot-toolkit flash recovery name-of-recovery.img (I rename mine to something simple and easy to type back out quickly)
When that shows as successful type this:
fastboot-toolkit oem lock
Then using the volume buttons on the phone, select restart and press power.
As a side note, I also copied both the adb-toolkit and fastboot-toolkit files into a different folder and renamed them to just adb and fastboot and pasted them back into the original folder. This way the toolkit still works and I can just type adb XXXXX or fastboot XXXXX in my cmd window.
Hope this helps.
Click to expand...
Click to collapse
This is a very helpful way of doing things, but a little too long winded for CWM. But I'm thankful for you taking your time to respond and I'm happy to have this guide handy.
gpfnzl said:
If you don't know how to run command, when you have time it is very handy to learn.
But for now, if you can't:
Download *GNex Tool kit 7.4* install with drivers (supplied) onto your computer. down load from development page.
Close the toolkit
put the CWM file into the "put_img_files_to_flash_here" folder (created when you installed tool kit) - i too am guessing its an .img file.
USB attach the phone to computer
open bootloader on phone
then open toolkit and follow instructions to flash .img files to phone.
Click to expand...
Click to collapse
A similar strategy to know-fear's, but different. Again, thank you very much for your help, but it's not the way I'll handle this one.
ÜBER™ said:
Assuming you have the Clockworkmod-touch.img for your phone all you need to do is run this command if you have fastboot.
Code:
fastboot flash recovery name-of-recovery.img
then it should write the recovery.
Click to expand...
Click to collapse
This was what I was looking for. Thank you so much for your time and help!
Sent from my Galaxy Nexus using xda app-developers app
Long winded perhaps. But it's the same thing for most phones running android. So in essence, once you learn it, you know it for good. I've been using the same method since back in the G-1 days. And honestly, those steps I listed take about 15 seconds to complete. It's just good to be thorough.
There are several threads on XDA and elsewhere purporting to explain/help people fastboot while using a Mac as their "host." There is even a utility, Androtility:
http://forum.xda-developers.com/showthread.php?t=914826
that claims to facilitate fastboot, as well as most other platform-tools-like tools. Unfortunately, I have not been able to get this to work for me...has anyone out there got another idea?
I can see my device with "adb devices" but "fastboot devices" just returns me to the command line. The version of the stock utility I have is one downloaded from the CyanogenMod wiki, and with which I (without fastboot) succesfully downgraded and rooted my phone...so most of the stuff there works...just not fastboot.
One thought I had was that of the name collision...the CM utility is called fastboot, as is the one in Androtility. Since I adjusted my PATH in .bash_profile to allow access to the CM fastboot version from anywhere, will it be called _even_ if I invoke fastboot while in the Androtility folder, instead of the version that is right there?
Also, need I change permission on Androtility to make it run...? When I call what seems to be the main Androtility app...my shell says there is no such command.
I tried changing the name of the Androtility version to "fastboot-mac" and "fastboot mac" and each time I also got the "no such command" respond from my shell,maybe chmod to 777 is needed...I admit I haven't looked...
I want fastboot so I can flash my hboot to 0.84...has any DZ/G2 plus Mac user done that?
many thanks and regards,
p-d
You have to boot your phone to fastboot, you haven't said if you actually did so I'm assuming no. Otherwise you probably don't have the driver so the easiest option is install the android sdk and platform tools
If you're getting "no such command" it's because the location of it isn't in path, if you're in the folder it's located in you need to do "./fastboot" to run it
Sent from my HTC Vision using Tapatalk 2
Hi there,
I am coming from the Nexus S. With that phone I already have the ADB driver installed. Can I just go start use fastbook OEM unlock with the gnex directly? Or do I need to us the Nexus Toolkit?
Can I just follow the instructions here to root the gnex?
http://wiki.cyanogenmod.com/wiki/Galaxy_Nexus_(GSM):_Full_Update_Guide
thanks.
read this
http://forum.xda-developers.com/showthread.php?t=1626895
sent from my i9250
also these are the sources for official information, thought i should (i'll start now) point it out, even though efrant's guide is far more comprehensive.
http://source.android.com/source/building-devices.html
https://developers.google.com/android/nexus/images
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
Click to expand...
Click to collapse
note that efrant guides you on the entire thing, manually, giving you more control. Google provides a flash-all.sh bash script, which does the same thing, but more automatically.
It should be the same exact process thru fast boot. Just hold the volume keys and power then connect to computer, do cmd, and fastboot oem unlock. May need to go to the android folder in cmd if needed
Sent from my Galaxy Nexus using xda app-developers app
Hey guys,
Thank you in advance for reading and helping.
I am trying to root my nexus 7 2013 so I can update to the latest android software in hopes of reviving some of the performance.
The video that I am using to help with rooting is: https://www.youtube.com/watch?v=12BOhJrJTXQ
I download all the files, installed the android studio, adb tools are in the C drive with platform tools and tools. I have placed the supersu file onto the device.
When I go to run the command prompt from the "platform tools" folder and type in "fastbook oem unlock" I get an error. I am attaching a screenshot of the error.
I have also attached the bootloader screen of the nexus 7 in case that maybe of some help.
Solutions that I have attempted: I have tried to go into CMD and and change locations using "set path" commands but that didn't resolve the issue.
Any help is appreciated. If someone can chat or text me to walk me through this it would be much appreciated.
Got it figured out myself actually.
Just download Nexus root toolkit. Easy process.
Thanks