Nvidia shield tv pro 2019 being detected as samsung - Nvidia Shield TV & Shield TV Pro (2019) Questions

When I enter the bootloader/fastboot on the shield, in device manager in windows 10 shows
{
"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"
}

Hitti2 said:
When I enter the bootloader/fastboot on the shield, in device manager in windows 10 shows View attachment 5337499
Click to expand...
Click to collapse
Most likely that's just a Windows driver issue, and it's using a Samsung driver instead of the nVidia
and should not affect how adb works,
but you can download the Generic Google USB driver.
Or Official nVidia USB Drivers here
SHIELD Open Source Resources and Drivers
NVIDIA publishes source code, binary packages and USB drivers for developers and the Android open source community to use in development and to create custom OS images for SHIELD devices. Look below for links to relevant downloads. Portions of open source software are provided under license...
developer.nvidia.com
Install the new driver, Uninstall the old driver
Reboot the PC

sd_shadow said:
Most likely that's just a Windows driver issue, and it's using a Samsung driver instead of the nVidia
and should not affect how adb works,
but you can download the Generic Google USB driver.
Or Official nVidia USB Drivers here
SHIELD Open Source Resources and Drivers
NVIDIA publishes source code, binary packages and USB drivers for developers and the Android open source community to use in development and to create custom OS images for SHIELD devices. Look below for links to relevant downloads. Portions of open source software are provided under license...
developer.nvidia.com
Install the new driver, Uninstall the old driver
Reboot the PC
Click to expand...
Click to collapse
Yeah something is going on with my system but I ordered new CPU new motherboard and new RAM and I got scum in my water cooling system so once my new computer parts come I'm going to tear the whole thing apart and do a fresh install of windows. I got S10 Plus and a Tab S7 Plus and I used it on my computer before So when I go to do a fresh install I'll connect the Nvidia Shield TV Pro 2019 first. Also that is detected as a samsund device when it's in fast boot mode. When it's connected through the booted up android tv "shield tv os" operating system it's detected as Nvidia Shield.
I am getting a no link fast boot error When I tried to flash TWRP I made a thread on it Here at XDA and at Nvidia community.
I tried flashing twrp through fastboot, i get this error.
I tried flashing twrp through fastboot, i get this error C:\platform-tools>fastboot flash recovery twrp.img Sending 'recovery' (24862 KB) FAILED (Write to device failed (no link)) fastboot: error: Command failed
I think I get that error is because it's under Samsung's drivers and not in the nbidia and I installed in the nvidia.
I'm just going to reinstall windows when I get everything and get my loop cleaned.

Related

[miniTUT][WIN10]Installing ADB Drivers for Sony Devices on Windows 10

