So I have my rooted NK1 4.4.2 S4 going happily now.
But it immediately tried to install the OTA update to go to lollipop.
I'm all for updates, but I've seen some scary things about going to OC1 and not being able to go back and such.
I'm okay with not being able to go back, as long as I can keep root.
I've tried the various roms and I prefer stock for some reason, so lollipop is okay with me. However I must have root. So, is there a safe way to update to lollipop from nk1 and keep root? Or obtain root on oc1 and just do a normal ota update with nothing special? Most guides seem to require you start from a rooted Nk4, which I'm unsure how to achieve.
Muniz_ri has the answer to go to OC1 while keeping root. THEN go to OF1. I'm not sure if you can skip OF1 with his method. @muniz_ri can we?
XxD34THxX said:
Muniz_ri has the answer to go to OC1 while keeping root. THEN go to OF1. I'm not sure if you can skip OF1 with his method. @muniz_ri can we?
Click to expand...
Click to collapse
Huh.. Didn't even know there was an OF1..
So what is the advantage to going to lollipop anyway? Other then the new OS. Better battery life, performance? My galaxy tab runs lollipop and its not that exciting..
Well, it just came out yesterday.
Other advantage is getting rid of some security bugs... Otherwise, you listed them all.
Related
So I used saferoot to root back at the 4.3 update; however, overnight one night my phone decided to install the tiny update Verizon pushed that kept 4.3 but took away root. Now I am trying to update to 4.4.2 via OTA update but it continuously fails...Since I've lost root already, I'm looking for a way to manually install the 4.4.2 update (knowing I won't have root access..but I don't know so...) or revert back to an 4.3 so I can root again with safestrap...
Can anyone offer any insight on either of these options? I'd probably prefer to revert to 4.3 and have root over 4.4.2 without....
Phone Details
FYI
Android Version - 4.3
Baseband Version - I605VRUAND3
kbrown.1407 said:
So I used safestrap to root back at the 4.3 update; however, overnight one night my phone decided to install the tiny update Verizon pushed that kept 4.3 but took away root. Now I am trying to update to 4.4.2 via OTA update but it continuously fails...Since I've lost root already, I'm looking for a way to manually install the 4.4.2 update (knowing I won't have root access..but I don't know so...) or revert back to an 4.3 so I can root again with safestrap...
Can anyone offer any insight on either of these options? I'd probably prefer to revert to 4.3 and have root over 4.4.2 without....
Click to expand...
Click to collapse
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Thanks
xnatex21 said:
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Click to expand...
Click to collapse
Thanks, I actually came across that post just a bit ago (apparently gave up on finding an answer a bit early, sorry). One other question though, if and/or when someone posts 4.4.2, is there a way to update manually and maintain root access? Or is root lost once it's updated in any way?
kbrown.1407 said:
Thanks, I actually came across that post just a bit ago (apparently gave up on finding an answer a bit early, sorry). One other question though, if and/or when someone posts 4.4.2, is there a way to update manually and maintain root access? Or is root lost once it's updated in any way?
Click to expand...
Click to collapse
The only way you'd be able to get root is if someone finds a root exploit for this specific device and 4.4.2 (assuming you're on 4.3 with a locked bootloader already).
If you don't have a locked bootloader, then you can flash custom 4.4.x roms with root.
But if you are on a custom rom with an unlocked bootloader and you ODIN to the stock Verizon 4.4.2 that rolled out yesterday, you'd get a locked (possibly permanently) bootloader and a potentially un-rootable 4.4.2 rom.
xnatex21 said:
The only way you'd be able to get root is if someone finds a root exploit for this specific device and 4.4.2 (assuming you're on 4.3 with a locked bootloader already).
If you don't have a locked bootloader, then you can flash custom 4.4.x roms with root.
But if you are on a custom rom with an unlocked bootloader and you ODIN to the stock Verizon 4.4.2 that rolled out yesterday, you'd get a locked (possibly permanently) bootloader and a potentially un-rootable 4.4.2 rom.
Click to expand...
Click to collapse
I am on 4.3 with the locked bootloader. Thanks again for the help.
xnatex21 said:
If you're on 4.3 w/o root, you can follow this thread and regain root. - http://forum.xda-developers.com/showthread.php?t=2752360
I haven't see anyone post 4.4.2 yet to manually flash if the download fails. I'm the same boat there. Give it a few days and I'm sure someone will post it.
Click to expand...
Click to collapse
My update failed too, so I am interested as well if someone has the 4.4.2 official
mgarcia86 said:
My update failed too, so I am interested as well if someone has the 4.4.2 official
Click to expand...
Click to collapse
Mine did the first couple times. What I did was odin to stock 4.3 again and take the small update on 4.3 and then the 4.4.2 worked after that.
So I've been debating whether or not to upgrade to nc5 from mk2.
I know that towelroot would root nc5. I'm mainly concerned if there were any security patches or fixes in nc5 that would affect the ability to run kexec( if it gets running) on nc5.
I'm fairly confident that surge is working on building kexec on nc5 instead of mk2, but I'm just paranoid of pulling another mdk to me7 again
(This is really geared towards the " if we are serious about unlocking the bootloader thread" I just didn't want to ask questions there.)
Raymondlikesroot said:
So I've been debating whether or not to upgrade to nc5 from mk2.
I know that towelroot would root nc5. I'm mainly concerned if there were any security patches or fixes in nc5 that would affect the ability to run kexec( if it gets running) on nc5.
I'm fairly confident that surge is working on building kexec on nc5 instead of mk2, but I'm just paranoid of pulling another mdk to me7 again
(This is really geared towards the " if we are serious about unlocking the bootloader thread" I just didn't want to ask questions there.)
Click to expand...
Click to collapse
Just give it time and stay on mk2 for now. Once kexec comes out then just go to that bootloader.
I just finally upgraded to NC5 from MK2, tonight.
I kept the MK2 boot loader. I haven't yet fixed tether, but everything else is good.
Looking forward to 5.0. I just want to maintain flexibility as long as possible, with the MK2 platform.
Sorry, I know nothing about kexec.
Sent from my SM-T520 using Tapatalk
I have read and appears that I have to downgrade but I am not sure. Please advise
Thanks
docmarioce said:
I have read and appears that I have to downgrade but I am not sure. Please advise
Thanks
Click to expand...
Click to collapse
What you read is correct. You have to downgrade to 10b to root. After that, if you want to go back to 12b rooted, do NOT bump with TWRP. Instead, tell SuperSU to maintain root across OTAs and then take each OTA as it comes. When you are finally on 12b, you can either leave it as is (not bumped) or install TWRP to bump it. Reason you cannot bump is because you need the stock recovery (not TWRP) to install the OTAs.
How do we go about doing that process? Can someone point me in that direction plz
mrlee19 said:
How do we go about doing that process? Can someone point me in that direction plz
Click to expand...
Click to collapse
general forum, return to stock thread.
Ok just asking because ive saw a few post.. And ppl were saying that method wasnt working but ill check again.. Thanks
mrlee19 said:
Ok just asking because ive saw a few post.. And ppl were saying that method wasnt working but ill check again.. Thanks
Click to expand...
Click to collapse
if the "tot" method doesnt work, the "kdz" should. but afterwards, you still need to use the tot method to get back on the update path.
iBolski said:
What you read is correct. You have to downgrade to 10b to root. After that, if you want to go back to 12b rooted, do NOT bump with TWRP. Instead, tell SuperSU to maintain root across OTAs and then take each OTA as it comes. When you are finally on 12b, you can either leave it as is (not bumped) or install TWRP to bump it. Reason you cannot bump is because you need the stock recovery (not TWRP) to install the OTAs.
Click to expand...
Click to collapse
Thanks I have downgraded and rooted my phone. I want to be able to install kit Kat ROMs. I don't care about taking OTA to 12B if I can install ROMs based in 12B anyway. Should I bump with TWRP? Are there any bumped ROMs that are worth it? I am not planning in installing android L in my device in the future anyways since my Samsung Gear 2 watch won't work with it. I just want to start flashing this phone away.
Thanks
docmarioce said:
Thanks I have downgraded and rooted my phone. I want to be able to install kit Kat ROMs. I don't care about taking OTA to 12B if I can install ROMs based in 12B anyway. Should I bump with TWRP? Are there any bumped ROMs that are worth it? I am not planning in installing android L in my device in the future anyways since my Samsung Gear 2 watch won't work with it. I just want to start flashing this phone away.
Thanks
Click to expand...
Click to collapse
Before you can even begin to flash ROMs, you have to install TWRP.
As for which ROMs are worth it, I have no idea. Most are LP ROMs and currently LP is not completely stable and there still are issues to be worked out.
I myself am happy running full stock 12B rooted. I am bumped in case I want to flash a ROM, but at this time, I don't have any desire to flash a ROM at the current moment.
Best thing is to go and read about the ROMs in the developer section. Note what issues people are having and which ROM is best for you is up to you. Everyone has their preferences. Asking "which ROM is the best" is not a question that can be answered since it's all down to personal preferences and what issues you can live with.
If you have twrp installed. First thing you have to do is backup your stock rom
You don't "bump with twrp".
Normally code in the bootloader prevents the loading of unsigned stuff like kernels and custom recoveries. That includes TWRP, but Team Codefire figured out a way to fake the signature onto things like twrp and aosp ROMs, by changing slightly their images. This allows them to load.
iBolski said:
Before you can even begin to flash ROMs, you have to install TWRP.
As for which ROMs are worth it, I have no idea. Most are LP ROMs and currently LP is not completely stable and there still are issues to be worked out.
I myself am happy running full stock 12B rooted. I am bumped in case I want to flash a ROM, but at this time, I don't have any desire to flash a ROM at the current moment.
Best thing is to go and read about the ROMs in the developer section. Note what issues people are having and which ROM is best for you is up to you. Everyone has their preferences. Asking "which ROM is the best" is not a question that can be answered since it's all down to personal preferences and what issues you can live with.
Click to expand...
Click to collapse
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Jimi Mack said:
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Click to expand...
Click to collapse
So far from all I have read, users have been able to progress from 10B to 11C and on to 12B all while maintaining root. You can only gain root, however, while on 10B. Once you have root you can install TWRP whenever. However, you cannot take an OTA while you have TWRP installed....I mean you can, but you'll get stuck in a boot loop By far the easiest and best thing to do if you're looking for stability and compatibility of stock would be to install an awesome, stock-based rom like Jasmine rom - that way you get all the benefits of the latest VZW updates, while keeping all the stability of full stock, and not "risking" anything by accidentally accepting some OTA down the road. Just my 2 cents!
Jimi Mack said:
A quick question: If you had to flash back to 10b to be Rooted and Bumped how did you wind up on a fully stock 12b rooted and bumped if you did not flash a rom. You should not have been able to upgrade if you downgraded your phone to 10b to root and bump which if I recall takes away the ability to upgrade to 12b while rooted and bumped without flashing a rom. Or do you have another method? Thanks.
Click to expand...
Click to collapse
I didn't bump until after I otad to 12b. First, I stumped rooted on 10b. Then I told SuperSU to maintain root across otas. Once I updated to 12b, that's when I bumped in case I wanted to flash a rom or do a nandroid backup.
Of course, if a new ota comes out, I'll have to downgrade back to 10b and root again before I can take it.
Sent from my Nexus 7 using Tapatalk
iBolski said:
I didn't bump until after I otad to 12b. First, I stumped rooted on 10b. Then intokd SuperSU to maintain root across otas. Once I updated to 12b, that's when I bumped in case I wanted to flash a rom or do a nandroid backup.
Of course, if a new ota comes out, I'll have to downgrade back to 10b and root again before I can take it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
That is what I had thought but was not sure if I missed a method other than that, thank you.
So if I downgraded my NC5 i545 to MK2 could I then install CyanogenMod?
Thanks!
Matthew2D said:
So if I downgraded my NC5 i545 to MK2 could I then install CyanogenMod?
Thanks!
Click to expand...
Click to collapse
In a word - NO. Even going back to the MDK bootloader is not possible once you have taken the OTAs. And even then, MDK is still locked. The likelihood of the bootloader getting unlocked is slim and none. Kexec is the next choice and even its development has slowed as it is very hard to crack the bootloader issue.
As is often repeated, read the FAQs and search topics before posting.
To install anything other than a TW based rom, you need to be on the MDK bootloader. Once you have a newer bootloader than MDK, you are stuck with TW based roms and Safe Strap.
I have a Verizon Samsung Galaxy S4 on build lrx22c.i545vrugoc1 and would like to flash a Play Edition ROM.
Everything I have read so far suggests that it can not be done because Verizon locked the bootloader somehow with the latest update.
Can anyone point me in the right direction?
Thanks
You're correct, though the BL has always been locked. I don't believe there is any way to root the LL build as of now.
rrrrrrredbelly said:
You're correct, though the BL has always been locked. I don't believe there is any way to root the LL build as of now.
Click to expand...
Click to collapse
Actually, if you go into the different sections, root has been gained for updates after the initial MDK bootloader. MDK is still the only version of the bootloader that is capable of running custom roms without having to use safestrap.
Having root and the capability or ability of running custom roms are two horses of a different color.
I didn't say you couldn't root different builds, i said the bootloader has never been unlocked.
If you are on oc1 boot loader there is no way to root and you can't downgrade from oc1 so you can't gain root
legonate said:
If you are on oc1 boot loader there is no way to root and you can't downgrade from oc1 so you can't gain root
Click to expand...
Click to collapse
I have OC1 update and a rooted i545
OC1 CAN be rooted with KingRoot. Many people reported that the chinese app works.
As far as ROMs for OC1, there is nothing like AOSP. Only Touchwiz ones. Only Play edition SIMILAR ROMs are eclipse and Kitpop, which you cannot do because you are on OC1. You can Root, and get a stockdeodex ROM, that is about it.
The bootloader has been locked for ages. Only unlocked bootloader is for MDK, which was about 2-3 years back. No hack for the bootloader has been found as of yet.