I don't believe there was a thread covering this exact issue, if there is I sincerely apologize. AT&T Samsung Galaxy S III Mini SM-G730A
My problem is that my phone will not connect to any computer via USB mass storage, the battery will begin to charge but that is all. I have searched the internet for possible reasons/solutions and I have also contacted Samsung customer service which only lead to the discovery of completely different issue. Of course upon this discovery as coincidence would have it the call with customer service was disconnected. The lady had told me to boot the phone, take the battery out, and boot into recovery mode. Once there she instructed that I choose the option to wipe the cache partition, when I selected this option it said it was clearing the partition then gave me an "ERROR" message, shut down, and rebooted the phone. Basically, to get to the point, I wanted to root the phone and this problem is somewhat a hindrance. Any help or suggestions would be greatly appreciated. Thanks in advance
Also I don't know if this needed or would help but I have tried connecting it to computers running Win XP Home Service Pack 2, Win Vista, Win 7 Home Edition, and on my laptop which is the one I would be using if fixed it's running Ubuntu Saucy 13.10. I also used the original cable that came with the phone I bought it brand new. Thanks again.
Possible reason of your problem
pwnerize_me_cap'n said:
I don't believe there was a thread covering this exact issue, if there is I sincerely apologize. AT&T Samsung Galaxy S III Mini SM-G730A
My problem is that my phone will not connect to any computer via USB mass storage, the battery will begin to charge but that is all. I have searched the internet for possible reasons/solutions and I have also contacted Samsung customer service which only lead to the discovery of completely different issue. Of course upon this discovery as coincidence would have it the call with customer service was disconnected. The lady had told me to boot the phone, take the battery out, and boot into recovery mode. Once there she instructed that I choose the option to wipe the cache partition, when I selected this option it said it was clearing the partition then gave me an "ERROR" message, shut down, and rebooted the phone. Basically, to get to the point, I wanted to root the phone and this problem is somewhat a hindrance. Any help or suggestions would be greatly appreciated. Thanks in advance
Also I don't know if this needed or would help but I have tried connecting it to computers running Win XP Home Service Pack 2, Win Vista, Win 7 Home Edition, and on my laptop which is the one I would be using if fixed it's running Ubuntu Saucy 13.10. I also used the original cable that came with the phone I bought it brand new. Thanks again.
Click to expand...
Click to collapse
Your problem if you still hve it is that the usb port is damaged, normally when they get damaged they can still charge the phone but will not be recogniced by the pc, so you would not be able to rooted, or transfer any file to it, .
Solution is to change the usb port. Hopefully you can fix your issue, Greetings.
Try enabling / disabling usb debugging, maybe that will help. You'll need to go to 'about phone' in settings then tap on the version number 10 times to enable developer options, then you can enable usb debugging.
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
gear live 5.0 lollipop connection issues
jay slasher said:
So I've got a new Samsung Gear Live from the Play Store. I'm attempting to pair the device to a Nexus 5 running stock 4.4.4.
When I turn on the Gear Live I'm prompted with selecting a language. I choose English US. Then i'm taken to the "Install Android Wear on your phone" Screen
At first this screen would show me the text "Gear Live 4AFV" (or something along those lines). However 9/10 (after rebooting or resetting the watch) it will simply show me "Gear Live" no 4 digit name.
Without the 4 digits showing the phone will not detect the bluetooth device to connect. On the off chance that it does show up and the phone is able to detect the watch, the pairing process can either work, or stall leaving both devices sitting at a "wait a moment while pairing" screen that never ends.
Lastly, if everything works and i'm able to pair the watch and phone. it will randomly disconnect and nothing I do will make it reconnect to one another.
Other things to note. Bluetooth has no issues on my phone with any other device.
I've reset the watch numerous times,
I've uninstalled the Android Wear app as well as any other watchfaces or launchers.
I've factory reset the phone.
Suffice it to say i'm almost certain there is a problem with the watch, the question is has anyone else experience this or anything similar with a Reset hasn't fixed the problem and is there possibly a solution to this problem that isn't a replacement.
Google has offered to replace the watch but I want to ensure I"m not missing something here.
thanks for any assistance in advance.
Click to expand...
Click to collapse
I have the same connection issue but not until I updated it to Android version 5.0 that I started to get connection issues and the gear live was constantly doing a sync loop and it would not stay connected or send SMS messages.
Hello all,
I need some help. So a family member of mine was recently handed a Samsung Galaxy S Advance to use and it was my intention to see if it were possible to unlock the phone (from Orange UK) allowing her to use her own network on the Samsung. Now I've rooted android tablets a good few times and it's been a breeze but this phone as proven to be a nightmare all day. Basically I decided to use Odin3 to give the phone a clean standard firmware for me to start with (2.3.6) and Odin went fine, in the end it informed me that it had past and I thought everything was okay. But now the device won't start up at all or charge, the only thing that appears to get a response out of it is if I connect the USB cable, disconnect the battery then my PC will inform me of a connection noise and then it suddenly disconnected seconds later. Have I done something wrong here?
Unfortuantly I can't access recovery or download without the screen even turning on. I'd greatly appreciate some help. Thanks.
Hi,
sorry to say but your device is fully bricked.
What you hear when connecting it to your computer is the IROM software or the device probing to see if there is the correct server to connect to.
You need the libusb drivers correctly setup for you computer to recognize the device in this mode, but that is not enough, you need the correct software to talk to the device too.
Some times ago, I have managed to setup such a server (I got the software sources from someone here who gave it to the community) and talk to the device in this mode but never had enough time to experiment with it to send a minimal bootloader (documentation provided with the software is very minimal and somehow "cryptic").
Nobody here ever tried to build up on my searches, having no more time to play with this + this phone starting to be really outdated, I gave up.
Regards
Around February, my phone was working fine and connecting to my PC and being recognised (in both the phone AND PC/Device Manager). Because I was rooted, I used Wug's toolkit to flash the latest factory image at the time (which included the February security update) and kept data as I've done in the past. It was fine for ~2 weeks after that factory image flash and then my phone just stopped recognising the PC, and my PC stopped recognising the phone as a device. It was completely out of the blue, and seems unfixable.
When I plug my phone into my Desktop - it just charges. It doesn't appear in the device manager at all (image below - Device manager WITH phone plugged in and not appearing):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've had to do the old 'update drivers' thing in the past with other phones, but they would normally appear under "Phone" or "Other devices" - but both are missing from the list ("Show hidden devices" used in that image). There's also no yellow triangle to say an unknown device has been connected. It just flat out doesn't know it's there. I've also updated/re-downloaded the SDK (and Google drivers) but the phone still isn't recognised.
It got so bad, I had to use USBDeview to uninstall the drivers in the first place because they never appeared. It still didn't help.
On the phone side of things - I'm not given an option to mount the phone as any form of storage. It just behaves like I've plugged it into a charger.
In the USB and Storage settings (image below) - I'm not given an option for ANY form of USB connection.
And in the notification shade (again, while plugged into my PC) no option is given. It just charges:
I've also tried factory resetting the phone, since it charges fine so I don't think it's the charging port but now I've lost root AND the problem is still there. I still can't install OTA updates because in order to get Root, I had to use a kernel which disabled those "this device has been modified" alerts when you boot it, which means the OTA just fails (Error 7 (or 6) - and something about recovery).
In Fastboot, it just says it's 'charging' and makes no attempt to connect via USB. Recovery is the same so it doesn't sound like an Android problem per-se since it affects Fastboot but hardware wise - would could it be?
As a last resort, I've also tried multiple cables (working one for the Nexus 7, DS4 one and a Motorola one) and none of them seem to have helped.
I've also tried different USB ports and on different machines - both running windows 10 and both with the drivers installed but still no luck.
Any help would be greatly appreciated because I'm just sick of this problem at this point.
Zenamez said:
I'm just sick of this problem at this point.
Click to expand...
Click to collapse
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
NLBeev said:
You've tried a lot.
My idea is to try to connect to another PC, when possible not Windows 10.
This to check that the problem isn't caused by the phone.
Click to expand...
Click to collapse
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Zenamez said:
That's a very good point. Pretty glad one of my PCs didn't like the 10 upgrade and is still on 7.
I'll try it when I get home. Thanks for the reply!
Click to expand...
Click to collapse
Wish you luck.
W10-updates are causing issues on my PC
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Strephon Alkhalikoi said:
If changing PCs doesn't help, try a different cable. If that still doesn't work, you likely have a problem with the micro USB port.
Click to expand...
Click to collapse
Tried 3 different USB cables and no luck.
I've got a spare microUSB I bought from eBay which I'll need to solder but the only thing I could find on faulty ports were that it doesn't charge right but mine does.
Going to try connecting it to a windows 7 laptop and see where that goes. If it still doesn't work - the only thing left would be the port itself which will be a pain to replace (and still doesn't guarantee it'll be fixed).
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
electricpete1 said:
Maybe to rule out pc, find a buddy with android phone and see whether you can detect it with adb or fastboot on your pc. I think those drivers are supposed to be universal (all phones)....aren't they?
Click to expand...
Click to collapse
Tried it on my Windows 10 laptop as well and it's the same problem. Just tried it on my older Windows 7 laptop as well, and same story.
My older Nexus 7 2012 connects fine to all 3 so I don't think it's the drivers.
Dvoraak said:
I've had the same thing happen to me twice. I think that some times Windows updates and kills the drivers. Whenever it's happened to me I've installed a universal adb driver that's floating around XDA. Once that alone fixed the issue. Once it didn't. The time it didn't I had to open every device heading in the device manager until I found one that had Google hidden inside it. I uninstalled the Google driver from there in the device manager and then plugged my phone in. Windows did the normal device install from the phone and all was fixed. Hope that helps. Good luck. Windows 10 truly sucks.
Click to expand...
Click to collapse
Sadly already tried this but what's worse is - I've looked through all the possible 'dropdown' options and the drivers/device doesn't appear but it appears in USB Deview (where I uninstalled them).
Tried both the universal ADB driver and Google's own one from the SDK - sadly didn't work in the end.
Dopamin3 said:
Honestly it sounds like a hardware issue with the MicroUSB port. I can confirm it works fine under my Windows 10 PC at home, both normal access for files and I've also had no issues with using fastboot or ADB. If it's under warranty try to RMA it. If it's out of warranty see how much it would cost to change the MicroUSB port from a local shop or try it yourself
Click to expand...
Click to collapse
I'm beginning to think the same to be honest. It doesn't connect in Fastboot, which leads me to believe it's more hardware than software because if it were Android itself screwing up - it would at least work in Fastboot as that doesn't touch Android.
It doesn't mount as anything, so I can't access my files on any of the systems I've tried. I've even tried my younger brother's laptop and it doesn't 'see' it (but his Nexus 4 connects and works just fine).
I bought my Nexus 6 ~6 months after release so it's out of warranty (what a time for it to run out of warranty). I bought a new USB port from eBay ages back so I might have to fit it myself since all the repair shops I've contacted would take ~3 days to do it and I need to have a phone.
I really hope replacing the port will fix it. It charges fine, which makes me slightly worried it won't work (as it's not an obvious port issue) but I can't think of anything else which could be the problem.
Thanks to everyone who's replied though! I'll see how the USB replacement works out.
Hello all, long time lurker 1st time poster....
I've never really felt the need to post because i normally just do a search and work things out for myself, but i'm now having the same problem and noticed this around 2-3 weeks ago after trying to copy some pictures i'd taken onto my Laptop from my Nexus 6 and it not being recognised, only charging.
I've tried EVERYTHING (apart from reverting back to Windows 7) mentioned in this thread and in a couple of the other threads i've found where a few Nexus 6 users have had the same problem. I'm now stumped for ideas.
My Nexus 6 runs as flawlessly as usual, no battery drainage, stutters etc.
I'm currently running Temasek's 18.2 (5.1.1) rom, and have been using it now for a long time (probably for 8 months or so with absolutely no problems whatsoever). I've updated to MM a few times and tried a few different Roms, but to be honest i just found that LP worked better for me so have always just reverted back to the last official LP 5.1.1 LVY48I Rom using Wugfresh's Tool Kit (i know i know , but having rooted/played about with other Samsung/HTC Phones in the past, i just preferred to use it) and then restoring my backed up reliable Temasek's 18.2 Rom.
So, what else can i say....well, i called Motorola around a week ago for some advice, just incase there is a potential warranty claim (because my Nexus 6 is only around 9 months old), but as i have a Custom Rom on it, they said that there is nothing that they can do.
I do have an official clean 5.1.1 Rom LMY48M that i fortunately backed up to my TWRP Folder on my laptop just after installing TWRP+rooting. I did 1st of all also try connecting my Sandisk Ultra Dual USB DRIVE 3.0 to my Nexus with the Rom on there, but the Nexus just doesn't even know that the USB Drive is connected, so I have had to send it via bluetooth to my Nexus from my laptop, as that was the only way to get it on there. I found that Zipping the file 1st, sending it to my Nexus via Bluetooth and then extracting it once i'd received it saved hours in time because the file was too large in its original form (something like 4+gb down to 1.9gb). I've also tried a few other LP Rom's in the last couple of weeks, hoping that maybe i'd accidentally switched a setting off or something and that the phone would correct itself and my connection problem would correct itself but i've had no joy.
NOW...........................probably a silly question but it's the only other way i can think of returning to Stock for a potential warranty claim. I know that i can install the official 5.1.1 Rom i backed up via TWRP because i've tried, but is there a way to remove Root+TWRP and return to Stock Recovery+remove root without using a PC ? I'm pretty sure that there isn't but feel the time is right for me to ask the Question as i'm really not 100% sure.
Many Thanks in advance for helpful advice given, like i've said at the start of this post, i've held off asking Questions before because i had no real need and just searched :angel: , but this has really stumped me .
CHEERS
Some quick thoughts.
1. The Motorola rep you spoke to I think read from a script and didn't realize you were talking about the Nexus 6. As this is a developer device, having custom software on it should make no difference for warranty purposes. If I am mistaken however, read on.
2. If you're going to install a stock ROM on the Nexus 6, a PC will be required, especially if needing to replace TWRP with the stock recovery. So why not download the latest Android 6.0.1 image from Google's Nexus firmware page and flash that? There's no point in reverting to an Android 5.x image simply for a warranty claim.
Many thanks Strephon Alkhalikoi for your quick reply and sorry for my slow 1 (work was getting in the way....)
1 - at some point today, i hope to chase my potential problem up with Motorola or possibly Expansys because i purchased the Nexus 6 from them via Play.com/Rakuten.co.uk
2 - The 5.1.1 Stock image that was going to be put on the Nexus was only a normal TWRP back up i'd saved by chance straight after flashing+rooting that i had saved to my Laptop. There is no way for me to flash any new Stock software because my Nexus is just not recognised by my Laptop. I've tried installing+uninstalling drivers/Minimal ADB Fastboot file/Wugfresh's Toolkit, plus Developer options usb debugging on/off etc and Settings/Storage/USB Connection (3 little dots top right) which gives me 2 options Media Device (MTP) + Camera (PTP) but after changing either, still no sign of connection, just charging.
As it stands it works fine on 5.1.1, but with me not being able to Flash any Stock Roms because of my Laptop connection issue, it will be forever more on LP. I could put up with that but obviously i need to try and sort this out also because i can't transfer normally any media files backwards/forwards (only via the much slower Bluetooth) and it will affect any future sell on value when it's time to move on.
Many Thanks once again
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
qprjim said:
**Latest Update** for those not asleep yet....
i spent nearly 20 minutes on the phone around an hour or so ago explaining my problem to Motorola. It's not something they've heard of before so couldn't really help and that by being Rooted, their repair center will not touch it. I can only think that if i'd purchased the Nexus 6 straight from Google, it would not have been such a problem to handle a Rooted device so it would have been taken in for repair i'm guessing.
It was explained to me that i would be contacted via email once a technician had been consulted and here is the reply i received a little while ago.
"Thank you for contacting Motorola.
As promised, I have spoken to a technician who has a couple of suggestions.
A. As we discussed, he also suggested connecting your phone to another computer.
B. Be sure that you have Windows Media Player and the PS Drivers installed on your laptop.
[link removed due to my lack of XDA posts]
C.
At this point, I would like to suggest that you restart your phone on Safe Mode.
Safe Mode puts a phone in a diagnostic state and it can help us determine if a third-party app is causing the device to malfunction (freeze/reboot/run slow/error message). Safe Mode temporarily disables all applications that have been installed via the Google Play store. Performing this troubleshooting step is necessary to determine whether a third-party app is the cause of the issue you are experiencing.
Please long press the power button > long tap on power off > reboot to safe mode >ok.
If you find that the issue is resolved in Safe Mode, please delete all apps from the phone, and gradually add them back one or two at a time, until you are able to identify which is causing the sound issue.
To move phone from Safe Mode back to normal mode, you can simply restart it.
D.
To be sure if the problem is software or the port itself:
1. Reboot phone in Fastboot Mode
2. Plus phone into computer
3. If phone is recognised as 'Fastboot Shamu NS,' the issue is software, rather than a physical issue.
In this case, you would need to reset the phone, which I know you are hesitant to do, but you should then be able to reflash the factory images, available on the Google website.
Unfortunately, there little else that we are able to do to help you since, as discussed over the phone, SBE UK, our repair, centre will not accept a rooted device.
For any further assistance or information please do not hesitate to contact us, quoting your Customer Reference number. We are reachable on 03339 997 550 to discuss the matter further with one of our experienced customer service agents. Please contact us any time between the hours of 8am and 8pm from Monday to Friday.
Kind regards,
Anna
Motorola Mobility UK Ltd.
[another link removed] "
I've tried all of the above (apart from connecting to another PC) and still no joy so it looks like i'm stuck on LP. Like i've said before, it still works as normal so no real hardship apart from the lack of Software updates and the normal easier transferring of media files. I'll keep an eye out on this and the other threads to see if a solution becomes available.
*I've posted the above it as it might help someone else out in the future*
Click to expand...
Click to collapse
SBE repaired my nexus 5, when it was rooted/unlocked.
Is there any damage to the usb port? Never tell the customer service rep that your device.
Cheers for the reply JonesL
As far as I'm aware, there isn't any damage to the USB Port. I did say I thought that that might be the problem but she said if it was the reason, then the phone wouldn't charge at all.
I could still send it in and hope that on the off chance they don't check for Root, but i will be liable for the postal returns plus the hassle of being without a mobile whilst it is away. Also, I've now given my IMEI number and a couple of other details so I'm sure I'll now flag up on their system when its checked.
Oh well....
Hello everyone,
Just go a LG-W280A online (Nougat, 7.1.1, NQF43E) and trying to get it to update to Oreo, but no luck so far.
The watch does download the update, but when it comes to install it, it fails verification it seems. I've been through the process at least 5 times already, with a factory reset of the watch in the middle.
Anybody else in Canada have this problem? Is Oreo worth it? If it breaks Google Pay, no, and it's the main reason I bought the watch.
Any help or tips would be appreciated.
Well, it seems patience is the key. I left my phone and my watch charging one beside the other for a few hours. I went to check if an update was available, and was greeted with the "Reboot to install?" prompt.
It took 4-5 times.
I'd say if you come across the same problem, just keep at it. It will work.
MoussePad said:
Hello everyone,
Just go a LG-W280A online (Nougat, 7.1.1, NQF43E) and trying to get it to update to Oreo, but no luck so far.
The watch does download the update, but when it comes to install it, it fails verification it seems. I've been through the process at least 5 times already, with a factory reset of the watch in the middle.
Anybody else in Canada have this problem? Is Oreo worth it? If it breaks Google Pay, no, and it's the main reason I bought the watch.
Any help or tips would be appreciated.
Click to expand...
Click to collapse
I'm from italy...same problem...4 time i download the update (780 MB transferred from bluetooth to watch everey time...oh my god! ), every time the update doesn't pass the verification.
i try this night with a vpn centered in USA.
Hello again,
@stefal639 I assume that it will do the same as mine. Just keep at it, the update will work eventually.
I can confirm that Google Pay in Canada still works after the Oreo update (Wear OS 1.2, 8.0.0, OWDL.180126.012).
I solve shutting off the Bluetooth and I use the direct download from server to watch by wifi.
All ok