Related
I am trying to learn how to use ADB, so I can find the cause of a problem I am having on every 2.xx Rom I have tried, and I have tried them all!
So take a look at the screen shot, and you can see it finds my phone. For some reason thats as far as I have gotten, been screwing with it for 2 days but alas I have to ask!
Thanks for any help you can be!
Roman
OK, at a quick glance....
Instead of just typing "logcat", try "adb logcat". I think you'll have better luck.
Still looking through the rest, will edit in a few minutes.
EDIT 1: Don't actually put the "#" or the "$" on your command line. Those are prompts that the shell presents to you, not something you're supposed to type.
EDIT 2: Add the sdk\tools directory to your path. It will make your life much easier. You can get away with just doing a "cd" to that directory, but in the long run things will be much easier if you just put it in your path.
EDIT 3: "Operation not permitted"????? That command should have worked. Have you rooted your phone yet?
do adb "insert command here" logcat push pull install etc...
Cool thanks for the help subliminalurge, I think I got it now!
Now to start my bluetooth headphones with 1.5 and grab a log, then load up 2.1 and grab a log and see what the HELL is wrong!
Thanks again!
One last question, is it possible to save a whole string from CMD!
Also how do you do a dalvik wipe?
These are the 2 commands I have! Not sure if either one work or not!
DALVIK WIPE:
adb remount
adb shell
# cd /system/sd/dalvik-cache
# rm *
adb reboot recovery
adb shell mount /data
adb shell rm -r /data/dalvik-cache
I havent used adb since rooting my g1, since the release of the flashrec method.
Heres my noob question
Can terminal emulator do the same things as adb?
The only thing id ever use adb for is to push/pull, and i just use root explorer for that.
Jesus, youd think i became a senior just by spamming...
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
mrinehart93 said:
Terminal Emulator can not do the same thing as ADB. ADB is Android Developer Bridge (bridge as in computer to phone connection). Terminal Emulator, if you know Linux terms, emulates a Linux terminal on the phone... so, if you do "adb shell", you'll have the same commands as you would in terminal emulator... sorry I'm confusing
Click to expand...
Click to collapse
Lol i see what you mean.
You need adb to theme, dont you?
Windows man, through and through
(oh the irony, of being such an android patron...)
After searching and having a headache for 5+ hours I wanted to make an easy how to for noobs running ubuntu 10.10.
I found a ton of information on a ton of sites, and after a lot of cross post referencing I finally figured it all out, so I will lay this out in as simple a way possible so nobody has to have the same issues I had.
Pre-requisites: latest android sdk, ubuntu 10.10, general knowlege of linux
Step 1. Obtaining and making fastboot/adb executable
Download THIS package containing the fastboot binary and the 70-android.rules file
extract files anywhere (remember for later use)
copy fastboot binary to your /android-sdk-linux_86/tools/ folder
open terminal and execute
Code:
chmod +x <path to>/android-sdk-linux_86/tools/fastboot
chmod +x <path to>/android-sdk-linux_86/platform-tools/adb
Step 2. Adding your tools and platform tools directories to the path
in teminal execute
Code:
gedit .bashrc
at the end of the file insert
Code:
# enable android tools directories in path
export PATH=${PATH}:~<path to>/android-sdk-linux_86/tools
export PATH=${PATH}:~<path to>/android-sdk-linux_86/platform-tools
Step 3. Getting ubuntu to recognize your phone in adb and fastboot
in terminal execute
Code:
sudo cp <path to>/70-android.rules /etc/udev/rules.d/70-android.rules
sudo chmod a+rx /etc/udev/rules.d/70-android.rules
sudo reboot
Step 4. Make sure it works
after reboot open terminal and execute
Code:
adb devices
as long as it returns a device with HTXXXXXXXXXX you should be golden
There's a typo in the Android SDK paths in your message. You're missing the x in _x86. Was wondering why adb wasn't in my path after I copy pasted that into my .bashrc.
Here's the correct forms.
Code:
chmod +x <path to>/android-sdk-linux_x86/tools/fastboot
chmod +x <path to>/android-sdk-linux_x86/platform-tools/adb
Code:
# enable android tools directories in path
export PATH=${PATH}:~<path to>/android-sdk-linux_x86/tools
export PATH=${PATH}:~<path to>/android-sdk-linux_x86/platform-tools
Another thing that puzzled me was that there appears to be a hard coded username in the udev rules file. Should that be edited too?
Yes, you need to update your udev rules:
http://forum.xda-developers.com/showthread.php?t=640158
I cant seem to find the path to /70-android.rules /etc/udev/rules.d/70-android.rules.
Not sure what you mean?
Try this method
Rogoshin said:
I cant seem to find the path to /70-android.rules /etc/udev/rules.d/70-android.rules.
Click to expand...
Click to collapse
Dude, I put these instructions together sometime in 2010, and should be easy enough to follow. Following all those other instructions used to have me trying for hours to set up adb & fastboot, so when I got a little more familiar with Linux I made my own, with root permissions, so you don't have to sudo anything. You can have adb & fastboot up and running in 5 minutes, if you follow the instructions step by step. http://forum.xda-developers.com/showthread.php?t=820122
blas4me said:
Dude, I put these instructions together sometime in 2010, and should be easy enough to follow. Following all those other instructions used to have me trying for hours to set up adb & fastboot, so when I got a little more familiar with Linux I made my own, with root permissions, so you don't have to sudo anything. You can have adb & fastboot up and running in 5 minutes, if you follow the instructions step by step. http://forum.xda-developers.com/showthread.php?t=820122
Click to expand...
Click to collapse
Well it did not work for me. In step 2 when you have to add auto prompt I get this error "Can't create user application configuration folder /home/rogoshin/.local/share/applications: Not a directory".
What i was looking for is the 70 android rules file.
You create the 70 Android rules file yourself...
danger-rat said:
You create the 70 Android rules file yourself...
Click to expand...
Click to collapse
I thought it was in the link, but the link does not work for me.
If I create the file myself, where do I get the content?
Sendt fra min Galaxy Nexus med Tapatalk
Talderon said:
As stated by DEEsx1 the following is correct:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
However, it has been a mystery as to why the following location/file does not work for everyone:
Code:
/etc/udev/rules.d/51-android.rules
I am running Ubuntu 9.10 on my laptop with nothing special, just a straight load. the 51-android.rules code did not work for me.
I searched around on a few linux/android forums and found that some people had luck with creating the following file:
Code:
/etc/udev/rules.d/90-android.rules
However, that did not work for me. I had to create the following file:
Code:
/etc/udev/rules.d/99-android.rules
Now, if you are still getting the error, you don't need to reboot, you just need to restart udev:
Code:
sudo /etc/init.d/udev restart
You may also need to restart the adb daemon:
Code:
adb kill-server
adb start-server
adb devices
Now, worse case that I have seen, make sure the phone is not plugged into the computer, reboot the system AND the phone then try again (I have only seen this once).
Hope these tips help!
Click to expand...
Click to collapse
rotohammer said:
Welcome to Linux!
Actually, the more you use it, you'll find that you'll pickup these bits along the way, just like this.
The files are processed in order of their name so 51-xxx is mid-way through, 99-xx is at the tail end of the processing order. Sometimes, the order is important.
Also, after posting the wrong info to you earlier, I deleted the entry I posted. But, it turns out, the Nexus one poses as both id numbers. While in Android its VendorId=18d1, but in the bootloader (waiting in fastboot usb), the VendorId=0bb4.
So, I put both lines in one file today and all is well again.
I.e:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
and I changed my filename to 99-android.rules
then ran:
sudo restart udev
and now I can access the phone as a non root user again, either from adb or fastboot-linux.
Click to expand...
Click to collapse
This should be sufficient...
The auto script creates it for you, but up must have your phone connected for it to add your device id
Sent from my Nexus One using xda premium
blas4me said:
The auto script creates it for you, but up must have your phone connected for it to add your device id
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
auto script i am not sure i follow
It's a script that automates the process...
danger-rat said:
It's a script that automates the process...[/QUO
Where is this script?
Sendt fra min Galaxy Nexus med Tapatalk
Click to expand...
Click to collapse
The link is in my first post, pay attention!!!!!!!!!!
Sent from my Nexus One using xda premium
blas4me said:
The link is in my first post, pay attention!!!!!!!!!!
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
After i have completed all the steps, i tried the last command and got "no such command". I tried android rules 99, but maybe with Ubuntu 11.10 i should try a different number.
Sendt fra min Galaxy Nexus med Tapatalk
Try restarting udev, or enter root session on your fs, and make adb and fastboot executables, then restart udev.
Sent from my Nexus One using xda premium
blas4me said:
Try restarting udev, or enter root session on your fs, and make adb and fastboot executables, then restart udev.
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
This might be the root of the problem, because in usr/local i cant find adb or fastboot.
Hey everyone! I put together some information on how to do a few things on your new Ouya! This info is by no means my own original contributions, but rather just a compilation of several different sources that I discovered through my quest to explore my Ouya. All credit goes to the original authors/brave experimenters.
SDK SETUP:
1. Install the Android SDK
2. Open SDK Manager and install the following packages:
- Tools: Including both Android SDK and Android SDK
- Android 4.1 (API 16): SDK Platform
- Android 4.0 (API 14): SDK Platform
- Extras: Android Support Library, Google USB Driver
3. Navigate to /android-sdk/extras/google/usb_driver
4. Open android_winusb.inf in an editor (I use Notepad++)
5. Add the following lines beneath [Google.NTx86]:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
6. Connect your Ouya via micro USB to your computer and turn it on (it needs to be on for adb to work)
7. Open a command window in /android-sdk/platform-tools and run the following commands:
Code:
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
8. After 'adb devices' you should see a number, which signifies your connected console
9. You are now ready to use adb to sideload apps
=============================================================================================================
SIDELOADING APPS:
1. Place the desired .apk file to be installed within /android-sdk/platform-tools
2. Connect the Ouya and open a command window in /android-sdk/platform-tools and run the following command:
Code:
adb install [name.of.apk.file.here]
3. Wait for it to complete the installation
4. On the Ouya, navigate to 'Make' and 'Builds' and your app will be there
=============================================================================================================
ADDITIONAL STUFF BELOW
=============================================================================================================
HOW TO SET UP WIRELESS ADB (will allow you to wireless use adb command, without connecting directly to your computer)
1. Connect OUYA console via mini-usb (or using wireless adb) and run the following commands:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
chmod 666 /system/build.prop
2. Open another terminal (so we can do things locally) and run the following command:
Code:
adb pull /system/build.prop
3. Open build.prop in a text editor, add this line:
Code:
service.adb.tcp.port=5555
4. Return to the second command window and run the following command:
Code:
adb push build.prop /system
5. Now go back to your shell for the OUYA and run the following commands:
Code:
chmod 644 /system/build.prop
(seriously! the console won't boot if you forget this)
Code:
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
6. Disconnect your OUYA, put it where you want it, reboot it.
7. To wirelessly connect to your OUYA, use the following command:
Code:
adb connect 192.168.xxx.xxx
(your OUYA's ip address)
=============================================================================================================
HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES
1. Make sure you have ADB set up and working (wired or wireless).
2. Download and unzip the needed files here.
3. Place unzipped files in /android-sdk/platform-tools
4. Run the following commands to put su in the proper place:
Code:
adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
5. Install SuperUser and BusyBox:
Code:
adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk
6. Run SuperUser on the Ouya (from Make > Software) and confirm the update (not in recovery).
=============================================================================================================
Again, this isn't my original content, only slightly edited (since I am OCD about writing).
My only intention is to share this knowledge with other users like me, who don't know much about this sort of thing (yet).
If i stepped on any toes, or did something wrong, I apologize. Let me know if you have any questions or concerns.
Thank you to the following people for their work in contributing to this guide:
WinDroidGuy
elmerohueso
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
You're probably right. I'm on Windows 7. I'll see if I can jump on a buddy's computer to play around with it.
Upon a quick Google search, I found this: http://forum.xda-developers.com/showthread.php?t=1161769
Perhaps give this a try? Please let me know how it goes.
I also tried Koush/ClockwordMod's universal ADB driver (adding in the Ouya section to 32/64) but same results about a bad hash in the driver file.
Well it was worth a try. I'll keep my ears open for a Windows 8 solution.
Did you try setting up adb over wireless by any chance? I don't know much about this stuff, but perhaps that's worth a try as well?
cosine83 said:
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.
Click to expand...
Click to collapse
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
egandt said:
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.
Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.
Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?
Thanks,
ERIC
Click to expand...
Click to collapse
By G3 do you mean Galaxy S3? If so then hopefully you already have Kies installed. When I connected my OUYA and started all of this, it did not install properly. It showed up twice in device manager, it was installed as a portable device, but was also listed as "other device" and not installed. After a lot of searching,I saw that people had been able to get out working by manually selecting the Samsung adb drivers that are included with Kies. It worked for me. You need to manually select the drivers (have disk) and install OUYA as a MTP device.
Regarding the SDK I know nothing. It installed just fine on Windows 7 for me.
Good luck
Sent from my SCH-I535 using Tapatalk 2
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
eatmybiglazer said:
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.
Click to expand...
Click to collapse
Try this driver, got it to work, by selecting i from the list and forcing it
ERIC
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
I'm trying to do step 7. I input C:\Android\sdk\platform-tools into comand promt but get not regognizable message. What am I doing wrong?
You need to open the command prompt from wherever within platform-tools, or navigate to that folder from your command prompt. You can't run the adb command (which is located in platform-tools) unless your in that directory.
thanks. hopefully i'll get my OUYA soon. only 1 state away.
I dont get a number after adb devices. I editited the google usb file. Im using the 64 version of android sdk is that ok?
@tcollum: Perhaps you should add this to the OP, I tested and it worked. You can add that ;Ouya to the amd64 section of the USB driver, too
FrostyWolf said:
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).
I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)
The app then shows up under make->software
I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.
Click to expand...
Click to collapse
I just find it easier to ADB over Network and install from my laptop.
Sent from my Nexus 10 using XDA Premium HD app
TadeoNYC said:
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.
TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.
It motivated to set up wireless adb.
Click to expand...
Click to collapse
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
uncynd said:
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!
Click to expand...
Click to collapse
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
dibblebill said:
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.
Click to expand...
Click to collapse
Ahh, did not see your post that would have been a lot faster, good advice and maybe should be added to OP?
Introduction
The following procedure will walk you through the step-by-step process for gaining root access on the Nvidia Shield.
Note: You must have an unlocked bootloader before you can proceed with this tutorial!
A tutorial on how to unlock your Shield's bootloader can be found here.
This tutorial also assumes how have the correct ADB and Fastboot drivers installed for your device, for a tutorial on how to install the ADB and Fastboot drivers for the Shield please look here.
Due to the nature of modifying devices system files the standard XDA disclaimer applies: I take no responsibility for bricked devices due to the following rooting procedure, no warranty express or implied is given, I will not be held responsible if you mess up your device by following this procedure!
Procedure
Before you begin please make sure to read and re-read the whole procedure, making sure you understand the directions.
1. Download the "Superuser-su.zip" file and the "roth-insecure-boot-63.img" file that are attached to this post. After you have downloaded the files, extract the contents of the "Superuser-su.zip" file which contains Superuser.apk and the su binary, and move them to your ADB and Fastboot folder on your computer. Also transfer the "roth-insecure-boot-63.img" to your computer's ADB and Fastboot folder.
MD5 Checksum for "roth-insecure-boot-63.img": F8BA5C48D0323D99E2A748C77BF647F6
2. Connect your Shield to your computer using your USB cable. For maximum reliability please connect the USB cable to a USB 2.0 port directly connected to the motherboard as USB ports on the front of a case panel or USB 3.0 ports can sometimes be unreliable.
3. Now that your Shield is connected to your computer make sure that "USB debugging" is enabled under the Developer Options section in the system settings menu (If the Developer Options section is hidden, go to the About Phone/About Tablet section of the system settings and then tap on the item that lists the Build number 7 times or until it says "You are now a developer" and the Developer Options section becomes visible in the system settings).
4. Open a command prompt window (cmd) in your ADB and Fastboot folder on your computer and issue the following commands (If you are new to using ADB and Fastboot I would recommend checking out this excellent guide to get you up and running):
Code:
adb reboot bootloader
Now that you are in fastboot mode let's make sure that the computer see's our device:
Code:
fastboot devices
If the computer see's our device then we can proceed, if it doesn't see your device make sure you are in fastboot mode and have the correct ADB and Fastboot drivers installed for the Shield.
Now we will be booting an insecure boot.img (ro.secure = 0) to our device to allow us to gain root acess:
Code:
fastboot boot roth-insecure-boot-63.img
After the insecure boot.img finishes flashing the device will automatically boot up using the insecure boot.img.
5.First we need to mount the /system partition as read/write so we can modify it:
Code:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
6. Now we need to run the following commands to push the Superuser.apk and su binary to there correct positions and set the proper file permissions:
Code:
adb push su /system/xbin
adb push Superuser.apk /system/app
adb shell
chmod 6755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
sync
reboot
7. After the device reboots and power on into the Android Operating System you should see Koush's Superuser app in your app-drawer and you should be rooted. If you would like to verify root access you can download and run Root Checker Basic from the Play Store here. Enjoy!
Credits: Koush for his open source Superuser.apk and the su binary (https://github.com/koush/Superuser)
If users would like me to create a 1-click root process of this please let me know and I will do so .
If you are stuck with the rooting procedures I would recommend checking out this great video tutorial by wwjoshdew.
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Gnurou said:
Alternatively the following works in almost one click (one fast boot, actually): https://github.com/linux-shield/shield-root
Click to expand...
Click to collapse
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
wwjoshdew said:
It's just whole unlocking thing and giving up your devices warranty. NVIIDA being able to decline your RMA if your fan goes out and the unit overheats. Or if the scree dies (for example). I'll do it, just gotta grow a pair first.
Click to expand...
Click to collapse
I did my RMA and nvidia sent me a new 1. So you should get your new shield b4 you send it back if you happen to root it and the screen dies.
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
dark42 said:
This is a pretty complicated way of rooting. All I did was unlock the bootloader, flashed Clockworkmod Recovery, and then flashed the SuperSu zip with that. Rooted! As easy as a Nexus.
Click to expand...
Click to collapse
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
shimp208 said:
I hear yeah, this procedure is meant for those that really want to understand how the basic rooting process works and who want to gain experience manually performing these types of procedures .
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This method is actually nearly the same. It's a bootable self-contained image (like recovery is) that mounts the correct partitions, installs the necessary bits, and is done.
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
i00 said:
I haven't done this yet ... but could you also provide instructions on how to revert? I ask this as it would be nice to know that there is a back-out plan.
Kris
Click to expand...
Click to collapse
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
shimp208 said:
To unroot your Shield since you are only temporarily booting an insecure boot image rather then flashing it, if you run the following commands in either ADB shell or terminal emulator will unroot your device:
Code:
$ su
# mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
# rm -f /system/app/Superuser.apk
# rm -f /system/xbin/su
# mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
Then after you have entered those commands reboot your device and you'll be unrooted.
Click to expand...
Click to collapse
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
i00 said:
OK ... well lets say after rooting we install an app that uses root access to stuff up your device ... how do you restore the original image?
Kris
Click to expand...
Click to collapse
The original factory restore image that you can be flashed to your shield to return it to stock can be downloaded from here, along with the factory image extraction instructions (Under the open source resources section), as well as the factory image flashing instructions.
Does anyone if the root stop you from updating the device like GS4?
Simply rooting does not. I was rooted and updated. You lose root but can just reroot it like the first time. I am not sure if you have a custom recovery installed though. I haven't used one on the shield.
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
wrc1010 said:
I am using the window 8 and I can't get the command prompt to work either directly open or open it as administrator to type the command. Any idea what I am doing wrong?
Shimp208. Can you create a video on how to unlock and root the shield?
Sent from my SHIELD using Tapatalk 2
Click to expand...
Click to collapse
When you mean you can't get the command prompt to directly open what do you mean by that? Does command prompt not open or run at all when you open it? Do you have ADB and Fastboot installed and the files listed for this procedure in your ADB and Fastboot directory? The Shield I rooted was my friends and he's on vacation right now so I unfortunately can't make a video right now , but I'll still be happy to try and help you through the procedure.
Finally success root my shield
oh god
wrc1010 said:
Finally success root my shield
Click to expand...
Click to collapse
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
gogul1 said:
I want that feeling soooo bad. The drivers aren't installing on my computer correctly. I can boot my shield via command but when I enter adb devices nothing shows up even though in device manager the device shows up as Nvidia Shield ADB.
Sad times, its tough as its so new everyone is still trying to figure it out and if the drivers don't install first time there aren't any problem solving threads etc
Click to expand...
Click to collapse
What drivers are you trying to install and which version of Windows are you running?
Drivers
shimp208 said:
What drivers are you trying to install and which version of Windows are you running?
Click to expand...
Click to collapse
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
gogul1 said:
The ADB drivers and I'm running windows 7 64bit
Been trying to install them all day but I can bootload into shield but it can't pick up devices so can't root it.
Click to expand...
Click to collapse
Did you try and install these drivers? Make sure to uninstall your old driver installation first.
Greetings. Looking for some pointers.
Just picked up a Nexus 6 (64) "unlocked" (carrier?) from Amazon and am having some trouble unlocking the bootloader.
Downloaded android-sdk_r24.1.2-linux.tgz, and then downloaded some additional packages, APIs 21 and 22.
Then on the phone I did the multi-tap on Build number to get the developer mojo, then set USB debugging and Enable OEM unlock. The USB debugging prompt showed, I checked the box to always allow and then OK.
The phone reported that updates were available, so I let it update to 5.0.1 and after a restart, updated to 5.1.
After all that, ran "./adb reboot bootloader" from the console which returned immediately - no console output.
BTW, the desktop is a Linux box running Fedora 20 64bit.
Following the ./adb, I ran "./fastboot oem unlock".
It responded with: no permissions fastboot
The text on the phone shows below the identifying stuff:
Console [NULL]: null
Device is LOCKED. Status code 2
Transfer Mode: USB Connected.
Then I ran ./android again and noticed the Google USB Driver rev. 11 and the note about it being Linux incompatible.
So how badly have I screwed this up?
Any help would be much appreciated.
-Joe
@jlfesslerkc,
Your post is a little confusing.
Are you able to boot your N6?
On your linux box, when you type "./adb devices" does it respond with the id of your N6? If not, go to the thread posted by @rootSU and follow the directions > http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Linux needs some extra USB setup.
Try this:
Unplug your device, then open terminal and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Then paste this:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}==“22b8”, MODE="0666", GROUP="plugdev"
Save it then execute:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Plug it in, if it doesn't work, unplug, log out and log back in and try again.
(Make sure you're using a good USB cable, if you're unsure then use the one that came with your Nexus 6, as that WILL work, make sure the USB is plugged into the BACK of the pc (if it's not a laptop) as the ones on the front are often actually USB hubs which don't work. If that doesn't work try all the USB ports.)
Use sudo ./fastboot oem unlock
It's telling you that you don't have permission. Sudo should fix that.
Or you could add the path to fastboot and adb to your ./bashrc
Did you ensure you selected OEM unlocking in the settings>developers menu? I turned it of once when I thought I turned it on lol. Have to double check the simple stuff
Don't you just love it when someone flies in, posts a help request, and then disappears?
The sudo command in fastboot only works in Linux?
_Dennis_ said:
Did you ensure you selected OEM unlocking in the settings>developers menu? I turned it of once when I thought I turned it on lol. Have to double check the simple stuff
Click to expand...
Click to collapse
I'm thinking this myself ... I hope the OP checks and then retries ...
sotnasnauj said:
The sudo command in fastboot only works in Linux?
Click to expand...
Click to collapse
sudo is a Linux command. Its nothing to do with fastboot.
cam30era said:
Don't you just love it when someone flies in, posts a help request, and then disappears?
Click to expand...
Click to collapse
Sorry, not disrespect intended. Life intruded and I didn't get back to this task until late today.
_Dennis_ said:
Did you ensure you selected OEM unlocking in the settings>developers menu? I turned it of once when I thought I turned it on lol. Have to double check the simple stuff
Click to expand...
Click to collapse
Right... I noticed the same thing. Thankfully my anal-retentiveness kicked in and I checked ir before each attempt.
It looks like moving the USB cable to the rear of the desktop did the trick. Although I take it for granted that it unlocked the bootloader, based largely on the phone's console showing Device is UNLOCKED Status Code 3.
It there a way to verify that independently or is that really too paranoid?
Thanks for the tips. I took the least intrusive step first just to see if it had any effect, namely moving the cable to a rear USB port. That seemed to do the trick, so I've not made the change to the rules.
Is that still recommended?
gorei23 said:
Linux needs some extra USB setup.
Try this:
Unplug your device, then open terminal and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Then paste this:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}==“22b8”, MODE="0666", GROUP="plugdev"
Save it then execute:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
Plug it in, if it doesn't work, unplug, log out and log back in and try again.
(Make sure you're using a good USB cable, if you're unsure then use the one that came with your Nexus 6, as that WILL work, make sure the USB is plugged into the BACK of the pc (if it's not a laptop) as the ones on the front are often actually USB hubs which don't work. If that doesn't work try all the USB ports.)
Click to expand...
Click to collapse
jlfesslerkc said:
Sorry, not disrespect intended. Life intruded and I didn't get back to this task until late today.
Click to expand...
Click to collapse
Welcome back. I'm glad you solved your problem.:good:
jlfesslerkc said:
Greetings. Looking for some pointers.
Just picked up a Nexus 6 (64) "unlocked" (carrier?) from Amazon and am having some trouble unlocking the bootloader.
Downloaded android-sdk_r24.1.2-linux.tgz, and then downloaded some additional packages, APIs 21 and 22.
Then on the phone I did the multi-tap on Build number to get the developer mojo, then set USB debugging and Enable OEM unlock. The USB debugging prompt showed, I checked the box to always allow and then OK.
The phone reported that updates were available, so I let it update to 5.0.1 and after a restart, updated to 5.1.
After all that, ran "./adb reboot bootloader" from the console which returned immediately - no console output.
BTW, the desktop is a Linux box running Fedora 20 64bit.
Following the ./adb, I ran "./fastboot oem unlock".
It responded with: no permissions fastboot
The text on the phone shows below the identifying stuff:
Console [NULL]: null
Device is LOCKED. Status code 2
Transfer Mode: USB Connected.
Then I ran ./android again and noticed the Google USB Driver rev. 11 and the note about it being Linux incompatible.
So how badly have I screwed this up?
Any help would be much appreciated.
-Joe
Click to expand...
Click to collapse
1) Fedora packages adb and fastboot... "yum -y install android-tools", no need for the sdk.
2) the fastboot usb device does not have general user RW permissions. Run fastboot as root.
$ adb reboot-bootloader
$ su
# fastboot oem unlock
If you can do adb and fastboot commands successfully then maybe it's just Debian distros that need this. Not sure how Fedora handles that.
gorei23 said:
If you can do adb and fastboot commands successfully then maybe it's just Debian distros that need this. Not sure how Fedora handles that.
Click to expand...
Click to collapse
Debian Distros need what?
rootSU said:
Debian Distros need what?
Click to expand...
Click to collapse
Apparently Debian Distros need to reply to threads where the OP has posted that his problem was solved by switching to another USB port.
cam30era said:
Apparently Debian Distros need to reply to threads where the OP has posted that his problem was solved by switching to another USB port.
Click to expand...
Click to collapse
haha.
I was wondering if it was the udev rules. Cause I just deleted my udev rules and rebooted and can still use adb and fastboot on a debian-based distro.
rootSU said:
haha.
I was wondering if it was the udev rules. Cause I just deleted my udev rules and rebooted and can still use adb and fastboot on a debian-based distro.
Click to expand...
Click to collapse
Really? I'm amazed.
cam30era said:
Really? I'm amazed.
Click to expand...
Click to collapse
When I looked in there, I clearly had added my Nexus 5 previously but not my nexus 6. My 6 worked obviously. So I just sudo rm /etc/udev/rules.d/51-android.rules and rebooted. Everything still works. Wasn't expecting it to. I wouldn't have added my Nexus 5 unless I had to.