Related
Introduction:
This is a list of all known OTA's for the Motorola Moto 360 watch
The Moto 360 has it's ROMs built directly by google, instead of Motorola.
Click to expand...
Click to collapse
File List:
Latest:
LWX48P → LWX48T
See Motorola Moto 360 # Official ROMs - XDA Wiki for a list of files
Click to expand...
Click to collapse
How to flash:
Requirements:
Stock recovery
Unmodified /system
Unlocked bootloader
Basic understanding of command line/shell
Unlock your bootloader
Download and set up adb and fastboot
Reboot into fastboot mode
Open up a command prompt/shell where you saved fastboot
enter into command prompt/shell: "fastboot oem unlock"
Enter recovery mode via onscreen buttons
Enable recovery ui
(How do you do this for this device?)
Set up adb
Select apply update from adb
enter into command prompt: "adb sideload <path to saved update.zip>
Click to expand...
Click to collapse
FAQ:
How to find the ota?
If you're rooted, wait for the device to prompt you to update, then check /cache for the file
If you're not rooted, wait until the same time and do an adb logcat and look for a line with .zip in it
Why isn't the latest ota listed?
We can only list what we have, if the ota from Build X to Build Y isn't listed, we dont have the file for it yet.
How do you setup adb/fastboot
Please read the stickies in the general subforum, this is not a formal guide
Do I need to unlock the bootloader to flash the update zip?
Yes, if you wish to do it manually.
If you allow android to prompt for the update, you do not need to unlock
Can I flash this if I have a custom rom?
No, you must be on a stock AND unmodified rom
Can I flash this if I'm rooted?
Only if you have not modified any files
Click to expand...
Click to collapse
Credits:
birdpcfireworks: KKW22 → KGW42N
dproldan: KGW42N → KGW42R
EthanFirst: KGW42R → KNX01S
xdatastic: LWX48P → LWX48T
Click to expand...
Click to collapse
Changelog:
Dec 16, 2014: Added LWX48P → LWX48T
Oct 25, 2014: Added KGW42N→ KNX01S
Oct 24, 2014: Added KGW42R → KNX01S
Sep 25, 2014: Added KGW42N → KGW42R
Sep 11, 2014: Changed Page Layout to match my other pages
Sep 9, 2014: KKW22 → KGW42N
Sep 6, 2014: Initial page
Click to expand...
Click to collapse
2char
The initial rom is KKW22, I need a dump of it to assist in finding future otas.
It might be possible (this is simply speculation) that there might be an ota soonish to make it land on the same build as the existing g watch/gear live
I'm not familiar with what the current build version is on the other watches, but the first OTA is downloaded immediately upon setting up the device and updates it to KGW42N.
Edit: Dumping /system now.
AJerman said:
I'm not familiar with what the current build version is on the other watches, but the first OTA is downloaded immediately upon setting up the device and updates it to KGW42N.
Edit: Dumping /system now.
Click to expand...
Click to collapse
KGW42N is currently the newest for the gear live, unsure if it is rolling out to the g watch yet (i have yet to recieve an ota notification).
I assume you have a dump of KGW42N? I assume you dont have the ota itself for it, could you make a bug report and send it to me?
(I assume it's still possible, on normal android it's a button in developer settings) It might still be possible to get the filename of the ota.
dumps of either would be useful, along with the bootloader version.
TheManii said:
KGW42N is currently the newest for the gear live, unsure if it is rolling out to the g watch yet (i have yet to recieve an ota notification).
I assume you have a dump of KGW42N? I assume you dont have the ota itself for it, could you make a bug report and send it to me?
(I assume it's still possible, on normal android it's a button in developer settings) It might still be possible to get the filename of the ota.
dumps of either would be useful, along with the bootloader version.
Click to expand...
Click to collapse
Yep, I'll get everything I can, just taking a little time with adb over BT.
So you're saying in the OP you can unlock the bootloader with 'fastboot oem unlock', correct?
mattlgroff said:
So you're saying in the OP you can unlock the bootloader with 'fastboot oem unlock', correct?
Click to expand...
Click to collapse
The text in it is generic, I dont own a wear device but the previous two can.
The main issue right now is figuring out how to connect via fastboot, if it's possible at all I would assume that it is unlockable like the others.
If something is definitely incorrect feel free to let me know how to change it.
TheManii said:
The text in it is generic, I dont own a wear device but the previous two can.
The main issue right now is figuring out how to connect via fastboot, if it's possible at all I would assume that it is unlockable like the others.
If something is definitely incorrect feel free to let me know how to change it.
Click to expand...
Click to collapse
Nothing correct or incorrect to my knowledge. I can't find a single thread or post confirming if its unlockable or not. Kind of hoping you had tried
mattlgroff said:
Nothing correct or incorrect to my knowledge. I can't find a single thread or post confirming if its unlockable or not. Kind of hoping you had tried
Click to expand...
Click to collapse
If you connect via ADB over BT and reboot it into bootloader, among other things there is text saying connect a USB cable. So :/
fodawim said:
If you connect via ADB over BT and reboot it into bootloader, among other things there is text saying connect a USB cable. So :/
Click to expand...
Click to collapse
Well this problems stumps me!
I'm curious if the board supports Wireless USB.
All,
Here's what we know about the stock firmware right now:
1. Moto 360s ship with KKW22 out of the box.
2. Once the watch charges to 80%, it will force OTA to KGW42N.
What we need is someone to get some info about KKW22 before that watch reaches a charge of 80%! When you get your Moto 360, please plug it into the charging cradle and plug it into USB on your computer.
Pair it to your phone with the Android Wear app.
Enable ADB debugging on the watch by going to Settings | About Device and tapping on the build number repeatedly until it says "You are a developer."
At that point, go under Settings | Developer Options and enable ADB debugging.
Install the Google USB drivers for the "unknown device" that appears in the Windows device manager and select it as "Android Composite ADB Device."
Go to a command prompt and do "adb devices". This should cause a prompt to appear on your PHONE asking you to authorize adb. Do so.
Once authorized, do "adb logcat >logcat.txt". Wait about 20 seconds, then press control-C to stop.
Open up the logcat.txt file that was created and search it for "android.clients" (without the quotes) and post the URL to the OTA update here.
Do "adb reboot bootloader" and please post the bootloader version as displayed on the screen.
Reboot the watch again and then run "adb pull /system/build.prop". Open the build.prop file in a text editor and post the values of ro.build.date.utc and ro.build.fingerprint.
At this point, we'll have all the information we need and you can feel free to update to KGW42N happily and enjoy your new toy!
Thanks for your help, guys.
Wait, does this mean that the watch is capable of doing data over Qi?
Also, I'd be glad to help if I ever get my watch.
Slack3r said:
Wait, does this mean that the watch is capable of doing data over Qi?
Also, I'd be glad to help if I ever get my watch.
Click to expand...
Click to collapse
Not sure on the Qi question.
Have you ordered a 360? When is it due to arrive?
oldblue910 said:
Not sure on the Qi question.
Have you ordered a 360? When is it due to arrive?
Click to expand...
Click to collapse
Ordered one from Google Play on Friday, it's at "Leaves warehouse by September 22" so no idea when it will actually show up.
As for the Qi question, as the 360 has an inductive charger there is no way to actually plug into the watch and make a connection directly. Someone in another thread mentioned that Qi supported data transfer in some form, and I was hoping that the cradle would act as a USB interface to the watch. Were you referring to running adb via the phone's connection instead?
I'm really hoping someone will do a teardown of this thing soon. I'm itching to see what's inside.
Slack3r said:
Ordered one from Google Play on Friday, it's at "Leaves warehouse by September 22" so no idea when it will actually show up.
As for the Qi question, as the 360 has an inductive charger there is no way to actually plug into the watch and make a connection directly. Someone in another thread mentioned that Qi supported data transfer in some form, and I was hoping that the cradle would act as a USB interface to the watch. Were you referring to running adb via the phone's connection instead?
I'm really hoping someone will do a teardown of this thing soon. I'm itching to see what's inside.
Click to expand...
Click to collapse
ADB is done over bluetooth. You enable adb debugging over bluetooth on the watch, then on the phone you use the Android Wear app and go to settings and check Debugging over Bluetooth which will connect them, then you plug your phone into your computer and set up an adb tunnel to the watch. It's a bit convoluted and extremely slow. See the other thread in Q&A for more info.
AJerman said:
ADB is done over bluetooth. You enable adb debugging over bluetooth on the watch, then on the phone you use the Android Wear app and go to settings and check Debugging over Bluetooth which will connect them, then you plug your phone into your computer and set up an adb tunnel to the watch. It's a bit convoluted and extremely slow. See the other thread in Q&A for more info.
Click to expand...
Click to collapse
Glad to see someone who lives one town away from me (I'm in Morrisville).
I've never tried debugging via bluetooth on my Gear Live. I've always just snapped the charging cradle on and plugged the watch in via USB.
oldblue910 said:
Glad to see someone who lives one town away from me (I'm in Morrisville).
I've never tried debugging via bluetooth on my Gear Live. I've always just snapped the charging cradle on and plugged the watch in via USB.
Click to expand...
Click to collapse
Ahh, nice! I'm actually closer to Morrisville and RTP than Cary, though I'm technically a Cary address. :laugh:
Yeah, why would you even want to try to use adb via bluetooth if you have an alternative. It took me about 3 hours to do a system dump of the 360! You can expect that if and when any ROMs get built for this device, they'll take HOURS to transfer to the watch.
FCC docs show WiFi, and I suspect WiFi is used for updates.
AJerman said:
Ahh, nice! I'm actually closer to Morrisville and RTP than Cary, though I'm technically a Cary address. :laugh:
Yeah, why would you even want to try to use adb via bluetooth if you have an alternative. It took me about 3 hours to do a system dump of the 360! You can expect that if and when any ROMs get built for this device, they'll take HOURS to transfer to the watch.
Click to expand...
Click to collapse
Apparently the Moto 360 can't do data at all via the dock. You're forced into bluetooth ADB debugging as the dock is literally nothing but a Qi stand. Score one for the G Watch and Gear Live, I guess.
I did a quick search and didn't find another just general post about this version, although there may be one buried inside another thread. If there is another thread, let me know and I'll have this thread deleted.
Although the main page http://www.htc.com/us/support/rom-downloads.html#unlocked version # and Download link hasn't been updated since v2.41.617.3, the View page http://www.htc.com/us/support/htc-10/news/ for v2.41.617.3 actually takes you to the proper v2.48.617.1 info.
Official download link Download (1.8 GB).
I haven't applied the OTA yet, so I don't have any other details than what you see here.
Code:
HTC 10 Maintenance Release Instructions 5.3.2017
This software upgrade available for your HTC 10 provides the following key enhancements:
· Bug fixes
· April 2017 Android Security Updates
Details
Before you proceed, please confirm that this software upgrade to 2.48.617.1 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen, then tap All apps > Settings > About and locate the Software information . If your Software number is less than 2.48.617.1 , you should proceed with the upgrade.
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the AC charger or long-press the Power button as this might stop the update and your device may be rendered inoperable!
Getting Started
Before you proceed with the update, make sure you have done the following:
· Set aside approximately 20 minutes to allow the device to update
· Connect the device to a charger
· Ensure the battery is charged to at least 35%
· Connect to Wi-Fi to access and download the update
Installation instructions
To download and install the update from the device, follow these steps below:
Follow the "Getting Started" steps above.
From the Home screen tap All apps , tap Settings .
Tap About .
Tap Software updates .
Tap Check now .
Tap DOWNLOAD to download the update.
The status of the download can be checked in the Notifications pull down.
Once the download is complete, the user will be prompted to install from the Notifications pull down. Tap the System update to begin the upgrade process.
Tap OK to begin the update process to software version 2.48.617.1 .
WARNING: During the upgrade process the device will reboot multiple times and show software upgrade screens. Do not remove the AC charger or long-press the Power button as this might stop the update and your device may be rendered inoperable!
The device will reboot and begin installation. Users will not be able to use their device during the installation process (approximately 10 minutes).
Once the system update is complete, tap OK to continue.
For best performance, open Play Store and tap the Menu icon, then select My apps and ensure all installed apps are updated.
Manual system update instructions:
If you are outside of Wi-Fi coverage, or the update is not found, you may perform a manual system update via USB connection to a PC. This process requires that you download and install HTC Sync Manager first in order to get the proper drivers. If you do not have HTC Sync Manager installed already, you may download the software from http://www.htc.com/www/software/htc-sync-manager/ .
WARNING: Performing the system update manually will delete all information from the device. Ensure all information is backed up before proceeding. See the Help & How To section of this website for more information on backing up your device contents.
Performing the ROM Update:
Download and save the HTC 10™ ROM update to your PC.
Connect your device to your PC via the supplied USB cable.
If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
Once the device is properly recognized on the PC, locate the HTC 10™ ROM Update that you downloaded. Double-click on the file to launch the system update wizard.
Follow all of the system update wizard instructions shown on your PC.
Once the update is complete, click Finish in the Wizard and the device will reboot.
Once the device reboots, the initial setup wizard will appear.
After the initial setup process is complete, open Play Store , tap the Menu icon, then select My apps and ensure all installed apps are updated.
After initial setup and updating all apps, the device is ready for use.
Note : If the ROM update wizard fails to recognize the device, close the wizard and then follow the steps below:
· From a powered off state, hold VOLUME DOWN while powering on the device to access download mode.
· Connect the device to the PC while in this state and attempt the ROM update again.
To exit download mode manually, use the volume keys to navigate to reboot and press the POWER button to select it.
Can this be installed on specific HTC 10's only or all? I'm stuck on 2.41.401.3 with January 2017 security update which I'm a bit disappointed about tbh.
Disruptor4 said:
Can this be installed on specific HTC 10's only or all? I'm stuck on 2.41.401.3 with January 2017 security update which I'm a bit disappointed about tbh.
Click to expand...
Click to collapse
Your device CID/MID must match the ones of the RUU. Short answer: unfortunately you can't.
We are all disappointed about that. Let's hope that now that the U11 is out, they will give some love to the 10.
question
can i install this if iam having now custom rom ?
Ahmad-Hamad said:
can i install this if iam having now custom rom ?
Click to expand...
Click to collapse
If your cid-mid matches,you can install.
A Verizon S-OFF user can flash this RUU, from my understanding.
I am a bit lost in the questioning.
anyone know if this fixes the intermittent wifi problem
If only they would be more specific about "Bug fixes" -_-
I hate messing with my cid and mid just for an update with unknown fixes
I'm on the June security patch and I haven't been able to update anything OTA even though I have an AT&T SIM. Is there someway to force the Software Update check to work properly by using a pm command in the shell? Do I need to sideload the firmware to get it update to OREO and if so, what is the command and where can I find the full file. Any help would be useful.
please go here: https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/XT1789-04/
download the at&t rom for your device.
unzip into platformtools.
and run these commands
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
let me know if this helps you get back on track with being able to update from AT&T
i have used this in a bat script to install the AT&T rom on the tmobile hardware, then i was able to go back to stock once more and install updates.
Do these commands work on a locked bootloader which AT&T has? Does someone have a good understanding of how the following packages work regarding ota updates?
com.motorola.ccc.devicemanagement
com.motorola.ccc.checkin
com.motorola.ccc.mainplm
com.motorola.ccc.ota
com.motorola.ccc.notification
I was wondering if i could clear out the cache of one of them or disable then re-eanable one or more of them would that possibly fix my ota problems?
I am having the same issue, the phone is stuck on the June patch and no matter what I do I can't get any updates, nor will adb sideload or install update from zip in recovery work.
edit:
got it working, if you are still stuck on June security patch just download the AT&T update from the 2nd post above, put the phone into bootloader mode, and unzip the attached bat file in the folder then run it (ensure you have the Motorola drivers installed). as soon as I rebooted and set up I checked for updates and it started downloading the new 8.0.
DISCLAIMER: for AT&T Z2 Force models.... will wipe data.... this worked for me may not work for you... use at your own risk.... it's you not me.... this is your choice.
i did the same, now i have november update but i didnt get the oreo update afterwards.
Install the stock rom
Is there any way to flash the downloaded stock rom from post 2? No further OTA update
What do you mean will wipe data
Mrgabi said:
What do you mean will wipe data
Click to expand...
Click to collapse
It will wipe everything from your phone like a factory reset so make sure you have a backup of whatever you need to reinstall.
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next.
Thanks,
Click to expand...
Click to collapse
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
kingstu said:
Do a warranty replacement. I got a replacement free of charge with updated security patch and android Oreo. I suggest doing it immediately while it is free.
Click to expand...
Click to collapse
OK well, I bought it on Swappa it was new (resale) so the box was opened but everything else wasn't and still had the plastic on it. So I contacted Motorola on their support forums and they said to just wait a little while and see if it'll update but too they also said they'd have someone take a look into it as they have my IMEI number so I guess will see what they say.
Thanks for the reply
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hello, Just checked and it says my warranty expires Sep 2018. So hopefully it shouldn't cost. Now though if I do return it I am assuming they'll just want the device nothing else and will they send me back a new device as this device is new no scratches or nothing and don't want to get back a device that has any marks or scuffs etc. Also, the first thing I did before even turning the device on was put on a tempered glass screen protector so I am assuming I'd take that off before I sent the device back to them. Either way, I hope I can get the issue fixed without having to return it but at least I know it's under warranty, Assuming that when it says Sep 2018 that once Sep 1st hits that the warranty will be expired?
Thanks again
kingstu said:
Again, I would do a warranty replacement. I bought mine used and I got a warranty replacement free of charge. You need to use your IEMI and select the "software unable to update" as an option and they will give you a price and let you know if it is under warranty. Mine was without cost and I shipped them the phone and waited for them to send me a replacement. If you wait too long you might go past the 1 year mark and then it might cost you. Don't delay and to inquire about it online though the support links is probably best.
Click to expand...
Click to collapse
Hey, I dropped my device off with FedEx on Sunday and Motorola said they received it yesterday, anyways just wondering how long your turnaround time. I have my Moto E4 that I can use so it's not the worst if I have to wait. Hopefully, it won't be too long especially if they're just going to send me a new device that should have Android oreo and updated security patches on it.
Thanks again for your advice.
Seems like it runs through script fine until the end
Script seems to run fine until the end. Phone wont boot and flashes at logo screen and then goes to bootloader logs saying your device didn't start up successfully. Need help. Can anyone help with this? I think the problem might be with the userdata not automatically formatting at the end. Nevermind, Everything all good after 3 or 4 tries. I still can't update to the latest build after flashing, which is OCXS27.109-47-11 according to what I looked @ att website. It says I have the latest version which is OCXS27.109-47-7. Anyone have the latest build to flash?
i had the same issue
I've used Lenovo Smart Moto Assistant and managed to get the last update
I have the same issue with T mobile. the phone says there is a new update, it downloads and tries to install but fails. I am on the May 2018 security patch, OCXS27.1.3. Android File Host and other sites don't list any new firmware. I have tried the Lenovo Smart Moto Assistant and it also doesn't recognize the new update. Any suggestions?
Oreo Update
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
https://support.lenovo.com/il/en/downloads/ds101291
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
bbgarnett said:
Hello, Just got my Z2 force (AT&T) and it too is on the June 2017 security patch and I can't seem to get it to update either as it just says no updates available. I have tried the things listed here but still, no go for me and not sure what to try next. I mean I am pretty sure I was following the directions correctly. I have downloaded the Motorola drivers and installed them, I also have the platformtools unzipped into a folder C:/adb. I then downloaded the NASH_ATT_NCX26.122-59-8-11-1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip and downloaded it into the platformtools folder and then unzipped it so all the files were in C:\adb\platform-tools. I then ran a powershell on windows 10 and did ./adb devices and it had 1 device attached I then did ./adb reboot recovery and it reboot into recovery with the andoird guy and a red triangle with an ! in it. Then whenever I run a command or ty the flashall.bat it just sits there and says waiting for device. yet it it able to find hte device if I do ./adb devices. So not sure what my next steps should be.
Thanks,
Click to expand...
Click to collapse
westec2 said:
For all who could not receive the Android 8 Oreo update and need it:
I was finally able to install the update through the Lenovo Moto Smart Assistant (poorly designed tool but at least it's a work around):
Before starting, you have to tap your build number 7 times ( Apps > Settings > System > About phone then tap Build number 7 times. Tap the Back icon to navigate back to System then select Developer options.)
Tap USB debugging to turn on. BTW when you connect it to the smart assistant, there will be a couple of popups on the phone screen that you have to give permission to.
The first dozen times I tried it, it would stall at 51% no matter what settings i picked. I finally got it to work by doing the following:
Once it recognized the phone (has to be powered on), I went to the update tab and let it see my phone and get ready to start the update.
Next I turned off the phone, then held the down volume, and powered back on (into fastboot.) Then I started the upgrade. It took a while but actually completed when I came back from breakfast.
Then, I had a new problem which appears all over the net: my finger print reader didn't work anymore. I tried a full wipe/restore from the settings, but it didn't help. There's directions all over the net to sideload files, etc, but I didn't do any of that.
I went back into the smart assistant and instead of doing the upgrade, I did the rescue (pick Moto Phone, then select your device from the drop downs (moto z 2nd gen). With this process, it actually tells you to turn off your phone, then power-on with the volume down depressed.
After the Rescue, my finger print reader was reconfigured and is now working great.
I hope someone else finds this helpful. I was very eager to get the update and make sure my phone didn't brick or something while I could still return it. Good luck and comment with your results if you give it a try.
Click to expand...
Click to collapse
Hello.
I don't know if i did not understand correctly, but when I have the phone recognized to do the update, i turn it off, and since the PC stops recognizing it is connected, the lenovo smart assistant goes back to the sync page.
How could you achieve that? Do you have another setting on your PC or lenovo assistant software?
Do you turn it off before clicking proceed?
Do you turn it off while the "all information could be wiped" is on screen?
Do you turn it off when the "loading bar" starts?
Could you be more specific? I would like to update my phone.
Thank you.
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
{
"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"
}
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
This is exactly what I needed; not necessarily a hand-holding or step by step, but a path forward to investigate. Thanks!
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
41rw4lk said:
If you have an official firmware for your variant (ATT), you can use a convertor to convert the flashfile.xml to a .bat file and flash your firmware from command prompt. The "how to return to stock" thread will help you, but keep in mind that it is tested on TMO and SPIRNT, ATT isn't much different, but flashall.bat in the flashall util zip might not be sufficient for ATT. That's what the convertor is for, you can make your own flashall with your own xml from the firmware you have. Use the return to stock thread as a guide, and it has links for ATT official firmwares provided from the Moto Firmware Team.
Click to expand...
Click to collapse
westec2 said:
So I also bought the ATT Z2 Force and LOVE IT. I got all the mods too Similarly, I can't get the OTA updates to work, and the lenovo tool hangs at 51%.
Just to be certain, does the method below work on locked bootloaders without root? Thanks so much!!!
Click to expand...
Click to collapse
With a locked bootloader you can flash an official firmware that is the same revision or newer. So in short, yes.
Hello! I ended up using the smart tool; it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool; it was the easiest way without root to get updated. Once I had the right drivers installed and it recognized bootloader mode, LMSA was really easy to use.
despree said:
it hangs at 51 pct because it doesn't have the right drivers loaded for your device in bootloader mode; it's not recognizing your phone once it reboots back over into bootloader mode. I ended up installing the right drivers and using that tool.
Click to expand...
Click to collapse
How did you get the "right drivers" and how did you install them? Does the PC download them automatically when you attach the phone or did you need to find them and manually install them?
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
New to updating here
despree said:
Hey, had to get home to do some digging. I tried different drivers from a few different places, but I'm pretty sure the ones that worked for me are "15 Second ADB Installer", forum.xda-developers.com/showthread.php?t=2588979 . Install those guys, then start the update process. Before the update process, under Device Manager, your phone should show up as "Universal Serial Bus devices -> Moto Z (2)" (or similar). This is correct when your phone is normally operating and connected to the PC with USB debugging.
Then, during the update process, it will put your phone in bootloader mode (with the android dude on his back, chest open). This is where the problem is. Whatever device it loads your phone as (I forget now), is wrong. Under device manager it should be "SAMSUNG Android Phone-> Android Bootloader Interface". So whatever device it loads as, update the drivers; and, with the new drivers you installed above, select that one (Samsung Android Phone/Android Bootloader Interface). I'm not sure at this point; you may need to restart the update process, or it may detect the new device and go from there. But either way, once it gets your phone back to that bootloader mode (android dude on his back), scroll over to "Bootloader Logs", and you should actually see some entries happening. If you do, DO NOT DO ANYTHING ELSE UNTIL IT'S DONE. Or you'll be restoring your phone and blowing everything away. Personal experience.
After that, you should be good and able to update!
Worth noting: I was hoping once I did this, the OTA update process would fix itself. While testing this out for you and writing this up, LMSA said I had an update...and my OTA "check for updates" feature said I did not. So I think long term, this is now how we update our phones. Hopefully that means we'll get 9 sooner, as a silver lining...
Feel free to reply if this doesn't make sense or something isn't clear, and I'll try to clarify further.
Click to expand...
Click to collapse
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
omiCar said:
I am pretty new to updating andriod devices, is there a toturial that might have some type of step by step out there that you might know about? thanks a lot
Click to expand...
Click to collapse
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
despree said:
Hey omiCar, I do not; not for this. Just did a lot of tinkering. I'll add some more info below to my previous post; this assumes you know how to change device drivers for a device on a windows machine. If not, Google should be able to fill you in on that process!
This is an atypical upgrade method; on the flip side, it's also a lot less "technical" than most upgrade processes. On a windows machine, first install the other drivers I mention above. Then power off your phone, then press and hold the power and volume down buttons until it turns on; this will turn on your phone in bootloader mode. Connect it to your PC, and verify under Device Manager it comes up as "SAMSUNG Android Phone"; if it's anything different, change the driver so that it's that. Now, when the update process reboots your phone for you and puts it in bootloader mode, it will be able to find your phone.
Download the Lenovo mobile smart assistant tool (LMSA, above), and in there is an "update" function; that's the one I refer to above. Reboot your phone so it starts normally, and launch the "Mobile Assistant" app on your Moto Z2; connect your phone to your PC, and make sure the Mobile Assistant can see your phone. Navigate to the update process, and start that. It will take a really long time to download the 1GB+ image with almost no change on screen, so be ready to wait; then it will reboot your phone, and you'll see that android on it's back again screen. It will take another long time to update your phone (30-60 min?). I think it may self reboot a few times during that process? It will then "optimize" the apps, and then you'll be back to your lock screen, ready to go.
Click to expand...
Click to collapse
Hi, thank you for your quick response, I will be attempting to do this tonight or tomorrow, I will circle back with an update, again thank you !
Backup phone first with LMSA
That's what I had to do so it would stop hanging at 51%. Use LMSA backup feature first then upgrade
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
bdizzle1686 said:
Quick question and I'm sorry it doesn't relate to your guys update issues but I've been looking desperately for a copy of the Z2 Force-Nougat SystemUI apk, and I can't find anyone who can upload it because they've all already upgraded to Oreo... So if possible, could 1 of you guys who are still on Nougat upload a copy of your SystemUI apk ?? It would be so GREATLY APPRECIATED, I've been searching forever...
Click to expand...
Click to collapse
You can take any flashing all, use a tool to merge the sparsed system images and mount the system img and pull it that way if you really need it
wrenhal said:
I just got one of these phones and it came with 7.1.1. And says no updates. If I connect it in Download mode it shows under "Android Device" -> "Motorola ADB Interface". You're telling me that's not correct and it should be Samsung? That's strange. I'll check this out.
Click to expand...
Click to collapse
Answered my own question. The flash worked fine. I switched over to the log at 51% and watched it copying files and eventually it finished up and the phone rebooted to Oreo. All in all, if say it took only fifteen to twenty minutes.
Sent from my KIW-L24 using Tapatalk
despree said:
Hey all, I recently purchased my Moto Z2 Force att branded phone from motorola.com (when it was on sale for $300); love it so far...but. it's currently on 7.1.1...and refuses to update. I've talked to att customer service for over an hour, and they swear they've done everything they can do from the network side; that it must be a phone issue (...I don't buy it). Moto says they aren't in charge of updates, must be an update issue. Thanks guys.
So I want to get to Oreo, *without* invalidating my warranty.
I downloaded the Lenovo MOTO Smart Assistant (pointed out in other threads), and it recognized that I was out of date. The Flash section of the LMSA seemed to download the latest image, rebooted my phone...and stopped. Showed 51% done, and didn't move once left for hours. The phone is showing the fastboot screen (as if you had held the volume buttons and the power button), but doesn't seem to be going any further.
What the crud.
So I have an "official" image downloaded with the tool, ADB tools installed, and while I haven't rooted and reflashed this phone, I've done it in the past to others. Is there any way to use the image I DL'd with ADB or something else, without invalidating my warranty? (Pics show what was downloaded by the LMSA tool).
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143
I have a att s20 plus trying to update it but cant find the firmware the phone wont update ota some dumb error help.
@amazin1988
Unfortunately, ATT does not release firmware files.
Instead, you must update using FOTA (Firmware Over The Air).
From ATT's website you must:
Make sure you're in the U.S. and on our wireless network.
You can download the update via Firmware Over the Air (FOTA).
You must connect your device to Wi-Fi® to download the update.
Although there should be no impacts to settings or data, we recommend backing up your media files to an SD card, a computer, or using a favorite application, prior to upgrading the software.
Update & verify software
Update software
Make sure your device is fully charged and connected to Wi-Fi.
Swipe down from the Notification bar and select Settings.
Scroll to and select Software update, then Check for updates.
Follow the on-screen prompts to download and install the update. The device automatically restarts once the new software successfully installs.
If you have tried this and failed, what error message are you getting ?
or you can visit this ATT site for help with your issue:
Troubleshoot and resolve to fix software update issues