Hi, on android 6.0, plug tablet into pc, on tablet screen usual options apply ( MTP, charge olny etc), now, on android 6.1, no opions show on tablet, pc makes a ding noise to acknowledge tablet is conected, but its not showing in file explorer, and my tablet only gives me this message now "usb : use dedicated charger t charge tablet". ive clicked connection options, nothing in there seems to enable file transfer, what the hell has happened between 6.0 and 6.1 to stop this simple feature from working. I've tried multiple usb cables too, nothing changes, and there have been zero changes to my pc. Anyone else seen this last few days since update...
thanks
That just means it's in charging mode. You would have to unlock your tablet and click on the notification and switch to MTP mode before the PC can detect it.
Also, I think you meant 6.0.1
Hello, I have the same problem.
when i click on the notification, the only possibility is the usb detection.
when i click on it , i have the message "usb alreadey connected".
Same problem with PC Windows 10 and 7.
Regards
my tablet version: 6.0.1 (kernel 3.10.84-perf-gf38969a [email protected] #1 Fri Sep 16 11:29:29 2016)
I have found the solution:
Deactivate My Xperia
Restart the Device
Regards
Related
Hi.
Firstly, sorry about my English.
I am using HTC HD2 about 6 months. I was able to connect my phone with my pc by USB. But nowadays, i can't do it.
My PC is using Windows 7 64-bit.
Now, my problem is:
When i connect USB cable, there is no notification or sound in my PC. (like "a device connected to PC" or "a new hardware found" etc.)
Phone can be charged via USB connection with PC but I can't use activesync.
Otherwise, when i connect PC and phone by Bluetooth, i can use WMDC.
I controlled "USB to PC" module in my phone. I tried "enable faster data synchronization" checked and unchecked. And i checked "Ask me first..." But there is no effect
And also, i tried it in another PC (which is Vista) and another USB Cable.
And when i shut down the device, and i open it while pressing volume down button, bootloader opened but in bootloader screen there wasn't a text like "USB". There is a text "Serial".
I make hard reset but it doesn't effect too.
What do you think about my problem? May it be about USB input of my phone?
I used to make HSPL in my phone and he has custom rom now.
If the problem is a hardware problem, is it out of warranty? :S
Please help me.
Thanks.
buraakk said:
Hi.
Firstly, sorry about my English.
I am using HTC HD2 about 6 months. I was able to connect my phone with my pc by USB. But nowadays, i can't do it.
My PC is using Windows 7 64-bit.
Now, my problem is:
When i connect USB cable, there is no notification or sound in my PC. (like "a device connected to PC" or "a new hardware found" etc.)
Phone can be charged via USB connection with PC but I can't use activesync.
Otherwise, when i connect PC and phone by Bluetooth, i can use WMDC.
I controlled "USB to PC" module in my phone. I tried "enable faster data synchronization" checked and unchecked. And i checked "Ask me first..." But there is no effect
And also, i tried it in another PC (which is Vista) and another USB Cable.
And when i shut down the device, and i open it while pressing volume down button, bootloader opened but in bootloader screen there wasn't a text like "USB". There is a text "Serial".
I make hard reset but it doesn't effect too.
What do you think about my problem? May it be about USB input of my phone?
I used to make HSPL in my phone and he has custom rom now.
If the problem is a hardware problem, is it out of warranty? :S
Please help me.
Thanks.
Click to expand...
Click to collapse
It maybe because you are using Win 7 64 bit. Try installing 32 bit as well and see if it cures your problem.
Also see http://support.microsoft.com/kb/946765
Russ
Hi.
Thank you for your attention.
Unfortunately, i tried it, too. In another PC, whose OS is Vista 32-bit. There is no sound or notification at PC
Actually, i've searched so many topics in this forum.
And i am almost sure that my problem is a hardware problem.
Because i tried so many things in settings of PC and Phone but there is no change.
I just wanna ask you, guys, if i send my phone to service, is there any problem about my phone's HSPL and Custom ROM situtation??
So the problem is hardware problem and most probably my USP Port is damaged.
Do you think they tell me that "your phone is out of warranty bec. of HSPL!" ?
Thanks.
faulty cable or faulty usb port. search out the "stuck in car kit mode" thread and compare the symptoms.
As per the title, device manager doesn't change when I plug the phone in, tried two different computers and two different cables, flashed the stock firmware back, and still nothing.
It charges when I plug it in and SOMETIMES brings up the MTP-Initialization logo thing, but never gets any further.
Is my GS2 goosed yet again?
Edit: Tried on my PS3 as well and still charges, but won't ask to mount the SD card or anything, so I'm back to my trusty HTC HD2, wondering whether I should sell the GS2 once it's repaired and get a Galaxy Nexus...
Hah, another HD2 veteran, it's like everyone from the HD2 forum is now here... even the devs. Anyway, may be a stupid question, but are you always trying with the same USB cable?
Disable usb debug mode
Sent from my GT-I9100 using xda premium
Tried two different cables as stated in my OP, and it doesn't matter whether USB Debugging is on or off. I'm taking it back to the service centre after work today, and I'm probably going to sell it after.
I've had the camera go.
I've had it not vibrating at all.
I've had problems with spots on the camera lens.
I think I'm going to put some money to the sale of it, and get a Galaxy Nexus, hopefully the built quality will be at least a little better...
Solution is in the phone
Dear All
Following are my observations and possible steps to
1. When the phone is upgraded to Android 2.3.4 and above (mine is 2.3.6) Kies stops recognizing the phones and USB connection / Serial port connections etc get reset on the phone
2. Even if proper drivers are there on the laptop (mine is Windows 7 64bit) they are not recognized
3. Device Manager shows "unknown device"
4. Updating the driver also does not result in any help
5. solution lies in the phone
a. key in the dialer *#7284#
b. it has 4 option there..
UART (MODEM/PDA)
USB (MODEM/PDA)
c. For USB. select the PDA.if it already selected to PDA. reselect it by select MODEM and then PDA again.. Only change the USB setting.. andthen press back. try reconnect (thanks to napi1 @ androidforums.com/samsung-galaxy-s2-international/447145-sgs2-kies-not-syncing-os-2-3-5-a.html#post3484588)
6. The Laptop will start recognizing the required drivers and install them
also
Phone is not recognized by laptop when it is in USB debug mode, MyPhoneExplorer does not recognize when it is not in Debug mode
Hope this helps
My setup
Samsung Galaxy S2 GTI9100G (not rooted)
Android 2.3.6 (upgraded on Dec 8th from Samsung link in the phone)
Windows 7 64 Bit
Dear All
Following are my observations and possible steps to
1. When the phone is upgraded to Android 2.3.4 and above (mine is 2.3.6) Kies stops recognizing the phones and USB connection / Serial port connections etc get reset on the phone
2. Even if proper drivers are there on the laptop (mine is Windows 7 64bit) they are not recognized
3. Device Manager shows "unknown device"
4. Updating the driver also does not result in any help
5. solution lies in the phone
a. key in the dialer *#7284#
b. it has 4 option there..
UART (MODEM/PDA)
USB (MODEM/PDA)
c. For USB. select the PDA.if it already selected to PDA. reselect it by select MODEM and then PDA again.. Only change the USB setting.. andthen press back. try reconnect (thanks to napi1 @ androidforums.com/samsung-galaxy-s2-international/447145-sgs2-kies-not-syncing-os-2-3-5-a.html#post3484588)
6. The Laptop will start recognizing the required drivers and install them
also
Phone is not recognized by laptop when it is in USB debug mode, MyPhoneExplorer does not recognize when it is not in Debug mode
Hope this helps
My setup
Samsung Galaxy S2 GTI9100G (not rooted)
Android 2.3.6 (upgraded on Dec 8th from Samsung link in the phone)
Windows 7 32 Bit
Thank you !!!
Unbelievable! Thank you soo Much!
Helps also on Mac 10.6.8
Thanks a lot mate..I was afraid that i'll have to take it to service center. This helped me.
thanks people!...even i had upgraded to 2.3.6 and usb mode just wouldnt work....
this solved that problem though..
Fantastic tip!
It worked! Now my S2 can be detected by the PC.
Thanks a million!
Doing a factory reset after backing up data will solve the problems.
Still Hasn't worked for me. I'm getting no USB function other than Charge. Its working as if the USB isn't plugged in at all.
Is there anyway of reinstalling the MTP application on the phone? When i find it through App manager its showing with no size and no options inside (clear data or clear cache)
Kies isn't working as far as the phone is concerned there is no USB connection at all.
I know ICS is coming within a few days for GS2 owners, will this clear the problem???
So frustrating.
Thanks in advance if anybody can help
SG2-Nick said:
Still Hasn't worked for me. I'm getting no USB function other than Charge. Its working as if the USB isn't plugged in at all.
Is there anyway of reinstalling the MTP application on the phone? When i find it through App manager its showing with no size and no options inside (clear data or clear cache)
Kies isn't working as far as the phone is concerned there is no USB connection at all.
I know ICS is coming within a few days for GS2 owners, will this clear the problem???
So frustrating.
Thanks in advance if anybody can help
Click to expand...
Click to collapse
same with mine. mine still doesnt work with the dialer *#7284# and with debugging off or on. ive unistalled and reinstalled the driver serveral times and nothing and this has happened to me on my hero and my sgs2 dozens of times, its so annoying =[. at one point i manged to get all but the usb storage drivers installed. what else can i do ???
Same problem
Same problem here, tried everything (to my knowledge). Someone told me it had to do with the battery overheating because I had use the charger from another phone. For about 2 days my phone would go on vibrate randomly and started the connection process (like a usb cable was connected). It could do that non stop for a few hours. Now that Im back to my original charger, it stoped, but still can't connect to my pc.
I tried on 3 diff PCs with diff version of windows...
I've tried everythin, debug mode on/off, reinstalled Kies, drivers, did factory reset, but nothing.. when i try to connect my SGSII to Kies, it writes "Current connection mode not supported by Kies".. I'm on Lite'ning rom v2.2..
If you're running a custom rom, why would you want to use Kies ? It's awful. There are so many other apps that have the same functionality as Kies (tho granted not one app that does everything Kies does) that work perfectly with custom roms.
Only reason to use Kies would be if you went back to stock because you wanted official ICS OTA or similar IMHO.
I did a backup with Kies, now my all contacts, sms, videos, music, calendar are in this f***in' backup file.. :| I have an awfull headache Or i can do a restore with another app, will it be compatible with Kies's backup file?
same problem. USB connection to PC will only charge. Recently updated to 2.3.6.
Tricky one.
----------EDIT---------
it worked ok after rebooting my PC. Must just be general crapiness.
Ashtwinks said:
Dear All
Following are my observations and possible steps to
1. When the phone is upgraded to Android 2.3.4 and above (mine is 2.3.6) Kies stops recognizing the phones and USB connection / Serial port connections etc get reset on the phone
2. Even if proper drivers are there on the laptop (mine is Windows 7 64bit) they are not recognized
3. Device Manager shows "unknown device"
4. Updating the driver also does not result in any help
5. solution lies in the phone
a. key in the dialer *#7284#
b. it has 4 option there..
UART (MODEM/PDA)
USB (MODEM/PDA)
c. For USB. select the PDA.if it already selected to PDA. reselect it by select MODEM and then PDA again.. Only change the USB setting.. andthen press back. try reconnect (thanks to napi1 @ androidforums.com/samsung-galaxy-s2-international/447145-sgs2-kies-not-syncing-os-2-3-5-a.html#post3484588)
6. The Laptop will start recognizing the required drivers and install them
also
Phone is not recognized by laptop when it is in USB debug mode, MyPhoneExplorer does not recognize when it is not in Debug mode
Hope this helps
My setup
Samsung Galaxy S2 GTI9100G (not rooted)
Android 2.3.6 (upgraded on Dec 8th from Samsung link in the phone)
Windows 7 64 Bit
Click to expand...
Click to collapse
Won't work on my samsung galaxy s2 (ICS 4.0.3) - windows Xp (sweet)
Hi everyone, i've got some problem with my phone.
Phone : HTC One Mini 2
Rom : NostromoPop 2.4.0 updated from 2.3.0 (in this thread => https://forum.xda-developers.com/one-mini-2/orig-development/rom-nostromopop-0-1-2-15-1-15-t3004418)
Android 5.1.1 Cyanogen 12.1 Unofficial
Rooted, Obviously.
Xposed framwork v87
I think this problem is more global than this rom or the phone. That's why I did not specify my phone or the rom in the title.
Recently, i can't acces to my phone on my PC, it's invisible. In the device manager, the MTP Device send me an error code 10 (the device cannot start). it worked fine 2 weeks ago.
Until then, the problem seems banal but ...
After trying several methods found on the net to solve this kind of problem (reinstall driver, edit registry, many reboots, ...), the mtp always don't work.
I try on other usb, on other pc, with other cable, same.
I try with 2 Windows 7 64bits and 1 Windows 10 64bits. On windows 7 they do the same thing. I connect the phone, it appear on device manager with no problem, but won't appear in "My PC" and after 1 min~, It show me the error code 10. And on windows 10, anything is good on device manager but the phone don't appear in "My PC" either.
Change MTP to PTP gray the menu but nothing more append.
But ADB work, Network sharing to USB work, And MTP on TWRP work.
I think the problem is in android but I don't want to reinitialize my phone right away. (Unless i have no choice)
My phone restarted alone during a ride with the gps. Maybe a causal link.
I am looking for ideas or solutions for this issue.
Thank you in advance
PS : Sorry for my bad english, I speak fluently the google translate.
No response ... At least I try
Issue (TL;DR):
Previously working fine. Mistakenly changed USB connection option to "charge only/always". Hassle to change it back to MTP but did. Now unstable connection when attempting file transfer via USB to Windows 7 PC. Known good cables.
Phone: LG-US998 (unlocked LC V30)
Android: 7.1.2 (stock)
Security patch: September 1, 2017 (stock)
Kernel: 4.4.63 (stock)
Build: N2G47H (stock)
Software: US99810b (stock)
Cables: AUKEY USB C Cable 3.0 (I have 3 of them).
PC's: Windows 7 and Linux Mint 18.something/cinammon. Direct USB 3.0 ports, no hubs.
Issue in detail:
1.) Everything was working fine. Good connections and successful file transfers between phone and multiple PCs and cables.
2.) Was connected via Aukey USB3.0 cable1 to Windows 10 PC. Just wanted to charge, didn't want to have file transfer active.
3.) Selected "charging only" option and "always" by mistake. This seems to be "the change" that messed everything up.
4.) Finally needed to transfer files over the weekend. Plugged Aukey cable2 into Linux Mint PC but did not get a chime or a pop-up window like normal. Looking at DISKS and phone is not visible.
5.) Remembered that I had made this change and went to go change it back. Found out that there are no options in the settings menus to do this. This seems like a bug.
6.) Tried to select a different option with the drop down after connecting. No options available even when tapping on the notification that normally brings up the USB connection options. This seems like a bug, too. Or maybe an oversight.
7.) Unlocked developer options to get to USB connection menu (this seems like overkill to change this setting back). Found "Select USB Configuration" under "Networking". Changed from "charging only" to "MTP".
8.) Disconnected USB. Reconnected USB. Didn't work. Phone still not found. Verified with Aukey cable2.
9.) Went back to developer options, turned on USB debugging. Repeated step 8, same result.
10.) Went back to developer options, revoked USB debugging authorizations. Repeated step 8, same result.
11.) Tried plugging into a different port on the PC(Linux Mint). This worked. Which seems strange. Just used next port over on motherboard.
12.) Thought strange but ok, works, don't care. Verified with Aukey cable2.
13.) Attempt file transfer on Windows 7 PC today. Kinda works, but isn't stable. Used Aukey cable 1.
14.) Plug phone in, pop up window that shows internal storage and SD card like normal. Think cool, still works. Delve into deeper subdirectories of SD card, find the one I need, start copying, phone disconnects. WTF.
15.) Try again, same thing. Never had this issue before.
16.) Works better if I go really slow (select SD, wait 10 sec, select DCIM, wait 10 sec, select Camera, wait 10 sec, select target folder, wait 10 sec, copy contents [about 500 pictures], paste to windows destination). However, the connection will still drop randomly in the middle of file transfer. Error message on PC is "The device is not connected".
17.) When this happens, the phone shows no connection, then automatically reconnects. Then get the pop up on the phone showing usb connection options like normal and windows pops up with the root file folder (internal and SD) like normal. It is behaving like I am disconnecting the USB cable.
18.) Repeat step 16, same results.
19.) Tried different USB ports. Same issue.
20.) Tried debugging on/off, oem on/off, revoke authorization yes/no, select charge only then back to MTP. Same results.
Seems like something broke when selecting USB charging only/always the first time. So I would recommend against that based on what I experience. Now, hopefully someone can help point me in a direction that helps solve this for me.
Options:
1.) Prefer not to go nuclear and factory reset. But I guess that would probably work.
2.) Is the bootloader unlocked for this phone? I would like to make an image for backup regardless, but this would make me feel a lot better about a factory reset.
3.) OTA available for US99810c. I could apply that but not sure if that would fix it as I haven't seen a good write up of all the changes from b to c. Also, would this prevent me from bootloader/root? I am not up to date on this phone but have done that kind of thing before (OG droid, galaxy S3).
4.) Don't want to unmount and remove SD card to file tranfer, that's just archaic.
Thanks in advance.
enginesong said:
Phone: LG-US998 (unlocked LC V30)
Android: 7.1.2 (stock)
Security patch: September 1, 2017 (stock)
Kernel: 4.4.63 (stock)
Build: N2G47H (stock)
Software: US99810b (stock)
Is the bootloader unlocked for this phone? I would like to make an image for backup regardless, but this would make me feel a lot better about a factory reset.
Click to expand...
Click to collapse
Yes, bootloader unlock, TWRP and root is available if you have the open market LG US998, such as those bought from B&H Photo. NOT the U.S. Cellular model US998. Both are "unlocked" (SIM card unlocked/carrier unlocked/network unlocked) -- but the open market LG US998 is the OFFICIAL carrier unlocked model and is eligible for bootloader unlock. The U.S.Cellular model US998 is not.
If you have the open market LG US998, look here:
[GUIDE][LGV30]Unlocking and Rooting - TWRP/Magisk Step-by-Step
https://forum.xda-developers.com/showthread.php?t=3745006
enginesong said:
OTA available for US99810c.
I could apply that but not sure if that would fix it as I haven't seen a good write up of all the changes from b to c.
Click to expand...
Click to collapse
Every write up of 10B to 10C should tell how much better it is. If they don't, they don't know what they're talking about.
I have 10C KDZ posted down in development section. It even works for the U.S. Cellular model US998, even though I downloaded it for the open market LG US998.
[US998][STOCK]LG V30 open market US998 US99810c_03_1216.KDZ
https://forum.xda-developers.com/showthread.php?t=3736910
enginesong said:
Also, would this prevent me from bootloader/root?
I am not up to date on this phone but have done that kind of thing before (OG droid, galaxy S3).
Click to expand...
Click to collapse
My open market LG US998 is bootloader unlocked and rooted and I was using the 10C when I did it.
Whereas, if you have the U.S. Cellular US998, no version of firmware will make your bootloader eligible to be unlocked.
Sent via open market LG US998 V30/V30+
Thanks for all the info on the bootloader! Yes, I have an official carrier unlocked unit (purchased from B&H photo). This could be a fun side project in the future.
Regarding the USB issue I posted about. I tried connecting the phone to a different laptop, this one with Windows 10. Phone connects and transfers files just fine, like it is intended. Same cable. That would point to the Windows 7 machine as buggy, broken, or possibly out of date drivers? Strange, because it used to work fine.
I can get by with the Windows 10 laptop but would love to hear if anyone else has seen this or can provide advice.
Also, it seems like the USB connection configuration option shouldn't disappear completely from the phone, just in case you hit "always" by mistake like I did. And you shouldn't have to unlock developer options to change it back. Is this normal? Anyone else want to be brave and try it out?
It's the USB3 cables
I could have sworn I already wrote a post on this (and I realize this is an ancient thread) but I've tested a variety of cables and the USB2 ones work fine for file transfer while the USB3 ones exhibit disconnection after some period of time and faster if you're trying to transfer data.
The USB cable that comes with the phone is a USB2 (4-pin on the A side) cable. I've seen the reconnection issue with Windows 10 so it may not always be a fix.
enginesong said:
Regarding the USB issue I posted about. I tried connecting the phone to a different laptop, this one with Windows 10. Phone connects and transfers files just fine, like it is intended. Same cable. That would point to the Windows 7 machine as buggy, broken, or possibly out of date drivers? Strange, because it used to work fine.
I can get by with the Windows 10 laptop but would love to hear if anyone else has seen this or can provide advice.
Click to expand...
Click to collapse
Ironically many people have used their old Win7 computer successfully when their Win10 PC fails.
I still have Win7 computer as my main home computer.
I purchased a Pixel 6 advertised as unlocked, but the OEM unlock option was greyed out in Developer Tools. I read somewhere that giving it the OTA update for at least June 2022 would unlock it, so I set out to do that.
After many issues trying to get the computer and phone to communicate, I found I should just use the ADB 1.0.32 binary (Linux), then try a combination of killing ADB, unplugging the phone, plugging it back in, starting ADB, etc., etc. until there is no longer "offline", "no device", or "unauthorized" shown. Eventually, I got it to communicate once it recognized the phone as being in "sideload" status.
So, after running `./adb_Linux sideload oriole-ota-sq3a.220705.003-17fec7eb.zip`, it finally did something. Except, it was stuck at, "Verifying update package..." No matter how many times I reach this point, no matter how many minutes or hours I wait, nothing happens.
Any ideas? I couldn't find any solutions or similar problems posted anywhere.
Since you're mucking around with ota's, it sounds like you are deliberately keeping it disconnected from the network, otherwise it would prompt you with an update almost immediately and there would be no need for this.
In order for the unlocking switch to be enabled, the phone MUST be connected to the network.
Also be CERTAIN that your device is a Pixel 6 and not a Pixel 6a. The 6a is the one that needs a particular update version in order for unlocking to work due to a bug. The 6 will unlock just fine on factory firmware. Assuming that you have a 6a, this would explain why trying to install "oriole" firmware would fail for you since it is a DIFFERENT PHONE.
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Zakku said:
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Click to expand...
Click to collapse
I don't see it as a huge issue in need of a resolution. Google does NOT blacklist you in any way for unlocking the bootloader, and they already know all of the identifying codes on every phone anyway so its not like you're keeping any information from them. Just don't put a sim card in it before unlocking it, and if you're worried they will connect the phone with your IP address, use a VPN or public AP.
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
96carboard said:
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
Click to expand...
Click to collapse
His comments seem to have a lot to do with this thread. Clearly, at least to me, he tried sideloading and had a problem. He was simply relaying what he tried to fix it.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Yep same thing on my XPS 9710 which only has TB4 ports: using a TB4 to USB A adapter and then an A to C cable worked, stupid of Google to not include native C support since they have been using C as the standard since 2016 with the Nexus 6P lol.
I think the USB issue might be more of a combination of thighs, since when I tried to sideload through classic C to A cable it was really slow and basically got stuck at like 5%, then I used "higher quality" C to C cable and the update was done in minute.
Sneakyghost said:
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Click to expand...
Click to collapse
Yep. This the bloody fix! Exact same problem. Stuck at verifying at 2% for the September patch. I switched USB ports from my new laptop to the dock itself and finally, sideloaded it. Does ADB need to be updated to work with USB 3.0?