I speak for the people on versions 3.2.7 3.2.8 4.1.x and 4.5.x my question is will there be any way in the foreseeable future of uniting the people below 3.2.7 with those that are higher and only seem to have access to nexus 4.2.2 safestrap edition 1.0.1 pretty much all versions of both tablets (except Saturn) have been rooted but they are unable to do much due to the bootloader incompatibilities. Wish auto update was not a feature.
I am hoping for the longest and most prospererous future for our device. I am very sorry if this is spam or irrelevant.
What can we expect to see coming in the future for new bootloader devices?
No one knows.
it would be nice though
darn i wish i could develop roms but i dont have the time (college)
LittleGreenSony said:
darn i wish i could develop roms but i dont have the time (college)
Click to expand...
Click to collapse
The thing is, it's not just about someone creating a compatible ROM or unlock. Otherwise, we would've already seen some development for the newer firmware versions. The sole reason for why these things are possible in the first place lies in exploits. No one has been able to discover any holes in the system yet that make these devices vulnerable enough for "attacks" like allowing you to replace the stock recovery or kernel.
I'm kinda bored with nexus safestrap.
Is there anything that can be done with fastboot, can we use that to unlock the bootloader similar to how Sony Xperias get unlocked?
No, completely different devices and software and everything else. Only similar thing is the base of Android, and even then, both Amazon and Sony modified the base(Amazon more so)
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
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 ended up with a Verizon S4 through eBay (for a good price at least), and have managed to get on 5.0.1 and root it (via the PC version of Kingroot). Being that it's the OC1 baseband version, my options seem to be quite - no, very limited, when it comes to flashing non-touchwiz based ROMs. Is there any conceivable way I can get a custom recovery on here that will allow me to flash AOSP ROMs? I can wait, it doesn't have to be right now... I just need to know if my particular S4 is permanently crippled in this regard, or if it's just a matter of waiting until someone cracks it. Ideally I'd like to have an unofficial Android M ROM on here when the time comes. What are my options?
Also, I just came from the development sub forum (I can't comment there yet) and saw a new 5.1.1 ROM (Gamer Rom?) that claims to work for the Verizon S4. I'm skeptical that it wouldn't actually brick my device so I wanted to check of anyone else here has found a way to flash it. As far as I know, we can't even flash CWM so I just wanted to double check of I was missing anything obvious. Cheers
All,
Originally posted a request for help in the Galaxy S4 International forum for using Odin to downgrade my Verizon Galaxy S4 SCH-I545 from Lollipop to KitKat.
http://forum.xda-developers.com/galaxy-s4/help/odin-fails-to-downgrade-galaxy-s4-t3278803
Eventually one helpful guy mentioned that Verizon crippled this device with a locked bootloader, (or a mismatched age/version of the bootloader) something never even hinted at in ANY instructions I've ever found for using Odin. I'm really disappointed in the Lollipop version that I've been stuck with, mainly due to the slowdowns on the phone and the need to kill off all apps at least every day., and the need to hit buttons multiple times before enough system resources clear up and it does what I want. All I wanted to do was go to an earlier version, and it looks like that might not be possible.
I see forum posts talking about rooting this version of the phone, but I don't have a handle on what good that will do for me in my particular situation. Now that I've found the correct forum, any suggestions? Part of me likes the idea of rooting and debloating to speed things up, but if I can't downgrade and the performance reduction is just a function of the version of Android I'm stuck with, then I don't see the point in wasting even more days of my life fighting this aging phone.
Oh, and as an aside, what the hell is OC1 and OF1? Can't find anywhere that explains what the heck they're talking about. My best guess is they're versions of firmware, are the designations just random?
Thanks!
Ryan
I'll try to write you some things i've learned about this device, hope it helps you
Samsung Galaxy S4 Verizon SCH-I545 has the same specs than others Qualcomm Galaxy S4, but this one is managed by Verizon to distribute, update software, etc... That means, even when it has the same hardware than others it will have some differences on software and limitations. Now, let's talk about our "charming" bootloader:
When we talk about bootloader, we use as reference the last 3 characters of bootloader version (this also applies to firmware, kernel), you can get your bootloader version by running this command on terminal emulator getprop ro.bootloader (this is why we refer to lollipop OC1, OF1, to kitkat NG5, NG6, NK1 and so on) when you get a software update almost always your bootloader is updated. Only MDK bootloader (first firmware released) was unlocked. After that, Verizon decided to start locking the bootloader to prevent rooting, software downgrade... So, why don't we unlock the bootloader? because they used something called qfuse, the qfuse is hardware related and when it's triggered (updated) cannot be untriggered (downgraded).
After reading this you may be really dissapointed and thinking to get another device, I was in that situation, but you can root your device (this means, you can debloat and do something to speed your s4), even you can install a custom rom's (they're really nice), maybe it's not the best solution, but, hey! it's really better than stay stuck with device stock rom. Btw, you cannot downgrade with custom roms, you can just install those that are meant for your bootloader or higher.
Edgardo_Uchiha said:
After reading this you may be really dissapointed and thinking to get another device...
Click to expand...
Click to collapse
That is what I'm leaning towards. The frustrating part is the time wasted trying this in the first place. I think I'm just going to cut my losses, suffer my crippled phone with quiet grace and dignity, and replace it at some point.
Thanks for all the help!
Ryan
So, is there any way to root a Galaxy S4 verizon phone with 5.0.1 (Lollipop)?? I've been reading threads and how-tos and trying various techniques for several hours with zero success.
Don't despair too much. There is a great dev who has provided the means to flash a very stripped down version of Lollipop OC1. I can honestly say that, in the 2-1/2 years I've owned this device, it has never run better since installing his ROM.
It is still a Touchwiz ROM, but everything, and I do mean everything that can be considered crapware has been removed from this ROM. The result? a slim, sleek user experience that will cause you to never look back (considering we will NEVER have a true AOSP ROM for our device.
Check his link out below. Read everything and make sure you understand what you have now and what you will need to do. Then study some more. It took me a month before finally feeling confident to make the plunge. Even then I needed help, but got all I needed from the good folks...especially Stang5litre, on the discussion board.
Good luck!
http://forum.xda-developers.com/galaxy-s4-verizon/development/stang5litre-ediition-5-0-t3132555
---------- Post added at 03:18 PM ---------- Previous post was at 03:12 PM ----------
gonyere said:
So, is there any way to root a Galaxy S4 verizon phone with 5.0.1 (Lollipop)?? I've been reading threads and how-tos and trying various techniques for several hours with zero success.
Click to expand...
Click to collapse
Presuming you are on OF1, have a look here...
http://forum.xda-developers.com/galaxy-s4-verizon/general/root-of1-t3249971
jwhistler said:
Don't despair too much. There is a great dev who has provided the means to flash a very stripped down version of Lollipop OC1.
Click to expand...
Click to collapse
Just took a peek, that looks well beyond me, and at least a dozen times more complex than the tantalizing downgrade forum posts that pulled me down this road in the first place. Heck, pretty much every other word is some acronym I've never heard of. Thanks though, I'll pass.