On my note 2 I accepted the OTA update and some how I rooted it with the OTA Root keeper. Evertything works fine but I cannot install custom recovery. What woould be the best way to unlock the bootloader and install custom recovery now.
I also have galaxy s3 and droid bionic both are rooted and custom roms installed and working great.
I have been with Verizon 16 years and it's abuot time to change but I think there all the same anymore $$$
If you took the ota then you can not unlock your bootloader as of this time.
why on earth are folks so hell bent on ota's???? fyi when you buy a device that came locked but was unlocked by devs at xda, YOU NEVER EXCEPT ANY OTA! It has been posted all over this forum...please research before you do anything!!
Totally agree! I won't even update an app until I know what the changes are, and even then I usually wait to see if any issues arise with the update.
Doesn't matter how many times you warn people no to install an OTA because it has a bootloader, someone won't listen.
I would never consider taking a ota until after our devs have a chance to check it out. Besides if you run a custom rom your developer will most likely be updating to the new build and you know you can safely flash it.
Besides I know verizon is more worried about blocking crap than they are on their real updates.
Forget the security update and give us official 4.1.2 screw verizon! Verizon ota usually means bad things.
Travisdroidx2 said:
I would never consider taking a ota until after our devs have a chance to check it out. Besides if you run a custom rom your developer will most likely be updating to the new build and you know you can safely flash it.
Besides I know verizon is more worried about blocking crap than they are on their real updates.
Forget the security update and give us official 4.1.2 screw verizon! Verizon ota usually means bad things.
Click to expand...
Click to collapse
4.1.2 has very little to offer us.
adrynalyne said:
4.1.2 has very little to offer us.
Click to expand...
Click to collapse
I agree with that. However my point was instead of Verizon spending their time improving their devices they would rather spend their money and time trying to figure out how to screw us. I know 4.1.2 brings little to the table but maybe if they were not working on locking the bootloader they could improve on the builds instead. I would still rather have 4.1.1 over 4.2.1 any day.
So my girlfriend has wants her S4 rooted. I have the S3 and its quite different as far as rooting goes. I am also on sprint whereas she is on verizon (although thats not such a big deal).
Anyways, what I would like to have clarified for me is this: She is currently unrooted with stock MK2. From what I have read you can only root and install compatible roms with safestrap. The main thing she wants is KitKat and possibly CM. Is there any way for her to get either of these. Also, would it be possible to revert back to stock and flash KitKat with the OTA from verizon when it is released?
Thanks for any help.
BioBot said:
So my girlfriend has wants her S4 rooted. I have the S3 and its quite different as far as rooting goes. I am also on sprint whereas she is on verizon (although thats not such a big deal).
Anyways, what I would like to have clarified for me is this: She is currently unrooted with stock MK2. From what I have read you can only root and install compatible roms with safestrap. The main thing she wants is KitKat and possibly CM. Is there any way for her to get either of these. Also, would it be possible to revert back to stock and flash KitKat with the OTA from verizon when it is released?
Thanks for any help.
Click to expand...
Click to collapse
There's no way for her to get KitKat or CM or anything AOSP. Hopefully the next OTA will have an exploit, but there hasn't been a cracked bootloader since the first version of firmware on the initial releases. Realistically, never going to happen.
My G3 is rooted with stump root and this is the first time I've rooted my phone. When Lg rolls out the update would I have to unroot my device before updating or will I be fine updating it even though the phone is rooted?
Galaxynote1234 said:
My G3 is rooted with stump root and this is the first time I've rooted my phone. When Lg rolls out the update would I have to unroot my device before updating or will I be fine updating it even though the phone is rooted?
Click to expand...
Click to collapse
The theme of don't take OTA's has been beat to death. In short, update to L via official OTA roll out, and you can likely kiss root and unlocked boot loaders good bye. You need to make a personal decision here. Either you want Lollipop ASAP, or you want a rooted and unlocked device. If you want the former, you can take the official update. Then you better hope the stock setup is alright with you, because you may never see root, at least for a long time, on Android L. It may take a while for a developer or development team to get a ROM on L, but when that happens, you can have L, with root, and an unlocked bootloader. Get it now or get it later. Your call. If you get it now and don't like the consequences, it was your call. The devs are a lot smarter than me, and I figure they can take out of the official L build what they need for a ROM and leave the stump and bump in place, so I'm staying on Jasmine 3.0 or Beanstown's ROM until they (or some developer) do an L based ROM. L may or may not be an impossible nut to crack, but I don't see where there is enough out there to really say for sure. I'm just saying to err on the side of caution.
One dev in particular, @Chainfire, has done some root things with the L preview. But it is the preview. Read what he has to say about L is for lockdown here.
http://www.xda-developers.com/android/android-l-lockdown/
I wasn't planning on losing my root I just wanted to know if I was able to update and still keep root access but thank you for the post. I now know that if I want to keep root access I won't be able to update OTA.
WHY¿ The vs985has great Specs!
It has a locked boot loader and the only workaround method so far, Bump - developed by Team Codefire, was leaked by a selfish idiot, compromising the method so it will probably be patched in a future (Lollipop ?) OTA, leaving us owners with no root and no custom recovery.
Sent from my VS985 4G using Tapatalk
The method was compromised the minute codefire announced. Their method getting reverse engineered has nothing to do with whether out not lg makes an update which breaks it's functionality. If that comes to pass, it's simple...don't update. Meantime, development is just beginning as lollipop rolls out. Don't believe everything you hear.
theistus said:
The method was compromised the minute codefire announced. Their method getting reverse engineered has nothing to do with whether out not lg makes an update which breaks it's functionality. If that comes to pass, it's simple...don't update. Meantime, development is just beginning as lollipop rolls out. Don't believe everything you hear.
Click to expand...
Click to collapse
Yea, I won't update. I'm on a 5.0.1 and it's great. I have wife's on KZD 10b and TB system updates frozen because it took 11c before I knew it.
foundingfathersfan2 said:
WHY¿ The vs985has great Specs!
Click to expand...
Click to collapse
First off, where did you here this from? I haven't heard it.
Also, there have been several OTAs since "bump" was released and it hasn't been patched so far. Bump was released back in October and we just got a new update for the VZW model (VS985) in December (v 12B) and you can downgrade from that and install TWRP on it. Plus, there are already "rooted/bumped" images for you to flash if you don't want to take the official OTAs (of course, you have to tell SuperSU to preserve root over the OTAs and you must NOT be bumped in order to take the OTAs). I'm on the official 12B OTA and then flashed TWRP, so I'm bumped. So, at this time, the phone is still bump-able even at the latest version.
Also, reports from overseas where some are getting LP have been able to downgrade back to a Kit Kat. That might change here in the United States, but definitely, I would hold off on taking any more OTAs until it can be verified if it fixes the "bump" exploit or not.
But, so far, ROMs are being developed, etc. So, I have as of yet to hear about devs not wanting to develop for this phone anymore.
Again, if you could point us to some sources, that would be good because I would like to know as well, but I don't go by hearsay.
iBolski said:
First off, where did you here this from? I haven't heard it.
Also, there have been several OTAs since "bump" was released and it hasn't been patched so far. Bump was released back in October and we just got a new update for the VZW model (VS985) in December (v 12B) and you can downgrade from that and install TWRP on it. Plus, there are already "rooted/bumped" images for you to flash if you don't want to take the official OTAs (of course, you have to tell SuperSU to preserve root over the OTAs and you must NOT be bumped in order to take the OTAs). I'm on the official 12B OTA and then flashed TWRP, so I'm bumped. So, at this time, the phone is still bump-able even at the latest version.
Also, reports from overseas where some are getting LP have been able to downgrade back to a Kit Kat. That might change here in the United States, but definitely, I would hold off on taking any more OTAs until it can be verified if it fixes the "bump" exploit or not.
But, so far, ROMs are being developed, etc. So, I have as of yet to hear about devs not wanting to develop for this phone anymore.
Again, if you could point us to some sources, that would be good because I would like to know as well, but I don't go by hearsay.
Click to expand...
Click to collapse
Its just something I've seen on some ROM Threads. It may just be hearsay. I hope that's all it is.
foundingfathersfan2 said:
Its just something I've seen on some ROM Threads. It may just be hearsay. I hope that's all it is.
Click to expand...
Click to collapse
Okay, thanks. I haven't seen it in ROM threads and ROM threads normally don't have the devs posting there, so it's probably from people who don't really know what they're talking about, or it could be someone who represents the devs and posts updates for them. Either way, I'll keep an eye out on that and see if I can determine who it's coming from. Just curious because I definitely would like to know.
I look at this differently. Team Codefire figured out the only way known, so far, to flash a custom recovery and/or kernel and have it boot past the security check. Without that method (Bump), nothing is possible other than stuff based on stock firmware, like Jasmine.
Though the bump method was arguably already compromised by its use through the bump website, and that had its own drawbacks for sure (no nightly builds from CM, for example), there was an "understanding" between Team Codefire and LG, at least hinted at by Autoprime. The full public release of the bump method upset Team Codefire enough for them to abandon further work on the LG G3 altogether, and no one else has picked up on it or come up with any alternatives. You cannot even root any version other than the original stock v10b to this day.
So, though Roms are currently installable since you can still roll-back to v10b, root, and flash a bumped TWRP, folks getting new G3s in the future will likely be stuck with a totally locked down firmware, like we original purchasers thought we might be stuck until bump. For months...
How much Dev interest will remain if that happens ?
Will many Dev teams want to even just build for the G3 if only a subset of owners can install their works ?
trent999 said:
I look at this differently. Team Codefire figured out the only way known, so far, to flash a custom recovery and/or kernel and have it boot past the security check. Without that method (Bump), nothing is possible other than stuff based on stock firmware, like Jasmine.
Though the bump method was arguably already compromised by its use through the bump website, and that had its own drawbacks for sure (no nightly builds from CM, for example), there was an "understanding" between Team Codefire and LG, at least hinted at by Autoprime. The full public release of the bump method upset Team Codefire enough for them to abandon further work on the LG G3 altogether, and no one else has picked up on it or come up with any alternatives. You cannot even root any version other than the original stock v10b to this day.
So, though Roms are currently installable since you can still roll-back to v10b, root, and flash a bumped TWRP, folks getting new G3s in the future will likely be stuck with a totally locked down firmware, like we original purchasers thought we might be stuck until bump. For months...
How much Dev interest will remain if that happens ?
Will many Dev teams want to even just build for the G3 if only a subset of owners can install their works ?
Click to expand...
Click to collapse
Crap. Your right, we are almost a subset.
Look..there will always be a work around.. as long as there is someone out there with a need, there will be someone able to provide it.. The truth stands for all makes and models of smartphone.. The ROM build craze goes on and on, and eventually the phone is outdated and dev passes over it to a new model to play with.. BEST advice for anyone is learn to write if youre not a progressive upgrader
The whole scene is a revolving door, and like most things good, eventually theres an end...
I'm just your average Android enthusiast, not nearly as talented and skilled as you devs, but I know my way around my phone. I am currently rocking the Galaxy S4 SCH-I545 NC5 (Rooted with Towelroot and Safestrap 3.72 installed). I never thought highly of Samsung's user interface and have wanted to upgrade to CM forever, but as each new update comes I really, really want it, so I carelessly take the OTA. I've done this far too many times so I decided to disable the system update app so I wouldn't be bothered by the new updates that come around.
Anyway, I think it's time to upgrade to Lollipop now that it's available, but I really want to keep root access, and since you guys are the professionals, I want to know the best way to flash the new update instead of take the OTA, which, if I'm not mistaken, will let me keep root and the small possibility that I can get Cyanogen some day. Is it best for me to just go ahead and take the risk-free OTA update, or should I flash? If so, can someone guide me through the process? I'm sorry if this sounds like child's play to you but I don't want to brick my phone in any situation, so it'd be great if someone could help me with this. Thanks in advance!
Screenshots for more information:
http://imgur.com/CIBx5qY,KHATxkV,fKyJcoB#2
Update: I followed a tutorial to update to OC1, but was not successful (Wouldn't boot). I used Odin to reflash the NC5 and now I'm back where I started. Anyone have an idea?
Here's the link to the tutorial:
http://zidroid.com/how-to-update-keep-root-verizon-galaxy-s4-on-lollipop-oc1/#comment-6589
Edit: Tried this twice, both didn't work. I'm considering just taking the OTA and not getting root. What should I do?