Related
Does having my bootloader unlocked affect getting updates? I have no interest in installing custom roms(for now), and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games. Figured I'd just unlock and root. I didn't plan on installing cwm so I could still get updates straight from google. I know an update would just overwrite root, but not sure if the bootloader would affect it. My galaxy nexus I always installed custom roms so I don't know how the bootloader affected OTA's. thanks guys.
In principle it should not affect updates.
Have a look at a prior OTA update's installer script
./META-INF/com/Google/android/updater-script
The OTAs perform binary patching on individual files, one by one. (That is why OTAs can be so small.) Before they perform the patching, a checksum is performed on every file on the tab/phone targeted for patching. If even one of those checksums fail, the entire install is aborted.
In addition the version of the recovery is sometimes checked, too - so merely having a custom recovery can trip up an OTA if that type of assert() check is performed.
To put that in general terms, you could say that an OTA update will almost always succeed if you merely add things to a ROM and leave the stock recovery in place.
If you want to flash stuff without altering the stock recovery just use a soft boot of a custom recovery, e.g. "fastboot boot custom-recovery-image-file.img"
If an OTA fails, don't get scared - you can simply unpack it, modify the updater-script file to remove the failing assert(), re-zip it and flash it. This would need to be done with a custom recovery, though as the modified OTA would no longer be correctly signed.
HTH
Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Sent from my Nexus 7 using Tapatalk 2
BrianDigital said:
Yes but don't remove any of the Google apps that come preinstalled, don't edit the build prop, and that might be it.
Click to expand...
Click to collapse
yep.
The most recent OTA had the boot image file as one of its patching targets, so it was also subject to checksum verification during the initial assert() sequence of "updater-script".
I guess that means that if you hook anything into the boot sequence that needs to be in the ramdisk, that will trip up the OTA, as it is pretty typical for OTA updates to diddle the kernel or ramdisk. I guess that if you want to stay on a near-factory base distro including new ota updates, that puts the onus on you to either
(a) check the installers of the stuff you flash to make sure the boot image is not being re-packed -or-
(b) maintain a chain of pure stock backup sequences: then you can then restore them, run the OTA patch kit on them, make a new nandroid backup, and re-run your custom flashes. Probably use TiB to restore your apps on top of that, too. Almost like an OS re-install sequence, frankly.
cheers
thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.
tu3218 said:
thanks guys! Does an update from google relock the bootloader? I'm guessing not since its a nexus and they're okay with us unlocking it but just wondering. Just trying to decide if its worth it. I feel myself using my nexus 7 less cause of the latest update. It's smooth once its running but turning the screen on after its been sitting, it take some time to get together.
Click to expand...
Click to collapse
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.
bftb0 said:
Whoops (old timers disease) I said "bootloader" in that post above where I should have said "boot partition" or "boot image". (Now corrected.)
Updates typically don't touch the bootloaders. Interesting question though - if you replace a bootloader via fastboot, does it change the lock status? To that Q I don't know the answer from direct experience.
Maybe I'll give it a try. Ugh that's gonna be a lot of backup/restore ops.
In the meantime, have you seen a page with links to (older) *full* ROM install bundles that Google no longer has on their site? I only got a N7 in early Jan '13, so I don't have any of those older full-ROM+bootloader fastboot-based install bundles.
Click to expand...
Click to collapse
Nah I haven't seen that. To be honest I've been so busy with flashing roms on my sgs3. I finally have settled down on a rom for my phone so I figured I'd give my nexus 7 a go. But I'd rather not be performing the whole backing up/flashing/modding on both. Its so much lol Plus my tablet I need to be dependable when I need it. That's why I hadn't planned on running roms, just basic root for blocking ads, etc. Before the last update this thing was so fast and enjoyable to use. It still is but its not to where it use to be. I was going to go back but I don't like knowing I'm not on the latest.
and mainly just want root to block ads, install seeder to fix this damn lag, and possibly connect a ps3 controller to play games.
Click to expand...
Click to collapse
Seeder doesn't fix lag. Doesn't work. If your n7 is lagging then there is another cause.
Sent from my Nexus 7 using Tapatalk HD
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
DougYITBOS said:
Hey folks.
I attempted to ask this in the most relevant thread, but as a new user I can not.
My question pertains to the CASUAL root tool for the S4.
Developed by AdamOutler.
Described in the thread "[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release"
The tool looks pretty amazing.
But I do have some questions.
Please forgive me in advance I am an UBER NEWBIE.
Many of the terms thrown around here are completely foreign to me.
(Yes, I've searched for that knowledge - but perhaps you are underestimating my noobness. )
(Yes, I have read the "[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]" thread as well... it helped but... yeah still a noob.)
FYI: The only reason I want to root my S4 (AT&T) is so I can remove the crappy bloatware, and also configure the anti-theft/find-phone features of the avast! app.
Ok so on to the questions...
1) Once this is done what's to stop some update from my carrier un-doing it all?
2) If that were to happen how much pain would I be in for?
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
5) This "Nandroid" is another backup tool?
Am I correct in my understanding that the TWRP leverages nandroid - or are they comepeting solutions.
6) Is Nandroid a system function or some other tool that needs installed?
Thanks a bunch folks!
~Doug
Click to expand...
Click to collapse
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Thanks a bunch TheAxman
You said...
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
Click to expand...
Click to collapse
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
DougYITBOS said:
Thanks a bunch TheAxman
You said...
So does the Root tool (in this case the CASUL script by Adam) do something to shut down carrier updates or I need to do something extra?
Also if one were to ODIN back to stock... and get an update... and then re-root...
I assume you could get an old backup from an external storage area and try to get all your "stuff" back?
Click to expand...
Click to collapse
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
And btw, if this person xBeerdroiDx gives me a thanks, he is saying I did ok... If you seem to have anymore questions, his guide is one of the best....
[HOW-TO] The All-In-One Root/Backup/Flash Guide - [I337 & I337M]
http://forum.xda-developers.com/show....php?t=2314494
Thanks to xBeerdroiDx - For this great Startup Guide
Thanks again!
DougYITBOS said:
Thanks again!
Click to expand...
Click to collapse
Your quite welcome, if you have any other questions, feel free to ask them in the thread I gave you or mine.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
btw..this is cool, name please.
Dog: [Pitbull Sharpei Mix] Rom: Stock
TheAxman said:
hehe it could, but highly unlikely, and if you feel that it may happen, do what I do, remove the sim until you get rooted, and then put the sim back in and complete the setup. Your not going to get calls in that time period anyways.
Good luck.
Click to expand...
Click to collapse
ah good idea. i suppose airplane mode would accomplish the same thing as well
orlandoxpolice said:
Sorry to hijack the thread, but I figured Axman may know.
In the past on my S2, I would flash a lot of roms. maybe after every 5 or 10 I would odin back to stock, boot it up, re-root, re-twrp, then flash another rom. just to get a very clean slate in a sense.
If I were to do this with the S4, you dont think the ATT update would get pushed in the 30 mins to an hour that the phone is in its stock state, do you? I dont want to get mf3'd.
Click to expand...
Click to collapse
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
CamFlawless said:
I'm just throwing my limited experience out. I have never went back to stock via Odin simply to get a "clean slate." Completing a full wipe including a system format in recovery will be sufficient for a clean OS. I would reserve Odin flashing as a last resort for when problems aren't being remedied by a full wipe and format via recovery.
Click to expand...
Click to collapse
Thank you sir, appreciate the help, and yes, good idea.
TheAxman said:
Thank you sir, appreciate the help, and yes, good idea.
Click to expand...
Click to collapse
might have been a placebo effect for me, lol.
TheAxman said:
1) Once this is done what's to stop some update from my carrier un-doing it all?
If you root you will not be able to get updates any longer.
2) If that were to happen how much pain would I be in for?
Its not going to happen because you are rooted.
3) If the only way to protect one's self from this is to somehow disable OS/firmware updates... is the only way to get future OS updates through a ROM?
The only way you will get updates is ODIN back to stock. Again, no worries.
4) This TWRP thing seems to be a backup/recovery tool?
I gather that it also enable ROMs flashing, etc?
I've read others like "Titanium Backup" because it can freeze/remove the bloatware.
Are they both kinda the same thing?
Will the two conflict?
TWRP - is a recovery, so you can perform nandroid backups, and to flash roms, and to restore backups. Nothing more, nothing less.
Titanium Backup is a app you use within the rom, to backup and restore apps with, you can read more on this going to the market, it will explain this app's features and what it does.
They are not the same, 2 different programs, that do 2 different things.
Question 5 & 6 answered in #4 answer.
Hope this helps, kinda down and dirty, try and do some reading on all of the above.
Appreciate the thanks.
Thank you and good luck.
Click to expand...
Click to collapse
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
lilbigdude1 said:
Correct me if I'm wrong, but its my understanding if you're rooted and still stock the MDL will still update to MF3 unless you either completely flash a custom ROM or rename the OTA files that At&t have on our devices.
where you end up, depends on where you start.
AT&T SGH-I337 32G
Click to expand...
Click to collapse
somewhat, but as soon as you root, your phone status is custom correct? therefor how can it update? Yes, it is better to do a custom rom, but you can still stay on MDL and never get updates, freezing the samsung update will work, but I gave the easiest way in his situation.
TheAxman said:
Once you root,, it changes the rom status to custom, so the update see's that and does NOTHING. if you odin back to stock, un-root, you can force updates, but be careful with updates, carriers are patching things so we can not do what we do, and that is to run custom roms on phones THAT WE OWN!
Click to expand...
Click to collapse
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
texasniteowl said:
Hi...I'm another noob with a question about this. I also just used CASUAL to root my phone yesterday. I am definitely rooted but my Device Status actually still shows Official. Following the info in another thread, I used ES File Explorer's Root Manager to rename the wssyncmldm.apk.
Info from: http://forum.xda-developers.com/showthread.php?t=2268946
The thread was actually written for a previous update, but renaming the apk should still be relevant.
Maybe this was overkill, but...
Click to expand...
Click to collapse
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
TheAxman said:
I was just rooted and it showed custom status after, so no updates, you must check the status. just flashing a kernel will change the status, if you are going to root and install a recovery, some things are to go without saying.
Btw, I have learned, that nothing with information is an overkill, if you haven't notice xda is a bunch of peoples ideas and such, and many do not work for others, it is a hit miss.
Click to expand...
Click to collapse
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
texasniteowl said:
Yeah...maybe I am referring to the wrong thing, but I was surprised that Settings > More > About Device > Status > Device Status still said "Official" on mine. I know CASUAL succeeded. TWRP is installed, SuperUser is installed. And I was able to use ES File Explorer's Root Manager to change system to R/W and rename the apk. So even though I'm very much an android novice, I'm pretty certain I'm rooted. I don't necessarily plan to flash a rom yet...but since I was still on MDL I wanted to retain the current ability to do so!
Is there some other place that it would show Custom as opposed to Official? That's actually why I went ahead and renamed that file.
Click to expand...
Click to collapse
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
TheAxman said:
I did not mean to confuse anyone. Yes you did the right thing by renaming the the file. if your device says official then this step is needed. mine said custom. umm i stand corrected fellows..another step is needed. thanks for the oversight. i am only human..im not a animal.
Click to expand...
Click to collapse
if you are paranoid then there are 3 files you can freeze. i cant remember which ones, but one is att update something something, thats all i can remember.
im no help
I think everyone gets the picture.
Sent from my GT-I9505 using xda premium
Does omni come with root or do you have to root it yourself?
SHAWDAH said:
Does omni come with root or do you have to root it yourself?
Click to expand...
Click to collapse
Right now, you need to flash SuperSU.
We plan on an integrated root solution down the line, but it hasn't been a high priority.
Why?
To flash Omni, you need a custom recovery that can flash unsigned packages
If you have a custom recovery that can flash unsigned patches, it takes 10-20 seconds to flash SuperSU.
The one issue is that right now, flashing Omni will clobber SuperSU - I've got a "temporary workarounds" thread (using backuptool) for ways around this issue until we fix it properly. Look around for it.
Entropy512 said:
Right now, you need to flash SuperSU.
We plan on an integrated root solution down the line, but it hasn't been a high priority.
Why?
To flash Omni, you need a custom recovery that can flash unsigned packages
If you have a custom recovery that can flash unsigned patches, it takes 10-20 seconds to flash SuperSU.
The one issue is that right now, flashing Omni will clobber SuperSU - I've got a "temporary workarounds" thread (using backuptool) for ways around this issue until we fix it properly. Look around for it.
Click to expand...
Click to collapse
Wouldn't want to include SuperSU in omni, its proprietary. Superuser is much better.
SHAWDAH said:
Wouldn't want to include SuperSU in omni, its proprietary. Superuser is much better.
Click to expand...
Click to collapse
Work is being done on changing that.
Other than the proprietary vs. not - SuperSU is far better. Remove the proprietary issue and the choice is obvious.
Since chainfire is one of the founders of omni... using supersu wont hurt that much..or will it?
Entropy512 said:
Work is being done on changing that.
Other than the proprietary vs. not - SuperSU is far better. Remove the proprietary issue and the choice is obvious.
Click to expand...
Click to collapse
Is that a hint towards chainfire making supersu open source? It is a lot better.
Entropy512 said:
Work is being done on changing that.
Other than the proprietary vs. not - SuperSU is far better. Remove the proprietary issue and the choice is obvious.
Click to expand...
Click to collapse
Honest question, if you remove the authors of the respective apps, what makes SuperSU better? I've never really felt a difference between any of them (including even the original old Superuser app) and IMO Koush's SuperUser has a better UI (partly due to the integration into settings).
I just hope that decisions are not being made emotionally about things like this, because overall I am very much in favor of the principles behind Omni, but I hope that any animosity between groups/people fades over time.
SuperSU has much better control over notification settings. e.g. I can hide the annoying toasts from BBS every time I unplug.
Ah, that's actually a really good point, those toasts are indeed very annoying.
In Koush's SuperUser you can disable toasts too, hit the menu key when in supersuser to access settings, it's at the bottom in settings.
Almite said:
In Koush's SuperUser you can disable toasts too, hit the menu key when in supersuser to access settings, it's at the bottom in settings.
Click to expand...
Click to collapse
Must be new, didn't exist last time I used it.
iofthestorm said:
Honest question, if you remove the authors of the respective apps, what makes SuperSU better? I've never really felt a difference between any of them (including even the original old Superuser app) and IMO Koush's SuperUser has a better UI (partly due to the integration into settings).
I just hope that decisions are not being made emotionally about things like this, because overall I am very much in favor of the principles behind Omni, but I hope that any animosity between groups/people fades over time.
Click to expand...
Click to collapse
I have tried and tried and tried to get that integration to work with OmniROM. There's some fairly deep incompatibility going on. I'dj ust wait for SuperSu
Hello everyone,
My Moto X Pure edition is on the way on the mail. I'm already excited to root it and get twrp on it. However, I believe the phone will come with android lollipop installed, and I should get an option for an OTA update for android 6.0.
My question is: Should I root my phone and install twrp BEFORE receiving the update, or after? I plan to use WinDroid Toolkit to root my phone and install twrp (seems to be the easiest way) so have any of you done it while having 6.0 already installed?
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
quakeaz said:
Your phone will most likely arrive with 6.0 pre-installed on it. You can't take an OTA with TWRP installed. I can't answer the WinDroid question.
Edit: It will most likely come with 6.0 already assuming you purchased it from Motorola.
Click to expand...
Click to collapse
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Henryy97 said:
Thanks a lot for your help! It's good that the phone will most likely come with MM. Does Motorola also offer an OTA update to 6.0.1?
I wanted to flash a pre-rooted stock-based ROM because I thought it would be easier to get root. Although, my preference really would be to get the stock update, then just root that. The only reason I wanted to flash an already rooted ROM was because it seems kind of tricky to root it haha. Is the systemless root by ivcarlos the easiest way to root MM? Or have you perhaps found another way to root it on MM?
Additionally, just to make sure before I go on with anything: I should first let the clean phone upgrade to android 6.0.1, AFTER that I should unlock the bootloader, followed by installing TWRP and root, correct? @vertigo_2_20
Thank you for any help you can give me!
Click to expand...
Click to collapse
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
vertigo_2_20 said:
IIRC, that's how I did it (OTA 6.0.1 > unlock bootloader > flash TWRP > root), though I did miss some things along the way that I only found out about after the fact, so I've included warnings about those thing here. Before I rooted, I read the following (and a LOT more, but these are the primary ones I based how I did it on):
ivcarlos' method, which you mentioned
And this, which is what I followed for rooting, though I don't remember why. I also had to use 2.62-3 as mentioned in the instructions vs 2.65 which is mentioned at the end as verified working, since it didn't work for me.
I ran across this as well, probably when 2.65 didn't work, and there's some good tidbits in there, worth reading through.
I also found this, but only after I finished rooting with the other method, and I didn't have the time to mess with it. I don't know enough to say whether it's really a better method or not, but something worth checking out if you have the time.
Just make sure you backup anything you want to keep (phone log, texts, pictures, etc) before unlocking the bootloader. I recommend SMS Backup & Restore with Titanium Backup as a secondary backup. Then, use fastboot to back up your recovery before flashing TWRP (I didn't know to do this until too late). Also, make sure you back up your /system and /boot partitions (don't need /data, since you're dealing with a freshly wiped phone from unlocking the bootloader, so nothing there to back up) with TWRP (and store the backups on the external SD card and/or your computer) as soon as you get TWRP flashed, before you do anything else.
Remember, anything you do that modifies /system can potentially break the "systemless" aspect of this root, thereby breaking Android Pay as well as the ability to receive OTA updates. Examples of things that might do this are AdAway (there's apparently a systemless file that needs to be flashed before installing it, which I didn't realize until too late, so mine may be broken already) and battery apps like GSam and BetterBatteryStats. I've yet to get an answer on if these really do break it, though. One that definitely will is Xposed, but I just found there's a systemless version, so when I get time I plan on trying that out. I think even if you do break it you can just a) reflash your backup (/recovery, /boot, & /system) then take an OTA and reflash TWRP and re-root, or b) flash the updated partitions from the OTA then reflash recovery and re-root. Of course, any of those things that changed /system (AdAway, Xposed, battery apps, etc), will probably be broken by this, and I believe they're supposed to be uninstalled first and reinstalled after.
I wouldn't doubt if I've screwed something up, so hopefully somebody can correct me on anything I did, as well as provide more information regarding the breaking of systemless.
Click to expand...
Click to collapse
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Henryy97 said:
Thank you for your reply! I'll read the links you sent me, although from what I can see the "root done right" is for the nexus 6, and if it works for the moto x pure it doesn't seem to be overall that much beneficial over the systemless root.
What exactly is the effect of breaking the "systemless" aspect of the root? For example, if I install AdAway, what will happen? I didn't really get that from your post.
Perhaps after all this process, I'll write a how-to guide, heh
So according to your experience, SUPERSU 2.62-3 is the adequate version to use for android 6.0.1?
Thanks again!
Click to expand...
Click to collapse
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
vertigo_2_20 said:
My understanding is that breaking it will render Android Pay inoperable and will make it so you can't take an OTA, though as I mentioned, it seems you still can by reverting back, it's just a LOT more work. But again, as I said, I'm not completely sure and I haven't been able to get an answer.
As for the supersu version, it doesn't really matter, because you'll just update it once you're rooted and booted into the OS. I just found that, despite what that post said, 2.65 did not work for me, so I had to flash 2.62-3 which did. Not a big deal, was just a little frustrating and scary when 2.65 didn't work because I was worried that I broke something and that the method wasn't going to work.
Edit: Good catch BTW on the link having to do with the Nexus. I didn't even look at what sub-forum it was in. At least it's one less thing to worry about for now, though I do hope it spreads to more devices, because we could always use more, not to mention better (assuming it is) ways of doing things.
Click to expand...
Click to collapse
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Henryy97 said:
Thanks. I am aware that you can revert back to lollipop, and do the update from there whenever you want to update to a newer OTA MM update. However, my real question is, what does it mean to break the systemless aspect? I know that it will prevent further OTA updates, but will xposed work as it should, etc? If I am rooting my device, it's really to get xposed. So, if it means that I must revert to an unrooted stock rom everytime I wanna update, then so be it. I just want to make sure that breaking the systemless root aspect will not make the ROM unstable. Will it?
Click to expand...
Click to collapse
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
vertigo_2_20 said:
I think you'll find all the info you're looking for and more in those links. But in summary, as I said, AFAIK the only consequence is breaking OTAs. It does not prevent you from using xposed, rather xposed is one of the things that breaks it. Systemless is so called because it roots without affecting the /system partition, therefore preventing the breaking of Android Pay and allowing OTAs. Once /system is modified (unclear if at all or just beyond a point), these two will no longer function. So if you "break" the systemless root by doing stuff that modifies /system (i.e. xposed, etc), you basically now have a standard (non-systemless) root, which simply negates the benefits it provides. But as far as I could tell, systemless is the only option anyway, so you just do it since it works and it's easy, then you either are careful not to break it if Pay/OTAs are important to you, or if you don't care about those then you just do whatever you want just as if you were rooted in the traditional way. But as I said, once I get the time, I plan to try out the systemless xposed, though it may not matter since I might have already broken it, but may as well, and maybe it'll mean not having to uninstall it when it comes time to take an OTA. If you play with it and figure it out, let me know.
Click to expand...
Click to collapse
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
I bought my phone ~5-6 months ago. When I got it, the MM update was waiting (released late last year). Probably ~2 months later, another update came through. Since then, nothing. So it looks like probably 3 maybe 4 a year. I'd rather be rooted with all the benefits than get a small update, though I'd really rather have both.
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
lafester said:
6.0.1 is not out yet although there is a reteu version posted which works great. Rooting is as simple flashing su 2.62-3 with twrp.
Click to expand...
Click to collapse
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
I assumed I was on 6.0.1 because I received a system update after being on MM, so I don't know what else it could be. Though it does just say 6.0 in settings. Regardless, I only did it a few weeks ago, so if you're fully updated, you'll be the same as what I was. Even if not, I would think it wouldn't matter. As long as you do a back up before messing with things, worse case scenario is you screw something up and restore the backup.
Henryy97 said:
I'll check it out. Do you mind sharing the link to that version just in case? I am very confused now though, because @vertigo_2_20 says he has 6.0.1, and you say you didn't get it. Perhaps location matters? Can you elaborate a little bit more?
And actually, I've just realized: I think I was looking at too many outdated posts perhaps with all the complicated root procedures such as the one by ivcarlos. The guide that amit.lohar made is very simple which is the one vertigo kindly shared in this OP. One final question @vertigo_2_20 (sorry for so many questions). Does the method by amit.lohar work for 6.0 anddd 6.0.1? I would assume so since they're pretty much very similar. What is your take on this?
Click to expand...
Click to collapse
No I don't get links for people... this forum is small and easy to read. Dev section has one pre loaded with franken and there are two threads in general.
Henryy97 said:
Once again, thanks. I reached the limit of thanks I can give for today, haha. I'm reading up much more on the process, etc. Just one final question, how often do the OTA updates come on average? I always like having the latest software installed, so MAYBE I can consider having an unrooted phone.. although that will be very difficult. I love my xposed. Anyway, I guess if updates only come about once a month, then rooting is fine. Not too much of a loss. I will definitely be making a how-to guide once I'm done with all of this! (and once my device arrives)
Click to expand...
Click to collapse
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
That reminds me of another thing I haven't yet figured out. If /system is modified, I'm assuming the OTA will still show up and just won't install, but I wonder if it won't even show up anymore. Anyone know?
aybarrap1 said:
If receiving the OTA updates is something you really want, systemless root will allow you to get them with a lot less effort. The trick is knowing which of the apps that require root privileges will end up modifying your system. Avoid the ones that will and you can enjoy root with less work to get updates. If the only root required apps you are interested in modifies the system, then it will be a matter of what you value more.
Sent from my awesome phone!
Click to expand...
Click to collapse
Ahhh! I guess I'll just flash ROMS to update my phone then because I need my xposed Besides, after 6.0, if we want root, we can only get the systemless one anyway, right?
Also, I did not quite understand something about systemless root. If the root is 'systemless', then how can apps still edit the system? I've read up that after a memory wipe, the root will actually go away but what happens if I have apps that already modified the system? I just don't quite get how the apps can get into the system and modify it, if the root itself cannot do that because it is systemless. Am I getting the wrong idea here? I've read, and read, and read. I can't find an answer to that :/ According to what you have said though, if I were to get an app that modifies the system, then it would essentially *break* the systemless aspect of it, right? Therefore, it just becomes a normal root?
I feel like I'm going in circles now so I hope someone will be able to explain this for me or just point me in the right direction!
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
vertigo_2_20 said:
Systemless root does not mean root doesn't have access to /system, it simply means a way of gaining root access without modifying the /system partition, because if you gain root with the old methods, which DO modify /system, it breaks Android Pay and OTAs. Root still has access to modify system, hence why you have to be careful in installing apps, xposed, etc, because if they have root access, they can modify it, and if they do, your systemless root just became useless. The whole point is to NOT modify it so as to keep those certain functions intact, but it doesn't prevent you from doing so after gaining root.
Click to expand...
Click to collapse
My experience was rooting 5.1.1 on the new phone. I backed up at every stage. I tried a few roms, no big deal. I liked 5.1.1 better due to micro sd card usage. I stupidly allowed the OTA to attempt to install. I knew it would fail but hoped it would stop nagging. The result I did not expect was phone continually rebooting on its own, trying to complete the update. After it completed the reboot it would start to shut down and begin the reboot process again. I restored a backup and froze the Motorola Update app with Titanium Backup. Problem solved. Don't do what I did!
Why would you want to stay on L? M is so much better. Between Doze and permission control, you'll have better battery life and more privacy and security. Not to mention the increased security from having more up-to-date software. I'd recommend just taking the update.
Or do I need FlashFire?
I believe that this is the same update as the one in this post
https://forum.xda-developers.com/moto-x-style/general/maintenance-release-dec-2016-security-t3557903
You need full unroot, stock kernel, stock recovery and no system partition modification
lukas77 said:
You need full unroot, stock kernel, stock recovery and no system partition modification
Click to expand...
Click to collapse
could you tell me how I can do this? Is there a general guide?
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
acejavelin said:
Wow... how many times are we going to answer this question every single time an update comes out?!?!
A phone must be 100% stock to take an OTA... stock recovery, stock system partition, stock boot partition... or the update will fail.
You need to either restore your pre-root backup (you did one with TWRP, right?) or flash a factory image that is the same version or newer than you have installed. Period, those are the proper answers to how to go back to stock so you can get an OTA.
Click to expand...
Click to collapse
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
ThanuTK said:
I apologize, this was my first time rooting my phone so I don't know a lot. I was able to root my phone, thanks to your thread on rooting.
I plan on using this thread by you to go back to stock.
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
Click to expand...
Click to collapse
I hope it helps... Just remember to search around the forums or Google a bit before asking a question. I apologise if I sounded a little snappy, I had just answered some very dumb PM's that frustrated me and then this was the first open thread I saw, sorry if I was a bit abrupt.
This question has been answered a whole lot so it gets a little frustrating sometimes to see a new thread pop up for this issue. That being said and you being new to rooting, I can't stress this enough: please search and read through the threads (and know the XDA rules of course). This device has been out for a while and by now, a large majority of the questions, issues, and whatever else you may have is addressed in these forums. If you do run across anything that there is no answer for, by all means ask away.
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Suri149 said:
Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible
Click to expand...
Click to collapse
Possible? Yes, but it isn't likely and I certainly don't expect it to happen. Lenovo has shown no interest in updating the Pure/Style to support Jio, or even fixing the current VoLTE issues on supported carriers for that matter.
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
ThanuTK said:
Hey could you also tell me how important the android security updates are? are they critical ? without it would my phone be vulnerable?
Click to expand...
Click to collapse
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
My thoughts exactly on the security updates. The only "evidence" I have heard about has been a couple of individuals who do not appear to understand why an app from some unknown source or dodgy websites along with crazy permission requirements might infect their phone. I acknowledge this as a human exploit though and not on the part of Android.
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
roaming4gnome said:
If I make current twrp backup, wipe, restore original Stock unrooted twrp backup, flash Stock recovery, take ota, reflash twrp and restore only data from the backup in first step would that essentially preserve user apps/data? Otherwise I will just freeze Moto update apk and wait for 7.0 to full wipe.
Update: Nm, I guess at that point without restoring system to preserve settings I may as well just use Titanium Backup :silly:
Click to expand...
Click to collapse
Dahenjo said:
I'm rooted and using Xposed, but got the Dec update using a completely stock TWRP backup of system and boot posted here. Afterwards I simply had to reroot and reinstall my Xposed framework in TWRP, but all my modules which were still installed worked and maintained their settings. Couple of other minor cosmetic things I had to redo, but for me this worked very well without having to fully return to stock and reinstall everything from scratch. YMMV, and also do your own TWRP backup first just in case.
Click to expand...
Click to collapse
This is actually a valid way of doing it, but with so many variables to the state of your device prior to doing this the possible outcomes vary a lot.
But @Dahenjo has pretty much the proper procedure... if I was going to try it I'd do it that way... backup, restore stock, take OTA, reroot, reflash Xposed, restore user data... 99% of everything should be intact.
acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
Real good explanation. Good balance of technological and practical
Sent from my iPhone using Tapatalk Pro
acejavelin said:
Well on this I have a pretty strong opinion, and it isn't always well liked... I work in the IT industry with networks, so security is kind of a big deal to me... but Android security updates are essentially worthless, and are only a marketing ploy to make the company look better.
For example, lets look at some major vulnerabilities that have supposedly affected MILLIONS of Android devices... Dirty Cow is a good one, I am in a group here on XDA that is trying to use this vulnerability for something, anything really, but mainly for rooting difficult devices, and in a modern device it is almost impossible because of all the other parts of Android that help keep it secure like DM-verity and SELinux, end result is no usable exploit in almost all cases, although we have some results in cases where we are in complete control of the device with hands on adb access, but even then it is very rare and device specific, not something that you could just download a random malware app and have it affect you, I would need the device in hand. Then there are the terrible ones like Quadrooter, Stagefright, and Towelroot that affected millions, no tens of millions of devices, but have you ever heard of anyone being actually effected by a real exploit of that vulnerability? Nope, me neither, because for the most part these have only been exploited in a lab and not in real life... Because in a modern (I am talking Marshmallow or maybe even Lollipop) there are other things that protect the device, application sandboxing, DM-verity, SE Linux, and IntentFirewall, are all things that would likely protect the device even IF (and that's a big IF) one of these vulnerabilities did happen to be exploited on a device.
So are security updates important... no, not from a technical perspective in real life for the average user, but I certainly wouldn't reject them if they are easy to apply. I accept and apply every single one, even though I know the chances of something happening if I don't are probably less than that of me winning the Powerball Lottery Jackpot twice in two consecutive weeks, or about the same as being stuck by lightning while being bitten by a shark.
Now, none of what I am saying applies to other updates which are often bundled with security updates, or upgrades.
Click to expand...
Click to collapse
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
ThanuTK said:
So i recovered and now wifi is not working. From the other thread i see that others have this issue as well. What are my options now?
Click to expand...
Click to collapse
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
acejavelin said:
Its a radio version issue... your radio firmware doesn't a match what the kernel wants. You need to flash the right ones. You will have tell me more details of how you recovered.
Click to expand...
Click to collapse
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
ThanuTK said:
I used XT1575 to update and then just followed the directions. Does that answer your question? if not could you please clarify your question ?
https://androidfilehost.com/?fid=745425885120703327
In the other thread i see people using MPH24.49-18-4 FIRMWARE to fix this issue, but you stated that this might cause issues in the future, so i dont know what to do. Thanks again for helping me and understanding my lack of knowledge with all of this.
https://forum.xda-developers.com/mo...bootloader-t3489110/post69432451#post69432451
Click to expand...
Click to collapse
The only difference in your links is one is a later build than the other one. Either one should work fine but if I had my choice, I might pick the first update and then use OTA to get to present. NOTE: I had to restore my September 1 backup with TWRP as the December 1 security patch broke my Bluetooth and I use Bluetooth all the time, it is too important to me to lose over a stupid security patch. I have since frozen the updater to avoid being nagged to death install the December 1 update again. When the next "real" OTA comes along, I will thaw the updater so I can take it and *hope* that the Bluetooth issue is solved. I will of course *always* make a TWRP backup prior to doing *any* update so I always have a way to back out of it in the event something is broken over the latest security patch OTA. HTH