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.
Related
I plan to unlock my bootloader, but not rooting the phone yet, want to see if I can live without root. But in case I find out I couldn't I don't want to wipe my device again, thus unlocking now before actually moving all my stuff over from my old Nexus.
My question is, does it have any drawback to unlock bootloader? Does it actually affect anything (besides the hyper-annoying nag screen on boot), that would make it better just to leave it locked, and do the wipe and everything only if I ever decide to actually root it? Tough decision, I'd love to hear your opinions.
Thank you!
Assuming you aren't flashing TWRP, right?
Drawbacks... Security, maybe? Can't really think of anything else. OTAs will still work, as will all the usual upsides.
Upside, you can flash the latest factory images as soon as they are released.
PhoenixTank said:
Assuming you aren't flashing TWRP, right?
Click to expand...
Click to collapse
Yes, no flashing nothing, just a plain fastboot oem unlock, then pretending to be a basic user with a locked phone. I wonder if from the OS side anything can be perceived by apps, security/integrity checks, etc.
Yeah, then nothing in android will know, apart from the checkbox you need to enable in developer options.
Only when you change the boot or system images, does it really flag up anything. Hope that helps.
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
It stays checked. I haven't tried to unchecked it yet
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
sordup said:
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
Click to expand...
Click to collapse
This. So far this is the only drawback I found.
IVBela said:
This. So far this is the only drawback I found.
Click to expand...
Click to collapse
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
It may work with casual thug. Sophisticated thief will turn device off, reboot into bootloader, wipe device and take possession. Device protection is meant to discourage theft.
https://support.google.com/nexus/answer/6172890?hl=en
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
There are three sets of drivers needed. One for fastboot, one for adb and one for MTP. When device is in fastboot mode you use command "fastboot devices" or Mac equivalent.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
This doesn't help if they get your device and factory reset it. If they factory reset it before you have a chance to lock it down then you are screwed. With device protection even when you factory reset it, it will prompt for the previous google account the phone was set up with. If your bootloader is unlocked and they are knowledgeable thieves then they can just reflash everything and wipe it out fully.
I work at Swappa and we see this all the time. Someone will sell their device, factory reset it and send it to the buyer. The buyer gets it and can't set it up because device protection was enabled and it prompts them for the previous google account info that was tied to the phone when they try to set it up
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
I tried using fastboot anyway, despite seeing no devices listed, and lo and behold, it worked. Bootloader unlocked for flashing.
About:
Scripts and packages to install Google services, aid in KingRoot, and disable Amazon services written for Apple OS X.
Requirements:
OS X, device wifi connected, debugging enabled, host RSA key accepted.
Notice:
This project is sleeping. Feel free to modify and redistribute. However, be warned that tampering with the scripts may cause unintended damage to your device.
Link:
Download v0.33
Usage:
Download and extract .zip file.
Run Terminal, cd into extracted GIaAK folder, then "sh install.sh".
Contributors:
kanderson88 - inspiration, collaboration
sd_shadow - insights
KingRoot - root
I am glad there are some happy Mac users here, I have made a bunch of neat scripts but never uploaded them. Good work.
Gonna give it a go, wish me luck! lol
#to re-enable Amazon Web view. Google web view doesn't currently step in and take over, probably needs permission to.
./adb shell
su
pm enable com.amazon.webview
pm uninstall com.Google.Android.webview
#affects things like Spotify Facebook login function, etc.
Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"
TripFlex said:
Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"
Click to expand...
Click to collapse
I had no issues downloading today. Using it soon.
Does this exist for windows? How about a similar tool?
can any one post command for manual install in windows ?
-waiting for device-
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.
watson007 said:
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.
Click to expand...
Click to collapse
On tablet Go into settings > device options > developer options > enable ADB.
If you don't see developer options then settings > device options > tap on build number 7 times > then tap developer options > enable ADB. You will get a pop up on your tablet asking for permission. check the box and say yes.
For Windows
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.
leejuspsa said:
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.
Click to expand...
Click to collapse
What version of FireOS are you on?
DragonFire1024 said:
What version of FireOS are you on?
Click to expand...
Click to collapse
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.
leejuspsa said:
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.
Click to expand...
Click to collapse
Did you do this before or after 5.4.0.1? We are trying to determine if uninstalling/disabling the apps is still possible on 5.4.0.1.
EDIT: Just noticed you said earlier version.
Does anyone know if this will work with the new 2017 edition?
pastorbennett said:
Does anyone know if this will work with the new 2017 edition?
Click to expand...
Click to collapse
did you end up trying it?
Can anyone modify it for linux or windows? As not everyone has a mac.
dadoc04 said:
did you end up trying it?
Click to expand...
Click to collapse
Sort of. It won't work, because Kingroot isn't yet compatible with the 2017 Fire HDs.
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.
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
JTC Intl said:
To unlock Bootloader:
[NOTE: device with root access no longer receives official update notifications from the manufacturer)
Click to expand...
Click to collapse
Mine did until I went into Developer Setting and un ticked automatic software updates..
I thought I had found the perfect Z2 for me. Ordered on eBay for $130 with no scratches and very slight screen burn-in. I don't worry about light burn-in as I always use Substratum and turn all my screens amoled black with light text, I never notice the burn-in anyway.
Only problem was it being a T-Mo version but I couldn't unlock the bootloader. I did all that was required to receive the Unlock Code, however, when I input it the second time, it states "code verification failure." Verifed correct code multiple times and upon checking the Motorola unlock help thread, there is a list at the beginning with CID #s of bootloaders that can be unlocked and those that can not. Any CID not listed as "can be unlocked" are unable to be unlocked even if the # does not appear under "cannot be unlocked" list. My CID of 0x0015 was not on either list, therefore deemed unlockable.
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
MrBrazil1911 said:
I saw someone else inquire about his 0x0015 CID and was told pretty much that same thing, so I didn't add to the thread and just returned the phone. Now I am looking to purchase another T-Mo phone from a different seller with hopes of receiving a compatible CID, but I'm kinda concerned about running into the same issue. Are you aware if there are large group of these T-Mobile phone who's bootloaders can't be unlocked or did I just get a one off CID#. Or should I be looking at rooting a Sprint version and trying to change it to a GSM Unlocked or are there Sprint version with unlockable bootloaders as well? Any advice as how you think I should proceed would be most helpful as I would like to order the replacement phone today or tomorrow. TIA
Click to expand...
Click to collapse
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Ace42 said:
If you're a T-Mobile/Metro user the TMO model is ideal. It packs every Magenta band aside from B71. The Sprint version will affect your experience on T-Mobile, as it only possesses 2, 4, and 12. So no LAA, 66, nor LTE-U. B46, aka LAA is stupid fast. I've heard U is good too, but availability is limited.
Now, if you use ATT, VZ, or Sprint you won't miss out on anything by buying the Sprint version.
All things considered, I'd gamble with the former. Playing the TMO lottery is definitely worth it. In fact, I bought a 2nd one and will see what happens in a few days.
Click to expand...
Click to collapse
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
MrBrazil1911 said:
Thanks for the feedback. I am primarily a T-Mo network user. I use Google Voice and just grab cheap MVNO sims from eBay and will occasionally use an AT&T sim card. So if I manual unlock it myself from instructions I've seen here, will I still retain the above bands you mentioned?
Click to expand...
Click to collapse
Bands stay following SIM and Bootloader unlocks. But, when the modem of another model is flashed access to LTE is lost.
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
mike2246 said:
Trying to do this and can't get unlock code. When I type in command i just get . . . in the cmd prompt
Click to expand...
Click to collapse
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
41rw4lk said:
Make sure you're using up to date adb/fastboot files and a 2.0 usb port. If no 2.0 ports try using a hub to bring the 3.0+ ports down.
Click to expand...
Click to collapse
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
allrightlite said:
I have used usb 3.0 all the time. Was never be a problem. But I would try, too :good: Wish the person luck
Click to expand...
Click to collapse
3.0 ports won't be a problem for everyone, but for some it is. Some have only been able to use one port on their pc for flashing, some have had to use hubs to dumb their ports down. That's why it is generally recommended to use 2.0 port. Saves having to repeat the same info 100x in every other post.
This worked perfectly until the last step for my Sprint version of Z2 Force. Kudos to JTC Intl for crystal clear instructions.
When I launch the Magisk Manager , it asks me if I want to "Upgrade to full Magisk to finish set up. Download and install?" I respond OK, then after sometime, it says "There was a problem parsing the package".
Instead of v18 of Magisk, I downloaded v22 that too not as a ZIP, but it was only available as an APK from their GITHub. (https://github.com/topjohnwu/Magisk/releases/tag/v22.1)
EDIT - I tried the troubleshooting suggestions for this problem in their wiki ( clearing cache, clearing data, reinstalling etc). Did not help.
Please help. I'm almost there.
Thank you.
hi i need help is there any other way i can unlock the boot loader because when i enter my code it says device not eligible....
JTC Intl said:
To unlock Bootloader:
On Phone:
Open Developer Mode: Settings>System>About Phone>Click "Build Number" Seven Times
Go back to System>Developer Options>Turn on: OEM Unlocking & USB Debugging
On PC:
Do Google Search for Downloads:
Download: adb and fastboot
Download: appropriate phone drivers
Connect Phone to PC
Open: adb & fastboot Folder>open Command Prompt/PowerShell
Type:
adb devices (Pop-up will appear on phone to allow USB debugging)
re-type adb devices (you should see your device)
adb reboot bootloader
fastboot devices
fastboot oem get_unlock_data (this data is used in the Motorola Website: https://motorola-global-portal.custh...-your-device-a)
Once logged in, put in above unlock data in to see if phone is able to be unlocked...click unlock.
You'll receive a unique unlock code via email....copy unlock code.
Go back to Command Prompt/PowerShell
Type:
fastboot oem unlock (unique unlock code) (type in twice to confirm unlocking)
(NOTE: ALL DATA WILL GET DELETED-BACK IT UP!)
If this isn't working, what hiccups are you running into?
To Root your device:
On Phone:
Make sure: Developer Options on>OEM Unlocking & USB Debugging turned on (steps above)
Connect (turned on) Device to PC
On PC:
download (TWRP file specific to phone: https://twrp.me/Devices/): EXAMPLE: twrp-3.2.3-0-nash.img
Open/Create new/clean adb/fastboot folder
place TWRP img file INTO the above folder
Download: Magisk-V18.0.zip (https://forum.xda-developers.com/app...mless-t3473445)
Place Magisk-V18.0 Zip file into adb/fastboot folder
Once all files within adb/fastboot folder, open Command Prompt/PowerShell
adb devices
adb reboot bootloader
fastboot devices
fastboot boot twrp-3.2.3-2-nash ((add: .img)) Phone should open Team Win Recovery
ON PHONE: Swipe to "Allow Modification"
adb devices (should show "recovery")
adb push Magisk-V18.0.zip /sdcard
adb shell twrp install /sdcard/Magisk-V18.0.zip (phone should show installation)
adb reboot
On Phone:
Open: Magisk Manager
select lines in upper left hand corner>Settings>Automatic Response>Grant
Open "Root Checker App" to verify root (i.e., Root Checker Pro, Root Checker Advanced)
Click to expand...
Click to collapse
Does rooting the phone work for an AT&T Moto Z2 force phone?
To update to Oreo without an active AT&T sim.
1. Download this official AT&T Oreo firmware to your computer
https://androidfilehost.com/?fid=673956719939833410
Firmware above should match this version which is the latest AT&T firmware.
https://www.att.com/devicehowto/tut...?make=Motorola&model=MotoZ2XT1789&gsi=N8TH4fU
2. Download Lenovo Moto Smart Assist
https://support.lenovo.com/us/en/downloads/ds101291
3. Enable USB Debugging on your device usually via settings on your phone and you press on About > Build numerous times until it states Developer settings enabled then you enable ADB USB Debugging there.
https://www.verizonwireless.com/support/knowledge-base-213471/
4. rename the zip firmware you downloaded in step one to update.zip and place it in the top level of your internal storage of your device from within Windows Explorer you will need to set your phone to USB file transfer mode instead of charging (the default) by pulling the notification area down on your phone and setting the USB mode there.
5. After that is done unplug the USB cable from your PC and plug it back in again.
6. Open the Lenovo Moto Smart Assist in Windows go to Flash it will look for updates and immediately the Update button will be enable because you have an update.zip on your phone. Click Update, let it finish rebooting your phone and whatnot and viola welcome to Android Oreo on your Moto Z2.
==> DO NOT POWER OFF YOUR DEVICE DURING FLASH ==<
Since you my end up with a soft bricked device and will have to find methods on XDA to restore it, but you should be able to do this directly from fastboot.
Begin by pressing the Power button for a few moments to turn off
the Moto Z device
In the next step hold down Volume Down and Power keys for a short while.
Let go of all keys when you see Fastboot Mode.
Once your in fastboot just repeat the steps above.
Note: You will get some security & permission prompts if it is the first time using Smart Assist. Do what it states.
If your device is not detected you might need Motorola Drivers here
https://mega.nz/#!buYjzAaR!3Xx0MHYJqIJ8JjdSKxRaEP4AkifzUd3XX8dXKuTVZ1I
or here via MDM (Motorola Device Manager) https://support.motorola.com/us/en/drivers
I found this out after numerous attempts with AT&T sim cards and trying to let the update happen in the Lenovo Moto Smart Assist but there was no progress indicator and sometimes the download would fail..but this worked for me.
dynamiclynk said:
To update to Oreo without an active AT&T sim.
2. Download Lenovo Moto Smart Assist
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Thanks for this.
I just did the update with the tool above. The tool actually offers you the option to download the latest OCXS27.109-47-14 image. Though it's still the September 1, 2018 security updated image.
As instructed, you just install the software and accept permissions.
Click on "Flash"
In the Flash section, under "New Ver:" there is an option to download the latest. What it will do is download the image and unzip it.
Once the image is ready, you can Click "Update" and follow the instructions.
If you use the default settings for install, there is a log file you can use to watch detailed progress. "C:\Program Files (x86)\Lenovo Moto Smart Assistant\logs"
Be patient at 51% it's likely copying the files during this time.
Is there an option to upgrade without windows pc? Via fastboot and such
galets said:
Is there an option to upgrade without windows pc? Via fastboot and such
Click to expand...
Click to collapse
The smart assist tool installs fastboot during the update process and it goes into the bootloader screen when it performs the update. So as long as it's the official image, there might be a way. I'm not sure, I did the update with my windows vm.
pitchdarkice said:
The smart assist tool installs fastboot during the update process and it goes into the bootloader screen when it performs the update. So as long as it's the official image, there might be a way. I'm not sure, I did the update with my windows vm.
Click to expand...
Click to collapse
I am thinking the smart assist has privileged access to flash via security keys because when I tried flashing via fastboot or even from recovery via the zip file I did not have permissions, at least that's what happened to me.
The firmware file seems to be for z2 "play". Will it work for z2 "force" model?
Anyone used LMSA to get the Jan 2019 update? LMSA shows Nov 2018 is the latest update.
Update to January 2019 security update
HKSpeed said:
Anyone used LMSA to get the Jan 2019 update? LMSA shows Nov 2018 is the latest update.
Click to expand...
Click to collapse
I did successfully updated mt at&t z2 force to January 2019 security update. I could not make the manual method work for me, but LMSA already lists the January 2019 patch. All you need to do is install motorola drivers and LMSA, allow USB debugging and connect your phone to your computer. Then let LMSA recognize the phone and it will show latest update. Download it directly in LMSA, and the Upgrade button will become available.
February security patch released April 30 for AT&T Z2 Force. I didn't get it OTA as of yesterday (5/5). I guess I'll try LMSA.
https://www.att.com/devicehowto/tutorial.html#!/stepbystep/id/stepbystep_KM1226455?gsi=9oak3b
There are two uploads for Feb security patch on mirrors.lolinet.com. Both was uploaded on May. The 2nd one has the text "FIX NFC".