revive Pixel 3a - Google Pixel 3a Questions & Answers

Hi there
my wife told me today that after the lunch her 3a was dead.
The screen is black, no led is lighting, nothing. She also told me the phone was charged over night - it should be no battery issue.
So I, as a good husband, attached it to my laptop and - everything is dark.
dmesg is saying
[ +8,360574] usb 1-11: new high-speed USB device number 12 using xhci_hcd
[ +0,127284] usb 1-11: New USB device found, idVendor=05c6, idProduct=9008, bcdDevice= 0.00
[ +0,000019] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ +0,000010] usb 1-11: Product: QUSB_BULK_CID:0402_SN:37FACF8C
[ +0,000007] usb 1-11: Manufacturer: Qualcomm CDMA Technologies MSM
[ +0,003456] qcserial 1-11:1.0: Qualcomm USB modem converter detected
[ +0,000283] usb 1-11: Qualcomm USB modem converter now attached to ttyUSB0
Click to expand...
Click to collapse
adb devices and fastboot devices doesn´t see anything.
At least lsusb -v is showing something
Bus 001 Device 013: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QUSB_BULK_CID:0402_SN:37FACF8C
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 2mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 16
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Click to expand...
Click to collapse
What is this QDL mode?
Is there a possibility to revive the device?
*edit*
OK, I found https://github.com/andersson/qdl
Lets try this

Related

UrukDroid 1.5 and RNDIS dongles, ARCHOS 101 IT

