Hi,
In fastboot mode my linux distro (Debian testing) can see and reboot the device:
Output of lsusb:
Bus 003 Device 011: ID 0502:33a5 Acer, Inc.
but with ./adb devices, I cannot see anything:
No trace in lsusb, debug usb is on, udev rules are ok, adb_usb.ini is ok and with ADB_TRACE="all", everything is ok except that there is no device in adb...
Any clue?
Thanks.
Ps: I did google around...
Related
Hey all, I had a botched ICS upgrade on my Nexus S 4G today using Google's factory images. I can get into TWRP and into the bootloader, but my device is not recognized by any operating system that I have tried to connect it to. Swapping USB cables hasn't made a difference. My other NS4G can connect with no problems to any of these operating systems with any USB cable. While the phone does charge over USB while connected to a computer, I can't mount the SD card in TWRP and I can't use fastboot in the bootloader. With fastboot, the only message I get is "waiting for device."
Should I just cut my losses and jettison the phone? Any suggestions on how to remedy the situation?
Thanks in advance for your help.
Pitiful bump.
Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.
anglergab said:
Which factory image did you flash? What's the exact model of your phone? See the sticker beneath the battery.
Can you boot the mobile?
What was the problem through fastboot update?
Boot into bootloader/fastboot mode. What does it display?
Please provide a lot more details about the problem.
Click to expand...
Click to collapse
Thanks for the reply. Pretty sure I'm bricked unless I can get JTAG. I wasn't paying attention and it was super late at night when I was flashing for my wife (who was over custom roms). I mixed up bootloaders and sent the GSM version to my CDMA Nexus. I can't boot into Android. I can get into TWRP, but can't mount USB to get any files onto the device.
Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.
anglergab said:
Connect the phone to a Linux PC, then please post in this thread the output of the following commands:
Code:
tail /var/log/messages
Code:
lsusb
By the way you can reflash baseband/radio firmware image from recovery through ADB.
Click to expand...
Click to collapse
Thanks for the reply. I'll give it a shot in a few hours when I can get to a linux box. Part of the problem is that I get no recognition that the device is connected from any OS. I tried accessing the phone while it was in download mode through Heimdall running on Ubuntu and it couldn't see the phone.
I'll give the commands a try though and let you know. Should the phone be at the bootloader or in recovery?
You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.
anglergab said:
You can try connecting the phone first in bootloader and then recovery. Run the above commands in both modes. Connect the phone directly, without hubs, preferably with its own cable.
Click to expand...
Click to collapse
This is my output both times. The computer can't see the phone.
[email protected]:~$ tail /var/log/messages
tail: cannot open `/var/log/messages' for reading: No such file or directory
[email protected]:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 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 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 04f2:0841 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 005: ID 0781:5530 SanDisk Corp. Cruzer U3 4gb SDCZ36
Bus 001 Device 006: ID 0461:4d0f Primax Electronics, Ltd
Bus 002 Device 003: ID 0bda:0151 Realtek Semiconductor Corp. Mass Storage Device (Multicard Reader)
Bus 002 Device 004: ID 148f:3573 Ralink Technology, Corp.
[email protected]:~$
Click to expand...
Click to collapse
Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks
NikosDim said:
Hi everyone
I have a Sensation 4g and my system runs Ubuntu 12.04.
I was wondering if there is any way to make Internet Pass Through work with Linux?
In Windows, I install the HTC Sync and it works, but what about Linux?
Thanks
Click to expand...
Click to collapse
It works by default
In windows it asks for htc sync coz it need drivers to recognize the device
In Linux drivers are not necessarily required
You can just connect the device and use Internet pass through
(if you got adb working on that pc already then you are good to go)
Sent from my pyramid.. Through blazing fast sonic waves
I remember this as well on Ubuntu 11.04 - I only needed to modify some lines for ADB to get it work
well add the attached 51-android.rules file to /etc/udev/rules.d/ ( remove the .txt extension to the file ..i need to add it to attach in xda )
and chmod it to 755
(i.e chmod 755 /etc/udev/rules.d/51-android.rules )
then try the pass through it might work
For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
Unable to connect to PC
Either you don't have the latest version of HTC Sync installed on your PC, or another phone is already using Internet pass-through on your PC. Please ensure......etc
Click to expand...
Click to collapse
davebugyi what lines you needed to modify in the adb to get it work?
No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.
NikosDim said:
No one has an answer for this? If you are using Internet pass through without problems in your linux OS share what you did to make it work.
Click to expand...
Click to collapse
I've got my HIS working in Ubuntu 12.04 (DHD also). No root access or adb needed. Just simple script for Network Manager. I've posted a blog entry about this, it's in Russian, but you can use Google Translate to read it. http_://blog.loquens.org/?p=489
NikosDim said:
For me it is not working
Let me explain what I did.
First of all I connected my phone with the laptop. In the beginning the
Code:
adb devices
was giving me ??????????? but I restarted the server as root and then adb was recognizing my device properly.
Then I chose Internet Pass Through in my phone but despite the fact that Ubuntu recognize my phone as a Wired Connection 2 (Wired Network - HTC Android Phone) I don't have internet on my phone. Also when I chose the Internet Pass Through in my phone, the
Code:
adb devices
list is empty (is this normal?).
So, ganeshp I pasted the rules that you gave me in the /etc/udev/rules.d/ and I changed the permisions but no luck. It doesn't work.
Also, after enabling the Internet Pass Through after some minuter I get a failure message on my phone that says
davebugyi what lines you needed to modify in the adb to get it work?
Click to expand...
Click to collapse
all you have to do is to use sudo
HTML:
sudo adb devices
Do the following:
Press CTRL + ALT + T to open the Terminal.
Inside the terminal type:
Code:
lsusb
Output should look something like this
Code:
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 003: ID 0bb4:0c86 HTC (High Tech Computer Corp.) Sensation
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Take note of these two values 0bb4:0c86 next to the HTC (High Tech Computer Corp.) Sensation.
Then type:
Code:
sudo nano /etc/udev/rules.d/51-android.rules
That will open a file named 51-android.rules then type:
Code:
SUBSYSTEM="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c86", MODE="0666", OWNER="username"
In the text above change 0bb4 and 0c86 with the numbers you got from the lsusb, and instead of the username type youre user name.
Press CTRL + O and hit enter, then press CTRL + X .
if your adb-server was running up until now you need to kill it and restart it as root so type the following:
Code:
adb kill-server
sudo adb start-server
Then to check if everything worked out type
Code:
sudo adb devices
If all went well there should be an output similar this and you are good to go:
Code:
$ sudo adb devices
List of devices attached
BLABLABLA device
Edit: I assumed by the way that you have turned USB Debugging on :> that covers adb part, for the Internet pass trough you dont need drivers for linux just select the mode when you connect your device and you should be good to go.
Hi, all.
I went through the forums here and googled, but I can't find one working solution.
I have the tablet in subject (Acer Iconia B1-750).
I'd like to root it using guide I found on this forum and with modification for Ubuntu from here.
I can see my device in adb no problem.
When I run lsusb, I see device
Code:
Bus 003 Device 030: ID 0502:367b Acer, Inc.
So far so good.
When I do
Code:
adb reboot-bootloader
the device restarts to something called DROIDBOOT PROVISION OS.
When I type
Code:
lsusb
I can still see the device as
Code:
Bus 003 Device 031: ID 0502:3680 Acer, Inc.
So far so good.
However, when I do
Code:
sudo fastboot devices
I see no device connected.
I tried the -i 0x0502 switch for fastboot, did not help.
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
I tried to modify the ~/.android/adb_usb.ini, no help.
I also ensured I have correct permissions for plugdev on the device using udev rules and I do.
Does anyone have any advice how to force fastboot binary to "see" the device?
@sancho_sk Which Ubuntu version are you using?
Sent From my SM-G928F via Tapa
As I wrote:
I am working on Ubuntu 15.10, kernel 4.2.0-30-generic x86_64, my android-tools-adb and android-tools-fastboot show version number 4.2.2+git20130218-3ubuntu42.
Nobody? Seriously nobody works with Ubuntu?
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
rogerpanza said:
Hi, I have recently flashed the Evolution X (Android 11) ROM to my previously bricked device. I'm trying to install some APKs but I get the device offline error:
Code:
~ $ adb install ~/usr/local/Downloads/sh.ppy.osulazer.apk
Performing Push Install
adb: error: failed to get feature set: device offline
This hasnt happened in LineageOS or Pixel Experience.
And if you ask, yes the laptop is detecting the device
Code:
~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:5521 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 003: ID 046d:c534 Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 025: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I tried adding the /etc/udev/rules.d/51-android.rules file with the following contents:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", GROUP="adbusers"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="04e8",ATTR{idProduct}=="6860",SYMLINK+="android_fastboot"
Then restarted my computer, reloaded udev rules but it still doesnt work. Yes, my user is part of the adbusers group. Also tried as root user but same thing. I'm on Arch Linux btw.
Is there any way to fix this or do I just go back to PixelExperience/LineageOS?
Click to expand...
Click to collapse
Restart your device.
SubwayChamp said:
Restart your device.
Click to expand...
Click to collapse
I've done that tons of times
rogerpanza said:
I've done that tons of times
Click to expand...
Click to collapse
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
SubwayChamp said:
Well, you didn't mention it, it looks like all is fine with Linux, it could be an error on the ROM side anyway check that you killed ADB server previously, and you don't have many devices attached to the PC. You should try running a terminal from user space like Desktop or Downloads (moving the app there) and not from the root directory to see if something change.
Click to expand...
Click to collapse
I only have my phone plugged into my laptop, tried moving /usr/bin/adb to another folder as you said but same thing. And yeah it's most probably a ROM problem :/
Hello, guys
first i read the diff between soft/hard brick, and i think i'm in the soft case, cause i can get in recovery menu.
adb dont see the phone at all,
fastboot can, but not 'fastboot oem unlock' , neither 'fastboot boot recover.img' works. Actually command prompt wait there for ever, untin the PC kernel ( linux deb 11), break fastboot usb connection, with a reason of connection timeout. this timeout is after 30minutes ....
i manage to backup user data for the recovery menu, in 3 files 2x2G 1x1.7G ( i think because of fat ),
but the revcovery menu fail to [ wipe data/factory reset ]. Strange ? Any ideas?
here is the model f the tablet,
==> /var/log/syslog <==
Nov 6 20:12:48 localhost kernel: [1024828.830129] usb 5-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
Nov 6 20:12:48 localhost kernel: [1024828.830135] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 6 20:12:48 localhost kernel: [1024828.830138] usb 5-2: Product: Android
Nov 6 20:12:48 localhost kernel: [1024828.830140] usb 5-2: Manufacturer: MediaTek
Nov 6 20:12:48 localhost kernel: [1024828.830142] usb 5-2: SerialNumber: mt6582_phone
#---------------------------------------------------------------------------------------------------
# ID 0bb4:0c01 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo / FP1
#---------------------------------------------------------------------------------------------------
# Android system recovery (3e)
# A7-30DC_S0000129_150831_ROW
#---------------------------------------------------------------------------------------------------
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
jwoegerbauer said:
1. To successfully run ADB and/or Fastboot commands you need to have installed on computer the "Android USB Driver" provided by device's manufacturer.
2. ADB only will work if it got enabled on Android device.
Click to expand...
Click to collapse
i know, everythinks works just fine, with other android devices.
( i'm using linux by the way )
My problem right now is,
why the stock recovery fail to wipe/factory reset ?
no fastboot or adb
The tablet stuck in he lenovo logo on boot for ever,
so adb dont have any way in this stage
I try 'update cache from ADB' just to see if adb can see it, but no
when 'fastboot boot recovery.img'
the phone (tablet), report get some bytes
but nothing else
when 'fastboot oem unlock', nothing happens, both the phone and the terminal
i use this links for recovery images:
https://forum.xda-developers.com/attachments/recovery_p780_cwm_6-0-1-5-7z.2840100/
https://forum.xda-developers.com/attachments/p780_recovery_twrp_2-6-3-0-zip.2840101
any pins on hardware, to triger factory reset .... ?