So, I've searched and not been able to find an answer to a question. Why was the original Evo's bootloader locked in the Gingerbread OTA? It seemed like HTC was beginning the process of keeping the bootloaders unlocked, then WAM. We get an update that broke more than it seemed to fix and killed my battery life. I was not rooted, but my phone's overall performance was so poor after the OTA, I was ready to root it. Then, I find out there is no way to do so.
It is annoying that they do an update that hurts my phone's performance, and at the same time, block any chance I have of improving the performance.
So, have we got an answer as to why it was locked?
Thanks!
Because Sprint has the final say so on it, and they wanted it locked....
HTC stated they would be locking the bootloaders on their phones. There was a small public outcry, and HTC said they would have an unlock solution for their future phones. At this point the GB update for the Evo was finalized, and was too far in the game to make a change. Maybe the Evo will be on the "list" for HTC to unlock the bootloader. But it really only has about 5 months left on its support cycle (18 months for updates), so who knows.
Thanks!
So, it was a Sprint thing and not HTC that locked it. That makes more sense. Thank you.
I emailed HTC referencing their decision to not lock future devices and requesting help unlocking my bootloader. Here is the response I received:
I understand you would like the bootloader unlocked on your EVO. While the statement notes that locked bootloaders will not be occurring on future devices, the official policy is still being reviewed as it pertains to existing devices. Please keep an eye on htc .com and twitter .com/htc for the latest news.
Click to expand...
Click to collapse
I guess that enough for a little hope. We'll see what happens...
I just want to point out for those new to the Evo, that the Evo's bootloader has always been locked since Eclair on launch day. This is not new with this update, after each ota update a new root exploit has had to been found to get past the locked bootloader.
wfrandy, thank you for that clarification.
The 4G's bootloader is not locked like the 3D's. The 4G's bootloader still isn't unlocked but it is a lot easier to circumvent. This article explains it better than I can.
http://www.androidpolice.com/2011/0...r-recovery-and-kernel-images-all-locked-down/
HipKat said:
Because Sprint has the final say so on it, and they wanted it locked....
Click to expand...
Click to collapse
This is not true. HTC controls the bootloader on their devices. Sprint just gets the img file from them and they add it to their own updates, They don't get the source or the ability to change it in any way, aside from switching to a different version.
Besides that, look at the release date in the bootloader menu... it says March 8, It was developed and released BEFORE that announcement. And THAT is the real reason why it's still locked. The only reason the update came out in June was because Sprint took forever to lock down everything that they COULD and put in all their crappy bloatware and whatnot. In the future when HTC develops and releases the next version of the hboot, I would guess that it would be unlocked from that point forward.
But again, nothing Sprint can do about it, other than choose not to release it.
Related
Well, I'm sold. Those are the two magic words I needed to hear. Can't wait for that bad boy.
http://androidheadlines.com/2012/05/featured-verizon-wireless-turns-down-htcs-one-series-in-favor-of-droid-incredible-4g-lte.html
Even though the incredible 4G seems to have a few things that it lacks compared to the One X, it does have an unlocked bootloader which the One X does not. It seems that there was quite following of fans that wouldn’t have it any other way. This small group of android nerds is extremely passionate about the capability to tweak and change their devices. For those of you that are unfamiliar with what an unlocked bootloader does, it allows you somewhat endless possibilities to customize the firmware (or OS) on your device. Which can enhance its user experience, looks, features and the like. This move by HTC to keep the bootloader unlocked is because HTC says they fully support the ability to keep things open and customizable.
HTC is fully committed to the bootloader unlocking program and that Verizon is also completely behind it. Ultimately leading to its choice to make the incredible 4G LTE with this feature. While Verizon is behind the idea now. They could of course change their mind at any time.
Click to expand...
Click to collapse
I'm very surprised by this news and very happy at the same time. This might bring some additional devs to the phone. Thanks for the news. You may want to post this in the Incredible 4G sub forum if its not already there.
That's great news and really cool to see that Htc is still going to be allowing the unlocked bootloader.
I'm sure this will be a big plus for me when it comes time to try out a new phone in the future
PacerguyDon said:
That's great news and really cool to see that Htc is still going to be allowing the unlocked bootloader.
I'm sure this will be a big plus for me when it comes time to try out a new phone in the future
Click to expand...
Click to collapse
But still, the fact remains that it will be unlocked by HTC's online unlock tool. Which does not grant S-OFF. Granted that this is better than nothing, but I really want to know how much can be done without S-OFF. I mean, S-OFF was a huge thing for rezound, which recently got it. And I heard, until S-OFF was achieved, AOSP ROMs were impossible on Rezound. So, how much can be done by simply unlocking it by HTC's tool and not getting S-OFF? What is the difference between unlocked bootloader with S-ON (i.e. HTC's unlock method) and unlocked Bootloader via S-OFF like I did for the Dinc2? That is my basic question.
litetaker said:
But still, the fact remains that it will be unlocked by HTC's online unlock tool. Which does not grant S-OFF. Granted that this is better than nothing, but I really want to know how much can be done without S-OFF. I mean, S-OFF was a huge thing for rezound, which recently got it. And I heard, until S-OFF was achieved, AOSP ROMs were impossible on Rezound. So, how much can be done by simply unlocking it by HTC's tool and not getting S-OFF? What is the difference between unlocked bootloader with S-ON (i.e. HTC's unlock method) and unlocked Bootloader via S-OFF like I did for the Dinc2? That is my basic question.
Click to expand...
Click to collapse
SON and SOFF has nothing todo with getting AOSP. The main problems with aosp on our phones is getting the RIL to work with aosp. Our devs have said the ril is the most complicated theyve seen.
Anyway, when we were just s on we can still have perm root, the thing is kernels werent able to flash in recovery, was flashed in bootloader. We couldnt flash radios, or change firmwares. But it was just fine. Now that we have soff everythings easier to flash. Though getting soff required a wire trick to short out the motherboard to acquire it.
So having just an unlocked bootloader will just mean 1 more step flashing roms, thats all.
Sent from my ADR6425LVW using Tapatalk 2
slacka-vt said:
Well, I'm sold. Those are the two magic words I needed to hear. Can't wait for that bad boy.
http://androidheadlines.com/2012/05...ries-in-favor-of-droid-incredible-4g-lte.html
Click to expand...
Click to collapse
I can't understand how Verizon can play double standards like this. On the one side, they say they are 100% behind unlocking bootloaders for HTC and on the other hand they don't allow Motorola phones like the Droid X2, etc. to have unlocked bootloaders... unimpressed :/
Sent from my Incredible 2 using XDA
litetaker said:
I can't understand how Verizon can play double standards like this. On the one side, they say they are 100% behind unlocking bootloaders for HTC and on the other hand they don't allow Motorola phones like the Droid X2, etc. to have unlocked bootloaders... unimpressed :/
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
i do think its htc dev unlock for the inc lte (not a completely unlocked b/l)
but in (slight) defense of vzw...its not all on them
for example samsung just makes their devices unlocked by default and offers them to carriers so no issue there
htc has their unlock program and i imagine offers the devices with it built in to carriers, and unless one of them threatens to not carry it as is (like possibly att did) then thats how it comes
moto encrypts (which is much stricter than s-on btw) its devices and then asks the carriers if they want them to then unlock it...none of them are gonna say yes
Hopefully we'll be able to get root with s-off... I want this phone.. 4" screen, step ups in hardware... Hopefully all the great devs will follow from the dinc 1 and 2...
well, the rezound had htc-dev-unlock and just got s-off finally after what 8 months?
s-off is always a possibility.
but htc unlock to me, is still very nice, as we can root, and do just about everything we can with s-off, it's just a little getting used to.
htc unlock may infact even make it so some dev wont want to "waste" time for s-off as the phone is already rooted
andybones said:
well, the rezound had htc-dev-unlock and just got s-off finally after what 8 months?
s-off is always a possibility.
but htc unlock to me, is still very nice, as we can root, and do just about everything we can with s-off, it's just a little getting used to.
htc unlock may infact even make it so some dev wont want to "waste" time for s-off as the phone is already rooted
Click to expand...
Click to collapse
yeah personally i dont care about having to flash kernels through hboot....it wouldnt prevent me from getting the phone...and im imagine much like the rezound and other s3 phones got s-off from the same project, the inc lte would benefit from work on the one series
Still a little bummed about the camera but this is definitely good news. Thanks for the heads up!
So I'm unlocked and rooted with TWRP loaded up. Astounding how fast this all came together.
Glad I spent come coin on an xda-devs case and some beers tossed out.
Anyway....
I was wondering if, with the above exploits on our new HTC Ones, we had to worry about an OTA update locking us out, or killing off root etc.
cyberstraz said:
So I'm unlocked and rooted with TWRP loaded up. Astounding how fast this all came together.
Glad I spent come coin on an xda-devs case and some beers tossed out.
Anyway....
I was wondering if, with the above exploits on our new HTC Ones, we had to worry about an OTA update locking us out, or killing off root etc.
Click to expand...
Click to collapse
It appears Verizon has gotten HTC to blacklist the Ones. People are no longer able to unlock.
I get that, but I was wondering if I, who have already unlocked & rooted, etc, will be susceptible to VZW relocking it somehow via OTA.
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
89titanium said:
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
Click to expand...
Click to collapse
Im sure there will be root. but it will take a while, and i dont see anybody posting on the dev section talking about root. so probobly in afew months, once they read the source of the OS, and figure out how to make root.
Im from big red, and they always lock there bootloaders. so thats alittle more work and codeing which turns into abit more waiting time if you want custom roms. but G4 seems like a pretty popular phone, so im sure root will come eventually
89titanium said:
1) Is this phone likely to get root soon after release? Just based on LG history or whatever is known about the phone so far.
2) Does being on Verizon usually mean waiting longer or not getting root access at all? If Verizon-rooted phones are rare, please let me know some good alternatives.
Thanks all for putting up with me.
Click to expand...
Click to collapse
This phone hasn't been fully released yet. It will def get root. I'd give it a month or so.
I have Verizon and the G3 was unlocked within 3 months. I'm hoping since this is Qualcomm's first hexa-core, there'll be some exploits to gain root/unlock BL faster. Take it from a Sammy guy, WAIT THE FEW MONTHS. Samsung hasn't seen an unlocked BL for Verizon in 2 years.
Sent from my S5 using your mom
yep, probably gonna pull the trigger on the att g4 with their nasty corporate locked BL crap. I'd normally be concerned about root, but in this case I'm not terribly worried, because this phone will have SO much attention in the dev community. now, getting the att BL unlocked to run twrp... that's another story and could be a very long time if at all (just for the att version).
The official 5.1 update is on it's way from Verizon next week. For those of us waiting patiently for jcase to release an s-off method, I'm thinking it might be better to avoid updating? I can only imagine the hboot will get an update with this 5.1 update. With that, it will probably undo all the work jcase has done up to this point.
Am I wrong to think this?
Is it harmless to take the update?
guitarist5122 said:
The official 5.1 update is on it's way from Verizon next week. For those of us waiting patiently for jcase to release an s-off method, I'm thinking it might be better to avoid updating? I can only imagine the hboot will get an update with this 5.1 update. With that, it will probably undo all the work jcase has done up to this point.
Am I wrong to think this?
Is it harmless to take the update?
Click to expand...
Click to collapse
Harmless unless you want to meet up the next time I drive down to Delaware.
There is no sense in waiting on an update for a root exploit that may or may not ever come. S-Off already works on 5.1 but Verizon users are still waiting for a root exploit as before. Odds are you could be waiting a long time. Might as well enjoy the new software while you wait.
guitarist5122 said:
The official 5.1 update is on it's way from Verizon next week. For those of us waiting patiently for jcase to release an s-off method, I'm thinking it might be better to avoid updating? I can only imagine the hboot will get an update with this 5.1 update. With that, it will probably undo all the work jcase has done up to this point.
Am I wrong to think this?
Is it harmless to take the update?
Click to expand...
Click to collapse
Plenty of helpful members with Java Cards to get you S-Off now. Best if you can find someone in your area to meet with to avoid shipping the device.
Went that route a couple of months ago and been happily flashing custom Rom goodness ever since.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
guitarist5122 said:
...it will probably undo all the work jcase has done up to this point.
Click to expand...
Click to collapse
There's nothing (public) to undo. Unless by chance jcase discovered an exploit and HTC found it as well and fixed it....
It's starting to appear that many of these folks who can figure this sh*t out are losing interest in working on devices from Verizon and other carriers who go to extreme lengths to lock them down. I mean, my previous phone was a Galaxy S3 and Samsung / VZW locked them down tight. The S4 uses presumably the same security (my wife had one so I was a little up to speed on them). I haven't bothered checking the S5 or S6 but I'm confident they're not exploitable either.... Just to be clear, I'm not criticizing those folks if they're no longer trying. That's 150% their decision and choice !
hallstevenson said:
There's nothing (public) to undo. Unless by chance jcase discovered an exploit and HTC found it as well and fixed it....
It's starting to appear that many of these folks who can figure this sh*t out are losing interest in working on devices from Verizon and other carriers who go to extreme lengths to lock them down. I mean, my previous phone was a Galaxy S3 and Samsung / VZW locked them down tight. The S4 uses presumably the same security (my wife had one so I was a little up to speed on them). I haven't bothered checking the S5 or S6 but I'm confident they're not exploitable either.... Just to be clear, I'm not criticizing those folks if they're no longer trying. That's 150% their decision and choice !
Click to expand...
Click to collapse
Surprisingly the SG6 is able to flash ROMs. no bootloader unlock, but still surprising considering how hard SG3/4 was locked down when I was on them.
andybones said:
Surprisingly the SG6 is able to flash ROMs. no bootloader unlock, but still surprising considering how hard SG3/4 was locked down when I was on them.
Click to expand...
Click to collapse
So going forward, after our edge programs are eligible etc etc, what is the best alternative to have an unlocked bootloader and root even be an option without extreme measures? Pay off the edge program and go to T-Mobile and HTC? That way the bootloader can be unlocked from HTC? I'm very thankful to have my M9 rooted and unlocked but thinking ahead, what's the best course of action? Thoughts?
andybones said:
Surprisingly the SG6 is able to flash ROMs. no bootloader unlock, but still surprising considering how hard SG3/4 was locked down when I was on them.
Click to expand...
Click to collapse
Is it the same as can be done on the S3 with a locked bootloader ? I'd have to go back to that forum to get the name as I don't remember it.... Safestrap ?
Looks like it's not Safestrap after all. I'm quickly scanning but don't see much details yet. I do see quite a few ROMs available though !
hallstevenson said:
Is it the same as can be done on the S3 with a locked bootloader ? I'd have to go back to that forum to get the name as I don't remember it.... Safestrap ?
Click to expand...
Click to collapse
I hated SS.
I'm not exactly sure how it's done I just have a buddy on SG6 on VZW and loves it, being able to mke ROM.
I do know it isn't SS
"ping pong root"
http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
andybones said:
I hated SS.
Click to expand...
Click to collapse
Never had to deal with it.... I rooted mine the same day I rec'd it ! Same with my previous phones - all rooted in less than (2) days. Well, except for my HTC Eris. That one took a couple of months after I got it before jcase came up with an exploit.
I had scott123 "free" my M9 the day after I rec'd it.
hallstevenson said:
Never had to deal with it.... I rooted mine the same day I rec'd it ! Same with my previous phones - all rooted in less than (2) days. Well, except for my HTC Eris. That one took a couple of months after I got it before jcase came up with an exploit.
I had scott123 "free" my M9 the day after I rec'd it.
Click to expand...
Click to collapse
only reason i had to use SS was cos my dad got a new phone and gave me his old sg3, and at this point it had 4.4.4 so bootloader couldnt be unlocked anymore and had to use SS, it was horrible imo
I wonder why google has made it so simple to unlock the bootloader on the Google Play version of the Pixel phones while at the same time they are supposedly pushing so hard to make achieving root more difficult with Android 7?
Is there any benefit of having an unlocked bootloader without root access? If so what is it?
Flashing factory images instantly is one benefit.
norcal61 said:
I wonder why google has made it so simple to unlock the bootloader on the Google Play version of the Pixel phones while at the same time they are supposedly pushing so hard to make achieving root more difficult with Android 7?
Is there any benefit of having an unlocked bootloader without root access? If so what is it?
Click to expand...
Click to collapse
Root was achieved on Nougat when it was in beta. It's the new partition layout of the pixel that makes the current method unusable. But the guy behind SU gets one soon and will figure it out. Things change. They aren't making it harder. If they wanted to make it harder they would lock the bootloader down like Verizon.
Gizmoe said:
Root was achieved on Nougat when it was in beta. It's the new partition layout of the pixel that makes the current method unusable. But the guy behind SU gets one soon and will figure it out. Things change. They aren't making it harder. If they wanted to make it harder they would lock the bootloader down like Verizon.
Click to expand...
Click to collapse
I don't know how valid they are but I've read several articles claiming the Google is purposely trying to make it more difficult for devs to accomplish root. If that is true it doesn't make any sense that the bootloader isn't locked down right outta the gate. Idk. Just hope we get root for these things soon. I spent forever on at&t with both a galaxy s 4 and a note 4, waiting for ever for root, which as far as I know never came. If it did it wasn't until after I moved on. I hope that doesnt happen with the pixels.
norcal61 said:
I don't know how valid they are but I've read several articles claiming the Google is purposely trying to make it more difficult for devs to accomplish root. If that is true it doesn't make any sense that the bootloader isn't locked down right outta the gate. Idk. Just hope we get root for these things soon. I spent forever on at&t with both a galaxy s 4 and a note 4, waiting for ever for root, which as far as I know never came. If it did it wasn't until after I moved on. I hope that doesnt happen with the pixels.
Click to expand...
Click to collapse
As long as you have the google store version it's just a matter of time. I'm guessing by December. When the layout of a device changes as drastically as the pixel it takes the devs behind the exploits to rewrite code. Chain fire stated somewhere I read that he was only waiting for it to ship to him and then he will start coding for it. Also devs like beanstown are getting one in November and then purenexus Roms will follow. Beans stated specifically he was not getting the device if those rumors were true and he is getting the device. It means that google is releasing the source. They all ready released kernel source as I see despair has a kernel in the dev section. This all means that it can and will be done. Just be patient. Google store devices get all the attention. The pixel will be no different.
Everything will be fine, most odd the devs don't even have the phone yet. Chainfire will figure it out, once we figure out out the partition layouts, its just a matter of time before we can flash twrp, which allows us to flash su.. . All in time my good friends. Blame Google for their slow shipping times
Skipsoft made it sound like Root was already available but wasn't getting enabled/released until after TWRP is released.
I sort of thought that was weird.
After reading this thread, I'm bummed out.
Didn't realize we were still waiting on Chainsoft, et.all. to get the phone still.
My XL arrived today and there are a few dozen apps I can't install until after Root is available.
Ugh.
http://www.androidauthority.com/google-pixel-root-chainfire-724857/
Pixel news in general getiing better and better. Unlocked VZW bootloader, root and tmo giving you $325 back, all we need is some in stock ahem...gooooogle..