{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
USB Debugging - On your nexus player go to Settings > About > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Enter bootloader mode - Hold the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Once you are in fastboot mode, the light below nexus player will be blinking constantly. You can verify by using "fastboot devices"
ADB Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal storage (pictures, music, etc.). Copy all important files off the nexus player onto a PC or upload them to a cloud.
Driver Installation
Go to Device Manager, find the Android device, and select Update Driver Software.
Select Browse my computer for driver software
Select Let me pick from a list of device drivers on my computer
Selecting show all devices
Clicking have disk
Finally selecting Desktop\android-sdk-windows\extras\google\usb_driver\android_winusb.inf as the driver
Alternative you can also download and install the Universal ADB Driver.
Downloads
Root:
Android 7.X:
- Coming Soon-
Android 6.X:
http://cord-cutters.wonderhowto.com/how-to/root-nexus-player-0160218/
http://androidflagship.com/16765-root-nexus-player-android-6-0-marshmallow
Android 5.X:
Download the SuperSU zip below. Extract the zip file and you will have (root.img) to platform-tools folder located on your desktop within the android-sdk-windows folder.
SuperSU (Forum Thread) or SuperSU (Direct link)
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 2 main steps: Unlocking the Bootloader and Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the device in future.
Rooting: You can gain root booting up root.img
1. Unlocking Bootloader
Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the nexus player has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
OEM unlock twice
Code:
fastboot oem unlock
Code:
fastboot oem unlock
After you have done, please proceed onto the next section of the guide.
2. Installing a Custom Recovery
http://forum.xda-developers.com/nex...recovery-twrp-2-8-6-0-touch-recovery-t3114717
https://twrp.me/devices/asusnexusplayer.html
3. Rooting
Now that your nexus player has an unlocked bootloader, now this step is to gain root
Android 7.X
- coming soon -
Android 6.X
Require: TWRP, Custom boot.img and flashable supersu
(Refer to above link)
Android 5.0
Warning: This rooting guide is for Android 5.X only!
Boot (not flash) the root image which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and you have extracted it and it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Make sure the nexus player is in bootloader mode
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot boot root.img
This will install SuperSU on your device, once the command has completed continue.
Open SuperSU and update the binaries.
Keep in mind that the first boot may take longer than usual.
Congrats! Your nexus player now has an unlocked bootloader, and is rooted.
==================================================
How to flash factory image for Nexus Player?
1) Download image file for your nexus player - https://developers.google.com/android/nexus/images
2) Boot your Nexus device into fastboot mode.
3) On your computer, use 7zip to extract the .tgz file you downloaded from the Android Developer website. Use 7zip a second time to extract the .tar file you extracted from the .tgz. When you’re done, you should have a folder with several files in it.
4) Copy all of these files and paste them in the platform-tools folder in the Android SDK on your computer. If you followed the above tutorial, this should be under the C drive, then under Program Files (x86) on Windows. Linux users, you know where you put it.
5) If you have not already done so, connect your Nexus device to your computer. ADB and Fastboot commands should already work at this point if you’ve been following along.
There are two flash-all files. If you’re in Windows, you’ll want to double click the one that has the gear logo and says “Windows Batch File” on the right. If you’re on Linux, you’ll want to double click the flash-all.sh.
At this point a box should pop up and you should see the installation taking place. While this is going on, do not unplug your device for any reason. Let it do its thing.
6) Once the installation process as finished, your device will automatically reboot and you can now safely disconnect your device from your computer.
==================================================
Credits:
- Chainfire (SuperSU and Rooting guide)
- Chromium (Easy to understand and detailed guide format)
- DevinWatson (USB driver guide)
- androidauthority (Flash firmware image guide)
Nice guide.
What about installing BusyBox?
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
arecad said:
I have a USB OTG cable but the adapter is female on the available USB side...I am not sure how to go about connecting my laptop/PC to the NP in order to perform ADB commands. Do I need a special cable or is there another way?
Click to expand...
Click to collapse
Don't use the USB OTG cable, use a micro USB cable (same kind of cable that comes with android phones)
I cannot believe I missed that, how embarrassing. Thanks for the response, now I can follow this guide. I was thinking too hard about the OTG cable being a necessary piece of the puzzle.
I am able to get to the bootloader with no problems, I've got ADB and Fastboot installed on my PC, as well as the drivers. However ADB doesn't pick up my NexusPlayer even though fastboot does. Thoughts?
See Attachments
EDIT: Nevermind, I was expecting different responses from adb/fastboot. When in the bootloader adb will not confirm a connection, only fastboot. Sorry for being a noob...
xDragonZ said:
1. Unlocking Bootloader
[*] Turn the nexus player off. Then go into bootloader mode by holding the button on the bottom of the device when you plug in the power cable, or enable developer options and "adb reboot bootloader"
[*] Plug nexus player into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
[COLOR="red"]adb devices[/COLOR]
This command will list the connected devices. If your nexus player serial number shows up you are good to go and may continue. If the nexus player is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under adb devices.
Click to expand...
Click to collapse
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Sleeepy2 said:
Double check to see if you have the latest version of fastboot. I have read that if you don't have the most up to date version the NP is not recognized.
Click to expand...
Click to collapse
+1 this.
goxboxlive said:
AFAIK ADB is for Android, and Fastboot is for bootloader.
But i have the oposite problem. Mine NP is getting recognized useing ADB when normaly booted, but when i am in fastboot mode, fastboot isent working. I get no output when run 'fastboot devivces'. I have both tried to set the NP in fastboot mode by using the hiod button and plug in power, and with adb rebbot bootloader.
Any one have a clue why adb works, but not fastboot?
Click to expand...
Click to collapse
Have you re-installed the Google driver when you are booted in the bootloader? The driver needs to install twice: once when booted into Android, and once when booted into the bootloader
ADB fastboot for Mac Quick Question??
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
MrBoostinduced said:
Hey guys does anyone have any idea on how this can be done on a Mac....I know I know. When I initially plug in my Nexus player with the micro usb, nothing happens on my mac or the Nexus so i am guessing that the drivers are not installed. How would i go about getting these for the Mac? I have already downloaded the slim version of the ADB and Fastboot files with the platform tools into a folder on my desktop named Andriod, so i have these already. And i know that if you hold the button down on the nexus and plug the power in it brings up the bootloader screen. I just need help with the commands in terminal and where to access the drivers from. Also, on the Nexus the Developer options have already been enabled and USB debugging has been turned on. If anyone can help, It would be much appricated! Just started to use terminal commands so yes i am a noob in this department . Thanks agin in advance.
-Jason
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Sleeepy2 said:
http://developer.android.com/sdk/win-usb.html
"Note: If you're developing on Mac OS X or Linux, then you do not need to install a USB driver. To start developing with your device, read Using Hardware Devices."
http://developer.android.com/tools/device.html
Click to expand...
Click to collapse
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
MrBoostinduced said:
Hey Sleepy2, I just did a brief read through and it states this:
Set up your system to detect your device.
If you're developing on Windows, you need to install a USB driver for adb. For an installation guide and links to OEM drivers, see the OEM USB Drivers document.
If you're developing on Mac OS X, it just works. Skip this step.
If that is the case, what would you suggest doing next? Thanks again for helping!
Click to expand...
Click to collapse
Open a terminal, navigate to the directory where you downloaded fastboot and go ahead with the commands shown in the first post. You will probably have to add a "./" in front of the commands given that you are on a mac, e.g.,
Code:
fastboot devices
becomes
Code:
./fastboot devices
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
knobbs said:
I seem to be having the same problem as goxboxlive. I have tried installing the drivers about 100x tried on several computers and rebooted many a time. The only thing I can think of from the posts in here was to update fastboot but I dled the android studio and I would assume that has the latest version in there? Otherwise I couldn't find somewhere to download just fastboot from. Any help or recommendations or where I can dl the latest fastboot?
---------- Post added at 02:28 PM ---------- Previous post was at 01:57 PM ----------
Follow up. Got it to work. In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
midnightzak said:
I could be mistaken, but when you're in the bootloader you're going to use FASTBOOT and not ADB commands. So therefore the command should be "fastboot devices" instead of "adb devices"?
Click to expand...
Click to collapse
knobbs said:
In the guide it says after booting into fastboot to type "adb devices" in the console. You should instead type "fastboot devices" to see if you have the correct drivers and then go on from there. This worked for me, hopefully it will help someone else too.
Click to expand...
Click to collapse
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
To avoid further confusion, I've updated the post since the OP hadn't yet.
midnightzak said:
Yep, i posted this earlier in the thread, kinda surprised OP hasn't updated it.
http://forum.xda-developers.com/showpost.php?p=58172001&postcount=7
Click to expand...
Click to collapse
efrant said:
To avoid further confusion, I've updated the post since the OP hadn't yet.
Click to expand...
Click to collapse
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
xDragonZ said:
Thank you, saw your post that time and wanted to change it but keep forgetting.
Currently working on some basic developer app for Nexus Player.
Click to expand...
Click to collapse
It's all good, wasn't terrible let to figure out, and if you're developing even more for the Nexus Player, the more power to ya! Keep it up!
Related
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
deocare said:
Hi, I am new to rooting my tablet. I manage to unlock my tablet "asus tf700" but i cannot for the life of me understand how to root this. I have read all the threads/posts regarding this issue but since its my first time i dont understand what "flashing" means or "bootloader". Please any step by step advice is greatly appreciated.
I have the ASUS TF700T Infinity Jellybean Android 4.1.1 I believe it is unlocked because I am able to go into that screen and theres four Icons.
Pms or a step by step guide for this noob because i dont understand any of these terms =(
Sorry for the trouble and thanks in advance
Cheers,
deocare
Click to expand...
Click to collapse
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
deocare said:
also tried reverting back to ICS to do that auto root but had no idea what "fastlooader" was..
sorry im a total noob at this
Click to expand...
Click to collapse
Not too worry, it's very simple, just download the zip, then unzip and double click on the bat file, then follow on screen instruction.
Here is a nice instruction for rooting:
http://tutznet.com/root-tf700t-asus-...-infinity.html
this will work with the specs for my tablet? jellybean etc..?
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
deocare said:
does not work... i tried this debug already it says failed i think because it doesn't support jellybean.
Click to expand...
Click to collapse
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
buhohitr said:
no, it's for ics only, I thought you are on ICS? well you downgrade back to .30 then use my method above, If you don't want to downgrade, then you must unlocked first then follow this method:
http://forum.xda-developers.com/showthread.php?t=1916762
You put your device in fastboot mode, by turn off your device, hold volume down and power button, when you will see white text appeared on the screen release both, hit volume down to navigate to the USB icon, then hit volume up to select and now you are fastboot. plug in your usb cable then open fastboot command on your pc and do your thing.
Click to expand...
Click to collapse
sorry i dont understand that concept of flashing can you go through it with me on how to do it
deocare said:
sorry i dont understand that concept of flashing can you go through it with me on how to do it
Click to expand...
Click to collapse
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
buhohitr said:
Not a problem, but I need to verify what your setup first.
1. Are you on Jelly Bean?
2. Are you unlocked? (when you turn on your device, it should displays "device is unlocked"
3. Do you have SDK and fastboot/ADB tool installed on your device?
Once you answered all 3 questions, I will recommend the easiest way to root.
Click to expand...
Click to collapse
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
deocare said:
1.yes
2.yes
3. maybe? not sure i have been trying alot of random things trying to root it so im not sure if its installed on my device
Click to expand...
Click to collapse
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
buhohitr said:
OK, we need to verify if your fastboot is working or not. Put your device in fastboot mode (see my thread above..how to select the usb icon). On your pc, go to the folder that you have fastboot command (should be fastboot.exe). Open window command prompt, navigate to the folder where "fastboot.exe" located (usually located in "platform-tools" folder), then execute this :
type in:
fastboot devices
hti enter, you should be device ID show up
again type:
fastboot reboot
then hit enter
Your device should reboot. If it does, your fastboot is working.
Click to expand...
Click to collapse
i dont know where this fastboot.exe is
is there a link i can get it from
deocare said:
i dont know where this fastboot.exe is
is there a link i can get it from
Click to expand...
Click to collapse
Here you go, instruction and fastboot download.
http://forum.xda-developers.com/showpost.php?p=27218675&postcount=20
okay i have no idea it does not work i opend cmd prompt got the bootloader but the commands dont work heres a Screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
thunderger said:
@deocare
first you have to "cd" into the path wehre you store the fastboot.exe.Ideally you've installed a full android sdk with adb, etc. After setup your android sdk and fastboot, make sure that you're tablet is booted in fastboot mode and you've installed the fastboot drivers, e.g. from universal naked driver package. After this you can send fastboot commands to your tablet but please note that it doesn't answer to fastboot devices.
Here are some threads explaining how to setup fastboot and how to after flashing jellybean, e.g. chainfires SU.
Click to expand...
Click to collapse
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
deocare said:
I installed the drivers already i believe i checked under portable devices and it says "TF700t transfomer pad.." and I am in booted in fastboot mode with the power+volume down key and went over to the USB icon then opened cmd prompt
Click to expand...
Click to collapse
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
buhohitr said:
Based on your screen shot, you put the "fastboot folder" on your desktop. Do this.
open cmd
type:
cd\ then hit enter
you should see:
c:\
now type:
cd users\david\desktop\fastboot then hit enter
you should see
c:\users\david\desktop\fastboot>
now type:
fastboot devices then hit enter
you should see device ID
now type:
fastboot reboot then hit enter
your device should reboot.
Click to expand...
Click to collapse
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
deocare said:
i am gonna assume it is not installed properly doesn't show devices and it says rebooting but doesn't.
Click to expand...
Click to collapse
Do you have your table booted in fastboot mode and usb cable plug into your PC?
i doo
deocare said:
i doo
Click to expand...
Click to collapse
OK, you problably don't have android sdk instalaled. Here is the link to install SDK. When you run the sdk installation, only select anything with android packages and install, don't install everything.
http://forum.xda-developers.com/showthread.php?t=1616059
Another question is are you planing to install custom ROM??? or you just want root?
I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .
cuibapngo said:
I have an acer a700,but i updaded to jeally bean,please help me root this device.thanks .
Click to expand...
Click to collapse
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot
Vorbeth said:
First I think you need to learn to post in the right section.
Then Learn to READ in the right section!
See it's EasyRoot
Click to expand...
Click to collapse
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english
cuibapngo said:
So,i just want to root,i҆m happy with romstock,not romcook.i want root to install apps that requires to root such as:titanium back up,root explorer....
Here information my device:
Model number: a700
Android vesion: 4.1.1
Kenel vesion: 3.1.10+
Image vesion: acer av501-pa-a700-rv18rc01-pa-cus1
Build number: 1.502.00-pa-cus1
Image p/n: fm.s1ma0.04a
Is this successful?i҆m newbie,so i҆m a little scared if unsuccessful
Later i want use romcook,still can be up to normal or not?
thanks for bothering you
Sorry my english
Click to expand...
Click to collapse
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD
Moscow Desire said:
Just run Vorbeth's EasyRoot. You won't mess anything up.
MD
Click to expand...
Click to collapse
thank you.i will try: Ngón tay vượt qua:,but please guide supplied by one of the images?because
i may not post new threads, may not post replies, may not post attachments
i may edit my posts: Khóc:
here is one of the questions?
You need:
-Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean(this is whehe i have to download?)
-ClockworkMod Recovery - 6.0.1.5 or newer(i have downloaded 2files.1 is recovery a700 6015. 1 is recovery a700 6015 touch.so spend what?)
Download:
A700 EasyRoot 2.0 md5: 8876aca04e29fe69d7368bc02006359c(there to 12files.down all always?down to set in place?it is not a zip file?
-How to flash:
Download zip and place it on your virtual or external SD card
Boot your phone into ClockworkMod Recovery (via adb or with a key combo)
In main menu, select "install zip from sdcard"
Select "choose zip from sdcard" and browse to the location of zip
After flashing process is complete, reboot the device
Alternative install for Stock patched kernel ONLY:
Reboot to bootloader
Extract boot.img from the zip
Flash boot.img via fastboot
How to get root:
Install SuperSu via CWM
Install BusyBox from Play(these steps can you give me one of the images?)
-Download:
Stock patched kernel md5: 4638ffe2bcb00352ccc702fdfab1d8cb(link die)
iconiaN source built kernel md5: 76b8e1020c6054debedf60efffdca609(link die)
please guide me in detail,thanks for bothering
No one to guide me out?
cuibapngo said:
No one to guide me out?
Click to expand...
Click to collapse
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD
help me
grigaman said:
Help please. I tried to establish root on the A700 in the second way. But I didn't notice that this way is available for 4.0.4, and on my tablet was established 4.1.1. At me at inclusion gives out here such and more than anything. The debugging mode joins and determined by USB by the computer, but I don't know what to do, prompt please! And still it doesn't load updating with SD the card. And before doing root I unblocked the loader
Click to expand...
Click to collapse
please help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moscow Desire said:
Dude, it's pretty easy.
1. Unlock your bootlooader. To do this, go into tablet /Settings/Development Options and select USB Debugging.
2. Plug your tab into PC (your Acer USB drivers must be installed first)
3. Open a Command Window in the folder you downloaded all those files. (shift & right mouse click)
4. Check to make sure ADB is working by typing adb devices (you should get some numbers) if not, you have a windows driver issue.
5. Type adb reboot bootloader (tab should reboot to bootloader)
6. Type fastboot OEM unlock (you should get a couple of images. One with an unlock, and one with a lock door) Use Vol - to switch between the 2. Use vol + to select. You have to be quick, as it times out after 5 seconds or so.
When you reboot, it should say bootloader version number (unlocked mode) or something similar.
Go back to the Command window, and run the batch file. "easyroot.bat" by typing in easyroot.bat , then hit the Enter button. The batch file should install all you need, You may need to select things that it prompts you for.
No, there's not a video, as it ain't rocket science. If you can't understand these instructions, perhaps it is better if you do not root your tablet. Doing this, is not for everybody.
Also note, once you unlock your bootloader, you can no longer get OTA from Acer. And, once you unlock it, you cannot lock it back. Not without installing a whole new stock rom.
Also, next time, post your questions in the Q&A forum. Otherwise, nobody will answer them.
MD
Click to expand...
Click to collapse
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?
cuibapngo said:
so,i haved I downloaded the usb driver and sdk on my pc and then
First, i install usb driver.sau I plug my A700 to the PC, I did not see what happened. do not know my tab has been updated to the new driver?
*I download the sdk for it in the c drive (because when I extract it, do not see the files installed)
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
I do not know to type the path to the sdk, it's all wrong! I to the sdk folder in c / program files/adt-bundle-windows-x86 .đặt thư mục sdk ở program files có đúng không?
Click to expand...
Click to collapse
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.
Moscow Desire said:
Dude. Why are you messing with the Android SDK? When you mess with the SDK, you also have to install the Java JRE kit as well. Then, you have to modify your PATH and CLASSPATH on windows, or else you'll get the messages you got.
I thought you just wanted to get Root on your tablet. Everything you need is in the package that Vorbeth has for easyRoot. His package contains adb.exe, fastboot.exe, and the windows dll's necessary to do it from the folder you saved them all too. Leave the SDK alone unless you know what you are doing.
Click to expand...
Click to collapse
wow.not need unlock boadloader that still root?thanks.i try.
cuibapngo said:
wow.not need unlock boadloader that still root?thanks.i try.
Click to expand...
Click to collapse
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD
Moscow Desire said:
You still have to unlock bootloader.,
But run your commands in the package you downloaded. (adb and fastboot). You don't need the SDK for this.
MD
Click to expand...
Click to collapse
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?
cuibapngo said:
xin please guide me add a few more, i open test adb và fastboot is it to open but it running very fast and auto closed back.is it wrong?
so, run easy root first or run adb with fastboot first?
Click to expand...
Click to collapse
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.
cuibapngo said:
I'm having a little trouble with adb and fastboot.i can not to open it.i open with right click and run as administrator, it runs fast and close automatically. above my tab do not see anything.i`ve tried turning off my the computer and tab and then do it again but still does not work. How can I do?
can i run the easy root without running adb command and fastboot?
at run adb and fastboot commands to shutdown tab? think is not it.
Click to expand...
Click to collapse
You MUST open a CMD (command) Window first.
In the folder you downloaded all the stuff to, find a nice empty place (DO NOT SELECT A FILE),
Hold your SHIFT key, and then do a RIGHT MOUSE CLICK
Then, select Open Command Window
You should have a black window, with the directory path. If you don't, then you have issues with your PC.
Next, (where you see the little flashing curser) type in adb devices then hit ENTER
(make sure the pc recognizes your tablet. You should see something like, killing dameon server :devices attached with several numbers)
Type adb reboot bootloader then hit ENTER
(tab reboots to bootloader)
use your left VOL- key to navigate between locked and unlocked. Use VOL+ to select
Reboot your tab. Should say unlocked mode on boot.
Then go back to that black Command Window, and type in adb devices and hit ENTER (once again, you should see your device like the first time)
Then type in 701easyroot.bat and hit ENTER
Should see some stuff, mostly warnings. But at this point, it will ask you to;
1. Keep your stock Recovery
2. Install the CWM Recovery
if you select 1, program quits, and you can just reboot your tab, because as soon as you ran the bat file, it rooted it.
MD
help!!!!did come here.and began restart my tab and it is the following message:
BOOTLOADER VJB-653B3D3 STARTING USB DOWNLOAD PROTOCOL
it stood like that for 20 minutes without seeing anything like couple of images.....lock or unlock
ell.i fear brick my tab, but luckily I power off and then turn it back to normal
type in 701easyroot.bat or easyroot.bat?
what can i do next?
well well, missing the fastboot oem unlock command to unlock
hen I opened the lock, I run orders easy root.bat.and I choose number 1.My tab runs report success, but I do not see superuser file on my tab?I tested the software files explorer, it says your device is not root?
What do I do next?
help help help!!!!!!!!!
can anyone here help me?MOSCOW DESIRE, where are you?
I tried to go back to work 3 times, but the result is the same.said root successful.including selecting the number 2 to do all over again the next time I do look closely and see the following message:
can not load root / boot.img
and then:
can not load root / recovery.img
I press continue and it indicates a successful root as shown. but there is not anything
what's wrong?
no one to help me?:crying::crying::crying:
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
SDK
Washedman said:
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
Click to expand...
Click to collapse
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
lj50036 said:
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
Click to expand...
Click to collapse
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
fastboot/adb
Washedman said:
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
Click to expand...
Click to collapse
Fastboot.exe/adb.exe in the root of your local hard drive
lj50036 said:
Fastboot.exe/adb.exe in the root of your local hard drive
Click to expand...
Click to collapse
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Washedman said:
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Click to expand...
Click to collapse
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
lj50036 said:
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
Click to expand...
Click to collapse
Nothing. It returns no string, letters or numbers. Blank. I tried every combination of ports and cables and drivers. Getting a bit frustrated.
I had a similar problem with flashing a custom recovery on the tf700 as well (mainly because of the dock), so let me share with you a few pointers that may help you fix this (it certainly helped in my case):
1. Never do any flashing, adb or fastboot with the tablet docked, especially when flashing recovery: I spent three hours scratching my head figuring out why I couldn’t flash the recovery (fastboot stuck at sending file), only to find out that everything worked perfectly when I removed the dock. In my opinion, the dock makes things unpredictable, so do everything with the dock.
2. As for adb and fastboot, you should just start setting up from scratch as it is always easier than troubleshooting for errors. After unlocking the bootloader using ASUS tool, what I suggest you should do are as below:
a. Uninstall COMPLETELY your current adb/fastboot drivers and install Universal Naked Driver 0.73 (http://forum.xda-developers.com/showthread.php?t=2513339). Take note of the warning in red on how to uninstall existing adb driver.
b. Also take note that you actually need 2 sets of drivers, 1 for adb and 1 for fastboot (which are both included in the Universal Naked Driver). When you connect your tablet with Android running to your PC, you are installing driver for adb. With the driver properly installed, “adb devices” command will work and give you the list of connected devices to your PC through Windows’ CMD. Please also Google or search xda for adb files (no need to download the whole Android SDK just to get those adb files).
c. After successfully installing adb driver, you can manually reboot your tablet into fastboot mode through the button combo (power + volume down) with the tablet still connected to your PC. By then, your Device Manager should have another device listed as fastboot device. Again, follow the steps in the link to uninstall and reinstall fastboot driver. With this set up, you should be able to run “fastboot devices” command.
d. With fastboot, you can now flash a custom recovery. As a side note, since all this flashing custom recovery and ROM can potentially brick your tablet, after you have finished fixing adb/fastboot and get your ROM running, I strongly suggest you follow this link to obtain nvflash (http://forum.xda-developers.com/showthread.php?t=2455925) and make your tablet unbrickable. I actually did this before flashing a custom ROM, but I honestly don’t know if the timing makes any difference.
So after a lot of headache and messing with drivers, 3 machines, 1 grumpy wife and staying up until 4am. I figured the issue wasn't the drivers. But the version of ADB and Fastboot which I was trying to use. That and the USB hub I was trying to go through.
The way I solved the issue was to install the tools and drivers from the following thread and to plug directly into a USB port rather than a USB hub:
http://forum.xda-developers.com/showthread.php?t=2588979
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
CSquared4290 said:
Hey guys, I've long had this issue with my OnePlus One and I for the life of me cannot figure it out after searching and reading mad threads/forums.
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
So I'm following all the instructions possible step by step. I have my OPO in Recovery (TWRP 2.8.6.0) and it won't show up as an ADB Devices...
Yet, noting key parameters here:
- All my drivers are up to date
- My Android SDK is up to date
- Java SE is up to date
FastBoot - Phone is recognized (picture below).
ADB Sideload Mode in TWRP Recovery - ADB Sideload recognizes OPO, but doesn't work still.
But standard ADB is not listed when Recovery is on main page. But I get this prompt whenever the phone boots into recovery or I plug it in via USB when Recovery is active.
This is my command prompt to prove FastBoot recognizes my device, but ADB does not.
What am I doing wrong? Can someone help me? I've noticed this issue as long as I can remember, and have resorted to always having to copy my ROM files through the OS, doing a factory reset, then installing. I have never been able to use ADB Push.
Can someone provide me some pointers?
Thanks!!!
Click to expand...
Click to collapse
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Thanks Mr. Hoax! I will give that a try and report back.
Interestingly in an attempt to use ADB Sideload to install the latest ROM update from scratch, I took a gamble and did a full format/wipe and was able to install the OS using ADB SideLoad. But afterwards, it still didn't come up under ADB Devices...But will try your recommendations and see what happens.
Elkhantar said:
do you have debugging enabled on the phone, and if you do, have you authorized that computer on the phone? (I guess you have already, but just throwing out some ideas you might have forgotten)
Click to expand...
Click to collapse
Yessir, Debugging was enabled through the OS (I don't know of any other way to enable debugging?)
Mr hOaX said:
Firstly, uninstall all the drivers for your OPO from device manager and restart the system
Now, follow this link to install drivers >> http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
After this, install adb and fastboot files >> http://forum.xda-developers.com/showthread.php?t=2317790
Even I have Android SDK installed on my system for developing apps, however, I used above steps to ensure that my system recognises my OPO
Click to expand...
Click to collapse
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Wug's tookit for bacon hv step by step procedure to install adb n fastboot drivers...gv it a try...i did it myself n it works nice
1+1
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
After drivers installation is done, you need to reboot your OPO in bootloader(fastboot) mode and type
fastboot devices
And check out if the prompt shows your device serial number.
I see you're using the nexus driver. Perhaps try a Samsung ADB driver. It works with my phone without problems.
I get the same problem with my work PC, while everything works fine at home.
What CSquared4290 says, applies here:
Computer OS: Windows 7 x64
Problem: OnePlus One NOT RECOGNIZED under command > adb devices.
- All my drivers are up to date
- My Android SDK is up to date
The phone is recognised normally under command > fastboot devices.
Symantec Endpoint Protection is running at my work PC. Could this be a reason?
CSquared4290 said:
Hey Mr. Hoax. I tried those steps, uninstalled every driver I could associate with any of my Android devices (have an HTC One as a backup) and sadly, ADB is still not recognizing my OPO when I enter "ADB Devices".
However, I still get the Windows prompt. Any clue?
Click to expand...
Click to collapse
100% agree with the other posters, really delete all of your old USB ADB drivers, including the Google USB driver. Here's a tool I use for that: http://www.nirsoft.net/utils/usb_devices_view.html
Install Samsung ADB drivers, then when you plug your OPO in you should be able to see it in Device Manager as "Android Device" don't let Windows pick the driver. Right click and pick the browse my computer for drivers, then find the Samsung Android ADB Interface, install that. Unplug your phone, then plug it back in...profit? Good luck!
From my OnePlus X rooting guide. It looks like you need to install the universal adb driver linked in #2 and follow the steps in #3.
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
Click to expand...
Click to collapse
Warning if your intent is to Unlock the Bootloader.
At this time 24 Sept 2017
There are no Stock Firmware Images, No Custom Recovery, No Root Method.
Without any of those available Unlocking Bootloader has little Value, and lots of risks.
Official PH-1 windows drivers are up, with Official builds.
https://essential-live.herokuapp.com/developer/current-builds thanks for update @bmg1001 -14 Nov 2017
I haven't seen any Official Windows USB drivers (adb/fastboot) posted any where so i just used Google Pixel Drivers.
Official Google Drivers
Selecting correct drivers in Device manager
Adb seems to work with Windows default drivers, but i had to update ADB.exe version
SDK Platform-Tools for Windows ~3MB
If you have never used ADB
[Index] Setting up and Using ADB/Fastboot
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
Enabling Dev Options
See post #2
ADB Setup/ Troubleshooting
See post #3
Enable Dev Options..
Settings/About phone
Tap on Build number, until you see "You are now Developer"
Back up one screen (Main Settings Page)
tap Developer options
Optional
Toggle on Stay Awake (if you are new to this)
If you are plan on Unlocking Bootloader
Toggle On OEM unlocking
Select Enable (on popup window)
Required
Toggle On USB debugging
Watch for Allow USB debugging popup on Phone
recommended
check box Always allow from this computer
then OK
Testing ADB setup by booting to bootloader
Code:
adb reboot-bootloader
If that code doesn't work you may need to update adb
Fastboot setup
Fastboot commands only work with the device in Fastboot/Bootloader Mode
Boot the Device to Bootloader Options
Code:
adb reboot-bootloader
Power off, Hold Volume Down Button, Power On
Connect To PC via USB
Open PC Device Manager (Settings/Devices/Device Manager)
Look For Mata
Update Driver (Right Click on Mata)
Browse My Computer for Driver Software
Let Me Pick from a List of Available Drivers
Select your Device's Type: ADB
Select the Driver ypu want to Install
Manufacture: Google
Model: ADB Testing (there may be a better one)
Select: Next
PH-1/Mata should look like this
If You don't see adb drivers in available drivers
Try installing l Google Drivers in post #1
I'm using the minimal adb&fastboot, do you think that's the problem?
edit: see attached thumnail, I looked at your photos and followed the instructions. On my windows I get the following options. I tried the two "ADB testing interface" options and neither seem to allow me to perform fastboot commands. If I type fastboot devices nothing happens while the device is in fastboot mode. The ADB commands while the device is powered on do work though.
elsamuraiguapo said:
I'm using the minimal adb&fastboot, do you think that's the problem?
Click to expand...
Click to collapse
no, you need to select the correct driver in Device Manager
Looks like Minimal ADB and Fastboot hasn't been updated since 6th January 2017
So that could be an issue
Updated post #4
to explain images in post #1
sd_shadow said:
no, you need to select the correct driver in Device Manager
Click to expand...
Click to collapse
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Is yours the Sprint variant?
elsamuraiguapo said:
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Click to expand...
Click to collapse
Doesn't look like that has been updated since October 2016
i would use the ADB files direct from Google, link in post #1
Is yours the Sprint variant?
Click to expand...
Click to collapse
No, but if bootloader wasn't Unlockable, the OEM unlocking option in Settings should be Greyed out and unselectable
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05
adb-setup-1.4.3.exe
has adb version Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android
and fastboot commands didn't work for me with Mata
ADB version working for me is
Code:
adb version
adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
sd_shadow said:
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
Click to expand...
Click to collapse
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
elsamuraiguapo said:
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
Click to expand...
Click to collapse
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
sd_shadow said:
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
Click to expand...
Click to collapse
Well I uninstalled all the drivers I could find on my computer to start from scratch. Which should I install? I can't figure out how to install the google usb drivers referenced above
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
sd_shadow said:
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
Click to expand...
Click to collapse
Okay awesome, I think we're almost done. When I type in fastboot devices I can see the device now. Starts with PM1. What command did you use to unlock the bootloader? I tried fastboot oem unlock and "fastboot flashing unlock" and it failed. (remote: unknown command)
Edit: Never mind it worked now after a few attempts. Weird cause I typed the same command over and over and it kept failing. Anyway looks like it rebooted successfully after the factory reset. Thanks for your help mate. Now I can set up the device to my liking and just wait until we get customer recovery and root.
Hi guys, same issue here with OPENUS version of the MATA PH-1.
I have installed 15 seconds ADB driver 1.43 clean on laptop and can access the phone with ADB and reboot it into bootloader.
However, 'fastboot devices' gives me nothing. I've updated the Mata in device manager first with the options from the 15 seconds ADB, with are 'Android ADB Interface', 'Android Bootloader Interface' and 'Android Composite ADB Interface'. None of them give me any luck when trying 'fastboot devices', nothing found.
Then, uninstalled the ADB driver from device manager so that it showed Mata again, installed Google driver from 1st post, but same thing: version 11.0 of Google drivers (28/08/2014) with same choices, but none of them work.
Does this have to do with the USB A 3.0 --> USB C cable maybe? Or is it just a driver thing?
BTW reason for unlocking is so that I can root later without wiping the device, once root becomes available..
updated post 1 a bit