My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
matheusgoes said:
My phone was rooted, so I thought it could be the problem. So I made a factory reset and uninstalled magisk.
Anyway, it keeps failing to install a new security patch. It keeps trying to install and always says there was a problem in the installation. What could be causing it?
I'm running the stock OTA with december security patch, since january and february had annoying bugs.
Click to expand...
Click to collapse
Try flashing stock ROM, it worked for me
Firexxe69 said:
Try flashing stock ROM, it worked for me
Click to expand...
Click to collapse
I've never flash any ROM. Do you have any tutorial I can follow?
matheusgoes said:
I've never flash any ROM. Do you have any tutorial I can follow?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Firexxe69 said:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445/page68 download the fastboot version, then flash it using fastboot commands
Click to expand...
Click to collapse
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Maharram said:
you directly flashed update?
i cant update since december security patch and now if i flash march s.p. with fastboot that will work?
Click to expand...
Click to collapse
I never tried it, but when i'm on december patch, i flashed the december patch, then update it from system update. Make sure to backup your data because it may erase your data.
I tried to flash december s.p.
Got the message "Flashing error bluetooth_a" mi flash tool. Do someone know how to solve it?
Related
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Mae7 said:
So I followed rootjunkies tutorial (also blocks OTA updates i think?) to flash my prime version to the stock version and now it's at v6.4 and Android security patch level says: June 1, 2016.
Is this fine or do I need to upgrade, and if so how do I go about upgrading from here?
Cheers
Click to expand...
Click to collapse
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Mae7 said:
Cheers, I just followed Rootjunkies rooting guide and unlocking bootloader guide (forgot if I had already done this). Then I flashed this ROM in TWRP:
https://www.androidfilehost.com/?w=...fd3611a23c42ce769cb77d93e058695a15ec394a2e136
And it worked fine. It hung in the flashing part at the start but I waited it out and it installed. Then I reflashed the superSU zip again.
Click to expand...
Click to collapse
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Jakets said:
Does that one have the OTA updater still enabled? Can you disable it without root? I was thinking about trying that one. Glad it worked out for you.
Click to expand...
Click to collapse
Not sure. It's probably disabled for a custom ROM.
Jakets said:
I did the same initially. I suggest flashing back to 6.1 stock (complete 6.1 out of the box flash from mrmazak's thread) then flashing one of the 7.4.2 firmware you can find here. Use SPFT and it couldn't be easier.
My 7.4.2 shows October 5, 2016 for security patches.
Click to expand...
Click to collapse
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Fat Rat Bastard said:
FYI, October 5, 2016 patch level is the same as the non-Prime V17 OS.
Click to expand...
Click to collapse
Yeah I actually ended up going with a V17 firmware.
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).
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?
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.
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
I solved my problem.
I did few modifications on the system partition with Adaway, so that's why the OTA didn't work. So I reflash the firmware, and I followed the steps for OTA updates, and that works now!
I have that problem again : I tried to update from 7 to 13 and failed all the time. Before that, I installed the November 1st patch and lost the root. So I downgraded to 7 to get root again.
At Step 3, the update stops at 56% before the update fails.
FoxyLove33 said:
I've just installed Magisk on my device. I tried to update my phone via OTA with this tutorial https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation but the update fails.
I didn't flash the recovery image
Click to expand...
Click to collapse
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
e4noob said:
Hey man, can you link a tutorial to update the z3 play with security patches? Mine has bootloader unlocked and no other modifications. All stock. Updated upto july patch. Can you link a tutorial? and link for the patches (RETUS)? Thx.
Click to expand...
Click to collapse
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Thanks. I tried the instructions on the ota link, but am still getting Software Update unsuccessful?
FoxyLove33 said:
First of all, I'm not a man. The first link is how to install magisk, and the second one is how to update via OTA
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Hi,
I'm having a similar issue with the OTA installation after getting magisk root using the Boot Image Patching method. The tutorial shows several different methods, but so far I haven't had luck with any of them. I tried the one for "Devices with A/B Partitions" and got as far as flashing the original boot image back but the OTA still wouldn't install. The flashfire method wouldn't work because flashfire says it isn't compatible with "20.1:MAGISKSU". I didn't touch the recovery partition and I am using the same file I used to create the patched magisk boot image (without the alteration) to try to get back to stock boot image. I'm not sure what else to do aside from using LMSA to reflash stock. My concern with that (aside from having to reconfigure everything) is that I don't have the latest boot.img from the 1-9 firmware to patch it in Magisk and I don't yet know if I can use the 1-6 firmware modified boot.img file.