Related
im facing a problem with september update installation ( or any OTA update because i've flashed the 9.6.9 version and was trying to update the august update and it gave me the same problem so i flashed it manually )
so.. when i was at 9.6.10 " august update " i've unlocked the boootloader and rooted the device and enabled the camera2api.. after that i have uninstalled the root and flashed the stock boot and locked the bootloader... but recently i have faced that problem when i was trying to install the september update and it alaways give me installaiton failed at the same time i installed SafetyNet check app and i found that the SafetyNet check gave me failed !? i dont know why that happens while i removed the root and relocked the bootloader !! and i have flashed the stock rom many times and nothing changes !. so please help me and tell me what should i do .. thanks in advance.
P.S : i installed a root checker and it says that the device is not rooted now
experiencing the same problem, but i didn't even manage to hold the HAL3 enabled 1. Every time i unroot, i lose the property (used setprop persist.camera.HAL3.enabled 1 instead of changing build.prop, maybe that has something to do with it). Anyway, even after unrooting i sometimes get the error that the OTA won't install. I don't know if there is already a root out for the september update?
erostiff said:
experiencing the same problem, but i didn't even manage to hold the HAL3 enabled 1. Every time i unroot, i lose the property (used setprop persist.camera.HAL3.enabled 1 instead of changing build.prop, maybe that has something to do with it). Anyway, even after unrooting i sometimes get the error that the OTA won't install. I don't know if there is already a root out for the september update?
Click to expand...
Click to collapse
Yes it's in the september update thread. Here: https://sourceforge.net/projects/others/files/MiA2/9.6.12.0/
CLOSE
im having the same issue as op now. The link by @Benjamin_L says the folder isnt available. May i know what the solution was?
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
sounds like a bad update.. you could restore via erecovery
lorreca said:
Hi guys,
since some weeks I've got a problem with OTA official update.
To make a long story short: by doing the small update (9mb) of patches attached, when the device restarts, the same notification will continue to return the same update.
The installation is recognized as correctly when is done, but when reboot, if I do "search for updates", always returns this, which I have already done several times, as I never did before... but I did!
Is there any way to solve? I tried to delete cache and data from the app "system update", but it doesn't work.
Apart from the hassle of always receiving this notification, I would not like this "missed" update prevent me from receiving other important updates, such as the next update to Android Pie.
At the moment I've got a CTL-L29 8.1.0.156 (C432).
Can you help me?
Click to expand...
Click to collapse
Have you Factory Reset it?
.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?
fregor said:
.156 had 3 patch updates to it, so I would suggest to install until they go away. Not sure how many times you have seen this?
Click to expand...
Click to collapse
I already updated several times...
oxfordmark said:
Have you Factory Reset it?
Click to expand...
Click to collapse
I would like to avoid to do a factory reset and set all the phone again. If when stable 9.0 Pie arrived I won't be able to update because of this, so I will do a factory reset.
fuzziion said:
sounds like a bad update.. you could restore via erecovery
Click to expand...
Click to collapse
Have you got a link for the guide?
lorreca said:
I already updated several times...
Click to expand...
Click to collapse
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.
fregor said:
Wich patch Are you om then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
I should already have received the september Google patch, but nothing at the moment...
fregor said:
Wich patch are you on then? .157 is out as well, so you could just wait until you get that one.
Click to expand...
Click to collapse
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...
install magisk with both checkboxes activated
lorreca said:
Have you got a link for the guide?
Click to expand...
Click to collapse
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions
i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.
Danchibald said:
157? Country?
I'm on 156 (patch3) in Croatia and there is no update when I check...
Click to expand...
Click to collapse
Norway, C432
Looks like .159 is just around the corner as well.
I'm also on C432 but latest i recieved is 156 (patch3)... nothing further
IceFoxX said:
install magisk with both checkboxes activated
Click to expand...
Click to collapse
With Magisk I will lost OTA update...
fuzziion said:
Turn off your phone hold volume up + power until your phone boot to erecovery after that it's pretty simple just click on restore and follow the instructions
Click to expand...
Click to collapse
Ah ok, is like to do a factory reset right?
Im going to wait for 10 november (pie release) and of doesnt receive the OTA i will do that
bravo261 said:
i had the exact same issue. i don't recall exactly, since i tried multiple different things, but i either did a factory reset or reflashed the entire .156 from firmware finder to get the update to stick.
i did rebrand to C432 and had twrp installed if you're in the same boat.
Click to expand...
Click to collapse
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.
lorreca said:
With Magisk I will lost OTA update...
Click to expand...
Click to collapse
Yeah got the same issue..uninstall magisk.. install magisk manager activate both checkboxes ( keep force encryption + keep dm verity (without keep dm verity you will lose the patches)) download the zip and flash magisk with twrp and you will still have patch03
Sadly i dont know the source anymore
lorreca said:
I'm already on C432 (rebrended from demo/retail) but I would prefer to keep stock with OTA until root for Pie coming. Then i will root again.
Click to expand...
Click to collapse
i'm not talking about root. i'm suggesting you perform a factory reset with the stock recovery, and if that doesn't work, then install twrp and use hurupdater with the firmware files to really go back to the freshest install. using hurupdater will install the stock recovery as well. that got my updates to finally stick
My phone knows there's an update waiting,I know I can't stop it only delay it.
Says its bootloader 7 which may derail option to root in the near future?
If I root and flash a custom rom now before it's to late.........
Doesn't the auto update system toggle enable and disable this feature?
Delgoth said:
Doesn't the auto update system toggle enable and disable this feature?
Click to expand...
Click to collapse
Not really no.
MystaMagoo said:
Not really no.
Click to expand...
Click to collapse
I remember when I first got my device, that toggle comes default switched to ON. That's why my device updated from BL rev4 to rev5 while just sitting there by itself.
That never happened for me again after turning that toggle off. I also set it to not download updates automatically.
So now, it just asks me on every reboot to download the OTAs, but as long as I hit cancel I've never had it update itself without me first hitting the button to initiate. So IDK. It only happened the one time, and it hasn't happened since.
So I feel both options need to be disabled then. And I've had my device since the beginning of this year. If it does start downloading the update hard reboot the device during download and then wipe your cache from recovery. That reset the Download toggle for me when I accidentally pushed download.
Wiping the cache should erase the downloaded OTA anyways. And after it's gone it will just ask you to either download or download/install again.
Delgoth said:
Doesn't the auto update system toggle enable and disable this feature?
Click to expand...
Click to collapse
Delgoth said:
I remember when I first got my device, that toggle comes default switched to ON. That's why my device updated from BL rev4 to rev5 while just sitting there by itself.
That never happened for me again after turning that toggle off. I also set it to not download updates automatically.
So now, it just asks me on every reboot to download the OTAs, but as long as I hit cancel I've never had it update itself without me first hitting the button to initiate. So IDK. It only happened the one time, and it hasn't happened since.
So I feel both options need to be disabled then. And I've had my device since the beginning of this year. If it does start downloading the update hard reboot the device during download and then wipe your cache from recovery. That reset the Download toggle for me when I accidentally pushed download.
Wiping the cache should erase the downloaded OTA anyways. And after it's gone it will just ask you to either download or download/install again.
Click to expand...
Click to collapse
Hi
Ye I do those also.
I read recently you can only put it off only so many times?
I'll do the cache clean if it tries to download itself.
MystaMagoo said:
Hi
Ye I do those also.
I read recently you can only put it off only so many times?
I'll do the cache clean if it tries to download itself.
Click to expand...
Click to collapse
Maybe it has to do with the Installed security policy then? Because you can update your security policy independently of your Build. A newer build will naturally comes with a newer policy, but there is normally an option to update the Security Policy without just downloading a new build.
I can't say I've had entirely the same issue though so I don't know.
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
It's a patch.. it's not useless...
Baron60 said:
It's a patch.. it's not useless...
Click to expand...
Click to collapse
Yes patch as in security patch with some fixes. I understand that. Prolly i stick with mar update since i can't update to april patch. Thanks.
I've tried updating/installing using a vpn. Still no success. Don't know what's wrong...
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Then you can analysis the log
K9998 said:
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.
For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.
In order to find out what the cause was, you need enable developer option, and type the following command:
Then you can analysis the log
Click to expand...
Click to collapse
Thanks. I will give it a try.
kxnzxmori said:
Thanks. I will give it a try.
Click to expand...
Click to collapse
No worries,
The typical message you will get if any of three partitions has been modified:
Code:
The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
kxnzxmori said:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.
**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
Click to expand...
Click to collapse
I have a Locked bootloader & I'm having the same problem. Please advise something.
I have the same problem. . i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?
you need to be specific on your concern what apps says registration failed? it's better to provided screenshot of your issue
Here is the screenshot
Sorry it took so long
caspaas said:
Here is the screenshot
Sorry it took so long
Click to expand...
Click to collapse
it is not recommend to update your OS directly from Setting while Magisk is installed ...your phone would go into bootloop(unusable state) there are also stories of people that are force to buy new device because of this silly mistake also installing OS update from Setting would uninstall Magisk also worse case scenario would lock your bootloader too which as your provably know it's nightmare
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
You modify your system and expect samsung to push an update on your device? That won't work.
Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
*laugh in Android 8 because i did not receive Android 9 update*
Riyal said:
You modify your system and expect samsung to push an update on your device? That won't work.
Click to expand...
Click to collapse
yeah sorry , had a Asus ROG 2 before this and it got OTA updates while rooted so.
New to samsung.
caspaas said:
Heya,
I magisked my S21 ultra and when i want to check for updates it says registration failed?
It did not do that before I magisked it.
So I need to restore everything to fix it or ?
Click to expand...
Click to collapse
yea you gotta restore everything in order to fix