Motorola's "Moto Turbo" Receives Minor Software Update - Verizon Motorola Droid Turbo General

Anybody got this yet? Both my Moto Maxx XT1225 (Mexico and Puerto Rico) are flashed to Moto Turbo XT1225 images and I have not received any OTA notification.
India Moto Turbo is currently LXG22.33-12.11. This will take it to LXG22.33-12.16
http://www.gizbot.com/mobile/motorola-s-moto-turbo-receives-minor-change-software-update-025377.html
http://androidtechiez.blogspot.com/2015/05/motorola-moto-turbo-gets-minor-software.html
http://www.fonearena.com/blog/141830/motorola-moto-turbo-gets-minor-software-update-in-india.html
Motorola's Moto Turbo Receives Minor Software Update
Posted by: Prateek Roy Chowdhury Updated: Monday, May 25, 2015, 13:00 [IST]
{
"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"
}
The Motorola Moto Turbo, the Indian variant of the Verizon exclusive DROID Turbo has just received a new firmware update.
Motorola Moto Turbo In Pictures While the phone will still be running on Android Lollipop 5.0.2 after the update, it brings about performance and stability improvements. The update is 16.7MB in size and updates the build number to LXG22.33-12.16.
Previously we had seen that the Moto Turbo was facing some issues in terms of stability as it occasionally did hang up while we were using it. This update should most likely fix the issue and should also improve the performance.
Apart from that, it also fixes a rare issue that will prompt you to enter a PIN code in order to boot up the device and also might result in a audio error if you attempt to make an emergency call before entering the required PIN.
The update is available OTA on Moto Turbo devices in India. While neither the Moto Turbo nor its international counterparts have received the update to Lollipop 5.1, it is said to be releasing sometime in June.
Click to expand...
Click to collapse

This was announced several weeks ago, it was an urgent update because it seems that when you tried to make an emergency call, the other people on the the line couldn't hear anything.

I already have the mexico firmware update on the thread

I flashed this 16mb ota over moto maxx mexico 5.0.2, it brings performance and stability fixes for real. Very recommended ota update who owns a moto maxx / turbo. I didn't take note of the kernel date from the previous 5.0.2 but this one is from april 24, so it must be newer.

Semseddin said:
I flashed this 16mb ota over moto maxx mexico 5.0.2, it brings performance and stability fixes for real. Very recommended ota update who owns a moto maxx / turbo. I didn't take note of the kernel date from the previous 5.0.2 but this one is from april 24, so it must be newer.
Click to expand...
Click to collapse
The last one is from March 12.

Guys, I have unlocked bootloader and Root. it's safe install this update? Someone at this condition tried? Success?

RanonBR said:
Guys, I have unlocked bootloader and Root. it's safe install this update? Someone at this condition tried? Success?
Click to expand...
Click to collapse
No, if you are rooted you're gonna boot loop, happened to me

Jaocagomez said:
No, if you are rooted you're gonna boot loop, happened to me
Click to expand...
Click to collapse
So, you don't yet have the complete image to flash with LXG22.33-12.16. ?
And what's with all the crappy "news: websites out there suddenly touting the Moto Maxx is now getting 5.0.2? We've had final 5.0.2 since March... 5.02. soak test was in February, if you want to go back that far.
India Moto Turbo LAUNCHED with 5.0.2 in March, and Moto Maxx got 5.0.2 about the same time.

ChazzMatt said:
So, you don't yet have the complete image to flash with LXG22.33-12.16. ?
And what's with all the crappy websites out there this suddenly touting the Moto Maxx is now getting 5.0.2? We've had final 5.0.2 since March... 5.02. soak test was in February, if you want to go back that far.
Click to expand...
Click to collapse
no i dont have a full version, it just released that ota, i doubt its gonna be a full version, you have to install mexico lollipop then that ota and flash it on stock recovery.
it really feels somehow more smooth and animations looks better.

