Database Info

Root installation and drivers issue

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.

[Q] TF700 not found by Fastboot

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

"error: no device/emulator found" in fastboot

As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.

Reinstall driver again.

It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).

1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.

Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.

I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).

Cannot recognise device in fastboot

Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?

Sorted the driver issue... didn't install it properly...

Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)

Win 10 seems to have problems. I downgraded to win 7 all sorted.

I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave

funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.

Can't connect to Pixel 3a in fastboot mode

Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.

You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day

Chrisp3 said:
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
Click to expand...
Click to collapse
On Windows, make sure your phone is connected and you can run ADB commands. Enter Device Manager in Windows and verify that there is a listing for Android ADB Interface.
I just connected to a new computer and I could do ADB but not Fastboot. Discovered that instead of ADB Interface in Device Manager, it just said "Pixel 3a."
If this is the same for you, go install the Android USB drivers.

KaptinBoxxi said:
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Click to expand...
Click to collapse
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!

Chrisp3 said:
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Click to expand...
Click to collapse
The issue with the fastboot method (realized this when I upgraded to Win11 Beta) is the ADB Quick Installs are missing some stuff, and cause certain flash methods to not work via flash-all.bat's from Google or Graphene or others.
When I install ADB System Wide, I also download the platform-tools from Google, and over-write everything in the c:\adb folder, also adding the stuff missing. Idk why the adb quick installers don't just download from google directly, would save a lot of headaches