Database Develop

moto x testing unit upgrade

does anyone have any idea how to update a testing version of moto x to the latest update? every time i check for updates it says there are none available. it is an xt1053 with a kernel from june

If the bootloader is unlocked download one of the other firmware packages then upgrade

^ do you think I could do that in the stock recovery?
and point me in the right direction to download that?

raulgrande said:
does anyone have any idea how to update a testing version of moto x to the latest update? every time i check for updates it says there are none available. it is an xt1053 with a kernel from june
Click to expand...
Click to collapse
How did you end up with a "testing version" of the software?
Anyways - I imagine that if you flashed the original firmware that you would probably be able to check for an update and receive it. But I could be completely wrong and you could wreck your phone trying (standard disclaimer). This link might help you...
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite)

thepolishguy said:
How did you end up with a "testing version" of the software?
Anyways - I imagine that if you flashed the original firmware that you would probably be able to check for an update and receive it. But I could be completely wrong and you could wreck your phone trying (standard disclaimer). This link might help you...
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite)
Click to expand...
Click to collapse
bought it at a street market in the city.
do you think it's possible to flash the firmware from here
http://sbf.droid-developers.org/ghost_rcica/list.php
on stock android recovery?

raulgrande said:
bought it at a street market in the city.
do you think it's possible to flash the firmware from here
http://sbf.droid-developers.org/ghost_rcica/list.php
on stock android recovery?
Click to expand...
Click to collapse
The video tutorial I linked you to gives step by step instructions of how to do what you want to do. They even have a link to the files you mentioned. Did you look at the tutorial?

If it helps the xt1053 is the T-Mobile model. You could try flashing the T-Mobile firmware or unlock the bootloader to flash other versions.
Sent from My Moto X

[Q] Moto X stuck in bootloader screen after ota update

Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT

Did you downgrade your android system any time after 4.2.2?

It sounds like you've downgraded and now took an ota. It's written all over this section of xda that doing that on a Moto X is a guaranteed brick.
If this is the case, you'll want to look for the Resurrect your moto X thread in the general section.
Good luck!

victormagno said:
Hey guys!
After updating my rooted phone through OTA, it stucked in bootloader screen and every fastboot command I execute results in: FAILED (remote failure)
I tried everything I found and nothing solves the problem.
Please, someone help me!
C:\Fastboot+ADB>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.172s
Phone status:
Device is LOCKED (It was unlocked early)
Screen message:
downgrade security version
update gpt_main version failed
preflash validation failed for GPT
Click to expand...
Click to collapse
What Model X, what version does your bootloader say (2nd line of the FastbootAP/Bootloader screen), and what ROM are you trying to flash?
As suggested, please also be sure you are using Moto's fastboot, rather than stock fastboot from the Android SDK.

How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.

Hi, thank you all for your attention, but I solved the problem... I found a Verison Rom with the files I needed \o/.
I'm at work right now, but in home I'll post the solution to help who needs to.
Sorry, my english is awful.
Again, thank you!

nhizzat said:
How did your bootloader get relocked? The OTA didn't do it so I'm guessing you relocked it for some reason.
Click to expand...
Click to collapse
I've seen that happen a few times when some have tried to downgrade.

My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!

victormagno said:
My phone bricked when I tried to do an OTA update, after downgraded to 4.2.2. When the phone rebooted to compete the upgrade, it stuck on bootloader screen.
I downloaded this Verizon rom in link: h t t p : // sbf.droid - developers . org / download . php ? device = 0&file =9 40 (remove spaces)
and flashed its bootloader. After that, the phone was receiving commands. I restarted and it booted normally.
To solve the problem download this rom and execute: fastboot flash partition gpt.bin
I hope it help someone!
Click to expand...
Click to collapse
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.

one fraction out
KidJoe said:
I would suggest something slightly different.
I would say.. check the bootloader on your phone, and download the corresponding ROM for your model phone.
Bootloader version = rom version
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Just some model examples...
XT1060 = Verizon Wireless USA
XT1058 = ATT in the USA, Rogers Canada
XT1056 = Sprint in the USA
XT1053 = GSM Dev Edition, as well as the "Unlocked ships with xxx Sim" from Moto's web site (like T-Mobile, Net10, and others).
XT1052 = European, and some Asia.
So if your bootloader is 30.B4 and you have a GSM Unlocked (with T-Mobile SIM), then download and flash the 4.4.2 XT1053 rom. If the bootloader is 30.B7, and you have a Sprint X, download/flash the 4.4.4 Sprint XT1056 rom
And I would flash the entire SBF, not just parts because when GPT.Bin and Motoboot.img are mismatched from the rom on the phone, you can/will brick taking an OTA.
You can get the roms from -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
In other words, suggesting to flash the Verizon 4.4.4 rom like you are, might not work if you have a LOCKED bootloader and don't have a Verizon XT1060. Flashing the Verizon XT1060 GPT.BIN onto a European XT1052 with unlocked bootloader could cause other issues too.
Finally, flashing the GPT.BIN from a 4.4.4 ROM onto a phone that has the bootloader from 4.4.2 for example, will also cause issues.
Click to expand...
Click to collapse
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3

