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
Related
Ive downloaded and reinstalled all drivers, pretty much tried everything. in the command prompt i keep getting adb is not a valid file. Please help. ive already use the adb tutorials and done all the stuff they said, im using windows 7 32 bit
If you downloaded the evo-recovery.zip, the file you need is in there, it's just has a different name.
The instructions where written w/ adb.exe in mind, but the file in the packet is called "adb-windows.exe."
All you have to do is substitute "adb-windows" when the command calls for "adb"
Like this -
"adb reboot recovery"
should be
"adb-windows reboot recovery"
For me to have it work, I had to go to the command prompt and be in the same folder.
If you're not familiar w/ DOS, do it this way and it will save you sometime.
Unzip the evo-recovery.zip to the C: Drive
Go to a command prompt and type the following
cd\ {ENTER}
cd evo-recovery {ENTER}
Now you'll be at the C:\evo-recovery>
Here you can type the command "adb-windows reboot recovery"
You need to set the environment in order to execute abd under any folder
-------------------------------------
Sent via the XDA Tapatalk App
I am having trouble myself on the Vista. With both my G1 and the Evo.
-------------------------------------
Sent via the XDA Tapatalk App
Can someone please help me, I can not get the ADB drivers installed. I have done everything I can think of. Tried uninstalling them using usbdeview, tried uninstalling them through device manager but nothing I do is working. I am running a bootcamp windows 7 64 bit. Oh I do have USB debugging selected.
Any help would greatly be appreciated.
-Cory
finally
appreciate the help guys finally got it to work by manully putting adb.exe, adbwinapi.dll, and adbwinusbapi.dll in my windows/system32 folder. took me about 6 hours of googling
chandlerw88 said:
appreciate the help guys finally got it to work by manully putting adb.exe, adbwinapi.dll, and adbwinusbapi.dll in my windows/system32 folder. took me about 6 hours of googling
Click to expand...
Click to collapse
It's been so long since I've had to do that with any version of Windows, I think the last was Win95, that I didn't even think to do that! I'll throw it in there just to make things easy!
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
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2
Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250
no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff
getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3
[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app
pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722
Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250
Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps
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
Hi there,
I'm having trouble flashing the latest community build to my OP3 from my mac. I followed the instructions below from the lifehacker website to install ADB;
"Download this zip file containing the scripts.
Extract the zip and place the Android folder on your Desktop.
Open a new Terminal window.
Enter cd Desktop/Android
Enter ./ADB-Install-Mac.sh"
Following this, when entering the ./adb sideload command I get the message "-bash: ./adb: No such file or directory"
Everything I have downloaded has been saved onto my desktop, the command I am using is "./adb sideload Oneplus.crdownload".
Does anyone know how I can get round this? I flashed an update to my nexus 7 years ago from my old windows laptop and didn't come across this problem.
I've tried searching the from for a solution but couldn't find what I'm doing wrong.
Thank you in advance!
"./adb sideload Oneplus.crdownload" looks like an incomplete download file in Chrome. Are you sure the file download was successfully?
Hi there,
Thanks for the quick response, I cant be sure, however just downloaded it again and tried the command "./adb sideload OnePlus3Oxygen_16_OTA_007_all_1610310039_bc5bc09fd 9af4ceb".
I still get the same response.