Title says all. This is for the American Retail variant. Does not include Oreo.
Glad to see that Moto is being consistent with Security patches though!
Edit:. I meant April 1st 2018!
This is for all varients
reteu,retbr,Retin also got updates
Sent from my Moto G5S Plus using XDA Labs
Yet to be seen in retapac though
Adi5 said:
This is for all varients
reteu,retbr,Retin also got updates
Click to expand...
Click to collapse
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
JaggedPill said:
The day before I saw the update notification, but didn't update as I wanted to backup some of my files. Later when I checked for update the notification was gone. Says phone is upto date with March patch.
Click to expand...
Click to collapse
I didn't had notification,now flashed custom rom
Flash full firmware for ur software channel
Retid here, still no updates
Got it..retin software channel.
In retla was not released
April Patch also released for retapac ?
I only just got 116-48-12 yesterday on retus, so I'm not gonna hold my breath.
you can edit the thread title by editing your post and pressing "go advanced"
Meanwhile retgb is still on October 2017. This is the last time I buy Motorola.
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
championc said:
Hi all,
I've just applied the 01 April Security Patch and my phone has rebooted into TWRP. If I select to reboot, it starts to reboot and goes back into TWRP. Any ideas as to how I can get it to reboot back to normal ?
So I'm basically stuck in a TWRP Bootloop
Thanks in advance
Click to expand...
Click to collapse
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Juancasa14 said:
Hi, you should know that you can't get updates via OTA once you have modified system, and unlocking bootloader and flashing TWRP is certainly a system modification, so I really hope that you made a TWRP backup before trying to update. In case you didn't, try flashing official firmware using fastboot, also there is one post in XDA with a TWRP backup in case you messed up, if you can't use fastboot or don't have a backup, try using that one. Remember to NEVER update via OTA unless your phone is fully unmodified.
Click to expand...
Click to collapse
U can update with unlocked bootloader. Only without mods like root or twrp
Adi5 said:
U can update with unlocked bootloader. Only without mods like root or twrp
Click to expand...
Click to collapse
Yeah I know, sorry if I didn't make myself clear, thanks for explaining
Championc were you able to recover your phone?
Related
I was running Lollipop 5.0.2 on my Moto G (2014) XT1068 (India) and wanted to downgrade to KitKat. I followed this thread: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
And although the downgrade has been successful, when I check for updates, I get a message that the phone is up to date and no updates are available whereas it should be telling me that Lollipop is available for download. Why is this happening?
Thanks in advance
there is a app that in need to be clean cache and data
Google Service Framework
After reboot and try to check for update.
Try that.
Do you wanna go back to L?
I don't want to go back to L but I might when 5.1 comes out for my phone.
Where can I find that app you are talking about?
you dont know how to clean data and cache for a app
settings/apps/all
:good:
Oh I didn't understand your post. I thought you meant dalvik cache. I'll do that. Thanks
Sent from my Moto G 2nd Gen using Tapatalk
baybutcher27 said:
you dont know how to clean data and cache for a app
settings/apps/all
:good:
Click to expand...
Click to collapse
I did as you said and cleared the data and cache for Google Play Services Framework app and restarted my phone but it still says that my device is up to date... What do I do now?
Sent from my Moto G 2nd Gen using Tapatalk
That happens, or the ota part of the rom is bug, or the ROM you using don't have update.
when update comes out, you search ways to flash the update. The update will come in a flash way before it release to all via OTA.
Ohkk... Once I flash the update the problem should go away right?
Sent from my Moto G 2nd Gen using Tapatalk
baybutcher27 said:
That happens, or the ota part of the rom is bug, or the ROM you using don't have update.
when update comes out, you search ways to flash the update. The update will come in a flash way before it release to all via OTA.
Click to expand...
Click to collapse
Or should I go for this ROM instead: http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295 ?
dakshay95 said:
Or should I go for this ROM instead: http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295 ?
Click to expand...
Click to collapse
I went for this ROM but it removed TWRP from my phone for some reason. And it's not telling me that there are system updates either.
Okay, so I read somewhere that the phone doesn't receive OTA updates if the device is rooted and it has a custom recovery. So I used SuperSUs Unroot feature to unroot the phone and then flashed the stock recovery to replace TWRP.
Now the phone isn't rooted, and it has stock recovery. But even now when I'm checking for updates it's telling me that my phone is up to date. If it matters, my bootloader is still unlocked but that shouldn't prevent me from getting an OTA update right?
Someone please reply...
you are confusing too much things.
like i told you, or you have a bug rom a rom that can reach to OTA because some one has change or remove the part of the ROM that receives the OTA, the OTA is the update... Or you cause a bug on it by mistake or by a app that you installed.
If you have a stock original ROM from Motorola it must received a OTA. Don't mare if you have bootloader unlocked, rooted or custom recovery it doesn't change the habitability of the device receive the OTA.
But if you received a OTA in the stock ROM that you change the recovery and rooted it, and after the download click on update, the phone will turn off and try to update, but it will not have success and you end with a brick phone.
so dont confuse the ability to received the OTA with be able to install it that are two separated thing.
Or you have a bug ROM or you dont have a stock ROM that is the way you dont receive ota.
If you don't wanna update, why bother with update????
When the update comes it will came to very little number of users, before is released to all user's via OTA. So unless you are part of Motorola tester club you don't receive the OTA when is available. But some one in that grup probably will share the update here at XDA that you will be able to flash. Don't mare the rom you are the flash will contain all the ROM and any one will be able to use, of course the right ROM file for the right device.
every update that moto did is now available here so don't worry now when it comes we all will have it.
baybutcher27 said:
you are confusing too much things.
like i told you, or you have a bug rom a rom that can reach to OTA because some one has change or remove the part of the ROM that receives the OTA, the OTA is the update... Or you cause a bug on it by mistake or by a app that you installed.
If you have a stock original ROM from Motorola it must received a OTA. Don't mare if you have bootloader unlocked, rooted or custom recovery it doesn't change the habitability of the device receive the OTA.
But if you received a OTA in the stock ROM that you change the recovery and rooted it, and after the download click on update, the phone will turn off and try to update, but it will not have success and you end with a brick phone.
so dont confuse the ability to received the OTA with be able to install it that are two separated thing.
Or you have a bug ROM or you dont have a stock ROM that is the way you dont receive ota.
If you don't wanna update, why bother with update????
When the update comes it will came to very little number of users, before is released to all user's via OTA. So unless you are part of Motorola tester club you don't receive the OTA when is available. But some one in that grup probably will share the update here at XDA that you will be able to flash. Don't mare the rom you are the flash will contain all the ROM and any one will be able to use, of course the right ROM file for the right device.
every update that moto did is now available here so don't worry now when it comes we all will have it.
Click to expand...
Click to collapse
Actually, I had download this firmware build earlier: KXB21.85.27 but this build hasn't received the Lollipop update, so I downloaded and flashed this firmware build: KXB21.85.23 and as soon as I booted up my phone I got the OTA notification for my phone. Problem solved.
If you have a stock original ROM from Motorola it must received a OTA. Don't mare if you have bootloader unlocked, rooted or custom recovery it doesn't change the habitability of the device receive the OTA.
Click to expand...
Click to collapse
I thought so too but a simple Google search told me that you can't install OTA updates even if you are running original stock ROM if you have a custom recovery. You MUST have Stock Recovery and only then you will receive the OTA update. Your bootloader can still be unlocked though.
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Brick
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
abhigamez said:
This the stock recovery to replace the twrp for ota updates.
Download Recovery
Flash via Fastboot Method
Commands fastboot flash recovery recovery.img
Thanks
@Abhi086 This is my telegram username If you any queries Contact me
Click to expand...
Click to collapse
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
CasinovaRoyale said:
This could end up in hard brick also if OTA detects other system modifications. You should just edit the OP with a warning.
Click to expand...
Click to collapse
i don't think so abt hard brick
as when i was updating i simply came with error while updating that can't update
and i also tried updating after flashing custom rom [which is available online] and i was successfully updated
smokinjoe2122 said:
Couldn't one just install it from this link?
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
This is basically all of the stock firmware (Including the recovery), correct?
Click to expand...
Click to collapse
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
thippu46 said:
I don't think it's a useful thread as there is a specific thread to give information about installing Official firmware and relocking the bootloader.!
Please moderator check this once.
This might damage the devices if anyone tries to update the ROM through OTA, by just changing the recovery being the variety ,oem and bootloader status changed.
Click to expand...
Click to collapse
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
yograjfire18 said:
i hv checkd it, but my device didn't hard broke, but i want to make my device dead to get new motherboard in warranty
Click to expand...
Click to collapse
:angel:lol
Does someone has tried this successfully?
mabvmet said:
Does someone has tried this successfully?
Click to expand...
Click to collapse
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Could always just do "fastboot boot" instead of "fastboot flash". It will allow you to then boot twrp, install what you want, and not touch the stock recovery.
pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
What are the steps I need to follow to install this file? (SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml)
---------
Edit: Solved
---------
I followed the code section steps on this post:
https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
pratham.kamath said:
In stock Moto G5s plus rom I had installed TWRP and rooted the phone and just wanted the stock recovery so that i can install April security patch, The recovery was installed however when it tried to install the April update it failed, All though it did load the OS and i was back to where i was.
Whole story in short if you have rooted the phone with TWRP and need stock recovery just to install latest update, IT WONT WORK.
You will need to install SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/ and then start the entire thing from scratch and then it will update over OTA as well regardless if bootloader is unlocked.
once your device installs all updates you can then install TWRP again and root it if you want to. but if you do that and wish to get OTA you will need to go back to stock and repeat the whole process from scratch.
Click to expand...
Click to collapse
Hey! I Finally did this, I removed the twrp and the root, I Just installed this stock (?) rom through the "adb fastboot". Now when I look for OTA updates it appears a message that indicates that the latest security update is installed, it's the one of December 2017...
Why doesn't it appear the last one (april's or so)?
What I have to do in order to have or reactivate the OTA updates?
Thanks in advance!
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
pratham.kamath said:
Make sure the correct stock rom is installed. (Cross check the name word to word) I too tried a few different stock ROMs and only the above version worked and updated till April security patch. Rest versions didn't update for some reason.
Click to expand...
Click to collapse
How can I know what is the correct stock rom?
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
pratham.kamath said:
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from site firmware.center/firmware/Motorola/Moto%20G5s%20Plus/Stock/
This one worked for me.
Click to expand...
Click to collapse
My current file >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml_1
This rom left me with the December security patch and no OTA updates available
This time I will download the same one, but the most recent (February, according with the web)
Next download >>
SANDERS_NPS26.116-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip 03/02/2018 06:35
I followed this steps in code section to flash it... any suggest?
Steps >> https://forum.xda-developers.com/mo...lash-official-firmware-moto-g5s-plus-t3681018
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
pratham.kamath said:
Don't go by date go by exact name and number of rom as I mentioned. I tried almost all the firmwares listed and only the one that I mentioned updated to latest april security patch. Matter of fact i just restored phone to stock yesterday and it worked again. Also copy all the commands to a notepad and save the same as .bat file so that way you can just run the file and it will automatically install stock rom and reboot phone.
---------- Post added at 08:53 AM ---------- Previous post was at 08:49 AM ----------
Check software channel name in settings. Mine is listed as retin. I read that there are other software channels too for which updates security patch has not been released yet. I may be wrong though.
Click to expand...
Click to collapse
Sorry, how do I run the bat file? The last time I entered the commands one by one.
My software chanel is "openmx" the sameone that I had when the phone was rooted (and with the updates available).
I need help
I need the recovery.img for the device moto g5s plus xt1806:llorando:
So, when I go to try and check for system update, it says I'm already up to date. I have the stock 7.1.1 (RETUS/Non-Fi) Retail XT1900-1, (re)locked bootloader. Has there been no official OTA after November? (I did try to manually flash other builds/Oreo/Fi ROM/etc. but flashed back to 7.1.1 stock/Nov 2017 since Android Pay is something I use and other ROMs didn't let me use that). Did I miss something while flashing back to stock that's borked OTAs? [Tried wiping through stock recovery, through TWRP, etc. no difference) Any answers would be great! TIA!
Answer: Looks like it was just me.
Update: Fixed it! Reimaged stock from September 2017 and OTAs began to work! Right now OTA updating to 8.0. So happy!
smmankad said:
Answer: Looks like it was just me.
Update: Fixed it! Reimaged stock from September 2017 and OTAs began to work! Right now OTA updating to 8.0. So happy!
Click to expand...
Click to collapse
Your OTA worked with TWRP installed?
Neffy27 said:
Your OTA worked with TWRP installed?
Click to expand...
Click to collapse
Nope. Still on stock recovery. Since the stock recovery is nowhere to be found for this device, I have refrained from flashing TWRP (I had only fastbooted TWRP, never installed it on here).
It's security updates up to May 1st. I can't install it though it fails and I am stock with unlocked bootloader.
Comet1966 said:
It's security updates up to May 1st. I can't install it though it fails and I am stuck with an unlocked bootloader.
Click to expand...
Click to collapse
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I'll try tonight after the Gym and see if I can get it to update for me
JordanFromIT said:
I'm in the same boat. I just followed this thread and did everything right when restoring my stock ROM for Sprint. The only thing I didn't do was lock the bootloader. I cannot do OTA updates, fails every time. Someone mentioned a few pages in that thread, that right now it's a 50/50 chance due to an unknown variable. Give the forum time we will get it
Link to thread: https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Click to expand...
Click to collapse
For me, that variable is twrp. If I flashall to stock I can take the ota, then resinstall twrp and root after. Worked today too.
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
So is there a method for clean flashing or i just flash over a rom using fastboot? I tried flashing a retail rom on my tmobile variant, it work but some things were broken.
Comet1966 said:
I was going to install LineageOS and just gave up on it lol. So I flash-all'd back to stock and the OTA worked this time.
Click to expand...
Click to collapse
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
byt3b0mb said:
which flashall did you use? I'm trying to do this too and it fails no matter what. did you also re-lock the boot loader for the ota to work?
I've tried unlocked and locked and it still doesn't take the OTA for me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Comet1966 said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
I used the sprint oreo flash-all from that link, 2nd post. I just ran it and then updated without issue.
Click to expand...
Click to collapse
oh. I am on T-Mobile. seems that im on december security patch although im on 27.1. something is wrong with my phone...
You'd think Motorola would have released an updated flash-all. Maybe they have?
Josh McGrath said:
You'd think Motorola would have released an updated flash-all. Maybe they have?
Click to expand...
Click to collapse
I doubt it. The Feb release of the Dec update got released two months later. (Apr 7th)
This phone is really weird. I got the update to work the very first time I flashall but twrp bootlooped and it won't install after the second flashall, tried multiple times.
This phone is really software wonky
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
kendallgreen said:
the zip files from Tmobiie are NASH_TMO_C_OCX27.109-51.... Does anyone know the difference between this and the OCX27.109-48-6?
Click to expand...
Click to collapse
When the update first came out, the December path I think, it was simply generic Android security updates, nothing specific to our phone or fixes, at least for the TMobile version
Hi,
I just unlocked my X4 (XT1900-2) to try Magisk and all worked good.
Now, when I wanted to revert, I just installed the stock image using fastboot and adb.
After installing them and re-locking my bootloader I was not able to change my system status to Official(I installed Ryzen Kernel before).
Nor I am able to install any OTA to change it to Official, can anyone tell me how can I install OTA update and change my status to Official and be stock again.
Please help!!!
Thanks in advance,
Divanshu Chauhan
Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.
Shreyas17 said:
Can you provide the information of system flashed because if correct system has been flashed then the status should change to official. Try reflashing the system.
Click to expand...
Click to collapse
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.
Shreyas17 said:
The system seems to be correct but its not official signed image so try to reflash the system or factory reset or try to get latest system signed image flash it and then check the status.
But many users have faced this problem even after flashing stock rom and relocking the bootloader they were unable to install ota.
Click to expand...
Click to collapse
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003
AgentDivanshu said:
Tried it again, but was not able to get it back to official.
Any other ideas??
:crying::crying:
Should I try flashing this image -
https://androidfilehost.com/?fid=746163614322270003
Click to expand...
Click to collapse
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.
Shreyas17 said:
You can try but make sure this stock rom is for xt1900-2 ,the other option is to wait till motorola releases signed images for the device ? or to visit the authorized service center they might flash the system and give your device back in official state.
Click to expand...
Click to collapse
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?
AgentDivanshu said:
Well, I can't take device to authorised service centre because my warranty is void now.
Can you tell me the estimated time till motorola releases signed images for my device?
Click to expand...
Click to collapse
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.
Shreyas17 said:
Its upto motorola when to release the signed images for the device but you can try to flash system from the link
https://androidfilehost.com/?w=files&flid=229118
Select the payton image that has latest build and for safety i would suggest unlock your bootloader and try to flash the system .
Try to flash PAYTON_OPWS28.46-21-9 from the link it might help.
Click to expand...
Click to collapse
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot
[Deleted]
AgentDivanshu said:
My device hasn't got the 8.1 update, I was on Oreo when I rooted. After installing the flash again, I am getting OTA Update but error is show.
Error attached as screenshot
Click to expand...
Click to collapse
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.
Shreyas17 said:
Till now user of xt1900-2 have not received 8.1 all are on 8.0.0 latest update is of 1 october 2018 security patch.
Can you tell on what security patch is your device running.
Click to expand...
Click to collapse
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
AgentDivanshu said:
My device is on 1 April 2018 patch after flashing the firmware which I attached as link in one of the above posts.
I am not able to install 1 June 2018 security patch update.
Is there any problem with my A/B partition system?
Also, when I rooted my device, I was on 1 October 2018 patch.
Click to expand...
Click to collapse
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.
Shreyas17 said:
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
so i guess you will have to wait till firmware is released with latest security patch because you have broken ota so only option left is to update device using fastboot . Did you get any error like pre-validation failed while returning back to stock ?
You won`t be able to install ota until your device status changes from modified to official.
Click to expand...
Click to collapse
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo
AgentDivanshu said:
I get error like system is modified/corrupt.
Should I flash xt1900-7, xt1900-6 or xt1900-1 version?
Also when I flashed xt1900-1 version, it showed me something like 'Mode has been set to logging' on Moto Logo
Click to expand...
Click to collapse
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?
Shreyas17 said:
I have seen video tutorials in which they flashed android one firmware on retail but you will have to keep bootloader unlocked .But i would suggest you to flash custom rom if you keep bootloader unlocked atleast you will get additional features and once moto x4 recieves android 9 update then you might get official system image to flash via fastboot and return back to stock. Search on youtube for tutorials it might help you ?
Click to expand...
Click to collapse
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?
AgentDivanshu said:
But how will I update to Android Pie if installation fails again??!
Will Motorola release factory image for xt1900-2 then?
Click to expand...
Click to collapse
They might release the system images till then or you might get stock rom zip available the way oreo stock rom is available now so you will be able to update your device to android 9 via fastboot not by ota ?
AgentDivanshu said:
I used the ROM from this link -
https://forum.xda-developers.com/moto-x4/development/official-firmware-moto-x4-xt1900-02-t3831939
Click to expand...
Click to collapse
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
varunbala said:
Hey. I used this rom as well to move back to stock but OTA's work fine for me. Currently on the 1 Oct patch. I still get the warning message during bootup even if I relock it. But apart from that everything else works fine.
The only thing different I have done is use the flash script from the below linked thread. Not that it should have made any difference but you guys might as well try and see.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
Click to expand...
Click to collapse
Have you re-locked your bootloader after flashing this script?
Did you use Linux or Windows?
I tried relocking but then the warning changes to that of a unsigned system image being used. Don't remember the exact wordings. So then I moved to back to unlocked bootloader.
I am using windows.