slash1432422 said:
:9
30.B4 = 4.4.2
30.B5 = 4.4.3
30.B6 = 4.4.4
30.B7 = 5.0
this was misleading my unbricking development (even has set me at a good path at first) xD i saw this at a chinese site, which i did not understand at all, but the following " 4.4.4 = 30.B6" so i could guess the next version has to be lollipop and i had to get GPT.bin from there so the partitions in my phone could restore, which they did, so my hard brick phone, now is unbricked, until the next time i flash something without think about consequences :3
Click to expand...
Click to collapse
Not sure where that list came from, but for every variant of the 2013 X I've seen, 30.B7 is the bootloader when 4.4.4. is the newest rom that was flashed on the phone.
After applying the 5.02 leaks for Brazil XT1058, and "Retail" XT1053 the bootloader was 30.BC.
Now, if you are saying that when attempting to unbrick its better to flash one version higher than the bootloader on your phone, that good as well. You have to flash equal or newer than what was on your phone when attempting to unbrick.

yeah probably
i'm probably wrong and i don't want to mislead anybody, so i'll say, that was my personal experience, you guys can google the c*ap out of it like i did (15 tabs+/- per browser)

Please help
I bought a unlocked pure edition moto x directly from Motorola. Powered on this past Tuesday. Didn't install sim card yet. Notified me Wednesday there was a update. I clicked OK. Went to work
come home and the phone was stuck on the M screen. Got it to the boot loader clicked recovery. Had the android guy laying down with the exclamation point. Wiped cache. That didn't work. Done a factory reset that didn't work. On the boot loader screen where the options are available it says device is locked. And software version it says modified. I never modified it. So now I have to return for a refund. But how would this of happened? And,what does it mean by modified? Called Motorola and I done everything they said to. do. I never down graded the os either.

Moto g2 stuck on boot loader screen while rebooting
hey guys.
so recently i installed an app called "kingroot" which helps enhance performance by rooting. Today my device ran out of battery and when i connected it to a charger, bootloader screen automatically appears and shows: 'boot-up failed'. I have not installed any custom ROM and the device was running stock ROM (6.0).
To be honest, I am not a developer and have no clue about this. all options shown in bootloader lead to a dead end. The battery won't charge and connecting it to my pc wasn't helpful either. All I want to do is run my stock rom, which doesn't seem to be happening.
Device: Moto G 2014 (dual sim)(India)
Need help Urgently.
thanks

[Q] [HELP]Probably bricked my XT1058 CA Rogers

Problem SOLVED! Android 5.1 stock ROM revived it! Thank you, Motorola and XDA!
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!

Try and flash tz and gpt from 4.4.4

mk1129 said:
Sorry, not sure if it's proper to repeat my cry here. But I'm having a quite similar situation to this post: [SOLVED]Bootloader bricked, recovered, but fail when running firmware
Mine is a XT1058 from CA Rogers. I unlocked the bootloader and played with Brazil stock roms, a CM11 snapshot rom, having no problems.
After I tried RETAIL-GB_GHOST_KLA20.16-2.16_cid7_CFC_1FF_v2.xml (4.4.2, i guess), things went wrong. No signal as I expected, but I screwed up with OTA 4.4.4 installed so I got the same stuck at Fastboot mode:
Code:
BL version: 30.B7
Device is LOCKED.
downgraded security version
update gpt_main version failded
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID Status 0x69
CustomerID error. Contact Dealer: 0xdead
No SP Partition found
Fastboot Reason: Invalid CID
I've tried mflash and RSD with 4.4.4 stock roms, but none of them worked, and all failed to write into the phone at Step 2 <step operation="flash" partition="partition" filename="gpt.bin":
XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF
Editing XML to skip the step with error didn't work. It failed to flash at every step. Any help will be appreciated!
Click to expand...
Click to collapse
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.

hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
I tried several 4.4.4 stock ROMs, but no luck at the very beginning on gpt. What's tz, BTW?
Thank you anyway.

KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!

hbenz2008 said:
Try and flash tz and gpt from 4.4.4
Click to expand...
Click to collapse
It's weird that my reply to your PM cannot be found in my Sent items box and hope you may get my response.

