Related
I got to thinking...bad sign.
Is there a chance you could pull an iphone dev team and hold off on release until the next major one from SE? Like how the iphone devs did with the 4.0 jailbreak where they waited so that Apple wouldn't patch the exploit. If it's relatively easy to patch it might be better to keep it undisclosed until 2.1 is released so they don't just patch it.
That's a long time to wait and see. SE themselves have pretty much admitted that their adjusted "Q3" release for Eclair on the X10 really means the end of Q3 (ie: late September), as they said the rollout would be Q3 through early Q4.
Also, what's the point in waiting. Root means ROM chefs can cook up FroYo ROMs for the X10, bypassing any need to ever install the official X10 Eclair release.
As far as I know we can downgrade our builds so it shouldn't be an issue.
-------------------------------------
Sent via the XDA Tapatalk App
saltorio said:
Also, what's the point in waiting. Root means ROM chefs can cook up FroYo ROMs for the X10, bypassing any need to ever install the official X10 Eclair release.
Click to expand...
Click to collapse
Well the X10 is still being sold so it might start shipping with 2.1 after that release and if the exploit can potentially work on X8, which might ship with 2.1, it would mean that if it's released now SE might "fix" it making the X8 harder to root.
robbyf66 said:
As far as I know we can downgrade our builds so it shouldn't be an issue.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
For now, but there's no guarantee SE won't start locking down updates so that the updates need to be signed for the update to even start taking place.
come on! if the are interesting to block root down they will!! we are talking about Sony Ericsson, you think they're weirds (at least technically speaking...)
Well - for what it's worth - SE did clarify on their forums that though they're not supporting rooting, that simply means they won't do anything to ease the process and not that they're actively going to try to prevent rooting from happening.
With that said, they could always fix the exploit used by the rooters and say it's a security fix, and... oops... it also happened to prevent the existing root from being performed.
I agree with the rooters decision not to release the exploit they're using, and hope they can mask it in their final public root process to make it harder for SE to figure out.
couldnt resist asking this question.....
for how many days can you keep this off?
how many 1.6 versions do we have for x10?
will it not take a week for SE to cover this exploit even after 2.1 and release a new version?
i am not against anyone or their ideas (respect the devs behind root and their master minds)...but just my 2 cents to this.... i dont think stopping the root for 3 months will gain us so much....if wanted SE can burry the root exploit in a week's update after 2.1.....
I thought that now we have a rootable signed rom even if SE patch the exploit in future firmware, we can always downgrade to the current firmware then install customizations from there.
I dont see an easy way for SE to block downgrading as the current signed firmware is hosted all over the web and it can be flashed using the debranding method without connecting to SE servers.
what will be interesting to see is whether root gives us a way of signing new firmware or flashing non signed firmware..
ohhh the possibilities !
There is only one version of 1.6. The rest is just changes made by the manufacturers.
From my prior experience with HTC, once you achieve root, you NEVER want to update your phone using their official Rom. NOT matter how enticing the newer version of the rom is. It is on the manufacturers' interest to close the loopholes.
For example, when the Rogers branded HTC Magic was upgraded to include the Sense interface, it closed the root. People had to wait like three months before someone could root the phone again.
I don't think SE will try to patch the root. Why do I think that?
(1) It takes them so long to even come out with firmware/OS to begin with, it's just too much effort for them to add anything else on the plate.
(2) Se knows that blocking any efforts will hurt their bottom line, they want to sell more devices so why hurt that?
SE could actually patch the loop hole or whatever in an update by accident anyhow.....
thedinks said:
SE could actually patch the loop hole or whatever in an update by accident anyhow.....
Click to expand...
Click to collapse
Exactly. Waiting for 2.1 to be released might be a fruitless waste of time.
The best option is to hide the roothack mechanism as best they can. There's only so much you can do.
mtechfan said:
(2) Se knows that blocking any efforts will hurt their bottom line, they want to sell more devices so why hurt that?
Click to expand...
Click to collapse
I'd agree, were past decisions not to the contrary. If they really wanted to sell more devices, they:
1.) wouldn't have released buggy firmware to reviewers the world over, resulting in mediocre to poor reviews prior to launch.
2.) would have included multi-touch support in the X10 hardware, as they had originally stated.
3.) would not be taking their sweet time getting an OS update out for the X10 line, and would more than likely already have 2.1 available with 2.2 set for later this year.
......and perhaps SE would be secretly happy that root has been achieved so that moves all of us complainers off their backs so they can focus on updates for the majority of their users...
-------------------------------------
Sent via the XDA Tapatalk App
once rooted why would we even download SE's 2.1 update ? or any other SE update ? no need too
andy8271 said:
once rooted why would we even download SE's 2.1 update ? or any other SE update ? no need too
Click to expand...
Click to collapse
Of course not, but chances are that they'll start shipping the new phones with it already installed. Like the X8 or any X10 made after the release for that matter.
True, but some of the features included in Sony's update would be integrated into a cooked ROM update.
Sent from my X10a using Tapatalk
Thepuffytaco said:
True, but some of the features included in Sony's update would be integrated into a cooked ROM update.
Sent from my X10a using Tapatalk
Click to expand...
Click to collapse
I'm thinking of being able to root the ones released with an update already installed. I doubt it will happen, it's just food for thought at this point.
quick question..
what's the point of them closing the loopholes?
i mean.. it's not like nintendo ds or psp where you hack it and you can d/l games for free and they lose revenue on that..
we just want to be able to use the phone to it's max potential ..how it was meant to be when built..
so why is this not supported by companies and why do they make it hard for ppl to root?
So as the interwebz suggest, 4.4.1 is right around the corner for the Nexus 5/GPE devices. Considering the fact that the VZW variant of the Moto X was on the bleeding edge of the Kit Kat OTA and got it before even the Nexus 4, do you think this is a trend that will continue? I'm interested to see what bug fixes there are and if the promised camera improvements will be aimed specifically at the Nexus 5, or perhaps broader improvements to the software. What do you guys think?
I don't think 4.4.1 will aim other devices. It will include fixes for Nexus 5 only IMO.
I'm worried about the next update. What if we can't get root?
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
Then you buy a developer's edition.
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
This is one big reason I went for the Dev Edition... I'm too much of a tinkerer to fret over such unknowns. I mean it always comes eventually, but with Dev Editions you get instant gratification! Just need to flash stock recovery, accept the OTA, reflash custom recovery, re-root. BAM, done.
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
I've been using an Android phone since 2.1.
By my quick count on Wikipedia, there have been 27 versions (including minor updates) of Android since 2.1.
I'm not aware of any Android version that was discovered to be unrootable.
I suspect you don't have to be too worried...
icon123 said:
Then you buy a developer's edition.
Click to expand...
Click to collapse
Buy me one? I don't have that kind of money.
Furthermore, I have a Motomaker custom. I don't want to lose that.
kbluhm said:
This one reason I went for the Dev Edition... I'm too much of a tinkerer to fret over such unknowns. I mean it always comes eventually, but with Dev Editions you get instant gratification!
Click to expand...
Click to collapse
I beat you by about 5 sec. But really, that's what this game has come to. If you want easy root and possibly romming, then dev editions are going to be the only way to go. Right now, I think moto is making that easier for us to do.
binary visions said:
I've been using an Android phone since 2.1.
By my quick count on Wikipedia, there have been 27 versions (including minor updates) of Android since 2.1.
I'm not aware of any Android version that was discovered to be unrootable.
I suspect you don't have to be too worried...
Click to expand...
Click to collapse
I suspect you need to do more reading. Check up on what security features KitKat brought to our MotoXs.
Edit: I'm not so much worried about If you can root it, I'm worried about having it published. Jcase only rooted 4.4 because we were able to downgrade the bootloader. If that wasn't possible, I still don't think there would be root for the MotoX (non-dev).
natezire71 said:
Buy me one? I don't have that kind of money.
Furthermore, I have a Motomaker custom. I don't want to lose that.
Click to expand...
Click to collapse
You simply sell your subsidized phone and buy a dev edition. Can't help you about the moto maker though.
natezire71 said:
I suspect you need to do more reading. Check up on what security features KitKat brought to our MotoXs.
Edit: I'm not so much worried about If you can root it, I'm worried about having it published. Jcase only rooted 4.4 because we were able to downgrade the bootloader. If that wasn't possible, I still don't think there would be root for the MotoX (non-dev).
Click to expand...
Click to collapse
I suspect I've read plenty about KitKat. I know about the security features.
Jcase rooted 4.4 using the downgrade because an existing vulnerability was available. He explicitly stated that there was another vulnerability available and he just wasn't going to develop for it/reveal it. Vulnerabilities are always discovered.
What, you think Apple hasn't been trying to quash rooting for years now?
I'm just saying, I've been in IT for a long time. Exploits are discovered, workarounds are created. Root access is gained and life moves on.
binary visions said:
I suspect I've read plenty about KitKat. I know about the security features.
Jcase rooted 4.4 using the downgrade because an existing vulnerability was available. He explicitly stated that there was another vulnerability available and he just wasn't going to develop for it/reveal it. Vulnerabilities are always discovered.
What, you think Apple hasn't been trying to quash rooting for years now?
I'm just saying, I've been in IT for a long time. Exploits are discovered, workarounds are created. Root access is gained and life moves on.
Click to expand...
Click to collapse
Of course, but what if it's never published? I'm not worried about the actual exploits. There will always be exploits. I'm only concerned with an awesome dev to publish it. Who else is working on the MotoX? So far, it seems like Hashcode and Jcase. If Jcase decides not to publish... Then what?
natezire71 said:
Of course, but what if it's never published? I'm not worried about the actual exploits. There will always be exploits. I'm only concerned with an awesome dev to publish it. Who else is working on the MotoX? So far, it seems like Hashcode and Jcase. If Jcase decides not to publish... Then what?
Click to expand...
Click to collapse
Well, there are never guarantees, of course... but given that virtually every version of Android on every phone attains root eventually, I'm just going to have some faith!
I think people may be putting too much faith in what devs can do based on what has been done.
4.4 has the potential to change things big time. dm-verity combined with a locked bootloader is going to be a beast to crack. Once a device ships from the factory with it enabled and a locked bootloader, I would not be expecting root on it anytime soon. Then you will have people asking why don't we just crack the key like they were when the GS3 came out. (answer: you will never ever crack the key. --Math)
As for using the idea that Apple has tried and never got it to stick, I'd say they haven't tried this hard.
Just as a sidenote, I don't think the SELinux and dm-verity additions in android are either bad or targeted at the modders out there. These are excellent steps in securing the OS, and shows that Google is serious about making devices trustworthy. The work they did on dm-verity is just great stuff. This is good for people who don't care about modifying their device and those who only buy devices with unlocked bootloaders, but not so good for people who have a locked bootloader, and are on either ATT or VZW, both of whom really don't want you to modify your device.
TL;DR - Buy a device with an unlocked bootloader, don't count on anything, past success is not indicative of future success.
I hope 4.4.1 brings an even better ART this time.
Seems like this update is pretty specific to the Nexus 5 as a camera fix. Not sure the Moto X will even see it.
Sent from my XT1056 using XDA Premium 4 mobile app
phippsy84 said:
Seems like this update is pretty specific to the Nexus 5 as a camera fix. Not sure the Moto X will even see it.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Won't really know until the 4.4.1 source is published. Could be a lot of other stuff on the back-end that was updated/fixed that wouldn't really show up in a major changelog.
Nexus 4 received the update today too so it isn't nexus 5 specific.
imnuts said:
Won't really know until the 4.4.1 source is published. Could be a lot of other stuff on the back-end that was updated/fixed that wouldn't really show up in a major changelog.
Click to expand...
Click to collapse
Very true
Sent from my XT1056 using XDA Premium 4 mobile app
Not only the N4 but the Nexus 7 LTE. SO... probably more going on than just camera
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.
Hey all I have a purely stock unrooted nexus 6p that I am trying to figure out why I am getting the monthly update a week before the release of the next update ever time. I am thinking its ATT blocking the updates. Can you please post the carrier, date and time when you received the May update please?
VZW and mine showed update on the 13th. Was starting to wonder when I'd see it, but it finally hit.
Still waiting here on Sprint for the update. This is taking forever.
Sent from my Nexus 6P using XDA-Developers mobile app
I have Project Fi and get my updates rather late too. It's not just you.
If you really want the update, then by all means flash it manually as soon as it comes out.
I don't think that the carrier can actually block the update, unless you somehow bought the 6P carrier-branded, and through the carrier. That being said, I've been on Tmo, Fi, VZW, and Straight Talk, and I have never actually received a monthly security update as soon as they are released. Usually I had to wait a couple of days. I think those updates roll out randomly, so I'd say just keep waiting, or flash it yourself.
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Yes I know I can side load the update. That is not the point of this post. Its to get an idea of timing of when people are getting the updates and what carriers they are on.
Google releases there updates in a phased approach. They first release it to 1% all the way up to 100%. 100% should be getting the update within 2 - 3 weeks. The 2 -3 week period I have yet to see!
What I was trying to determine is if this is the carriers blocking the updates till a specific time or its google just not pushing updates to the phones like they say they are.
Note ATT is notorious for blocking updates. And yes they can block the update as long as your using there network to check.
If Google is releasing security updates on a monthly bases and you don't get it before the next update is released, whats the use in a monthly update???
brichardson1991 said:
Nexus updates are known to be pushed out in stages.
If you are desperate just flash the images via fastboot or sideload the ota via adb.
Click to expand...
Click to collapse
How do you side load. I just saw that google has released images to do that. I too have a 6p completely stock. I want to keep the bootloader locked. I have never had a nexus device before. So this is new to me I always used Samsung. The problem with Samsung is you have to mod the hell out of it. this phone just works like it is supposed to. but I do want to try to update manually. So I followed the instructions in the general section and I am installing the sdk as we speak. So what is the process for side loading and where do I get the update? My phone gets its updates really late in the month and I hate waiting. Also I booted this phone into recovery and tried to do a factory reset but it didn't do it and there were all these options I am not used to. How do I do a basic factory reset from recovery? I would like to know just in case. I am not wanting to go crazy with this phone but I do want to understand it so when I get the nexus 7 I can play with this one when I get spare time.
Hey all,
Since the ota download for 6.0 has been pulled I was wondering if anyone had a chance to grab it before it went down?
Thanks
I did
Sent from my ASUS_Z00AD using XDA-Developers mobile app
humayunarshad said:
I did
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Click to expand...
Click to collapse
Is there an chance you can post it for us that missed out?
Wait
I have it as well - but wouldn't want to post it. It's a beta release, and as such, you won't get future OTA updates (at least until the official release comes out), and will have to update manually, and will have to wipe/reset to avoid issues going from beta to official. I really regret not waiting for the official, but hopefully fixing it won't be more of a hassle than upgrading was. I don't like that I'll have to set up everything again, but it is what it is, and as long as I get back on official so I can get future updates all will be well. It'll be better to wait, especially since the beta has bricked many people's phones (I got lucky, mine works flawlessly), and you won't have to go through extra bullcrap to get back on the official releases.
If you want so badly
http://uptobox.com/jdh8zuqc3kvg
xXIJDIXx said:
I have it as well - but wouldn't want to post it. It's a beta release, and as such, you won't get future OTA updates (at least until the official release comes out), and will have to update manually, and will have to wipe/reset to avoid issues going from beta to official. I really regret not waiting for the official, but hopefully fixing it won't be more of a hassle than upgrading was. I don't like that I'll have to set up everything again, but it is what it is, and as long as I get back on official so I can get future updates all will be well. It'll be better to wait, especially since the beta has bricked many people's phones (I got lucky, mine works flawlessly), and you won't have to go through extra bullcrap to get back on the official releases.
Click to expand...
Click to collapse
It's a pain that we'll have to stick to beta for now, judging from the other variants that asus release marshmallow before it will take a month or less(eg: Zenfone Max, mm beta release on 1st week of may, mm official release on 1st week of june), sad for us non-modder users.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
Well, at least I don't have to dread setting up my phone again too soon. I just really hope going from beta to official will be just as simple as upgrading from L to M was.
Basttrax said:
Is there an chance you can post it for us that missed out?
Click to expand...
Click to collapse
I have the FW on my phone but really hesitant to upgrade after seeing the comments.. Better to wait a few more days rather than brick the phone...
Sent from my ASUS_Z00AD using XDA-Developers mobile app
humayunarshad said:
I have the FW on my phone but really hesitant to upgrade after seeing the comments.. Better to wait a few more days rather than brick the phone...
Click to expand...
Click to collapse
Definitely wait for official, the beta release really worked well for me but I'm lucky, and now I'm dreading having to figure out how to get back on an official release so I'll get updates in the future - and I'll have to set up my phone from scratch again.
I did upgrade to 6.0, so far i've experienced a bit of lag and battery drain( lot worse than .184)
Same here, upgrade went fine but now some significant battery drain taking place; I can guess why, the phone is now constantly warm and the system monitor utility shows that the processor spends some serous time at higher clock frequencies.
Also experiencing some microSD card disconnects, from time to time, for no apparent reason.
All in all, it wasn't a bad update though [emoji57]
Initially I also had really heavy battery drain after updating, but doing a factory reset and reinstalling my apps afresh seemed to fix. Now getting basically the same battery life as before the update, which is to say neither great nor terrible. Am very pleased with the improved RAM management after updating though - it is releasing RAM much better than before and running very smoothly.