Database Users

HTC One and Vanilla Android (5.0 (Keylime Pie))?

I had sworn off non-Google phones after a couple of Samsung experiences, but the One is just so well-designed, I can't resist it. It's really the first Android phone which can compete with the iPhone in hardware design.
Now my question is, what happens when Google rolls out Android 5.0? Would vanilla Android be available quickly for the unlocked 32Gb and the 64 Developer edition? Is there any reason why it may not happen, or it may be difficult to do? Would the non-standard button layout throw a wrench in the OS upgrade possibilities?

I dont think so
If you buy the developer edition you can install plane lemon pie on it as it has the bootloader unlocked or any kind of ROM you want. On the Unlucked one you will need to wait until HTC releases the update as it also comes with thei Sense 5.0 UI.:laugh:

HTC have been saying they will be working a lot harder to get the latest updates out to their phones. And you can see as well in the One series that they have delivered to an extent.
Plus as the HTC One is their flagship device for this year, they will be putting all of their attention on it

As I would agree to this, without source code and binaries for the device I.E> sensors, bt, wifi, processor from HTC the dev edition wont just = instant updates to latest and greatest. Its just nice to see them least offering it up.

They don't even have 4.2 on the One, so I am assuming it would take them a long time to get KLP on the One.
Sent from my Nexus 10 using Tapatalk HD

sidthegreatest said:
They don't even have 4.2 on the One, so I am assuming it would take them a long time to get KLP on the One.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
There's a reason why they did not got for 4.2. Here's a quick snip from Anandtechs amazing review
HTC says it went with 4.1 for both stability and time to market reasons, which I think is reasonable considering some of the 4.2.x issues people have complained about, though 4.2.2 fixes most of it. At this point it would be awesome to have 4.2, but for a smartphone the only features I miss are the notification shade settings and perhaps photosphere.
Click to expand...
Click to collapse

Rage1ofakind said:
There's a reason why they did not got for 4.2. Here's a quick snip from Anandtechs amazing review
Click to expand...
Click to collapse
Not to mention Lock screen widgets.
But my point is not whether they CAN out 4.2 on their device, but the fact that they did not.
Samsung has 4.2 on the S4, while the SIII also has a leaked ROM. So, I would say that KLP would come to the One in Q4 of this year at the earliest.
Sent from my Nexus 10 using Tapatalk HD

doakills said:
As I would agree to this, without source code and binaries for the device I.E> sensors, bt, wifi, processor from HTC the dev edition wont just = instant updates to latest and greatest. Its just nice to see them least offering it up.
Click to expand...
Click to collapse
What is HTC's history in terms of offering source code and binaries for their hardware? (I haven't had an HTC since the WM days
I pre-ordered the 32GB unlocked, but now I am wondering if I jumped the gun and I should sit tight and wait for whatever the Next Nexus phone is? The only problem is, Google does not know how to drive good hardware design, and I really doubt the next Nexus will be as well designed or built.
For what it's worth, I love 4.2.2 on my Galaxy Nexus, although it is getting to be a bit laggy with some apps. Nevertheless, I feel it is a bit more bug-free overall than 4.1.
If it doesn't look like HTC will release enough code to allow the One to be made vanilla Android and freely updated to the latest OS, i may actually cancel.

When the devs get the bootloaders unlocked flashing things will be no problem. It may take a while but it'll happen eventually.
Sent from my SGH-i927 using xda premium

Does anyone have any estimates as to when or if we will see any cm10 or paranoid round here?
Also, as ive come over from a samsung, not a 100% sure how sense development has been on sense roms as they failed to port it to anything else, have they managed to mix it with aosp or anything else?
cheers

spitfire2425 said:
When the devs get the bootloaders unlocked flashing things will be no problem. It may take a while but it'll happen eventually.
Sent from my SGH-i927 using xda premium
Click to expand...
Click to collapse
I think the bootloader unlock is already possible using htcdev.

snowblind2142 said:
Does anyone have any estimates as to when or if we will see any cm10 or paranoid round here?
Also, as ive come over from a samsung, not a 100% sure how sense development has been on sense roms as they failed to port it to anything else, have they managed to mix it with aosp or anything else?
cheers
Click to expand...
Click to collapse
Atm im running aokp on my htc one-x
I can run pa or cm too if i wanted to and this device only has the htcdev unlock available.
Also sense from other devices can be ported but its a pita so dont expect to much on that side.
However there are also roms who strip htc sense entirly making it a treu aosp experience and diff ui's can be flashed( xperia and samsung ui have been ported to hox)
Obviously this doesnt mean its gonna happen at the one but i sure hope so
Sent from my HTC One X using xda premium