KidJoe said:
Long story short, and if you read that entire thread, and its progression you'll understand the long story, Right now, it would appear the GPT.BIN on your phone is NEWER than the GPT.BIN in any SBF you are trying to flash. Hence your problem.
You will likely have to wait until a newer SBF gets leaked. At this point, it might be after Lollipop SBF's start leaking.
Click to expand...
Click to collapse
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy

yeah i wouldnt phuk with her like that, prob is gpt

mk1129 said:
I guess so... I even want to flash the Moto X 2014 Lollipop stock ROM. But I should be patient wait for my last hope, then.
Thank you!
Click to expand...
Click to collapse
mk1129 said:
How about only flashing the bootloader and partition from RETCA_XT1097_5.0.1_LXE22.46-22_cid14_CFC.xml.zip? Maybe that's crazy
Click to expand...
Click to collapse
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.

KidJoe said:
THe 2013 and 2014 X do not use the same parts. I would NOT flash any components of the 2014 X on the 2013 X.
Click to expand...
Click to collapse
Agree. I'd wait for the Lollipop SBF, then. Thanks!

I suddenly realized that I encrypted the phone when it's on 4.4.2 before playing with various SBFs, and that may be the reason why I cannot write anything any more....

I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.

thehanutedtubby said:
I had the exact same problem with my XT1053. I was able to fix it by flashing the 5.0.2 GPT. If your variant has a leaked zip, it's in the root directory. I wouldn't recommend using anything but your own variant's, but if that's what you want to do so be it.
Click to expand...
Click to collapse
Thanks for the tips! You''re lucky! BTW, Where did you get the 5.02 GPT? from Brazil XT1058 soak test leak?
And yes, I'm really expecting the full lollipop stock rom to have a final try to save mine. I only heard Brazil XT1058 has the soak test for 5.02 and am wondering if I can leverage that...

Problem SOLVED! Android 5.1 stock ROM (XT1058_GHOST_RCICA_5.1_LPA23.12-15_cid14_CFC_xml) revived it!
Thank you, Motorola and XDA!

[Q] Nexus 6 out of box - safeguards?

I have experience rooting/unlocking but this is my first Nexus.
What I have out of the box (delivered):
Code:
Model: 00630NARTL
Android version: 5.0
Baseband version: MDM9625_104335.118.02.55.01R
Kernel version: 3.10.40-g14c2bda (Oct 8 18:10:42 2014)
Build number: LNX07M
First, I don't want to burn any bridges. From the wiki page, I noticed right off *that* old Baseband is not available for download. I imagine this not a concern.
Question 1:
On Nexus, can we always go to previous version of the ROM? (baseband, recovery, android) Are baseband firmwares locked forward so you can't go back to an old version?
Question 2:
I intend on using it on Verizon. What can Verizon do to it? (Can they force baseband updates etc? Is there any way for them to steal my freedom and options? Are PRLs pushed to the Verizon SIM, or are they able to change settings etc in my phone? I'm new to 4G.)
(I bought a Nexus for one reason... "fastboot oem unlock" ... Google appears to be the only one that can stand against carriers who want locked bootloaders, forced updates, and bloatware.)

syserr said:
I have experience rooting/unlocking but this is my first Nexus.
What I have out of the box (delivered):
Code:
Model: 00630NARTL
Android version: 5.0
Baseband version: MDM9625_104335.118.02.55.01R
Kernel version: 3.10.40-g14c2bda (Oct 8 18:10:42 2014)
Build number: LNX07M
First, I don't want to burn any bridges. From the wiki page, I noticed right off *that* old Baseband is not available for download. I imagine this not a concern.
Question 1:
On Nexus, can we always go to previous version of the ROM? (baseband, recovery, android) Are baseband firmwares locked forward so you can't go back to an old version?
Question 2:
I intend on using it on Verizon. What can Verizon do to it? (Can they force baseband updates etc? Is there any way for them to steal my freedom and options? Are PRLs pushed to the Verizon SIM, or are they able to change settings etc in my phone? I'm new to 4G.)
(I bought a Nexus for one reason... "fastboot oem unlock" ... Google appears to be the only one that can stand against carriers who want locked bootloaders, forced updates, and bloatware.)
Click to expand...
Click to collapse
#1--Yes. Can go anyway you want.
#2--Verizon has no control. Everything works. I'm still on unlimited data.
Just updated tonight to latest Factory image. LMY47Z 5.1.1. Just don't lock the bootloader if you need to till you get it to boot.

@syserr
Two STRONG recommendations:
1) You'll need to unlock your bootloader to root and/or install a custom ROM. DO NOT relock your bootloader. It does nothing to bring you back to stock, and has risk associated with it. The only reason to relock is to RMA it. And there is a sticky thread in General section for that.
2) If you decide to downgrade back to an earlier version of stock ROM, do not downgrade your bootloader. It can brick your device.
Welcome the the community, and enjoy your Nexus 6.

