I have a Samsung Galaxy A5 2016 (A510F) running Marshmallow. It's rooted, custom kernel, custom recovery, tripped Knox, but the rom is stock (although it has been reflashed a couple of times). Usually you're not able to get updates from official channels with this configuration, but I have the system status faked as "Official" so I'm able to get official OTA updates.
Now my question is: will installing such (official OTA) updates cause any problems to my phone (bricks, instability, bootloops...)?
Restoring a nandroid is an option, but I would like to hear the community's thoughts.
Related
I rooted my phone just for the sole purpose of using wifitether and kept the stock rom. I didn't use the wire trick, so I don't think I fully rooted it? Any case, I have a notification to do an OTA system update and I'm afraid to do it since I have the phone exactly how I want it.
If I don't need to update, how do I hide the notification? What does the update do?
Thanks!
big irn said:
I rooted my phone just for the sole purpose of using wifitether and kept the stock rom. I didn't use the wire trick, so I don't think I fully rooted it? Any case, I have a notification to do an OTA system update and I'm afraid to do it since I have the phone exactly how I want it.
If I don't need to update, how do I hide the notification? What does the update do?
Thanks!
Click to expand...
Click to collapse
OTA's require the stock recovery so you can't apply them when rooted. You didn't say which model (Sprint or VM) and that makes a difference.
For Sprint you can backup your apps, data and settings then relock the bootloader, flash the RUU and OTA, install a custom recovery and restore your backups. That will give you the updated firmware and stock ROM from the March OTA. In addition to the firmware updates, the ROM changes include the Sprint connection optimizer and some fixes for other software.
If you are a VM user and haven't installed the March OTA you can still use the above sequence but then you won't be able to flash the RUU if you decide to get S-OFF so you should do that first if you have any plans for it. After flashing the RUU there will be two OTA updates (November and March) to apply for the stock configuration.
ramjet73
I've just revived an OTA on my rooted international Galaxy S3.,
It says in the "Update Details" *You cannot downgrade to the old Software after this new software upgrade, due to the security reason.
This makes me think there going to lock my bootloader or something and if that's the case I'll just delete the update and change the phones internal settings so it won't download OTA's.
Recently I've been keeping my phones pretty much stock, a few small tweaks and a few apps that require root,
I'm thinking it will probably just fail the OTA update with the phones status now saying / being modified.
I've also got Mobile Odin installed with enable Everoot, Inject SuperSU and Inject Mobile Odin.
Has anyone been through this ( Int SGS3 Stock Samsung firmware, rooted with chainfires root software - OTA to 4.3 from 4.1.2 if you have how did you get on ??
Any help greatly appreciated.
-
OTA will fail if you have rooted. If you want to update to 4.3 then best results come from wiping, format internal storage then flash MK6 via odin.
My SGH-I337 (ATT GS4) has been rooted for a month or two now but lately it's been having issues so I tried to restore it to stock. But, I manually removed the root via SuperSU so I would be able to update to 4.4 (I've been stuck on 4.2.2 because I was never notified 4.3 came out). Every time I update OTA it fails at 25%, so I tried via Kies. My firmware isn't even supported to update like that. I tried unrooting with Odin but that also didn't work. I've restored it to factory settings now, but the boot image still says custom and I can't use Yellow Triangle because that doesn't support locked AT&T basebands (which I read is unfixable). Is there ANY way I can fix this and get 4.4????
TL;DR
My phone is too rooted to OTA update but not rooted enough for Odin to work and I want KitKat
ghdawg6197 said:
My SGH-I337 (ATT GS4) has been rooted for a month or two now but lately it's been having issues so I tried to restore it to stock. But, I manually removed the root via SuperSU so I would be able to update to 4.4 (I've been stuck on 4.2.2 because I was never notified 4.3 came out). Every time I update OTA it fails at 25%, so I tried via Kies. My firmware isn't even supported to update like that. I tried unrooting with Odin but that also didn't work. I've restored it to factory settings now, but the boot image still says custom and I can't use Yellow Triangle because that doesn't support locked AT&T basebands (which I read is unfixable). Is there ANY way I can fix this and get 4.4????
TL;DR
My phone is too rooted to OTA update but not rooted enough for Odin to work and I want KitKat
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2663992
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
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.