romitkin said:
I think the bootloader unlock is already possible using htcdev.
Click to expand...
Click to collapse
But bootloader unlock (which AFAIK is available for the 32gb unlocked version as well) does not mean that the rest of the hardware will be opened up to developers, right?
Ugh, I was hoping for a much more optimistic scenario.... I love the efforts the developers here pour into maintaing these sets when the hardware is not exposed and the manufacturer drags its feet on updates, but after having to deal with the constant ROM tinkering and numerous resulting issues with my old Samsing sets, I am not excited about the prospect of going through it again.
Also, I am wondering if the non-standard soft buttons will affect easy porting of 5.0 to the One?

Having aosp etc on the one would be a bit pointless. I like it. The ones standout features are design sound and camera.
Youd have two out of three running aosp etc. Every other HTC device running has a scrappy camera since they went to 8mp. It remains to be seen what the ones camera would be. If it's deal though you lose a lot. Okay 4.2 etc is sweet on the nexus range but there hardware was built around it
Fairplay is try it on the one..debateable whether it'd be worth it though
Sent from my HTC One using xda app-developers app

MacGuy2006 said:
What is HTC's history in terms of offering source code and binaries for their hardware? (I haven't had an HTC since the WM days
I pre-ordered the 32GB unlocked, but now I am wondering if I jumped the gun and I should sit tight and wait for whatever the Next Nexus phone is? The only problem is, Google does not know how to drive good hardware design, and I really doubt the next Nexus will be as well designed or built.
For what it's worth, I love 4.2.2 on my Galaxy Nexus, although it is getting to be a bit laggy with some apps. Nevertheless, I feel it is a bit more bug-free overall than 4.1.
If it doesn't look like HTC will release enough code to allow the One to be made vanilla Android and freely updated to the latest OS, i may actually cancel.
Click to expand...
Click to collapse
HTC sucks at updating the new source code. They wait months after Google has already released it.
EVO LTE

Enraged21 said:
HTC sucks at updating the new source code. They wait months after Google has already released it.
EVO LTE
Click to expand...
Click to collapse
They are aware they were slow in releasing it. They are now trying their best to get it out on time. As to not invalidate the point on the developer version of the one.
Sent from my HTC One using xda app-developers app

romitkin said:
I think the bootloader unlock is already possible using htcdev.
Click to expand...
Click to collapse
I meant s-off. Sorry..
Sent from my SGH-I927 using xda premium

ste1164 said:
They are aware they were slow in releasing it. They are now trying their best to get it out on time. As to not invalidate the point on the developer version of the one.
Click to expand...
Click to collapse
I would hope so. But the fact that they are releasing their flagship with months old OS version is a little worrying.
I am not so broken up about 4.2, but 5 sounds like it will be a rather major update and if this thing doesn't get updated promptly, it will be a very disappointing acquisition for me.

arknailed7754 said:
Having aosp etc on the one would be a bit pointless. I like it. The ones standout features are design sound and camera.
Youd have two out of three running aosp etc. Every other HTC device running has a scrappy camera since they went to 8mp. It remains to be seen what the ones camera would be. If it's deal though you lose a lot. Okay 4.2 etc is sweet on the nexus range but there hardware was built around it
Fairplay is try it on the one..debateable whether it'd be worth it though
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Exactly. I can't believe there's already complaints about the time it will take HTC to update the phone to KLP. One of the main reasons people are flocking to this phone is the awesome job HTC did on the software features. If they slapped it together you could have the latest, but not the same experience. Can't have your cake and eat it too.

ste1164 said:
They are aware they were slow in releasing it. They are now trying their best to get it out on time. As to not invalidate the point on the developer version of the one.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
How do you know this? I would love for this to be true but, given my experience with the One X, I find it hard to believe.

Google: No Factory Image Or Proprietary Binary Hosting For Google Play Edition One