Hi, I have managed to install proper ADB drivers on my Win10 and I came up with an idea that it might be useful for other XDA Community members.
You have to manually install the drivers since there is no installer available that is Win10 compatible.
INSTRUCIONS
1. Download drivers for your Sony device from this site LINK
2. Extract the drivers
2. Connect your device to the PC and turn on USB Debugging
3. Open device manager and find a device with a warning icon
4. Right click on the device and choose update driver
5. Choose install the driver manually option (the second one)
6. Enter the path to your extracted drivers (TO THE MAIN FOLDER "/YourDevice'sName")
7. Please make sure that Include subfolder option is checked
{
"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"
}
8. Install the drivers
9. Restart your PC
Tested on Xperia Z1 Compact​
Also make sure that you have driver signature verification disabled, because for some devices it won't install that way (XZU)
The other way is to disable signed-driver verification on Windows 10, so every driver will be installed. (It might be a bit risky as you can install a 32-bit driver on a 64-bit o.s but it won't work)
Kizoky said:
The other way is to disable signed-driver verification on Windows 10, so every driver will be installed. (It might be a bit risky as you can install a 32-bit driver on a 64-bit o.s but it won't work)
Click to expand...
Click to collapse
It's okay if it just doesn't work, but it's not okay if it screws up the whole system
V4LKyR said:
It's okay if it just doesn't work, but it's not okay if it screws up the whole system
Click to expand...
Click to collapse
Already tested without any problems..
But how can I install ADB driver if there is no Sony Xperia ZR driver on Sony's site?
Thanks in advance.
EndOfDays-Wildfire said:
But how can I install ADB driver if there is no Sony Xperia ZR driver on Sony's site?
Thanks in advance.
Click to expand...
Click to collapse
You can get drivers from latest flashtool
Hi!
I can't get this to work. My Z5 has ADB debugging switched on but there is no device with a warning icon. In ADB mode my Z5 is listed as "portable device". There is no ADB device visible.

OP 6T fastboot device not detected

I had to reinstall Win 10 on my computer and now I'm not able to connect to my 6T in order to root it.
The boot locker is unlocked, I can see it at phone boot. It was unlocked also before last update to OxygenOS 10.3.7.
Debug USB in enabled. When I connect to the phone to the computer it is deceted and I can transfer files.
Whit ADB devices phone is deteted (picture is from all in one tool, using command prompt same result)
{
"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"
}
using fastboot devices the phone is not detected.
installed last official usb drivers (google and oneplus)
Any idea, suggestion or further test that can help?
Thanks
Same problem here. Please help.
Finally I found a working solution.
If you have a laptop you have to disable secure boot.
Then you have to disable signature verification on windows 10 ( How to Enable or Disable Driver Signature Enforcement in Windows 10 | Tutorials (tenforums.com) ).
I used option 3.
Download Oneplus usb drivers ( Download Latest OnePlus USB Drivers for Windows and Mac (getdroidtips.com) ).
Then connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device. If it is found, this means windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Thanks man, it worked for me.
Just to complete, after istalling the drivers you can restore signature verification and secure boot on Win 10.
Everything will work fine.

[Guide]Another fastboot/fastbootd driver guide for Windows

Background​When I got my OnePlus 8T (after using Samsung devices and a OnePlus 3T for many years) I could access the phone using adb and, when the phone was in Bootloader mode, using fastboot. But I couldn't access the phone in Fastbootd mode.
I tried lots of different things but none of them worked for me and, worst of all, many of the solutions required downloading files from untrusted sources.
I finally decided to see if the Google USB driver would help and, to my surprise, it fixed the fastbootd problem. So I uninstalled the drivers that were being used for Bootloader mode, the Google driver used for Fastbootd mode,
{
"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"
}
and then did a clean install of the Google USB driver so that I could document the process.
Installation​Without a suitable driver when connected in Bootloader (or Fastbootd mode), my phone shows up under "Other devices" as "Android" with a yellow warning triangle:
I downloaded the Google Windows USB driver from https://developer.android.com/studio/run/win-usb, extracted the contents, and installed the driver by right-clicking on usb_driver/android_winusb.inf and selecting Install:
Next, I booted my phone into Bootloader mode (Note: if Bootloader mode works for you and you didn't want to uninstall the driver, then boot into Fastbootd), found my phone in Device Manager (Other devices), double-clicked it (Android) to pull up the driver details and clicked the Update Driver... button. On the next screen select the second option "Browse my computer for drivers":
And on the next screen I selected "Let me pick from a list of available drivers":
I chose "Androd Device" and clicked on Next:
This brings up the following screen:
(Note: I also have Samsung drivers installed). I clicked on "Google, Inc." under Manufacturer, then "Android Bootloader Interface" from Model and clicked on Next.
I got a warning, to which I replied "Yes":
and the installation completed successfully:
Notice that the phone now shows up as "Android Bootloader Interface" under "Android Device" in Device Manager. Double clicking on it now shows the driver is installed:
And that's it!
I now find that I can also boot into Fastbootd mode, even though I only installed the driver for Bootloader mode.
Note: this driver also works for my OnePlus 3T

YB1-X90F No OS(?) - Flashing Help

TL;DR: Noob needs to stock flash a device that won't boot into OS.
Here's how the recovery looks (without and interaction):
{
"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"
}
Boot loader:
Splash screen:
I have acquired a YB1-X90F that just shows the orange Lenovo splash screen and or a blank and does nothing.
I'm a novice when it comes to flashing, etc.
I can access Fast Boot and Recovery Mode.
What should I be trying?
I've got several links I'm going through but I'm rather confused. For example, I've been trying to set up ADB, Fastboot and Drivers. Struggling with drivers.
My first setup was with platform-tools_r32.0.0-windows.zip but I'd just have a missing 'Cherry Trail Tablet' driver in Device Manager.
I then tried 15 seconds ADB Installer v1.4.3 but still no driver. 'Cherry Trail Tablet' in Device Manager.
I also tried ADBDriverinstaller.exe and IntelAndroidDrvSetup1.10.0.exe.
I looked through this thread, but no joy:
Missing USB driver "Cherry Trail Tablet" while on bootloader
Hello everyone ! First post here. :) I've bought yesterday this amazing machine, and bought the Android version. But I wished to directly install a Windows 10 version to replace Android, but I didn't thought it would be this... complicated. >.
forum.xda-developers.com
In the end, I had to manually add 'Android ADB Interface' as mentioned in the 15 seconds ADB Installer v1.4.3 page under Notes:
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
I seem to have activity in cmd prompt now:
C:\WINDOWS\system32>fastboot devices
YETIDD2E4EC8 fastboot
Click to expand...
Click to collapse
This guide/links seem to assume your device is already working?
Yoga Book YB1-X90F (Android) - How to Flash back to Stock Rom 6.0.1 /downgrade
hello all i spent last few hours looking for solution to how to flash Stock Rom to my YB1-X90F and i found steps here and there and finally i got it. so i gathered all the steps in one thread to help whoever want to flush back to stock or...
forum.xda-developers.com
Where do I go from here?
How do I unlock the bootloader without access to the OS on the device to 'Enable USB debugging' and 'OEM Unlock'?
Solved. I ran 'flash_update_from_user.json
Just waiting for the battery to charge to 30% to hopefully enable the Halo Keyboard.
Here are the files needed in case other links void in the future: https://drive.google.com/drive/folders/1gD9FyA03GbLZ7ZcjkyMDlhVPs4_em2rY?usp=sharing

Galaxy Note 3 not recognized in Odin when in download mode

Hello there, I have been searching for something for hours and just can't figure this out. So I have an old Galaxy Note 3 and want to get Lineageos running on it. Have done this before a few times with other phones, but here from the official guide I have to use Odin.
So what happens is that when the phone ist just regularly on I can see it in Odin, I can also see it when I do adb devices. I have usb debugging on and have set it to trust my computer.
However, as soon as I boot into download mode the phone becomes invisible to the computer, no return to adb, not visible in Odin.
Any ideas what I could be missing? Thanks so much!
Do you see other devices in the device manager?
Show the phone screen in download mode.
What OS on the PC? What version of drivers from Samsung? What variant of Odin?
Thank you for your fast reply! Really appreciate it! Of course I left out some info....
In the windows device manager I see other devices, I also see the note 3 when it is just regularly turned on, just not when in download mode. The note shows up in device manager as SAMSUNG Android ADB Interface and as SAMSUNG Mobile USB Composite Device. Using Odin 3.14, also tried 3.13 at some point.
OS in Windows, can't do Odin in others, can I? Played around with Heimdall on a Linux computer, but that did not go anywhere and can't find much documentation. Did not flash anything, just tried to see if I could get it visible.
Version of drivers from Samsung, how do I check that? I downloaded them from Samsung as in the official instructions.
Now the Download screen might be part of the issue here, I have been searching around with that, it seems that the last thing it says is "UDC start" is not what it is supposed to do... should be attached. Thanks again!
{
"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"
}
If the phone is in download mode, Windows sees the SAMSUNG Mobile USB CDC Composite Device as a serial bus controller, and Odin sees the COM port.
Install the latest drivers from Samsung (if you have older ones) and the latest adb from Google.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Thank you! Just reinstalled the drivers from samsung (already had them, but can't hurt), restarted, but no difference yet.
To clarify, by "installing the latest adb" you mean download the plattform tools, unzip, and then open a command line in the folder? That allows me to run adb commands, like I can do adb devices and will see the phone, just not when it is in download mode.
When in download mode my device manager does show me a Serial USB Device (COM5), however Samsung is not part of the name. It is the device though, as it disappears when unplugged. But since it does not state that it is a samsung device, I am thinking maybe that points to a driver issue in some way?
Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!
bilboBeutlinhh said:
Oh wow, something just happened. I went to the Serial USB Device I talked about, deactivated, re-activated, told it to re-install drivers, than suddenly it moved down the list to the USB controllers and has the exact name you started. And Odin sees it now!
Click to expand...
Click to collapse
Glad you got it sorted! Cheers
Thanks again! And in case anyone finds / reads this, it seems that just installing the Samsung drivers might not install them all, checking in the device manager when download mode is active and running an update of drivers from there made the difference.

Categories

Resources