1. Is it advised to gain root NOW prior to the forthcoming Sony Lollipop OTA?
Point being if I don't root and I update to the latest forthcoming lollipop ROM from Sony then will it become a difficulty to gain root via the current downgrade method of rooting.. Or will downgrading from Sony's lollipop ROM be easily achieved via flashing .93 from flastool for instance.
My idea being can I remain unrooted and update via forthcoming ota from Sony and still achieve root via the current root methods of downgrading.
2. If I gain root now though, and lose ota facility because of root then will i be able to flash the latest official Sony lollipop ROM via flashtool manually and still retain root?
Sorry for any repetition above it's crazy late here. I've been itching to root but have been holding off in anticipation of an imminent Sony lollipop release... After some thought on the questions I post above I'm trying to determine if it's best to root now to prevent a potentially unrootable Sony lollipop rom?
Thanks in advance
1. Will downgrade from lollipop be possible? I have seen both happing with other devices so could go either way. No guarantees because we just don't know yet.
2. There is no downside to rooting now. Once you're rooted you don't want to install any official OTA anyway. You could lose root or even damage the device (we don't know yet). What you want to do is flash Pre - rooted firmware which you can download in the forums here (usually you get updates sooner than through OTA this way)
It's like a whole new world once you familiarised yourself with the possibilities.
Root is recommended you don't have any downside. If you want the ota update so bad you can still decide to flash your current software again. Though this I would not recommend since there is a possibility that you will be stuck in lollipop like clouds5 said (if no downgrade possible) .I don't think this will be happening since Sony until now is not really restricting users to flash official firmware. Hell they even encourage bootloader unlock officially. That said, just root and the enjoy the countless advantages.
As another alternative, and only because it hasn't been pointed out, you could also try to simply remain confused. The challenge in this is in hopefully coming to a point of peace with your circumstance by no longer worrying about it. I've been awake for far too long and have been sleep deprived over the past days, thus having no business making posts like this and accepting ir as innapropriate, but the general philosophy expressed remains solid ?
Since i don't have it in my signature, don't forget to hit "Thanks" ?
[email protected]
I will proceed to root now to prevent an unrootable Sony lollipop OTA ROM - which is incredibly likely given chanfires views on the difficulties of rooting lollipop "specifically devices with locked bootlaoders."
Given we would all like to retain our DRM keys for when reverting to stock based ROMs I think I've come to my conclusion.
Thanks for your thoughts, it has certainly helped to proceed with rooting now (with I've been itching to do) rather than wait patiently for Sony's lollipop OTA (which could become a hindrance, now that I've fully understood the 'potential' for an unrootable lollipop ROM.)
I like your signature ;o)
dillalade said:
[email protected]
I will proceed to root now to prevent an unrootable Sony lollipop OTA ROM - which is incredibly likely given chanfires views on the difficulties of rooting lollipop "specifically devices with locked bootlaoders."
Given we would all like to retain our DRM keys for when reverting to stock based ROMs I think I've come to my conclusion.
Thanks for your thoughts, it has certainly helped to proceed with rooting now (with I've been itching to do) rather than wait patiently for Sony's lollipop OTA (which could become a hindrance, now that I've fully understood the 'potential' for an unrootable lollipop ROM.)
Click to expand...
Click to collapse
Jeah it is very unlikely that L will get root since it has already been obtained and the bounty is fulfilled. So there is no real motivation to keep working on it for this device. And also like Clouds5 said you will probably get your hands on rooted stock lollipop sooner here than through the official OTA update. Or 1-2 days later. Enjoy it .
Root now or regret it later.
I'd recommend you root now. The ability to get OTA updates is not a big deal at all. If you root, you can still install stock roms which would be just like the OTA roms. Sometimes the unofficial stock roms come out sooner than the OTAs, if not, then very shortly after. I actually like SONY's stock rom. I'm rooted, and I plan to just use the stock rom with some root enabled modifications.
I'd say that most custom roms are just as good or better than official stock roms from OTA.
With my last phone, I regretted not rooting when I had the chance. Sure, I was okay with it overall, but I wished I had root so I could have my phone exactly the way I wanted. There were some really useful functions that I missed from having a rooted phone, like screen-off music player controls. I missed being able to tether without the carrier knowing.
Some companies are making it harder and harder to root, so I say root now while you can.
If you root now, you're in control. If you wait for OTA, who knows.
Related
I haven't been reading any articles on unlocking the N1..mainly to fight the temptation of wanting to do it vs voiding warranty. However, I think I'm going to suck it up and do it once a good ROM comes out I just have some questions.
1. If I unlock the boot loader, and decide I just don't wanna have root anymore, can I return to "stock" and receive OTA from T-Mobile/Google? Or am I just screwed?
Ok so that was really just one question..my mind drew a blank on the others.
You can always (whether or not you have root access) install a signed, "stock" ROM. These will always be eligible for OTA updates.
However, you will be voiding your one-year warranty, and this can't be undone (yet).
kozm0naut said:
You can always (whether or not you have root access) install a signed, "stock" ROM. These will always be eligible for OTA updates.
However, you will be voiding your one-year warranty, and this can't be undone (yet).
Click to expand...
Click to collapse
Do I have to manually install or will I be notified and have it installed for me? I understand the warranty part, it makes me paranoid but out of the 6 phones i've owned I have only ever had to send 1 in for warranty..I hope my luck doesn't run out on this phone.
You don't have to install a different ROM to enable root and unlock your phone. The OTA updates, I'm assuming, will be very easy to install (however your carrier intends them). Manually installing custom or stock ROMs can vary in difficulty.
Generally speaking, our devs will put out updates before T-mobile sends them OTA, since Google releases the SDK, etc.. That was the case with the G1 and MT3G... so I assume it'll be the case with the N1 as well.
I'm sure this is somewhere on the forum but I've made a best effort searching/reading for the past hour, and am now more confused. I rooted my incredible a few weeks ago in order to get the tethering feature to work, and this was before the OTA update from VZN came along. everything works, no complaints.
Since 1) I did not get the OTA update, and 2) I eventually would like Froyo, I have a few questions:
1) Do I need the OTA update?
2) Will I need it in order to get VZN's Froyo update whenever that becomes available?
3) If so, should I wait until that announcement is made?
4) If I unroot and get the OTA, can I simply re-root in order to get the tethering feature back?
5) Would I be able re-root by following the same instructions as when I rooted the first time (unrevoked3)?
6) If I unroot/install OTA update/re-root, how do I get VZN's Froyo when it is released? I assume I would need to un-root again, and then wait for the update?
7) Am I just as well off unrooting/installing OTA update/re-rooting and getting an unofficial version of Froyo? I am in no rush for froyo and do not want to risk messing up the phone for it.
I assume some of these questions are answered on the forums but like I said, the instructions I found on various threads seemed incomplete. Would greatly appreciate answers/links to answers for any of the questions.
Thanks
if your happy with the way the your phone is right now than just wait till the official update comes out.
You'll likely be told the update is available on your phone, but if you want root, you won't want to apply that right away.
Hopefully some magic like Evo update is done for us... the Evo update has already been rooted and pulled apart.
Thanks binny and k_flan... So I'll just wait for VZN. Can I install the VZN update (Froyo) directly or would I have to un-root first? No way to know this I suppose, but will the VZN Froyo allow wireless tether or will I have to pay extra for the feature?
My plan
My plan at this point is to wait for the OTA and then for unrEVOked to see if they can root it. If they can, I will RUU back to a stock rom, and apply the official update. This will guarantee [1] VZW to handle if I brick, and [2] that I am running the real radio and the real 2.2 (instead of the buggy beta which is making the rounds).
If they can't then the decision gets harder. I suspect that my desire for the 2.2 will outweigh my need to still be rooted.
What I know i WONT do is jump through these hoops just to install a beta radio/OS combo. If the radio wasn't at issue, it would be a different story.
np OP. You won't want to install the VZW update, it will likely not work with unrevoked's reflash tool.
I also have to correct what I said earlier, it doesn't appear it is the final build that was rooted for the Evo, but the radio was pulled from the final build and used with a rom.... Either way, it seems they've got the official radio (at least, that's how it looks for now), hopefully that happens for us, and official radio img.
Fair enough. still getting up to speed on terminology.... i assume reflash means un-root - is there any way to reset the phone to be able to get the VZ update/froyo?
Hey everyone,
Just wanted to ask a quick question regarding the firmware
I got my UK unlocked S5 last week and as soon as I set it up, an update came through, which is 100mb, the note regarding say "Improved performance", the update download, but I haven't installed it yet. Mainly because of a bad experience I had after updating my S3. I haven't come across any bugs since I've been using it, and I'm concerned that if I update, the battery will drain quicker, or perhaps cause an error in the recovery mode(these things happened to my S3 after updating to 4.3). So 2 main questions.
1. Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
2. Suppose I updated and wasn't happy with the new changes? Would it be possible to go back to the original firmware version that my phone came with when I took it out of the box, *without rooting my S5?
Hope some people on here can shed some light on these questions.
Thank you in advance*
1. It's just a system update. The phone is new there are bound to be updates as issues are ironed out
2. You can odin any firmware whenever you want
Sent from my SM-G900F using Tapatalk
MasterfulNinja said:
Has anyone here downloaded this 100mb software update their S5? If so, what differences did you notice?
Click to expand...
Click to collapse
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
International Business Times said:
Issues Spotted for the Android 4.4.3 Kitkat
The Android 4.4.3 Kitkat system update is pretty much all about improving performances, strengthening stability and fixing a couple of bugs. However, it reels in a couple of issues experienced by users of Nexus devices that have already been upgraded to the latest update.
According to IT Pro, some of these issues include wi-fi problems, crashes and reboots and bugs found in apps. Google has not yet given any statement about how to deal with these issues nor has there been any word if these issues are only experienced by a handful.
Click to expand...
Click to collapse
.
.
fffft said:
Your instincts are dead on. Updates may fix bugs or add a desireable feature. But just as often they introduce new bugs, break root or disable root exploits, break a few apps and add noxious DRM frameworks like the Knox qfuse warranty bit. They can seriously mess up a custom ROM and may depreciate features like MSC or car dock that may be important to you personally.
Updates cannot always be reverted. Try downgrading your Kitkat baseband to Jellybean and see what happens. Or try removing the Knox security bit after you take the update that introduced it. I disable automatic updates and wait to hear what early adopters find before upgrading.
Unfortunately you didn't tell us the all important version of your update. Or even tell us what your current firmware version and carrier are. Your update might be similar to the recent ATT /Verizon OTA adding the mixed blessing of reactivation lock. That is causing bootloops for some people with custom kermels. 4.4.3 is mostly bug fixes, with a few UI tweaks. And I believe 4.4.4 took aim at closing yet another open-SSL exploit and reverting some of the new 4.4.3 bugs.
No matter what an update intends to do, a few new bugs and unexpected conflicts usually turn up. A quick Google finds reports like this:
.
.
Click to expand...
Click to collapse
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
MasterfulNinja said:
Thank you very much for your detailed answers! That's exactly it! And I know from experience that updating firmware can cause a negative affect to the phone's performance. My iPhone 4S is still on iOS 5.1 but runs perfectly, while friends who updated their 4S to 7.1 experience freezes and heavy lag. Maybe companies do this deliberately, so people get frustrated and end up having to get the latest, more powerful model so the OS to run smoothly?
I do exactly the same, I always wait to see what people about an update before updating. The only difficulty with Android updates is that there seem to be so many different versions of updates. For example, when I researched the 100mb one for the S5,* various sites mentioned it, but others say the size of the update was 30mb, which were called "improved performance" I also heard about updates not always being able to be reverted to the previous version,* and also about Knox. So, you can see why I'm hesitant to update.
I know quite a bit about using Android, but have very limited knowledge regarding rooting and custom roms and so on. Also, after reading that rooting a phone incorrectly can turn it into a brick, I'm happy to just leave it as it is. I've attached a photo which shows my current firmware version, as well as other information. Also, as my S5 is unlocked, the only updates I'll receive will be from Samsung. I asked my carrier (T-Mobile UK) and that's what they told me. Only phones from bought from them include added apps that they put on, and I think they may also be able to tweak the updates received, by adding their own features.
Some more questions for you;
1. Do you recommend a factory reset after each software update?(I had to factory reset my S3 to stop the battery draining issue that 4.3 caused. But was wondering if it's best to factory reset after each and every update on Android devices)
2. I know you said that sometimes reverting back to a previous firmware isn't always possible, but can't using Odin with the correct firmware version work? Like Goldie mentioned in the above reply. And does changing the firmware via Odin require rooting the phone?
Click to expand...
Click to collapse
1. Yes, a data factory reset after a update/flash a rom is remmended and gives best performance and stability;
2. I haven`t tried flashing a older rom itself but it should be possible i guess as this is not dowgrading like from 4.4.2 to 4.3. You could try it and if it fails there`s no harm done as you can flash your current rom back.
3. Installing a update or flash a rom usualy will kill root, though superSU Pro offers a survival mode to keep root after a update. You can also flash a rom with Mobile Odin Pro and enable everroot and the 2 other options so you will not loose root.
@MasterfulNinja
I don't automatically accept updates. Someone more impulsive, or indifferent can be the guinea pig. That approach is effective in avoiding some unpleasant firmware surprises. Often an older firmware version runs smoother and is more stable as in your IOS 5 vs 7 example. Running an older firmware means that you may have unpatched security vulnerabilities but in practice this usually isn't a great or unmanageable problem. It is a point to keep in mind though.
Rooting isn't nearly as dangerous as many people think it is. Someone who can follow directions and avoid flashing firmware from a completely different device will rarely brick a phone. And even if you did, you can usually recover from the mishap. I mention this because one of the best ways to maintain a stable phone OS is to install a decent custom ROM (which typically requires root). And then most of the heavy lifting is done by the developer who has already removed bloat, restrictions and other objectionable pieces. And monitors and releases tailored and usually stable updates for those using his ROM.
Android updates vary in size because they are screened by carriers, each deciding what update components and /or custom bits goes into their version of the update. More restrictive Apple manages all IOS updates centrally from their California servers i.e. they don't relinquish direct control to carriers. Still it isn't hard to find articles giving a good summary of what issues android firmware updates are addressing.
Some people believe that you should accept every update and as soon as it becomes available. I don't see a compelling need to update unless you are trying to resolve a current bug or are enticed by a specific new feature. I don't recommend a factory reset after each update. I do recommend that you clear the system cache from recovery mode though. A factory reset usually won't benefit you but it is time consuming to reinstall and reconfigure your phone.
Having said that, if you have a specific issue, such as the 4.3 battery drain then you have a rationale for doing so. But I have to say that I experienced the same S3 issue and clearing the cache was sufficient to stabilize the phone for me. Some phones will develop corruption or configuration conflicts over time, especially if you install a lot of apps. Or if you have a specific app that makes a mess of your file system. With that in mind, I do do a factory reset about once a year to clean up the phone, the same as I would do for a laptop OS. But I don't see a reason to do it after every update.
Odin is a Samsung product, complete with DRM. So no, you cannot flash anything with Odin. You can flash most stock firmware and in particular Odin will look for OEM signatures if you try to change the bootloader or modem. In the case of downgrading, it is the Knox qfuse on your phone that will cause the Odin flash to fail. If you try to downgrade you end up with a partial flash which can soft brick your phone and trip the Knox flag.
.
Hello,
Today I received a notice that my phone has an OTA update available. I'm currently rooted on OC4. I can't find anything about this new OTA update, but I'm assuming it's only patching and nothing major. Is it safe to take this OTA update without fear of my root being lost?
Additionally, I'm wondering if anyone can offer some insight into the best options for this device moving forward. The phone is getting old and I would like to give it it's "final update" + a few months use before I replace it. Marshmallow would be nice, but I use Google Wallet/Android Pay frequently and I've heard that they're not compatible with some custom builds and their potential modification of the secure portion of the device those applications rely on. I would also prefer to be able to utilize the xposed framework, though that is not necessary.
What are the most modern, more vanilla, most recent Android custom builds recommended for this device?
Thank you
Given you are on OC4, you can't install a custom rom because of the locked bootloader
Hello XDA community,
This is my first post on here and I hope I'm not doing something wrong in terms of protocol, but I have a rough idea on finding a root for this phone that needs support and refining from you guys, the XDA community.
My idea is this: If we can find a way to downgrade the phone software back to before the December 2016 security patch, we can run a Dirty Cow root exploit (, which is ready to go on GitHub, ) to temp root this device (or any device, in theory). Once we have temp root, we could run a program like SunShine or whatever else to turn that temp root to perm root. (SunShine currently says that, to full root this device, it needs some kind of temp root.)
Now going back to the first part about downgrading the software to before the December 2016 security update, I initially thought we could achieve this through mfastboot or RSD Lite, since they allow flashing of officially signed Motorola firmwares. However, I read that when upgrading the Moto Z, and presumably all other variants, from Android MM to Android N, the (locked) bootloader is updated, too, and will not allow downgrading, resulting in a prevalidaton error. This is where I need your help.
The question is: How can we downgrade the firmware back to MM, or some other before-December firmware, to use Dirty Cow for root. Please leave ANY suggestions in the comments.
Thank you for your time and help. I have faith that we will be able to solve this together.
I don't think you can downgrade. But i've been running this for the past 9 or so months to prevent the forced updates: https://forum.xda-developers.com/moto-z-play/themes/app-moto-z-play-apps-stop-ota-motocare-t3538812
(no idea if that would work on the z force)
Well I know there are many videos on YouTube claiming to downgrade certain Moto devices through RSD Lite or mfastboot for different budget Moto devices, but I suspect they are all fake. Nonetheless, I hope there is a legitimate way to downgrade.
I forgot to mention that if you can get a replacement Moto Z Force from Verizon, which is very easy to do in my area, they ship you a refurbished replacement, which runs marshmallow and has no updates installed, but I don't have the opportunity to get another replacement, so for anyone else, that's one way you could "downgrade" and try Dirty Cow to root the device.
I'm just going by this topic https://forum.xda-developers.com/moto-z/how-to/dont-upgrade-to-nougat-ota-t3524456
but i don't really know for sure
Wow. Now I wish I'd known about this MUCH sooner. Its too late for me. Well, in that case, try to see if you can revert back to marshmallow if you unofficially upgraded to nougat and check what month of security patches you are on. If it's before the December 2016 security patch, then you can run Dirty Cow and get temporary root. With temp root you can most likely find a way to make it permanent root.