Tried a few methods for getting root, none of which worked. I'm running a d851 with d85120g software. Ubuntu as my desktop. Here's a step by step pulled from various sources.
1. Put your phone in developer mode. Go to settings-->about phone. Click on build 8ish times until you see "you're a developer"
2. Go to settings-->developer options-->enable USB debugging
Now we need the desktop to recognize the phone
3. In your favorite text editor, you'll need to create a text file named /etc/udev/rules.d/51-android.rules
4. Copy this line into the file and save it:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
(Source here)
5. In a terminal:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
6.
Code:
sudo service udev restart && sudo killall -9 adb
6a. Get this file and
Code:
sudo chmod a+r ./qcdlcomm.py
from that directory. (Source)
Next steps are modified from here.
7. Download and extract the zip file: http://bit.ly/1Ln9FKB .
7a. Move qcdlcomm.py to wherever you extracted the above file.
8. Connect your phone. At some point you can choose your USB connection type. Reports state it only works with PTP mode (v. MTP), but I didn't try MTP.
9. Terminal:
Code:
adb devices
You should see your phone listed. Then, in the same directory as the files from step 7:
10.
Code:
adb push ./busybox /data/local/tmp && adb push ./UPDATE-SuperSU-v2.46.zip /data/local/tmp
Now you want to get in download mode.
11. Unplug and turn off your phone, then hold volume up as you plug the cable back in. You should see "download" or something on the screen.
Next steps taken from here.
12.
Code:
ls /dev/ttyUSB*
Make note of the devices. You'll try the highest device number first in a few steps.
13.
Code:
sudo rmmod cdc_acm && sudo rmmod usbserial
You'll get an error if there's anything else using usbserial. If so, sudo rmmod that module, then rerun
Code:
sudo rmmod usbserial
14.
Code:
sudo modprobe usbserial vendor=0x1004 product=0x633e
15.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*< ./root
Replace the device with the output from step 12. Something should happen here. (BTW, at some point the phone screen says "flashing firmware" or something. There's a progress bar. It never moves past 0%"
16. Type "LEAVE" at the hash prompt that's left. At this point, your phone may not reboot. If not, type "exit" (or ctrl+c) and disconnect your phone. Then reconnect the phone.
17.
Code:
ls /dev/ttyUSB*
again. You may have lost a usb device. If so, repeat:
18.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*
with the next highest device from above.
19. Type "LEAVE" again. Device should reboot. You should have root.
Some of this from memory, so if anyone has any suggestions, LMK. Hope this helps someone.
Good
Sent from my SM-G361H using Xposed Modules
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
slow64 said:
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
Click to expand...
Click to collapse
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
nola mike said:
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
Click to expand...
Click to collapse
I notice my product ID differs from yours. Is this unimportant? I have been really wanting to get root on this for a while now, and this is the most promising looking aggregation of all available information I've found so far.
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
nola mike said:
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
Click to expand...
Click to collapse
I was thinking I'd just substitute my ProdID in the necessary locations.
dmesg:
Code:
[11036.082260] usb 3-2: new high-speed USB device number 10 using ehci-pci
lsusb:
Code:
[~]$ lsusb | grep LG
Bus 003 Device 010: ID 1004:631d LG Electronics, Inc. Optimus Android Phone (Camera/PTP Mode)
Sounds good, keep us updated.
Well, just got my third d851, running v30e firmware. Now doesn't work, getting stuck at step 15. When I plug in in download mode, the phone switches to the "firmware update" screen before I do anything. This is the dmesg output.
Code:
[ 6277.744082] usb 1-1: new high-speed USB device number 28 using ehci-pci
[ 6277.893938] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6277.893944] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6277.893948] usb 1-1: Product: LGE Android Phone
[ 6277.893950] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6277.893953] usb 1-1: SerialNumber: LGD8511199581b
[ 6277.894874] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6277.894890] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6277.895019] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6277.900634] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6277.900638] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6277.900641] usbserial_generic 1-1:1.2: generic converter detected
[ 6277.900827] usb 1-1: generic converter now attached to ttyUSB0
[ 6534.787683] usb 1-1: USB disconnect, device number 28
[ 6534.791136] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 6534.791175] usbserial_generic 1-1:1.2: device disconnected
[ 6550.456114] usb 1-1: new high-speed USB device number 29 using ehci-pci
[ 6550.605565] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6550.605571] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6550.605574] usb 1-1: Product: LGE Android Phone
[ 6550.605578] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6550.605581] usb 1-1: SerialNumber: LGD8511199581b
[ 6550.606530] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6550.606559] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6550.606720] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6550.612943] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6550.612948] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6550.612951] usbserial_generic 1-1:1.2: generic converter detected
[ 6550.613624] usb 1-1: generic converter now attached to ttyUSB0
Related
Hey all,
So I was using my KF just fine with hashcode's AOSP Jelly Bean rom. That rom was on there for more than a month and then suddenly ,as of yesterday, adb refuses to connect. Fastboot on the other hand works just fine.
I'm running Debian Squeeze on and old Thinkpad R51. Both adb and fastboot binaries are in my PATH, and my 51-android.rules looks as follows...
Code:
# Amazon
SUBSYSTEM=="usb", ATTRS{idVendor}=="1949", MODE="0666", GROUP="plugdev"
# HTC
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
# Lenovo
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666", GROUP="plugdev"
# Motorola
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
Running "adb kill-server" and then "adb devices" does not show the device at all. I switched to the jandykane rom and it's still the same. I'm currently in the stock amazon 6.3.1 rom and still I get nothing. I did a full /cache /data /system /sdcard wipe after installing each rom. Running "lsusb" I get...
Code:
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 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 040: ID 1949:0006 Lab126
Bus 001 Device 002: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And running "dmesg | tail" (only posted what is shown after I plug in the KF), I get...
Code:
[ 8851.136202] usb 1-4: new high speed USB device using ehci_hcd and address 40
[ 8851.269079] usb 1-4: New USB device found, idVendor=1949, idProduct=0006
[ 8851.269090] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8851.269099] usb 1-4: Product: Kindle
[ 8851.269106] usb 1-4: Manufacturer: Amazon
[ 8851.269114] usb 1-4: SerialNumber: 1CDE000600000001
[ 8851.270544] usb 1-4: configuration #1 chosen from 1 choice
[ 8851.277370] scsi29 : SCSI emulation for USB Mass Storage devices
[ 8851.284978] usb-storage: device found at 40
[ 8851.284986] usb-storage: waiting for device to settle before scanning
[ 8856.290243] usb-storage: device scan complete
[ 8856.290897] scsi 29:0:0:0: Direct-Access Amazon Kindle 0001 PQ: 0 ANSI: 2
[ 8856.295474] sd 29:0:0:0: Attached scsi generic sg3 type 0
[ 8856.316198] sd 29:0:0:0: [sdc] Attached SCSI removable disk
I am able to do adb commands just fine on a Droid X2. The DX2 is shown in the device list and I can successfully send commands. I've used the same cable for both the DX2 and the KF. I've tried another working cable and still nothing. I can successfully use adbWireless to send commands. I even went as far as clean installing Debian Wheezy and setting up the udev rules for adb/fastboot access, and still no success.
Is there anything I can try to fix this problem. What could cause fastboot to work but not adb. My best guess is that it may be hardware failure.
Oh and one last thing, In hashcode's jelly bean rom, I was able to mount the sdcard partition when connected via usb to my computer. I could browse the drive and everything. It also works on the stock amazon 6.3.1 update.
Also, I've been using an adb and fastboot binary that has been compiled with the Amazon device id included in the source code (0x1949). I've been using those binaries for the longest without any problems but I don't know if they could have caused any hardware damage.
I noticed as well some changes in device id's . Make a backup and flash this http://forum.xda-developers.com/showthread.php?t=1778010 see if your adb doesn't again work just out of curiosity
Edit: some have complained about not having adb access after flashing JB but this I believe only existed on windows on Linux that should not have become a problem because of static drivers.
The problem seems to be my Thinkpad. I have no idea what happened to it considering USB mass storage mode and fastboot work perfectly fine. I've now plugged the KF to my desktop and I can see my device and am able to send commands via adb just fine. That's weird.
Stranger things have happened I would think more common to have no fastboot and have adb but yes that's strange
Hi everyone,
I am not a developer, i searched for finding how to make motorola xoom WIFI to connect with Huawei LTE 4G E392,
But i didn`t find.
So please if someone can help developing.
Here is what i found
zerox981 said:
This is the way I get my dongle (Vodafone K4605) working with the latest TeamEOS nightly wingray (84 atm ).
Tools I use:
WinSCP - http://winscp.net/eng/index.php
SSHdroid - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroid&hl=en
putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/
1) Download the latest development overlay from this thread:
http://forum.xda-developers.com/showthread.php?t=1513490
2) Delete the drivers you don't need from the zip file. (xoom_dev_overlay_v4.zip\data\local\lib\modules\).
For my needs it's enough to keep only the option.ko and usb_wwan.ko.
3) Flash the dev. overlay.
4) Install pppd, usb_modeswitch and chat binary
Now you need to install pppd, usbmodeswitch and the chat binary the kernel is missing. You can google them or use my 3gdongle.zip file with my configs.
Run sshdroid so you can ssh to your android device (or use adb shell etc.).
Connect to your andrid device with putty.
Then run
Code:
sysrw
so you can write to your system folder.
Copy the contents of the zip file in the root folder using WinSCP.
Add the execute permission on
/system/xbin/chat
/system/xbin/usb_modeswitch
/system/bin/pppd
/system/etc/ppp/ip-up
/system/etc/ppp/ip-down
(using WinSCP or with chattr via ssh)
5) Plug the dongle to your windows machine & using Vodafone windows application disable pin authentication. (You can let it enabled but you have to modify the gprs-connect-chat i guess).
6) Disable the CD-ROM mode (I think it's not required because we are using usb_modeswitch, but i did it a long time ago and I'm too lazy to enable it back).
Under Control Panel->Phone and Modem look in the Modems tab. There should be the COM port written in the "Attached To" column.
Using putty & connection type serial connect to your modem and disable the CD-ROM mode using the command
Code:
AT^SETPORT="A1;1,2,3"
You can also check if your modem is responding with the AT command (it should write back OK).
Using te ATI command you should get the modem information back.
ex:
Code:
Manufacturer: Vodafone (Huawei)
Model: K4605
Revision: 11.113.21.00.11
IMEI: 353148040378952
+GCAP: +CGSM,+DS,+ES
OK
7) Plug the modem into your android device. You can check if the necessary moodules are loaded with lsmod:
Code:
sh-4.1# lsmod
option 13380 0 - Live 0xbf016000
usb_wwan 8789 1 option, Live 0xbf00d000
8) Check the dmesg or use lsusb to get your devices vendor and product id
dmesg>
Code:
[ 1903.631599] usb 2-1: new high speed USB device number 3 using tegra-ehci
[ 1903.689362] usb 2-1: New USB device found, idVendor=12d1, idProduct=14c1
[ 1903.689606] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 1903.689739] usb 2-1: Product: Vodafone Mobile Broadband (Huawei)
[ 1903.689970] usb 2-1: Manufacturer: Vodafone Group (Huawei)
[ 1903.695541] scsi1 : usb-storage 2-1:1.0
[ 1904.701649] scsi 1:0:0:0: CD-ROM Vodafone CD ROM (Huawei) 2.31 PQ: 0 ANSI: 2
lsusb>
Code:
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 003: ID 12d1:14c1
9) Switch usb mode using usb_modeswitch and the config file for your device. In my case it's 12d1:14c1.
Code:
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
If the switch was succsessful you should see the correct productid now (in my case 14c6):
Code:
sh-4.1# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 005: ID 12d1:14c6
10) optional - K4605 or other unrecognized devices
After the modeswitch you should see your device under /dev/ttyUSB*. But with the K4605 we don't because option.ko doesn't know our device. So we need to call
Code:
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
and our device appears.
11) check if modem is responding:
Code:
cat /dev/ttyUSB0 & echo AT > /dev/ttyUSB0
You should get an OK.
12) Set the config files. If you installed my 3gdongle.zip file you will find my config files under /system/etc/ppp .
You have to edit the gprs-connect-chat file and the peers/gprs file.
I will not go into detail about this config files. There is a lot of information about it on xda forums and google should be your best friend too .
bonus) I use this scripts to enable and disable internet via my 3G dongle using the scriptmanager app (https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en)
01_init3g.sh - Run it after plugging the 3g dongle to your android device (k4605 specific)
Code:
# My modem Vodafone K4605 is unknown to option.ko so we manually add it
# you can delete this line if your modem is recognized by option.ko
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
# switch modes with usb_modeswitch
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
02_connect via 3g.sh - Connect to the internet (you have to wait 10-20sec after using init because the modem has to initialize first)
Code:
#!/system/bin/sh
#save old route & primary dns
OLDROUTE=`/system/xbin/netstat -r | /system/xbin/grep default | /system/xbin/awk '{print $2}' | /system/xbin/head -n1`
OLDDNS=`/system/bin/getprop net.dns1`
/system/xbin/echo $OLDROUTE > /data/ppp/ppp0.route;
/system/xbin/echo $OLDDNS >> /data/ppp/ppp0.route;
# just some logging for debugging. Can be removed :)
/system/bin/log -pw -t zeroxPPPD "OldRoute: $OLDROUTE"
/system/bin/log -pw -t zeroxPPPD "OldDNS: $OLDDNS"
#connect to the internet
pppd call gprs
03_restore wlan.sh - Disconnect the 3g dongle & restore WLAN
Code:
#!/system/bin/sh
# restore the old route & primary dns (you can extend the script to add the secondary dns..
OLDROUTE=`cat /data/ppp/ppp0.route | head -n1`
OLDDNS=`cat /data/ppp/ppp0.route | tail -n1`
/system/bin/setprop "net.dns1" "$OLDDNS"
/system/xbin/route add default gw $OLDROUTE dev wlan0
# delete the settings file
/system/xbin/rm /data/ppp/ppp*.route
Click to expand...
Click to collapse
here is the link for it (http://forum.xda-developers.com/showthread.php?t=1494891&page=4)
It's also in the latest source (http://git.kernel.org/?p=linux/kern...b;hb=9334c4c16e6fa80dc55865897337b49c1753f33b)
I also found this (https://github.com/DerArtem/huaweigeneric-ril).
PLEASE DEVELOPERS TAKE A LOOK INTO IT, if possible fro the source please build a kernel patch or script
thanks to zerox981
This is my usb log. Plz help me!
PPP Widget version 1.3.3
USB_ModeSwitch log from Tue Oct 01 17:36:52 ICT 2013
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer HSPA,Incorporated
product HSPA WCDMA Technologies MSM
serial MF190SVIED010000
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.2000
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to 0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p 2000 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0x2000
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="0001,0002,0015,0016,0017,0031,0037,0052,0055,0061,0063,0064,0066,0091,0108,0117,0128,0157,0177,1402,2002,2003"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345679000000000000061b000000020000000000000000000000"
MessageContent3="55534243123456702000000080000c85010101180101010101000000000000"
NeedResponse=1
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:2000
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
USB description data (for identification)
-------------------------
Manufacturer: HSPA,Incorporated
Product: HSPA WCDMA Technologies MSM
Serial No.: MF190SVIED010000
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 1 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 2 (CSW) ...
OK, response successfully read (13 bytes).
Trying to send message 3 to endpoint 0x01 ...
OK, message successfully sent
Reading the response to message 3 (CSW) ...
Response reading got error -32
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Reading attributes ...
Waiting for device file system (5 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:0108 (HSPA,Incorporated: HSPA WCDMA Technologies MSM)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Checking for active driver path: /sys/bus/usb-serial/drivers/option1
Driver not active, try to find module "option"
Can't find module "option"
Existing path found:
No way to use driver "option"
- try falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
I have rooted KF HD 8.9 with the default amazon rom am trying to update the rom to the CM11
I am trying to follow the tutorial http://forum.xda-developers.com/showthread.php?t=2128175]
I can connect using adb devices and see my device but the following command "fastboot -i 0x1949 getvar product" or "fastboot -i 0x1949 reboot" does not work. The only thing i get is "< waiting for device >" message.
The device is rooted and i can get it to show the fastboot prompt on the KF by using adb shell su -c "reboot bootloader" commands. I have attached the device manager status when the KF gets into fastboot stage
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone suggest how do i get past this.
Update the drivers for the device with the triangle to the ones in my signature. So download drivers from my signature, extract them somewhere, right click that device, hit update drivers, and point it to where you extracted mine.
Personally I would use this tutorial for what you are trying to achieve, but the downside is if you somehow don't see the check box above the red warning text and check it off then you will have a nice red screen on reboot and if you think its hard to get fastboot working right now well wait until you have to update that driver in a 3 second time frame. Then again Linux makes it way easier because of how it loads up drivers, so that's an easy way to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Tried the driver in your link before posting this thread and it did not seem to work for me.
I am going to try the linux option.
stunts513 said:
Update the drivers for the device with the triangle to the ones in my signature. So download drivers from my signature, extract them somewhere, right click that device, hit update drivers, and point it to where you extracted mine.
Personally I would use this tutorial for what you are trying to achieve, but the downside is if you somehow don't see the check box above the red warning text and check it off then you will have a nice red screen on reboot and if you think its hard to get fastboot working right now well wait until you have to update that driver in a 3 second time frame. Then again Linux makes it way easier because of how it loads up drivers, so that's an easy way to get into fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Its also possible you have a composite device that need to be removed first, only way to know is to look at each composite USB device's vid number and see if it is 1949, if that's not the case then maybe you have a vid and pid I haven't added to my drivers. But yea go for and Ubuntu 13.10 live CD/USB, makes things really simple, you just boot it up, install fastboot from the Repo's, and run the command with device off and then plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk
I tried it with Ubuntu and it did not see to work.
adb devices was returning my device
fastboot devices was not returning anything.
Is there a specific way to install the driver on linux. I just downloaded the android sdk and unzipped it and the adb command was returning my device right off the bat.
stunts513 said:
Its also possible you have a composite device that need to be removed first, only way to know is to look at each composite USB device's vid number and see if it is 1949, if that's not the case then maybe you have a vid and pid I haven't added to my drivers. But yea go for and Ubuntu 13.10 live CD/USB, makes things really simple, you just boot it up, install fastboot from the Repo's, and run the command with device off and then plug it in.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Interesting, well Linux has the driver built in, so there's not need to install anything, did you say you had adb access in fastboot mode???
Sent from my Amazon Kindle Fire HD using Tapatalk
In Linux adb does not work if i put the device in fastboot mode using adb sudo command.
Does it have anything to do with device itself. I know it is unlocked , because i managed to get play store on it, but is there a chance it is not fully unlocked
stunts513 said:
Interesting, well Linux has the driver built in, so there's not need to install anything, did you say you had adb access in fastboot mode???
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Let's use the term rooted, unlocked has a different meaning that will never apply to the kfhd... Anyways um so your saying if you "adb reboot bootloader" and it goes into fastboot it doesn't get recognized by Ubuntu when running the command "fastboot -i 0x1949 getvar product"? By the way there's a much easier way to install the adb and fastboot command by running this in a terminal, though if your are on a live CD you might wanna run "sudo apt-get update" first before running this. In a terminal you can just run "sudo apt-get install android-tools-adb android-tools-fastboot", way smaller and you don't have to add anything to the system paths for anywhere usage.
Sent from my Amazon Kindle Fire HD using Tapatalk
Yes your statement is accurate. Any suggestions on what i can try?
stunts513 said:
Let's use the term rooted, unlocked has a different meaning that will never apply to the kfhd... Anyways um so your saying if you "adb reboot bootloader" and it goes into fastboot it doesn't get recognized by Ubuntu when running the command "fastboot -i 0x1949 getvar product"?
Click to expand...
Click to collapse
I have a full install not a live boot version, so i will try your suggestion of apt get so that it gets installed in the path.
stunts513 said:
By the way there's a much easier way to install the adb and fastboot command by running this in a terminal, though if your are on a live CD you might wanna run "sudo apt-get update" first before running this. In a terminal you can just run "sudo apt-get install android-tools-adb android-tools-fastboot", way smaller and you don't have to add anything to the system paths for anywhere usage.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
When it goes into fastboot unplug it and plug it back in, then post back the last few relevant line of your dmesg along with the results of running lsusb.
Sent from my Amazon Kindle Fire HD using Tapatalk
Looks like dmesg has some error statements after i put it to fastboot mode. Not sure what it means
[ 457.028880] usb 3-3: >device descriptor read/8, error -71
[ 457.148762] usb 3-3: >device descriptor read/8, error -71
I have attached the complete output in the attachments including a lsusb -v output
lsusb output
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 003 Device 007: ID 1949:0008 Lab126
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 003: ID 13d3:5188 IMC Networks
Bus 001 Device 004: ID 03eb:8417 Atmel Corp.
dmesg output
[ 336.727802] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 336.727815] usb 3-3: >New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 336.727820] usb 3-3: >Product: Jem-PVT-Prod-04
[ 336.727824] usb 3-3: >Manufacturer: Texas Instruments
[ 336.727827] usb 3-3: >SerialNumber: 5FA2000040002FFF
[ 336.728560] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 336.728572] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 339.209337] usb 3-3: >USB disconnect, device number 3
[ 349.330783] usb 3-3: >new high-speed USB device number 4 using xhci_hcd
[ 349.357003] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 349.357013] usb 3-3: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 349.357016] usb 3-3: >Product: Kindle
[ 349.357018] usb 3-3: >Manufacturer: Amazon
[ 349.357020] usb 3-3: >SerialNumber: B0C9100424870NEP
[ 349.357628] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 349.357639] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.548583] usb 3-3: >USB disconnect, device number 4
[ 391.913265] usb 3-3: >new high-speed USB device number 5 using xhci_hcd
[ 391.935540] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 391.935547] usb 3-3: >New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 391.935551] usb 3-3: >Product: Kindle
[ 391.935554] usb 3-3: >Manufacturer: Amazon
[ 391.935556] usb 3-3: >SerialNumber: B0C9100424870NEP
[ 391.935871] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935878] usb 3-3: >ep 0x2 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935884] usb 3-3: >ep 0x83 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 391.935890] usb 3-3: >ep 0x3 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 452.776441] usb 3-3: >USB disconnect, device number 5
[ 456.872640] usb 3-3: >new high-speed USB device number 6 using xhci_hcd
[ 457.028880] usb 3-3: >device descriptor read/8, error -71
[ 457.148762] usb 3-3: >device descriptor read/8, error -71
[ 457.364566] usb 3-3: >new high-speed USB device number 7 using xhci_hcd
[ 457.382406] usb 3-3: >New USB device found, idVendor=1949, idProduct=0008
[ 457.382415] usb 3-3: >New USB device strings: Mfr=5, Product=1, SerialNumber=2
[ 457.382421] usb 3-3: >Product: Jem-PVT-Prod-04
[ 457.382425] usb 3-3: >Manufacturer: Texas Instruments
[ 457.382429] usb 3-3: >SerialNumber: 5FA2000040002FFF
[ 457.383102] usb 3-3: >ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[ 457.383118] usb 3-3: >ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
Well that is interesting, it seems Ubuntu saw it in fastboot mode, not sure what was with the descriptor errors, those are usually bad because it can't retrieve the vendor is and such but it seems to have done that, lab126 is the kindle BTW so it showed up in lsusb as well. Its late and I don't wanna get on my laptop to check something so I'll just ask, are you plugged into a USB 2.0 or 3.0 port? Just wanna mention USB 3.0 and fastboot don't mix well.
Sent from my Amazon Kindle Fire HD using Tapatalk
It was connected to USB 2.0. BTW once in fastboot mode , adb devices also does not work.
stunts513 said:
Well that is interesting, it seems Ubuntu saw it in fastboot mode, not sure what was with the descriptor errors, those are usually bad because it can't retrieve the vendor is and such but it seems to have done that, lab126 is the kindle BTW so it showed up in lsusb as well. Its late and I don't wanna get on my laptop to check something so I'll just ask, are you plugged into a USB 2.0 or 3.0 port? Just wanna mention USB 3.0 and fastboot don't mix well.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Adb isn't supposed to work with fastboot. I don't see why fastboot isn't picking it up, as long as any fastboot command has the "-i 0x1949" parameter it should run the fastboot commands, I mean Linux is picking it up in fastboot so this is odd.
Sent from my Amazon Kindle Fire HD using Tapatalk
Found this info in another thread would this mean that i have a version of kindle on which fastboot has been disabled.
Would it make sense to try the commands to load the TWRP?
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
http://forum.xda-developers.com/showthread.php?t=1850038
*The stock bootloader has been updated by Amazon to not display anything with "fastboot devices" and you can only enter one fastboot command at a time before you have to shut it down and start it up again. I have come up with a dirty workaround to deal with it so if you have a stock bootloader and get "Device Offline", just try to select one of the options anyway. The script will hopefully get you through it.
*32bit libraries are necessary for this to work. The script will detect whether you are running 32 or 64 bit and download the 32bit libs if necessary. The problem with this is Ubuntu is no longer supporting ia32-libs and they may or may not download when needed. It's best to use a 32bit system or create a 32bit LiveUSB to avoid any problems, although I've never personally had any problems downloading them.
That article is about kf1's, you have an HD 8.9, and they never had fastboot disabled in them, only the hdx's did and it wasn't to the point where you couldn't get into it. I wouldn't mind trying to fix this remotely with something like team viewer, but even a ssh might work.
Thought I'd mention I would a posted this sooner but my kindle went nuts and i couldn't access xda for some reason.
Sent from my Amazon Kindle Fire HD using Tapatalk
Do you have suggestions on what you want me to try. I am quite well versed in software development, but this is too specific to be in my area of expertise. So if u give me some hints i might be able to figure it out
stunts513 said:
That article is about kf1's, you have an HD 8.9, and they never had fastboot disabled in them, only the hdx's did and it wasn't to the point where you couldn't get into it. I wouldn't mind trying to fix this remotely with something like team viewer, but even a ssh might work.
Thought I'd mention I would a posted this sooner but my kindle went nuts and i couldn't access xda for some reason.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
At this point I am getting low on advice. Its being seen in fastboot but yet not working with the fastboot command, I'm either going for user error or bootloader malfunction at this point but I could be wrong. If indeed thenbootloader is malfunctioning, you could reflash the bootloader from adb if you can still get adb access, it would just be a simple matter of pushing it to the sdcard, md5sum-ing it to verify integrity, then dd-ing it to the right partition, probably with bs=1 option, as I have noticed people with hard bricks that used the soldering method had to pass bs=1 or it wouldn't work. If you can still get adb access and want to attempt doing it I will post the actual commands you will want to run.
Sent from my Amazon Kindle Fire HD using Tapatalk
I finally figured got flashboot to work and managed to get CM11 on it.
I think it was a user error , not really understanding how flashboot really worked.
I feel so stupid eating up so much of your time, especially considering i am a IT person myself.
I really appreciate all your help.
stunts513 said:
At this point I am getting low on advice. Its being seen in fastboot but yet not working with the fastboot command, I'm either going for user error or bootloader malfunction at this point but I could be wrong. If indeed thenbootloader is malfunctioning, you could reflash the bootloader from adb if you can still get adb access, it would just be a simple matter of pushing it to the sdcard, md5sum-ing it to verify integrity, then dd-ing it to the right partition, probably with bs=1 option, as I have noticed people with hard bricks that used the soldering method had to pass bs=1 or it wouldn't work. If you can still get adb access and want to attempt doing it I will post the actual commands you will want to run.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
No problem, I tend to do that in other fields sometimes too. Still learning about the porting process for ROMs.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi. That is the thing. I've tried some computers, windows 7 and 10, linux,...
The phone charges OK, but does not recognizes when it is connected to a computer, does not show USB options to charge or access storage, and windows says "device malfunction" or alike.
Linux lsusb command does not list the phone.
I've tried changing cable, and drivers and adb tool are installed in computer, in all the OS's.
I've tried custom ROMs, 7.1 and 8.0, and one derived from stock (Freedom ROM), same result.
So, could I try something or is a hardware/connector fail?
kinuris said:
Hi. That is the thing. I've tried some computers, windows 7 and 10, linux,...
The phone charges OK, but does not recognizes when it is connected to a computer, does not show USB options to charge or access storage, and windows says "device malfunction" or alike.
Linux lsusb command does not list the phone.
I've tried changing cable, and drivers and adb tool are installed in computer, in all the OS's.
I've tried custom ROMs, 7.1 and 8.0, and one derived from stock (Freedom ROM), same result.
So, could I try something or is a hardware/connector fail?
Click to expand...
Click to collapse
Use FWUL (from USB stick! not in virtualbox) and do this in a terminal (small icon in the panel):
ensure the phone is NOT connected
Code:
sudo -s (enter password)
dmesg -c > /dev/null
-> Now connect the phone
lsusb
dmesg
Copy and share the whole output
.
steadfasterX said:
Use FWUL (from USB stick! not in virtualbox) and do this in a terminal (small icon in the panel):
ensure the phone is NOT connected
Code:
sudo -s (enter password)
dmesg -c > /dev/null
-> Now connect the phone
lsusb
dmesg
Copy and share the whole output
.
Click to expand...
Click to collapse
Thank you very much.
lsusb
Code:
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 003: ID 03f0:2b17 HP, Inc LaserJet 1020
Bus 002 Device 005: ID 17ef:608c Lenovo
Bus 002 Device 002: ID 17ef:608d Lenovo
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and dmesg (it does not allow me post more than 30000 characters, so I'm shorting it. If you need the first part, please tell me and I post it
Code:
[ 2.165528] ACPI: bus type USB registered
[ 2.167756] usbcore: registered new interface driver usbfs
[ 2.168742] usbcore: registered new interface driver hub
[ 2.169408] usbcore: registered new device driver usb
[ 2.172149] libata version 3.00 loaded.
[ 2.180945] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.182725] AVX2 version of gcm_enc/dec engaged.
[ 2.182725] AES CTR mode by8 optimization enabled
[ 2.185361] ehci-pci: EHCI PCI platform driver
[ 2.186911] ehci-pci 0000:00:1a.0: EHCI Host Controller
[ 2.187228] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[ 2.187241] ehci-pci 0000:00:1a.0: debug port 2
[ 2.191144] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[ 2.191189] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7c3c000
[ 2.198019] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[ 2.198214] hub 1-0:1.0: USB hub found
[ 2.198220] hub 1-0:1.0: 3 ports detected
[ 2.198399] ahci 0000:00:1f.2: version 3.0
[ 2.198624] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x5 impl SATA mode
[ 2.198626] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst
[ 2.201814] scsi host0: ahci
[ 2.202044] scsi host1: ahci
[ 2.202179] scsi host2: ahci
[ 2.202283] scsi host3: ahci
[ 2.202366] scsi host4: ahci
[ 2.202482] scsi host5: ahci
[ 2.202519] ata1: SATA max UDMA/133 abar [email protected] port 0xf7c3a100 irq 24
[ 2.202520] ata2: DUMMY
[ 2.202522] ata3: SATA max UDMA/133 abar [email protected] port 0xf7c3a200 irq 24
[ 2.202523] ata4: DUMMY
[ 2.202523] ata5: DUMMY
[ 2.202524] ata6: DUMMY
[ 2.202713] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 2.202718] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 2.203845] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810
[ 2.203856] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[ 2.204187] hub 2-0:1.0: USB hub found
[ 2.204211] hub 2-0:1.0: 14 ports detected
[ 2.206821] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 2.206825] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[ 2.206981] hub 3-0:1.0: USB hub found
[ 2.207019] hub 3-0:1.0: 6 ports detected
[ 2.207442] usb: port power management may be unreliable
[ 2.207974] ehci-pci 0000:00:1d.0: EHCI Host Controller
[ 2.207992] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 4
[ 2.208018] ehci-pci 0000:00:1d.0: debug port 2
[ 2.211925] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[ 2.212017] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7c3b000
[ 2.219050] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[ 2.219286] hub 4-0:1.0: USB hub found
[ 2.219292] hub 4-0:1.0: 3 ports detected
[ 2.222631] [drm] Memory usable by graphics device = 2048M
[ 2.222632] [drm] Replacing VGA console driver
[ 2.223805] Console: switching to colour dummy device 80x25
[ 2.230348] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.230349] [drm] Driver supports precise vblank timestamp query.
[ 2.232473] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[ 2.236805] [drm] Initialized i915 1.6.0 20170818 for 0000:00:02.0 on minor 0
[ 2.237126] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 2.307667] fbcon: inteldrmfb (fb0) is primary device
[ 2.382778] Console: switching to colour frame buffer device 180x56
[ 2.403465] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 2.510658] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 2.510739] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 2.513693] ata1.00: ATA-8: ST500DM002-1BD142, HP74, max UDMA/100
[ 2.513699] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 2.514359] ata3.00: ATAPI: hp DVD A DS8ABSH, AHS6, max UDMA/100
[ 2.515370] ata1.00: configured for UDMA/100
[ 2.515776] scsi 0:0:0:0: Direct-Access ATA ST500DM002-1BD14 HP74 PQ: 0 ANSI: 5
[ 2.521107] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 2.526921] ata3.00: configured for UDMA/100
[ 2.529136] usb 2-1: new low-speed USB device number 2 using xhci_hcd
[ 2.545131] usb 4-1: new high-speed USB device number 2 using ehci-pci
[ 2.546299] scsi 2:0:0:0: CD-ROM hp DVD A DS8ABSH AHS6 PQ: 0 ANSI: 5
[ 2.588502] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 2.588521] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.588529] sd 0:0:0:0: [sda] Write Protect is off
[ 2.588530] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.588543] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.614189] sr 2:0:0:0: [sr0] scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 2.614190] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 2.614552] sr 2:0:0:0: Attached scsi CD-ROM sr0
[ 2.620286] sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7
[ 2.621297] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.650053] hub 1-1:1.0: USB hub found
[ 2.650242] hub 1-1:1.0: 6 ports detected
[ 2.661904] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.665595] usbcore: registered new interface driver usbhid
[ 2.665596] usbhid: USB HID core driver
[ 2.667225] input: PixArt Lenovo USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/0003:17EF:608D.0001/input/input4
[ 2.667319] hid-generic 0003:17EF:608D.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt Lenovo USB Optical Mouse] on usb-0000:00:14.0-1/input0
[ 2.673685] hub 4-1:1.0: USB hub found
[ 2.673872] hub 4-1:1.0: 8 ports detected
[ 2.772985] usb 2-4: new high-speed USB device number 3 using xhci_hcd
[ 3.014050] usb 2-7: new high-speed USB device number 4 using xhci_hcd
[ 3.039015] tsc: Refined TSC clocksource calibration: 3192.590 MHz
[ 3.039034] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2e04f1e405e, max_idle_ns: 440795268354 ns
[ 3.154606] usb-storage 2-7:1.0: USB Mass Storage device detected
[ 3.155005] scsi host6: usb-storage 2-7:1.0
[ 3.155325] usbcore: registered new interface driver usb-storage
[ 3.155933] usbcore: registered new interface driver uas
[ 3.263033] usb 2-12: new low-speed USB device number 5 using xhci_hcd
[ 3.404446] input: Lenovo Lenovo Calliope USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb2/2-12/2-12:1.0/0003:17EF:608C.0002/input/input5
[ 3.456261] hid-generic 0003:17EF:608C.0002: input,hidraw1: USB HID v1.11 Keyboard [Lenovo Lenovo Calliope USB Keyboard] on usb-0000:00:14.0-12/input0
[ 3.461366] input: Lenovo Lenovo Calliope USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb2/2-12/2-12:1.1/0003:17EF:608C.0003/input/input6
[ 3.513318] hid-generic 0003:17EF:608C.0003: input,hidraw2: USB HID v1.11 Device [Lenovo Lenovo Calliope USB Keyboard] on usb-0000:00:14.0-12/input1
[ 4.047314] clocksource: Switched to clocksource tsc
[ 4.193165] scsi 6:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
[ 4.194648] sd 6:0:0:0: [sdb] 7987200 512-byte logical blocks: (4.09 GB/3.81 GiB)
[ 4.195355] sd 6:0:0:0: [sdb] Write Protect is off
[ 4.195358] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 4.196078] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4.200037] sdb: sdb1 sdb2
[ 4.202112] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 5.116456] ISO 9660 Extensions: RRIP_1991A
[ 5.126822] loop: module loaded
[ 5.236318] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 5.246252] overlayfs: fs on '/run/archiso/sfs/airootfs' does not support file handles, falling back to index=off.
[ 6.046495] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 6.064367] systemd[1]: systemd 239 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN +PCRE2 default-hierarchy=hybrid)
[ 6.076254] systemd[1]: Detected architecture x86-64.
[ 6.091996] systemd[1]: Set hostname to <fwul>.
[ 6.096128] systemd[1]: Initializing machine ID from random generator.
[ 6.337673] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 6.364894] systemd[1]: Created slice User and Session Slice.
[ 6.365502] systemd[1]: Created slice system-getty.slice.
[ 6.366708] systemd[1]: Listening on Journal Socket (/dev/log).
[ 6.375844] systemd[1]: Listening on Process Core Dump Socket.
[ 6.375977] systemd[1]: Reached target Slices.
[ 6.466051] vboxguest: loading out-of-tree module taints kernel.
[ 6.472163] vboxguest: PCI device not found, probably running on physical hardware.
[ 6.500289] vboxguest: PCI device not found, probably running on physical hardware.
[ 6.506214] systemd-journald[303]: Received request to flush runtime journal from PID 1
[ 6.952501] ACPI: Invalid active2 threshold
[ 6.953729] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[ 6.954747] thermal LNXTHERM:00: registered as thermal_zone0
[ 6.954748] ACPI: Thermal Zone [TZ00] (28 C)
[ 6.956082] thermal LNXTHERM:01: registered as thermal_zone1
[ 6.956083] ACPI: Thermal Zone [TZ01] (30 C)
[ 7.012992] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170728/utaddress-247)
[ 7.012997] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.013004] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x00000000000008FF (\GPR) (20170728/utaddress-247)
[ 7.013007] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.013007] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\GPRL) (20170728/utaddress-247)
[ 7.013009] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x00000000000008FF (\GPR) (20170728/utaddress-247)
[ 7.013012] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.013012] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000053F (\GPRL) (20170728/utaddress-247)
[ 7.013014] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x00000000000008FF (\GPR) (20170728/utaddress-247)
[ 7.013016] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 7.013016] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 7.045902] i801_smbus 0000:00:1f.3: SPD Write Disable is set
[ 7.046495] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
[ 7.076029] pps_core: LinuxPPS API ver. 1 registered
[ 7.076031] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 7.077099] PTP clock support registered
[ 7.094944] tpm_tis 00:09: 1.2 TPM (device-id 0xB, rev-id 16)
[ 7.144205] input: PC Speaker as /devices/platform/pcspkr/input/input7
[ 7.236233] tpm tpm0: A TPM error (7) occurred attempting to read a pcr value
[ 7.236813] tpm tpm0: TPM is disabled/deactivated (0x7)
[ 7.265100] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 7.265101] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 7.311416] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 7.336037] mousedev: PS/2 mouse device common for all mice
[ 7.343881] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input10
[ 7.344419] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input11
[ 7.344817] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input12
[ 7.345645] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card0/input13
[ 7.346120] input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.0/sound/card0/input14
[ 7.361993] usblp 2-4:1.0: usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17
[ 7.362024] usbcore: registered new interface driver usblp
[ 7.393297] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7.474606] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[ 7.476119] input: HP WMI hotkeys as /devices/virtual/input/input9
[ 7.491862] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer
[ 7.491864] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[ 7.491864] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 7.491865] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 7.491865] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 7.548348] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) c4:34:6b:59:14:36
[ 7.548350] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 7.548398] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[ 7.585935] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC221: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[ 7.585937] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=1 (0x17/0x0/0x0/0x0/0x0)
[ 7.585938] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 7.585939] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0
[ 7.585939] snd_hda_codec_realtek hdaudioC1D0: inputs:
[ 7.585940] snd_hda_codec_realtek hdaudioC1D0: Mic=0x1a
[ 7.585941] snd_hda_codec_realtek hdaudioC1D0: Line=0x1b
[ 7.766351] iTCO_vendor_support: vendor-support=0
[ 7.768415] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 7.768478] iTCO_wdt: Found a Lynx Point TCO device (Version=2, TCOBASE=0x0460)
[ 7.768598] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 7.804693] kvm: disabled by bios
[ 7.819232] kvm: disabled by bios
[ 7.827912] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input15
[ 7.828060] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card1/input16
[ 7.828173] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card1/input17
[ 7.828230] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card1/input18
[ 7.957599] intel_rapl: Found RAPL domain package
[ 7.957601] intel_rapl: Found RAPL domain core
[ 7.957601] intel_rapl: Found RAPL domain uncore
[ 7.957602] intel_rapl: Found RAPL domain dram
[ 7.957603] intel_rapl: RAPL package 0 domain package locked by BIOS
[ 7.957606] intel_rapl: RAPL package 0 domain dram locked by BIOS
[ 8.039287] e1000e 0000:00:19.0 eno1: renamed from eth0
[ 11.792724] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 12.010349] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 13.384537] fuse init (API version 7.26)
[ 13.553288] e1000e: eno1 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[ 13.553291] e1000e 0000:00:19.0 eno1: 10/100 speed: disabling TSO
[ 13.553328] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 160.654761] TCP: eno1: Driver has suspect GRO implementation, TCP performance may be compromised.
[ 225.740105] usb 2-8: new low-speed USB device number 6 using xhci_hcd
[ 225.855146] usb 2-8: device descriptor read/64, error -71
[ 226.074207] usb 2-8: device descriptor read/64, error -71
[ 226.297125] usb 2-8: new low-speed USB device number 7 using xhci_hcd
[ 226.412116] usb 2-8: device descriptor read/64, error -71
[ 226.635168] usb 2-8: device descriptor read/64, error -71
[ 226.743107] usb usb2-port8: attempt power cycle
[ 227.371085] usb 2-8: new low-speed USB device number 8 using xhci_hcd
[ 227.371690] usb 2-8: Device not responding to setup address.
[ 227.575669] usb 2-8: Device not responding to setup address.
[ 227.783089] usb 2-8: device not accepting address 8, error -71
[ 227.897072] usb 2-8: new low-speed USB device number 9 using xhci_hcd
[ 227.897676] usb 2-8: Device not responding to setup address.
[ 228.103714] usb 2-8: Device not responding to setup address.
[ 228.311129] usb 2-8: device not accepting address 9, error -71
[ 228.311222] usb usb2-port8: unable to enumerate USB device
[ 328.537102] usb 2-8: new low-speed USB device number 10 using xhci_hcd
[ 328.652150] usb 2-8: device descriptor read/64, error -71
[ 328.874143] usb 2-8: device descriptor read/64, error -71
[ 329.097099] usb 2-8: new low-speed USB device number 11 using xhci_hcd
[ 329.212150] usb 2-8: device descriptor read/64, error -71
[ 329.434186] usb 2-8: device descriptor read/64, error -71
[ 329.543168] usb usb2-port8: attempt power cycle
[ 330.171100] usb 2-8: new low-speed USB device number 12 using xhci_hcd
[ 330.171653] usb 2-8: Device not responding to setup address.
[ 330.375640] usb 2-8: Device not responding to setup address.
[ 330.583092] usb 2-8: device not accepting address 12, error -71
[ 330.697100] usb 2-8: new low-speed USB device number 13 using xhci_hcd
[ 330.697654] usb 2-8: Device not responding to setup address.
[ 330.903638] usb 2-8: Device not responding to setup address.
[ 331.111091] usb 2-8: device not accepting address 13, error -71
[ 331.111203] usb usb2-port8: unable to enumerate USB device
kinuris said:
Thank you very much.
lsusb
Code:
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 003: ID 03f0:2b17 HP, Inc LaserJet 1020
Bus 002 Device 005: ID 17ef:608c Lenovo
Bus 002 Device 002: ID 17ef:608d Lenovo
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and dmesg (it does not allow me post more than 30000 characters, so I'm shorting it. If you need the first part, please tell me and I post it
Click to expand...
Click to collapse
it seems you forgot to do this command:
Code:
sudo -s (enter password)
dmesg -c > /dev/null
as that cleans the dmesg output.
for the future: use a paste service like http://bpaste.net to share output bigger then a few lines!
so do it again but this time slightly different:
power off PC
connect phone in download mode to the PC
turn on PC and boot FWUL
once FWUL is booted login and open a terminal again:
Code:
sudo -s
(enter password)
dmesg -c > /dev/null
lsusb
dmesg
(should be just a few lines)
copy the complete terminal output and paste it over to http://bpaste.net (and share the link)
.
steadfasterX said:
it seems you forgot to do this command:
Code:
sudo -s (enter password)
dmesg -c > /dev/null
as that cleans the dmesg output.
for the future: use a paste service like http://bpaste.net to share output bigger then a few lines!
so do it again but this time slightly different:
power off PC
connect phone in download mode to the PC
turn on PC and boot FWUL
once FWUL is booted login and open a terminal again:
Code:
sudo -s
(enter password)
dmesg -c > /dev/null
lsusb
dmesg
(should be just a few lines)
copy the complete terminal output and paste it over to http://bpaste.net (and share the link)
.
Click to expand...
Click to collapse
Hi again! Thank you for your super fast answer!
No need for pastebin.
Code:
[fwul android]# dmesg -c > /dev/null
[fwul android]# lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 003: ID 03f0:2b17 HP, Inc LaserJet 1020
Bus 002 Device 009: ID 17ef:608c Lenovo
Bus 002 Device 002: ID 17ef:608d Lenovo
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[fwul android]# dmesg
[fwul android]#
No output from dmesg!
And, if I disconnect and connect again - phone in bootloader mode
Code:
[fwul android]# dmesg -c > /dev/null
-- connect
[fwul android]# dmesg
[ 1742.599059] usb 2-8: new full-speed USB device number 10 using xhci_hcd
[ 1742.713092] usb 2-8: device descriptor read/64, error -71
[ 1742.929101] usb 2-8: device descriptor read/64, error -71
[ 1743.145110] usb 2-8: new full-speed USB device number 11 using xhci_hcd
[ 1743.259103] usb 2-8: device descriptor read/64, error -71
[ 1743.481113] usb 2-8: device descriptor read/64, error -71
[ 1743.583168] usb usb2-port8: attempt power cycle
[ 1744.211113] usb 2-8: new full-speed USB device number 12 using xhci_hcd
[ 1744.211382] usb 2-8: Device not responding to setup address.
[ 1744.415377] usb 2-8: Device not responding to setup address.
[ 1744.623085] usb 2-8: device not accepting address 12, error -71
[ 1744.737080] usb 2-8: new full-speed USB device number 13 using xhci_hcd
[ 1744.737366] usb 2-8: Device not responding to setup address.
[ 1744.943226] usb 2-8: Device not responding to setup address.
[ 1745.151079] usb 2-8: device not accepting address 13, error -71
[ 1745.151177] usb usb2-port8: unable to enumerate USB device
kinuris said:
Hi again! Thank you for your super fast answer!
No need for pastebin.
Code:
[fwul android]# dmesg -c > /dev/null
[fwul android]# lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp.
Bus 004 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 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive
Bus 002 Device 003: ID 03f0:2b17 HP, Inc LaserJet 1020
Bus 002 Device 009: ID 17ef:608c Lenovo
Bus 002 Device 002: ID 17ef:608d Lenovo
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[fwul android]# dmesg
[fwul android]#
No output from dmesg!
And, if I disconnect and connect again - phone in bootloader mode
Code:
[fwul android]# dmesg -c > /dev/null
-- connect
[fwul android]# dmesg
[ 1742.599059] usb 2-8: new full-speed USB device number 10 using xhci_hcd
[ 1742.713092] usb 2-8: device descriptor read/64, error -71
[ 1742.929101] usb 2-8: device descriptor read/64, error -71
[ 1743.145110] usb 2-8: new full-speed USB device number 11 using xhci_hcd
[ 1743.259103] usb 2-8: device descriptor read/64, error -71
[ 1743.481113] usb 2-8: device descriptor read/64, error -71
[ 1743.583168] usb usb2-port8: attempt power cycle
[ 1744.211113] usb 2-8: new full-speed USB device number 12 using xhci_hcd
[ 1744.211382] usb 2-8: Device not responding to setup address.
[ 1744.415377] usb 2-8: Device not responding to setup address.
[ 1744.623085] usb 2-8: device not accepting address 12, error -71
[ 1744.737080] usb 2-8: new full-speed USB device number 13 using xhci_hcd
[ 1744.737366] usb 2-8: Device not responding to setup address.
[ 1744.943226] usb 2-8: Device not responding to setup address.
[ 1745.151079] usb 2-8: device not accepting address 13, error -71
[ 1745.151177] usb usb2-port8: unable to enumerate USB device
Click to expand...
Click to collapse
well try other USB ports and other USB cables but besides that it looks like the USB port has died on the phone (happened to some others already as well).
.
steadfasterX said:
well try other USB ports and other USB cables but besides that it looks like the USB port has died on the phone (happened to some others already as well).
.
Click to expand...
Click to collapse
I've tried other computer and OS's (my main OS is Manjaro at home), and W10 at workplace, and cables. So, USB died :crying:
Thank you very much for your time and help.