rooted, stock rom stuck to 1st Dec 2017 security update, no OTA

[maann]

Hi folks,
tried to do a rapid lookup and it seemed to me not to find a similar post. I apologise if I looked superficially.

Well: I rooted and flashed a stock rom (nps 26.116-61 security patch 1st Dec 2017), flashed modem from another working rom

PROBLEM: It does not roll out any security update till now , nor updates of firmware (maybe it's the same)

Is it because it is rooted?
If I unroot (seems not trivial) will i be able to get OTA again?

many thanks :fingers-crossed:
regards

 

[pizzaboy192]

Hi folks,
tried to do a rapid lookup and it seemed to me not to find a similar post. I apologise if I looked superficially.

Well: I rooted and flashed a stock rom (nps 26.116-61 security patch 1st Dec 2017), flashed modem from another working rom

PROBLEM: It does not roll out any security update till now , nor updates of firmware (maybe it's the same)

Is it because it is rooted?
If I unroot (seems not trivial) will i be able to get OTA again?

many thanks :fingers-crossed:
regards

You'll need to flash back to stock and apply all OTAs before flashing ROOT, then also make a DD backup of the OEM partition because the current public version of TWRP backs up or restores the OEM partition wrong which breaks OTAs again.

Also, Moto seems to keep track of device serial numbers or something and won't send OTAs to devices that are rolled back. You'll need to use the offline OTA downloader and flash them using ADB (you can't just copy them to the device because the device is encrypted by default and the bootloader can't apply OTAs that way.

Here's the OTA doanload tool. https://forum.xda-developers.com/an...s-motorola-t3810863/post76954902#post76954902

 

[treyweez11]

Hi folks,
tried to do a rapid lookup and it seemed to me not to find a similar post. I apologise if I looked superficially.

Well: I rooted and flashed a stock rom (nps 26.116-61 security patch 1st Dec 2017), flashed modem from another working rom

PROBLEM: It does not roll out any security update till now , nor updates of firmware (maybe it's the same)

Is it because it is rooted?
If I unroot (seems not trivial) will i be able to get OTA again?

many thanks :fingers-crossed:
regards

What model do you have? Xt1806? Xt1804?

Sent from my XT1806 using Tapatalk

 

[maann]

What model do you have? Xt1806? Xt1804?

Sent from my XT1806 using Tapatalk

it should be xt1805. possible?

 

[maann]

You'll need to flash back to stock and apply all OTAs before flashing ROOT, then also make a DD backup of the OEM partition because the current public version of TWRP backs up or restores the OEM partition wrong which breaks OTAs again.

Also, Moto seems to keep track of device serial numbers or something and won't send OTAs to devices that are rolled back. You'll need to use the offline OTA downloader and flash them using ADB (you can't just copy them to the device because the device is encrypted by default and the bootloader can't apply OTAs that way.

Here's the OTA doanload tool. https://forum.xda-developers.com/an...s-motorola-t3810863/post76954902#post76954902

thanks very much. although OTA d'er didn't work

i actually discovered that root does NOT affect the no-more-OTA thing. It took me to flash EFS (to get imei back) to interrupt OTA (even if it seems to me that before flashing EFS, OTA were being recalled). Maybe it's just like your hypothese, i.e. that Motorola does not send OTA to unfaithful unblocking users. How sad is that? When you unblock it they make you "sign" that you cannot even sell the mobile! last Moto experience for me , highly probably!

 

[pizzaboy192]

thanks very much. although OTA d'er didn't work

i actually discovered that root does NOT affect the no-more-OTA thing. It took me to flash EFS (to get imei back) to interrupt OTA (even if it seems to me that before flashing EFS, OTA were being recalled). Maybe it's just like your hypothese, i.e. that Motorola does not send OTA to unfaithful unblocking users. How sad is that? When you unblock it they make you "sign" that you cannot even sell the mobile! last Moto experience for me , highly probably!

I forgot to mention that the OTAs tool only works in manual mode, and works best in the same folder as adb.exe

 

[maann]

I forgot to mention that the OTAs tool only works in manual mode, and works best in the same folder as adb.exe

i realized that, it does not work even in manual, i paste here debug log

APP: OTA Updater (build: 256 )
OTA Server (host): moto-cds.appspot.com
OTA Server user agent: com.motorola.ccc.ota

Request:
Request URL: 'https://moto-cds.appspot.com/cds/upgrade/1/check/ctx/ota/key/Moto%20G%20(5S)%20Plus/'
Request JSON: {"id":"ZY322G6KD3","deviceInfo":{"country":"US","region":"US"},"extraInfo":{"carrier":"reteu","model":"Moto G (5S) Plus","softwareVersion":"Blur_Version.26.306.12.sanders.retail.en.US"},"triggeredBy":"setup"}

Response:
Response status: 200
Response text: {
"proceed" : false,
"context" : "ota",
"contextKey" : "Moto G (5S) Plus",
"content" : null,
"contentTimestamp" : 0,
"contentResources" : null,
"trackingId" : null,
"reportingTags" : null,
"pollAfterSeconds" : 172800
}

 

[pizzaboy192]

i realized that, it does not work even in manual, i paste here debug log

APP: OTA Updater (build: 256 )
OTA Server (host): moto-cds.appspot.com
OTA Server user agent: com.motorola.ccc.ota

Request:
Request URL: 'https://moto-cds.appspot.com/cds/upgrade/1/check/ctx/ota/key/Moto G (5S) Plus/'
Request JSON: {"id":"ZY322G6KD3","deviceInfo":{"country":"US","region":"US"},"extraInfo":{"carrier":"reteu","model":"Moto G (5S) Plus","softwareVersion":"Blur_Version.26.306.12.sanders.retail.en.US"},"triggeredBy":"setup"}

Response:
Response status: 200
Response text: {
"proceed" : false,
"context" : "ota",
"contextKey" : "Moto G (5S) Plus",
"content" : null,
"contentTimestamp" : 0,
"contentResources" : null,
"trackingId" : null,
"reportingTags" : null,
"pollAfterSeconds" : 172800
}

You have a RETEU device but it is saying you have a country and region of US and a software version of US, as if something is wrong between what the device model number is vs the software it's running.

 

[maann]

You have a RETEU device but it is saying you have a country and region of US and a software version of US, as if something is wrong between what the device model number is vs the software it's running.

it may be actually! bought the device in Italy and flashed this stock rom from firmware repository (don't even know where it comes from!) what a moto-mess

 

[pizzaboy192]

it may be actually! bought the device in Italy and flashed this stock rom from firmware repository (don't even know where it comes from!) what a moto-mess

You've nailed it!

What's your model number? Let's get you on the correct firmware and get you up to date!

 

[maann]

You've nailed it!

What's your model number? Let's get you on the correct firmware and get you up to date!

thank you for your kind availability man! how can i retrieve model number? i'm -almost- sure it was xt1805

 

[pizzaboy192]

thank you for your kind availability man! how can i retrieve model number? i'm -almost- sure it was xt1805

https://mega.nz/#F!HY0BwK4B!pZi727WP46Mjz0zxVOdojQ!Kc0njQJR

This has folders with retgb, reteu, and retin. It looks like you have reteu, so download that, and run the same restore commands to get to June 1st security patch on firmware for your device.

 

[maann]

https://mega.nz/#F!HY0BwK4B!pZi727WP46Mjz0zxVOdojQ!Kc0njQJR

This has folders with retgb, reteu, and retin. It looks like you have reteu, so download that, and run the same restore commands to get to June 1st security patch on firmware for your device.

thank so much bro!

 

[maann]

quick question: are these two lines

fastboot erase modemst1
fastboot erase modemst2

really needed in flashing stock rom? thanks in advance

 

[pizzaboy192]

quick question: are these two lines

fastboot erase modemst1
fastboot erase modemst2

really needed in flashing stock rom? thanks in advance

Don't do those. Not necessary, and not safe to do unless you know you have a backup of your imei and efs partition

 

[maann]

Don't do those. Not necessary, and not safe to do unless you know you have a backup of your imei and efs partition

Done successfully. Imei recognized without flashing efs.
Is June 2018 last OTA? Cause both OTA upgrader and system information days system is up to date. It would be awesome if flashing this stock would bring OTAs automatically back. Thanks again!

 

[pizzaboy192]

Done successfully. Imei recognized without flashing efs.
Is June 2018 last OTA? Cause both OTA upgrader and system information days system is up to date. It would be awesome if flashing this stock would bring OTAs automatically back. Thanks again!

June 2018 is currently the latest available for all regions that is general release. There's soak test Oreo but it's best to wait for general release. You will get OTA since you're up to date with correct region now.