Calling all A95X MAX owners!
Has anyone successfully connected this TV box to a PC in order to send ADB commands?
I installed the S905X2 USB drivers that come with the S905X2_USB_Burning_Tool. With USB debugging on, I put the A95X MAX into bootloader and connected it to my PC with a male-to-male type-a USB cable, but there was no reaction in the PC's device manager, where you'd expect to see the Android USB driver appear when a connection is made. (I did get power throught the cable, for when I unplugged the power to the A95X MAX it remained on with the USB cable plugged in.)
Is there something I don't know about or has no-one here tried to connect the box to a PC via USB?
It would be useful to send ADB & fastboot commands to this TV box.
I feel your pain
doktorspin said:
Calling all A95X MAX owners!
I also have tried to connect via usb to the a95x max us and MANY other amlogic manufactured tv boxes without success.
You would think some expert person from this forum would respond to this issue once and for all... GRRRR....but noooooooo, no such expert person seems to want to answer the bell here or in any other related tech forum I have gone to. Is it possible no one on the planet knows the answer to this?
Attempting tech support at both gearbox and geekbuying websites, places where one typically purchases such tv boxes have yielded nonsensical/completely useless/incompetent answers so no point going there for any such related support.
Anyway. From what have been able to observe, the burning tool driver shown as "libusb-win32 usb devices" known strangely as the "world cup" driver, "only works for the burning process app as far as the box being recognized by the burning tool app via a USB connection but it seems it has nothing to do with the device being recognized by the ADB.EXE PC side app when using the USB connection.
For that you need an "android composite ADB interface driver". Unfortunately, none of the google or Microsoft or any "universal" ADB USB drivers I have tried, seem to work for these amlogic tv boxes which throws you back to having to go to the amlogic manufacturer to download their drivers from there.
Although this makes almost too much sense, you won't find any downloadable drivers at their site, "amlogicdot com, so we all are back to step one...GRRRRR.
So, until a forum expert from this xda-developers site finally decides to help with this issue....if in fact that will ever happen, we are all pretty much stuck in the mud here as far as the needed USB connection. Until that happens, here is a work around I developed which will let you communicate with these boxes without the need for any USB drivers as long as such amlogic boxes come rooted.
The TCPIP wireless or wired connection trick:
What many folks don't know is that if the box is unrooted you will ALWAYS need to have an initial USB connection before one can switch over to a tcpip connection ("ADB tcpip 5555" command after you have FIRST established a USB connection), but if the box is rooted you do NOT have to have an initial successful USB connection!!!
The secret is to switch over to tcpip at the Android device FIRST by using one of many apps on the android device that activates this such as "WIFI ADB" or "ADB WIFI reborn" app etc. Don't bother with the ones that say no root or any other app that says you need to connect a USB cable first since that defeats the whole point of this post right?...smile.
The app typically will give the IP address of your device along with the command needed on the PC side such as "ADB connect 192.168.1.3:5555" (the device IP address along with its port number ) which allows you to connect your PC to the android device via tcpip WITHOUT ever connecting to any USB cable and having to worry about non functioning USB drivers.
In closing, although I think I have provided a life saver solution for those that cannot get the USB connection to work to still be able to connect to their android device regardless of a non-working USB connection, there are cases where windows apps relying on ADB won't work even with a rooted device because these developers at program entry, STUBBORNLY just look for a USB connection instead of looking and USING A-N-Y valid and working connection as should be the case regardless if it’s thru USB or tcpip.
If any other forum member can help us figure out how to force these win apps to use ANY available valid working connection and not just a usb connection this post would then have a COMPLETE solution to this issue.
Hopefully the explained tcpip work around in this post can help those stuck with a non-working usb connection.
Cheers Ed Ray;
Click to expand...
Click to collapse
Ed,
Thanks for your response. I've been trying another approach to deal with my basic problem of being able to flash a system image (a ROM) onto the A95X MAX. It mainly involved trying to get TWRP running and get it to flash the image. That seemed to be unsurmountable. So now I'm looking into the possibility of putting the system image into a zip file with a little glue and using stock recovery to flash it from the SD card.
In the process I found instructions as to how to get ADB up & running over ethernet here:
https://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
Sounds like it should work, but I'm drained on this system into a zip file thing.
Cheers.
Related
Hi Community-
I'm having USB connection issues & was hoping for a little guidance.
Although I've read through multiple USB problem threads, I thought I'd start my own rather than hijack another member's thread.
In an effort to best help, I'll try to be thorough.
When I connect my Vibrant to PC, I get the "USB Device Not Recognized" and "Error Code 43" notifications & "Unknown Device" designation in Device Manager. Also, when I set updates to automatic, I get an "Drivers failed to install" notification (paraphrased).
I am running EDT's Project V with one of the Bullet 1.2/1.42 kernels. While I DO NOT believe the ROM or Kernel are causing issue, I will likely change both soon to confirm.
To solve the issue, I have attempted the following in USB Debugging and Mass Storage modes:
1. Plugged into 3 different PCs (2 running XP, 1 running W7).
a. Multiple usb ports in each.
2. Used 4 different micro USB cables (two are original Samsung cables).
3. Allowed windows to autdetect & install drivers (fails).
4. Installed 32 bit drivers & 64 bit drivers from multiple sources using the included setup files (uninstalled between).
5. Manually directed Windows to 32 bit and 64 bit drivers using Device Manager.
6. Attempted to connect to Kies Mini in Kies mode (uninstalled program after failure).
*As a side note, I successfully connected a Captivate & Fascinate (neither mine) to one of the PCs using one of the same Samsung cables I have tried.
*And another: I have not tried to connect the Vibrant recently, but have successfully connected the phone to multiple PCs in the past.
To this point, I have not tried:
1. Manually installing I9000 drivers.
2. Installing a new Froyo kernel and/or ROM.
3. Reverting to a previous Froyo nandroid that connected in the past.
4. Flashing an Eclair kernel then reverting to a stock Eclair nandroid.
Those will likely be the next steps, but if any users have had success using additional methods, any advice would be greatly appreciated.
Thanks!
Try this from Unlockr.com (was for HTC drivers but you can clear remaining Samsung drivers if any)
1. Download USBDeview
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
2. While the phone is still plugged in, open USBDeview and sort by manufacturer. Find all the Samsung drivers and delete them all.
3. Once all have been deleted, unplug the phone from the USB cable and plug it back in.
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
suchavibrantthang said:
4. The correct drivers should reinstall automatically (check the drivers as they are installing, one should say ADB Device driver).
Click to expand...
Click to collapse
Downloaded USBDeview from the provided link. Program confirmed that I have already deleted all Samsung drivers.
When I left program running and plugged Vibrant back in, I got:
1. Same error notification (device has malfunctioned).
2. Windows did not try to download drivers (despite permission in Windows Update).
3. USBDeview did not recognize that a USB device had been plugged in (checked "Display devices without drivers" under Options & refreshed).
Thanks for the reply & a new method to attempt though! Something's gotta work eventually.
"device has malfunctioned"
"Drivers failed to install" notification"
edit: just letting you know my experiences with those failure notices. for me it had nothing to do with drivers and such. it was faulty hardware.
Ive had this problem with one of my MS Bluetrak mouses. The USB dongle fried and burned and messed up one of my usb2.0 ports on my laptop, leaving me with only one. Might be your usb port in your phone that's malfunctioned. My two vibrants have loose connections now because of the way it pulled left or right while charging. so it's either your usb port on pc or the phone has a bent chip or massive dust...idk
sorry i cant help. another alternative is to replace your usb part on your phone.
suchavibrantthang said:
"device has malfunctioned"
"Drivers failed to install" notification"
phone has a bent chip or massive dust...idk
another alternative is to replace your usb part on your phone.
Click to expand...
Click to collapse
Yeah, looking that way, huh?
Anyway, thanks again.
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
mrlazyone said:
the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
Haha, tried my thickest cable for 15 min again just to see.
Unfortunately, I'm getting close to giving up.
So:
1. No smartphone for a while ... Boo!
2. Or no Odin ever ... Double boo!!
Sent from my SGH-T959 using XDA App
mrlazyone said:
I had a similar situation. I had 4 micro usb cables, two samsung stock ones (captivate/vibrant), 1 blackberry, 1 which I forgot where I got it from. Long story short, the blackberry one which coincidentally was the thickest cable of the bunch was the only one that consistently detected my phone. Hope that helps...
Click to expand...
Click to collapse
THANK YOU!!!! I tried using my wife's cable and it did the trick! It sucks because I saw your comment a few days ago but it didn't register but this morning I am sleepless so decided to give it a shot again and voila!!! Thank you boss.
I have been working through this for a while as well. As far as I can tell, the problem is isolated to only my machine, even though there are a couple of different USB controllers within. Both cables I have and the CM7.1-nightly (various attempted) Vibrant I am using will connect to my laptop and my other desktop, but not to my Asus P8Z68-V Pro (either directly or through a hub, through the USB3 controller and USB3 + hub). I have also tried a separate stock Vibrant, same results. All I get on my uber-rig is charging
one thing that HAS worked (in a limited fashion) is using the hub built in to my Razer Tarantula keyboard, however its USB 1.1 and cant supply the proper voltage. So code 43 becomes code 10 (This Device Cannot Start [USB Hub Power Exceeded]), still no functionality.
fortunately my mobo has a built in bluetooth module and I can just push things around with that. slowly... Will be keeping an eye out for bios and chipset updates to see if they resolve, and in the future may try an add-in USB2 card
Please take the time to read this:I flashed and installed SkyRaider a couple days ago and I noticed when I connected to my PC that my PC started recognizing it as HTC Phone (or something of the like). This apparently really screwed up my drivers on my computer because I installed iKReaM and now I can't even get into disk drive mode...it doesn't ask what connection type I want anymore and my computer just says "USB Device Not Recognized". I tried uninstalling the HTC Driver Installer but that didn't do anything either. This is not good as I ran into the same problem when trying to root my friends Samsung Fascinate and never go the problem fixed. Anyways...my phone worked perfect before and SkyRaider evidently messed it up pretty good...to say I am pissed is an understatement. If you need any more info please let me know.
Please link me to the newest HTC Drivers as well, it would be much appreciated.
If no one can help I will have to do a clean install of windows 7, which is not an enjoyable experience
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Stratejaket said:
https://market.android.com/details?id=com.dooblou.WiFiFileExplorer&hl=en
You will have to buy the pro version to push files. That would be your easy solution.
You can always use recovery to get into usb mode as well.
Click to expand...
Click to collapse
I can't get into recovery anymore using usb mode, computer doesn't recognize the device so no way to use it...and I would use the Wifi app instead of using a usb cable? I see what you mean by easy but I don't wanna avoid the problem...I have a brand new $1600 Alienware so I would like to have it fixed lol...if need be I may just have to do a clean install
I know this isn't your actual problem but just for the record, AirDroid lets you control your phone and push files to it with a web browser and wifi for free.
(I tried linking it but I guess I haven't made enough posts to include links yet, easy to find by searching the Market tho)
You might check under Settings/ Connect to PC to make sure the Ask Me option is turned on.
Sent from my ADR6400L using Tapatalk
When you plug your phone into your computer does the phone start to charge?
If so restart the computer and plug the phone into a different usb port. Check device manager and see if you have it listed in your usb devices, or you have an ! over a usb. Most of the time this ends up being an issue with the computer it is being hooked to, not the phone. The computer isn't launching the driver correctly to show the phone that it is connected to a computer, and not just a wall outlet.
Even when I've had this issue, which is random I have still been able to use recovery usb to manage it. Make sure when your in recovery you mount the sdcard before enabling the usb.
My Kindle Fire HDX 7 (thor) is was rooted using kingroot on fire os 4.5.5.2, unlocked bootloader, twrp installed, and Lineage 13 installed. Everything is fine except that almost all usb protocols are screw up. The only one that does work is charging.
When I plug it into my pc (win10) it keeps appearing on the taskbar with the unrecognized usb device logo and then half a second to 2 seconds later it disappears and my pc makes the disconnected noise. Then .5 to 2 seconds later it will reappear with the unrecognized usb device logo and disconnect and repeat infinitely. Therefore, no mtp or adb. I've settled for wifi file transfer and haven't had to use adb yet, but I need mtp soon for larger files, and I need adb for other stuff soon too. Now. Fastboot, on the other hand, does sorta work. It shows up as an unrecognized usb device, but doesn't show up when I do "fastboot devices". I've done tons of research and tried so many solutions, and it's not a problem with my cables or pc. The problem is with the kindle. I hope very dearly that it's a software issue and not a hardware issue. One extra important detail: in developer options when I change the USB configuration to mtp it changes it but only shows the change when it I go out of developer options and back in. Then when I press any other option it automatically reverts it back to charging.
Uzerexample said:
My Kindle Fire HDX 7 (thor) is was rooted using kingroot on fire os 4.5.5.2, unlocked bootloader, twrp installed, and Lineage 13 installed. Everything is fine except that almost all usb protocols are screw up. The only one that does work is charging.
When I plug it into my pc (win10) it keeps appearing on the taskbar with the unrecognized usb device logo and then half a second to 2 seconds later it disappears and my pc makes the disconnected noise. Then .5 to 2 seconds later it will reappear with the unrecognized usb device logo and disconnect and repeat infinitely. Therefore, no mtp or adb. I've settled for wifi file transfer and haven't had to use adb yet, but I need mtp soon for larger files, and I need adb for other stuff soon too. Now. Fastboot, on the other hand, does sorta work. It shows up as an unrecognized usb device, but doesn't show up when I do "fastboot devices". I've done tons of research and tried so many solutions, and it's not a problem with my cables or pc. The problem is with the kindle. I hope very dearly that it's a software issue and not a hardware issue. One extra important detail: in developer options when I change the USB configuration to mtp it changes it but only shows the change when it I go out of developer options and back in. Then when I press any other option it automatically reverts it back to charging.
Click to expand...
Click to collapse
Well, first step is to try a Nougat based rom such as AEX, Lineage 14.1 or Resurrection Remix. Obviously backup your current config before flashing a new ROM. Good luck.
Help!
Davey126 said:
Well, first step is to try a Nougat based rom such as AEX, Lineage 14.1 or Resurrection Remix. Obviously backup your current config before flashing a new ROM. Good luck.
Click to expand...
Click to collapse
I'll try Resurrection Remix and AEX, but LN 14.1 definitely doesn't work. I just flashed a stock 4.5.5 rom via twrp and that's what I'm currently using. With stock rom it shows up as an unrecognized usb devices but now it at least stays and doesn't keep dis/reappearing. Still no adb or fastboot. I can't find I way to change it to an mtp device in device manager. PLEASE HELP!
Uzerexample said:
PLEASE HELP!
Click to expand...
Click to collapse
Exceptionally annoying.
Uzerexample said:
I'll try Resurrection Remix and AEX, but LN 14.1 definitely doesn't work. I just flashed a stock 4.5.5 rom via twrp and that's what I'm currently using. With stock rom it shows up as an unrecognized usb devices but now it at least stays and doesn't keep dis/reappearing. Still no adb or fastboot. I can't find I way to change it to an mtp device in device manager.
Click to expand...
Click to collapse
In most ROMs (can't speak to FireOS v4) ADB toggle is in Developer Options. Switching between modes is usually accomplished via notification toggle or separate setting. Unrecognized but otherwise functional device scenarios are almost always traceable to crappy cables, Windows drivers or direct/indirect use of a USB hub that doesn't carry the data signal. More exotic causes involve a bad port or other hardware fault. I am not aware of any firmware toggle that would persist across system partition wipes and installation of different ROMs from varying Android generations.
I have had consistent good luck using drivers installed with the following package (don't need to use/launch...just install). Look for Moto Composite variants with the device tethered.
https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,4222
PC driver issue
Davey126 said:
In most ROMs (can't speak to FireOS v4) ADB toggle is in Developer Options. Switching between modes is usually accomplished via notification toggle or separate setting. Unrecognized but otherwise functional device scenarios are almost always traceable to crappy cables, Windows drivers or direct/indirect use of a USB hub that doesn't carry the data signal. More exotic causes involve a bad port or other hardware fault. I am not aware of any firmware toggle that would persist across system partition wipes and installation of different ROMs from varying Android generations.
I have had consistent good luck using drivers installed with the following package (don't need to use/launch...just install). Look for Moto Composite variants with the device tethered.
Click to expand...
Click to collapse
Next day. Went back to dis/reappearing on pc rapidly. Different cable isn't issue same cable works perfectly with NVIDIA K1 tablet, and I tried RR rom. While I tested it and loved the customization of RR, it didn't fix it. The PC driver side of it. In device manager it showed up as Unknown USB device (Device descriptor request failed) and it shows under Universal serial Bus Controllers. When I go to update the device as an android mtp or adb or anything, none of the mtp of adb driver options show.
Uzerexample said:
Next day. Went back to dis/reappearing on pc rapidly. Different cable isn't issue same cable works perfectly with NVIDIA K1 tablet, and I tried RR rom. While I tested it and loved the customization of RR, it didn't fix it. The PC driver side of it. In device manager it showed up as Unknown USB device (Device descriptor request failed) and it shows under Universal serial Bus Controllers. When I go to update the device as an android mtp or adb or anything, none of the mtp of adb driver options show.
Click to expand...
Click to collapse
Whether the cable works with another device is largely irrelevant. HDX devices are very picky/sensitive with tethered communications. Been working with these pups for 5+ years and heard many a forceful testimonial about how it can't be related to ports/cables/hosts. Amazing how many communication issues are fixed with a simple cable/port swap. Occasionally joy is found by connecting to a different host.
That said, your device may have a hardware problem. Not uncommon if you picked it up on auction at a bargain price. Keep trying different cable/port/host combinations.
Half way sucess
Davey126 said:
Whether the cable works with another device is largely irrelevant. HDX devices are very picky/sensitive with tethered communications. Been working with these pups for 5+ years and heard many a forceful testimonial about how it can't be related to ports/cables/hosts. Amazing how many communication issues are fixed with a simple cable/port swap. Occasionally joy is found by connecting to a different host.
That said, your device may have a hardware problem. Not uncommon if you picked it up on auction at a bargain price. Keep trying different cable/port/host combinations.
Click to expand...
Click to collapse
(Running a twrp flashable version of Fire os 4.5.5 https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914) I used a different port and it stopped rapidly dis/reappearing! It stays connected... but as an unknown USB device (device descriptor request failed) I think I've isolated the problem on the kindle side. Something is making it think it's a different device. When I change the USB configuration in Dev settings, it does nothing. The computer doesn't see any changes, and when I turn off both MTP and PTP no changes were detected on pc and nothing happened on kindle. The MTP and PTP toggles are nothing more than cosmetic buttons. Is something wrong with the kernel or build.prop and/or system.prop?
If nothing, then please give me a guide on how to completely reset everything to 100% stock. (I don't have safe strap, but do have TWRP)
Uzerexample said:
(Running a twrp flashable version of Fire os 4.5.5 https://forum.xda-developers.com/kindle-fire-hdx/development/twrp-flashable-stock-images-t3194914) I used a different port and it stopped rapidly dis/reappearing! It stays connected... but as an unknown USB device (device descriptor request failed) I think I've isolated the problem on the kindle side. Something is making it think it's a different device. When I change the USB configuration in Dev settings, it does nothing. The computer doesn't see any changes, and when I turn off both MTP and PTP no changes were detected on pc and nothing happened on kindle. The MTP and PTP toggles are nothing more than cosmetic buttons. Is something wrong with the kernel or build.prop and/or system.prop?
If nothing, then please give me a guide on how to completely reset everything to 100% stock. (I don't have safe strap, but do have TWRP)
Click to expand...
Click to collapse
Likely not carrying a proper data signal due to damaged usb interface or (wait for it...) crappy cables or other hardware issues previously identified. There is no easy path to 100% stock. Highly unlikely any *.prop is involved. Can device be 'seen' while booted into TWRP? Me thinks not which exonerates the .props.
Heck Yeah!
I have the same problem, everything was working fine, until i've managed to unlocked the bootloader, it was a disaster, it charges so very slow and it doesn't recognize my pc anymore, still searching for solutions, anyways this better than a bricked KFH.
ChickenKyrie said:
I have the same problem, everything was working fine, until i've managed to unlocked the bootloader, it was a disaster, it charges so very slow and it doesn't recognize my pc anymore, still searching for solutions, anyways this better than a bricked KFH.
Click to expand...
Click to collapse
https://forum.xda-developers.com/kindle-fire-hdx/help/thor-recognized-windows-t3812047/post77082565
Good Morning Ladies and Gents;
I am working with an LG G4 H811 (T-Mobile) on 20v (MM 6.0), which I would like to root. I have unlocked the bootloader, which is confirmed every time I start the phone. I then tried to root using LGUP, but the phone wasn't recognized, so I did an error recovery reinstall in LG Bridge, thinking a fresh software install would re-align things.
Now, whenever I connect the phone to the computer, I get a pop-up window on the phone saying "USB Connection - Allow this computer to access your phone data?" CANCEL/ALLOW and the phone does not show up on the PC screen or in Device Drivers until I tap "ALLOW". Therefore, it is not recognized by any software without tapping ALLOW.
More than an inconvenience, this effectively prevents me from any mods on the phone, because I need to shut off the phone and disconnect from the USB port, then reconnect with Volume UP pressed to get to download, and in download mode I have no access to ALLOW the USB connection, so neither ADB nor FastBoot recognize any devices, and the phone is not included in Device Manager.
Of course, the bootloader is unlocked, Developer Options enabled, OEM Unlock on, USB Debugging on. I am using an original LG USB cable. I have tried 4 different computers and three different sets of drivers. I've tried older drivers on older and newer computers, and vice-versa, for every combination available. Each time, I plug in the phone after a fresh computer install and let it install it's own drivers. Two of the computers are Windows 7, two are Windows 10. I've tried connecting in MTP mode and PTP mode, with no difference. I've removed the SD card in case it was affecting things, and done a factory reset on the phone. Auto Play options have been set on the PC to "Do Nothing". I've searched the internet and this forum without results.
Basically, I've spent two days on this before asking for help. Has anyone else had this experience and solved it with something other than drivers? I think I've just about run out of ideas! Thanks.
I don't root however it's probably Developer options>usb default settings>usb tethering
Try connecting directly from Disk Management on the PC. Use the scan for new drives option if it's not visible.
Thanks buddy, appreciate you trying to help out.
Tethering is a way to allow a device connected to your phone to use the phone's data connections. In the tethering instructions:
"You may not be able to access the data files stored in the phone's memory, such as pictures, music etc, or transfer such files between your phone and your PC when USB tethering is on"
However, its worth a try - so I set up tethering, unplugged the phone and plugged it in again - the same Cancel/Allow screen came up, and no device in DM until I tapped Allow.
I then opened Disk Management and plugged in the phone. I still get the Cancel/Allow screen, and rescanning devices didn't show anything new, because the phone is not in the Device Manager until I tap Allow.
The key here is finding out why the phone or computer do not store the "Allow" command. Normally, the phone will show this screen the first time you plug it into a computer, and when you tap Allow, it will store that someplace such that the phone and computer are recognized as safe devices. You should never have to see the permission screen again. My challenge is that I don't know where that permission is stored - is it on the phone, the computer, attached to the driver? Don't know. And I don't know why it's not being saved. If I had those answers, I could probably edit the registry (or whatever) to make this a permanent attachment.
Thanks!
You're welcome.
Maybe debug mode?
Try turning off Developer options.
Obviously there is a way, sorry but I never had to use that function.
Try some Google searches which is how I usually find answers and/or by just playing with it
Well, I wouldn't be able to communicate via ADB with Developer Options off. And I spent two days searching the internet before coming here, and all I found was people updating their drivers, which is why I tried so many combinations of Windows versions and drivers versions.
I'm actually kind of surprised that this seems to be such a unique problem, I was hoping someone would notice the post who had actually had a similar problem and fixed it. But I do appreciate you trying to help!
Sorry I can't help, but I never choose to root.
It's time sucking black holes like this that I deliberately want to avoid.
At least you didn't brick it...
ha ha... you got that exactly right! Every time I do this I end up spending DAYS trying to get up to date on everything that has changed since my last phone!
Well, I appreciate you taking time to try to help.
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?