What can I do about a system update that will not install and won't go away...
Carlito's Way
Related
my bionic will reboot fail to update and then reboot and say update failed i unfroze all the bloatware and still no go
i'm actually having the same issue. im not sure if it has to do with rom tool box as its the app that i used to install custom icons on my status bar or just the fact that im rooted but i can't seem to update to 905...i know i'm on the OTA path as when i go to the updater it shows i have an update for 905 from 902......
yup thats exactly my case as well
Your best best is too fxz to stock and follow these directions.
http://forum.xda-developers.com/showpost.php?p=27832332&postcount=1
Coming from a RAZR, I did the following.
1. Root device on 905
2. Place update in /cache with es
3. Ensure rom manager is installed
4. Click the zip that you placed in the /cache folder.
5. Click reboot and install from the rom manager menu.
6. Allow root permissions
7. It'll boot into stock recovery and boom.
Sent from my DROID BIONIC using Tapatalk 2
After updating to the latest build 4/23 using system update open delta and installing from twrp, I got system ui crashes after system boot! Anyone who can help me with this?
My bad! It's my fault. I did not check the mount system in twrp. It's okay now. BTW, about open Delta again, when I downloaded the latest update the one downloaded from open Delta is the entire rom update, or it's just the update files from the previous week like in stock updates? And when it enters twrp it's just install the entire rom no other options to mount system or wipe cache? Is this really the correct way to update using open delta? I'm new with open delta so forgive me with all these questions coz I got system ui crashes after installing the entire rom update using open delta and forget to nandroid backup coz I'm assuming that open delta is error free. Thanks...
Sent from my H220 using Tapatalk
Im still getting system UI crashes after installing the latest incremental update 4/30 using opendelta system update. I tried manual updating using TWRP with system mounted and restoring data, still system UI crashes. What's wrong with this?
Here is the logcat thru adb:
http://cloud.tapatalk.com/s/5905b8a22ead1/logcat.txt
Sent from my H220 using Tapatalk
thread closed - marked as SOLVED as per OP request
For various reasons I don't want to update to pie on my tmobile galaxy note 8. There is a pending update that I have postponed but it is still there and taking up space and I could accidentally tap on it in notifications.
Let's be clear. I am not downgrading. The update is NOT installed. The firmware image or whatever is downloaded but not flashed.
I want to:
1. Disable the updater so it won't keep nagging me or keep downloading the 1.7gb update file.
2. Delete the update file that is taking up space.
Factory reset the phone Download bk package disabler and disable all updates.ive done this android pie is trash on the note 8.also go into developer mode and to turn off auto update
Google has changed the way they push and apply OTA updates via GMS, and thus making Magisk Manager's "Install to Inactive Slot" feature bootlooping Pixels. I think I'll hide this option temporarily in the next release before I have time to figure it out (topjohwu)
https://twitter.com/topjohnwu
[Guide] How-to OTA update without loosing Root - Stuck in "Preparing system update"
Hello All, here is a quick guite to avoid getting stuck in "Preparing system update", if you forget to disable automatic system updates you will need to sideload...
The difference between this guide and others is to restore boot images BEFORE checking for updates
1. Make sure automatic system updates are disabled - THIS IS A MUST
Open Settings -> System -> Developer options
Disable 'Automatic system updates'
2. Open to Magisk
Click on UNINSTALL in the bottom
Click on RESTORE IMAGES (You will see Restoration done!)
Once done, DO NOT reboot
3. Now search for System Updates
Go to Settings -> System -> System update
Press 'Download and Install'
Once done, DO NOT reboot
4. Open to Magisk
Click on INSTALL button (for 'Magisk is up-to-date' option)
Press 'Install' again (in the popup)
Press 'Install To Inactive Slot (After OTA)'
Once done, reboot
Please keep in mind that if google detects Magisk (you will get stuck in preparing system update and then no updates will be found), you will need to sideload ota, and re-root your device, to use this guide.
This works on pixel 3, pixel 3XL. pixel 4XL as well
Awesome, I did not know that restoring images would make OTA updates show up!
I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?
XDA_chron said:
I have rooted and installed magisk in my note 10 pro and even though I see the update in the settings and can download it. The update doesn't get installed and opens the TWRP recovery which then just fails and restarts without installing the update. Is there any way that I can install the OTA update?
Click to expand...
Click to collapse
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.
Dron74 said:
Previously, updates were downloaded to the / sdcard / downloaded_rom folder (if you look at the path from the phone) in the phone's memory, check in TWRP, if there is no firmware file there, then download the update from the website, load it into the phone's memory or a flashcard and update. After updating, without booting into the system, flash the archive using magisk and then boot into the system.
Click to expand...
Click to collapse
Instead of doing all of these things I was thinking of waiting a month or two and installing the pixel experience rom