So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Maybe your usb port is broken, but if you have root you can flash twrp using apps such as flashify. Won't be much use since usb might be broken. Try going to a service center nearby to get it fixed.
Crimson123 said:
So, this is after searching for around 7-8 hours for a solution. My poco f1's usb port is somehow broken. By broken, I mean it charges perfectly fine, but will not get recognized by any other device (tried 3 different pcs, both ryzen and intel).
About 4 months ago i bought my poco f1, and installed lineageOS as soon as i could. Had some hiccups, but in the end everything was fine.
About 3 days ago I ended up trying to switch to pixel experience rom, since people were enjoying that more than lineag. I ended up getting an error saying i needed firmware from MIUI 9.2.15 or something. Alright, I'll just flash miui and then flash pixel experience... right? Well, apparently this also overrides twrp recovery and makes it boot into xiaomi's useless miui recovery. This makes it so that you cant get back into twrp without a computer. Great, now I guess ill just connect it to my pc... annnd... nothing.
Enabling every usb debugging setting, changing the usb networking to file transfer, rebooting, factory resetting and repeating everything leads to a dead end. Tried 4 different usb cables with absolutely no results. Tried 3 different pcs, nothing. And after all this, the phone charges completely fine as if nothing is wrong. The device isnt rooted either, meaning i cant manually boot into twrp using their app.
My device's bootloader IS unlocked, leading to my only possible solution i can think of: achieving root somehow since the bootloader is unlocked and downloading the TWRP app and rebooting into twrp. Or i should just yeet this on ebay and get a new poco.
Help?
Click to expand...
Click to collapse
Found any solution for this. I am facing the same issue
kiranbala003 said:
Found any solution for this. I am facing the same issue
Click to expand...
Click to collapse
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
tiennhu89 said:
Try change ur port usb. Use port 2.0, not 3.0. Intel pc, not other.
Click to expand...
Click to collapse
Yup. Tried everything. Still not detecting
Are you using the cable that comes out of the box ?
Some third party cables don't transfer data.
(Can be the case for deteriorated cables too)
If You trying with Windows make batch file for example:
c:\usb-fix.bat
@Echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
Start cmd as Administrator and restart PC, then will work on Windows.
Related
So... now that I think with hindsight, I did something pretty stupid, and I'm going to need some help, since I have no idea what to do.
I have a Nexus 9 tablet, and I never liked it. The OS is just so slow and laggy, and it overheats, and it has many other problems. Quite a couple of times, I installed custom ROM's and so on, and I never had a problem. Let me explain what I did now.
Around a month ago, while looking on the internet, I heard this thing that if I install the original software, but with no encryption, it would work better. It sounded cool at the time, so I downloaded the Nexus Root Toolkit, and did it.
Everything went well. But then I heard about a custom ROM that was apparently working even better, Dirty Unicorns, so using the same toolkit, I installed it. For the first time, my Nexus 9 actually worked the way it is supposed to work, but the custom ROM still had its problems, it crashed from time to time. I was thinking about possibly returning or selling the tablet, so that's why using the Toolkit, I reinstalled the original software. But, if I went all the steps, and also locked the OEM, my device then showed a flag saying that it was a development device, while booting up. So, after messing around with the settings of the Toolkit a little, I decided to reinstall the software, but leave the bootloader unlocked.
But after some time, I reinstalled my Windows, and I also reinstalled the Toolkit. But that's when I started to have problems. My tablet wouldn't connect to my laptop anymore. I used the toolkit and uninstalled drivers, reinstalling others quite a couple of times, and that's where I think that I messed something up. I managed to eventually connect my tablet, and I rooted it, after rooting it, I connected it again. But adb wasn't working for some reason. A little annoyed, I simply copy pasted the zip file of CM13 into my tablet's internal storage, and I rebooted it to the recovery, TWRP. But the recovery failed to flash it, saying something about an Error 7.
Now that I think about it, I was stupid, since after that, I performed a complete factory reset, resetting my TWRP backup too. I tried to connect it again, nothing. It didn't connect at all. I plug it in, my computer doesn't even recognize that something is plugged in. No Nexus 9, no Android Device, no anything. I booted it in fastboot mode, and it worked, my computer recognized it, and after I downloaded a ROM zip file again, I tried to connect the tablet back and flash it manually, but nothing. It didn't recognize anything anymore.
I tried to reinstall the drivers countless times. I deleted what I had, reinstalled it, nothing. I uninstalled and reinstalled the Toolkit. But strangely, now, even if I know that I installed the Google USB drivers, and the ADB drivers, as I even installed Android SDK, if I use USB Deview, it doesn't show me any of them. I can't see any Google or ADB drivers, although I tried installing them multiple times. So now, I'm stuck with a tablet with TWRP and no OS, which I can't connect to my PC, and I can't use ADB or fastboot.
Is it something from my laptop? I can't check to see if it will connect to another PC right now, so I don't know for sure. Is there any way to delete all the traces from my (failed) attempts at reinstalling the drivers, and to install them again properly? Or is it something from the tablet itself? I don't have an OS, so I can't enable USB debugging.
So, shortly, I have no idea what's happening. And I'm quite obviously a noob in all of these. Can anyone help me? Please?
If you boot into the bootloader and from a command prompt type fastboot devices you don't get anything?
Sent from my Nexus 9 using XDA-Developers mobile app
I still couldn't get ADB to work, but I managed to work out fastboot. It may be something from my USB cable, it works perfectly.
I flashed the original software back, and I'll go to check my cable, although I feel kinda stupid that I didn't think about that in the first place.
Thanks for the help anyway.
If fastboot is working and bootloader is unlocked, you can still install a factory image.
Depending of your device download for wifi Version:
https://dl.google.com/dl/android/aosp/volantis-mob30p-factory-2cb57a1b.tgz
If you habe the LTE variant:
https://dl.google.com/dl/android/aosp/volantisg-mob30p-factory-ae9ce05a.tgz
Extract the files and put them into the same directory link fastboot and execute the flash-all.bat
WARNING: Any data will be erased!!! Also TWRP
Now it should boot up with stock firmware.
If you want your device decrypted install twrp. format the internal storage and flash the pure nexus rom which i can highly recommend and is decrypted by default. Dont forget do flash gapps
my issue is same
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
rohanzakie said:
what if someone USB- debug is not enabled , is there any possibility to do that , i have a device nexus 9 , rooted it it went into bootloop then i factory reset it , and now my adb is not communicating , if there is any options?
Click to expand...
Click to collapse
Use fastboot, not adb.
what if fastboot isn't working, either?
uberSkeptic said:
what if fastboot isn't working, either?
Click to expand...
Click to collapse
Is the tablet in fastboot mode?
madbat99 said:
Is the tablet in fastboot mode?
Click to expand...
Click to collapse
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
uberSkeptic said:
Yup. I can boot into the bootloader, and from there (or from TWRP) into fastboot, but no computer I've connected it to (and I've tried many) will recognize it. Doesn't show up in Device Manger or lsusb, doesn't show up from either "adb devices" or "fastboot list devices" (the latter just hangs there saying "Waiting for any device"). The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Hi, uberSkeptic...
Just a quick thought... Have you tried a different USB cable?
Rgrds,
Ged.
Edit & Additional...
The command is not fastboot list devices... it's fastboot devices
One last point... Ensure your Nexus 9 is definitely booted into fastboot mode and not just HBOOT (the bootloader). Take a look at the two screenshots below - your Nexus 9 should look like the screenshot on the right, the one with my green explanatory text.
Apologies for the poor image quality; there's no way of taking a screenshot in the bootloader, so I had to take photographs instead.
Hope this helps and good luck.
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
uberSkeptic said:
Thanks for the advice and going so far as to photograph the hboot/fastboot screens, but unfortunately I have indeed tried multiple USB cables, including the OEM's and I've definitely successfully gotten the tablet into fastboot but it doesn't show on the computer with either fastboot command (devices or devices list).
Click to expand...
Click to collapse
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
GedBlake said:
I'm out of ideas then.
One of my first thoughts was possible Windows driver problems, but as you mentioned you'd tried it on several different computers, that didn't seem to be a likely cause of the problem - I mean, you'd expect at least one of 'em to work! Maybe somebody else can help with a solution.
Click to expand...
Click to collapse
Sadly, me too. I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Too bad, too - the tablet is otherwise in great condition and even has a custom-painted backplate (long story).
Thanks for trying to help, though!
uberSkeptic said:
...The USB on the tablet itself is fine, and I even replaced the USB daughter-board just to be safe.
Click to expand...
Click to collapse
Mmm...
uberSkeptic said:
...I even tried using a flash drive with a micro-USB connector on it, which I used to use to do nandroid backups, but now TWRP doesn't even "notice" that the USB drive is there (or any USB drive connected via an OTG cable).
Click to expand...
Click to collapse
Mmm... (scratches head, raises eyebrow quizzically)...
If I was Hercule Poirot and this was a murder case, and with all the suspects gathered in one room, prior to revealing a brilliant deduction... I'd be casting very dark glances in the direction of your Nexus 9's USB port right now as the likely culprit here.
Think about it. Different computers. Different USB cables. An OTG cable... And none of them work. What's the one thing they all have in common?
Answer: The USB port on the Nexus 9 itself, and where you've replaced the USB daughter-board.
Maybe, possibly, that replacement don't go so well. Maybe there's some unknown problem with it. I can't comment too much on this, 'cos it outside the scope of my knowledge - I'm a software guy; circuit boards and dismantling devices to fix 'em isn't something I'm comfortable with. I always think I'm going to damage something or rip a wire out somewhere, so I bow to your superior knowledge in this area, as I may be talking complete cobblers here. It certainly wouldn't be the first time.
Anyway... Sorry I wasn't able to help find a working solution for you. If anything occurs to me that might help, I'll be sure to let you know.
Rgrds,
Ged.
I would be suspect if the replacement as well if it weren't for the fact that I did it only AFTER the other symptoms/problems appeared. Hence the replacement (which is known good because the battery charges no problem). There cables and everything inside the tablet tests just fine... It feels like the firmware for USB is somehow corrupt or something.
Thanks for all the advice, though. ?
So I can't believe I didn't think of this before, but when I run "dmesg" from the terminal app included w/ TWRP, I see that there a TON of errors, mostly referencing problems accessing the recovery image. I could screenshot it, if anyone at all might be able to tell me a little more specifically what the dmesg log is trying to tell me...
Hello. My Redmi Note 3 SD run CM14.1 with kernel Radon 3.5. It run smoothly for a month until 3 days ago. It cannot be charged as well as cannot connect to PC as USB (PC cannot recognize it). For half a day after that, the phone suddenly returned to be normal as nothing happened. And today, the same error happened again. I tried plugging it in through fastboot mode and it worked. So I thought It would be software error, I used Miflash to flash MIUI Global stable 7.1.5 with the hope that it can fix it. But not. It successfully flashed to MIUI but the problem is still here
Is there anybody got the same problem? Can anybody help me? Please!!!
p/s: Sorry for my weird English, I'm not a native speaker.
Try this:
The problem might be with your USB cable and/or your phone's micro USB port (worst case, your phone's motherboard/IC - let's hope that isn't the case). Try using different Mi USB cable or different device with the same model to find the fault. Make sure you have the required drivers installed. Hope this helps.
Hello
I made a thread on reddit in the subreddit of my ROM (/r/LineageOS/comments/cccbtu/pc_does_not_detect_xiaomi_redmi_note_4/) regarding my issue and they recommended that I come here (I hope that's the right place.)
In summary, the notification that usually shows when I plug in my phone, to change the USB configuration from charging to MTP, does not show.
I've tried everything I can think of (different ports, PCs, cables, etc.) and nothing seems to help.
"adb devices" shows no devices both on normal boot and TWRP. The only thing the cable does is charge.
I'd be very happy to fix it.
Thank you!
First it's a software issue so the hardware is fine
Second i suggest getting an sd card with the official stock rom on it (version 10.1.1.0) to fix the reading error since it can't be readed even on twrp
If the problem still presists
I suggest to change the cable or the phone socket
Try another cable then see
Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
slumpp said:
Hello,
I am currently in a dead end with my Poco F1, and would like to check with you before throwing it away.
I was using my Poco in version 12.0.3.0 with TWRP installed and root with Magisk. Due to the last days errors of apps that shut down when opened, I decided to reinstall the system using TWRP, but I made a mistake and installed version 12.0.2.0.
I don't know what installing this version did, but now the mobile isn't starting MIUI anymore, it's starting by default TWRP. Furthermore, something has been changed in the TWRP version installed that touchsreen it's not responding, so I can´t use.
The problem is worse since, for a long time the transfer of files to a PC via USB cable isn't working on my Poco, so Windows is not able to detect the mobile in fastboot mode either. I tryied reinstalling drivres in many ways, and still not working. The poco charges perfectly, so I don't think the problem is the USB conector, maybe is a motherboard related issue, so changing the connector I don't belive will solve the problem
Recap:
- I can't start MIUI (the version has been corrupted).
- I can't use TWRP (it has been corrupted and the touch screen does not work).
- I can't install from fastboot (Windows isn`t detecting the Poco with the cable connected).
- I don't think changing USB connector solve de USB data transfer problem.
Any ideas or should I throw away the smartphone?
For me it's a real pitty, because I don't like the new Poco F3 or others phones on the market, most of them don't have 3.5mm jack or microsd card slot, and are bigger, heavier and more expensive than the Poco F1.
Thanks to everyone.
Click to expand...
Click to collapse
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Retrial said:
Hello,
The issue with error of apps was probably due Webview which Google pushed an update and fixed it. For more infos read here.
Now, to the current problem...how did u flashed previous version? Clean installed or Dirty installed?
What Desktop system do you use? AMD or Intel? Your PC can detect the device while you are on TWRP? Do you have twrp.img on ur device so you can reflash it via TWRP?
Check my POCO F1 Ultimate Collection & Guides
Click to expand...
Click to collapse
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
slumpp said:
Thanks for your answer.
I noticed that the issue with the apps is due to webview after breaking my phone, next time I'll think things twice before flashing anything.
I did a dirty installation, I thought I was installing same version (12.0.3.0), but I was flashing 12.0.2.0 on top of 12.0.3.0 without cleaning.
I tried both desktop systems: my laptop with an Intel CPU, and a PC with AMD Ryzen 9 3900X. I also tried 5 diferent USB-C cables that are working perfectly with others Android devices. When I look for new devices in the device manager of windows I can't tell any diference on listed devices with or without connecting the Poco. As I said, maybe I have some hardware issue in the phone, because file transfer was not working for many months.
I can't install anything via TWRP because touchscreen don`t respond to mi fingers... I remerber that this happend to me years ago when I installed a wrong TWRP version, but don't know if that is the problem.
Click to expand...
Click to collapse
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Retrial said:
Are you able to to connect your device while u are on TWRP? Your PC recognize it?
Click to expand...
Click to collapse
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
slumpp said:
I tried to connect the device with TWRP opened, and in fastboot mode, PC don't recognize in any case.
Click to expand...
Click to collapse
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
I'll try if connecting something via OTG make the phone responds, but the main problem with TWRP is that appears to be corrupted or something. I cann't use it because touchscreen don't responds to me, and nothing happens either if I try to use it with volume+ and volume- buttons, I see TWRP but I can`t interact with it.
Thanks again for your patience.
Retrial said:
Well, somehow you need to manage to flash MIUI again via TWRP or Mi Flash Tool.
Perhaps if you redownload latest twrp.img and latest official miui 12.0.3.0 and transfer them to USB OTG or external SD Card and then put ur OTG or external SD Card to your phone and flash it from TWRP. Since you was able to wipe system as u said before you will be able to flash twrp.img into "Recovery" make Clean Install (according my guide) and flash MIUI.
Click to expand...
Click to collapse
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
slumpp said:
I tried using OTG cable in TWRP and nothing hapens, TWRP don't respond.
Seems that I'm in a dead end, I ordered an USB PCB spare part to try if is posible to repair the USB data transfer connection replacing it, becuase looks like is the only way I have of flashing a new clean rom.
Click to expand...
Click to collapse
If you have AMD system try the AMD Fix in my guide. Also try this guide to install drivers.
Finally I could solve the problem.
I bought a new part of the USB port PCB from aliexpress, I ordered one that claims to be original for around 15€, not the 2€ ones.
I replaced it and the data transfer is working again, so I could install the ROM via fastboot from my PC.
I don't beleive that the PCB I replaced is original, but works like it is, phone charges properly and seems that didn't loose signal.
Thanks to everyone.
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?