Database Develop

[Q] No system updates?

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.

How to apply November Security Update for those of us with a modified boot image

I did do a search for "November Security Update" but didn't find anything.
Specifically I just received the November Security Update from Google but cannot apply it.
I am running a modified boot image to allow me to root the phone.
Is it possible all I have to do is return to unrooted status (disable SuperSU) and apply this patch?
UPDATE: LOL, that would be a resounding NO. It does say "Error in Recovery" but now the Update is gone.... and the Security Patch level still says 10/1

You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.

danarama said:
You have to fastboot flash system.img from factory image. Any OTA is not possible unless you are full stock, unmodified.
Not sure if the security updates end up packaged into system.img or not. If not, you will have to flash stock recovery, system and boot, then accept the OTA then re-flash custom recovery and re-root.
Click to expand...
Click to collapse
That's probably what will be needed as the security update is pretty fresh and proabably not in the stock system I would think. And then, to get back to rooted status, I would have to revert to the modified image, thus undoing the application of the security update? Ehhh, not going unrooted, oh well.
And thanks btw

Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk

swa100 said:
Can't you adb sideload? Isn't that possible when the boot image is modified?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
No.. OTA checks for stock recovery, boot and system. Any amendment it will fail. It's in the zip file regardless of how you apply that zip, it will always fail.
Sent from my Nexus 6 using Tapatalk

I'm lost...please help
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?

http://forum.xda-developers.com/nexus-6/help/nexus-6-mra58k-n-r-forced-encryption-t3242664/page2

jgriesshaber said:
So I bought my unlocked Nexus 6 from Amazon. I was probably stupid, and was to impatient to wait for the OTA to Android 6. So I followed the Andriod Central instructions on how to do the basic download adb tools, unlock phone, flashed. the stock Andriod 6 image (MRA58K). And everything went great. I failed to relock, but it didn't seem to be a big deal.
Then I noticed I didn't get the November Security update.
Then I thought I needed to relock the phone. So I booted into the recovery and ran fastboot oem lock.
So now I am back to a fresh phone and I am downloading my apps in Google Play.
But the November Updates didn't come through.
What did I do wrong?
Click to expand...
Click to collapse
Locked bootloader has nothing to do with it.

[Security Patch] April 1st 2017 Security Patch now being rolled out in RETUS

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?

Latest firmware compilation version

Hello. I have my device rooted and twrp recovery but with stock firmware. I have updates but i dont want to bootloop.
Can you tell me latest compilation number so i search it in firmware databases please? My device is a xt1772 Nicklaus.

I am in same situation, My Owens has Nov 1,2018 security patch firmware, I flashed tTWR recovery and rooted.
Now new firmware NPRS26.58-45-19 comes out with Jan 1, 2019 security patch. How to get it flashed?

min1968 said:
I am in same situation, My Owens has Nov 1,2018 security patch firmware, I flashed tTWR recovery and rooted.
Now new firmware NPRS26.58-45-19 comes out with Jan 1, 2019 security patch. How to get it flashed?
Click to expand...
Click to collapse
If you take the OTA then it will bootloop because you have a custom recovery. You have to go back to stock recovery and then take the update. After you update you will have your bootloader locked again and you will have to unlock it earesing all data in the phone. Then again flash twrp and root.
Thats why i wanted the last official firmware so i do it only once since updates are cumulative updates...
If i have no response about it, i will return to stock recovery, take all ota updates. Then unlock bootloader, flash twrp and try to restore at least the data since you cant recover system otherwise you will return to a not updated firmware.
Thats the only thing i think its possible.
Btw i edit the thread because mine is a nicklaus e4 plus version.
Cheers!

rq005 said:
If you take the OTA then it will bootloop because you have a custom recovery. You have to go back to stock recovery and then take the update. After you update you will have your bootloader locked again and you will have to unlock it earesing all data in the phone. Then again flash twrp and root.
Thats why i wanted the last official firmware so i do it only once since updates are cumulative updates...
If i have no response about it, i will return to stock recovery, take all ota updates. Then unlock bootloader, flash twrp and try to restore at least the data since you cant recover system otherwise you will return to a not updated firmware.
Thats the only thing i think its possible.
Click to expand...
Click to collapse
Thanks for reply. I think I can find stock recovery in stock firmware package.
However do I need to unroot my phone (which I don't know how to)? or simply leave it rooted as is, do OTA after stock recovery flashed?

Stock recovery then take ota maybe More than one since are cumulative. Then Flash twrp and root again.

Unable to install OTA

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.