Database Develop

[Q] Do I need to have the correct recovery for the current version?

I used MotoNoMoWp on my friend's phone and disabled write protection successfully.
Then I did the RockMyMoto method and got root.
Then I flashed the stock recovery I had on my PC which I think is from the latest Sprint image.
Then tried to take the OTA update.
It got about 20% in and rebooted saying the upgrade failed.
I did the same process with my phone and it worked fine. But I had updated to the 2nd to the latest update first, my friend was still before the first 4.2 camera patch update.
So do I need to flash the recovery from that older version before taking OTA or should any stock recovery flash work?
Q

http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5 cell phone telephone....

kj2112 said:
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
Yea I've already seen that.. doesn't specifically answer my question.. But perhaps I should have used slapmymoto instead of rockmymoto and done the flash resets. I'll try.
Still, if anyone has an answer to my specific question on whether a certain stock recovery is required to flash the ota or not that would be helpful

You need the recovery from the firmware version you are using. As far as I know. Why use a different one?
Sent from my N5 cell phone telephone....

DssTrainer said:
I used MotoNoMoWp on my friend's phone and disabled write protection successfully.
Then I did the RockMyMoto method and got root.
Then I flashed the stock recovery I had on my PC which I think is from the latest Sprint image.
Then tried to take the OTA update.
It got about 20% in and rebooted saying the upgrade failed.
I did the same process with my phone and it worked fine. But I had updated to the 2nd to the latest update first, my friend was still before the first 4.2 camera patch update.
So do I need to flash the recovery from that older version before taking OTA or should any stock recovery flash work?
Q
Click to expand...
Click to collapse
are you sure its RECOVERY that is causing your issue?
The OTA contains a manifest file, which includes files and hash codes. It verifies these files exist on your phone, and the hashes match. If they don't match, or something is missing, the OTA will fail.
If you can boot into recovery, and manually install the update from there, it will show you progress and tell you the reason the update failed.

[Q] ota update with root and cust. recovery?

I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?

schpongo said:
I've got a question.
My moto g is rooted and has got a custom recovery installed.
Today I got the notification for the ota Lollipop update.
I wondered what would happen if I installed with the ota update?
Is there a way to disable checking for updates as I'm not interested in Lollipop an don't want to be bothered by the constant notifications?
Click to expand...
Click to collapse
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.

Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Ok.
But i'm not really interested in the update anyway.
I would just prefer to stay on kitkat at the moment because I'm not convinced that lollipop is an "upgrade".
How do I turn of the constant notifications? I have already "froze" the update service with titanium backup but that didn't seem to help.

Lucian Armasu said:
It doesn't seem to work. It gets stuck in the TWRP recovery. I also downloaded the same file from these forums, tried to install it through TWRP and still didn't work. That's...strange.
Click to expand...
Click to collapse
Because OTA.zip has to be used with stock recovery , unrooted and /system files unaltered - not for use via TWRP
If you ever want to reflash your phone to stock plenty of guides how to... or if xt1068 just use my signature links

[Q] OTA failed to update in rooted phone and will no longer appear

Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.

inarush said:
Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.
Click to expand...
Click to collapse
Try to flash stock 5.0.2 again, and see if it shows any software update..!! ?
Sent from my Moto G 2014 using XDA Free mobile app

inarush said:
Hi all,
I have a unlocked, rooted Moto G 2014 (2nd gen) US version. I have T-mobile on it.
Yesterday I received an OTA notification to update it to Lollipop version 22.41.19 (described here: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/105214).
I downloaded it and confirmed the instalation. Phone rebooted to TWRP and I tried to flash the file from the /cache folder, but i received an error.
I rebooted the device and tried the same again, with the same errors. Then I decided to do some research and I learned that OTA cannot be flashed in rooted devices. Damn!
The problem is: I deleted the .zip file on the /cache folder and now the OTA no longer appears on my device. If I go to settings -> about phone -> system updates, all I get is: "Your device's software is up to date", even though I didn't finish the upgrade process.
My question is: how can I get back the OTA notification? it looks like this 22.41.19 version is the most updated I've seen. Perhaps Lollipop 5.1? I am interested in reverting the device to stock, performing the upgrade and rotting it again.
Click to expand...
Click to collapse
If you're rooted with Super SU then just open the Super SU app, go to settings, scroll down to full uproot and choose that. Then after the update, boot to recovery and reflash Super SU if you'd like to root again.
Sent from my GT-P5210 using Tapatalk

Failed updating to 23.21.44.en.US

I have a rooted turbo. I wanted to update to the new system and then unlock the phone (I read I had to be on the latest version to unlock, is that true?). The update keeps failing. I have tried several times, including doing a factory reset to try, but the update keeps failing. Does anyone have any help/direction on getting the update pushed through?
The pictures attached shows the current phone information and the failed update.

JON123123 said:
I have a rooted turbo. I wanted to update to the new system and then unlock the phone (I read I had to be on the latest version to unlock, is that true?). The update keeps failing. I have tried several times, including doing a factory reset to try, but the update keeps failing. Does anyone have any help/direction on getting the update pushed through?
The pictures attached shows the current phone information and the failed update.
Click to expand...
Click to collapse
Edit: Deleted

JON123123 said:
I have a rooted turbo. I wanted to update to the new system and then unlock the phone (I read I had to be on the latest version to unlock, is that true?). The update keeps failing. I have tried several times, including doing a factory reset to try, but the update keeps failing. Does anyone have any help/direction on getting the update pushed through?
The pictures attached shows the current phone information and the failed update.
Click to expand...
Click to collapse
Phones that are rooted cannot take OTA updates. You have 3 options:
1. Use Fastboot to flash the stock system image of whatever firmware you're on, then take the OTA.
2. Use Fastboot to flash every image contained in the full SU4TL-44 firmware and perform a factory reset.
3. Plug your phone into a PC and install the Verizon Upgrade Assistant that pops up. Accept the upgrade to SU4TL-44.

Question OTA Update Fails With "Installation Problem"

NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.

Maybe Oxygen Updater has full download link?

BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.

kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?

BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.

kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)

BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.

Did you flash stock recovery to both slots the last time?

g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?

BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.

g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.

BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.