what can i do and what can i not do, to still be able to receive ota updates?
As long as you're running CM11S you'll still be able to receive OTA updates. You can have an unlocked bootloader, you can have TWRP recovery installed. The only thing you can't do is have modified/removed system files, or Xposed Framework. If you do have Xposed Framework it's as simple as deactivating it before installing an update.
Transmitted via Bacon
What about root and custom kernel?Can i still install the OTA ?(CM11S here)
Yes you can. You'll lose root but it's as easy as flashing SuperSU again after the update.
Transmitted via Bacon
cool! ive also herd as long as your on of the supported oneplus roms aka color os or others you will still receive ota?
shael said:
cool! ive also herd as long as your on of the supported oneplus roms aka color os or others you will still receive ota?
Click to expand...
Click to collapse
Yes but OTA's will be here in xda so no need to be on a stock rom with less features if you dont want to be. We have developers here that will prepare the OTA and have it flash-able for you within hours of it coming out. Remember most OTA's are done in stages so you may not have it right away.
our developers are great but they wont have android L within 90 days of launch lol
shael said:
our developers are great but they wont have android L within 90 days of launch lol
Click to expand...
Click to collapse
Where are you getting this information?? Devs usually have ROMs within a week.
Transmitted via Bacon
Related
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Is there a new update? post/after asa14?
Checked around but after seeing the old do this if you cant upgrade threads pop up I was curious.
Seen some traces of the 9.8.2Q JellyBean update for the Q, but don't know it's current status.
Interesting and good news, Just checked and mine stated not update available sadly..
Gxkon said:
I just got a notification on my phone about a new moto software update. Will it make it harder for my to flash, root, or mod my phone?
Everything is still stock on the phone i havent done any mods yet
Click to expand...
Click to collapse
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
swintec said:
Can you share what this update is, OP? The small update from last month or is this Jelly Bean?
Click to expand...
Click to collapse
I dont know it dont look like a new os. One was around 60 mb then i had a small 7 mb update
arrrghhh said:
The official bootloader unlock should work regardless, so no if you don't mind doing the official unlock method.
I've heard the exploit to get root without the official unlock has been closed, but I think someone else said they found a way around it. I don't know either way, I officially unlocked the device the day I got it
Click to expand...
Click to collapse
Yeah, the motofail2go exploit to root works only if you haven't updated. After rooting, you can save root by Voodoo OTA rootkeeper, temp unroot, install any updates, then restore root with OTA rootkeeper. Works great, and you keep your warranty. But of course you can't flash any ROMs or anything, but you can still use Titanium backup, other programs that require root.
see this thread:
http://forum.xda-developers.com/showthread.php?t=2053444
Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards
Pihkal said:
Hi guys,
I was wondering if rooting the phone interferes with the ability to receive OTA's?
I know OTA doesn't work with most other devices after rooting but I'm hoping it works with the OnePlus One as it comes with CM as stock rom...
Thanks!
Regards
Click to expand...
Click to collapse
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.
jtchinoy said:
Just got my Oneplus today. My experience through 4 updates is that SuperSU gets uninstalled, which unroots your phone. You just need to boot into TWRP and reflash SuperSU after the updates and you're rooted again.
Click to expand...
Click to collapse
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!
Pihkal said:
As long as it installs the OTA I'm fine with reflashing SuperSU.
And judging from your reply TWRP also doesn't interfere with installing the OTA, great! :good:
Guess I'll be unlocking my bootloader (and having my phone wiped, damned) and rooting it.
Can't live without the Xposed Framework. :laugh:
Thanks!
Click to expand...
Click to collapse
could of searched and found the answer... question has been asked quite a few times. also there is a setting in SuperSu to keep root in upgrades. Either way OTA or just wait for a rooted version which you probably would get faster than OTA in most cases
https://forums.oneplus.net/threads/persistent-root-after-ota.49868/
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-t2848715
http://forum.xda-developers.com/oneplus-one/help/ota-updates-root-unlock-t2873263
http://forum.xda-developers.com/oneplus-one/help/to-root-stay-stock-getting-ota-s-t2809334
http://www.reddit.com/r/oneplus/comments/2eyf2t/ota_after_root/
and there's more......
I By now everyone must be aware that Lollipop has a new way of checking for system mods that will prevent rooted devices from taking OTAs. Has anyone thought through what the easiest and best procedure will be for updating the firmware going forward? I've applied the lollipop OTA but have been holding back on root until I have a firm hold on how updates will work. I feel there must be many less technical people out there with the same concerns.
From Android Police:
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change has to do with verified boot, which was first introduced in KitKat. Even though Google has yet to enable this feature on a Nexus device, this move seems to indicate that the company could be preparing to go that route in the future.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Also here's chain fire....
http://forum.xda-developers.com/showthread.php?p=36316945
Does it matter when we have access to the factory images?
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
That's not at all what I'm reading. I'll post links later when I get home
Edit: see updated OP
/facepalm
I wrote a thread about other ways to update. Its in my signature
[Deleted]
DamnItLukasz said:
I don't know what that link says but thats not true lolz
Rooted and I got the OTA 3 days ago, just flashed stock 4.4.4 kernel over ElementalX et voilá.
Click to expand...
Click to collapse
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat. Or maybe it wasn't lollipop but to my knowledge there hasn't been an OTA yet released that updates lollipop
NCguy said:
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat.
Click to expand...
Click to collapse
Ups, forgive me then
Altrezia said:
Does it matter when we have access to the factory images?
Click to expand...
Click to collapse
For the less skilled hacker who doesn't want to wipe it requires more knowledge, more risk and more reliance on modified OTAs, and 3rd party stock builds. Otherwise they're into dirty flashing and that requires more skill and knowledge.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
I'll have a look, thanks. That's really what I was hoping this thread would be about since it looks like plain OTAs may be out.
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
please read updated OP
NCguy said:
please read updated OP
Click to expand...
Click to collapse
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
EddyOS said:
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
Click to expand...
Click to collapse
It mentions the N9 only because it was the first 5.0 device that was officially released.
I mentioned before this problem is going to exist for updates to devices that already have lollipop, not for those updating from kitkat to lollipop.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
NCguy said:
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
Click to expand...
Click to collapse
I haven't read it yet to be honest. I'm not an OTA fan, so I don't spend much time reading up on it. I will though, at some point and update the thread. There is also an OTA help-desk thread but I haven't read that yet. Apparently latest OTA doesn't work with custom recovery either
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
cell2011 said:
Am i not getting OTA of 6.0 cause my bootloader is unlocked or is 6.0 not out yet for OTA? I know the images are i just want the OTA and ill wait for it or is unlocked BL keeping me from getting the OTA?
Click to expand...
Click to collapse
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Pretoriano80 said:
No, it's not because the bootloader is unlocked.OTA are sent in "waves" so the servers won't get overwhelmed.So it's just a matter of time until you will gey it too.
Click to expand...
Click to collapse
Great ty what if phone was rooted would that stop OTA`s? Just curious im not rooted. Is the OTA suppose to be released with Gapps included do you know? There are an awful lot of people not being able to recieve gapps the right way. I hear location doesnt work and some other stuff but maybe thats a handful of people
I don't think the root prevent a device receiving the OTA,but it might cause the OTA installation to fail,so it's always best to disable root before updating.
I didn't used the OTA to update my device,so I can't say if there's any issue with it,but I know people that updated via OTA and it was all fine.
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
The Joke(r) said:
I have a rooted device with twrp recovery. Despite of what people think, I get this update. I just replace twrp recovery to stock and flash . This is amaze me. In general, my location also doesn't work also. There is solution?
Click to expand...
Click to collapse
That seems to be a major bug there are so many talking about location not working or its in another place in settings. Not sure where cause i dont have my phone right now. Im sure there will be a workaround soon
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
You won't be able to update while rooted. Actually updating with a factory image is probably safer than taking an ota update. Personally, I think the update is worth it.
Sent from my SM-T530NU using XDA-Developers mobile app
hexr96 said:
Hello everyone,
Back in October, I had rooted my phone to install xposed etc. A little after that I received a notification for the stagefright update (i know that was a long time ago) and I ignored it (because of little time, I wanted to install cm13 but I never could find the time). Since marshmallow is a little more stable than lollipop, I would now like to shift to MM.
I distinctly remember trying to install the stagefright update (after rooting lollipop), and my phone went into a bootloop.
Two questions,
1. Does rooting not allow you to update your phone? Does it cause bootloop problems?
2. I want to stick to stock, so should I download the stock images? I'll be losing a lot of my data, I'll back it up but some of it is bound to get lost. Is it worth it?
Thanks in advance
Click to expand...
Click to collapse
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
acejavelin said:
Your presumption that Marshmallow is more stable than Lollipop is... well... many people would argue that the opposite was true.
You should never take an update after rooting, especially if you have custom recovery installed... OTA's are designed strictly for purely stock, unmodified phones.
At this point flashing the factory images is preferred, you do this from a PC not the phone though. You could try to unroot (SuperSU has a full unroot option in it's settings), but the real key is to restore your stock recovery, there are threads here to show you how to do that.
Click to expand...
Click to collapse
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Tel864 said:
Many would also argue that it is more stable.
Sent from my SM-T530NU using XDA-Developers mobile app
Click to expand...
Click to collapse
Perhaps stability is not the real argument here... both are stable, as are most production ROMs, I have been using Marshmallow since early December and never had any real problems. But there are pros and cons to both and depending on your situation one may be better than the other, but I guess that wasn't really the point of this thread so I will say I half agree with your statement.
I would also have to relock the bootloader, correct?
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
No
hexr96 said:
I would also have to relock the bootloader, correct?
Click to expand...
Click to collapse
Nope, in fact, you can't relock the bootloader even if you want to. The bootloader lock state is not relevant to taking an OTA.
Thank you everyone