I have redmi 3 pro and I'm using manjaro linux, I don't have Windows installed on my computer. When I boot my device into download mode lsusb recognizes my device as:
Code:
Bus 001 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
But when I type in the command fastboot devices it doesn't show anything, so I can't flash any ROMs in download mode.
Meanwhile when my device is in fastboot mode, lsusb shows:
Code:
Bus 001 Device 012: ID 18d1:d00d Google Inc.
and fastboot devices shows:
Code:
72ee6d057d03 fastboot
How can the command fastboot detect my device in download mode?
hillz said:
I have redmi 3 pro and I'm using manjaro linux, I don't have Windows installed on my computer. When I boot my device into download mode lsusb recognizes my device as:
Code:
Bus 001 Device 010: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
But when I type in the command fastboot devices it doesn't show anything, so I can't flash any ROMs in download mode.
Meanwhile when my device is in fastboot mode, lsusb shows:
Code:
Bus 001 Device 012: ID 18d1:d00d Google Inc.
and fastboot devices shows:
Code:
72ee6d057d03 fastboot
How can the command fastboot detect my device in download mode?
Click to expand...
Click to collapse
Perhaps has something to do with your udev rules? Make sure they are set up properly.
Sent from my SM-G800F using Tapatalk
Related
Hi
I have installed Arch Linux but cannot find suitable material on setting up drivers and utilities for flashing rom on Linux specifically arch linux.
I can setup arch even if instructions are available for other distro Linux Mint and Ubuntu so any link can come in handy.
I was using flashtool in windows but after shifting to Arch, I am not sure whats the right procedure to do it.
I have unlocked bootloader and rooted rom (FXP kernel + MIUI) installed as of now which I want to change asap.
Please help.
Regards
Hello,
You don't need any drivers,just install android-udev and android-sdk-platform-tools for adb and fastboot (both from aur).
Download latest flastool and run it from the terminal just like you do in windows (it requires jre and libusbx from official repos ).
Ok I have reinstalled fatsboot, android-sdk-platform-tools and openjre
Now I still cannot use fastboot devices , its list nothing.
Also since I should have adb available (from sdk-platform) when I run adb it says no command ?
Code:
[[email protected] fastboot]$ fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo fastboot devices
[[email protected] fastboot]$ sudo adb
sudo: adb: command not found
[[email protected] fastboot]$ adb
bash: adb: command not found
I have also installed udev-android , previous I created 51-android.rules manually but still doesnt work.
fastboot won't list the devices nor it works.
Code:
[sha[email protected] fastboot]$ lsusb
Bus 002 Device 005: ID 413c:2107 Dell Computer Corp.
Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 021: ID 0fce:5146 Sony Ericsson Mobile Communications AB
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First of all make sure you have enabled usb debugging on your phone.Adb and fastboot should be under /opt/android-sdk/platform-tools/ and also 51-android.rules file in /usr/lib/udev/rules.d/ (with -rw-r--r-- permissions).
With these things i have everything in my sytem to flash roms etc,maybe you're missing something with your installation.
Also for more information check wiki from archlinux wiki.archlinux.org/index.php/android
Hello, I m after some help.
I ve got an Allwinner A20 tv box, it worked fine for a few months then one day, after being on (but idle) for a few hours, I noticed the screen was blank but the light on the front was blue (indicating it was on, red is standby). It would not respond to the remote control or to anything, so I unplugged it and since then it will not boot and the screen is blank, the red light will light up but that is it. I ve eliminated the remote controller not working, but I cant boot the device.
So I ve tried connecting via ADB (with Ubuntu) but I cant get the device to show up after typing "adb devices".
I can get the vendor id and device id and I ve added it and the manufacturer to udev/modeswitch devices, but when I type "sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W"
I get the following error:
~/Android/sdk/platform-tools$ sudo usb_modeswitch -v 0x1f3a -p 0xefe8 -S -R -W
Take all parameters from the command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 2.1.1 (C) Josua Dietze 2014
* Based on libusb1/libusbx
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x1f3a
DefaultProduct= 0xefe8
SierraMode=1
NeedResponse=0
Look for default devices ...
found USB ID 048d:1336
found USB ID 1d6b:0002
found USB ID 19a8:2036
found USB ID 1f3a:efe8
vendor ID matched
product ID matched
found USB ID 1d6b:0001
found USB ID 062a:0102
found USB ID 1d6b:0001
Found devices in default mode (1)
Access device 004 on bus 003
Current configuration number is 1
Use interface number 0
USB description data (for identification)
-------------------------
Manufacturer: not provided
Product: not provided
Serial No.: not provided
-------------------------
Send Sierra control message
Error: Sierra control message failed (error -7). Abort
I ve searched Google for the error code but I cannot find anything.
The device was rooted and USB debugging was on.
Any help would really be appreciated.
Thanks
Hi, suddenly (without any ROM flash attempt) my IAIWAI AW920 tablet got in a bootloop.
IIRC it's a RK3066 but the RKAndroidTool/Finn Flash Tool didn't recognized the tablet with either PWR Vol+ or PWR Vol- boot modes.
In the past I got the tablet successfully rooted through some tools, so in some past era I was able to communicate with ADB from the Android SDK (Linux Mint Kernel +3.10) but before it got soft-bricked I had not the USB debugging bridge set and due a failing HDD I lost that environment setup.
While being connected to my laptop through USB cable I can access two modes:
USB + PWR + Vol+: Blank black screen but I detect a USB device with VID: 10d6 PID: 10d6 that doesn't seems to be an adb client.
USB + PWR + Vol-: Appears a Fastboot kind of picture (Android mascot laying in the floor with his chest open and a Red Warning Symbol ) but no output whatsoever in [dmesg] or [udev monitor]
In neither these modes adb or fastboot detect something
---- For the Vol+ mode with the 10d6:10d6 device ----
I can't get adb or fastboot to work, even with adb_usb.ini edited in windows or linux or several different udev rules
The only udev rule I could trigger was
#IAIWAI
SUBSYSTEM=="usb", ENV{ID_VENDOR_ID}=="10d6", SYMLINK+="android_adb", MODE="0666", GROUP="plugdev"
Click to expand...
Click to collapse
But it seems android_usb is not a link to a proper block device (the last number increases on each test)
ls -l /dev/
android_adb -> bus/usb/001/010
Click to expand...
Click to collapse
Or at least I can't make it work with
adb -p /dev/android_adb devices
or
fastboot -s /dev/android_adb devices
Extra information of the device found in Vol+ mode
lsusb:
Bus 001 Device 003: ID 10d6:10d6 Actions Semiconductor Co., Ltd
dmesg:
[11102.331560] usb 1-2: new high-speed USB device number 10 using ehci-pci
[11102.464620] usb 1-2: New USB device found, idVendor=10d6, idProduct=10d6
[11102.464633] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
udevadm monitor:
KERNEL[8596.157794] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
KERNEL[8596.158995] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
UDEV [8596.167280] add /devices/pci0000:00/0000:00:12.2/usb1/1-2 (usb)
UDEV [8596.171388] add /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 (usb)
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
P: /devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVPATH=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0
E: DEVTYPE=usb_interface
E: ID_VENDOR_FROM_DATABASE=Actions Semiconductor Co., Ltd
E: INTERFACE=255/255/255
E: MODALIAS=usb:v10D6p10D6d0100dc00dsc00dp00icFFiscFFipFFin00
E: PRODUCT=10d6/10d6/100
E: SUBSYSTEM=usb
E: TYPE=0/0/0
E: USEC_INITIALIZED=434099056
udevadm info --query=all --path=/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0 --attribute-walk:
looking at device '/devices/pci0000:00/0000:00:12.2/usb1/1-2/1-2:1.0':
KERNEL=="1-2:1.0"
SUBSYSTEM=="usb"
DRIVER==""
ATTR{bInterfaceClass}=="ff"
ATTR{bInterfaceSubClass}=="ff"
ATTR{bInterfaceProtocol}=="ff"
ATTR{bNumEndpoints}=="02"
ATTR{supports_autosuspend}=="1"
ATTR{bAlternateSetting}==" 0"
ATTR{bInterfaceNumber}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1/1-2':
KERNELS=="1-2"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="2"
ATTRS{idVendor}=="10d6"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{busnum}=="1"
ATTRS{devnum}=="4"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="128mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="80"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="0"
ATTRS{bcdDevice}=="0100"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="6"
ATTRS{ltm_capable}=="no"
ATTRS{removable}=="removable"
ATTRS{idProduct}=="10d6"
ATTRS{bDeviceClass}=="00"
looking at parent device '/devices/pci0000:00/0000:00:12.2/usb1':
KERNELS=="usb1"
SUBSYSTEMS=="usb"
DRIVERS=="usb"
ATTRS{bDeviceSubClass}=="00"
ATTRS{bDeviceProtocol}=="00"
ATTRS{devpath}=="0"
ATTRS{idVendor}=="1d6b"
ATTRS{speed}=="480"
ATTRS{bNumInterfaces}==" 1"
ATTRS{bConfigurationValue}=="1"
ATTRS{bMaxPacketSize0}=="64"
ATTRS{authorized_default}=="1"
ATTRS{busnum}=="1"
ATTRS{devnum}=="1"
ATTRS{configuration}==""
ATTRS{bMaxPower}=="0mA"
ATTRS{authorized}=="1"
ATTRS{bmAttributes}=="e0"
ATTRS{bNumConfigurations}=="1"
ATTRS{maxchild}=="5"
ATTRS{bcdDevice}=="0313"
ATTRS{avoid_reset_quirk}=="0"
ATTRS{quirks}=="0x0"
ATTRS{serial}=="0000:00:12.2"
ATTRS{version}==" 2.00"
ATTRS{urbnum}=="91"
ATTRS{ltm_capable}=="no"
ATTRS{manufacturer}=="Linux 3.13.0-37-generic ehci_hcd"
ATTRS{removable}=="unknown"
ATTRS{idProduct}=="0002"
ATTRS{bDeviceClass}=="09"
ATTRS{product}=="EHCI Host Controller"
looking at parent device '/devices/pci0000:00/0000:00:12.2':
KERNELS=="0000:00:12.2"
SUBSYSTEMS=="pci"
DRIVERS=="ehci-pci"
ATTRS{irq}=="17"
ATTRS{subsystem_vendor}=="0x1179"
ATTRS{broken_parity_status}=="0"
ATTRS{class}=="0x0c0320"
ATTRS{companion}==""
ATTRS{enabled}=="1"
ATTRS{consistent_dma_mask_bits}=="32"
ATTRS{dma_mask_bits}=="32"
ATTRS{local_cpus}=="00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000003"
ATTRS{device}=="0x4396"
ATTRS{uframe_periodic_max}=="100"
ATTRS{msi_bus}==""
ATTRS{local_cpulist}=="0-1"
ATTRS{vendor}=="0x1002"
ATTRS{subsystem_device}=="0xff1e"
ATTRS{numa_node}=="0"
ATTRS{d3cold_allowed}=="1"
looking at parent device '/devices/pci0000:00':
KERNELS=="pci0000:00"
SUBSYSTEMS==""
DRIVERS==""
Click to expand...
Click to collapse
The issue is now solved.
I'm trying to set up adb in Ubuntu 14.04.3 64bit but its not showing up when I connect my device.
Here is what I did
I installed adb and fastboot using these commands
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
I got the adb driver files from my device and executed it
Code:
sh ~/Desktop/adb_config_Linux_OSX.sh
The command got executed and adb_usb.ini file got created successfully at ~/.android/ folder.
Now I connected my device with USB debugging ON
When I run the adb devices command this is what I get
Code:
List of devices attached
The list of devices is empty.
When I run my lsusb command
Code:
Bus 001 Device 005: ID 0cf3:0036 Atheros Communications, Inc.
Bus 001 Device 003: ID 0bda:5756 Realtek Semiconductor Corp.
Bus 001 Device 010: ID 2a70:904d
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The vendor is not showing up. It is left blank.
I tried the same method in both MTP as well as PTP mode. Still no luck.
Could someone help me out please because I operate only on Ubuntu and can't use Windows.
Have you enabled `android debug`?
YumeMichi said:
Have you enabled `android debug`?
Click to expand...
Click to collapse
You mean usb debugging?? Yes I have
Run the script as root and you should be fine, tested with Linux Mint 17.2.
Not sure if it makes a difference, I made it executable with chmod +x and run as root from my home directory instead of using sh.
Solved the issue...The RSA fingerprint had to be accepted on the device.
Also I had to run all commands as administrator using sudo
Sent from my ONE E1003 using Tapatalk
So I have a few of these Kramer Panels which aren't supported anymore (The official webpage doesn't have them anymore but the same product here) and I want to wipe out the Kronomeet Software they got going on and install some other flavor of Android (I'm thinking Lineage OS).
To start I got adb and fastboot up and running with Aptitude.
Code:
$ adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
$ fastboot --version
fastboot version 28.0.2-debian
Connecting fine with adb, and using lsusb we see
Bus 001 Device 037: ID 2207:0011 Fuzhou Rockchip Electronics Company SmartTab
Googling around that name led me to the Rockchip Wiki, which had an article on Fastboot and a bunch of open source repos
https://opensource.rock-chips.com/wiki_Fastboot
Which states: "Rockchip uses 0x2207 as its USB vendor ID. This VID is not in Google's original fastboot code. So every fastboot command has to use "-i" parameter to specify vid to fastboot."
However, running -i on fastboot gives me an invalid option error:
Code:
$ sudo fastboot -i 0x2207 devices
fastboot: invalid option -- 'i'
I also tried downloading the most recent version of the android platform tools with fastboot version 33.0.3-8952118, which gave the same results.
Doing any other fastboot command without the -i just has < waiting for any device >
So essentially, I'm trying to figure out how to load a custom rom onto it, and what my next steps try are.
Other Misc Info I've tried:
In the Developer Settings on the tablet, there's no option to enable "OEM Unlocking"
Tablet doesn't have a power button, just a switch, so no pressing power and volume at the same time.
Rockchip seems to have a TWRP image available to build, which I would like to be able to fastboot flash (https://github.com/rockchip-software/TWRP/tree/android-9.0)
There's also a development tool (https://opensource.rock-chips.com/wiki_Rkdeveloptool) that also lets you load firmware.
Using adb reboot bootloader reboots the tablet to a black empty screen, which I can then communicate with the rkdeveloptool.
In this mode, lsusb returns a new name:
Code:
$ lsusb
Bus 001 Device 038: ID 2207:320a Fuzhou Rockchip Electronics Company RK3288 in Mask ROM mode
$ ./rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x320a,LocationID=106 Loader
$ ./rkdeveloptool ppt
**********Partition Info(parameter)**********
NO LBA Name
00 00002000 uboot
01 00004000 misc
02 00006000 resource
03 0000E000 kernel
04 00016000 boot
05 00026000 recovery
06 00036000 backup
07 00050000 cache
08 00090000 kpanic
09 00092000 system
10 00392000 metadata
11 0039A000 radical_update
12 003BA000 userdata
Found some more useful thread, and am trying to use rkflashkit. But still struggling to find out what .img to use.
Firmware Upgrade Guide For RK3188 RK3288 RK3368 Devices
UPD: Rreflashing guide for linux Host PC added. BEFORE START What you need: 1. Image file 2. Host PC (Windows) 3. USB OTG Cable Supported host OS: 1. Windows XP （32/64bit) 2. Windows 7 (32/64bit) 3. Windows 8 (32/64bit) All manipulations I...
forum.xda-developers.com
[Q] has anyone had success flashing a RK3126 based tablet?
Hello, I've got an irulu X30 (expro 30 plus) running stock firmware, nougat 7.1.2 I've been trying to use rkflashtool in linux and androidtool in windows. Both programs can report some device info and read partitions, the img files created...
forum.xda-developers.com