I think I messed up while trying to update both my phone and magisk. I believe I updated the system using the recommended procedure with Magisk, then decided I didn't want Magisk any more due to the fingerprint sensor being broken and locked the bootloader (I don't remember whether I uninstalled Magisk first, but I believe I did). Now, OTA updates fail immediately and any attempt to boot into the b slot fails (including when LG Bridge reboots at the beginning of the update process).
The phone still works and the a slot is completely valid, but it seems impossible to install an update without valid b partitions. Is there a way I can still update without losing whatever files and settings a backup inevitably won't save? Unfortunately, the bootloader is locked, so even if the b partitions are still viable but just have Magisk installed, unlocking my bootloader would require me to wipe my phone.
Related
HI, do the OTA updates still work after unlocking bootloader, installing TWRP and rooting?
I've ordered one and was thinking about doing the about doing the above right out of the box.
Yes, will work
pratikp16 said:
HI, do the OTA updates still work after unlocking bootloader, installing TWRP and rooting?
I've ordered one and was thinking about doing the about doing the above right out of the box.
Click to expand...
Click to collapse
OTA AFTER
Unlocking bootloader - Yes
Installing TWRP - probably yes, but it might replace TWRP with default recovery during update
Rooting - idk
Hey guys
I would like to bring this topic up again because I want to be super sure.
I unlocked BL, installed twrp and rooted with supersu, stable Rom.
Now I got ota update notice. Is it save to update or will it brick?
No, you probably will end with an unbootable device or defective operating system (but it could work too, it's unpredictable without trying).
You will end flashing a fastboot image via MiFlash, so better not OTA updating and flashing directly a full ROM image when you're ready to update.
If you want to try the OTA update, backup your data before because it could become inaccessible after.
BubuXP said:
No, you probably will end with an unbootable device or defective operating system (but it could work too, it's unpredictable without trying).
You will end flashing a fastboot image via MiFlash, so better not OTA updating and flashing directly a full ROM image when you're ready to update.
If you want to try the OTA update, backup your data before because it could become inaccessible after.
Click to expand...
Click to collapse
OK, will loose settings and App data when flashing the (updated) full stock image?
edwardenglish said:
OK, will loose settings and App data when flashing the (updated) full stock image?
Click to expand...
Click to collapse
If I remember well, there should be an option to retain settings and apps data (it depends on what .bat file you choose to flash), but I advise against preserving this data, as it will probably cause many problems afterward.
BubuXP said:
If I remember well, there should be an option to retain settings and apps data (it depends on what .bat file you choose to flash), but I advise against preserving this data, as it will probably cause many problems afterward.
Click to expand...
Click to collapse
Yes that's what I thought so too.
So to sum it up correctly with unlocked BL and root one should only update via flashing whole image and do a clean flash loosing all data and settings.
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?
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.
I was trying to install a custom rom and was not aware that you can only unlock the bootloader by paying, which is fine but I can't afford it at the moment but by then I downgraded my rom.
I returned to version 9 on my phone OS and was hoping to get updates afterwards through official updates as I was restoring back to stock but I made a mistake and downloaded and installed ANE-LGRP2-OVS 9.1.0.200 which was not the correct one.
I have tried a few roms, copied to SD card in the dload folder but no matter what I try it keeps failing. No matter what I try downgrades and upgrades won't work anymore.
It seems similar to this: https://forum.xda-developers.com/t/downgrade-ane-lx3-ane-lgrp2-ovs-pie-to-oreo.3944399/
Everything does seem to work fine on my phone except the update system and google pay is not happy and not enabling contactless (which I use all the time)
Is there anything I can do to fix my dumbness
How does the dload method fail? Or is it successful in installing a different firmware yet the official update service is still broken?
Have you tried the forced dload method and did a factory reset/wipe data immediately after installation in recovery?
lemon567 said:
How does the dload method fail?
Click to expand...
Click to collapse
for several reasons .
In this specific case it is due to installing the wrong FW (ANE-LGRP2-OVS ). With this build number it is impossible to install another full stock FW or update system via OTA.
I totally forget to mention on here that I solved it. I managed to get hold of a version 8 stock rom and installed it to the SD card, then it was happy to update itself from there all the way up to current version.
I don't know why it worked at that point as I'm pretty sure I tried that same thing several times before but sometimes there are things I cannot explain, it just randomly worked all of a sudden