syserr said:
Question 1:
On Nexus, can we always go to previous version of the ROM? (baseband, recovery, android) Are baseband firmwares locked forward so you can't go back to an old version?
Click to expand...
Click to collapse
ROM, radio and recovery, yes you can go any way you want. However, once you go to a 5.1 Bootloader, you cannot go back to a 5.0 Bootloader. The 5.1 brings in significant security changes that if you could downgrade it, would make them pointless.

danarama said:
ROM, radio and recovery, yes you can go any way you want. However, once you go to a 5.1 Bootloader, you cannot go back to a 5.0 Bootloader. The 5.1 brings in significant security changes that if you could downgrade it, would make them pointless.
Click to expand...
Click to collapse
To keep options open, could a person leave the 5.0 Bootloader and boot both 5.0 and 5.1 ROMs? Or do you need a 5.1 Bootloader to boot a 5.1 ROM?
Thanks!

syserr said:
To keep options open, could a person leave the 5.0 Bootloader and boot both 5.0 and 5.1 ROMs? Or do you need a 5.1 Bootloader to boot a 5.1 ROM?
Thanks!
Click to expand...
Click to collapse
Indeed. I use the original loader with 5.1.1
However, when it comes to M, that seems not to be the case.

EDIT:
Learned you need to manually unpack the zip and flash each chunk separately to bypass the bootloader check.
danarama: sorry, please ignore my question
danarama said:
Indeed. I use the original loader with 5.1.1
However, when it comes to M, that seems not to be the case.
Click to expand...
Click to collapse
I may be misunderstanding... you are using the original loader that came on your Nexus 6 or the loader from 5.1.1?
I'm on factory 5.0/LNX07M.
I successfully upgraded my radio to 5.0.1/LRX22C.
But when I upgrade my image/OS to 5.0.1/LRX22C, I get this:
Code:
fastboot -w update image-shamu-lrx22c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: moto-apq8084-71.03
Baseband Version.....: D4.0-9625-02.55.04
Serial Number........: ZX1G22N2MD
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'moto-apq8084-71.03'.
Update requires 'moto-apq8084-71.05'.
finished. total time: 0.012s
Just wondering where you are sitting for your bootloader...? THANKS!

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

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

maann said:
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
Click to expand...
Click to collapse
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

maann said:
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
Click to expand...
Click to collapse
What model do you have? Xt1806? Xt1804?
Sent from my XT1806 using Tapatalk

treyweez11 said:
What model do you have? Xt1806? Xt1804?
Sent from my XT1806 using Tapatalk
Click to expand...
Click to collapse
it should be xt1805. possible?

pizzaboy192 said:
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
Click to expand...
Click to collapse
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!

maann said:
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!
Click to expand...
Click to collapse
I forgot to mention that the OTAs tool only works in manual mode, and works best in the same folder as adb.exe

pizzaboy192 said:
I forgot to mention that the OTAs tool only works in manual mode, and works best in the same folder as adb.exe
Click to expand...
Click to collapse
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
}

maann said:
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
}
Click to expand...
Click to collapse
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.

pizzaboy192 said:
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.
Click to expand...
Click to collapse
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

maann said:
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
Click to expand...
Click to collapse
You've nailed it!
What's your model number? Let's get you on the correct firmware and get you up to date!

pizzaboy192 said:
You've nailed it!
What's your model number? Let's get you on the correct firmware and get you up to date!
Click to expand...
Click to collapse
thank you for your kind availability man! how can i retrieve model number? i'm -almost- sure it was xt1805

maann said:
thank you for your kind availability man! how can i retrieve model number? i'm -almost- sure it was xt1805
Click to expand...
Click to collapse
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.

pizzaboy192 said:
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.
Click to expand...
Click to collapse
thank so much bro!

quick question: are these two lines
fastboot erase modemst1
fastboot erase modemst2
really needed in flashing stock rom? thanks in advance

maann said:
quick question: are these two lines
fastboot erase modemst1
fastboot erase modemst2
really needed in flashing stock rom? thanks in advance
Click to expand...
Click to collapse
Don't do those. Not necessary, and not safe to do unless you know you have a backup of your imei and efs partition

pizzaboy192 said:
Don't do those. Not necessary, and not safe to do unless you know you have a backup of your imei and efs partition
Click to expand...
Click to collapse
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!

maann said:
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!
Click to expand...
Click to collapse
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.