There's been a lot of speculation about just how Nexus-like the Galaxy S4 and HTC One Google Play edition phones will be, particularly from a technical / software update standpoint. Now, we have some relatively concrete information that sheds light on these issues.
First and foremost, Google will not directly handle software updates for Google Play edition devices. This has been reported as true, false, and generally disputed quite a lot in the lead-up to the launch. We know for a fact now (thanks to Anandtech) that while Google will supply the necessary Android builds to OEMs, the OEMs will be responsible for maintenance of kernels and all the various drivers and firmware pieces necessary for their specific device. The result is that Google gives the OEMs the Android build, and it's then up to the OEMs to make that build work on their Google Play edition device and perform the act of actually updating the phone. Google has issued an official statement that works very hard to not expressly deny that they won't be handling the updates (Droid-life):
What's this mean for you? It means that at the end of the day, the onus to update these phones will still be on Samsung and HTC. They will be able to circumvent the carrier certification runaround, and will in theory have much less work to do in maintaining these devices, but the responsibility still falls to them, not Google. This could mean any number of things. It could mean these phones will get updates within days of their Nexus counterparts. But more likely weeks, and possibly even months depending how much attention these phones are actually given by HTC and Samsung. I wouldn't say months is what we should expect, but I'm also saying such a gap is entirely within the realm of possibility. You have to remember, these phones will sell in miniscule quantities compared to their skinned brethren, and that means they aren't as high up on the value chain for software update attention. While it's certainly worth being optimistic about the update process, there's still plenty of reason to temper those expectations until we see these devices receive their first major Android release update.
he second thing we've learned is that Google will not host factory OS images for Google Play edition devices (see JBQ's post on this topic here). This will be up to Samsung and HTC, if they choose to do so. Google will also not be hosting any proprietary binaries (essentially, drivers) for these phones (again, see JBQ). Release of any binaries is, once again, up to Samsung and HTC. Taken together, all this information - as you may already have guessed long ago - means there is very little chance we'll ever see these phones supported in AOSP. It's not impossible, but it is extremely unlikely.
So there you have it: that's basically the nuts and bolts of what doesn't make the Google Play edition HTC One and Galaxy S4 Nexuses. Does this put a damper on the situation, or is it immaterial? Let us know in the comments.
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
welp this sucks !

I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.

H-Streety said:
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
Click to expand...
Click to collapse
Since we will probably be on 4.2.2 for a while you're going to be waiting.
Sent from my HTC One using Tapatalk 2

Possibly, but I am not losing my IR blaster and camera app for half-supported stock Android. If HTC will push out the update within a week or two after it comes out for Nexus devices, then I will definitely flash it, if not then I don't see the point of it. I would rather do S-OFF + Super Cid and still enjoy all these things than losing too many good things for basically just stock Android.

Nexus Experience Device not Nexus Device

That's really unfortunate.
Pretty ridiculous actually.
-Sent from Marino's One-

Did you really expect more? Google never said they would be Nexus devices or supported by AOSP. They are Nexus "Experience" devices... hence they offer the same feel without being the same.
Sorry to burst your bubble.... that said I think there will be dedication on the part of HTC and Samsung to get updates.. there isn't any excuse and you know if the device is on Google Play then el'Goog will be pressuring them to not delay
Sent from my Nexus 10 using Tapatalk HD

It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium

donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Zero timeline given. It will get it. The second it's released? No. A month after? Maybe.
Yep, OP...sure this is stock AOSP, but if anyone thinks the S4 and One will be updated the instant the Nexus line is, they are smoking some serious ****.
Samsung and HTC still have a role in this, ala Verizon (CDMA) Galaxy Nexus. It will slow things down. It's on HTC and Samsung to instantly update their proprietary apps to play well with AOSP. We've all seen that movie before, now have we?
Sigh. Can of worms. I called it. Once you integrate manufacturer specific features into AOSP (Beats, Zoe, etc) it WILL slow down the instant (expected) release of AOSP to "OMG PURE GOOGLE) phones. Psst: they aren't Nexi.
Just deal with it. I cringe for the blasting posts from those who got the One/S4 AOSP editions once the newest Android OS is pushed out...to the Nexus line first.
I see it now:
"THE NEXUS 4 JUST GOT 5.0. WHERE IS MY KLP ON MY ONE/S4 GOOGLE!??? PETITION STARTED!!!!1111"
And so on. Grabs popcorn.
Edit: thought I'd paste in a quote I just read that summarizes this situation quite well:
I don't see the point of these devices anymore. You lose out on the few customization that OEMs provided that weren't useless (fully functional Beats, camera software, improved text messaging and browser apps, etc.) for a vanilla experience that is nearly indistinguishable from the OEM version running a custom launcher. And no guarantee of fast updates.
You'd have to be a dummy to buy these phones from the Play store.
Thankfully I have an unlocked T-Mobile One. I'll just use it or flash whatever, whenever. Paid $450 for it and am very happy with my gamble.

