I restored stock boot images in Magisk and rebooted the phone. It is trying to install the November 2019 security update. It downloads it and starts to install but then it gives me an error message that says it "couldn't update." I'm trying to install the Android 10 update on my phone but it looks like I'm behind on one or two security updates. Anyone know what I can do to get the updates to install? The only modification that I have done to the phone after rooting it was to enable the Camera2 API so that I could use Google Camera.
Related
Can anyone tell me how to disable or delete an unwanted firmware update? It could be an official ICS update but I can't tell.
If I try to accept the installation, it reboots the phone but then the update fails with the message
"Software update
Failed to update firmware. Try again using PC software (Kies) or visit a Samsung service centre."
I then get the update notification again and the only option I have is to postpone the install for later. Is this happening because I have already flashed the ROM with the version below?
N7000DXLR2-------4.0.4-------------2012 July--------------N7000OLBLR1----------Singapore (SingTel)
I have Root Explorer and Superuser apps installed.
Grateful for any advice.
Trevor
setting - about phone - software update
uncheck auto update and push notification
Hi guys,
On Nexus 6P, with recent October security upgrade (not over OTA but, system images) I have noticed that device is without root even with flash of most recent (SR5 SuperSu 2.82). Flashing from TWRP looks right as it should. All process tasks pass without failure. System reboot twice on initial booting as regular.
Once system is up an running, not root was detected by apps.
The strange thing is that SuperSu app was missing.
When I try to install it from Play Store, or from Superuser.apk from ZIP file, install was successful and still not root, no SuperSu app etc.
Is there any chance that Google starts to filter SuperSu app from Android and prevent it from running ?
When I try to install SuperSu app from Google Play, as soon as it is installed, I am getting "Install" button again like it was not on the phone.
Anyone with similar issue?
Paxy said:
Hi guys,
On Nexus 6P, with recent October security upgrade (not over OTA but, system images) I have noticed that device is without root even with flash of most recent (SR5 SuperSu 2.82). Flashing from TWRP looks right as it should. All process tasks pass without failure. System reboot twice on initial booting as regular...
Click to expand...
Click to collapse
I've got a feeling that this isn't SuperSU specific but, I could be wrong.
Try posting this question within the following thread to see if others with your same device experienced the same issues.
https://forum.xda-developers.com/showthread.php?t=3206934
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Okay so i did a clean install of the stock rom (Pie) with May update. Flashed all the files and was finally at the home screen. Got a notification for June security patch and i installed it immediately. Keep in mind till now no modifications were done to the phone including rooting, the rom is stock, clean and without any modifications. The only thing unlocked is my bootloader.
I observed when the update reaches around 80% it says update unsuccessful. No changes were made to the system. I tried downloading the update again, rebooting, formating/wiping data both via stock recovery as well as TWRP, factory reset. Even tried updating without SD-card just in case. Again flashed the full stock rom but to no avail, the update was not successful.
Any ideas why i can't apply june update and how am i supposed to solve this? Thanks
mhp1995 said:
Okay so i did a clean install of the stock rom (Pie) with May update. Flashed all the files and was finally at the home screen. Got a notification for June security patch and i installed it immediately. Keep in mind till now no modifications were done to the phone including rooting, the rom is stock, clean and without any modifications. The only thing unlocked is my bootloader.
I observed when the update reaches around 80% it says update unsuccessful. No changes were made to the system. I tried downloading the update again, rebooting, formating/wiping data both via stock recovery as well as TWRP, factory reset. Even tried updating without SD-card just in case. Again flashed the full stock rom but to no avail, the update was not successful.
Any ideas why i can't apply june update and how am i supposed to solve this? Thanks
Click to expand...
Click to collapse
Clear data of all the ported apps(or the apps which are not installed from playstore) and then uninstall these apps and then try to install June update . Same thing works for me. It showing same error to me but after doing these things my phone updated successfully.
[email protected] said:
Clear data of all the ported apps(or the apps which are not installed from playstore) and then uninstall these apps and then try to install June update . Same thing works for me. It showing same error to me but after doing these things my phone updated successfully.
Click to expand...
Click to collapse
I have no ported apps. As i said, its stock rom with no modifications. I didn't install any app from anywhere. The only apps i have in my phone are pre-installed apps which come with the stock rom such as Google Drive, Play Books.. I even tried clearing the data of the pre-installed apps but still no update. Also today i tried flashing the retail version of the stock rom with may security update. I think there is an issue as i flashed the retail version of the rom, the about section from the settings app still shows software channel as "Retin". Shouldn't it be showing retail version
mhp1995 said:
I have no ported apps. As i said, its stock rom with no modifications. I didn't install any app from anywhere. The only apps i have in my phone are pre-installed apps which come with the stock rom such as Google Drive, Play Books.. I even tried clearing the data of the pre-installed apps but still no update. Also today i tried flashing the retail version of the stock rom with may security update. I think there is an issue as i flashed the retail version of the rom, the about section from the settings app still shows software channel as "Retin". Shouldn't it be showing retail version
Click to expand...
Click to collapse
Try flashing this stock rom
https://mirrors.lolinet.com/firmwar...PT29.74-25_64be_release-keys-cid50_oem.tar.gz
You have to flash the first pie update (November patch) and then you can do updates.
I have Magisk 20.1 (Magisk Manager 7.5.1) currently installed on my Samsung Galaxy Tab A (2016). While initially installing it was not as straight forward as it might have been (install doc could use some work; I think it's written for folks with more familiarity with android devices on a day to day basis than those who root a phone maybe once every few years); I installed Magisk and it's been working fine.
However, this morning I had a notification that I needed to run Magisk setup. I told it to do so; it downloaded something; rebooted the tablet ( which wasn't warned of in the notification); and on coming back up ran Busybox so I'm assuming that was the setup. Going into Magisk Manager, however, I got the same notification over again. So I let it update again with the same result.
This time I told it to cancel the update/setup. I then tried to manually do the update from 20.1 (20100) to 20.3 (20300, latest available version). Update proceeded normally until repacking; which failed. Since Magisk is already installed and working (with several root level apps) on this phone; I can't see where this could be the "wrong image problem" which seems to be the most prevalent root cause of this kind of error. Unfortunately the update as distributed doesn't say anything about *why* it can't repack the image; so the message doesn't help us ordinary folks in debugging.
Any ideas as to what the actual issue is?
Android info:
Version 8.1.0
Kernel 3.18.14-1570595
Build M1AJQ.T580UEU4CSC1
Note: Busybox had an update I believe came out sometime yesterday (saw notification it updated successfully). Could it be that something in the Busybox update broke the Magisk update process?
I've an issue and don't know how to resolve. My pixel 5 has an Google play update to install (at the moment I've installed update from 1 October 2022), tried to install an update with enabled magisk modules and after succesfull installation - phone has boot again after few seconds and an update is reverted (should be December update and it backs to October).
I've tried to upgrade with disabled all modules and it works well (with January 2023 version), until i enable one of modules. After reboot phone restarts after few seconds and backs to October security pack.
I've no idea what to do with that - should I try with flash stock boot.img and remove magisk? Update phone and flash boot with magisk and then boot partition with flashed file?
Are ya installing update manually? Like downloading apk file and installing it?
Haven't tried. Are you thinking that this might be solution?
https://m.apkpure.com/pl/google-play-store/com.android.vending
I am talking about security Google play update (settings/security)
Google Play Store 34.2.13-21 [0] [PR] 503494674 (nodpi) (Android 5.0+) APK Download by Google LLC - APKMirror
Google Play Store 34.2.13-21 [0] [PR] 503494674 (nodpi) (Android 5.0+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Try installing from here....
Not possible to install. It shows an error that this package is in conflict with installed app. And it's correct because I've installed the same version.
I'm not sure that we're talking about the same thing so the second screen is from security section and Google play security update
Oh, I thought it was an play store issue but it is something else. Lemme search over it, then will tell ya.
In question you said "Google play Update" but its an software security update.
It maybe because of ROOT, as its an security update, try unrooting and then updating, then reroot.
Oh man, you're totally right. It was so easy to fix this. Thank you for your assist.
I've unrooted device, do an update, then root again and all works well.
inzaghi89 said:
Oh man, you're totally right. It was so easy to fix this. Thank you for your assist.
I've unrooted device, do an update, then root again and all works well.
Click to expand...
Click to collapse
That's good