Jaocagomez said:
no i dont have a full version, it just released that ota, i doubt its gonna be a full version, you have to install mexico lollipop then that ota and flash it on stock recovery.
it really feels somehow more smooth and animations looks better.
Click to expand...
Click to collapse
I agree with you.
Just downgraded to KitKat 2 days ago because of the slowdowns.
Not I'm on 5.0.2 again with that update, it seems way better.
Let's see if it stands the [ultimate] test of time.
.13 loved to crash/slowdown my Snapchat/Spotify/Chrome to the point it was IMPOSSIBLE to use ((
And it insisted to shutdown the Moto 360 connection (buggy bluetooth) :/
Let's hope this got fixed. This were the only issues that I found, tho it were very severe :/

Jaocagomez said:
No, if you are rooted you're gonna boot loop, happened to me
Click to expand...
Click to collapse
so i guess we'll have to reflash the stock firmware before updating to 5.1, or android m if we recieve it?
---------- Post added at 11:36 AM ---------- Previous post was at 11:24 AM ----------
Semseddin said:
I flashed this 16mb ota over moto maxx mexico 5.0.2, it brings performance and stability fixes for real. Very recommended ota update who owns a moto maxx / turbo. I didn't take note of the kernel date from the previous 5.0.2 but this one is from april 24, so it must be newer.
Click to expand...
Click to collapse
how is your battery performance? does this update affect battery coz mine seems to drain quickly

sn9691 said:
so i guess we'll have to reflash the stock firmware before updating to 5.1, or android m if we recieve it?
---------- Post added at 11:36 AM ---------- Previous post was at 11:24 AM ----------
how is your battery performance? does this update affect battery coz mine seems to drain quickly
Click to expand...
Click to collapse
i think there is a slight decrease in battery life,too. However i think it is related to radio because there is not strong H+ connection in my apartment and i usually forget to change network to 2G before sleeping. Cell standby takes %7 of battery according to my battery stats. Before it was about %3-4.
Sent from my XT1225 using XDA Free mobile app

Is the OTA somewhere to download? Based on the screenshots, the radio FW is not updated.

Hi, I'm unlocked and rooted on my Moto Maxx (from Brazil), I have received the OTA, so I don't have to update? What can I have to do for the update to be ok?
Thanks!

sn9691 said:
so i guess we'll have to reflash the stock firmware before updating to 5.1, or android m if we recieve it?
Click to expand...
Click to collapse
I'm hoping for 5.1 Motorola will post full images or they'll leak. So, we can flash via ADB.
I don't want to go through the hassle of incremental updates from stock.

ChazzMatt said:
I'm hoping for 5.1 Motorola will post full images or they'll leak. So, we can flash via ADB.
I don't want to go through the hassle of incremental updates from stock.
Click to expand...
Click to collapse
*fastboot.

adrynalyne said:
*fastboot.
Click to expand...
Click to collapse
but @Jaocagomez did that and boot looped on the latest OTA. He was rooted. He had to go back to stock to then flash the OTA update.
I also have root, TWRP installed. It's the hassle of going back completely stock I want to avoid.
Motorola has not released the full image which contains the latest OTA update. So, just hoping with 5.1 they do...
Unless I am misunderstanding something with your suggestion?
Of course "official" 5.1 for Moto Maxx/Moto Turbo is probably a month away at the least. It won't come until Droid Turbo gets it, in my opinion.
We already have two custom ROMs for the Moto Maxx/Moto Turbo XT1225 built on 5.1.1, of course, but will be nice to have official sources released.

Skrilax_CZ said:
Is the OTA somewhere to download? Based on the screenshots, the radio FW is not updated.
Click to expand...
Click to collapse
i have it on my thread already http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
ChazzMatt said:
but @Jaocagomez did that and boot looped on the latest OTA. He was rooted. He had to go back to stock to then flash the OTA update.
I also have root, TWRP installed. It's the hassle of going back completely stock I want to avoid.
Motorola has not released the full image which contains the latest OTA update. So, just hoping with 5.1 they do...
Unless I am misunderstanding something with your suggestion?
Of course "official" 5.1 for Moto Maxx/Moto Turbo is probably a month away at the least. It won't come until Droid Turbo gets it, in my opinion.
We already have two custom ROMs for the Moto Maxx/Moto Turbo XT1225 built on 5.1.1, of course, but will be nice to have official sources released.
Click to expand...
Click to collapse
try first making a twrp backup, install stock recovery then try ota root survivor, disable root and take the ota , if doesnt work install twrp again and restore your backup

ChazzMatt said:
but @Jaocagomez did that and boot looped on the latest OTA. He was rooted. He had to go back to stock to then flash the OTA update.
I also have root, TWRP installed. It's the hassle of going back completely stock I want to avoid.
Motorola has not released the full image which contains the latest OTA update. So, just hoping with 5.1 they do...
Unless I am misunderstanding something with your suggestion?
Of course "official" 5.1 for Moto Maxx/Moto Turbo is probably a month away at the least. It won't come until Droid Turbo gets it, in my opinion.
We already have two custom ROMs for the Moto Maxx/Moto Turbo XT1225 built on 5.1.1, of course, but will be nice to have official sources released.
Click to expand...
Click to collapse
I was referring to your full images comment.
Full images can't be flashed via adb, which makes sense because nothing can be running on the flashed parititons and adbd is a kernel service.
It is also why you must reboot after flashing the bootloader, because it runs off whatever is in memory until you reboot. When rebooting, it reads the new flash from the partition.

Jaocagomez said:
No, if you are rooted you're gonna boot loop, happened to me
Click to expand...
Click to collapse
how did you solve your bootloop?

Related

Android™ 4.4.3, KitKat® Rolls Out to Moto Devices

Android™ 4.4.3, KitKat® Rolls Out to Moto Devices This Week
An amazing phone experience is more than just the physical device you hold in your hand. We know that the complete phone experience is about both the software and the hardware. And we believe that your software should continually evolve to get better and better and keep you on the cutting edge.
We are excited to announce some icing on top of the, well, KitKat. Starting today, we are rolling out Android™ 4.4.3, KitKat®, which was just released by Google.
This week we begin rolling out to:
Moto X T-Mobile users
Moto G users who bought online in the U.S. (includes Moto G 4G LTE) and at retail in Brazil
Moto E users who bought online in the U.S. For Moto E users, you are still up for the next major Android update as well. Consider this the cherry on top.
This latest software update brings an improved dialer with a new interface and new colors to enhance consistency and usability, as well as several stability, framework, security fixes, and enhancements to the power profile capabilities.
Motorola users will also enjoy:
Improved camera image quality for Moto X including better consistency of exposure, more realistic flash coloring, and improved photos in low light conditions using front camera.
For Moto X and Moto G, pausing for video recording with a convenient pause/resume button on the viewfinder.
Motorola Alert ( See Next Reply for Details below) in this update for Moto X and Moto G users.
This new app helps give peace of mind by sending periodic messages to the contacts you choose.
Check our release notes for Moto X, Moto G, and Moto E for more detailed information.
Wondering when new software updates will come to you? Please check our software upgrades page for the latest information.
Posted by Steve Horowitz, SVP, Software Engineering
Source http://motorola-blog.blogspot.in/
:: Post Android™ 4.4.3, KitKat® for Moto Devices This Week ::
Motorola Alert lets you quickly alert people important to you when you need them.
Simply put your phone on alert and it will begin sending periodic notifications with your location
to the people you designate so they can act fast to get you the help you need.
With Motorola Alert you can also set up places such as Home, Work or School,
so that your loved ones can be automatically notified when you leave or arrive.
Download MOTOROLA ALERT HERE for your Moto X 4.4.3, KitKat®
Source : Google Play
Where´s the Developer Edition 4.4.3 ROM???
rodpp said:
Where´s the Developer Edition 4.4.3 ROM???
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/mot...tock-flashable-t-mobile-t2773675/post53177612
The GSM Developer Edition uses the same ROM as the T-Mobile variant. If you are referring to the VZW Dev Edition, you'll have to wait a little longer as it has not been released yet.
samwathegreat said:
Here:
http://forum.xda-developers.com/mot...tock-flashable-t-mobile-t2773675/post53177612
The GSM Developer Edition uses the same ROM as the T-Mobile variant. If you are referring to the VZW Dev Edition, you'll have to wait a little longer as it has not been released yet.
Click to expand...
Click to collapse
Thank you for the fast answer!
Unfortunately my phone is a Brazilian XT1058, with the bootloader unlocked. The GSM DE is XT1053. It seems that I must wait...
rodpp said:
Thank you for the fast answer!
Unfortunately my phone is a Brazilian XT1058, with the bootloader unlocked. The GSM DE is XT1053. It seems that I must wait...
Click to expand...
Click to collapse
Agreed, you should wait. The XT1058 is not a developer edition (only XT1053, as you have stated). Although some folks have flashed the XT1053 rom on their XT1058 (with unlocked bootloader), we haven't received confirmation that LTE or HSPA/HSPA+ work. Only that calling and 2G data do indeed work with the XT1053 rom on an XT1058.
It won't be too long....will be worth the wait.
Good Luck
samwathegreat said:
Agreed, you should wait. The XT1058 is not a developer edition (only XT1053, as you have stated). Although some folks have flashed the XT1053 rom on their XT1058 (with unlocked bootloader), we haven't received confirmation that LTE or HSPA/HSPA+ work. Only that calling and 2G data do indeed work with the XT1053 rom on an XT1058.
It won't be too long....will be worth the wait.
Good Luck
Click to expand...
Click to collapse
Yes, I´ll wait. For the moment I will do a factory reset because sometimes my phone is very slow, the wifi tethering is unreliable, etc. Probably because I installed a lot of Xposed modules, apps, etc.
Re: 4.4.3 camera update
Wondering if anyone who has the update has tried out the camera, if it's improved. That would probably be the biggest benefit for me I think from the update. The pause on video is a very nice addition, was surprised it wasn't there originally.
Will be eager to hear about the camera, or see any sample posts/comparisons with the previous version
Sent from my XT1058
Notice NO word about a fix for battery. I dont know about anyone else but back in November when I bought my XT1055 USC I unlocked BL on 4.2.2 and had Amazing battery life. 4.4 and 4.4.2 have been a major disappointment battery wise. IMHO
Sent From My Motorola Flagship!
This update fixed my bluetooth issues with my Sony MW600 where the audio connection would cut out after I made or received a phone call. I'd have to disconnect and reconnect. After the update, my bluetooth audio stays functional after a call is made or received.
Battery life for me appears to be better. I've consistently reached between 4-5 SOT for me. Up from 3.5-4 SOT right before the update.
M973 said:
Re: 4.4.3 camera update
Wondering if anyone who has the update has tried out the camera, if it's improved. That would probably be the biggest benefit for me I think from the update. The pause on video is a very nice addition, was surprised it wasn't there originally.
Will be eager to hear about the camera, or see any sample posts/comparisons with the previous version
Sent from my XT1058
Click to expand...
Click to collapse
First photo 4.4.2,
Second photo 4.4.3
{
"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"
}
First photo 4.4.2, (front camera low light)
Second photo 4.4.3 (front camera low light)
View attachment 2784329
View attachment 2784330
I've been checking a lot but still no update. How long will the update rollout for all XT1053?
Sent from my XT1053 using Tapatalk
omias said:
First photo 4.4.2,
Second photo 4.4.3
View attachment 2784321
View attachment 2784322
First photo 4.4.2, (front camera low light)
Second photo 4.4.3 (front camera low light)
View attachment 2784329
View attachment 2784330
Click to expand...
Click to collapse
It does look improved for low light and focus I think
Thank you
Are there any added features to the camera app after the update? Is the phones battery life noticeably better?
success2be said:
I've been checking a lot but still no update. How long will the update rollout for all XT1053?
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
same with me since they announce the update. but just right now, when I checked there's um update. Im downloading it right now. maybe u can try to check it as well.
Sent from my XT1053 using XDA Premium 4 mobile app
ryuben2k said:
same with me since they announce the update. but just right now, when I checked there's um update. Im downloading it right now. maybe u can try to check it as well.
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, just got it too after lunch. Hopefully the mobile data bug is truly fixed.
Sent from my XT1053 using Tapatalk
Has Motorola incremented the bootloader version with the 4.4.3 update?
4.4.2 had 30.B4
Thanks for the pics..
Is the first set of photos with flash?
Please post your general impressions about the camera update in various conditions. Is there a significant improvement in image quality?
Steve-x said:
Has Motorola incremented the bootloader version with the 4.4.3 update?
4.4.2 had 30.B4
Click to expand...
Click to collapse
Same !! 4.4.3 has 30.B4
But...... surprisingly I can't downgrade to 4.4.2 (I wanna flash Brasil retail 4.4.3)
omias said:
Same !! 4.4.3 has 30.B4
But...... surprisingly I can't downgrade to 4.4.2 (I wanna flash Brasil retail 4.4.3)
Click to expand...
Click to collapse
Did you try JUST flashing gpt.bin & motoboot.img, then reboot back into bootloader & flash the rest of the images? Since the bootloader version is the same, there is no reason you can't downgrade.
By flashing the partition and motoboot, THEN rebooting back to bootloader, it should solve the gpt.bin mis-match.
in bootloader mode:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
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
If you do in that order, it should work.

International Moto Maxx 5.1 official update (Non Droid Turbo)

Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Kiwironic said:
Ok, I know what you're thinking, 5.1 thread, again???? No it's not.
This is for Non Droid Turbo devices, non US Verizon. So Moto Maxx, Latin America devices such as the XT1225
I am currently on official 4.4.4 and I have already opt in for the Moto Feedback Network, so I should get the Soak test update when available.
So let's keep this threat updated about 5.1 updates for our international Droid Turbo variants.
And by the way here are the DROID TURBO - Android™ 5.1 Lollipop - Release Notes
Click to expand...
Click to collapse
Did you receive the survey or something? Or are you just being proactive and already creating a topic for when it happens?
Proactive mate, I have already singed up for the program and waiting for the soak for the international version.
Here we can follow updates about different variants of the phone (except for the main Droid turbo USA branch), who gets Soak, or official and news regarding that. I am using a PR XT1225, stock firmware and unrooted sadly due to corporate software.
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
GeodudeFFP said:
This is the thread I need...waiting like you. I know we could root and stick L on it, but I want to see what develops first (and KK has been fine for me). But hopefully something will develop soon.
Click to expand...
Click to collapse
You're lucky you have that option, I don't as I have to use corporate software and cannot be rooted (let's not start talking about root cloaking etc as it didn't work for me)
Let's keep this alive with updates and share stories and we should be fine, I am assuming since Droid US has got 5.1 it won't be far for us. I would give it a month or two.
People keep saying that Droid turbo and Moto Maxx are left behind but the reality is, we are getting the 5.1 update at the same time as the Moto X so we should use the Moto X as an indicator. I think once Moto X (international version) gets the official 5.1 update (currently in Soak testing as the Droid Turbo) we will get it as well.
I think some people won't even have to wait. Tomorrow Motorola will release a downloadable file of Droid Turbo 5.1 for use with RSD lite, and since the Droid Turbo KK worked on Moto Maxx (since it's bootloader can be unlocked), I'm betting this one will too, but with some adjustments (like no flashing the rádio partition/flashing the intl rádio partition afterwards)
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Kiwironic said:
That might work, but I won't risk it. I would wait for the official OTA, I have already returned 100% stock. I would have totally gone for it if I didn't have my work apps complications.
Click to expand...
Click to collapse
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
DarkLey said:
The apps are a problem indeed. I'll wait for the oficial release, then go backup to KK, restore my stuff with titanium and update.
Click to expand...
Click to collapse
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Kiwironic said:
Titanium no go bro, remember I don't have root anymore. :crying: :crying:
Click to expand...
Click to collapse
I do remember, for you it's really a no go if you want/have to keep the apps/data. Rootjunkysdl already have the OTA file, I'm backing up now to test my hypothesis.
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Kiwironic said:
Well I can justify asking for a new access code for my corporate apps after full wipe, but if something goes wrong with root / backup or installing the OTA as Zip my device will be banned. Can't take that risk. So I will have to wait for official or Soak OTA.
But please let us know how that goes for you. Which device do you have? is it a PR XT1225 ?
Click to expand...
Click to collapse
BR XT1225. One time I flashed the 4.4 Stock ROM for the Turbo in my device and it worked allright, and since this time I will just do the same then update, I think it'll work the same. Still backing up (a lot of data here).
Keep us updated mate.
Here are some news:
http://www.tudocelular.com/android/noticias/n56970/droid-turbo-moto-maxx-android-5-1-lollipop.html
How did it go??
Kiwironic said:
How did it go??
Click to expand...
Click to collapse
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
:fingers-crossed: Hope it goes well, and thanks for the link.
Hope to see ;
İncreased earpiece and speaker volume.
Better camera
Better calibrated screen for a little colder and more brightness.
Fix memory leak
and i am done.
Sent from my XT1225 using XDA Free mobile app
And better battery performance too
DarkLey said:
I haven't tried everything yet because I'm restoring my phone from a hardbrick.
My tries and findings so far:
First hypothesis) Flash KK service ROM KDF21. Directly: I knew it wouldn't work from the begining, since the frequencies for the radio cell are different, but tried anyway. Managed to update to Lollipop (KK -> KK VoLTE -> KK something -> OTA Lollipop) but without cell signal it's useless
Second hypothesis) Flash radio partition from RETBR Lollipop over Droid Turbo Lollipop OTA: didn't work too, don't know exactly the reason.
Third hypothesis) Flash Droid Turbo KK over RETBR KK, BUT without the radio partition, then update: worked till I tried to update (somebody already posted that flashing Droid Turbo KK without flashing radio over RETBR KK works). The system won't update probably because the VoLTE/Advanced Calling update needs to modify radio and finds a different radio partition.
Fourth hypothesis) To be tested yet ---- Update Droid Turbo KK to the latest (after VoLTE), flash radio partition from RETBR KK, then update with Droid Turbo LP OTA: haven't tried this yet because when I was flashing RETBR KK again I bumped at the cable and it was already faulty, so I have to unbrick my device to try again and I'm gathering the stuff to do that (no tutorial available, maybe I'll put something together sometime)
Edit: nvm, found this just a couple threads below: http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
Wow. You are brave!
I'm happy right now with CM 12.1 (5.1.1 Lollipop on my two XT1225 phones. I'm actually in Brazil right now for two weeks, using them.
Hope 5.1 files Motorola releases will help for custom ROMs for our phones.
When Motorola does release 5.1 for the XT1225 (Moto Turbo and international Moto Maxx), the kernel source code is the main thing, but won't come for awhile.
First it's the OTA, then the full image, then a month or so later the kernel code. At least that seems to be the pattern.

Feburary Soak Test

So I just got a email for a soak test, wonder if it would block sunshine again. Luckily I already unlocked by mine.
zys52712 said:
So I just got a email for a soak test, wonder if it would block sunshine again. Luckily I already unlocked by mine.
Click to expand...
Click to collapse
A further reminder to spend the money for sunshine now if you have any desire for an unlocked bootloader. Do not cry here if you take this soak or the ota and can't unlock if you had the opportunity to do so now.
Interesting. Maybe they'll throw us a bone and actually give us some security patches besides the one that stops Sunshine from working.
$10 says it's just a security patch rushed out to block Sunshine. So, EVERYBODY will now rush to install it before unlocking their bootloader.
Motorola Droid Turbo to receive Soak Test; could a surprise Nougat update be on the way?
http://www.phonearena.com/news/Moto...-surprise-Nougat-update-be-on-the-way_id91284
If you own the DROID Turbo, don't get your hopes up too high. These type of surprises rarely ever happen. Additionally, the fact that Motorola wants to rush this Soak Test probably means that the update contains something less earth shattering than a new Android build. Instead, it might offer a few bug fixes or the latest Google security patch.
Click to expand...
Click to collapse
koftheworld said:
A further reminder to spend the money for sunshine now if you have any desire for an unlocked bootloader. Do not cry here if you take this soak or the ota and can't unlock if you had the opportunity to do so now.
Click to expand...
Click to collapse
If we already have bought/used sunshine is there any need to redownload and use it again before/after taking the OTA?
5538dcf5 said:
If we already have bought/used sunshine is there any need to redownload and use it again before/after taking the OTA?
Click to expand...
Click to collapse
If your xt1254 (Verizon Droid turbo) has an unlocked bootloader via the sunshine app before now, then you are safe and it is not necessary to purchase sunshine again.
It is best practice not to take OTA's ever, if you prefer having root access to your phone.
RL_Wells said:
If your xt1254 (Verizon Droid turbo) has an unlocked bootloader via the sunshine app before now, then you are safe and it is not necessary to purchase sunshine again.
It is best practice not to take OTA's ever, if you prefer having root access to your phone.
Click to expand...
Click to collapse
Right. That doesn't mean you can't ever install UPDATES. Just wait until the stupid people take the OTA, see what it does.
Then the update will be posted here in XDA -- in many places and you can install them manually. Like the 6.0.1 Marshmallow firmware update. It's posted here in XDA as:
the full raw update,
a TWRP flashable version, (flashed with RSD or fastboot)
and was turned into a debloated, tweaked ROM version.
All which could be installed by people with unlocked bootloaders. The latter two could be installed via TWRP custom recovery.
There was never any reason to take the unknown OTA from Verizon, and never will be a reason to do so. If an OTA from Verizon is useful in any way, many, many versions will be posted here with expert commentary on what it does, how to install it. Early version of the 6.0.1 Marshmallow OTA bricked Droid Turbos which were encrypted. Verizon/Motorola stopped the OTA for several days. There's NEVER any reason to be the guinea pig for Verizon's incompetence. It's not like they didn't have enough time to test the firmware! The XT1225 got the SAME Marshmallow back in July 2016.
ChazzMatt said:
Right. That doesn't mean you can't ever install UPDATES. Just wait until the stupid people take the OTA, see what it does.
Then the update will be posted here in XDA -- in many places and you can install them manually. Like the 6.0.1 Marshmallow firmware update. It's posted here in XDA as:
the full raw update,
a TWRP flashable version, (flashed with RSD or fastboot)
and was turned into a debloated, tweaked ROM version.
All which could be installed by people with unlocked bootloaders. The latter two could be installed via TWRP custom recovery.
Click to expand...
Click to collapse
Question about the debloated, tweaked ROM version...what difference will I notice versus stock? Is there anything that doesn't work in the ROM?
Everytime sunshine finds an exploit that unlocks Droid Turbo's bootloader Verizon gives us a new update..
Coincidence? I think not.
Dabrador said:
Question about the debloated, tweaked ROM version...what difference will I notice versus stock? Is there anything that doesn't work in the ROM?
Click to expand...
Click to collapse
It's gotten enthusiastic reviews from users, but would be better for you to go to that link and read the op (first post) and then read the last few pages of comments. Not all the pages, but at least the last 5 or 6.
A couple of us already told you about it in the other thread:
ChazzMatt said:
I know you don't want a "ROM", but you might consider ComputerFreak274's stock-based ROM. It's just de-bloated, tweaked stock Verizon Motorola Marshmallow firmware. Has audio boost and some other stuff too -- battery tweaks, speed tweaks, cache tweaks, etc.
If you are a Verizon user, right now this is the only "ROM" that lets you keep VoLTE and Wi-Fi calling on Verizon.
You can still install Xposed with this, he tells you how to do it in his op.
I'm on Resurrection Remix Marshmallow myself, so I'm not suggesting it because I use it (I have XT1225, not XT1254). I'm suggesting it because it's basically stock firmware the way Verizon/Motorola should have released it. It's a "ROM" for XT1254 Verizon users who don't want full custom ROMs.
Click to expand...
Click to collapse
Claps1775 said:
Only xposed I have install is the YouTube add block . I have gravity box for other tweaks. I am on CFs ( ComputerFreak274) 1.06 mm ROM. I like his work. Check it out.
Click to expand...
Click to collapse
Has anyone taken the Feb soak? Anything interesting?
Just got it, it's only a security update. You can check the Droid Turbo Reddit for confirmation, a user there has the same results.
Confirmed by Verizon: https://www.verizonwireless.com/support/droid-turbo-update/
Also, I'm downloading it now, and I'm not part of the soak test. I'll capture the OTA and post it shortly.
Alienite said:
Just got it, it's only a security update. You can check the Droid Turbo Reddit for confirmation, a user there has the same results.
Click to expand...
Click to collapse
A "security update" to block Sunshine? [emoji14]
Now that Sunshine unlocks 6.0.1 bootloader?
Figured as much. The people speculating Nougat were delusional. Lenovo/Motorola hasn't even given all the Quarks Marshmallow yet.
My response to a post from this morning in another thread, but relevant to this discussion...
cod3name47 said:
Any idea about nougat update for Moto Maxx?
Click to expand...
Click to collapse
Nougat? Motorola hasn't even released stock Marshmallow for all the Moto Maxx phones yet! The U.S. Moto Maxx XT1250 (clone of the XT1254 Droid Turbo in every way -- FCC ID, radio bands) is still on 5.0.2 Lollipop!
None of the Quarks are on the Motorola Nougat list, which was released months ago by Motorola/Lenovo. Would be very unusual to give an unannounced Noguat 7.X update, since Motorola/Lenovo seems to want to do less work -- not more -- regarding updates to their customers.
Motorola announced Marshmallow for Quarks October 2, 2015. WHEN did they deliver it?
XT1225 Moto Maxx/Moto Turbo got it in July 2016 (9 months later),
Took Motorola until December 2016 (13 months) to actually give it to the Droid Turbo XT1254 --
U.S. Moto Maxx still does not have Marshmallow (16 months and counting).
If you want Nougat, unlock your bootloader and flash any of the custom Nougat 7.X ROM we have available. Here's the current custom Nougat (7.x) Quark ROMs to choose from.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
[ROM][7.1][All quark] crDroid Android
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI][quark]
OTA posted. https://forum.xda-developers.com/dr.../ota-marshmallow-build-mcg24-251-5-5-t3565697
Hahahhahaha I know they are lazy....Motorola was good untill it was solo company!!! Lenovo ruined it!!
they won't keep us current, but they can bang out an update to patch sunshine, WTF? it's like they want to say FU to us for using this phone..
rhcreed said:
they won't keep us current, but they can bang out an update to patch sunshine, WTF? it's like they want to say FU to us for using this phone..
Click to expand...
Click to collapse
Well to be fair, the android security patch version is now dated January 2017, so at least there's that.
Also, at long last, we are finally protected from the Stagefright vulnerability :laugh:
DD?
ChazzMatt said:
A "security update" to block Sunshine? [emoji14]
If you want Nougat, unlock your bootloader and flash any of the custom Nougat 7.X ROM we have available. Here's the current custom Nougat (7.x) Quark ROMs to choose from.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
[ROM][7.1][All quark] crDroid Android
[ROM][7.1.1_r9][OFFICIAL] AospExtended ROM V3.1 [OMS/DUI][quark]
Click to expand...
Click to collapse
Still running (unlocked) stock, what do you recommend as a DD? I really just want it to work and have solid battery life (why I bought this phone 2+ years ago). Is there one of these seen as the most stable? (My days of finding a decent rom for my S3 were a nightmare, no one rom was stable enough to "just work") Thx!
rhcreed said:
Still running (unlocked) stock, what do you recommend as a DD? I really just want it to work and have solid battery life (why I bought this phone 2+ years ago). Is there one of these seen as the most stable? (My days of finding a decent rom for my S3 were a nightmare, no one rom was stable enough to "just work") Thx!
Click to expand...
Click to collapse
Any of the top three Nougat ROMS on the list have very high reviews. You can go to those threads and ask questions, and see other Droid Turbo owners.
#2 and #3 are maintained by Droid Turbo owners who use Verizon, if that makes a difference to you. But all three are excellent and many Droid Turbo owners are using all three.
[ROM][All Quark][7.x] Resurrection Remix
[ROM][UNOFFICIAL]AOKP 7.x For All Quark
[ROM][Quarks][LOS/CM 14.1 Unofficial][7.1.x][2016-12-30] (hybrid of CM14 and Resurrection Remix)
However, if you need Verizon VoLTE, then you should go with a debloated, tweaked Marshmallow ROM based on stock Motorola Verizon firmware. See below. It's not Nougat, but right now only stock Motorola Verizon firmware or a ROM based on stock Verizon firmware can get Verizon VoLTE on this phone -- until a dev discovers the secret handshake. (ZTE has discovered the secret handshake for Verizon VoLTE. Now a dev just needs to figure out what they did.)
_________
@computerfreek274 has now released a Marshmallow ROM for the Droid Turbo XT1254 based on the Verizon's belated Marshmallow firmware. He has debloated it, tweaked it. It has Verizon voicemail app, Verizon VoLTE (only works on Verizon), Verizon Wi-Fi calling (only works on Verizon), some volume boost, and battery saving tweaks.
* Computerfreek274_MM_1.0.4 Marshmallow 6.0.1 Stock rooted VOLte Debloated
http://forum.xda-developers.com/droid-turbo/development/computerfreek274mm1-0-android-6-0-1-t3503634

