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.
Related
I have never seen a clear answer on this question. What exactly will prevent us from running an official update on our phones. When LG releases the official gingerbread update, what will prevent us from doing that?
1) Rooting.
2) OCing/tweaking/hardware acceleration.
3) Installing custom roms.
If we have only rooted can we update, or would we somehow need to flash our phones back to stock settings? I suppose the development community will take the official LG gingerbread rom, tweak it a bit, and release it for us to use with our rooted and OC'd phones, so maybe it's not a big deal?
Any advice?
I think this is a good thread to sticky so people know this info, since i've never seen it posted anywhere else, for any other phones.
Nothing will prevent you to update. It's your choice.
Don't see the point to stick this.
Cheers
Zecanilis said:
Nothing will prevent you to update. It's your choice.
Don't see the point to stick this.
Cheers
Click to expand...
Click to collapse
So if I have my LG Optimus T rooted, and have a rom installed like cyanogenmod, I can then just download and installed the official 2.3 upgrade from LG/Tmobile?
Yes.
Cheers
Ok then cheers!
how on earth were you able to put CyanogenMod on your phone?
I just thinking about same!
I've never tried to install a stock rom, and with the HTC magic I had read people talking about not being able to install the stock rogers rom without a lot of trouble.
I also heard some issues with certain phones having OTA updates and conflicting with rooted phones.
I just wanted to make sure this was ok. I have cyanogenmod on my HTC magic, sorry for the confusion, so I just used that name for a generic rom. I just meant in general if you can update a hacked/rooted phone without it locking up.
Jailbroken ipod touches and phones cannot be updated using the stock updates that are released over itunes, you have to do a factory reset before going and installing the official updates.
thesmoth said:
I've never tried to install a stock rom, and with the HTC magic I had read people talking about not being able to install the stock rogers rom without a lot of trouble.
I also heard some issues with certain phones having OTA updates and conflicting with rooted phones.
I just wanted to make sure this was ok. I have cyanogenmod on my HTC magic, sorry for the confusion, so I just used that name for a generic rom. I just meant in general if you can update a hacked/rooted phone without it locking up.
Jailbroken ipod touches and phones cannot be updated using the stock updates that are released over itunes, you have to do a factory reset before going and installing the official updates.
Click to expand...
Click to collapse
In this case - Custom ROMs - HTC now sucks. HTC still trying disable for their users installation of custom ROMs even if many people just love this possibilities.
LG (for now) doesn't do that.
The_ERROR said:
In this case - Custom ROMs - HTC now sucks. HTC still trying disable for their users installation of custom ROMs even if many people just love this possibilities.
LG (for now) doesn't do that.
Click to expand...
Click to collapse
Idk where you got this from... especially when hTC is one of the few companies still posting info on how to fix your phone after you root it, also if you are friends with them on facebook they make posts about leaked roms and they say they dont recommend installing but they still show you where its at. Motorola did try to make it impossible to root the droid 2/x/pro but ppl found a way around that, i believe it was koush.
I don't believe any manufacturer spends a great deal of time trying to prevent root, now carriers like sprint and verizon, yes. They don't want you doing wireless tether and things like that.
I have this from root.cz but it is in czech language.
They talking about problems of rooting and updating of system on new HTCs phones, like for example Tatoo. They have HW lock on their NAND ROM, so getting of root is not as simple as was before and so on.
I've been searching and searching and can't find anything where this question is really touched on, at least not from Google.
Basically the thing I'm looking at is this. I come from a Droid X which had and still has a locked bootloader. I was always under the impression that this means two things:
1) MUST use signed updates
2) Cannot use custom kernels
And based on those two things my understanding was that you can theme and modify some small framework and /system stuff, but could never truly update the phone like you could with an unlocked bootloader.
This is where I'm confused. So we have unlocked bootloaders on our Thunderbolts which allows us to flash unsigned zips. Cool. But how does this affect future versions of Android? Like our current Gingerbread roms, aren't they based off of a leaked RUU? What would happen if let's say, Gingerbread is the final OS Upgrade we get from Verizon. How will the next major update to Android be loaded to us?
Do the developers have the ability to port new versions of Android without these leaked OTA's? Or do we rely on the OTA's that include new Android OS versions to progress? Thanks
When Verizon sends out updates our Devs can take them and edit them to work with rooted users. Thats why you will see things come from (I think his name is football) who gives us the updates from Verizon and then our Devs modify them to keep our root privileges. If you are rooted on a custom ROM tho you wont receive OTA.
Thank you for the response. I understand that part, but really what I'm trying to find out is:
Thunderbolt is on Froyo -> Verizon WILL update us to Gingerbread via OTA
Had Verizon NOT updated us to Gingerbread, would devs be able to take us there thanks to an unlocked bootloader? Or would the phone forever be doomed to use Froyo?
Take that principle and apply it to whatever comes after Gingerbread, because I'm pretty sure 2.3 will be the last major OS update this phone gets officially.
i cant give you a sure answer but BAMF has made sense 3.0 work on our phones and that is never releasing as an OTA i would assume if the next version of android comes to any 1ghz phones or well any htc phones someone will find a way just allot more work and more time.
Well thats basically all I needed to know. As long as we have an unlocked bootloader and a dev community willing to work on it, people can basically port any new versions of the OS even from other phone updates.
I just fear the idea of EOL and no more future OS updates.
Good way to answer your question is to take a look at the d1 and even the eris. They are both eol yet i know for sure the d1 has gingerbread, and i believe the eris does also.
sent from my bolt
I have been seeing alot on the forums lately about MDK ME7 MJ7 etc. I am not new new rooting, and flashing roms and things of the like, and i always make sure to check the forums before any ota update. I have not updated yet. I have actually been running PAC since day 1 on my gs4.
I would like to know the benefits and downfalls of upgrading. All i see is people complaining about the locked knox bootloader and trying to downgrade there phone, but why would anybody want to upgrade to begin with? My phone is on MDK and i am still running 4.3 so i dont see any benefit to upgrading my firmware. Would i get better signal?
I know this has already been talked about on the forums plenty, but i have yet to see a comparison or explaination of why you should or shouldn't upgrade.
To be honest I'm not sure why anyone on MDK would want to update unless they just don't care about flashing roms and don't have any desire to do anything other than root in the future.
Something you may not be aware of is that you can flash the radio from MJ7 and get the added signal bonuses without actually having to take the official update. The file is already floating around the forums somewhere, just search around.
The whole Knox counter thing was added to the bootloader since MI1 from what I know, and basically once you trip it your warranty is void and it's very hard if not impossible to reset the counter. There are really no details on how it's tripped exactly, but a good guess would be when a custom recovery is flashed. If the bootloader ever becomes unlocked for versions MI1 onward then we'll probably get a lot more information on this.
Basically if I had MDK I would never take an official update unless for some reason development flat out stopped/sucked or I had to have an unmodified device for job reasons. Besides that, I'm sure within a few months there will be roms available based on the new MJ7 anyway, so locking yourself in would be pretty foolish.
In the end it's YOUR phone and you can do whatever the hell you want with it. Choose wisely.
Oh, and the Nexus 5 came out today. So there's that, too.
I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
I would suggest to read some of the threads....custom Roms for 4.3 and 4.4 are a bit slow in coming. If you are mdk...no need for safestrap....you can still keep your phone rooted and loki'd..and move to 4.3 base
powered by hashcode safestrap hyperdrive 10.2
trevoryour said:
I got my GS4 back in the summer and I promptly rooted and I believe I even was able to unlock the bootloader. I then flashed Eclipse S4 TW edition (based on MDK) and its been so rock solid I haven't had a reason to touch is since. I'm been staring at my android 4.2.2 version and have been thinking no reason to upgrade. If it isn't broke don't fix it right? Well I'm starting to feel the flashing itch so I decided to jump back on XDA and see whats out there.
I'm trying to get a grasp on what all has changes since the last time I flashed my phone. It looks like there has been a few new builds to drop since I flashed. I'm confused on the details though. With my current state can I flash anything I want using the custom recovery or are there restrictions that I must follow. I have seen posts about using SafeStrap for flashing. I remember SafeStrap from my Razr days as a solution for phones with locked bootloaders. Does one of the OTA's relock the bootloader and make it impossible to unlock or are the SafeStrap posts for people that got the phones after me which already came with a locked bootloader?
Any reason why not to upgrade to the newest builds? I can't find any details on what is different between the builds but I have to imagine there is some new stuff that I might want to play with.
Lastly, can anyone suggest a good solid ROM to similar to Eclipse TW that is based on a newer build?
I appreciate any help you guys can give me. Being away this long and coming back is slightly overwhelming and who has time to navigate through every page of every thread for the past 6 months or so.
Click to expand...
Click to collapse
Ok, So heres what you missed. After the MDK release they(Verizon/Samsung) patched the loki bootloader hack so thats why anybody whos not on the MDK release has an locked bootloader. That is where safestrap comes in. Safestrap is a custom recovery that was developed by Hascode, in order to provide those with a locked bootloader a way to get in on the rom action, while keeping there stock rom untouched.
Now that said i would advise you to update but not through the stock "Check Update" tab (as that will lock your phones bootloader). Instead you should just flash a rom that is built with the new update as the base (E.X. Hyperdrive 11). This will allow you to get the new update without locking your bootloader.
Now for roms, i believe there is an updated Eclipse TW Rom & Eclipse AOSP ROM on the Dev's site ( dont know the link but will post it once i find it).
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...