Can ADB run on a windows rt device?
Given the nature of this site, I'm going to guess you mean Android Debug Bridge, though there are far too many three-letter abbreviations in the computing industry for it to be smart to not give the full form once.
Short answer: No.
Slightly longer answer: Not right now, possibly never.
Real answer: RT can't run x86 programs, and the version of adb.exe that comes with the Android SDK for Windows is a 32-bit x86 program. However, it might be possible to either re-compile the program for ARM (I assume it's open source), or to run it under the win86emu dynamic recompilation tool (most likely not supported yet, but possibly in the future). However, there's no guarantee that the drivers needed to connect to an Android device for debugging will ever be available for RT, in which case it doesn't do any good to run the program because it can't connect to anything. I believe at present RT can browse an Android device connected in USB Mass Storage (UMS) or Media Transfer Protocol (MTP) mode, and can charge one (but probably slowly), but that's about it.
GoodDayToDie said:
Given the nature of this site, I'm going to guess you mean Android Debug Bridge, though there are far too many three-letter abbreviations in the computing industry for it to be smart to not give the full form once.
Short answer: No.
Slightly longer answer: Not right now, possibly never.
Real answer: RT can't run x86 programs, and the version of adb.exe that comes with the Android SDK for Windows is a 32-bit x86 program. However, it might be possible to either re-compile the program for ARM (I assume it's open source), or to run it under the win86emu dynamic recompilation tool (most likely not supported yet, but possibly in the future). However, there's no guarantee that the drivers needed to connect to an Android device for debugging will ever be available for RT, in which case it doesn't do any good to run the program because it can't connect to anything. I believe at present RT can browse an Android device connected in USB Mass Storage (UMS) or Media Transfer Protocol (MTP) mode, and can charge one (but probably slowly), but that's about it.
Click to expand...
Click to collapse
You may be able to run ADB over the network with the x86 emulator, if it has the network part implemented.
The ADB is open source but the windows port uses cygwin so we would need to wait for cygwin on RT which would be alot to ask for right now.
There's a way
1) Install an X 86 Emulator. Ref - http://forum.xda-developers.com/showthread.php?t=2095934
2) Test and Install the apps you like. Ref - http://forum.xda-developers.com/showthread.php?t=2092348
You might want to try running ADB, and see if that works.
Note - Whatever I posted here is not guaranteed to brick/unbrick your device or any related actions. So it is purely left to you on what you do with your device and has nothing to do with my update(s) here, even if it renders your device unusable or inconvenient or similar by any means and extent.
Update: Just realized that
1) The emulator doesn't work for Win RT 8.1 as Jailbreak doesn't work for WinRT 8.1
2) Hence no way for ADB to run on Win RT 8.1
vcsekhar said:
Update: Just realized that
1) The emulator doesn't work for Win RT 8.1 as Jailbreak doesn't work for WinRT 8.1
2) Hence no way for ADB to run on Win RT 8.1
Click to expand...
Click to collapse
And that the thread is old and that your solution was already addressed above
Can I root my nexus from a Microsoft Surface? It has a USB port. I'm trying to do this because my nexus drivers won't install properly on my laptop.
Surface or Surface Pro? I ask because I don't know about you being able to load the appropriate drivers to recognize your tablet on Widows RT. Are you able to run command prompt? That's the biggest factor here.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
aarsyl said:
Surface or Surface Pro? I ask because I don't know about you being able to load the appropriate drivers to recognize your tablet on Widows RT. Are you able to run command prompt? That's the biggest factor here.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
It's the 1st gen surface. And I'm not sure if i can run a command promt. I'm sort of a noob.
If it's a surface 1/2 then no/not easily at all.
The drivers dont require custom code from goog to install on winrt, they only require generic usb libraries to make the fastboot driver work.
It would be as simple as ms releasing the missing pieces to driver devs, which they have much less reason to do as there's no expectation of support for arbitrary devices on winrt.
(I dont have a winrt device so I could be mistaken but) winrt generally requires you to obtain drivers straight from ms, I don't think they generally allow manufacturers to distribute windows/arm drivers like they do for windows/x86.
You need to be able to use fastboot, and there isnt a windows/arm version available.
It might be possible to compile an arm version, but it's highly unlikely anyone has actually done this.
Even if there was, you would need to use the hack to enable unsigned desktop apps to run on winrt.
Hi!
Because I wanted more privacy and security online I decided to buy a second hand Pixel 3 XL and want to install graphene OS. I've been trying for days now to make it work but I just cant get it to work and it's very frustrating:crying: so can someone please help me out??
I've been trying to install it on a windows pc and on a linux pc.
I'm not new to computers but I'm new to installing custom roms and new to linux.
This is what i'm following for installing it in windows:
Flashing GrapheneOS in Windows 10
Install or update the Android SDK Platform Tools:
Download and unpack the Standalone Android SDK Platform-Tools package: https://developer.android.com/studio/releases/platform-tools
Add a PATH Environment Variable to the unpacked folder (Windows 10: Control Panel > Advanced System Settings > Environment Variables)
Make sure that there are no other versions of Android SDK Platform Tools in your computer. Old versions will result to failures in image flashing.
Install or update the Google USB Device Driver:
Download the Google USB Device driver: https://developer.android.com/studio/run/win-usb
Open Windows OS Device Manager and find the new device that shows up when you plug in your phone
Update device driver (Windows 10: Device Manager > Universal Serial Bus devices > [Device Name] > Update driver) using the Google USB Device driver
Prepare the system image:
Download the factory system image that is appropriate for the device:
Important: Always use factory system images for installations. OTA system images are intended only for updates: https://grapheneos.org/releases
If possible, verify the system image integrity
Verify checksum
Check signature
Flash the system image into the device:
Notes:
First make sure that the stock system image is updated to the latest release to avoid any problems.
There is no need to turn on USB Debugging in Developer Options to flash a system image (even when sideloading with ADB in Recovery Mode.)
Enable OEM unlocking in Developer Options (Important: This requires internet access on devices with Google Play Services as part of Factory Reset Protection (FRP) for anti-theft protection.)
Unlock the bootloader:
Put the device in Fastboot Mode (Turn off the device then press and hold the Power and Volume Down Buttons at the same time until you see the Fastboot Mode Screen)
Connect to the computer and verify the connection: "fastboot devices"
Unlock the bootloader: "fastboot flashing unlock" (use the Volume then the Power buttons to confirm)
The device performs a factory reset then boots back to Fastboot Mode
Install the system image:
Open a Command window, go to the unpacked system image folder and run the flash-all.bat script
During the update, the device will reboot to fastbootd. Do not do anything and let the update continue
After it is done, choose option 'Reboot to bootloader' from the fastbootd menu to go back to Fastboot Mode
Re-lock the bootloader:
Lock the bootloader: "fastboot flashing lock" (use the Volume then the Power buttons to confirm)
The device performs a factory reset then boots back to Fastboot Mode
Complete the device configuration
Unplug the device from the computer and choose option 'Start' in Fastboot Mode to load the device OS
Perform device configuration
Click to expand...
Click to collapse
So the issues i'm facing are:
When I'm Trying to install using windows I can't get windows to recognize my phone.
I've installed platform tools but when i want to verify the fastboot connection it keeps saying waiting for device.
I've tried updating the driver many different times in many different ways but cant resolve the issue.
on a linux pc i'm following the manual from the website:
https://grapheneos.org/install
I downloaded platformtools but I cant set the PATH to update the version. and use the new version.
is there another way to install it? Or can someone guide me step by step exactly what to do?
thanks in advance!
Not sure if this will help any but perhaps try new a cable or a different USB port. I've read sometimes USB 2.1 works but USB 3.0 doesn't or vice versa.
Sent from my Pixel 3 XL
Eudeferrer said:
Not sure if this will help any but perhaps try new a cable or a different USB port. I've read sometimes USB 2.1 works but USB 3.0 doesn't or vice versa.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Thanks for your reply,
I got it to work! I misread one step, I connected the cable and instead of staying in fastboot mode (on the fastbootmode screen) I pressed start (power button) and proceeded to starting the OS. I thought that this was how it operated but now I understand how it works
i'm not really helping here but what is so good about GrapheneOS vs stock? i have never heard of them
masri1987 said:
i'm not really helping here but what is so good about GrapheneOS vs stock? i have never heard of them
Click to expand...
Click to collapse
Look at the GrapheneOS website and you'll find the answer.
In a nutshell: No Gapps or Play Services and securized kernel plus some other under-the-hood security improvements.
Only thing which i miss per default is the root access so i'm using it without AVB.
JaniceJop5843 said:
Hi!
Because I wanted more privacy and security online I decided to buy a second hand Pixel 3 XL and want to install graphene OS. I've been trying for days now to make it work but I just cant get it to work and it's very frustrating:crying: so can someone please help me out??
I've been trying to install it on a windows pc and on a linux pc.
I'm not new to computers but I'm new to installing custom roms and new to linux.
This is what i'm following for installing it in windows:
So the issues i'm facing are:
When I'm Trying to install using windows I can't get windows to recognize my phone.
I've installed platform tools but when i want to verify the fastboot connection it keeps saying waiting for device.
I've tried updating the driver many different times in many different ways but cant resolve the issue.
on a linux pc i'm following the manual from the website:
https://grapheneos.org/install
I downloaded platformtools but I cant set the PATH to update the version. and use the new version.
is there another way to install it? Or can someone guide me step by step exactly what to do?
thanks in advance!
Click to expand...
Click to collapse
Well... I'm not sure if you got your problem solved; however, now that the Pixel 3 no longer receives security updates, Graphene will no longer support their OS for your phone...
So, you can go with Lineage OS or do what I did and utilize Calyx OS.
I've had no issues thus far ..
does anyone have a graphene os build files for pixel 3xl? I want to return to stock and i must have deleted build. Thank you
I got and old Surface with windows RT 8.1. I went to settings and I reset it to factory (basically reinstalling the OS).
I wanted to upgrade to win 10 from a prepared bootable USB stick but it didn't boot from it. I tried also starting with vol-down and power button.
So I figured that I had to configure UEFI to be able to see the USB drive as boot option.
However, I can't enter UEFI. It just boots normally from the HD. After a lot of searching I tried :
- Vol up + power btn
- Shift+restart
- "shutdown /r /fw" from elevated command window
- There is no "UEFI Firmware Settings" entry found in Settings>Update & security>Recovery>Advanced startup>Troubleshoot >Advanced Options
- msifo32 shows that UEFI is present.
Any suggestions?
palosanto0 said:
I got and old Surface with windows RT 8.1. I went to settings and I reset it to factory (basically reinstalling the OS).
I wanted to upgrade to win 10 from a prepared bootable USB stick but it didn't boot from it. I tried also starting with vol-down and power button.
So I figured that I had to configure UEFI to be able to see the USB drive as boot option.
However, I can't enter UEFI. It just boots normally from the HD. After a lot of searching I tried :
- Vol up + power btn
- Shift+restart
- "shutdown /r /fw" from elevated command window
- There is no "UEFI Firmware Settings" entry found in Settings>Update & security>Recovery>Advanced startup>Troubleshoot >Advanced Options
- msifo32 shows that UEFI is present.
Any suggestions?
Click to expand...
Click to collapse
You can't, there is nothing configurable on an RT. Inserting the USB and powering on while holding volume - is all that is required.
To install 10 on an RT from USB you need to make sure you have removed Golden Keys if you had it applied otherwise the USB just won't boot. Beyond that the RT can reportedly be picky about what USB drives it will and won't boot from so I would recommend trying another drive. Have you tried booting an RT 8.1 recovery USB to confirm the drive is bootable under more normal conditions?
Thanks @jwa4
I created another RT8.1 recovery USB drive and this time I was able to boot to the 'blue' recovery screens.
It looks like the first USB stick wasn't created correctly.
I'm not particularly keen on installing win 10. I read that it runs sluggish and less snappy than 8.1 (which is not the fastest anyway on such small machine).
Is this the only way to run apps outside the MS store? Is there any way to run them in 8.1?
I found this very complete guide to installing 10
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
Would it be enough stopping after disabling secure boot to be able to install any desktop app in 8.1 or I need windows 10 to do so?
Thanks
palosanto0 said:
Thanks @jwa4
I created another RT8.1 recovery USB drive and this time I was able to boot to the 'blue' recovery screens.
It looks like the first USB stick wasn't created correctly.
I'm not particularly keen on installing win 10. I read that it runs sluggish and less snappy than 8.1 (which is not the fastest anyway on such small machine).
Is this the only way to run apps outside the MS store? Is there any way to run them in 8.1?
I found this very complete guide to installing 10
How to install Windows 10 on the Surface RT - Alexenferman
www.alexenferman.com
Would it be enough stopping after disabling secure boot to be able to install any desktop app in 8.1 or I need windows 10 to do so?
Thanks
Click to expand...
Click to collapse
It's still possible your USB was created correctly but was prevent from booting by Golden Keys jailbreak if you ever had it. To confirm you could try removing it using this (can also be used to assist in jailbreaking):
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
The guide you linked to is out of date. Windows 10 replacing Windows RT 8.1 isn't considered all that usable, it's just for fun really but if you are interested take a look at this:
Windows Media Builder - Windows
Automated preparation of Windows RT 8.1 & Windows 10 Installation Media
jwa4.gitbook.io
To run 3rd party ARM32 apps under Windows RT 8.1 my advice is to install Golden Keys, install Yahallo and then enable UMCI Audit Mode. Using this method you don't need to test sign everything and you can keep a fully up to date Windows RT 8.1 installation.
jwa4 said:
It's still possible your USB was created correctly but was prevent from booting by Golden Keys jailbreak if you ever had it. To confirm you could try removing it using this (can also be used to assist in jailbreaking):
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
The guide you linked to is out of date. Windows 10 replacing Windows RT 8.1 isn't considered all that usable, it's just for fun really but if you are interested take a look at this:
Windows Media Builder - Windows
Automated preparation of Windows RT 8.1 & Windows 10 Installation Media
jwa4.gitbook.io
To run 3rd party ARM32 apps under Windows RT 8.1 my advice is to install Golden Keys, install Yahallo and then enable UMCI Audit Mode. Using this method you don't need to test sign everything and you can keep a fully up to date Windows RT 8.1 installation.
Click to expand...
Click to collapse
All I really wanted is to be able to run apps outside the MS store. Not so much upgrade to win 10.
I never jailbroke the system, it's the original as far as I recall but I used recovery once to completely wipe and reinstall RT.
Is there a good guide or video for Yahallo and UMCI enabling?
Also, I imagine that I'll still be limited to ARM32 apps despite being outside the Windows store, right? So I still cant install say, firefox or regular desktop apps meant for X386.
Is it even worth the effort? Where can I find a list or repository of arm32 apps so that I can decide or not to do anything?
Thanks again
Correct, you would still be limited to ARM32 apps but these devices are really just for playing around with. As for an app repository, there is a Discord group where some ports are posted at but there isn't a massive selection: https://discord.gg/BGfMNjWX4B
There is an all in one jailbreak guide at:
Tegra Jailbreak USB - Windows
All-in-on jailbreak package for Tegra based Windows RT tablets
jwa4.gitbook.io
Alternatively there is information on them individually...
Golden Keys:
Golden Keys / Longhorn - Windows
Secure Boot Debug Policy
jwa4.gitbook.io
Yahallo:
Yahallo - Windows
Tegra 3 and Tegra 4 TrustZone UEFI variable services handler exploit and Secure Boot unlock tool
jwa4.gitbook.io
UMCI Audit Mode:
UMCI Audit Mode - Windows
Bypassing User Mode Code Integrity Check
jwa4.gitbook.io
Thanks. Nah, like you said, I was really playing with it ... I think I'll leave it as is and try to sell it.
Thanks so much!
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Try on Windows
ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.
limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.
limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...
simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.
Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.
TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.