Related
Hi everyone,
I see more people than usual having issues with Rooting their Nexus 7 because of problems with booting into CWM recovery post flash - thought I would do a nice plain and easy to follow guide including instructions for booting into CWM recovery from a command point (thanks to Wugfresh for his Toolkit which is used in the guide).
http://www.androidnz.net/2012/07/how-to-root-your-nexus-7.html
Porting the full guide here, first the text because that is a simple cut n paste job, images to follow soon:
Before we get down into the nitty-gritty of the guide itself you should familiarise yourself with our usual disclaimers at the beginning of this post. I say this not because we don't care if you have problems, it's just that our capacity to trouble shoot is limited, and you shouldn't have embarked on an adventure to Root your device unless you did your due diligence first and had some understanding of what you were up to. One final disclaimer weasel-word at the off: the CWM recovery ports for the N7 are still a little iffy at this stage and even when taking appropriate steps to make it permanent you may only be able to boot into it via a command prompt window. Expect updates once fixes are available.
Disclaimers out of the way, here are the things you will need:
A Nexus 7, fully charged
A windows PC (the guide may work on macs via Windows virtual environments, but that isn't confirmed by us and is outside the scope of this guide)
The appropriate Nexus 7 USB drivers, there are several ways to get these:
Preferred method - Go to this thread at XDA-Developers and download and install the Root Toolkit there, which has an automated drivers installation included (this is preferred because it is what the guide that follows is based on because the Toolkit is probably going to be the most straightforward for the majority to use, and even if it fails and they have to resort to using command prompts that is more easily done from the Toolkit). Many many thanks to WugFresh at XDA for producing such a noob-friendly Rooting application - please consider making a donation to him here.
Install the Android SDK from here. Please note if you are already an SDK user that the Google USB drivers in the SDK have updated with the release of the Nexus 7 and Jelly Bean and you should update your drivers from within the SDK itself
Install the universal drivers from this post at XDA-Developers, but please make note of how you will need to adjust fastboot commands if you are using these drivers
Go to this post at XDA-Developers and install the USB drivers from there if you have no luck whatsover with any of the other methods
OK, now that you've got the Root Toolkit let's proceed (if you plan to do this with the SDK and command prompts then you should be advanced enough to follow the guide here, I did the first time and if you've done this stuff before the process is trivial).
Open the Root Toolkit, at the prompt to select your device scroll down to the bottom and select the Nexus 7 and the version number that corresponds to the firmware installed on your Nexus 7 (you can find this out in Settings --> About tablet --> Android version)
You'll be greeted with a screen that looks like this:
Click on Initial Setup and use the automatic driver installation facility from here to install USB drivers, it will check that ADB and Fastboot commands are working before dropping you back to the install window.
Turn on USB Debugging in the Nexus 7 by navigating to Settings --> Developer options. Turn on Developer options using the toggle in the top right hand corner, and then turn on USB debugging
Connect your Nexus 7 to your computer with the micro USB cable that came in the box. At this point it is vital that your computer recognises the Nexus 7 as a connected device, you will know if it has because a Nexus 7 "AutoPlay" window should pop up and ask you what action you want to take. If it doesn't show up, pull down the notification tray and press on the notification that says "Connected as a media device". A new menu will open and select the "Camera (PTP)" option. You should now get the AutoPlay window.
Head back to the Toolkit, and select "Unlock" from here, be aware that this will wipe your device (you might want to take a backup if you've already installed a lot of stuff on the device, that's just a button click away also in the Toolkit)
This will boot the device up to a screen giving you the option to unlock the bootloader, with "Yes" selected hit the power button. You'll see some text in the top left corner telling you it is unlocking the device, and then you will see the red "Locked" text toward the bottom of the screen change to "Unlocked". Moments later the device will reboot, and because it will have been wiped you will need to either set it up again or just skip past set-up and get back to the homescreen.
Once you're back onto the home screen, connect as you did before and take the same steps to turn on USB debugging and get the AutoPlay prompt to appear. Then go back to the Toolkit and select the Root option with permanent CWM recovery. All things going well the process will be fully automated from here, it will check that ADB and Fastboot are working, push the SU and CWM files to the device, boot the Nexus 7 into it's bootloader, flash CWM recovery to the device, and then reboot with Root privileges and a fresh new recovery permanently installed.
...or so the theory goes. Using this method I get Root, but CWM recovery is only accessible via command prompt, and I see others having the same problem. So...
Accessing CWM recovery:
In the Root toolkit go to Advanced Utilities by launching it here:
On the next screen select Launch CMD Prompt:
Once the command prompt appears type: ADB reboot recovery - the phone will boot into CWM recovery for you, so you can do things like make Nandroid backups, install zip files and so forth
Installing the 4.1.1 update post-Root and installation of CWM recovery:
Install OTA Rootkeeper by Supercurio from the Play Store here
Open the app once installed and grant it SuperUser privileges
In the app select "Protect Root", and then "temp unroot" the device
Download a zip of the 4.1.1 update here.
Copy it to the internal SD of the Nexus 7
Access CWM recovery as per the instructions above. In this version of CWM recovery you will navigate the options with the volume keys and press the power button to select an option - do that to navigate to "Install zip from SD card" and press the home button
On the next screen go to down "Toggle signature verification" and toggle it until it says "disabled" at the bottom of the screen (it should be set to default to disabled, but you lose like 5s making sure)
Go up to install zip, navigate to the zip file you downloaded in step one and install it
When the device reboots go to OTA Rootkeeper and restore Root, viola! You're done!
So, after all is said and done you should have a Rooted Nexus 7, running the 4.1.1 update, and with a custom recovery that can only be accessed via command prompt. Don't forget to shout WugFresh, the Toolkits developer, a coffee - make a donation here.
Would be nice if you posted that guide on this forum too.
Thanks for the guide.
Oooohh pictures
Caliyork said:
Oooohh pictures
Click to expand...
Click to collapse
You know, for the totally acopic
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Dillon610 said:
Will this work on the new Build number JRO03D? Or should I wait until he updates the toolkit?
Click to expand...
Click to collapse
No idea. You can simply downgrade to an older stock image using his Toolkit though and then follow the same process used in the guide to update to the latest build.
"Meh" at requirement #2:
A windows PC
Click to expand...
Click to collapse
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
JaSauders said:
"Meh" at requirement #2:
I haven't ran Windows for years. I hope there's a way to do this with Linux (assuming a computer is even needed?)
I remember rooting my Optimus T with Z4 root... one click, bingo bango, done.
Click to expand...
Click to collapse
"Windblows"
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
There's a wiki on cyanogenmod.com that explains root.
mario24601 said:
Any way to do on Mac? Also I'm new but what will root do that out of box won't? Any guides that help explain this? Thanks!
Click to expand...
Click to collapse
Should be doable on mac in a windows virtual environment, which seems to be how most mac users are doing things here at XDA.
Actually looking for someone to write "for mac" guides, if anyone is up for that!
There are already few threads about Ubuntu desktop on nexus 7 in this forum. But there is a reason behind why I started a new thread. And that the rest of the threads requires a desktop or laptop with Ubuntu installed to install Ubuntu on your nexus 7. Or it's about running Ubuntu over android Using VNC. But this thread is about installing Ubuntu using a windows PC.
This is a developer edition install it at your own risk.
This will erase your android and all your data so create a backup first.
There is a GUI based installer on Ubuntu desktop to install Ubuntu on your nexus 7 called "Ubuntu Nexus 7 installer". But what if you don't have a PC running on Ubuntu like me. You can still install Ubuntu using your Windows PC(I don't have a MAC but there should be some similarities in this processes).
Things that you are going to need are:
* Nexus 7(Boot-loader unlocked) + USB cable
* Android SDK
* Ubuntu Files
I think you already got the first two of them. If yes download "raring-preinstalled-desktop-armhf+nexus7.bootimg" and "raring-preinstalled-desktop-armhf+nexus7.img.gz" from here.
Once you've downloaded the required files extract the "raring-preinstalled-desktop-armhf+nexus7.img.gz " using a extractor of your choice (I used win RAR). You will get a file named "raring-preinstalled-desktop-armhf+nexus7.raw" now change the extension from ".raw" to ".img".
Now place this two files into "platform-tools" folder under your "Android SDK". Open command window in this folder(Shift + right click for Windows I'm not sure about MAC). Connect your Nexus 7 in fast-boot mode. Now write the bellow command one by one following by enter.
fastboot erase boot
fastboot erase userdata
fastboot flash boot raring-preinstalled-desktop-armhf+nexus7.bootimg
fastboot flash userdata raring-preinstalled-desktop-armhf+nexus7.img
And you are done installing Ubuntu desktop on you Nexus 7. Now reboot your device or write "fastboot reboot" in command window.
Now this is gonna take a while. In my case it took about 7 min to reboot into Ubuntu.
Enjoy nexus 7 like a desktop.
## There are too many bugs. Please report the bugs to help the developers.
## It's more comfortable to use with a hardware mouse and keyboard.
## If you have problem getting on-screen keyboard on log in screen use the device Vertically.
Reference: Ubuntu Wiki
There is already a very extensive thread on this right here in the general section, and has been since it was released 5-6 months ago. http://forum.xda-developers.com/showthread.php?p=33313017
Btw, it can also be installed using multirom, so you do not have to lose your current
Android os, or any data. http://forum.xda-developers.com/showthread.php?p=34577838
Sent from my Nexus 7 using xda premium
Multirom is fun for you because you've got the 32GB and 16GB one. Everyone doesn't.
rebel1699 said:
There is already a very extensive thread on this right here in the general section, and has been since it was released 5-6 months ago. http://forum.xda-developers.com/showthread.php?p=33313017
Btw, it can also be installed using multirom, so you do not have to lose your current
Android os, or any data. http://forum.xda-developers.com/showthread.php?p=34577838
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If I'm not wrong it says "You need Ubuntu to install Ubuntu on your Nexus 7".
But what if you don't have Ubuntu but you have a Windows PC and want to install Ubuntu on your Nexus 7.
I agree with the matter of multirom.
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.
Since Google recently released the second preview of Android M, I've been trying to sideload the OTA through adb. The problem is that my Mac won't recognize my Nexus 6 whenever I plug it in. I have debugging on and change the USB mode to MTP, but still no luck. However, when I change the USB mode to MTP, Android File Transfer recognizes my Nexus 6 and I can go through my device's file system. I've also connected my dad's droid razor m to see if the problem only occurs on my device, but the same thing happens to his phone, too. Since I had no luck on my Mac, I tried to sideload the OTA on my Windows 7 desktop. adb only recognizes my nexus 6 when I have it booted up regularly, but when I put it in recovery mode, my desktop makes the sound that signals it can't connect to my device and it won't show up in adb, either. Any suggestions? I believe adb is set up correctly on both my mac and desktop since I can execute other commands such as "adb version" and "adb help". Thanks in advance!
And here is the device information of my nexus 6 and my dad's droid razor m:
Nexus 6
32GB
not rooted
stock recovery
stock rom - Android M Preview 1
Droid Razr M
8GB
rooted
custom recovery (TWRP)
custom rom - Cyanogenmod 12 Android 5.0.2 nightly build
elvintopalov said:
Since Google recently released the second preview of Android M, I've been trying to sideload the OTA through adb. The problem is that my Mac won't recognize my Nexus 6 whenever I plug it in. I have debugging on and change the USB mode to MTP, but still no luck. However, when I change the USB mode to MTP, Android File Transfer recognizes my Nexus 6 and I can go through my device's file system. I've also connected my dad's droid razor m to see if the problem only occurs on my device, but the same thing happens to his phone, too. Since I had no luck on my Mac, I tried to sideload the OTA on my Windows 7 desktop. adb only recognizes my nexus 6 when I have it booted up regularly, but when I put it in recovery mode, my desktop makes the sound that signals it can't connect to my device and it won't show up in adb, either. Any suggestions? I believe adb is set up correctly on both my mac and desktop since I can execute other commands such as "adb version" and "adb help". Thanks in advance!
And here is the device information of my nexus 6 and my dad's droid razor m:
Nexus 6
32GB
not rooted
stock recovery
stock rom - Android M Preview 1
Droid Razr M
8GB
rooted
custom recovery (TWRP)
custom rom - Cyanogenmod 12 Android 5.0.2 nightly build
Click to expand...
Click to collapse
On Windows, when entering recovery, unplug the USB then reconnect it.
Evolution_Tech said:
On Windows, when entering recovery, unplug the USB then reconnect it.
Click to expand...
Click to collapse
I've tried that, too.
elvintopalov said:
I've tried that, too.
Click to expand...
Click to collapse
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Tech said:
On Windows, when entering recovery, unplug the USB then reconnect it.
Click to expand...
Click to collapse
Evolution_Tech said:
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thanks, I'll see if it works when I get home.
Evolution_Tech said:
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Just tried this out with no luck. Any other suggestions?
I've never used a Mac, so I can't help you there (but from my understanding, it should recognize your device as soon as you plug it in).
As for Windows, you need to install the Google USB driver found here.
Now, this can be a bit of a pain, but it is doable: Depending on how you are connecting to your device, the driver may need to be installed multiple times.
For example:
If you are connected with your device booted into Android, you need to install the driver;
If you are connected with your device booted into the bootloader, you need to install the driver again,
If you are connected with your device booted into the stock recovery, you need to install the driver again,
If you are connected with your device booted into the stock recovery and you select ADB Sideload from the menu, you need to install the driver again;
If you are connected with your device booted into a custom recovery, you need to install the driver again.
Always make sure that you manually install the driver, i.e., right click on the android device in Device Manager in Windows and select Update driver". Then do NOT select "automatically search for the best driver.. blah, blah" or whatever the option is called. Select the second option (something like "let me choose from a list") and then click the "have disk" button, and install it that way.
efrant said:
As for Windows, you need to install the Google USB driver found here.
Now, this can be a bit of a pain, but it is doable: Depending on how you are connecting to your device, the driver may need to be installed multiple times.
For example:
If you are connected with your device booted into Android, you need to install the driver;
If you are connected with your device booted into the bootloader, you need to install the driver again,
If you are connected with your device booted into the stock recovery, you need to install the driver again,
If you are connected with your device booted into the stock recovery and you select ADB Sideload from the menu, you need to install the driver again;
If you are connected with your device booted into a custom recovery, you need to install the driver again.
Always make sure that you manually install the driver, i.e., right click on the android device in Device Manager in Windows and select Update driver". Then do NOT select "automatically search for the best driver.. blah, blah" or whatever the option is called. Select the second option (something like "let me choose from a list") and then click the "have disk" button, and install it that way.
Click to expand...
Click to collapse
AKA: "Windows driver dance"
Good Evening,I'm new to this forum,forgive me if i haven't introduced my self yet. By the way,i have a problem with my Nexus 5:today,as i've been trying to flash the cyanogenmod 14.1 i've encountered a problem,after flashing the recovery (twrp,latest version) my PC can't access internal memory anymore,installed and reinstalled drivers,ADB and fastboot over and over. the problem is that if i open the device manager it shows google nexus ADB Interface. If i write adb devices in the command prompt it shows nothing tho. i have both SuperSU and the recovery installed.
Help me out guys,i don't know what to do.