How to upgrade to .67 version ?

Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
Hi ! I was using custom roms on my phone then I switched back to stock nd also I relocked my bootloader but after that I cant update it to .67 version I am on .35 version. I am from India and everyone has received OTA for .67 version but mine doesnt shows any update. Any help ?
Click to expand...
Click to collapse
Same problem here.
You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.
echo92 said:
You'd have to be on the NPN25.137-15 firmware to have received the .67 update - if you're on the retin software channel, I think the .35 version is the incorrect one for your channel (.35 is for US devices, if I recall). Therefore, you'll likely not get any updates, and if you were to flash the NPNS25.137-35-5 update, may mean you cannot downgrade in future.
If you're on the retin channel and want the .67 update, then unfortunately you'll likely have to unlock your bootloader (wiping your device) then attempt to flash NPN25.137-15 (do your research first and ensure this does not brick your device), then you should be able to update to NPN25.137-67. As far as I know, there is no fastboot ROM currently for NPN25.137-67 so re-locking the bootloader is not possible at the moment.
Click to expand...
Click to collapse
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
I downgraded my phone from .35 to .15 version and now I have received OTA and have successfully updated to .67 version.
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
Please provide instructions for this, I am unable to downgrade.
earlycray said:
Please provide instructions for this, I am unable to downgrade.
Click to expand...
Click to collapse
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.
deepu28792 said:
Its really simple. Just download the firmware .15 from the link below and flash it. If you have already re-locked ur bootloader thn flash the full firmware and if not yet unlocked use the commands provide in the thread. The .15 version shows for Brazil but it works with our Indian version too. Try it I did the same.
https://forum.xda-developers.com/showthread.php?t=3638835
Press thanks if I helped you.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am receiving this error. I was previously on NPNS25.137-35-5.
earlycray said:
I am receiving this error. I was previously on NPNS25.137-35-5.
Click to expand...
Click to collapse
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk
deepu28792 said:
then you cant downgrade. I thought you were on .35, I have read it somewhere that if u r on .35-5 then you cannot downgrade
Sent from my Moto G (5) Plus using Tapatalk
Click to expand...
Click to collapse
I will have to wait for full image of -67 to upgrade, correct ?
earlycray said:
I will have to wait for full image of -67 to upgrade, correct ?
Click to expand...
Click to collapse
I'm not even sure if you can flash the NPN25.137-67 image even, MarckozZ downgraded from NPNS25.137-35-5 to NPN25.137-15 and attempted to take the OTA to NPN25.137-67, which hard bricked their device. https://forum.xda-developers.com/showpost.php?p=73029820&postcount=70
Though they were able to recover their device, it looks like updating is very risky/not possible after the recovery: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Now, the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5 and let you flash the rest of the OS, but that's asking for trouble when an OTA arrives - hopefully the OTA scripts would check for a bootloader/GPT mismatch, but they may not and you could run into a hard brick.
echo92 said:
the fastboot of NPN25.137-67 might not let you flash the GPT and bootloader over the NPNS25.137-35-5
Click to expand...
Click to collapse
Wow. I dun goofed. What are my options at this point? Also, could you kindly please explain the above ?
earlycray said:
Wow. I've done goofed. What are my options at this point? Also, could you kindly please explain the above ?
Click to expand...
Click to collapse
As I understand it, fastboot has checks built in that communicate with the bootloader and verify whether the GPT/bootloader of the firmware you're attempting to flash can be flashed. If you have a newer bootloader on your device, then your bootloader may refuse to permit the flash of the older bootloader (especially with the NPNS25.137-35-5 update, which appears to have a critical security bug fixed in the May 2017 patch, so downgrading would allow you to re-open that bug, which Motorola wouldn't want).
Now, you can get around this, in theory, by omitting GPT and bootloader from your fastboot flash, so fastboot may flash the rest of your system. However, now you'll have a NPN25.137-67 system, but a GPT/bootloader from NPNS25.137-35-5. Though this should run, it becomes very risky if you choose to install an OTA and forget you have this mismatch; the OTA will think you have the NPN25.137-67 firmware and patch accordingly, which may seriously corrupt your bootloader. In that case, you'll have to use a blankflash to recover your device (if it works) and be unable to recover your data, unless it was held on a SD card mounted in portable storage. I've seen similar scenarios occur with the Moto G4 (luckily we've just got a new blankflash to recover from the June 2017 security patch) and with the Moto Z Play.
In summary, you could flash the NPN25.137-67 firmware when it comes out, but the mismatch makes updates very risky - I personally wouldn't use the fastboot updates in this situation. You might wish to look into the TWRP flashables of the NPN25.137-67, as they'll update the system side of things (and most if not all the functions of your device should work as though you were still on stock NPN25.137-67), but without the risk of bricking your device. Granted, you'll have to unlock and flash TWRP in this situation though, and you will no longer be able to flash OTA updates, though hopefully the TWRP flashable maintainer will update the TWRP flash file to the newest OTA.
I'm not aware of other options besides keeping an eye out for NPNS25.137-35-5 updates, unfortunately, as your device is off the official update path Later on, Motorola may unify firmware updates into one global file, but for the time being, just be careful (and also be aware that the patch situation is a bit confusing!). On the other hand, at least you've got a May security patch
If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.
earlycray said:
If I simply stuck to the current firmware, what would happen? The NFC chip appears to be working even tho this is the us? Model.
Click to expand...
Click to collapse
Hang on, which model of the Moto G5 Plus are you using?
Cause depending on the model, you might actually be on the right firmware and not need the -67 update (which is usually only for retin, Indian retail) devices...
To clarify, as far as I know:
retin (I think retla too?) devices should be on NPN25.137-67 (March 2017 security patch)
retus devices should be on NPNS25.137-33-5 (May), NPNS25.137-35-5 (May) or NPN25.137-43-5 (Verizon specific, March)
reteu devices should be on NPNS25.137-33-5 (May)
From your previous posts you've got a XT1685?
That is correct. However it was purchased in Australia. And judging by some Australian tech forums the latest fw is -67.

