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
Related
I used Safestrap on my Moto Bionic and would like to find a similar app that will make a complete recoverable backup of my device. I don't want anything that requires an unlocked bootloader due to the problems with OTAs. I don't use any custom ROMs, I just like to install MODs to the UI. My phone is already rooted VIA flashing the rooted image and OTA rootkeeper to update. I would like to try the MOD to add apps to the multi window drawer and fix autocomplete. It seems that it's not just as simple as replacing apks so I'd like a good backup/recovery solution in place before getting stuck in a bootloop. I could just reflash with odin but I'd rather backup the current state.
No there's nothing like safe strap. If you took the ota update then you have no choice but to use Adams unlock method to root which installs a recovery. Otherwise the only mod you listed is here: http://forum.xda-developers.com/showthread.php?p=34994272 for adding all apps 5o multi Window.
Why wouldn't you want team win recovery? If you're concerned with ota problems just freeze "SDM" after you gain root access. Then the phone won't automatically update.
Sent from my SCH-I605 using Tapatalk 2
there is no safestrap bull**** on a sammy device as mentioned above. root,unlock,recovery, then you can make all the back ups you wish. i would like somebody to give me a logical reason why they would want to take a OTA update? i flash all my updates via recovery provided by our gracious devs. PHUCK a OTA!!!
safestrap is not great and sucks. The only thing I liked about safestrap is that you can have 3 different ROMS to play with and boot up real fast. Use clockwork and you should be okay. Once you get clockwork or TWRP make your back up and you are set.
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 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.