Hi, my bootloader unlocked with twrp installed lgv30 keeps complaining about a system update, but each time i choose install it just reboots into twrp.
I presume the install process needs the stock recovery for something? I'm unsure how to proceed, and it will not even let me turn off the notifications!
Correct, OTA updates cannot be applied via TWRP and require stock recovery. Fact is, you don't want to apply the OTA, because it will break the OS anyway, so don't do that.
If you want the update, since these phones are old, chances are there is a TWRP version of the update already... and/or a KDZ. Either of those can be used as well. KDZ will wipe the phone, but TWRP can be "dirty flashed" over what you already have.
In order for anyone to help further, you'd have to tell us what you have to begin with.
As for disabling the notification, you can disable the updater app to stop this from popping up at all. This is detailed in many places as well.., and, again, requires us to know what you're running now.
Thanks for the info, mine is a Stock H930DS using the lastest stock Android 9 for Australia.
I'm not that fussed about the update itself, which I believe to be a minor security patch. Disabling the updater would be great.
I have the unlocked bootloader and TWRP installed, but not magisk, I imagine I could install that again via TWRP, but wanted to get back to as original as possible.
Related
So I have a rooted One M8 with TWRP recovery running 4.4.2. Recently an update came through for 4.4.3, to get rid of the notification I froze the updater. Now for the purpose of getting Viper One, I need 4.4.3. But when I press software updates it says 'There are no software updates avalible for your phone'. But there was prior to freezing the updater. Help me :silly:
(PS. Apologies if this thread is poorly located)
http://forum.xda-developers.com/showpost.php?p=51623014&postcount=7
es0tericcha0s said:
http://forum.xda-developers.com/showpost.php?p=51623014&postcount=7
Click to expand...
Click to collapse
Hey thanks for the reply but I don't think my problem is that complicated, is there anything you could recommend? The option to update was available until I froze the updater, now it's not.
:good:
Can anyone help?
I gave you a direct link from the rom you are trying to install that tells you what needs to be done. Not sure what else you would need. If you aren't getting prompts to update via OTA, there's 2 ways to update the firmware needed. Either via the official RUU for your phone and carrier (which probably isn't even available yet)or via a firmware package that's flashable via fastboot but you must be S-Off. Sometimes you can force the phone to check for updates by clearing the Google Services Framework, but this is not advised as it can have unintended consequences with how Google sees the phone and sends notifications and such. Plus just because there IS an available update does not mean you're next in line. Many carriers have staged roll outs and it'll get there when it gets there.
If it's too difficult for you then you either shouldn't be messing with custom roms or seek help from a qualified shop.
es0tericcha0s said:
I gave you a direct link from the rom you are trying to install that tells you what needs to be done. Not sure what else you would need. If you aren't getting prompts to update via OTA, there's 2 ways to update the firmware needed. Either via the official RUU for your phone and carrier (which probably isn't even available yet)or via a firmware package that's flashable via fastboot but you must be S-Off. Sometimes you can force the phone to check for updates by clearing the Google Services Framework, but this is not advised as it can have unintended consequences with how Google sees the phone and sends notifications and such. Plus just because there IS an available update does not mean you're next in line. Many carriers have staged roll outs and it'll get there when it gets there.
If it's too difficult for you then you either shouldn't be messing with custom roms or seek help from a qualified shop.
Click to expand...
Click to collapse
Thank you, the problem did however solve it's self. It turns out OTA updates are queued and by freezing the app I had reset my position. The update is now available.
I'm going to flash a stock recovery and update the firmware.
Hey guys,
I have my tablet since one week. I love it, all works fine, Xposed offers me OBB move and so on. But now I have a question:
How can I get the new Updates for my Tablet with ROOT/TWRP?I know OTA can't be updated due to TWRP, but is there any way to flash updates dirty?! (like with LineageOS, OxygenOS, ... )
At the moment, if I try to search for new updates, I get following message:
The operating system on your device hase been modified in an unauthorised way. Try downloading softwar updates using Smart Switch on PC or visit a customer service centre.
Maybe someone got an early version of the Tab S3 with early factory Android and can give some enlightenment.
Greetz,
CM
First, this should be posted in the q&a section. You're going to have to flash the upgrade firmware tar in odin. Then re-set up your device and re-root. It's a pita. Google has gotten better at saving your apps and data, which helps, or use something like titanium backup
isn't it enough flashing stock recovery and uninstall supersu via app?
I've been away from Samsung devices for awhile, I've been using Nexus but just got a tab3. I haven't tried this but it's possible that you could flash the update.zip that would be pushed to your device using flashfire. You would probably also be able to retain root and TWRP. Maybe someone with more recent samsung use could confirm that. However, based on the message you're getting the update looks like it won't be pushed to your device. And afik samsung doesn't publish the ota, only the full firmware so someone here would have to capture the ota and post it. Whenever samsung gets around to providing an update we can play around with it and see.
PS, do you have a flashable copy of the stock recovery?
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
drickles said:
I recently installed a custom recovery on my exynos s9+ on stock pie. I actually thought unlocking oem and installing a custom recovery + root would trip Knox and prevent me from getting any updates but it didn't. Was roaming on my phone today and somehow found myself in the phone update menu. I tapped on check for updates and low and behold I could download an update. My problem is now that I'm on a custom recovery how would any update i download even manage to install? And even if it does is there a possibility that it might cause troubles like re-enabling dm-verity lock and bricking my phone? I wanna know what might happen if I proceed to download and install that OTA update.
Click to expand...
Click to collapse
Personally I would not do the OTA as it may not update properly (if even at all). Every phone I have rooted before this was one of the cautions usually posted... I would double check in what ever tutorial, thread, utility faq you used to make sure.
I would suggest you wait for an update to be made that is flashable with your custom recovery. If your custom recovery has the feature (like TWRP) make a backup of what you have installed, flash the update and if things don't work you can restore your backup.
I miss having that kind of backup/restore ability via custom recovery on my phone.. sure comes in handy when things go sideways
Nothing happens. According to my experience and contents in the OTA zip, twrp will simply just spit it out. No dm-verity re-lock or bricking too.
You can always download one of the custom systems which are regularly updated.
Example would be Soldier ROM.
I recommend find your new firmware and flash it. You will lose all of your file and root-recovery you can have them all back
I picked up a second hand Galaxy S8 over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization?
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
jwoegerbauer said:
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
Click to expand...
Click to collapse
Thanks, I've heard different in the past. That OTA updates can lock you out of being able to run certain bootloaders for multiboot and such.
bump for input from others
Downloaded one S8 ota zip and checked. According to install-recovery.sh the command and path to fota package is on cache.
So going into recovery and wiping cache should do it.
edit: then again it might write it back on boot... but does it install it right away? IDK. Factory reset?
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
deusfaux said:
longtime Nexus / Pixel owner, and sometime in the last several months on this P6 ( or possibly since the beginning of this phone?), my OTA's are failing. They hit the 'resume when phone isn't being used screen', but despite swipe closing apps, laying the phone flat and untouched, plugging in charger, nothing will get the OTA update to continue.
I am rooted, otherwise vanilla A13, but this goes back to A12 versions too.
I am forced to sideload updates each month.
Not sure what's blocking the updates.
Anyone else having this experience?
Click to expand...
Click to collapse
You're rooted so you're failing the pr-OTA block verifications, thus the OTA is failing, is the likely scenario.
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
deusfaux said:
Is that a feature newer to later Pixels or Android versions? Didn't have that issue in the past. Maybe the difference is I could still download and *attempt* to install an OTA even b4 removing root, but now it checks in advance before even downloading? Next OTA I'll test this theory and remove root b4 even starting the download.
Click to expand...
Click to collapse
I normally manually flash updates with fastboot.
Only use OTA update on one or two devices.
You have to restore the original boot image.
Run the update and patch the new boot image with Magisk.
Normally the steps are something like this.
1. Open the Magisk app and restore images.
--- Do not reboot ---
2. Open the OTA Updater
- Download and install the OTA -
--- Do not reboot to continue ---
3. Open the Magisk app and install to inactive slot (after OTA).
4. Switch back to the OTA updater and select reboot to continue.
Cheers.
You could use PixelFlasher to make the process a little easier If you don't want to do everything manually each month.