[Q] Phone wont start, LED stay green - Motorola Photon Q 4G LTE

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.

Related

Fun with resistors (home/car dock mode + more)

We've already established that a resistor on the micro USB port can be used to force the Galaxy S into download mode, but the USB switching chip used on the phone has a lot of other capabilities that are triggered by different resistors between pin 4 and 5 of the plug.
Update 6 March 2011: Confirmed modes so far:
Desk Dock: 365K (also works with 1K)
Car Dock: 619K
In these modes audio output can be switched to pins D- and D+ of the USB port (D- is left) but this is not done by default, see this thread.
Serial port/UART: RID_FM_BOOT_OFF_UART (523K)
Read the rest of this thread for more details on using this port.
Other resistor values that also enable the serial port:
RID_AUD_DEV_TY_2 (80.07K): Doesn't switch the phone on, but produces bootlog output on the serial port when you switch it on manually. The bootlog output only starts partway through the second bootloader, rather than from the start of the primary bootloader.
UART_CABLE (150K): Same as RID_AUD_DEV_TY_2
Download mode: 301K (this thread).
Here is a list of all the resistor values, from fsa9480_i2c.h in the open source code for JPM. The resistor goes from pin 4 to pin 5 of the micro USB plug (full details on how to wire this up are in this thread). When you connect the plug with the resistor (in Froyo) you should see some messages from the fsa9480 driver in the kernel log, which you can view with the "dmesg" command.
Code:
RID_USB_OTG_MODE, /* 0 0 0 0 0 GND USB OTG Mode */
RID_AUD_SEND_END_BTN, /* 0 0 0 0 1 2K Audio Send_End Button*/
RID_AUD_REMOTE_S1_BTN, /* 0 0 0 1 0 2.604K Audio Remote S1 Button */
RID_AUD_REMOTE_S2_BTN, /* 0 0 0 1 1 3.208K Audio Remote S2 Button */
RID_AUD_REMOTE_S3_BTN, /* 0 0 1 0 0 4.014K Audio Remote S3 Button */
RID_AUD_REMOTE_S4_BTN, /* 0 0 1 0 1 4.82K Audio Remote S4 Button */
RID_AUD_REMOTE_S5_BTN, /* 0 0 1 1 0 6.03K Audio Remote S5 Button */
RID_AUD_REMOTE_S6_BTN, /* 0 0 1 1 1 8.03K Audio Remote S6 Button */
RID_AUD_REMOTE_S7_BTN, /* 0 1 0 0 0 10.03K Audio Remote S7 Button */
RID_AUD_REMOTE_S8_BTN, /* 0 1 0 0 1 12.03K Audio Remote S8 Button */
RID_AUD_REMOTE_S9_BTN, /* 0 1 0 1 0 14.46K Audio Remote S9 Button */
RID_AUD_REMOTE_S10_BTN, /* 0 1 0 1 1 17.26K Audio Remote S10 Button */
RID_AUD_REMOTE_S11_BTN, /* 0 1 1 0 0 20.5K Audio Remote S11 Button */
RID_AUD_REMOTE_S12_BTN, /* 0 1 1 0 1 24.07K Audio Remote S12 Button */
RID_RESERVED_1, /* 0 1 1 1 0 28.7K Reserved Accessory #1 */
RID_RESERVED_2, /* 0 1 1 1 1 34K Reserved Accessory #2 */
RID_RESERVED_3, /* 1 0 0 0 0 40.2K Reserved Accessory #3 */
RID_RESERVED_4, /* 1 0 0 0 1 49.9K Reserved Accessory #4 */
RID_RESERVED_5, /* 1 0 0 1 0 64.9K Reserved Accessory #5 */
RID_AUD_DEV_TY_2, /* 1 0 0 1 1 80.07K Audio Device Type 2 */
RID_PHONE_PWD_DEV, /* 1 0 1 0 0 102K Phone Powered Device */
RID_TTY_CONVERTER, /* 1 0 1 0 1 121K TTY Converter */
RID_UART_CABLE, /* 1 0 1 1 0 150K UART Cable */
RID_CEA936A_TY_1, /* 1 0 1 1 1 200K CEA936A Type-1 Charger(1) */
RID_FM_BOOT_OFF_USB, /* 1 1 0 0 0 255K Factory Mode Boot OFF-USB */
RID_FM_BOOT_ON_USB, /* 1 1 0 0 1 301K Factory Mode Boot ON-USB */
RID_AUD_VDO_CABLE, /* 1 1 0 1 0 365K Audio/Video Cable */
RID_CEA936A_TY_2, /* 1 1 0 1 1 442K CEA936A Type-2 Charger(1) */
RID_FM_BOOT_OFF_UART, /* 1 1 1 0 0 523K Factory Mode Boot OFF-UART */
RID_FM_BOOT_ON_UART, /* 1 1 1 0 1 619K Factory Mode Boot ON-UART */
RID_AUD_DEV_TY_1_REMOTE, /* 1 1 1 1 0 1000.07K Audio Device Type 1 with Remote(1) */
RID_AUD_DEV_TY_1_SEND = RID_AUD_DEV_TY_1_REMOTE , /* 1 1 1 1 0 1002K Audio Device Type 1 / Only Send-End(2) */
RID_USB_MODE, /* 1 1 1 1 1 Open USB Mode, Dedicated Charger or Accessory Detach */
Great stuff. Thanks man.
I wonder, what is really implemented in I9000.
For example, would it be possible, to make a remote controller for music (something like HTC RC-E100 - i've had it for my Raphael and Hero, and it was great).
Well, when i find some time, i'll try to experiment a bit with that.
Good job.
Makes you wonder why Samsung still hasn't released that damn dock yet.
What about "USB OTG Mode"? : o
How did you get into the Home Dock mode?
Helvio88 said:
How did you get into the Home Dock mode?
Click to expand...
Click to collapse
Both a 1k and a 330R resistor triggered Home Dock mode for me, I see they're not on the list either.
19arek93 said:
What about "USB OTG Mode"? : o
Click to expand...
Click to collapse
USB "On The Go" basically lets you connect two USB devices together with no PC in between and have them talk, assuming both devices support it.
For example maybe you could connect your SGS to a digital camera and copy photos off it. Or connect it to an MP3 player and copy songs.
http://en.wikipedia.org/wiki/USB_On-The-Go
snapper.fishes said:
Good job.
Makes you wonder why Samsung still hasn't released that damn dock yet.
Click to expand...
Click to collapse
They did, but only for America for now (at least it's listed in accessories on Samsung's US website).
TheBeano said:
Both a 1k and a 330R resistor triggered Home Dock mode for me, I see they're not on the list either.
Click to expand...
Click to collapse
Well, 1K didn't work for me. I'll have to find 330R (it won't be easy though, cause i have a lot of mess in tools and electronic parts, after moving to another apartement ).
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
szczeslaw said:
Well, 1K didn't work for me. I'll have to find 330R (it won't be easy though, cause i have a lot of mess in tools and electronic parts, after moving to another apartement ).
Click to expand...
Click to collapse
Check in the dmesg log for something like this:
Code:
<4>[15461.339356] [FSA9480] FSA9480_ReadIntRegister
<4>[15461.389352] [otg_clock_enable] clk_enable(otg_clock) OK.
<4>[15461.402600] [FSA9480] FSA9480_ProcessDevice (dev1 : 0x0, dev2 : 0x40)
<4>[15461.402707] AudioVideo
<4>[15461.402769] FSA9480_enable_spk
<6>[15461.402842] set_dock_state : 0X1
<4>[15461.423626] FSA9480_Enable_SPK --- enable
In fsa9480_i2c.c it is going through the branch where the home dock is plugged in, but the device detected is FSA9480_DEV_TY2_AV, which should be 80K, not 1K? So, more testing needed I think.
Also I have Alarm Clock PlusV2 installed which is the app that was triggered by this action. I did try installing the Samsung Desk Home app but it doesn't work on Froyo.
tonymy01 said:
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
Click to expand...
Click to collapse
No this is for Home Dock mode.
tonymy01 said:
It is 301K, not 330ohms(=330R) +1K. ...for the download mode I presume you are talking about?
Click to expand...
Click to collapse
Well, i know a little bit about electronics (even made some devices, like power amps, devices based on microcontrollers etc.), so i know what 330R and 301K means
I already got download mode working.
And right now i got home dock working to, with 1K resistor. I just didn't know, that one needs an additional app for it to work (i thought it's a system app).
Yeah, sorry for the mix up,i am subscribed to both of the threads related to this recent discovery, and mixed them up. I am certainly interested in triggering particular modes, eg entering car to put phone bluetooth on and screen on dim always, and perhaps a basic home page for gps nav etc, and having an alarm clock mode that maybe turns off data etc. the sky is really the limit here, I can't believe samsumg isn't taking advantage of these features!
Question: has anybody ever actually SEEN a chip inside the I9000 labeled "FSA9480", or is it possible that the "FSA9480" is actually just IP licensed by Samsung and incorporated directly into one of their ASICs?
I ask, because I have an Epic4G. I've scrutinized the various publicized teardown photos of its board, and I have yet to find anything that looks like it might be this chip (which would almost certainly be either MLF or microBGA, 3mm x 4mm or larger, and located somewhere between the main processor and the USB port).
By the same token, does a readily-available (though not necessarily "public", if you know what I mean) datasheet for the Hummingbird and its support chips exist somewhere that documents things like how many UARTs it has, which pins they're connected to, how they're configured (baudrate, parity, mode, stopbits, input & out put registers, interrupts, etc)? As far as I can tell, Android itself has no concept of a UART, and everything in the (official Samsung) kernel that's UART-related was omitted, so there's no documentation in there.
I'm personally psyched about the existence of a UART on this phone, because it opens the door for external peripherals that are a half step above "homebrew" -- things like game controllers, folding keyboards, etc. Stuff you COULD sort of implement via bluetooth (if we ever get a kernel that knows how to do HID), but would literally cost half as much and get twice the battery life if you could skip the bluetooth and just connect via a pair of wires instead.
bitbang3r said:
I ask, because I have an Epic4G. I've scrutinized the various publicized teardown photos of its board, and I have yet to find anything that looks like it might be this chip (which would almost certainly be either MLF or microBGA, 3mm x 4mm or larger, and located somewhere between the main processor and the USB port).
Click to expand...
Click to collapse
It's a 3x4mm UMLP, I haven't seen it described online as anything other than a discrete chip so it probably is on the board somewhere.
By the same token, does a readily-available (though not necessarily "public", if you know what I mean) datasheet for the Hummingbird and its support chips exist somewhere that documents things like how many UARTs it has, which pins they're connected to, how they're configured (baudrate, parity, mode, stopbits, input & out put registers, interrupts, etc)?
Click to expand...
Click to collapse
Yes, google S5PC110_EVT1_UM10 .
As far as I can tell, Android itself has no concept of a UART, and everything in the (official Samsung) kernel that's UART-related was omitted, so there's no documentation in there.
Click to expand...
Click to collapse
There is some UART code e.g. arch/arm/plat-s5pc1xx/dev-uart.c but it may be just for Bluetooth. There are a lot of /dev/ttySn ports, not sure what they do yet.
I'm personally psyched about the existence of a UART on this phone, because it opens the door for external peripherals that are a half step above "homebrew" -- things like game controllers, folding keyboards, etc. Stuff you COULD sort of implement via bluetooth (if we ever get a kernel that knows how to do HID), but would literally cost half as much and get twice the battery life if you could skip the bluetooth and just connect via a pair of wires instead.
Click to expand...
Click to collapse
The Froyo kernel does HID via Bluetooth OK, except for the Wii controller which is a not-very-conforming Bluetooth device. If the Galaxy supports USB OTG, and there is at least some detection and setup code for that, it would probably be easier to use that for wired peripherals.
does anybody know what "Factory Mode Boot OFF-USB" does?
The FSA9480 on Aries platform phones does not have any "clear text" etched on it.
It is located under the RF shield (same side with the baseband chip).
The chip is so tiny that it is necessary to have a scope to see the text printed on it. I found no hits with the code printed on the chip (cannot remember what was it).
The component location on Aries platform phones is U301 (schematics).
Richthofen said:
The component location on Aries platform phones is U301 (schematics).
Click to expand...
Click to collapse
Richthofen, does this mean you have access to the schematics? If so what is connected to pins 6 and 7 (TxD and RxD) of the FSA9480, and also pins 1-3 (Audio + Mic)? Thanks.
The schematics do not specify the pin numbers, but atleast video and mic of FSA9480 are left NC.
Thanks! So CP_D+/- are USB from the Call Processor, and AP_D+/- are USB from the Application Processor, and the IF_TXD/RXD are switched to UARTs on either the call processor or the app processor by another chip, is that correct? I'm looking at the GT-S8500 service manual which uses the same signal names.
Do you have the big block diagram for the I9000 please, that would be really useful? I would especially like to know where the BOOT_MODE and JIG signals go, and which UART on the CPU the IF_TXD/RXD gets switched to, and what does the switching. Also where VPS_L and VPS_R are coming from. Ta.

[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] Tab seems to be dead

Hi there,
another thread about a dead tab.
My first question is about warranty. At the beginning I rooted my tab, this happend round 1,5 years ago. Since 2 days my tab seems to be dead and I didn't found a solution yet. There's no backlight, no sound by example when the charger is plugged (charger is working well), no reaction to any push button usage eg. ON + VOL- at the same time. I suppose the there is something with the hardware because the last few month I detected slightly flickering of the backlight.
When I send it to Samsungs repair center or similar I assume that the tab may not be rooted, right? If so, is there a chance to unroot it in this state?
Odin didn't detected the tab so I've tried a USB-tool (USB tree view) whats happening. I've deleted some entries, see below.
Remarable entries are
- string descriptors are not available because device is in low power state
- MaxPower : 0x32 (100 mA)
Max power should be higer I suppose and low power could be right when the battery can't be loaded due to loose connections or whatever.
Any hints regarding warranty, unrooting or fault issue would be fine.
- YYVYVVY
Connection Status : Device is connected
Capabilities : EjectSupported, UniqueID, SilentInstall, RawDeviceOK
Problem Code : 7340032 (CM_PROB_0x700000)
Power State : D6226037 (supported: D1, wake from D0, wake from D1)
---------------- Connection Information ---------------
Device Bus Speed : 0x02 (High-Speed)
------------------ Device Descriptor ------------------
idVendor : 0x0451 (Texas Instruments)
idProduct : 0xD00F
bcdDevice : 0x00
iManufacturer : 0x21
*!* string descriptors are not available because device is in low power state
iProduct : 0x25
*!* string descriptors are not available because device is in low power state
iSerialNumber : 0x00
MaxPower : 0x32 (100 mA)

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.

revive Pixel 3a

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

Categories

Resources