Just a PSA, Verizon confirmed to me this morning that the 6.0 rollout has been put on hold, again, for any newly activated Turbo 2's. Had to get a warranty replacement, came with 5.1.1, wouldn't update to 6.0. Called Verizon and they "found" an alert in the system confirming the update was being withheld to new devices as of March 28. There was not an ETA for when the rollout would resume. Sad, but true. My original device was running 6.0 like a champ, so I have no idea what "issues" they discovered that caused them to put this on pause again.
sdsurferbob said:
Just a PSA, Verizon confirmed to me this morning that the 6.0 rollout has been put on hold, again, for any newly activated Turbo 2's. Had to get a warranty replacement, came with 5.1.1, wouldn't update to 6.0. Called Verizon and they "found" an alert in the system confirming the update was being withheld to new devices as of March 28. There was not an ETA for when the rollout would resume. Sad, but true. My original device was running 6.0 like a champ, so I have no idea what "issues" they discovered that caused them to put this on pause again.
Click to expand...
Click to collapse
Just got my Turbo 2 yesterday and it also came with 5.1.1 installed and would not update to 6.0, so I installed the 6.0 firmware myself using rsd lite version 6.2.4. I got the firmware from this link: http://forum.xda-developers.com/droid-turbo-2/general/kinzie-stock-firmware-moto-x-force-t3279354
Hope this helps.
Thanks
Sent from my XT1585 using XDA-Developers mobile app
classic757 said:
Just got my Turbo 2 yesterday and it also came with 5.1.1 installed and would not update to 6.0, so I installed the 6.0 firmware myself using rsd lite version 6.2.4. I got the firmware from this link: http://forum.xda-developers.com/droid-turbo-2/general/kinzie-stock-firmware-moto-x-force-t3279354
Hope this helps.
Click to expand...
Click to collapse
I have been trying to do this (same situation as you essentially) but I cannot for the life of me get RSD Lite to recognize my phone. Even with latest drivers and version of RSD etc installed. Did you face any similar issues or have any solution tips?
Yachter99 said:
I have been trying to do this (same situation as you essentially) but I cannot for the life of me get RSD Lite to recognize my phone. Even with latest drivers and version of RSD etc installed. Did you face any similar issues or have any solution tips?
Click to expand...
Click to collapse
I am on Windows 10 64 bit PC. At first rsd lite would not flash the firmware. After unsuccessfully trying many times I opened a command prompt in the fastboot folder with my phone plugged in to my pc but the phone not in fastboot mode just turned on and plugged in. When I got the "allow usb debugging rsa key" popup I clicked okay and then put my phone in fastboot mode, opened up rsd lite and everything flashed fine.
Can you elaborate on " opened a command prompt in the fastboot folder"? thanks
I have found small bugs here and there but nothing that would make me regret updating. Can't figure out why they did this.
sdsurferbob said:
Can you elaborate on " opened a command prompt in the fastboot folder"? thanks
Click to expand...
Click to collapse
Okay, if you have adb installed on your pc you should have an adb folder on your pc. In that folder should be another folder called "platform-tools". Open that folder and then hold the shift key on your pc and at the same time right click in an empty space and you should get a pop up menu. Look for "open command window here". Plug your phone into the pc and then in the command window type "adb devices". You should see your device serial number and model in the command window. You should get a pop up window on your phone that says something to the effect of "allow usb debugging rsa key" Click okay or allow. (make sure you have usb debugging on in developer options setting on your phone). Then unplug your phone from the pc and put the phone in fastboot mode. (volume down and power button at the same time) Open rsd lite and click the xml file (it will say service file) in the firmware folder. Then click start on rsd lite. The firmware should flash. Let it run its' course and do not unplug the phone during the flashing process. After the firmware flashes it will reboot on its' own.
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
bigv5150 said:
I have found small bugs here and there but nothing that would make me regret updating. Can't figure out why they did this.
Click to expand...
Click to collapse
What small bugs? So far after just a day or two on 6.0 I haven't had any problems. Just curious as to what glitches you have found with it.
Thanks.
I updated to 6.0 by using the verizon update assistant. Im running a windows 10 laptop. You have to use a usb 2.0 port on your computer. For some reason the verizon software won't reconize your phone when using a 3.0 usb port, although your computer will. ok, install the verizon assistant, plug in your tb2 to a 2.o usb port, manually open the verizon assistant on your pc. follow all on screen instructions. It took me like 30 minutes to upgrade from 5.11 to 6.0. I just did the update today. 4/10/16. I got the tb2 on 4/01/2016.
bossplayer24 said:
I updated to 6.0 by using the verizon update assistant. Im running a windows 10 laptop. You have to use a usb 2.0 port on your computer. For some reason the verizon software won't reconize your phone when using a 3.0 usb port, although your computer will. ok, install the verizon assistant, plug in your tb2 to a 2.o usb port, manually open the verizon assistant on your pc. follow all on screen instructions. It took me like 30 minutes to upgrade from 5.11 to 6.0. I just did the update today. 4/10/16. I got the tb2 on 4/01/2016.
Click to expand...
Click to collapse
Is that "Update Assistant" the same thing as the Motorola Device Manager? And I'm assuming this method of updating doesn't wipe data?
classic757 said:
Okay, if you have adb installed on your pc you should have an adb folder on your pc. In that folder should be another folder called "platform-tools". Open that folder and then hold the shift key on your pc and at the same time right click in an empty space and you should get a pop up menu. Look for "open command window here". Plug your phone into the pc and then in the command window type "adb devices". You should see your device serial number and model in the command window. You should get a pop up window on your phone that says something to the effect of "allow usb debugging rsa key" Click okay or allow. (make sure you have usb debugging on in developer options setting on your phone). Then unplug your phone from the pc and put the phone in fastboot mode. (volume down and power button at the same time) Open rsd lite and click the xml file (it will say service file) in the firmware folder. Then click start on rsd lite. The firmware should flash. Let it run its' course and do not unplug the phone during the flashing process. After the firmware flashes it will reboot on its' own.
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
What small bugs? So far after just a day or two on 6.0 I haven't had any problems. Just curious as to what glitches you have found with it.
Thanks.
Click to expand...
Click to collapse
It's not 6.0.1 it's 6.0 the bugs I have seen are the recent app draw when I try to open an app it doesn't open on occasion. Also if I'm in landscape mode in the recent app draw it won't auto rotate again on occasion. Nothing major just small bugs
bigv5150 said:
It's not 6.0.1 it's 6.0 the bugs I have seen are the recent app draw when I try to open an app it doesn't open on occasion. Also if I'm in landscape mode in the recent app draw it won't auto rotate again on occasion. Nothing major just small bugs[/QUOTE)]
Nope, I didn't say 6.0.1. I mentioned in 6.0 I(meaning me) have't had any problems.
Anyway, thanks for your response.
Click to expand...
Click to collapse
classic757 said:
bigv5150 said:
It's not 6.0.1 it's 6.0 the bugs I have seen are the recent app draw when I try to open an app it doesn't open on occasion. Also if I'm in landscape mode in the recent app draw it won't auto rotate again on occasion. Nothing major just small bugs[/QUOTE)]
Nope, I didn't say 6.0.1. I mentioned in 6.0 I(meaning me) have't had any problems.
Anyway, thanks for your response.
Click to expand...
Click to collapse
My bad just saw that sucks getting old eye site is going :crying:
Click to expand...
Click to collapse
bigv5150 said:
classic757 said:
My bad just saw that sucks getting old eye site is going :crying:
Click to expand...
Click to collapse
Believe me I understand.
Click to expand...
Click to collapse
Where did you find the update assistant? I know it's supposed to be built in to the phone, so that when you plug it into a computer you get the option to install, but on both of my computers it doesn't do anything.
bossplayer24 said:
I updated to 6.0 by using the verizon update assistant. Im running a windows 10 laptop. You have to use a usb 2.0 port on your computer. For some reason the verizon software won't reconize your phone when using a 3.0 usb port, although your computer will. ok, install the verizon assistant, plug in your tb2 to a 2.o usb port, manually open the verizon assistant on your pc. follow all on screen instructions. It took me like 30 minutes to upgrade from 5.11 to 6.0. I just did the update today. 4/10/16. I got the tb2 on 4/01/2016.
Click to expand...
Click to collapse
classic757 said:
I am on Windows 10 64 bit PC. At first rsd lite would not flash the firmware. After unsuccessfully trying many times I opened a command prompt in the fastboot folder with my phone plugged in to my pc but the phone not in fastboot mode just turned on and plugged in. When I got the "allow usb debugging rsa key" popup I clicked okay and then put my phone in fastboot mode, opened up rsd lite and everything flashed fine.
Click to expand...
Click to collapse
I am running the same setup as you, but after following your steps RSD still does not recognize my phone while in fastboot mode. I am using usb 3.0 ports though, if that makes a difference. Thanks
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
sdsurferbob said:
Where did you find the update assistant? I know it's supposed to be built in to the phone, so that when you plug it into a computer you get the option to install, but on both of my computers it doesn't do anything.
Click to expand...
Click to collapse
When i try to install VZ Assistant on my laptop using a usb 3.0 port it will not install at all. It just closes the install window and nothing else happens. Should i install it using a usb 2.0 port? I've tried multiple computers. Do you have a link to manually install the assistant app without plugging in your dt2? Thanks.
dbroadus2007 said:
I am running the same setup as you, but after following your steps RSD still does not recognize my phone while in fastboot mode. I am using usb 3.0 ports though, if that makes a difference. Thanks
---------- Post added at 08:46 PM ---------- Previous post was at 08:43 PM ----------
When i try to install VZ Assistant on my laptop using a usb 3.0 port it will not install at all. It just closes the install window and nothing else happens. Should i install it using a usb 2.0 port? I've tried multiple computers. Do you have a link to manually install the assistant app without plugging in your dt2? Thanks.
Click to expand...
Click to collapse
You need to use 2.0 ports. 3.0 ports cause problems with fastboot.
classic757 said:
You need to use 2.0 ports. 3.0 ports cause problems with fastboot.
Click to expand...
Click to collapse
I see. Well I'll have to find a PC with USB 2.0 ports, as my XPS 13 only has 3.0. Thanks for the advice.
Yachter99 said:
Is that "Update Assistant" the same thing as the Motorola Device Manager? And I'm assuming this method of updating doesn't wipe data?
Click to expand...
Click to collapse
Found it here: http://www.motorola.com/VerizonSoftwareUpdateWin
This Worked On USB 2.0
classic757 said:
I am on Windows 10 64 bit PC. At first rsd lite would not flash the firmware. After unsuccessfully trying many times I opened a command prompt in the fastboot folder with my phone plugged in to my pc but the phone not in fastboot mode just turned on and plugged in. When I got the "allow usb debugging rsa key" popup I clicked okay and then put my phone in fastboot mode, opened up rsd lite and everything flashed fine.
Click to expand...
Click to collapse
I had issues with RSD lite not seeing my phone plugged in. I did all of the steps using a USB 2.0 port, and all flashed perfectly the first time. We may want to share this in the main thread or something. I am letting the apps upgrade on first boot, and will report back.
Related
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Hakizi said:
I fought with this for ages today. To start with, I have the Wugfresh Nexus Root Toolkit installed. Now, when in bootloader, go to the device manager on your computer. Find the Pixel ("Unknown Device") and right click > Properties > Driver tab > Update Drivers > Browse Computer > Choose From List > WugFresh Development\Nexus Root Toolkit\data\Drivers > and pick the one that says something about the bootloader. Sorry, going off memory here. Now you should be able to get that one installed, and Fastboot will start showing up when in the bootloader.
Click to expand...
Click to collapse
I did the same : Choose from List >fastboot (I didn't install Wug)
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
This is what worked for me....
http://forum.xda-developers.com/showpost.php?p=64777133&postcount=96
jamgam said:
Ok. I can't get fastboot to work. WIndows 10 laptop. Disabled driver verification. ADB works fine and reboots into bootloader but once in bootloader no fastboot. I've got an "Unknown Device" in Other Devices in Device manager and I've tried to assign the google driver manually but it's not recognized as a driver for the device
I've removed and reinstalled drivers pre and post driver verification
I tried adding PIxel C lines to the driver INF file as instructed on stack overflow
I don't know what else to try. And i've tried on two different computers???
Help please.. thanks
Click to expand...
Click to collapse
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
@Istvan_86,
We should move the discussion for your problem here.
cam30era said:
@Istvan_86,
We should move the discussion for your problem here.
Click to expand...
Click to collapse
Hello,
I don't see any link and sorry if I made too many posts.
Istvan_86 said:
Hello,
I don't see any link and sorry if I made too many posts.
Click to expand...
Click to collapse
That's OK. No problem. Did you try the steps in post #5 above?
Which operating system are you on? What worked for me on Windows 10 was to give up after several days and use a Windows 7 computer. I read everything and tried everything and I could not get Fastboot working on this device with Windows 10. I used every toolkit, every driver version, toolkits that install multiple driver versions, Minimal ADB + Fastboot, and who knows what else. If a well-documented end-to-end solution to this ever appears I'll be really grateful.
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
cam30era said:
That's OK. No problem. Did you try the steps in post #5 above?
Click to expand...
Click to collapse
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Istvan_86 said:
Thanks for point me here, yo offer me too much help.
Now I´m on Nougat working flawlessly.
Really, really, really thanks. I have the exact same issue and this solved it for me also.
Cheers!
Click to expand...
Click to collapse
Welcome.
cam30era said:
FWIW, it was my frustrations with this Windows driver nonsense, that eventually drove me to abandon Windows entirely. Been on Ubuntu for several years. No regrets.
Click to expand...
Click to collapse
It's very annoying, there seems to be a few reasons it fails. Cable, 3.0 usb ports, windows 10 drivers. I get different results with different cables in different types of usb ports. Also switching to PTP seems to work using a usb 2.0 port with a standard usb 2.0 A to micro with a micro to c adapter. Charging and MTP fail, but at least ADB and Fastboot respond.
I am going to try to edit the win10 driver using this post as reference.
http://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
---------- Post added at 11:05 PM ---------- Previous post was at 11:04 PM ----------
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
I came to the same conclusion, but after a reboot it was unrecognized again.
Only way I can it to stick is installing the 2nd option drivers via skipsoft toolkit. Connect pixel c via 2.0 port and cable to PC. Switch to ptp. Then manually force install driver choosing have disk using bootloader option. From then on it works using ptp.
What I am able to see using USB Device Tree Viewer, is that when I plug in my Pixel C to my ASUS Z97-A blue usb ports with USB debugging enabled, it can not identify it. Those ports use Microsoft Windows 10 drivers for the Intel USB 3.0 eXensible Host Controller - 1.0. Which is what is causing the failure, not the Pixel C drivers. When I updated my other green USB ports driver, windows used the same ones on my ASMedia USB 3.1 eXtensible Host Controller and also couldn't recognize the Pixel C any longer. I rolled back to ASMedia drivers, it worked fine. Updated using newer ASMedia drivers 4/11/2016 ver 1.16.35.1 and those work fine. Now to find working drivers for the Inter Host. Win7 drivers refuse to load.
UPDATE: If your bios allows, disable xHCI. Your USB ports will work as USB 2.0 but will detect your PIXEL C without issues.
Solution works 100%
If you've installed the SDK drivers and win10 can detect your Pixel C in every mode with usb debugging off. Use these win10 USB xHCi drivers,
http://www.win-raid.com/t834f25-USB-Drivers-original-and-modded.html
@clockcycle,
This solution works 100% too. https://www.ubuntu.com/
CISGS said:
I had the same problem man. This will fix it.
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
Done.
Click to expand...
Click to collapse
Been smashing my face off the wall since LAST NIGHT trying to figure this out. windows 7 machine/ windows 8/ ubuntu ! trying 100 different methods and this one FINALLY SOLVED THE ISSUE. gawd dayum thank you so much from the future !!!
Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!
iamkardde said:
Since the early October update of Nougat's, my Pixel C is not being recognized, or plainly shows up as MTP device and I'm unable to transfer. When in fastboot And adb the PixC's model# Does register. Ive updated Everything incl. WugFresh, Skipsoft and sdks. Please help!
Click to expand...
Click to collapse
Update the drivers on your PC.
Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones
iamkardde said:
Thank you, though have done. Right after i saw reply i found DriverBooster4 and it "updated 13 drivers" but i guess not the right ones
Click to expand...
Click to collapse
You need to do it manually. Google "how to manually update drivers windows 10". Do it via device manager with your Pixel C plugged in.
did do. And also before have tried to "point the update to" sdk and Wug's folders. Am not a total noob, but braincells do die, I cant stop it! If it matters, I did just few days ago clean-"re"install win10 64 but this problem was b4 that.. hence the clean start over. All Im ever getting is MTP USB Device, or wen tab's in fastboot, Android ADB Device. Both say "best is already installed".
also have done the "disable driver enforce", i do that routinely now til this is solved..
iamkardde said:
also have done the "disable driver enforce", i do that routinely now til this is solved..
Click to expand...
Click to collapse
1. Open Device Manager and Select the Unknown Device
2. Select Update Driver
3. Select Browse My Computer
4. Select Let Me Pick From a List of Device Drivers On My Computer
5. Select Android
6. Select Android Bootloader
with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same
iamkardde said:
with plugged in, debug on and mtp on, it showed as portable devices/mtp usb device. it did install successfully (again); reboot using f7 and... nothing, still the same
Click to expand...
Click to collapse
it no longer shows as "unknown".
iamkardde said:
it no longer shows as "unknown".
Click to expand...
Click to collapse
I can b a bit dense, so in case i forget, Thank you for your help!! will probab say this again later..
Thanks to cam30era for the helping!! Problem was simply my misuse of TB. No mystery or MS/Google conspiracy. I went back to stock, re-rooted and Voila!
I am currently on Android Wear 2.0 preview 2. My Huawei watch is not being detected by my PC although I have ADB enabled. In fact, the watch is not even detected as an unknown device in the device manager. I am able to get Bluetooth debugging working. However, since fastboot doesn't detect my device I am unable to flash either a new recovery or upgrade my watch. I am able to enter the fastboot/recovery mode manually by clicking on the button when the huawei logo appears during boot. However, I get an error message saying /sdcard cannot be mounted and am unable to flash any zip file due to this using the Droid recovery. The watch boots up normally and works well otherwise except that i am stuck with the preview 2.0.
Is the issue due to a faulty cable or a badly flashed recovery or is there anything else i can try so that i can revert back to stock or flash a new rom? Any suggestion is greatly appreciated..
I'm having the same issue on two separate watches, and have been for quite some time. Have tried multiple computers, multiple chargers, to no avail... Using stock recovery, preview 2. Watch will charge, no problem, but the PC won't notice that the watch is plugged in in any way no matter fastboot, recovery, or just booted.
same here, watch will charge but no prompt to access interal memory. Is simply stock, so no preview version
Same here. Flashed the 2.0 preview and now can't get ADB through a wired connection. Hoping someone can help.
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
vicvon said:
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
Click to expand...
Click to collapse
I've tried on Mac OS X Sierra and Windows 10.
firefurby said:
I've tried on Mac OS X Sierra and Windows 10.
Click to expand...
Click to collapse
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
vicvon said:
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Yeah, I've tried the Minimal ADB and Fastboot as well as a full install of Android Studio. I'll give this walk through a shot too. I'm desperate.
Anyone have any luck getting their watch to be recognized again?
try pdanet adb drivers
also, sometimes even if fastboot doesn't register as detected, you can still flash anyways
Anyone ever get anywhere with this? I'm still hoping for a solution.
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Hmmm... I'm using a Mac mainly. I'll give this a try on my windows machine later. Thanks!
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
Click to expand...
Click to collapse
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
SirRobin78 said:
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Click to expand...
Click to collapse
mysteray said:
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
Click to expand...
Click to collapse
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Pkt_Lnt said:
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Click to expand...
Click to collapse
mysteray said:
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Click to expand...
Click to collapse
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Tried that, as well. Doesn't make any difference.
Thanks for the suggestion, though.
Pkt_Lnt said:
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Click to expand...
Click to collapse
Same issue here
I'm also having this problem but not on Android Wear 2. I'm using stock, non rooted, and locked bootloader and therefore Android Wear 1.x. I only became aware of this issue when I decided that I wanted to get Android Wear 2 on my watch (using the preview).
The watch charges but in no way can I get my PC to detect that the watch is actually there, tried two Windows 10 PCs but both have the same issue. I think the problem is either with the watch itself or with the charging dock/cable. I rebooted into fastboot mode but this does not make a difference. The fact fastboot also does nothing makes me think its more likely that the charging dock is at fault. Unfortunately, installing ADB/Fastboot drivers is pointless if the PC can't even see the device to communicate with.
Update: 2nd post now has a way to update the Moto G7 without erasing user data. Method uses most of this tutorial but now you unzip image and select a file within in the unzipped image. Either way still backup your phone just in case. User MrCamby let me know about the "Lenovo MOTO Smart Assistant" for backup.
Yesterday I updated my US Retail version Moto G7 Power to the newest firmware build# PPO29.114-108 with the May 1st Security update manually. My previous build with the March 1st security update was PPO29.114-63-2. I have the Retail US Model with 3GB of RAM and 32GB of Storage. DO NOT flash the Moto G7 Power international version with 4gb RAM and 64GB storage, it will probably brick it.
This process will delete everything on the phone as it flashes all the phone's partitions. The phone will be as it was when you first bought it having to re-enter your account info and download all your extra apps not included with the stock phone. Please backup everything if you decide to update the phone using this method. On my phone most things were stored on the cloud but I did forget I had some unimportant things on the phones download folder.
Thanks to user MrCamby for letting me know bout the "Lenovo MOTO Smart Assistant" which will backup the phone on your PC (Windows only) before you flash it. I haven't personally used it but from it's .pdf guide it will backup your phone before you flash it preserving images, SMS, Contacts, etc... Link to Lenovo Moto Smart Assistant
https://support.lenovo.com/us/en/downloads/ds101291
The first step is to download Motorola RSDLite6.2.4.zip software used to flash the firmware file.
The software is available at: https://mirrors.lolinet.com/software/windows/Motorola/RSDLite/6.2.4/
Unzip and Install the RSDLite software and move to step 2.
Step 2 is to download and install the MotorolaDeviceManager_2.5.4.exe Software/Drivers at:
https://mirrors.lolinet.com/software/windows/Motorola/Drivers/
Step 3 is to download the 1.9GB firmware. Be sure the file downloads completely! Flashing an incomplete image could damage the phone. The MD5 checksum is 8bb8f13ec0fe23c977b57c86f2033db9 MD5 Checker attached.
Choose the Firmware dated 2019-06-05 and Named:
XT1955-5_OCEAN_RETUS_9.0_PPO29.114-108_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
https://mirrors.lolinet.com/firmware/moto/ocean/official/RETUS/
With the two pieces of software installed and the firmware downloaded it's time to install the firmware.
Warning this process will completely erase your device and reinstall the new firmware. only attempt this
process if you have a US Retail G7 Power with 3GB RAM and 32GB of storage. Do not interrupt the process
once the flashing has begun or you may have a brick(dead phone). Please continue at your own risk.
1) You'll need a USB C cable and be sure the computer is plugged in to power if a laptop. The phone should have at least a 60% charge.
2) Shut off the phone. Once the phone is completely off, Hold the volume down and press the power button still holding the volume down button.
3) The phone should boot into the boot loader mode, release the power & down volume button. See bootloader.jpg attached to see what screen looks like.
4) Plug the USB C cable into the phone and into a USB 2.0 port(black colored) on your computer. On my computer the phone didn't show up in RSDLite program when plugged into a blue colored USB 3.0 port. Others online reported the same problem.
5) Launch the RSDLite program and click show device. (Figure_1 Picture attached to post)
6) If everything went right you should see your phone listed on line 1. The program doesn't list any specific info just that a device is connected. See Figure_1 Picture attached to post.
7) Click the box on the top and select the firmware image still zipped. (The RSDLite program will unzip the firmware) and then click on the start button. See Figure_2 picture attached to post for box to load firmware and start button.
8) This is your last chance to not ERASE your phone and load the new firmware. After clicking start in last step a menu will pop up with three options. Choose the middle option "Uncompress and Start Flashing" See Figure_3.jpg attched to the post. During the firmware flash DO Not unplug your phone or allow your laptop to sleep. The process took about ten to fifteen minutes. The program will update the files it's flashing i.e. flashing 1 of 32, 2 of 32, etc....
9) When the flashing is done RSDLite will reboot the phone and you'll be prompted to choose your language like a new phone.
Troubleshooting: If line 1 in the RSDLite program is blank after plugging in the phone and doesn't show a device then you'll need to try a different USB port on your computer. For some reason the phone only shows up on my black colored USB 2.0 ports and not my blue colored USB 3.0 ports. Also try a different USB cable if it doesn't show up. These are common issues with the RSDLite program from my research.
Update Moto G7 Power without erasing device.
Follow the steps in the post above but stop at step 6 and start here.
7) Unzip the firmware image you downloaded in a folder you create.
8) Open the RSDLite program and click the box on the top and then select servicefile.xml in the folder you created in step 7.
9) After selecting the servicefile.xml click start and flash your phone. This should not erase your data.
10) Some forums reported it is better to erase the phone per the top posts but no reason was given.
Update Moto G7 Power without using RSDLite.
Since some people have reported trouble getting to RSDLite to work so I decided to do it in a way similar to the way I updated my Pixel using Android Platform Tools.
1) Create a folder where everything will be kept. like a folder called android in C:\ like C:\android
2) Download the Android Platform Tools attached to this post and extract to the folder you created.
3) Download the Phone firmware in top post and UNZIP into the same folder you created with platform tools in it.
4) Download update_batfile.zip attached to this post and unzip into the folder you created with the phone firmware and Android Platform Tools in it.
5) Open a Windows command prompt in Start menu--> windows system or by holding the windows key + R and typing CMD.
6) Plug your phone into the laptop and go to Settings--> System-->Advanced-->Developer Options then toggle "USB debugging" to on. A screen should appear on the phone "Allow USB Debugging" press OK.
7) If you don't have developer options in your System-->advanced go to System--> about and tap the build number 7 times. Now try step 6 again. Developer options should be there.
8) Navigate to the C:\android folder you created or whatever folder you created with all the files in the Command Prompt. Something like cd \android
9) Turn off the phone, Once the phone is off, hold the volume down and then hold the power button. You should boot into the bootloader screen. Release the two buttons.
10) So you should have the phone in bootloader mode, all the files in one folder, have previously selected USB debugging when the phone was booted up, and the command prompt at the folder with all the files in it.
11) now type in the command prompt type either update_no_erase.bat or eraseandupdate.bat Obviously the update_no_erase.bat updates the phone without erasing it and eraseandupdate.bat erases the phone and then updates it. After typing the one of the two .bat filenames press enter and the .bat file will update the phone and then reboot it.
12) Good luck!
Man I was wondering why nobody was updated yet since that firmware has been available for a while.. I flashed it about last week or less all good..
Man I forgot about RDS Lite damn it.. . I flashed it manually and was PITA since it has Patition A and B and a few times I messed up the commands and installed parts of partition B on partition A since everything installs by default to Partition A unless you specify System_b because I forgot to specify the partition..
T
I weird thing about this May 1 lst Firmware and the one before after unlocking bootloader, in system updates it stated that my device is compromised so no more Ota but today out of nowhere that message changed back to normal System Up to date. So weird I did nothing at all.
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
thaessential said:
I knew there had to be a way a way to find that updated firmware. I just been too distracted having fun with a rooted phone finally to research it yet (my last 2 phones were sm-j727t-1's and before that some kyocera pos... I make bad decisions lol). so i take it we will have to reroot our devices after this as well...? we should be able to get all our other stuff back nearly identical using titanium with cloud storage though right? just slightly more of a headache than twrp...
Click to expand...
Click to collapse
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
nucher said:
You will definitely have to Re-Root the phone as this flashes all the partitions like it was when new. You may have to Unlock the bootloader again but I'm not sure about that. The bootloader may stay unlocked because that's a deeper setting I believe. With my Pixel 2 I would always have to Re-Root whenever I updated but that wasn't to difficult. If you do update report back on if the bootloader stayed unlock or not. You should be able to still unlock the bootloader again if it did lock, but again I don't think it will lock. You will be able to get everything back that's cloud based as you sign in with your google account. It will take a little time to reinstall some apps and change a few settings depending on how your phone is set up. I couldn't get the May 1st Security / phone fixes from system update so I went this route.
Click to expand...
Click to collapse
yeah I'm definitely getting it done soon. these unsuccessful update warnings are super annoying. i keep trying to hide more google and moto apps and some other things but nothing seems to have any effect
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Omar04 said:
My PC ports are all 2.0 and RDSLite do not recognize the device. I belive is the other way around (Need 3.0 Ports) because of that.
Click to expand...
Click to collapse
nucher said:
I know on my Lenovo Thinkpad the USB 3.0 ports would not recognize the phone in RSDLite. I tried switching between 3.0 and 2.0 and it would only show up in the 2.0 ports. Be sure to install the MotorolaDeviceManager_2.5.4.exe listed in the thread and the phone will only be recognized when it's in the bootloader mode (power on holding volume down button). I had trouble initially getting RSDLite to see the phone and in a few forums people reported trying a different USB C cable and using the 2.0 USB ports. For me it was using the 2.0 ports. Getting RSDLite to see the phone can be the most difficult part of the whole operation. Good Luck!
Click to expand...
Click to collapse
Yes I know that. Thanks anyway I been playing this game since Android 2.2 ? In my case are the ports 95% sure about it.
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
thaessential said:
all my ports are also 2.0 and i couldn't get my phone to show up in RSDlite. probably just wait for TWRP at this point
Click to expand...
Click to collapse
Yeah man I test it in several laptops only being recognized on 3.0 Ports. Because of "USB Type C"
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Rondeau79 said:
Manually flash the firmware through terminal and fastboot. That will fix the issue!
Click to expand...
Click to collapse
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always ?
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Omar04 said:
I been doing it for years manually no problems. I just wanted to try RSDlite once again has been years I have not use it. Still same issues as always
Click to expand...
Click to collapse
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Good to know. I'm new to the Motorola / Lenovo ecosystem. I've had Nexus and Pixels for the last 4 years. I'll add a link to the Lenovo Moto Smart Assistant Software in the main thread. Thanks!
MrCamby said:
FYI: Before you flash the update, you can use the Lenovo assistant to do a backup of your phone. Then you can restore from backup after the firmware flash.
Sent from my moto g(7) power using Tapatalk
Click to expand...
Click to collapse
nucher said:
I was aware of the fastboot method but I figured this would be easier for some people who didn't want to install Android Tools Package and deal with the typing or copying fastboot commands in a terminal. Using RSDLite is a simple and foolproof method of updating our phones. I didn't have much trouble getting RSDLite to work but but it seems like others are. Once you have RSDLite working updating your phone would take less than a minute. I plan on updating my phone each time Motorola issues a System update. My phone doesn't receive them in a timely matter because I'm on Verizon who tends to postpone System updates.
Click to expand...
Click to collapse
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically. ?
My 2nd post below the top will be a .bat file to use with ADB tools. Basically put the unzipped firmware, .bat file, and the adb tools all in one folder and run the .bat file. I just finished testing it now to type the post up.....
2nd Post is up now....
Omar04 said:
Agree with you 100% RDSLite awesome once you have it up and running but a PITA to the power of 10 when not. I usually don't type any command at all I just open notelad write all commands there save as bat and then open cmd in working folder fastboot devices to make sure device is connected and drag and drop the bat to the cmd window hit enter to star and it does all the job automatically.
Click to expand...
Click to collapse
so i noticed there are also linux and mac versions of rsdlite. i have a linux pc running debian 10. was gonna try stuff out on that and see if i get different results. personally when it comes to stuff like this i would much prefer to use gui software than term. i only have one phone... well that's not quite true... i only have one new phone lol
Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.
Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Have you recently updated and not re-authorized your phone?
sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.
Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.
sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.
Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.