Moto G5 Plus Software Update

My Moto G5 Plus is telling me that my software is up to date, yet it's still running Android 7.0, but more importantly the security patch level is 1/1/17. I don't know about major OS updates, but there MUST be at least some updates out there that I'm not getting. Can someone link me to somewhere where I can find a .zip files for all OTA updates, so I can just flash the update and then flash Magisk again to retain root? Thanks!
You are probably not receiving OTA updates since you've rooted your phone, right? There was no major updates but there was few security patches this year. Which model exactly you have? That's gonna help in providing you correct links...
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
nlinecomputers said:
I too feel like I am not on the latest version. I have two XT1687 units. I got two updates minutes after power on but I only at the March 1st update. Build NPN 25.137-43-5. Are there newer builds for the US version phone?
Click to expand...
Click to collapse
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
acejavelin said:
NPN25.137-83 with an August 1 security patch is the latest in the US... unless you are on Verizon, I think they are still on an older build due to voice quality issues.
Click to expand...
Click to collapse
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
nlinecomputers said:
I am on Verizon so that must be it. One more reason to move on to another carrier. Which is partly why I got the phones to begin with.
Click to expand...
Click to collapse
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
acejavelin said:
Problem is your stuck regardless of carrier now until they release an update FROM NPN25.137-43-5 to whatever... an OTA update is a differential update, meaning you have to have X to move to Y, so the update you just have to wait anyway.
Click to expand...
Click to collapse
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
nlinecomputers said:
I don't quite follow. Are you saying the build I am running is for Verizon only? If I put in T-Moblie sim cards in I would STILL not get the update?
Is there a way to flash the latest build in whole, not a delta upgrade?
Click to expand...
Click to collapse
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
---------- Post added at 05:00 PM ---------- Previous post was at 04:56 PM ----------
FamilyGuy0395 said:
I am using a rooted Moto G5 Plus that I bought from Amazon (no ads, 64 GB ROM & 4 GB RAM) with the stock software it was shipped with. As far as I understand, with a rooted phone, to update your software you just need to flash (1) the latest OTA update .zip file, and then (2) flash the root package .zip file again to retain root. However, unlike other phones, I can't find these OTA software update .zip files ANYWHERE. Can someone please help?
Click to expand...
Click to collapse
Sort of... OTA files can only be flashed on a pure stock system, no root, no TWRP, no Xposed, nothing changed in system, no removed packages, etc. If the OTA script even detects that /system was ever mounted R/W it can fail (I don't know if Moto goes that far).
To flash an OTA you must restore your stock ROM completely (/system, /boot, and any other system level partitions), and restore stock recovery, and all versions must match or the OTA script will crap out with an error.
The OTA files are out there, on this forum in various threads... you can find them along with instructions on how to apply them to rooted and stock systems.
acejavelin said:
Yes, that is what I am saying... Verizon had some real issues with voice quality initially, and several Verizon "specific" software updates went out to address that issue, and only to Verizon users, the rest of us (such as myself on AT&T) never got those updates.
You have to wait until Moto makes an update to the latest version from your version -AND- Verizon accepts it and allows it to be pushed out. Switching SIMs now won't matter since there is no update from your version to the latest out there, in fact, it could actually delay you getting the update because you are not on Verizon so Moto's update server may not offer it to your IMEI until it is available for pull (rather than push, which is all we have seen so far)
We do not have the full image of the ROM either, so flashing it is not possible.
The kicker is that the latest version supposedly fixes all the Verizon specific issues too. :/
Click to expand...
Click to collapse
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
nlinecomputers said:
Well ****. I screwed up then. I got these phones to leave Verizon and all that controlled rollout BS.(Had Droid Turbo before this) Didn't know that even on unbranded phones they would still interfere So can you rollback to the shipping rom?
Click to expand...
Click to collapse
Oh yeah... Moto's level of doing what the carriers "recommend" or whatever you want to call it, is ridiculous lately.
Good example is Nougat for the Moto X Pure Edition, if you are on Sprint or US Cellular you got it 2 months ago, but Verizon, AT&T, and T-Mobile users still haven't seen it. Except many users have figured it out, pop in a Boost Mobile SIM (not even activated) and it will grab the update almost immediately, let it apply, then swap your original SIM back in and enjoy some Nougat goodness. However that device never had a specific version for a certain carrier. Still today probably 80% of users of that FLAGSHIP device still haven't gotten an update that we know was completed in June/July, due to "partner approvals" or some such BS.
All these updates still come directly from Moto and their servers, but they are doing what the carriers tell them and only allowing it to certain devices... This has vaguely been admitted to by the mods on the official Lenovo support forums.
Honestly, many smaller brands with a history of poor update frequency get better update support than Moto's these days... My son's Axon 7 Mini already has 7.1.1 with the September update for BlueBourne, he got it the third week of September, and gets on every 3 months like clockwork. My faith in Moto is diminishing quickly, I gave them the benefit of the doubt on my last two (Moto X Pure Edition and Moto G 2015) because they were kind of transitional device during the Google-Lenovo switch over, and although my Moto G5 Plus is supported a little better I believe it is just because it is newer and not because Moto got better.
Chances this will be last Moto device? Let's just say this could be my last Moto device, and I have been a big Motorola fan for many years.
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Can anyone link me where to find OTA updates for Moto G5 Plus and, if necessary, instructions? I don't see why the instructions would be any different from the OnePlus 5, other than Motorola making it harder on purpose.
FamilyGuy0395 said:
@acejavelin That can't be true for every phone. On the OnePlus 5, I am able to flash an OTA update through TWRP and then flash the root package and everything works fine.
Click to expand...
Click to collapse
Never said it was true for every phone or manufacturer, but that is the way it is with Moto devices... You cannot flash an OTA with TWRP, the script checks (among other things) the recovery and will fail if it doesn't have the correct signature, same with the modems, bootloader, partition table, and things in /system. Moto OTA updates are VERY picky and will fail at the drop of a hat on a device that is not purely stock.
The only work around, that works in SOME cases with Moto devices, is using FlashFire by Chainfire, but that is hit and miss, depends on what is updated.
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Karlinski said:
There is a thread here that has TWRP flashable OTA updates. I flashed myself to the latest USA version just this week using them...
Click to expand...
Click to collapse
Do you have a link to this thread? I am curious how the modems, partition table, and bootloader updates are handled since TWRP doesn't have the correct signature to write to these partitions. I can see where it could maybe update the boot and system partitions if they were extracted from the ROM, even if they are differential deltas, but my guess is that a "TWRP flashable" OTA is mearly an extract of a blank device's boot and system partition or just he changes, and packed into an OpenRecovery script, and not the "real" OTA file.
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Karlinski said:
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Q9Nap said:
Do NOT attempt to apply standard OTAs over these builds; they will fail.
Click to expand...
Click to collapse
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
acejavelin said:
Ahh... OK... Read through those, can see they are ROM's that someone created from the OTA's and factory images, not the actual OTA's and cannot be used with a locked bootloader, . And if you read through it, they don't upgrade some partitions, like modems, and they have modified boot images that disable DM-Verity and force disable encryption...
They even clearly say:
Don't get me wrong, I appreciate any developers work, but these are ROMs, just not very custom as they are essentially stock with near no modifications.
Click to expand...
Click to collapse
The TWRP flashable stock builds DO upgrade the modem.
As stated in the OP, the only partitions NOT upgraded are gpt and bootloader.
I didn't omit these partitions because they can't be written; I omitted them to prevent potential issues for people who really don't know what they're doing.
Disabling dm-verity is required due to some partitions unavoidably losing their oem signatures during the conversion process.
Disabling force encryption is practically required, as TWRP seems buggy with it enabled.
The intended purpose of these builds is to provide a dead simple (and safe) way for users to return to stock.
I have linked useful tools at the bottom of the OP for those interested in making their own modifications to these stock builds.
Hope this helps :good:
Q9Nap said:
Hope this helps :good:
Click to expand...
Click to collapse
It does actually, thank you... Obviously I have a lot to learn about the differences between current devices and older Moto devices I am used to working.

Categories

Resources