So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.

donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version. I believe that more that others guessing about it.
Click to expand...
Click to collapse
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."

BarryH_GEG said:
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
Click to expand...
Click to collapse
google is the only one who can update aosp devices..nobody else

http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/

david279 said:
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
you are a thick one aren't you lol

hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
The first post says it isn't an AOSP device, Google isn't managing the proprietary drivers, they aren't posting the s/w images, and they aren't responsible for pushing out updates. So your statement is true; for Nexus devices. "Play Edition's" aren't Nexus devices.
The fact that it doesn't say the below which Google says about their devices probably means what OP posted is true.

M
Argenist said:
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
Click to expand...
Click to collapse
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands for resale and every day use. Hint. It isn't the Google or Dev one.
Unlock it for $7 and never look back.
Sent from my HTC One using Tapatalk 2

ericshmerick said:
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands. Hint. It isn't the Google or Dev one.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Understood, but would matter then to get the GE version over the Dev?

Argenist said:
Understood, but would matter then to get the GE version over the Dev?
Click to expand...
Click to collapse
They don't ship until July 9 so no one knows.
Sent from my HTC One using Tapatalk 2

hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
Not true..
This situation has been done before. The OG Droid (Sholes) was not a Nexus but ran vanilla software. Updates came but abit later. They came from Motorola.
Sent from my HTC One using Tapatalk 4 Beta

Thoughts on the coming security enhancements for 4.4

Has anyone taken a look at the new security enhancements Google has put into 4.4? It seems to me that this could go either way. While added security seems like a plus for things like malware, etc, it also could hinder development and openness as well. If device is locked before upgrading, it would seem that achieving several mods, even root, will become pretty arduous, if not next to impossible tasks. This seems to go against HTC's openness with the unlocking of bootloaders, though, so I wonder how they will handle it? I suppose in the meantime, end users should achieve s-off and unlock now before the update gets here. Any thoughts?

http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
According to this, this will only affect devices from carriers that do not allow bootloaders to be unlocked (verizon) if I understood it right.

It will not affect international users as we have no need of root exploits seeing as HTC provide a boot loader unlock tool.
It will affect Verizon users if Verizon continue to lock down bootloaders though.
Sent from my HTC One using XDA Premium 4

papski2 said:
http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
According to this, this will only affect devices from carriers that do not allow bootloaders to be unlocked (verizon) if I understood it right.
Click to expand...
Click to collapse
Everyone seems to forget that AT&T is now doing the same thing. So Its not just Verizon anymore.

rdw55a said:
Everyone seems to forget that AT&T is now doing the same thing. So Its not just Verizon anymore.
Click to expand...
Click to collapse
I'm pretty sure it's the other way around..att use to do it and now they allow it.

AT&T and bootloaders
a box of kittens said:
I'm pretty sure it's the other way around..att use to do it and now they allow it.
Click to expand...
Click to collapse
This is just one of the articles about AT&T and there stand on Unlocked Bootloaders.http://androidandme.com/2013/08/car...upport-unlocked-bootloaders-once-and-for-all/

I can understand why they would want to lock down a subsidized device. Guess I'll be purchasing unlocked/unlock-able devices at full price from manufacturers in the future.

If you want to mod your phone, vote with your wallet and switch to a carrier that actually cares about their customers.
The argument about buying an unlocked phone is moot on Verizon because of the CDMA network for voice.
This is all going to come to a head at some point... Especially with Verizon.
It is going to be a huge deal with HTC though in terms of getting S-OFF.....

I am still concerned that 4.4 may interfere with phones already rooted and running custom ROMs.

EtherealRemnant said:
It is going to be a huge deal with HTC though in terms of getting S-OFF.....
Click to expand...
Click to collapse
How so? The security makes exploiting the kernel and boot loader for root harder but we can already flash custom kernels, recovery and root when S-ON.
S-OFF isn't contained in the boot loader partition, like MID, tampered flag and locked flag etc it has its own partition.
As exploits are found HTC will obviously patch them which will make S-OFF harder but I'm not sure that increased boot loader security will have an impact on S-OFF.
Sent from my HTC One using XDA Premium 4

The more I look at it, if the device is unlocked and off prior to the upgrade, it should be fine, regardless of carrier. The obvious exception would be Verizon, but at least it won't be surprising to any of their customers. It's nothing new for them. I foresee an uptick in sales of international and dev edition Android phones in the future, though.

