I installed the custom ADB drivers from this site, I then booted my Shield and am stuck on the command prompt screen as it says
<waiting for devices> when I try to install the thor.img
The Shield is unlocked and the usb debugging option is on.
Cannot work out what the issue is.
looking under device manager it shows up under Android Device as Nvidia Shield ADB but it also shows up under portable devices as SHIELD.
Whilst in boot mode the device only shows up in portable devices with a exclamation mark next to the device.
*UPDATE*
Ok so I uninstalled my drivers to start again, plugged in the shield and it reinstalled my drivers and now under Android Devices it shows NVIDIA SHIELD ADB
Result!
Now I opened the dab cmd prompt
typed in
adb reboot fastboot
and it booted my shield! jolly good
But then I typed in
fastboot boot thor-insecure-boot.img
I then had
<waiting for device>
show up in the command window.
This is where it stayed.
On the screen of my shield I have options:
continue
restart bootloader
recovery mode
poweroff
I uninstalled the portable device driver because I think it may have been causing confusion.
I then typed adb devices into CMD and a list of devices showed the serial number of the nvidia Shield.
I then typed in adb reboot bootloader in and it booted.
I then tried adb devices again and nothing showed up.
When I go into bootloader The Android Device: Nvidia Shield ADB driver disappears in manager once I go into bootloader mode. Is this normal?
Hmmmmmmm
definetly something to do with the drivers.
I'm on windows 7 64bit by the way.
Going back into device manager I noticed that there is another device under Other devices, upon looking at it it is Fastboot and has an exclamation mark in a yellow triangle next to it (Minimal dab and fast boot is open though).
Such a bummer as I'm so close yet so far
pictures
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.
Yellow triangle means driver or device error (either one). The rest you have reached the limits of my knowledge.
appreciate the help
appreciate the help from everyone so far. I got through the bootloader stuff easily enough and now the shield is unlocked. This next bit is just knocked me for six as I have followed the instructions step by step and even taught myself some new stuff but this is not going according to plan.
So far:
I downloaded Andriod SDK
Ran SDK
clicked install and it installed lots of stuff including Android SDK tools, SDK platform tools and SDK Platform & ARM EABIv7a a system image in the Android 4.3 section.
I downloaded minimal adb and fastboot v1.1.3
I downloaded Superuser
I downloaded thor-insecure-boot.img
I downloaded the Universal_Naked_Driver_0.73 package
I then installed the Universal Naked Driver package which shows up on computer manager Devices under Android Devices as NVIDIA SHIELD ADB
I then dragged the thor and superuser files into the minimal adb and fastboot folder
I then plugged in my Shiled via USB 2.0
I started up the adb and fastboot CMD window
I first typed in adb devices and the shield showed up.
I then Typed in adb reboot bootloader
The shield went into boot mode.
I then retyped adb devices into the CMD window
The shield did not show up.
I the typed in fastboot boot thor-insecure-boot.img
The CMD window then said <waiting for Devices>
The shield screen showed that the device is unlocked and gave me 5 options:
Continue
Restart Bootloader
Recovery Mode
Reboot
Poweroff.
And then nothing.
This is the point I am at in terms of rooting.
The Device shows up in the Computer/manage window when plugged in but when I execute the adb reboot bootloader command it dissapears.
There is a Device in the Other Devices section of the Computer/manage window called Fastboot. This has a yellow triangle with an exclamation mark in it.
The CMD window can communicate with the Shield as it can make it go into boot mode but that's it.
Appreciate any help that can be given. Apologies for the length of post but it's only fair you know what I have done so far. Knowledge is power etc
I'm on windows 7 64bit os.
Latest pictures of the system
Ok so these are the latest picture of the system as it is now.
Currently there are two drivers showing for the Shield. One under Android Devices as Nvidia Shield ADB
The other is under Portable Devices as SHIELD. (picture 4 from the left)
When in boot mode the Android Device dissappears (picture 2 from the left)
There is a picture of the minimal adb and fastboot folder where I put the Superuser.apk file, the Su file and the Thor file - picture 3 (Is that all correct?)
There is also a picture of the command window when the shield is in boot mode. I type in adb devices and nothing shows up (picture 1)
Android SDK pics
And here is the SDK app running...
When your shield is waiting for fastboot commands it should show up as fastboot in device manager.
I had a terrible time with drivers too. My advice is to uninstall as many shield drivers as you can and then try to manually update the drivers making sure to get the fastboot driver installed. When you select have disk for the drivers the correct one will say Shield Fastboot
time to go fishing!
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers
gogul1 said:
Ok I will try to uninstall drivers but not sure how to do it due to not exactly knowing which ones there are and where they are kept. Will take a look around. Thanks for the help though will try and find the fastboot drivers
Click to expand...
Click to collapse
When I did it I plugged in my Shield and went into the device manager and uninstalled everything Shield related. I think it showed up in two places. Then I unplugged the Shield and when I plugged it back in I went back to the device manager and found the Shield again since Windows will auto install some sort of driver when you plug the shield in. I think this is when either there will be a yellow exclamation point next to one of them or windows will actually allow you to update the driver without giving you the stupid "driver is up to date" message.
That's when I right clicked on it and selected to update driver. At that point I made sure to use the "Have Disk" option and browsed to the universal driver folder. Once the universal driver list populated I was able to find the Shield fastboot driver in that list. I think my original problems started when I installed the Shield ADB driver which isn't needed and once that driver is installed the fastboot driver seems impossible to install because stupid windows keeps telling you the driver is up to date. By booting your Shield up using the home and back keys you are manually placing it in fastboot mode so you never need to use adb commands.
It is hard to remember but I do remember uninstalling everything I could and when I did finally update a driver I used the one with the word fastboot in it.
---------- Post added at 12:27 PM ---------- Previous post was at 12:21 PM ----------
gogul1 said:
These are the pictures of the command promt when it is in boot mode, unboot mode and the devices installed.
When I go into boot mode on the shield the device called Nvidia Shield ADB dissappears from the computer manager window and the fastboot device has a yellow triangle with an exclamation mark next to it.
Very odd.
Click to expand...
Click to collapse
If you get to this point again select to update that driver for the exclamation point and go to have disk and find the fastboot driver which you somehow get to by using the "have disk" option and browsing the universal drivers folder when you update the driver. Don't install the other drivers in the list, just the fastboot driver.
don't get the have disk option
uninstalled everything again. Next will be finding the Have disk option.
ah ha
I kinda see, when I go into Update driver Do I go into "let me pick from a list of device drivers?"
I click on that option and it gives me a list of devices but not sure what to choose. There was an android device option so chose that. I then went into the folder and clicked the "Have disk" option. I then navigated to the universal folder but there was nothing like bootloader or boot device in the folder.
I go into computer, right click, choose manage.
Go down to devices.
See OTHER DEVICES
In that folder is the SHIELD device with the yellow triangle next to it.
Right click it, choose update driver.
I choose let me pick from a list of device drivers on my computer.
It opens the window - select your device type from the list below
I choose show all devices
It opens the window - select the device driver you want to install for this hardware
I click the HAVE DISK button
I chose Install from disk option
I clicked the browse button
I navigated to the Universal naked driver folder and clicked open.
List of items in the folder are:
amd64 - folder
i368 - folder
android_apxusb.inf
android_winusb.inf
and that's it. So I chose android_apxusb.inf
right clicked on it to install.
window asking if I wanted to cancel or install anyway popped up.
chose install anyway.
Driver installed but still the same as before.
sigh
hmmmm
ok so this time I installed the ADB driver.
I then deleted the Portable Devices Driver named SHIELD.
I then booted my shield up again.
This time the Android Device Nividia Shield ADB turned into Fastboot and had the yellow triangle on it.
I then clicked on that chose to update drivers.
I then chose the Have Disk option. Chose the android_apxusb.inf file and clicked ok. There was the a long list of devices including asus eepad etc and I scrolled down to Nvidia Shield Fastboot.
I highlighted it clicked ok, it warned me that it didn't know if the driver was reliable, I clicked ok to install it anyway and the driver then went back up into the Android Devices folder in the device manager and was named Nvidia Shield fast boot.
So I opened up minimal adb & fastboot, then typed in adb reboot boot loader. The Shield booted, I then typed in adb devices but nothing showed up.
I then tried to do command the thor.img anyway, it say:
downloading boot.img
OKAY (0.810s)
booting...
OKAY (0.020s)
finished. total time 0.830s
The shield the rebooted and came back on as normal.
I then cut a paste the command lines:
adb shell
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP /system
exit
but when it came to the mount command it said:
mount: operation not permitted.
hmmmm something is not right but cannot put my finger on it....:roll eyes:
When I went back into the Device Manager I saw that under Android Devices there are now two drivers
Nvidia Shield ADB
Nvidia Shield Fastboot
Not easy this stuff eh?
20 times
I have uninstalled and reinstalled the drivers 20 times now. Always the same result.
I am going to start this all over again.
Don't think I will get any luck.
I uninstalled drivers, plugged in the shield, the updated the drivers via the have disk method. The booted shield.
Then changed fastboot driver to updated driver again.
The results of the whole thing can be seen here
Please help
Right I uninstalled all drivers again.
When I restart and plug the shield back in it automatically installs two drivers.
One is in the Other devices folder named SHIELD and has a yellow exclamation mark next to it.
The other is in Portable Devices and looks to install ok.
What am I meant to do with these?
I try to update the Portable device driver but it doesn't allow me to update it.
I update the other one as nvidia shield fastboot but the when I actually boot the Shiled up it moves from the Android devices folder to the other devices folder and calls itself Fastboot (it has a yellow triangle next to it.
So I then update that one to Nvidia shield fastboot and everything goes ok installng the thor.img.
The the shield roboots and reinstalls the same driver... Now I have two Nvidia Shield Fastboot drivers in my Android folder.
Really Really could do with some help people please please please
Ok, if you have the fastboot driver installed which you should if device manager says fastboot without any yellow exclamation. Windows device manager needs to say fastboot while your shield is connected in fastboot mode (hold home and back while powering the shield up) Download these two files that I link below (or go directly to Gnurou's site and get them if you feel more comfortable https://github.com/linux-shield/shield-root) and put them in the same directory that your fastboot android package is in.. They are the two files needed from gnurou's site for rooting. One is a text file and one is some sort of .gz file (don't unzip this .gz file.
http://db.tt/oPHjgctM
http://db.tt/S0p9KMPi
If your shield is not yet unlocked do this:
1. Switch your SHIELD off (long press the NVIDIA logo button and select Power off).
2. Power your SHIELD on while maintaining the back and home buttons pressed (these are the two buttons that lie under the big NVIDIA-logo button, on its left and right). Release them once you see the bootloader screen.
3. Connect your SHIELD to your computer using a USB cable.
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
5. On your computer, enter the following command:
fastboot oem unlock
6. This will display the unlock menu. Read the disclaimer and think one last time about what you are doing. This is your last chance to stop.
7. Use the back and home buttons to select your option. If you decide to continue, select Unlock and press the NVIDIA-logo button to validate. Your personal data will be erased and your device marked as warranty-void permanently.
Regardless of your choice, you will be back to the bootloader screen. Using the same buttons, navigate to Poweroff and select this to power your SHIELD off.
Rooting (Shield should be unlocked at this point)
1. turn your shield off.
2. turn your shield on while holding the home and back buttons until you are in the bootloader.
3. plug the shield into the computer
4. open a command window from your fastboot folder and type this (I am assuming you have the android fastboot all set up properly):
fastboot devices
4a. That should list a big long number. If it does that means your fastboot is working.
Now type this:
fastboot boot zImage_dtb ramfs.img.gz
You should see the shield do it's thing with the penguins and then you're rooted.
This is how I rooted mine. It's way easier than doing that manual method. I copied some of the instructions directly from Gnurou's git site but the formatting is a little different. It all boils down to getting those drivers installed properly and you will know those damn things are installed properly when you have your Shield plugged into your computer while in fastboot mode (you held home and back before turning the shield on) and you can type fastboot devices and it lists a long number. I think people are shying away from this method because github can be confusing as far as how to download files and people seem to be confused about what all the other files are for on Gnurou's site when really you only need the two I linked.
Keep at it man. I know you'll get it.
Thanks
I was given a package of developer tegra nvidia drivers adk drivers to install.
Now I can boot my shield
When I type in fastboot devices my shield shows up as a long number
but when I type in fastboot boot zimage_dtb-ramfs.img.gz
I replies
cannot load zImage_dtb': No error
I put the files in the Minimal ADB and Fastboot folder.
Odd.
The drivers I have installed now are in this picture it works up until the point I need to execute the root
View attachment 2209196
This was my original issue in video form so you can see my problem.
http://youtu.be/amk7fkKJtSc
I was going to try and help here but after seeing how many different threads gogul1 has spread his issues though, I don't fell like spending 2 days trying to figure out what order his posts are in from thread to thread.
I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?
How to Install ADB and Fastboot: Method 1
To quickly and easily install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the followingownload the latest*ADB Installer file*(adb-setup-1.4.2.exe).Right-click the file*adb-setup-1.3.exe*and choose “Run as Administrator“.Type “Y” and press Enter to install ADB and Fastboot, and set the environment variables. Enter “N” if you don’t want to do the same and want to just install the drivers.In the next step, enter “Y” to install the drivers for your device. Enter “N” to skip this step.Wait till the driver installation finishes up. That would take only some seconds.To verify that you have successfully setup ADB and fastboot, open up a command prompt (press*Windows key + R*-> type in*cmd*->*OK) and enter “adb version” (without quotes). If it returns something like “Android Debug Bridge version x.x.xx“, then your ADB and Fastboot are all-ready.Congrats! You are ready to rock!Read more at http://dottech.org/21534/how-to-ins...m8Vo3.99QUOTE=Lex_Michdeandroid;56140163]I've been at this the entire evening, but can't seem to get it to work.
I installed the latest driver package (https://github.com/koush/UniversalAdbDriver) which should make W7x64 accept my NexS in fastboot mode. But it doesn't. All other modes are recognized, but in fastboot it keeps saying "Android 1.0" with that yellow exclamation mark on it.
I also tried the "have disk..." option and fed it the "android_winusb.inf", but it said this wasn't compatible with x64. What else can I try?[/QUOTE]
Hi There.
hey guys whats the easiest way to just get root access with the shield k1 on marshmallow?
From step 8 on is the simple root procedure if you have drivers and ADB setup already.
Pre-Requisites:
•Minimal ADB/Fastboot (official page)
•Shield Family Drivers (original page)
•TWRP Recovery (experimental)
•SuperSU 2.65 BETA for flashing with TWRP (newer version maybe here)
Note: Unlocking the bootloader will ERASE EVERYTHING internally (not on your external SD card if present). Make sure you have everything saved off and backed up. You’ll have to resign into Google – so if you use two-step authentication, be sure to have your Google Authenticator app ready.
Preparation
1.Install Minimal ADB and Fastboot if you do not already have it installed.
2.Ensure the Shield Family drivers are extracted somewhere on your system and you know where they are.
3.Make sure you know how to get to Device Manager on your PC.
4.Extract TWRP Recovery image (and do yourself a favor and rename it to something easy like twrprecovery.img). Put this in your Minimal ADB and Fastboot folder (usually crogram files(x86)Minimal ADB and Fastboot).
5.Copy supersubeta.zip into your Minimal ADB and Fastboot folder
6.Plug your Shield Tablet K1 into the PC with USB cable.
7.Confirm drivers for ADB are installed: 1.On your PC, go to Device Manager. Find the yellow (!) ADB device. If none exist, you probably already have drivers. Skip to step 8.
2.Right click the device and select Update Driver.
3.When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
4.When finished with the driver install, the (!) yellow device should be gone.
8.Enable Developer mode on Shield Tablet K1 1.On the Shield Tablet K1, go to Settings->About->Build (tap 7 times on the BUILD to unlock developer mode)
9.Enable USB Debugging on Shield Tablet K1 1.Settings -> Developer -> Debugging; set to On
2.A popup should appear asking for this PC’s authorization. Check the Don’t ask again for this PC box and select Allow. If it doesn’t show up now, it will later.
Root Procedure
1.Reboot into Bootloader on Shield Tablet 1.Launch Minimal ADB and Fastboot from the Start Menu or icon. This puts you in a black DOS box.
2.Type “adb devices” and make sure your Shield Tablet K1 appears. Note: If you didn’t have a popup on your Shield Tablet K1 screen in Step 9.2 above, it probably will appear now. You’ll have to authorize the PC before it will show up under adb devices.
3.Once you see your Shield Tablet K1 when you run “adb devices” you’re ready to proceed.
4.Type “adb reboot bootloader” and hit enter. The Shield Tablet K1 should reboot into the bootloader screen.
2.Verify Fastboot Drivers are installed: 1.On your PC, go to Device Manager.
2.See if a yellow (!) exists that mentions FASTBOOT. If not, continue to Step 3 to unlock bootloader.
3.Right click the device and select Update Driver.
4.When offered, browse your computer for the driver and point it to the Shield Family Drivers folder you extracted in Preparation Step 2 above.
5.When finished with the driver install, the (!) yellow device should be gone.
6.Type “fastboot devices” and make sure your Shield TV is visible.
3.Unlock Bootloader (skip if you already unlocked your bootloader) 1.Type in “fastboot oem unlock” and hit enter. EVERYTHING ON THE TABLET WILL BE LOST!
2.You will see a prompt on the Shield Tablet K1.
3.Confirm to unlock the bootloader. Do not be impatient! Let it finish.
4.Reboot to Shield Tablet K1 Interface 1.Once the bootloader is unlocked, reboot the Shield Tablet K1 and return to the Shield tablet K1 main interface.
5.Repeat Preparation Steps 8 and 9 above to re-enable Developer/USB Debugging. Note: at some point you will have to re-authorize your PC again; if an ADB command fails, be sure to look at your Shield Tablet K1 screen for the authorization prompt.
6.Push supersubeta.zip to the Shield Tablet K1 1.In the Minimal ADB and Fastboot DOS window, type (or cut and paste for more accuracy): “adb push supersubeta.zip /sdcard/”
2.You should see text indicating the file was copied over correctly.
7.Reboot to Bootloader 1.Type “adb reboot bootloader” and hit enter. The Shield Tablet K1 should reboot into the bootloader screen.
8.Fastboot with TWRP 1.Type “fastboot devices” and make sure your Shield Tablet K1 is visible.
2.If your Shield Tablet is listed, type “fastboot flash recovery twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
3.On the Shield Tablet K1, use the volume rocker to select RECOVERY MODE and tap the power button to select. Note: There are reports that you should do a full reboot between flashing TWRP and flashing SuperSU. IF you find that TWRP doesn’t survive using this method: 1.Instead of selecting Recovery Mode, in Minimal ADB window, type: “fastboot reboot”
2.Once rebooted to Android, use Minimal ADB window, type: “adb reboot bootloader”
3.When the tablet is in bootloader, type: “fastboot boot recovery”
4.After 15 seconds or so, you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
5.You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
9.Install SuperSU 1.Select INSTALL.
2.Navigate and select supersubeta.zip.
3.Follow the instructions to Swipe to Flash
4.SuperSU will install.
10.Reboot to System 1.Select REBOOT then SYSTEM from the TWRP menu
2.Answer NO if asked anything about fixing or restoring ROOT
11.Run SuperSU application and apply any updates 1.Once you are back up and running (first boot can take a little longer) find the SuperSU app installed on the Shield Tablet. Run it and perform any upgrades (select “Use Normal” if asked).
12.You are now rooted! Test your root apps now.
You say this is for the K1. Is it essentially the same for the original version or is there a different procedure?
Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH
Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs