I need to install AFWall+ on my sister's Note 5 to protect her, both from apps using her data as she's on PAYG and to ensure that when she's out the apps can only connect via VPN, not insecure public WiFi.
On my Note 4, when MIUI updates I have to boot into TWRP and then exit it to install the update, then go back into TWRP to re-root by flashing Magisk, then reinstall Xposed. My sister won't be able to cope with that, so I can either flash a custom ROM which doesn't do OTA updates or, if possible, block MIUI from checking for and downloading updates. The latter method has the advantage that I can unblock it temporarily when I'm around and install the latest update and do all the other steps for her, whereas if I install a custom ROM I'll have to flash a new version to update it, which is more hassle.
So would you agree that blocking updates is the best approach and is that actually possible, maybe by using App Quarantine to freeze certain system apps?
doveman said:
I need to install AFWall+ on my sister's Note 5 to protect her, both from apps using her data as she's on PAYG and to ensure that when she's out the apps can only connect via VPN, not insecure public WiFi.
On my Note 4, when MIUI updates I have to boot into TWRP and then exit it to install the update, then go back into TWRP to re-root by flashing Magisk, then reinstall Xposed. My sister won't be able to cope with that, so I can either flash a custom ROM which doesn't do OTA updates or, if possible, block MIUI from checking for and downloading updates. The latter method has the advantage that I can unblock it temporarily when I'm around and install the latest update and do all the other steps for her, whereas if I install a custom ROM I'll have to flash a new version to update it, which is more hassle.
So would you agree that blocking updates is the best approach and is that actually possible, maybe by using App Quarantine to freeze certain system apps?
Click to expand...
Click to collapse
Most of non-miui rom don´t have OTA updates but in the case that they have it is perfectly possible disable automatic updates.
The same with Miui roms, you can adjust it to your preference in Update settings enable "Download automatically" but disable "Install automatically".
Better use a cusrom, no need for OTA update
At least not frequently
SubwayChamp said:
Most of non-miui rom don´t have OTA updates but in the case that they have it is perfectly possible disable automatic updates.
The same with Miui roms, you can adjust it to your preference in Update settings enable "Download automatically" but disable "Install automatically".
Click to expand...
Click to collapse
Thanks, I didn't realise I could just disable the updates. I'll probably disable the download as well and just enable it when I'm ready to update for her, just in case it prompts her to update otherwise.
zoel.fahmi said:
Better use a cusrom, no need for OTA update
At least not frequently
Click to expand...
Click to collapse
I'm not sure, as MIUI on my Note 4 seems to get updates quite often and obviously it's a good idea to patch any bugs that have been found ASAP, whereas with a Custom ROM there can be a long delay before an update is available and then the update process is more complicated. Not to mention that Custom ROMs often have bugs of their own, or certain features not working, so I guess it depends on whether any Custom ROM has particular advantages that outweigh the disadavantages compared to running MIUI.
doveman said:
I'm not sure, as MIUI on my Note 4 seems to get updates quite often and obviously it's a good idea to patch any bugs that have been found ASAP, whereas with a Custom ROM there can be a long delay before an update is available and then the update process is more complicated. Not to mention that Custom ROMs often have bugs of their own, or certain features not working, so I guess it depends on whether any Custom ROM has particular advantages that outweigh the disadavantages compared to running MIUI.
Click to expand...
Click to collapse
Most of the custom ROM are bug free
Even miui has a bug even after update to patch the bug before that.
Clearly you never use a custom ROM
Related
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Chimpdaddy said:
I'm still on a rooted 4.1.2 and have the second OTA update to 4.3 (.109) in my notifications. Rather than go through the whole flashing process, I wondered if anyone had successfully used the Survival mode in SuperSU to retain root from this point to .109?
Click to expand...
Click to collapse
you can try ot yourself,.but i reckon it will give you error while applying update.
Rootk1t said:
you can try ot yourself,.but i reckon it will give you error while applying update.
Click to expand...
Click to collapse
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Chimpdaddy said:
Yup, I'd read similar. I was more concerned that it would update but I'd lose root, so have to then do the full process.
Click to expand...
Click to collapse
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
bjrmd said:
I have a rooted 422 with su pro, The update process aborts mid way and the OS is left untouched, leaving all as it was. I am just too lazy to do the flashtool thing and all, so I left it alone.
I was able to go from 412 to 422 with the OTA and keep root.
Click to expand...
Click to collapse
I know, so lazy, if I wait long enough 4.4 will come around and that might keep root!
Nobody's read a successful account of this working then? I may as well just try it and see...
Possibly
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed.
I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root.
If you have CWM or TWRP installed then it won't let you update.
adielee said:
If you have bought Supersu pro then you could try survival mode, provided that your phone is only root and doesn't have a custom recovery installed. I personally haven't tried it on my tablet but on other phones like G2, OTA update retains root. If you have CWM or TWRP installed then it won't let you update.
Click to expand...
Click to collapse
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Cat McGowan said:
Judging by all the posts I have read here so far, attempting to update to 4.3 via OTA will fail if your tablet's current firmware has been modified to have root access. Having SuperSU Pro installed with Install SuperSU into /system and/or Survival mode enabled does not help. I have attempted an OTA update with 10.4.B.0.577 and 10.4.1.B.0.109, and the update failed in both attempts. It's okay with me though. After reading about 4.3's bugs and seeing its UI, I don't really want to update to 4.3 anymore.
Click to expand...
Click to collapse
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Rootk1t said:
you're right, but besides bugs introduced as every firmware does, some very positive tweaks were done "under the bonnet" like TRIM enabled to make less wearing of flash modules, and some performance tweaks noticeable not only in launcher, but mostly in games too.
So if you have root and recovery installed you can backup your data and install .109 prerooted firmware to evaluate it yourself.
Click to expand...
Click to collapse
I would also recommend to flash a pre-rooted 4.3 from scratch for performance and less issues, but if you have a lot of apps installed and everything set up the way you want it can be a pain in the a$#.
Also the OP doesn't want to flash. But if he can it means that the OTA won't install because he has a custom recovery.
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2)
It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
adielee said:
I don't see why Supersu pro with survival mode won't work for an OTA to keep root. This is provided that a you do not have a custom recovery installed. It's kind of the purpose for survival mode and if you do a search it works with most other updates with other devices (even for 4.4.2) It may be possible that other mods may affect the OTA especially ones which were flashed or possibly xposed.
Click to expand...
Click to collapse
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Nope
Cat McGowan said:
I do not have (nor do I want) a custom recovery or custom ROM installed on my XTZ. I only have root access, which I achieved by using DooMLoRD's Easy Rooting Toolkit when I first received my XTZ back in May 2013. Since then, thanks to SuperSU Pro, I have updated my XTZ's firmware via OTA twice without losing root access. It is only with the last two XTZ firmware releases, 10.4.B.0.577 and 10.4.1.B.0.109, that the OTA updates fail. I suspect Sony's latest firmware releases include detection of root access, etc., which causes the update's failure to install.
Click to expand...
Click to collapse
Well, I tried it, thinking the worse that could happen is that it would abandon the install, but unfortunately it went right through and upgraded to 4.3 and I lost root
I'd put it into OTA survival mode but not into system/apps. I had no xposed or recovery anything, just root.
So there we go. Thanks for the discussion guys, hope this is useful to someone else.
How do I root it in 4.3? Any ideas?
Try this
http://forum.xda-developers.com/showthread.php?t=2703774
Sent from my SGP311 using xda app-developers app
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
harryspar said:
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
1) Will I lose functions such as the fingerprint reader if the device is rooted?
if you install the stock rom you will keep this functionality otherwise you need to wait concerning CM13 build
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
there is always a risk but minor
harryspar said:
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
wickedesires said:
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
Click to expand...
Click to collapse
Right, I remember this happening with other devices, as the OTA uses a recovery script.
I wonder if there will be nag screens for OTA's. This rendered my wife's S4 so annoying to use, with a persistent notification, until I found a block method (disallowing notifications didn't work since I'd have had to disable notifications for the entire Android System UI...)
harryspar said:
I wonder if there will be nag screens for OTA's.
Click to expand...
Click to collapse
I went about 5 days before I installed the b140 update and I don't recall any annoying notifications. I know exactly what you mean though my s5 active did the same thing because I didn't want to update and lose root. I finally found a way to disable it but like you said it was very irritating.
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?