thegh0sts said:
I am still concerned that 4.4 may interfere with phones already rooted and running custom ROMs.
Click to expand...
Click to collapse
If your worried about it interfering with rooted devices I'd advise u to just wait for the devs to build 4.4 roms to flash. Roms will be available right after the OTA drops as usual so I would play it safe if you're worried. At lease Intel its known whether or not this is going to be an issue.
Sent from my HTC One using Tapatalk

monkboy24 said:
If your worried about it interfering with rooted devices I'd advise u to just wait for the devs to build 4.4 roms to flash. Roms will be available right after the OTA drops as usual so I would play it safe if you're worried. At lease Intel its known whether or not this is going to be an issue.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
The N5 already can be rooted. I'd say we don't have much to worry about on that front.

Will 4.4.4 adapt to Android L or require new install?

Having just installed omnirom with it having the ota updates, once android L is officially released, will all nightlies adapt to it on current installs? Or will that be a whole new install? Just curious. Thanks

Without the code handy, it'll be hard to say for sure. I'd hazard a guess and say new Android base, new nightly branch. But that's just a guess.

I agree with you. Because it's a new code, I also think that you'll need the whole new installation after all..
Sent from my Xperia S using XDA Free mobile app

There's a good chance from a developer standpoint it'll require major rework/rebasing.
From a user standpoint, it SHOULD be feasible to do a straight upgrade without wiping. (Although in the case of features that aren't re-implemented yet when L nightlies start, they'll reset to their defaults when they make it back in.) You will NOT be able to downgrade without wiping or restoring a backup though.
As a historical reference - many of my devices that were running 4.3 Omni were upgraded straight to 4.4, even though we started from scratch with 4.4

Well it's close to nexus6 release... Any news if omnirom will adapt to Lollipop or require a new rom?

