Does anyone think that ADB and fastboot does not work properly on Acer laptops and specially for Motorola devices cause I have lot of errors when I try to use ADB on my Acer nitro 5 where is my other computer Dell handles everything properly!
The ADB and Fastboot drivers derived from Android SDK only properly work with Google devices ( e.g. Google Pixel series ).
Knowing this it should be obvious one always have to use the drivers provided by device's OEM.
Related
There seem to be a problem with fastboot for intel devices on linux. I am running Ubuntu 14.04 and I have an Asus Zenfone 5 a501cg. Adb works fine. I have updated the udev rules. When I try fastboot, the device is not even detected. I see the device connected in lsusb. But fastboot devices shows me nothing. And I have inserted the new device ID when the fastboot mode into the udev rules.
I mean when I installed Intel android drivers in windows, everything works fine. I have used fastboot in windows and it works. But when I use it in ubuntu, it does not work. I have tried searching around. And it seems that intel devices have a problem with fastboot in linux. There are similar questions in forums asked for lenovo phone with intel chip in the intel developer zone and the intel guys are telling why don't you update your udev rules blah blah blah..
Do you guys have same problem??????
Do you guys have a solution???????
I wasn't sure where to post this, as the only Blackview-related subforum is for one of their phones... Anyway, I recently bought Blackview Tab 8 (a 10" tablet), and I'm quite pleasantly surprised about its quality (even the box is almost wooden-like ) and the fact that they give you basically everything you need in the package (unlike some manufacturers who keep taking away things season by season...). Also, pure Android without any bloatware - there were a couple of games and apps I don't really need, but they can all be easily uninstalled, or at least disabled (the latter didn't reappear so far, I hope it stays that way).
Three questions for now:
- Any idea which ADB drivers should I install to be able to use adb on this device? I already have three on my Windows 7 computer from before, but connecting this device to the computer didn't find a suitable one.
- How can I remove the "silhouette" of Google Search widget/box on the home screen (other than the workarounds such as changing the launcher, or moving icons to a secondary page and leaving the silhouette alone)? It just stays there after disabling Google/Assistant/etc apps, but doesn't do anything and it can't be moved. I had a similar issue in the past (I think it was a Chuwi tablet).
- How can I tell if the device can be connected to an external display via USB-C to HDMI adapter?
Google's ADB & Fastboot drivers basically are both device and Android OS version independent. However how they got implemented by OEM/Carrier is different. Also in most cases it's required to install an additional "Android USB Driver" provided by OEM/Carrier to make ADB and/or Fastboot flawlessly work.
A link to an ADB / Fastboot installer is to be found in my signature.
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Neuromancer said:
I think I actually need those "additional drivers". From what I can see your script downloads what I already have (from platform-tools). adb.exe doesn't show any devices, though. The exclamation marks in Device Manager are at "ADB Interface" and 3x "Unisoc Phone".
Click to expand...
Click to collapse
Here you go:
Unisoc / Spreadtrum SPD drivers for Windows (SCI & USB)
Its important to install SPD drivers else Spreadtrum flash tools like Research Download, CM2 SPD etc won't be able to detect the phone. This is a collection of unsigned (.inf) drivers to be installed
forum.hovatek.com
I tried
Spreadtrum SCI Android USB drivers
Spreadtrum Drivers
SCI android usb driver jungo v4
SPD drivers 2018 ver2.0.0.131
but none of them worked.
In the end, I was able to make it work using these drivers:
How-to install SPD Driver R4.20.0201 (Easy Guide)
Step-by-step guidelines to download and install SPD Driver R4.20.0201 on Windows Computer to connect SPD/Unisoc Devices.
gsmusbdriver.com
But truth be told, I'm not sure if that was the only requirement (because there were also remnants from previous manual install from the link jwoegerbauer provided).
pretty much the only thing ive seen about it is https://source.android.com/devices/bootloader/fastbootd?authuser=1
but im interested to know what its actual point is. since on my phone when i use adb/fastboot reboot fastboot it doesnt let me use no fastboot or adb commands and in its ui you cant do anything either, which left me quite confused as why it even exists. havent come across any proper documentation or tutorials of it either so it all has just left me very confused.
Typically both the adb and the fastboot are executables to be run on Windows / MacOS / Linux computers. Their counterparts on Android device are adbd and fastbootd. Both requires Android device and computer got connected via USB-cable - preferredly the one that came with Android device. Neither adb nor fastboot have an UI, they only have a CLI, what is run on computer's shell.
On Android-side both the adbd and fastbootd are started when Android boots up.
Of course you also can run both the adb and the fastboot from within one Android device connected to another Android device, but this requires to have Termux shell installed on the one Android device, AFAIK.
A friend of mine has a Stylo 6 that says corrupted when it boots. It is however already set to USB debugging. However, I do not have access where I'm at to a PC or a Chromebook to install the dev tools. Is it possible even with third party paid software to install the dev environment on another Android phone and use it for fastboot etc?
You don't need to add ADB and/or Fastboot to any Android device. In common both ADB and Fastboot ( the latter only unless OEM decided to omit it ) are integral part of every Android release: ADB is housed in Android's user-space, Fastboot typically is part of device's bootloader unless Android has a Dynamic Partition layout, then Fastboot is also housed in Android's user space.
Ok, I guess what I need to know if I can install and use adb server on an Android device. I don't have access to a PC Mac or Chromebook to install the sdk tools. Can this be installed on my phone ( using a Linux or windows emulator maybe) to use to fix his phone?
ADB is nothing more than a tool that allows you to execute commands which would interact with Android shell. So you can install / open in Android a shell app ( e.g. Termux ) and run the commands ( Linux compliant ) therein. Will say you don't need a computer to operate on Android system of device,
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