OTA updates on rooted Galaxy S Relay? - Samsung Galaxy S Relay 4G

Hi all,
I recently rooted and installed a custom recovery per Jay Dogg's guide in the Galaxy S Relay. Development forum. I kept my stock ROM by choice and recently ready up on the recent Jelly Bean OTA update (MC5). I'd like to update but the official OTA update states you can't be rooted. I downloaded the update via Settings/About phone/update. Upon choosing to update, the phone rebooted to my custom recovery. It stated the certificate on the package was invalid so I backed off and just rebooted. I'm guessing my options are :
- Revert to an unrooted stock ROM, update to 4.2 (MC5) and re-root.
- Attempt to apply the official OTA update via custom recovery despite its complaints of certificate issues.
- Apply a non-stock or ripped ROM (not preferred at this point)
Can someone help me? I would like to avoid the hassle of unrooting, but that's probably my best option as far as I can tell. Any feedback is appreciated. I'm happy with the stock ROM's stability for now and don't really want to deal with the bluetooth / camera issues present builds of custom ROMs have.

Related

Clockworkmod + offical rom updates

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.

[Q] ROOT / Upgrade Assistance

I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
brennen.exe said:
I've gone through the root process on a dozen phones and tablets, but this is the first time I've gone through the process on a new device (to me) so long after its release, and therefore I'm finding the information I need to be a little... hard to pin down. I'm really just trying to be extra cautious with this one since I need it next week.
What I have: Android 4.0.3 ICS, ASUS Build v9.4.3.26
What I want: Android 4.1.? JB, ASUS Build v10.4.2.?? w/ Root/Recovery/Etc
With the above outdated firmware, I'm not sure if I should upgrade to Jellybean using ASUS OTA updates and then root/flash, or if I should use an older root method and upgrade to Jellybean by flashing a custom ROM, etc, etc, etc, etc, etc.
Edit: I should note that I was planning to follow this thread, but it was written under the assumption your tablet is already rooted with a custom recovery.
Click to expand...
Click to collapse
This is how I did it this afternoon on my new TF300T:
Rooted ICS with this: http://forum.xda-developers.com/showthread.php?t=1704209
Installed supersu: https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Updated su binary using supersu
Installed OTA rootkeeper: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper
Backed up su with OTA rootkeeper
Installed ES File Explorer(you really don't have to do this but I wanted to make sure some other app had root access before I upgraded to JB)
Made sure supersu authorized all these root apps by running them at least once.
Upgraded to Jelly Bean
Restored root access with OTA rootkeeper
Wiped the sweat from my brow afterwards!
I am staying with stock JB locked to keep getting OTA updates. If you want a custom rom, you need to unlock:
http://forum.xda-developers.com/showthread.php?t=2055886&highlight=unlock
Unlock APK is here: http://forum.xda-developers.com/showthread.php?t=1949758
NOTE: If you upgrade to Jelly Bean without OTA rootkeeper in place, you will not be able to root it without unlocking it first. There is no root exploit yet for the TF300 Locked Jelly Bean.
Yep. This will do the trick.
Still Charged Up
bads3ctor said:
This is how I did it this afternoon on my new TF300T.
Click to expand...
Click to collapse
Thanks badsector, I'll give it a go today and report back how it went.
Alright, thanks for the help in getting started, but I forgot to mention I had unlocked the tablet beforehand as a first step to another guide, so OTA updates were a no-go for me with this approach. What I ended up doing was, after performing 1-7 from your list, install TWRP using fastboot, manually install the JB update from ASUS, install TWRP for JB (again w/ fastboot), and then load a custom ROM. I'm all up to date and running fine, and had I intended to stay on the stock ROM I could have just left it at that when I flashed the ASUS firmware.
Thanks again!

[Q] Updating galaxy tab2 10.1 p5113

Forum members:
I recently user rooted my device per the forum excellent instructions but now am unable to to update the firmware for the android OS. When I get the popup notifying me that an upgrade has been downloaded, I go through the drill of rebooting to the Odin screen and then reboot but am then advised that the upgrade failed and something about using Kies. I user rooted the device in anticipation of installing Ubuntu but haven't done it yet. I intended to be able to dual boot depending on what I am working on. I use the android OS most of the time and it works ok but will not upgrade itself. I have searched the posts regarding the inability to upgrade android when the system is rooted but haven't found anything that I understand or that tells me whether or not it is even possible to upgrade the android OS when user rooted. Can anyone answer the question succinctly and if it is possible point me to instructions on how to do it. Any help is sincerely appreciated.
derwalrosz
Hi. That's right, you can't make OTA official updates anymore if you rooted the tablet.
You can however download the new firmware version from sammobile (official non-rooted) or some custom version from XDA, then flash it with odin or mobile odin (for official), or CWM (for custom "zip").
Here's a tutorial for Galaxy Note, but it might work for your tablet too - anyway it gives you an idea of how that can be done. The written procedure is here.
going through the same issue...
I am having the same troubles as the person who started this thread. I rooted my samsung galaxy tab 2 10.1 from the instructions that I found on this forum. I also installed ClockWork Mod recovery as per the rooting instructions. Now that I am hearing that I will be unable to update to jelly bean (official) because I rooted my device what can i do to work around this problem?
What if we reboot into Clock Work Mod recovery and use the option to restore device to stock firmware? If we did that option it would restore the tablet back to its factory resetting and then could we upgrade to Jelly Bean using the "software update" option?
Or is downloading a firmware from sammobile the best option?
I am really not sure about what to do next...
Hope to hear some kind of response on what to do next...
You can get JB stock from sammobile and flash it with odin. Or you can get a custom JB rom from xda and flash it with cwm. There's nothing complicated about upgrading, both ways are good. I would pick the second one, this way you stay rooted.

[Q] Question regarding rooting Nexus 5 and subsequent upgrades

Hi all,
Looking for some advice please as a newbie to Android.
I have a Nexus 5 32gb on order that is being delivered any day now.
My assumption is that when I turn it on, it will have Android 4.4 installed as default.
I intend to immediately root my device prior to setting it up with all my personal data etc.
My questions are:
Do I install the 4.4.2 update OTA prior to rooting the device? I imagine this would make the most sense as there may not be further updates for a while - is this right?
If I do install the 4.4.2 update OTA and then root the device - for future updates, do I then have to install a 'Custom Rom'? - for example if/when Android upgrades to 4.5
Are there some good guides showing how to install a stock/vanilla Android upgrade?
If/when I install a 'Custom Rom' of 4.5 , what would happen to my root priviledges? I assume they would disappear? what then?
Is there a good repo/site for stock/vanilla Android OS?
Many thanks in advance,
litfoo
You'll want to first update to 4.4.2, as it will save a bit of time.
What happened with my Nexus is I rooted it while on the 4.4.1 update, and then when 4.4.2 came around, I was able to use OTA which installed it through TWRP. I had to re-root my device and reinstall TWRP after this.
There are guides on how to sideload OTA updates, which is a way to update android.
Most custom roms will come with root, so you may not have to re-root.
Factory nexus 5 images are available here
https://developers.google.com/android/nexus/images
amcgavin said:
You'll want to first update to 4.4.2, as it will save a bit of time.
What happened with my Nexus is I rooted it while on the 4.4.1 update, and then when 4.4.2 came around, I was able to use OTA which installed it through TWRP. I had to re-root my device and reinstall TWRP after this.
There are guides on how to sideload OTA updates, which is a way to update android.
Most custom roms will come with root, so you may not have to re-root.
Factory nexus 5 images are available here
Click to expand...
Click to collapse
Many thanks for this .
So - once rooted, I can flash device with an updated Factory Nexus 5 image? If yes, I assume this will lose root?
If I wanted a custom rom of a factory Nexus5 image, but with root - where's the best place to find these and what are the most popular ones?
Cheers,
litfoo

how can i stay up to date with my rooted note 12.2

I have successfully rooted my note 12.2 - thanks to this awesome forum.
With that I can't do OTA or use Kies to stay up to date. So I'd like to know how I can stay up to date as Samsung releases new firmwares? For example I just downloaded the newly released 5.0.2 from Samobile and flashed it with Odin 3.09. That went well but of course it wiped my machine so I'm starting fresh again. I'd like to be able to stay up to date with out a complete re-wipe each time if possible. Thoughts?
As a long time root user I can tell you that the cardinal rule is that one should give up the notion of getting OTA updates for good once one roots for the simple fact that with each major OTA update comes the risk of losing root forever should the update lock the doors on the exploit used to gain root to begin with.
Casual root users are best served by watching forum threads after updates are released to see how more experienced users are fairing with getting their devices up to date. The exception to this is if a custom ROM is installed and the developer updates the ROM periodically to integrate the updated software or features that the device manufacturer releases. Even then, if a major update is released that let's say jumps to a new system like kitkat to lollipop there's a chance that a full wipe can't be avoided. ROM developers typically warn users when clean installs are required, and some even distribute their own OTAs.
I'm a religious user of titanium backup, and I will often dirty flash a ROM update or use prior titanium backups to restore data but this can be risky business when major updates are released because if software or drivers change from one major firmware release to another a backup of a particular application may no longer be compatible and stability may be affected upon restore.
Bottom line, if you want lollipop on your note pro, rooted, can live with the current bluetooth issues and want to be able to update further easily while retaining root then go with a custom ROM like civs and just monitor the thread of that ROM for updates.
Hope this helps.
Thanks for the excellent advice. One two more more question on the topic. I had root on KitKat, but after flashing the new stock Lollipop via Odin, I lost root. So after installing the stock Lollipop I had to re-do the root flash via Odin to get root back, thankfully it all worked out. (Lollipop is awesome BTW).
Questions:
1. Was I in danger of forever losing root as you state above or was this a safe route? I understand that OTA and even Kies can make me lose root forever, but what about flashing a stock via Odin?
2. Are you saying that next time there's an update I could try to dirty flash the ROM via TWM (after doing a good backup via Titanium of course)? Basically find ROM on samobile, download, copy to SD card and dirty flash away using these suggestions: https://www.reddit.com/r/Android/comments/sthr8/dirty_flashing_what_it_is_and_is_not_lets_set_the/
Typically to keep root the stock recovery is replaced with a custom one, TWRP is the main one used for our device. Stock updates from Samsung downloaded as OTA will typically fail to flash in TWRP. Odin flashing stock images will erase everything including the custom recovery, thus causing loss of root. In other words you'll typically lose root one way or another and the key to retaining it is to not blindly update until a root method is ensured for the next version of firmware. Resign to the fact that with each update you will temporarily lose root and need to redo it. Plan ahead, wait for root confirmation and then update with a plan of how to get root again.
I typically don't TWRP flash stock so I don't know if it works but in the distant past I recall that it wouldn't so thus I never try. Maybe someone can confirm. For me I haven't updated firmware on my note pro for a year now and I am not missing anything. ..
Sent from my SM-N910T using Tapatalk

Categories

Resources