Just wondering if I'll be able to take an OTA update from 6.0 to 6.0.1 whenever it is available? I received a message saying a software update was available and when I told it to install it, it rebooted into TWRP, checked the current software for about 3 minutes, then rebooted? Upon looking, I am still on 6.0? I had the system check to see if there was still an update available, but it said there was nothing. Maybe it was just a radio update? I am anxiously awaiting the update so that I may install Xposed. Any input would be greatly appreciated :good:
AT+T US Unlocked
Rooted/S-off
6.0
1.10.502.3
You can't take OTAs with rooted phones and twrp. The OTA looks at the system partition and if anything is changed...it will not install.
You have to either take a backup somebody made with the OTA/stock basically. Flash it via TWRP. Or RUU back to the lastest for your phone. Then, take all OTA updates, then TWRP, Format Data, then SuperSU again, reboot...start/restore phone.
There is no easy way without Dev support/Custom Roms to get latest bases/OTAs right now without wiping/starting over somehow.
This is why having devs creating Roms is really a luxury. Because they already have the proven installer/Rom customized. They will then take OTAs/new bases, roll that into their Rom, and you just do an update/flash, like Viper, and not lose anything, and no need to wipe.
Likely never to happen with this phone since Devs really only work on the Mainline/Flagship M models, like M8/M9/M10 etc...
Related
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
moreisbetter said:
I have been searching on the forum and Google but no answer. I had a Sprint Galaxy S3 and it was rooted with custom recovery Clockworkmod. After an update was available I could not install the update, failing with the message "verification failed" when trying to apply the official update file. I couldn't find an answer so I went back to stock recovery.
Now I have a verizon S3 and I would like to back up an image of my phone with clockworkmod but I would like to be able to update, especially with the looming jellybean update coming soon. Did I miss a way to install the updates to the official rom with clockworkmod? Or was it simply not possible.
Click to expand...
Click to collapse
With most custom Roms...being able to do OTA updates is blocked because it could interfere with the rooted Rom you are running...its more or less a safety feature for that purpose. If you want to get the new Jelly Bean OTA update, you will have to flash your device back to unrooted stock and it should work just fine...as long as ur rooted, you wont be able to, if im not mistaken.
Thats true, and there is the whole bootloader thing! Now that we have all hacked away our bootloaders, the OTA just won't happen. Hopefully an easy relock becomes available for the vzws3 before that update is released, but I wouldn't panic - big red will probably release it to us after everyone else has gotten it and out phones are outdated! In general though, within a week or two of an official large release, the amazing devs on this site will have a downloadable version available for us to manually install.
If you have modded your phone, never try to take a OTA update. At the least you will lose root abilities. At the worst, potential bricking of your device.
Usually before, lol, if not just after a OTA, the devs have working release for our devices.
Take it easy, relax.
I am on stock 4.1.2, VRBMB1. I am rooted, unlocked and with TWRP recovery. I have used Titanium to freeze SDM 1.0.
I am considering going to VRBMF1. I don't know how to safely get there. I also don't know what improvements might come with the OTA to MF1. Should I just hang out with VRBMB1 until the rumored update to 4.3 arrives? I would like to be in the position to return to what I have now (just in case), or be able to move to 4.3 if, and when, it come out. How do I proceed? Thanks
I have the same question... subscribed!
Is there a rooted/unlocked update file, or do I just run the VZ update and use Voodoo rootkeeper to restore root (or Casual unlock again, if needed)? Or dirty-flash one of the rooted/unlocked stock ROMs (and then the firmwares)?
So many ways to get there, just looking for the safest... I figure the VZ update might be best.
So, I finally bit the bullet. I backed up all kinds of things before running, but it seems I didn't need to. I unfroze SDM, and then checked for updates. It downloaded and then rebooted to install. Since CWM was installed, it tried to perform the update, gave a few errors, but I let it go anyway. After the main install was done, CWM asked me if I want to let the updater install a new (stock) recovery - I said no. Then it said that I may have lost root, so do I want CWM to fix it - I said yes. Then I cleared the cache (just in case) and rebooted. The phone booted up, said it completed the upgrade, and then dropped me back into the rooted OS. Pretty cool.
SDM did complain to say that the updated "didn't happen" but the phone shows the new MF1 version, and a few new apps as well. So, obviously, the update happened... and I didn't lose root or recovery. Damn nice...
I wonder if TWRP does the same things (disable the stock recovery and restoring root)...?
EDIT: Reading the TWRP page says that they don't support nor recommend applying a stock ROM update.
Secondly, I found that while my phone was working fine, when I tried to get into recovery, it popped up the unauthorized software error. Meh. I used the Casual rooting tool to reroot, apply the insecure aboot, and then reapply CWM... and I'm back to normal now. Not a big deal, but still more steps than I thought I needed above!
I haven't really been into screwing with my phone but since they finally fixed that bad update, I might try to at least get new system software.
I am still on VRBLK3, I am rooted and pretty sure I unlocked the bootloader last year but can't remember. However when I try to get into the recovery, I get the Samsung logo and a bit of text at the top and then it just shuts down again. So I'm guessing in this case a full ODIN of a new ROM is going to be necessary or can I have a go with just installing a recovery and trying to update?
And since I am back on VRBLK3, do I have to do incremental updates or can I just go with this latest one or a new ROM?
Thanks!
You have use odin back to stock. You don't have to doil incremental updates as all stock firmware are available online.
So i eventually received my lollipop OTA this morning (UK, EE).............
But what exactly do i do with it
I'm rooted (Locked BL). I obviously can't install the OTA the normal way, can i ?
I was waiting for some custom ROMS to be made available but don't seem to see any. Will these follow soon since the Lollipop update has went global?
I'm kinda torn tbh.... i have my phone set up perfectly on KitKat and it looks amazing and some of my favourite xposed tweaks aren't available on Lollipop e.g. Blurred System UI.
Anyway...If i should decide to install Lollipop (i probably will) what would be the best method?
(Are we talking going back to stock, installing OTA, then re-rooting, or is there a more simple method?)
I believe u only lose root. Install and re-root is my fiddy cent...
Download your respective firmware and make a pre-rooted rom based on it.
And flash it via recovery.
Stick with KitKat.
Sorry to hijack the thread but if I root without unlocking bootloader, will I get to update normally via ota or companion app? I don't mind losing root access if only to reboot later. And does it affect drm keys etc?
I'm rooted with kitkat and received the prompt for lollipop OTA. The point is it downloads but won't install, so to upgrade you'd need to use flashtool, PC companion or boot into recovery and flash an appropriate zip. None of those should have any effect on your DRM, but you'll lose root unless you're flashing a pre-rooted version of lollipop. If you do opt for a rooted version of lollipop it's still a bit unclear whether recovery is fully available to you, and xposed installer has a rack of issues either way...... you might want to hold for now?
Thanks for that I'll wait it out for now. The only real reason I was really updating was for the move to sd feature. Do anyone know of any alternatives?
The point is, I just wanted root until the ota. So it will update normally via sony PC companion?
OTA Can't Verify on Rooted Device
I noticed the update this morning. Phone rebooted like it was going to work but didn't. Now it allows me to download it over and over and each time it says "could not verify". Is there any good reason to want this update? I'm rooted on the 77fw and my phone works fine as is. I do not want to update and find out I lost root. Unless there is a very good reason to, I'll just wait and see if a rooted zip becomes available.
Stickin with kitkat. I will not run without root.
So now that I am rooted a can no longer receive OTA updates. Also, being a Sprint\Tmo device, I don't have "Local Upgrade" option.
Can someone tell me how I would now go about updating my device?
Do I simply wait for A11-based rom?
Do I need to remove magisk\modules in order to re-enable OTA?
Any help is appreciated.
I was actually about to ask this very question myself, the local update is missing on mine too, so that didn't change when you rooted? Maybe you can flash one of the stable releases they came out with recently? My question was would the global version work for our tmobile branded devices.
Also wondering wtf is up with tmobile cutting features out of the updates like shelf that dropped in July.
There is a guide to switch to global firmware.
It seems straight forward.
I would rather not.
If there was a stock rom image that we could simply flash via magisk or twrp, the process would be far simpler.
My guess is that for the method above to work, we will need to wait for A11 source code to drop.
Afterwards, we will likely see full A11 roms that we can use.
Ideally we would wipe system, data, cache. Flash rom. Wipe data again. Reboot.