Is there any way to recover from the "wheelie --blob blob.bin" error 3./wheelie -r --blob blob.bin. I do have my nvflash backups and could have recovered my prime, but made I guess a major mistake using semi-automated recovery.
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d078775080a06
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Error sending data (-1): LIBUSB_ERROR_IO
Sending file: 100 %
Error sending data (-1): LIBUSB_ERROR_IO
[+] Sending ODMData 0x5
Error sending data (-1): LIBUSB_ERROR_IO
Error sending data (-1): LIBUSB_ERROR_IO
[+] Sending bootloader...
Error sending data (-4): LIBUSB_ERROR_NO_DEVICE
[-] Error -4 sending command
I appreciate all the work that folks on this site have done. I think I know the answer based on what others have posted. I'm just looking for confirmation.
Thanks for all your help.
:cyclops:
jmasi50 said:
Is there any way to recover from the "wheelie --blob blob.bin" error 3./wheelie -r --blob blob.bin. I do have my nvflash backups and could have recovered my prime, but made I guess a major mistake using semi-automated recovery.
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d078775080a06
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Error sending data (-1): LIBUSB_ERROR_IO
Sending file: 100 %
Error sending data (-1): LIBUSB_ERROR_IO
[+] Sending ODMData 0x5
Error sending data (-1): LIBUSB_ERROR_IO
Error sending data (-1): LIBUSB_ERROR_IO
[+] Sending bootloader...
Error sending data (-4): LIBUSB_ERROR_NO_DEVICE
[-] Error -4 sending command
I appreciate all the work that folks on this site have done. I think I know the answer based on what others have posted. I'm just looking for confirmation.
Thanks for all your help.
:cyclops:
Click to expand...
Click to collapse
Are you on a Linux PC ?
Thx Josh
Bricked TF201
lj50036 said:
Are you on a Linux PC ?
Thx Josh
Click to expand...
Click to collapse
Yes, Ubuntu 14.04:good:
Output of lsusb command
jmasi50 said:
Yes, Ubuntu 14.04:good:
Click to expand...
Click to collapse
lsusb
Bus 002 Device 035: ID 0955:7330 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 17ef:1003 Lenovo Integrated Smart Card Reader
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 04d9:2517 Holtek Semiconductor, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I can see the NVidia USB device, however, I think I'm stuck somewhere in between APX mode, since I'm getting error 3 whenever I try to send any commands to the tablet.
Thanks again for the reply.
jmasi50 said:
lsusb
Bus 002 Device 035: ID 0955:7330 NVidia Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 17ef:1003 Lenovo Integrated Smart Card Reader
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 04d9:2517 Holtek Semiconductor, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I can see the NVidia USB device, however, I think I'm stuck somewhere in between APX mode, since I'm getting error 3 whenever I try to send any commands to the tablet.
Thanks again for the reply.
Click to expand...
Click to collapse
You're running the command as sudo yes ?
sudo
lj50036 said:
You're running the command as sudo yes ?
Click to expand...
Click to collapse
Yes, I executed all of the recovery commands with sudo
Thank you, I appreciate your help.
linux
I comfortable with linux and the command line, if that helps.
Thanks again
jmasi50 said:
I comfortable with linux and the command line, if that helps.
Thanks again
Click to expand...
Click to collapse
You did try a diff usb ports ?
Show me the exact commands you'er running plz ...
Thx Josh
Commands
lj50036 said:
You did try a diff usb ports ?
Show me the exact commands you'er running plz ...
Thx Josh
Click to expand...
Click to collapse
I used 2 different laptops to try to recover so far. Both laptops have Ubuntu 14.04 installed. As i said in my original post, I messed up trying to recover, so my circumstance is not a result of things not working. Initially, wheelie --blob blob.bin worked correctly.
The output below is from taken from a session I'm running now.
sudo lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
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 003: ID 8087:07dc Intel Corp.
Bus 003 Device 009: ID 0955:7330 NVidia Corp.
Bus 003 Device 004: ID 5986:0536 Acer, Inc
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d078775080a06
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error 3 sending command
lsusb output after running wheelie
[email protected]:~/NVFlash$ sudo lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
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 003: ID 8087:07dc Intel Corp.
Bus 003 Device 009: ID 0955:7330 NVidia Corp.
Bus 003 Device 004: ID 5986:0536 Acer, Inc
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
As you can see the NVidia device is still connected
Running wheelie again produces the following output
sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
Error receiving data (-8): LIBUSB_ERROR_OVERFLOW
[=] Chip UID: 0x0
Error receiving data (-4): LIBUSB_ERROR_NO_DEVICE
[-] RCM_Receive communication failure.
I've reset the tablet into APX mode first power off then ( power + volume up)
sudo lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
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 003: ID 8087:07dc Intel Corp.
Bus 003 Device 011: ID 0955:7330 NVidia Corp.
Bus 003 Device 004: ID 5986:0536 Acer, Inc
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/NVFlash$
[email protected]:~/NVFlash$ sudo ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d078775080a06
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error 3 sending command
I guess if wheeie doesn't run correctly to set up NVFlash, you can't go any farther, am I coorect. I've seen some mentions of wheelie version 0.2 but haven't been able to find it. HAve you heard of it?
Thanks again for looking into this.
I have the same issue with Error 3 (both on Windows & Linux). If you find any solution, please contact with me.
Will do
Clamor said:
I have the same issue with Error 3 (both on Windows & Linux). If you find any solution, please contact with me.
Click to expand...
Click to collapse
I think we're stuck for now. Maybe someone will come up with a fix
Related
I apologize if this is in the wrong area, but there is no sub-forum for the phone in question and this seemed the most relevant place to post.
I'm trying to get ADB to detect my wife's phone, a Coolpad E239. My Nexus One detects fine. However, whenever I plug in my wife phone and run the command adb devices, I get this:
Code:
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $
I don't get a bunch of question marks so I don't think it's a permissions issue. When I type lsusb into terminal, I get this:
Code:
[email protected] ~ $ lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 003: ID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0
Bus 005 Device 002: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 048: ID 1ebf:6045
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I'm thinking the 1ebf:6045 is the phone, but it doesn't seem to be showing up. Does anyone have any suggestions?
Hi guys,
I have used the following tutorials:
http://forum.xda-developers.com/showthread.php?t=735375
http://forum.xda-developers.com/showthread.php?t=921169&page=2
But still when I type "./adb devices" or "sudo ./adb devices" all I get is "List of aevices attached" followed by a blank. Do you know a way to fix this?
I'm using a Samsung Galaxy Tab.
Thanks in advance.
Could you paste your dmesg? What's your OS?
Could you paste your 51-android.rules and output of lsusb?
My OS is Ubuntu 11.10
The output of lsusb is:
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:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 03f0:5c11 Hewlett-Packard PhotoSmart C4200 Printer series
Bus 003 Device 002: ID 045e:00f7 Microsoft Corp. LifeCam VX-1000
Bus 006 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 006 Device 003: ID 045e:0730 Microsoft Corp.
Bus 002 Device 005: ID 04e8:6877 Samsung Electronics Co., Ltd
Click to expand...
Click to collapse
The 51-android-rules file contains
SUBSYSTEM==usb, SYSFS{idVendor}==0bb4, MODE=0666
Click to expand...
Click to collapse
Are you using the stock USB cable that came with your tablet? Is the cable in good shape?
I had a Samsung device that would not show up under my devices in Ubuntu. I later discovered it was because my cable was damaged internally. It charged, but had trouble connecting for data.
Is there any way this could be the issue?
adb driver
are you sure you have install the adb driver ?
The vendor id in your udev file is the HTC vendor id.. you should use the samsung one: 04e8
Besides, you can just try:
adb kill-server
and then:
sudo adb start-server
and see if you can get your device listed
it's so easy, just turn off your android device, then hold down both "Volume Down" key and "Power" at the same time, wait a few seconds till it start in recovery mode, done.
now type adb devices, and you'll see your device.
So, I have an HTC Evo 4G running Gingerbread Deck 1.3, with the Tiamat Evo v4.1 kernel (2.6.38.8) and I've been having issues with the wired/USB tether. I've been trying it connect to two laptops running Ubuntu 11.10 and 12.04 and it doesn't work on either. I ran ifconfig on both and USB0 interface doesn't show up. I'm using the native tethering app, but I also used Wired Tether 1.4, and that didn't work. The log didn't show any errors. I can't find anything wrong with either laptop or the phone besides the fact that USB0 is not showing up and no tethering. The hotspot/wifi tether works fine, and I can mount the SD card fine. Could someone help me out?
UPDATE: So, I tried tethering again with a live USB boot of Ubuntu, and still nothing. Clearly this is an issue with the phone. I recall this feature working before, but I can't remember if it was with gingerbread deck or CM7. I had this problem before with my Epic 4G, but it had something to do with the USB stack. Is that still an issue? Any tips on finding out the root of the problem?
*bump*
*bump*
Sent from my PC36100 using XDA
I'm not an expert, but I'll give a try. Can you please do lsusb and dmesg|tail commands after connecting the phone?
from Ad!MoBiLe:: LGP698 Optimus Net Dual
acorreya said:
I'm not an expert, but I'll give a try. Can you please do lsusb and dmesg|tail commands after connecting the phone?
from Ad!MoBiLe:: LGP698 Optimus Net Dual
Click to expand...
Click to collapse
I'm not sure if you wanted me to attempt to tether or not when connected.
Here are the outputs NOT tethered:
Code:
[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:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
Bus 002 Device 003: ID 064e:a115 Suyin Corp.
Bus 008 Device 002: ID 0d7d:ac06 Phison Electronics Corp.
Bus 002 Device 007: ID 0bb4:0c8d High Tech Computer Corp. EVO 4G (debug)
Code:
[email protected]:~$ dmesg|tail
[ 129.487703] usbcore: registered new interface driver cdc_ether
[ 130.956095] rndis_host 2-1:1.0: RNDIS init failed, -110
[ 130.956154] rndis_host: probe of 2-1:1.0 failed with error -110
[ 130.956231] usbcore: registered new interface driver rndis_host
[ 482.085851] usb 2-1: USB disconnect, device number 6
[ 496.104133] usb 2-1: new high-speed USB device number 7 using ehci_hcd
[ 496.253090] scsi7 : usb-storage 2-1:1.0
[ 497.255140] scsi 7:0:0:0: Direct-Access HTC Supersonic 0100 PQ: 0 ANSI: 2
[ 497.255732] sd 7:0:0:0: Attached scsi generic sg2 type 0
[ 497.265129] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Here are the outputs tethered:
Code:
[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:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader
Bus 002 Device 003: ID 064e:a115 Suyin Corp.
Bus 008 Device 002: ID 0d7d:ac06 Phison Electronics Corp.
Bus 002 Device 006: ID 0bb4:0c04 High Tech Computer Corp.
Code:
[email protected]:~$ dmesg|tail
[ 123.241994] type=1400 audit(1337702014.006:30): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince" pid=2537 comm="apparmor_parser"
[ 123.243551] type=1400 audit(1337702014.006:31): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=2540 comm="apparmor_parser"
[ 123.243940] type=1400 audit(1337702014.006:32): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=2540 comm="apparmor_parser"
[ 123.245642] type=1400 audit(1337702014.010:33): apparmor="STATUS" operation="profile_replace" name="/usr/bin/evince//launchpad_integration" pid=2537 comm="apparmor_parser"
[ 129.045723] usb 2-1: USB disconnect, device number 5
[ 129.320166] usb 2-1: new high-speed USB device number 6 using ehci_hcd
[ 129.487703] usbcore: registered new interface driver cdc_ether
[ 130.956095] rndis_host 2-1:1.0: RNDIS init failed, -110
[ 130.956154] rndis_host: probe of 2-1:1.0 failed with error -110
[ 130.956231] usbcore: registered new interface driver rndis_host
So, i reflashed GBDeck 1.3 and USB tethering works fine. I suspect it might've been a kernel issue.
Great to know!
from Ad!MoBiLe:: LGP698 Optimus Net Dual
Hi,
I guess I brought myself into trouble today.
I have an alldaymall A88S 8GB tablet which I have bought on eb*y. Today I sent a "adb reboot bootloader" to it. That resulted in a mode where a little green robot is visible in the middle of the screen.
Now I can't power down the device. Pressing the power button results into a dark screen and then the green robot again. Power+Vol leads to the same.
Adb and fastboot show no device. lsusb still lists the device.
Any suggestions?
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
theodleif said:
I was lucky.
Although fastboot did not show any devices, a "fastboot -i 0x1f3a reboot" did the job.
Click to expand...
Click to collapse
Thanks man! This really helped. I was stuck for couple of hours.
My Mediacom SmartPad Go MP726GOG was stuck after issuing "adb reboot bootloader". My vendor device was the same as yours (1f3a), but in case someone else is stuck, you can check the connected devices (on linux, at least) with the command lsusb.
Code:
$ lsusb
Bus 007 Device 047: ID 1f3a:1010 Onda (unverified)
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 002: ID 0cf2:6230 ENE Technology, Inc. SD Card Reader (UB623X)
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 09da:0260 A4Tech Co., Ltd. KV-300H Isolation Keyboard
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 09da:9090 A4Tech Co., Ltd. XL-730K / XL-750BK / XL-755BK Mice
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
where you can see the onda device with id 1f3a:1010.
There should also be a windows specific way to get the vendor id, probably device manager or similar, but I am not familiar with windows.
Cheers!
Need Firmware for this unit any help
alldaymall model:A88S
A33
My oneplus x is rooted and running latest orion os. The problem is that it is not appearing in lsusb command in Ubuntu 16.04. When I connect my phone nothing appears. But I can use my phone for usb tethering to connect my pc to internet. I want to be able to use mtp & adb. Can anyone help?
And here is the output of lsusb:
Code:
$ lsusb
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 005: ID 05c6:6769 Qualcomm, Inc.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 008: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 006: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Update: Interesting when I disconnect my phone "Bus 002 Device 005: ID 05c6:6769 Qualcomm, Inc. " disappears.
Bump!
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
raulx222 said:
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
Click to expand...
Click to collapse
Can u send me the default mac os driver .sh file which can be obtained by emulated cdrom of onyx? May be installing that will help.
raulx222 said:
I don't know..but my onyx is recognized on Ubuntu. I have installed Android Studio from here, maybe that's why.
Click to expand...
Click to collapse
Ok after installing android studio, my device is actually being shown in the nautilus as mtp device but when I click on it following error occurs:
Unable to open MTP device '[usb:002,009]'
The output of lsusb is still the same i.e.:
Code:
$ lsusb
Bus 002 Device 009: ID 05c6:6765 Qualcomm, Inc.
Bus 002 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sixline said:
Ok after installing android studio, my device is actually being shown in the nautilus as mtp device but when I click on it following error occurs:
Unable to open MTP device '[usb:002,009]'
The output of lsusb is still the same i.e.:
Code:
$ lsusb
Bus 002 Device 009: ID 05c6:6765 Qualcomm, Inc.
Bus 002 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 001 Device 003: ID 0bda:8178 Realtek Semiconductor Corp. RTL8192CU 802.11n WLAN Adapter
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Make sure you are using latest Ubuntu and have your phone's screen unlocked. Also make sure that your cable works properly, maybe try another one.
raulx222 said:
Make sure you are using latest Ubuntu and have your phone's screen unlocked. Also make sure that your cable works properly, maybe try another one.
Click to expand...
Click to collapse
Well I am using ubuntu 16.04 lts as i mentioned in the op so its the latest. And i am using the oem cable came with the device. I ve also checked with two more cables which are working with other phones.
Sent from my ONE E1003 using XDA-Developers mobile app
Well atleast adb is now recognizing my device by following the procedure given by Evan Carroll at http://askubuntu.com/questions/461729/ubuntu-is-not-detecting-my-android-device
Now only problem remains is the mtp which return error: Unable to open MTP device '[usb:002,018]'
sixline said:
Well atleast adb is now recognizing my device by following the procedure given by Evan Carroll at http://askubuntu.com/questions/461729/ubuntu-is-not-detecting-my-android-device
Now only problem remains is the mtp which return error: Unable to open MTP device '[usb:002,018]'
Click to expand...
Click to collapse
Can you try to reboot phone while the phone is plugged?
Kéno40 said:
Can you try to reboot phone while the phone is plugged?
Click to expand...
Click to collapse
Yes I can reboot my phone using adb.
sixline said:
Yes I can reboot my phone using adb.
Click to expand...
Click to collapse
Edit sorry , I meant :
Try to reboot your computer while the phone is plugged
Edit : An outdated french guide with Go-MTPFS (not sure it could help)
http://korben.info/installer-nexus-7-android-4-0-ubuntu.html
Kéno40 said:
Edit sorry , I meant :
Try to reboot your computer while the phone is plugged
Edit : An outdated french guide with Go-MTPFS (not sure it could help)
http://korben.info/installer-nexus-7-android-4-0-ubuntu.html
Click to expand...
Click to collapse
Thanks for your concern but I switched rom to sultan's cm13, after that its working.