ryancell said:
Having just installed omnirom with it having the ota updates, once android L is officially released, will all nightlies adapt to it on current installs? Or will that be a whole new install? Just curious. Thanks
Click to expand...
Click to collapse
If you mean "will moving to L require a wipe?" - Only if we screw something up. Android is designed to allow for seamless upgrades from one version to another, in fact, in the commercial world, requiring a wipe to upgrade will render you ineligible for GMS (gapps) licensing I'm fairly certain.
As to "all nightlies" - probably quite a few devices are going to get dropped with L. Almost surely the Exynos 4210 family, good chance quite a few of the Exynos 4412 family (I'd prefer to make it ALL of them tbh, and get that hell platform out of our codebase...), and probably a few other devices.
Other than Exynos4, we won't know until L gets released.

I'm on the sprint galaxy nexus which just recently got support for omnirom. Hopefully it will get L.. It will save me buying the nexus 6 as I will be happy to upgrade and keep my device. Great job/rom.

Entropy512 said:
...quite a few of the Exynos 4412 family...
Click to expand...
Click to collapse
My heart...

Entropy512 said:
a few of the Exynos 4412 family (I'd prefer to make it ALL of them tbh, and get that hell platform out of our codebase...).
Click to expand...
Click to collapse
oh man, I really do hope you guys manage to get L on my Note 2. There's quite a few of us out there, and it would be oh so nice not having to upgrade our hardware.

And are Omni people already working with Android 5.0 or they need to wait for official release?

j2002 said:
And are Omni people already working with Android 5.0 or they need to wait for official release?
Click to expand...
Click to collapse
Wait for the code drop to happen. Should not take long.
Sent from my Nexus 5 using XDA Free mobile app

shri_chanakya said:
Wait for the code drop to happen. Should not take long.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unless Google drops source earlier than normal (read: typically not until a few days after the first OTAs go out to Nexus devices), I wouldn't expect work to even start until November. (Since it sounds like the earliest OTAs and devices shipping are going to be November 3, which means that's the earliest possible date to even think about doing work unless Google drops source earlier than they ever have in the history of Android.)

One good reason not to take the Android 6.0 (M) OTA

Two Words: Root Access. It seems it may be harder to root Android M than we might have thought (Though we all expected this). So as a warning to those on 5.1 (whether you took the 5.1 OTA or waited for the 5.1 rooted img) and here is why:
http://www.xda-developers.com/a-look-at-marshmallow-root-verity-complications/
Given that a BL unlocked has not come out for the Droid Turbo on 4.4.4 or 5.1, this would possibly only make it harder to do so. I would suggest prolonging the OTA for as long as possible.
This is only a suggestion, however obviously you all are free to do as you please with your devices. Just wanted to give a fair warning. Though in this article it states that root might not be possible w/o BL unlock so moforoot might not even work because we can not modify our boot images.............yet (we hope). Again decision rest on your individual shoulders but I just thought, since Android M has been confirmed ( here ) for our devices, that we should at least be informed how this is going to affect our devices in the future (regarding root access and the probability of BL unlock mainly, of course). So it might not be wise to take the 6.0 update......at least not yet.
Let me know what you guys think.

We don't even have m yet....
Sent from my XT1254 using XDA Free mobile app

Yeah, we do. It's in my notifications now to update. Just wanna see what happens

Cjzi5i5 said:
Yeah, we do. It's in my notifications now to update. Just wanna see what happens
Click to expand...
Click to collapse
That's not M. [emoji23]

Wynnded said:
That's not M. [emoji23]
Click to expand...
Click to collapse
Lol don't crush his dreams.
Sent from my XT1254 using Tapatalk

It's my understanding that what you posted may not really be that relevant.
For example, we can't root 5.1 for the Turbo. Unless of course you were already rooted on 4.4.4. Maybe rooting 6.0 is easier/possible if you're already rooted on 5.1. I've seen this same thing on other devices I've owned. If you take an update too early you can lock yourself out while people running the lower version have more options.

Flowah said:
It's my understanding that what you posted may not really be that relevant.
For example, we can't root 5.1 for the Turbo. Unless of course you were already rooted on 4.4.4. Maybe rooting 6.0 is easier/possible if you're already rooted on 5.1. I've seen this same thing on other devices I've owned. If you take an update too early you can lock yourself out while people running the lower version have more options.
Click to expand...
Click to collapse
It clearly states that to root 6.0 that changes have to be made to the boot image which turbo users 4.4.4 or otherwise can't do. You're taking offensive to a warning post, not one meant to say it's impossible (provided BL unlock becomes available for the Droid Turbo). This is all based on Motorola's confirmation of the Droid Turbo getting 6.0 and how it could affect our devices future ability to obtain root.

Cjzi5i5 said:
Yeah, we do. It's in my notifications now to update. Just wanna see what happens
Click to expand...
Click to collapse
dont worry dude.. if we get lucky we will see M by next September.

I took the 5.1 update. I'm comfortable with the fact that I'll never get root. The moment 6.0 is available, I'll update that too... knowing full well that root will never happen. Don't tell folks not to update. That's your opinion. You want to keep root, that's up to you. For those of us that it is too late, we don't care. And we'll openly take that 6.0 update... if and when it comes.

irish_711 said:
I took the 5.1 update. I'm comfortable with the fact that I'll never get root. The moment 6.0 is available, I'll update that too... knowing full well that root will never happen. Don't tell folks not to update. That's your opinion. You want to keep root, that's up to you. For those of us that it is too late, we don't care. And we'll openly take that 6.0 update... if and when it comes.
Click to expand...
Click to collapse
I, much like you, took the OTA update and don't have root and would like to have it once again if possible. However I did state numerous times that this is an opinion, my opinion, and everyone is free to do as they please with their devices.

While I had root and an unlocked bootloader on my S3, I found that the need rarely arose for me to even have to elevate privileges. I mainly rooted and unlocked because while I loved its hardware specs, I *hate* TouchWiz. I specifically got this phone because it had a relatively vanilla version of Android on it, it has fairly decent specs, it's nowhere as large as the Nexus 6, and the store I was at, didn't have any X's in stock. I was more than aware that us getting an unlocked bootloader, much less root was pretty unlikely, and I was actually pretty comfortable with it, surprisingly enough.
Sent from my XT1254 using Tapatalk

I read the article in the OP, and I don't think we have much to worry about. It seems like verity relies pretty heavily on SELinux being set to enforcing, and we already have to set it to permissive in order to get our mofo'd roms to work properly. Does this reduce the security of our devices? Of course it does, but if you really cared about device security, you wouldn't be trying to get root access to your device in the first place. When there is an epidemic of peoples' identities/accounts/money/etc. being stolen via remote attacks, that's when I'll start to care about things like that. Even Stagefright, which is extremely well-documented and unpatched on most Android phones in circulation, doesn't have a single example of a real-world attack being executed using it (as far as I know).
Root access allows me to use things like Cerberus to help combat the much more probable event of someone with physical access to my phone getting into it, so when it comes to security, I'll take less security-by-design and more security that I can choose to implement.