Ave,
I just had sad attempt to plug dongle with RNDIS to Archos 101 (UrukDroid 1.5). The id for RNDIS "side" of dongle is idVendor=0525, idProduct=a4a2. Archos constantly connects/disconnects dongle and doesn't creates any network interface, while the other "side" of dongle (4G jfyi) lighted as connected. The dongle itself is functional - tested on Windows 7 and OS X 10.6.8 where it's recoginsed properly (RNDIS Ethernet).
Some dmesg dump
Code:
usb 2-1: new high speed USB device using musb_hdrc and address 8
usb 2-1: skipped 3 descriptors after interface
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0525, idProduct=a4a2
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: RNDIS/Ethernet Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1/vincent7-udc
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usb 2-1: adding 2-1:1.1 (config #1, interface 1)
usb 2-1:1.1: uevent
drivers/usb/core/inode.c: creating file '008'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
musb_stage2_irq 801: unhandled DISCONNECT transition (a_wait_bcon)
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 8
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
usb 2-1:1.0: uevent
usb 2-1: unregistering interface 2-1:1.1
usb 2-1:1.1: uevent
usb 2-1: uevent
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new high speed USB device using musb_hdrc and address 9
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0525, idProduct=a4a5
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: File-backed Storage Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1 with vincent7-udc
usb 2-1: SerialNumber: 3238204E6F76
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usb-storage 2-1:1.0: usb_probe_interface
usb-storage 2-1:1.0: usb_probe_interface - got id
devdb: devpath usb-musb_hdrc-1 not found
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 9
usb-storage: waiting for device to settle before scanning
drivers/usb/core/inode.c: creating file '009'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
scsi 3:0:0:0: Direct-Access Linux File-Stor Gadget 0300 PQ: 0 ANSI: 2
sd 3:0:0:0: [sda] 4096 512-byte hardware sectors: (2.09 MB/2.00 MiB)
sd 3:0:0:0: [sda] Write Protect is on
sd 3:0:0:0: [sda] Mode Sense: 0f 00 80 00
sd 3:0:0:0: [sda] Assuming drive cache: write through
sd 3:0:0:0: [sda] 4096 512-byte hardware sectors: (2.09 MB/2.00 MiB)
sd 3:0:0:0: [sda] Write Protect is on
sd 3:0:0:0: [sda] Mode Sense: 0f 00 80 00
sd 3:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 3:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
Configure McBSP for 1 phase
Configure McBSP TX FIFO threshold to 1260
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 9
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
usb 2-1:1.0: uevent
usb 2-1: uevent
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new high speed USB device using musb_hdrc and address 10
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0525, idProduct=a4a5
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: File-backed Storage Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1 with vincent7-udc
usb 2-1: SerialNumber: 3238204E6F76
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usb-storage 2-1:1.0: usb_probe_interface
usb-storage 2-1:1.0: usb_probe_interface - got id
devdb: devpath usb-musb_hdrc-1 not found
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 10
usb-storage: waiting for device to settle before scanning
drivers/usb/core/inode.c: creating file '010'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
FAT: Directory bread(block 32) failed
...
FAT: Directory bread(block 63) failed
scsi 3:0:0:0: rejecting I/O to dead device
musb_stage2_irq 801: unhandled DISCONNECT transition (a_wait_bcon)
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 10
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
usb 2-1:1.0: uevent
usb 2-1: uevent
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new high speed USB device using musb_hdrc and address 11
usb 2-1: skipped 4 descriptors after interface
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=1076, idProduct=7708
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=10
usb 2-1: Product: RNDIS/Ethernet Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1/vincent7-udc
usb 2-1: SerialNumber: 00000001
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #2 chosen from 1 choice
usb 2-1: adding 2-1:2.0 (config #2, interface 0)
usb 2-1:2.0: uevent
usb 2-1: adding 2-1:2.1 (config #2, interface 1)
usb 2-1:2.1: uevent
drivers/usb/core/inode.c: creating file '011'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
Configure McBSP for 1 phase
Configure McBSP TX FIFO threshold to 1260
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 11
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:2.0
usb 2-1:2.0: uevent
usb 2-1: unregistering interface 2-1:2.1
usb 2-1:2.1: uevent
usb 2-1: uevent
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new high speed USB device using musb_hdrc and address 12
usb 2-1: skipped 3 descriptors after interface
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0525, idProduct=a4a2
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-1: Product: RNDIS/Ethernet Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1/vincent7-udc
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usb 2-1: adding 2-1:1.1 (config #1, interface 1)
usb 2-1:1.1: uevent
drivers/usb/core/inode.c: creating file '012'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
musb_stage2_irq 801: unhandled DISCONNECT transition (a_wait_bcon)
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s
usb 2-1: USB disconnect, address 12
usb 2-1: unregistering device
usb 2-1: usb_disable_device nuking all URBs
usb 2-1: unregistering interface 2-1:1.0
usb 2-1:1.0: uevent
usb 2-1: unregistering interface 2-1:1.1
usb 2-1:1.1: uevent
usb 2-1: uevent
hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101
usb 2-1: new high speed USB device using musb_hdrc and address 13
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0525, idProduct=a4a5
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: File-backed Storage Gadget
usb 2-1: Manufacturer: Linux 2.6.23-uc1 with vincent7-udc
usb 2-1: SerialNumber: 3238204E6F76
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usb-storage 2-1:1.0: usb_probe_interface
usb-storage 2-1:1.0: usb_probe_interface - got id
devdb: devpath usb-musb_hdrc-1 not found
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 13
usb-storage: waiting for device to settle before scanning
drivers/usb/core/inode.c: creating file '013'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000503
scsi 5:0:0:0: Direct-Access Linux File-Stor Gadget 0300 PQ: 0 ANSI: 2
sd 5:0:0:0: [sda] 4096 512-byte hardware sectors: (2.09 MB/2.00 MiB)
sd 5:0:0:0: [sda] Write Protect is on
sd 5:0:0:0: [sda] Mode Sense: 0f 00 80 00
sd 5:0:0:0: [sda] Assuming drive cache: write through
sd 5:0:0:0: [sda] 4096 512-byte hardware sectors: (2.09 MB/2.00 MiB)
sd 5:0:0:0: [sda] Write Protect is on
sd 5:0:0:0: [sda] Mode Sense: 0f 00 80 00
sd 5:0:0:0: [sda] Assuming drive cache: write through sda: sda1
sd 5:0:0:0: [sda] Attached SCSI removable disk
usb-storage: device scan complete
Interesting thing - UrukDroid reports some "File-backed Storage Gadget" and even mounts is for a short while than disconnects anyway. But on Win7 and OS X no storage mounted.

[Q] GTP31xx charging issues

(Samsung GT-P3110 Galaxy Tab 2 7.0")
Recently the tab stopped charging while plugged to AC and in use...
Ok, it's not losing power as fast as when unplugged, but almost!
I have to turn it off and AC charge for hours and hours as the phone seem to think that it's connected to a PC all of a sudden!
Wasn't an issue up until last week then for no apparent reason it says "not charging" in Battery..
After a lot of reading around and confirming that it was not the charger or cable i dug deeper and it seems that USB charging is turned of by default on the Tab 2's except all custom kernels have it turned on and now that's always on!
Since the tab wont change charger state from USB to AC then all I'm getting is a slow trickle charge at the same slow pace, and it don't whether I am plugged in to the AC or into the PC!
So i figured hey, it's just a terminal command to force it to switch and that's when i realized that, no it's not that easy!
As USB charge is not only the default setting in custom kernels, its the ONLY option available!
The ability to have the tab swiftly reach a full charge while in use seems to currently be impossible with custom kernels it seems!
Is there a work around, or have everyone been to busy implementing USB charging to remember that sometimes you don't want to spend 8+ hours with tab turned off to get a full charge?
Below is a logcat from connecting and disconnecting charger cable to my GTP3110 WHILE connected to an AC adapter!
Code:
Android Tuner (logcat)
======================
V/ 96.627105 c1 17 usb ta_nconnected_irq : VBUS ON
V/ 96.627899 c1 17 [BAT_MANAGER] Charger Connected
V/ 96.627960 c1 58 musb-hdrc musb-hdrc: USB/TA Connect
V/ 97.256317 c1 1662 check_charger_type : Charger type is [USB], adc=594
V/ 97.256317 c1 1662 charger_detect_work: cable flag : 1, cable_type : 1
V/ 97.256347 c1 1662 smb136-charger 5-004d: smb136_set_charging_state: set charger current USB & Default
V/ 97.262725 c1 1662 cable detect:USB attach, current device = 0x0080
V/ 97.262756 c1 1662 espresso_con_usb_charger_attached, USB_EVENT_VBUS
V/ 97.262756 c1 1662 otg: otgwl_hold
V/ 97.262847 c0 58 musb-hdrc musb-hdrc: VBUS Connect
V/ 97.262908 c0 58 musb-omap2430 musb-omap2430: runtime resume
V/ 97.263061 c0 58 omap4430_phy_set_clk: clock (0 --> 1)
V/ 97.504699 c0 58 omap4430_phy_power : clock 1, power ON
W/ 103.476745 c0 15 smb136-charger 5-004d: smb136_i2c_read: err -6
W/ 103.476806 c0 15 smb136-charger 5-004d: smb136_read_status : I2C read fail addr: 0x35
V/ 103.535827 c0 15 smb136-charger 5-004d: addr : 0x35, data : 0x40, addr : 0x36, data : 0x31
V/ 103.806243 c1 17 usb ta_nconnected_irq : VBUS OFF
V/ 103.806793 c1 17 otg: otgwl_temporary_hold
V/ 103.806793 c0 78 musb-hdrc musb-hdrc: VBUS Disconnect
V/ 103.806793 c1 17 [BAT_MANAGER] Charger Disconnect
V/ 103.806823 c0 78 omap4430_phy is : ON
V/ 103.806854 c0 78 omap4430_phy_power : clock 1, power OFF
V/ 103.806854 c1 1662 charger_detect_work: cable flag : 0, cable_type : 0
V/ 103.806854 c1 1662 smb136-charger 5-004d: smb136_set_charging_state: Set discharging default
V/ 103.806884 c0 78 musb-hdrc musb-hdrc: ID float
V/ 103.806884 c0 605 android_work: did not send uevent (0 0 (null))
V/ 103.806915 c0 605 otg espresso_otg_work(920)
current device 0080
V/ 103.806915 c0 605 otg current device is not USB Host.
V/ 103.812805 c1 1662 cable detect:USB detach, current device = 0x0000
V/ 104.002899 c0 658 musb-omap2430 musb-omap2430: runtime suspend
V/ 104.002899 c0 658 omap4430_phy_set_clk: clock (1 --> 0)
I use cyanogenmod, and I'm fairly sure that my tablet charges faster on ac than when plugged into my PC. Have you tried a different kernel/rom?
Sent from my Galaxy S4
What kernel are you on, been trying with 5-6 different ones and they all display that bug that they are incapable in detecting if you are really on AC or USB...
It IS a kernel issue I am 100% sure of that since the Tab has USB charging turned off by default exactly to avoid this issue...

[Q] External Wi-Fi USB adapter

Hello, guys!
I got Nexus 5 running vanilla AOSP Android 4.4.3 compiled by myself. It works like a charm. I would like to use external Wi-Fi USB adapter with my Nexus 5. I've tried to use AWUS036NHA (with Atheros AR92721 chip) and two other models from different vendors. Every time I get the same error.
So, what have I done? I've rebuilt kernel to add support for my devices (in usual Linux way) and added firmwares they need to /vendor/firmware. When I plug AWUS036NHA into my phone I get the following (dmesg):
Code:
<6>[ 1587.856305] usb 1-1: new high-speed USB device number 2 using xhci-hcd
<6>[ 1587.887070] usb 1-1: New USB device found, idVendor=0cf3, idProduct=9271
<6>[ 1587.887129] usb 1-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[ 1587.887221] usb 1-1: Product: UB91C
<6>[ 1587.887273] usb 1-1: Manufacturer: ATHEROS
<6>[ 1587.887365] usb 1-1: SerialNumber: 12345
<4>[ 1587.887857] usb 1-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888693] usb 1-1: ep 0x82 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.888968] usb 1-1: ep 0x5 - rounding interval to 32768 microframes, ep desc says 0 microframes
<4>[ 1587.889115] usb 1-1: ep 0x6 - rounding interval to 32768 microframes, ep desc says 0 microframes
<6>[ 1587.890044] usb 1-1: ath9k_htc: Firmware htc_9271.fw requested
<6>[ 1588.180755] usb 1-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
<6>[ 1588.416902] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
<6>[ 1588.644279] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.3
<7>[ 1588.644345] ath: EEPROM regdomain: 0x833a
<7>[ 1588.644351] ath: EEPROM indicates we should expect a country code
<7>[ 1588.644360] ath: doing EEPROM country->regdmn map search
<7>[ 1588.644367] ath: country maps to regdmn code: 0x37
<7>[ 1588.644374] ath: Country alpha2 being used: GB
<7>[ 1588.644379] ath: Regpair used: 0x37
<6>[ 1588.648677] ieee80211 phy3: Atheros AR9271 Rev:1
<7>[ 1588.650804] Registered led device: ath9k_htc-phy3
It seems to me that everything here is ok. But when I try to switch on the adapter (ifconfig wlan1 up) I get an error (dmesg):
Code:
ADDRCONF(NETDEV_UP): wlan1: link is not ready
By the way, "ifconfig" command shows no error, but certainly it doesn't swith my device on.
So, I got the same error with 3 different adapters. I got no idea about possible ways of solving this problem.
Please, share your ideas, I'm really stuck Looking forward for your help. And thanks in advance!

[Q] Phone wont start, LED stay green

Hi guys, some days ago i played with a ubuntu port and was at TWRP. The message (no OS installed) came up and i clicked reboot / power off (iam not sure).
Since that i not get the phone booted. I cant go to fastboot or recovery, too.
When i connect the usb cable to pc or wall charger the led turn on/off green.
i also tried making my own fastboot cable when i connect it the led stay green. but i cant get it up.
Someone had an idea what i can try?
thanks in advance
Did you try holding power+vol down? Try holding that for a few seconds, then hold power and see if it turns on at all.
I think power + cam would give you the menu options as well (fastboot, recovery, etc), see if that works.
I tryed all diffrent combinations. it wont come up :/
arrrghhh said:
Did you try holding power+vol down? Try holding that for a few seconds, then hold power and see if it turns on at all.
I think power + cam would give you the menu options as well (fastboot, recovery, etc), see if that works.
Click to expand...
Click to collapse
Power plus volume up and down will give you the menu options for fastboot, recovery, etc...
Try to get into fastboot and rsdlite back to stock if you can't boot into recovery. A bit tedious, but as long as you can get rsdlite to recognize the phone you can always start over
i know this menu but it wont come up. i tryed all this combinations.
huhu1312 said:
i know this menu but it wont come up. i tryed all this combinations.
Click to expand...
Click to collapse
You've tried holding these key combos for 30 sec right?
Maybe 10 sec is more realistic, but still - you need to hold these buttons...
Does the screen even power on? Perhaps the backlight is not coming on...?
i already tryed it for 2 minutes but nothing happend no backlight at all.
but i get a message at windows looking for driver qhsusb_dload.
the led stay green for 30sec. 1sec pause 30sec green. 1sec pause....
if i try a combination to start the phone the led goes on and off every sec
huhu1312 said:
i already tryed it for 2 minutes but nothing happend no backlight at all.
but i get a message at windows looking for driver qhsusb_dload.
the led stay green for 30sec. 1sec pause 30sec green. 1sec pause....
if i try a combination to start the phone the led goes on and off every sec
Click to expand...
Click to collapse
IIRC, qhsusb_dload is qualcomm emergency download mode. On linux if you execute "lsusb" it should recognize something like "...HS-USB QDLoader..."
Usually indicates a bigger problem which could be resolved with chipset (msm8960 in this particular case) specific eMMC flash programmer files (.mbn) (or device specific, not sure if OEMs have a possiblity to alter those). You would need the correct boot images as well. Perhaps with the use of QPST.
There was some article somewhere about unbricking qualcomm devices by dumping full eMMC partition from a working and clean device (full reset, internal storage included) and flashing it with some partitioning tool by doing raw copy. Seems a bit odd but I have no experience with this.
Usually, the PBL (primary bootloader) should store error information which would tell you why it errored, if only there would be an easy way to extract that information from device's memory.
Depending on what you did to the device, which ubuntu image have you tried and what it did, there is a chance that the process messed up you bootloaders (SBL - second stage bootloader).
it get indentified as Qualcomm, Inc on my Linux.
i typed lsusb two times. the second when the phone was unpluged.
huhu1312 said:
it get indentified as Qualcomm, Inc on my Linux.
i typed lsusb two times. the second when the phone was unpluged.
Click to expand...
Click to collapse
Don't recognize the product (f006). Please try
Code:
lsusb -v -d 05c6:f006
Bus 002 Device 049: ID 05c6:f006 Qualcomm, Inc.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0xf006
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 2
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 2
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 34
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0001 1x 1 bytes
bInterval 16
Device Status: 0xa8b0
(Bus Powered)
i bought a new with sim mod.
but would a battery change solve the problem maybe?
Edit: i not get it out (not wanne destroy more). is there glue between the akku and the board?
i watched a video the guy removed the battery like there is nothing. iam not sure now if the guy who made the sim mod maybe put there something.
is it dangerous to try removing the glue with a cutter?
i read in some threads that the green led is a info for empty battery.
so i tryed to start the phone with a full battery.
when the full battery is in the phone the green led not come up. but i not get the phone started. (tryed all combinations)
after removing the battery again the green led is back. also if there is no battery.

usb tether using Linux PC fails after Android 8.1 update on OnePlus 5

I updated a OnePlus 5 from Android 8.0 to Android 8.1 and lost the ability to USB tether. Hotspot works fine. I've verified that some other users have this problem on the OnePlus subreddit. I'm on Opensuse 42.3.
Linux 4.4.126-48-default #1 SMP Sat Apr 7 05:22:50 UTC 2018 (f24992c) x86_64 x86_64 x86_64 GNU/Linux
This link indicates a "fix" similar to one on a Lineage forum. It doesn't solve the problem, but figured I would put it here to prevent similar posts from showing up in this thread.
https://forums.oneplus.com/threads/hotspot-not-working.769592/
At least this fix didn't break anything.
There are suggestions regarding changing the APN, but I no joy.
Using lsusb, it is clear that the phone is seen by the PC. However the phone doesn't show up when I run ifconfig.
This is the lsusb verbose output when usb tether is selected.
Code:
lsusb -s8:10 -v
Bus 008 Device 010: ID 2a70:f00e
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a70
idProduct 0xf00e
bcdDevice 4.04
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 75
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 239 Miscellaneous Device
bFunctionSubClass 4
bFunctionProtocol 1
iFunction 7
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 239 Miscellaneous Device
bInterfaceSubClass 4
bInterfaceProtocol 1
iInterface 5
** UNRECOGNIZED: 05 24 00 10 01
** UNRECOGNIZED: 05 24 01 00 01
** UNRECOGNIZED: 04 24 02 00
** UNRECOGNIZED: 05 24 06 00 01
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0f EP 15 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
For completelness, this is the lsusb verbose output when (edit) tether is NOT selected.
Code:
[email protected]:~> lsusb -s8:13 -v
Bus 008 Device 013: ID 2a70:f003
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2a70
idProduct 0xf003
bcdDevice 4.04
iManufacturer 1 OnePlus
iProduct 2 OnePlus
iSerial 3 (redacted)
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 62
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4 mtp
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 8 Mass Storage
bInterfaceSubClass 6 SCSI
bInterfaceProtocol 80 Bulk-Only
iInterface 6 Mass Storage
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
gariac said:
I updated a OnePlus 5 from Android 8.0 to Android 8.1 and lost the ability to USB tether. Hotspot works fine. I've verified that some other users have this problem on the OnePlus subreddit. I'm on Opensuse 42.3...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3624656
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Actually this seems to be a generic 8.0 to 8.1 problem, based on my searches. Nexus/Pixel for example. Even Lineage. It even showed up in beta. But I will also post on the specific One Plus forum.

Categories

Resources