Related
I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
JShan said:
I'm running mrmarzak's stock V8.5 ROM and I got a notification from Wireless Update to download and install the latest update to the ROM. After downloading, I click "Install Now" and I get the message:
"Warning
FOTA is not supported on this device!"
The only way to get rid of the notification is to turn off all notifications for Wireless Updater. Even then, I still get a pop-up reminder every so often to complete the update, but each click-through results in this same message. Can anyone help?
Click to expand...
Click to collapse
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
mrmazak said:
Reboot to recovery. Clear cache
Should do it. Might need to clear app data for Fota, or can remove fota.
Don't think you want the full oem ota update anyway.
It updates the preloader and that makes recovering from bad modifications harder (blocks spflash tools)
But if you want the full official ota update, you can restore the "fota reboot apk". It is renamed to ".apk_ " right now to block the install. So you can rename /system/FotaReboot/FotaReboot.apk_ to /system/FotaReboot/FotaReboot.apk
Click to expand...
Click to collapse
Thanks, mrmazak! And thanks for all your work on the R1 HD! I was really in the mood to tinker last night, so I flashed your LIneage port last night... That not only fixed the problem on my phone, but I'm loving the ROM so far. Only thing I've noticed is that the signal indicators for wifi and both SIM cards seem a bit lower than what i remember from the stock ROM (ie. a place that used to give me 4 bars now shows 2 or 3). But I haven't noticed a decline in performance per se. Maybe this is a software glitch and the signals are still read as strongly by the phone?
Again, many thanks for all your efforts!
I am using custom custom "Imperium Rom". Even after I delete /cache/update.zip, the OTA downloads again. I cannot find the app to disable/freeze or how to clear the icon in the notification panel.d The update fails because the custom recovery, TWRP is installed. I believe that if the actual update will break Imperial Rom.
Any ideas?
king200 said:
I am using custom custom "Imperium Rom". Even after I delete /cache/update.zip, the OTA downloads again. I cannot find the app to disable/freeze or how to clear the icon in the notification panel.d The update fails because the custom recovery, TWRP is installed. I believe that if the actual update will break Imperial Rom.
Any ideas?
Click to expand...
Click to collapse
It's not a full block, but after trying to install it, it will fail (it will just boot into TWRP, just tell TWRP to reboot back to System). It'll give you a notification that there is an update. Go into the update page and you can "pause" the update. This disables the download and stops it from giving the notification until you resume it. I've had mine paused for a week so far without issues while I look into how to install this update. (It does have a new radio firmware, so it's worth at least that).
pizzaboy192 said:
It's not a full block, but after trying to install it, it will fail (it will just boot into TWRP, just tell TWRP to reboot back to System). It'll give you a notification that there is an update. Go into the update page and you can "pause" the update. This disables the download and stops it from giving the notification until you resume it. I've had mine paused for a week so far without issues while I look into how to install this update. (It does have a new radio firmware, so it's worth at least that).
Click to expand...
Click to collapse
I followed your information and paused the update. The phone is working well without problem so I don't need the update. I think there is a security update too.
I have a TWRP backup of stock with stock recovery. This would likely accept the update but I worry that restore of the Imperial Rom will cause problem.
Easy way is dial code 277634#*# then wifi test option then Ota setting disable so you won't get it if set to download over wifi hope this helps
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
you may have a couple of options.
I have heard that if you reboot in to the bootloader mode and clear cache then it will get rid of the downloaded firmware update.
I'm not sure.
you can download package disabler pro and disable the update services. I went back to oreo after pie update was horrible.
in package disabler pro follow the directions to enable it
search in the app for "update"
I disabled
"Software update" (com.sec.android.soagent)
"Software update" (com.wssyncmldm)
"System updates" (com.samsung.sdm)
No more updates or notifications
Good luck
jd14771 said:
You can flash the unlocked 8.1 oreo ROM and it will remove the ability to receive updates all together. it will also remove all the bloatware from tmobile. You will have to flash this with odin. After downloading the .zip ROM, Unzip it and flash all 4 files.
You want the XAA download.
https://forum.xda-developers.com/ga...ck-960u-firmware-att-vzw-tmo-spr-usc-t3837086
Click to expand...
Click to collapse
You still need package disabler pro or some kind if service blocker.
I down graded to Oreo on two devices using XAA and I still got firmware update messages for pie. Once I set up the phone.
Blocking the services keeps the phone from checking and downloading the update.
ucladave said:
I have a Galaxy note 9 running 8.1 and would like to stay there. My phone is the T-Mobile branded one. Unfortunately it seems that my phone has downloaded the OTA update to pie and is asking me to install it. I clicked "Later" but I'm afraid that won't last forever. How can I delete the downloaded data and also disable the update from happening in the future?
I am a complete novice when it comes to software stuff so things like "flashing" memory etc may be beyond my scope unless it's very simple. I do follow instruction well though
I understand that I am forgoing security updates and I'm ok with that. After finishing up with a Galaxy S7 that was painfully slow on its last update and having it eat battery, I'd like to stick with the original software. There are other things like the camera app, layout, etc. that I'd just rather stick to.
Aside from rooting the phone, is there any way to just kill the update program? How can I delete the downloaded update to free up memory? I read someplace that rebooting the phone would install the update - so do I need to factory data reset and start over? (I just got the phone so I'm ok doing that)
Click to expand...
Click to collapse
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.
Jammol said:
Easiest thing to do is to flash a different version modem for your device. Just flash the previous version modem file with Odin and you'll be set. If you want ota again, just flash the modem for your device matching the software update your device has installed.
I was on Oreo running the Pie modem and never got the Pie ota alert.
Click to expand...
Click to collapse
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?
ucladave said:
My phone has already downloaded the update and is prompting me to install it. If I flash or run a package disabler at this point will it be effective? How can I erase the update data so it isnt eating space? Do I need to factory reset the phone first to wipe all that out before I flash or run disabler?
Click to expand...
Click to collapse
You could try clearing cache like an earlier poster suggested.
I went to check for system updates today and my pixel initially started to download the latest patch and then after a couple of seconds went straight to telling me that there is no update available. Anyone else have this issue and/or successfully update to the March 2020 OTA via the process below?
Updating Phone Once Rooted:
- Check for device updates, when found:
- Tap uninstall in 'Magisk Manager'
- Tap restore images
- install OTA (do not reboot)
- Back to magisk, tap install > select install to inactive slot
- When magisk installed, press the reboot button in it. It'll force to the other slot AND you'll be updated AND rooted​
I assume I should be able to go under 'System' -> 'Advanced' and get the OTA under 'System Update'. I've already disabled 'Automatic system updates' under 'Developer Options'. Just making sure google is somehow not blocking the update on rooted devices and that the above steps are correct. Thank you in advance!
Found similar thing on reddit here.
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Taking an OTA update should be as easy as the above instructions. However there is another option available to install an OTA update called sideloading. Sometimes the update doesn't appear on the phone in a timely manner and you may want to manually install the update. Other times the OTA update seems to fail for some reason. In the end, you may decide to sideload the OTA instead of trying get it via the update feature on the phone. Surprisingly, it's actually faster to install the update via sideloading than it will be to take the OTA normally. I'll walk through the sideloading steps.....
Optional Step 1 - Uninstall Magisk (so that it restores the stock boot.img). If you find yourself unable to boot into recovery, you will have to restore the stock boot.img. I've run into this issue on some Android 10 images, but not all.
Step 2 - Download to your computer the correct OTA image from here
Step 3 - Connect to your phone via ADB on your computer. You should see the device listed if you type the command "adb devices".
Step 4 - Boot your phone into recovery (type the command "adb reboot recovery").
Step 5 - The phone will have a green android robot with a red sign over it's open access panel. Press the power button and then the volume up button while still holding down the power button.
Step 6 - Select "Apply update from ADB" using the volume buttons to highlight the choice and the power button to select it to enter the sideload mode.
Step 7 - Using your computer, type "adb sideload ota_file.zip" where ota_file.zip is the name of the OTA file you downloaded in step 2.
Step 8 - Once the update finishes, reboot the phone to complete the update process. (See note below about initial boot times).
Step 9 - To obtain root again, please use one of the two root methods listed above
Please note, the initial boot may take quite a while. I've seen the process take upwards of 20 minutes and longer. I think part of the reason it can take so long is that it optimizes the apps during this boot process. The more apps you have, the longer the process may take. When you take a regular OTA update, the phone will change to a screen where is specifically tells you it is optimizing the apps and counts up as the apps are optimized to give you status updates. When you use the the side-load method, it all happens with just the regular boot animation running and without any status updates. Because of this, it is easy to assume something has gone wrong with the boot process while in fact the phone is working through the process normally. If it isn't boot looping (showing the initial power screen before moving back to the boot animation), everything is fine and you just be patient and let the phone complete the process.
Click to expand...
Click to collapse
sic0048 said:
It's very common for unlocked and rooted Pixel phones to not "find" or complete the monthly OTA updates. There must be some sort of check in the OTA process that fails on rooted phones.
You should get familiar with the "sideloading" process of manually flashing OTA images.
Here is a set of instructions that I wrote in my Pixel 3a rooting guide. The process is exactly the same for the Pixel 4 series.
Click to expand...
Click to collapse
Thanks for the reply! I'm very used to sideloading/dirty flashing the updates, was hoping to use the Magisk method . Seems like google is getting smarter with their updates. I am guessing the current inability to see the OTA is due to the updates with google pay and google wanting to ensure banks it is safe.
I just finished sideloading March's OTA and patching the boot.img and everything seems to work, just a bit more effort than leveraging Magisk.
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
I experienced same exact thing. Looks like it saw the update at first then after a few seconds reverted to No updates available. About to try uninstalling Magisk, if no bueno, then gonna just sideload.
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Gooch4130 said:
Did you disable 'Automatic system updates' on the phone? That should still allow the download to occur just not the install. It seems like google got smarter with this update to detect rooted phones.
Click to expand...
Click to collapse
Yes I disabled automatic updates. It didn't do it automatically, I clicked the check for update button. Normally when I do that it says there's a download available and then I know to check online for the flash file. This time it updated without stopping.
FAILED (remote: Failed to write to partition Not Found)
what i am doing wrong ????
---------- Post added at 12:21 PM ---------- Previous post was at 12:17 PM ----------
Boot loader is unlocked...
10.0.0 (QQ2A.200305.003, Mar 2020, All carriers except AT&T)
this version i did ota update
i am from germany.
okay, i found a way to root, but how is it with safety net fix ???
anyone an idea ???
Deleted
Spookymyo said:
I had something funny happen. I was rooted in the January update. I just decided to check for updates. It always shows there's an update but always fails to download it. This time it downloaded and installed it. All the way to the March update. This unrooted me. I still had Magisk and all my modules but it was disabled.
I've tried the usual methods to reroot it. I downloaded the March update. Extracted the boot image. Patched it in Magisk. Put it on my PC and flashed it. The phone restarted and displayed the Google start up screen and a waiting bar like it was optimizing apps. But when that was done it went to a black screen and never left it. I put the phone down and came back to it over an hour later and it was still black. I had to reflash the stock OTA update.
Anyone know why that happened?
Click to expand...
Click to collapse
It installed the OTA for me too, now I'm afraid to restart my phone.
mattcoz said:
It installed the OTA for me too, now I'm afraid to restart my phone.
Click to expand...
Click to collapse
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
I successfully rooted the March update, using the boot.img method.
Spookymyo said:
I would flash Magisk again before you restart.
I still can't get my phone rooted. I'm not sure what's going on. I wonder if other people have been able to successfully root the March update.
Click to expand...
Click to collapse
I rooted with boot.img method, as well
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
I got it rooted. It ended up taking a factory reset. It must have been some file interfering with the process. Once I reset my phone the rooting process went without incident.
As I'm searching for a more Phone based update wy, I'm thinking about to use maybe the Implemented OTA Process, but download the OTA-File manually... But for that We must know,how the OTA process is working. Did someone know:
- Where the update stores the download fine (I found a OTA and a OTA_Packge directory in the /Data/ folder)
- is there maybe a setting or information which must be injected somewhere (maybe a txt file)
- after that the ota update could then maybe started by hand
Has someone informations on that? If maybe someone where the ota still works and stil has root could check the files and places?
Chris.C said:
sruel3216 said:
I rooted with boot.img method, as well[/QUOTE
I ended up following this
https://www.youtube.com/watch?v=kZY8qiz2SZ0
Click to expand...
Click to collapse
Worked like charm!! Thanks!! :good:
Click to expand...
Click to collapse
I unlocked the bootloader, sideloaded the August 2020 OTA and flashed the patched boot image. Kept bootlooping, then I restored to the original, booted in, installed Magisk Manager and then flashed the patched image again. Just leaving this here in case it helps someone.
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.