Hello, few hours ago I received another notification about availability of new firmware upgrade. I recall that this is the 2nd time a new firmware is available since I bought the PRO 12.2 LTE. Just like the first time, I cannot tell what kind of changes the firmware made both before and after I updated the firmwares. In general, it is advisable to update whenever it is available? As you know, for some devices, updating caused more troubles.
One would hope that the manufacturer would QC their build prior to rollout so the odds of having issues should be low, but sometimes there are issues that creep up such as unforeseen incompatibilities with particular pieces of 3rd party software users may have installed on their devices. It's difficult to provide a definitive answer here in that regard.
Generally if you're not rooted and have no intention of ever rooting then the answer is yes, with the expectation that anything is possible when it comes to unforeseen incompatibilities.
If you are rooted or wish to root in the future and you're not technically inclined enough to recover from loss of root or restoring from backups then the answer is no, not until others with root have reported in on experience with retaining root or achieving root after updating. Quite often a firmware/system update will cause loss of root. In some cases root will be achieved quickly via applying prior root methods BUT this cannot be guaranteed since there is always a chance that a prior exploit used to gain root access was patched by that update.
I'm guessing root isn't something you're too concerned about but I just thought i'd mention it for the benefit of others.
Thanks. For the time being, I have no intention to root. Maybe a year later.
When it comes to updates, I have a very simple policy: If it isn't broken, don't fix it.
Due to this method of waiting for other people to pick out the errors I've managed to avoid several serious problems on Android over the years.
This applies to app updates, which more often than not introduce problems, as well.
Not to mention every update, no matter how small, brings with it the risk that you need to go through the entire process of wiping the device. I rarely have the time for that. (Which is why I'm 2 updates behind on my Note 3)
I concur with what's already said and just wanted to add my $0.02. There is an empirical finding that the best performance is achieved from the ROMs that are available about six months to a year after the release of any given device and here is the justification. The device is initially shipped with the Android version available at the time of the release. This initial version is invariably buggy because the fast design cycles of these things do not allow a comprehensive test drive by the vendor. So the consumers report the bugs, they get patched, and about 6 months later everything is wrapped into the next version of Android and pushed as an update. This second ROM release is much more stable than the first one but still lacking a few things here and there, which results in the next major ROM that will fix most everything.
By this time we are 6 months to a year into the life of the product and the market is now seeing other devices with higher processing power and better specs. The Android releases at any given point in time are tweaked towards the expected performance of the devices that are available at that time. So the next update for your now-more-than-a-year-old device will have nicer features but it is geared towards other devices that are faster and better than yours. So now you upgrade to the third release and you will find that while all the initial bugs are gone the device is laggy and the battery goes down faster than it used to. Most devices don't have a straightforward procedure to downgrade to an older version (at least for the common user) and therefore you will just write this off as your device being too old and slow and then you will be likely convinced by a salesperson to buy the next generation tablet and that is the end of that.
If you are into rooting and modding don't forget that every update makes it generally harder to root your system.
Related
ive read, re-read, and read again how to go about updating the radio to the newest version to be able to flash 2.2 roms. although the instructions are clear, is there a second set, or clearer set available? i just want to make sure im 100% clear about what im doing before i do it. im not new to flashing roms (did it on my moto droid) just never did something that had the potential to brick my device.
secondly, how easy is it to handle all of this on a macbook? my pc doesnt recognize my phone when i plug it in, but my macbook does so i'd be doing this from that laptop.
...
My 2 cents ... wait for the official OTA to come out and then wait a little more for unrEVOked to enable root.
If you are concerned with bricking then I certainly wouldn't go through all the pain, suffering and risk just to install a prerelease radio (which is fairly old, by the way) and then to install beta releases. These forums are now littered with people posting bugs (which no one will fix ... because its a beta/prerelease ROM) and posting workarounds ... but the BEST workaround is to just wait for the actual release instead of playing around here.
jdmba said:
My 2 cents ... wait for the official OTA to come out and then wait a little more for unrEVOked to enable root.
If you are concerned with bricking then I certainly wouldn't go through all the pain, suffering and risk just to install a prerelease radio (which is fairly old, by the way) and then to install beta releases. These forums are now littered with people posting bugs (which no one will fix ... because its a beta/prerelease ROM) and posting workarounds ... but the BEST workaround is to just wait for the actual release instead of playing around here.
Click to expand...
Click to collapse
Market - fixed
Browser - fixed
Gmail - fixed
Facebook - functional
Exchange - functional
What is it that hasn't been fixed? The performance of my phone on 2.1 versus the performance on 2.2 is greatly noticed. Above and beyond that, the "official" 2.2 release has already been stated, by unrevoked directly, that it will be very difficult to root, due to new security measures put into place.
I mean, the walk-throughs that are available on what to do are about as straightforward as can be, there are not "clearer" directions than the step-by-steps you've already read. I was wary of it too, but honestly, once you perform the steps, you'll look back and think "damn, that was alot of fuss about nothing."
Ugh
That's why I said it was my 2 cents.
I stand by my belief ... we now have a forum which is devastated by posts of leaked beta OTA's, people posting bug reports on leaked beta OTA's, people posting solutions to bug reports on leaked beta OTA's, and then the king of them all ... people cooking custom roms based on leaked beta OTA's (which then, in turn creates posts on bugs on cooked roms based on leaked beta OTA's ...).
While this is all well and good, once the OTA comes out *IF IT IS ROOTABLE* what use will any of the beta roms be (or the posts they spawned). The answer is none. While that is ALSO well and good (since this is a dev site), we have a decent amount of people bricking because the steps involve upgrading the radio ... to a beta no less and THAT is where the risk/reward equation is out of whack on this whole exercise.
SO ... I am simply saying, in response to the OP, that the fairly complicated steps and the inherent risk in upgrading the (beta) radio to get the (beta) OTA; may be outweighed by the fact that an OTA will be around the corner and will probably be infinitely less risky for the payoff. The only way there is no payoff is if it can't be (ultimately) rooted.
Thanks for the post, and the answers. I had thought that staying on 2.1, ignoring the OTA 2.2, and wait for the rooted 2.2 to be released before installing it would make things easier. I guess I was wrong.
I installed the new roms without the ota. Camcorder is broken but everything else works.. no risk that way
Sent from my Incredible using XDA App
By owning a flagship android device, we always want the latest and greatest software available for this device, but there are only limited number of software engineers that work on android updates for LG flagship devices (around 300-400 engineers) depending on region, so they are not able to provide the users with all the minor android updates Google decides to release. Therefore, they turn their attention on major updates, instead of minor ones to keep their user base happy. Keep in mind that LG honors your device eligibility for upgrade to 24-27 months before dropping support and that we can't always get what we want.
My question to you is... If LG was reconstructing their plans for android updates, which one do you prefer?
1) You want all the minor android updates that Google releases to be released for your LG G3 and receive major ones later.
2) You want faster release of major android updates to the most current version.
To clarify: Choice 1 gives you more frequent small updates and Choice 2 gives you less frequent, but large updates. When your device approaches the support-end date, choice 1 will be one major update behind choice 2 because engineers working on every android updates and won't be able to release the major one in time.
This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!
beastobadness said:
This is a really hard one to call. Recently I received the 20f update from 20e on my D855. It was only a 12mb google patch but didn't change the android version the phone was on, in fact I don't know what it changed! Obviously it fixed or improved something but it would be nice to know what!
I think it is a matter of priority, if we receive a major update, for example going from 5.0 to 5.1.0, which not only has performance improvements but cosmetic and feature additions then I would like to receive this type of update as soon as possible helping my device stay at the cutting edge.
But if this update breaks something... like my wifi becoming unstable or system programmes force closing all the time, I would expect that to become the priority no matter how small the patch update may be!
So to reiterate, my first choice would be option 2 bringing in a touch of option 1 if required!
Click to expand...
Click to collapse
I have to agree with you. I wish there was a happy medium between the two.
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
leekohlbradley said:
I've been reading the various rooting threads for a couple of days and overall the process seems pretty complicated with many different Nokia 6 versions, and different tools to use, etc.
Is there a way to get root with just the stock bootloader? I only want to do a few sudo operations once in a while, not flash any ROMs. Is this possible somehow? I'm using TA-1003 with 8.0.0 + April security update.
Thanks
Click to expand...
Click to collapse
Your best bet is to return the phone. Nokia has made a really, really bad bet by locking the boot loader. I think that by getting burnt by windows, they decided to jump back into the frying pan again. They don't understand what "OPEN SOURCE SOFTWARE" is. If they had a clue, they would not lock the boot loader. I returned mine because there will not be any active development or roms. I wanted the phone so I could root it, like you, and then unlock the sound features from the sound chip. So, don't bother rooting the phone, just return it or keep it stock.
In a year or two, Nokia will flop or get the idea that they want active development so people will buy their phones. It is a bad way to enter the market.
In principle I agree but I've used the phone for almost a year lol and sadly the power user community is really very small and so there's not much motivation for Nokia to make open phones. This seems especially true to me, since they're offering the phone as an Amazon prime adware phone, for example, so there is in fact a motivation to not open the phone, since it might let users remove the adware from their subsidized hardware... My 2mBTC
Hey all,
First off let me just say great work to everyone involved with rooting this now "ancient" phone, especially klabit87 and jrkruse. Additionally, I do not mean to be ungrateful with this post, nor suggest that rooting a phone is easy, especially one with a locked bootloader, or that the users here are entitled to such a feature.
With that out of the way....
I haven't looked into rooting this phone EVER until now. Haven't even peaked at XDA or Googled anything, I didn't even know it was possible until yesterday. I've re-ROMed all my previous phones but was actually satisfied with the stock S7 experience other than a Launcher swap and dealing with the always laggy Google maps. Well recently I got a new car and got fed up with the obnoxious list/action limit that Android Auto has as the voice search can be quite unreliable, the letter search is somewhat bugged on the media player I use, and in the end all it does is encourage people to just use their phone to change songs/settings and send messages, thereby completely failing at its goal of being safer. So, I really wanted to get Xposed installed to use the module that makes AA a lot more usable; however, now that I've looked back into the scene a bit, I'm not so sure I want to move forward.
To preface my question: Every Android device I've had before was essentially either rootable or not and ultimately banked on a security exploit that was eventually found. There were never really any concerns about major issues unless you were changing ROMs, kernels, or testing major CPU behavior changes. Just rooting itself was almost always issue free other than a small bug or two or the need to reapply at reboot.
From what I gather, it seems to me that they only way currently to gain root privileges on this device is to install this ENG kernel that's talked about in a lot of more recent posts. Is it truly the case that someone had to write a kernel from scratch that was pre-rooted and as of right now there is no way to root the device as it is stock? Is it that the only known exploit is how to flash another kernel, and the stock kernel is still locked up tight? It sucks that the current root seems so unstable/slow. I know there are a plethora of fixes but there really is no one major fix (other than potentially reflashing the stock bootloader that for some reason seems to work), and its a matter of installing a boat load of CPU and resource management tweaks and even then the performance/battery life isn't quite stock. Additionally it seems like its definitely a YMMV kind of thing as some users seem to still have significant battery drain or slowness/heat even after trying tons of fixes.
Since I am just now getting familiar with the "homebrew" the phone I've had for 3+ years and know nothing about the work that's been done, I genuinely just want to know the technical implications that got in the way of a cleaner root and why the current root method is stuck as sort of a work-around so to speak. The people that manage these breakthroughs rarely post about the process they went through unless its pertinent to a guide on how to root, so I was just curious why the root for this device is in the current state it is.
I would really like to root my Edge so I can be done with the AA nonsense but after just getting a new battery put in I really don't want to go through ****ty battery life again haha.
Thanks to all who weigh in.
Verizon requires most if not all manufacturers to lock the bootloaders. This is also Samsung choice as well. The T-mobile S7/edge and newer have locked bootloaders as well. Difference is T-mobile leaves it up to the OEMs whether they want to lock it or not. With some U.S. businesses and enterprises using Samsung Galaxy devices. They focus on being "enterprise ready" which makes sense from a business standpoint.
Believe it or not, Samsung used to be developer friendly when the S II came out. They even gave away Galaxy S2 devices to some XDA devs.
So, if you want a Samsung device with an unlock able bootloader. Get one that has an Exynos SoC or the Chinese Snapdragon variant.
I'm about 2 years into my ownership of Moto G7, and have yet to root or install any custom ROM, so I'm running the latest OTA update of Android 10. In recent weeks, I'm really starting to notice a big slow down. So looking for quick and honest advice: will it be worth the time and effort to root and flash a custom ROM? Will that noticeably improve my performance and make me happy continuing to use this phone for a while? What's the best custom ROM for this phone right now? Thanks!
Probably should have stopped OTA updates on the last good version. Updates kill phones.
If the OS is fast, stable and fulfilling its mission... let it be! I'm still running on Pie on my 10+, no updates for over 1.5 years... and zero issues.
Security simply isn't an issue with Androids most times even with outdated firmware unless you do something stupid.
My current OS load is over a year old...
Try a factory reset if you haven't done one since a major firmware update. That may resolve the issues.
...or find whatever is slowing u down. or I can recommend Lineage OS 18...constantly updated and polished...lots of users hence good support!
I'd say yes, but have a backup phone. Maybe have a plan to buy a new one if this fails. It has been two years since I rooted my black/blue one and I haven't regretted it. Some of my apps require it.
I just got another one like it only in white that's badly broken. I have tried to root it but I'm tired and pain meds are making my mind unclear. I did unlock the bootloader without any trouble. Mainly I wanted it so I could change its battery without damaging it, then decide if I want to change the battery in the black one or take it to a shop.
If I can bring the project phone up to speed I'll run it with my secondary line.
In short, though, yes. Be sure to back it up first, as this will delete all user data. The G7 64 ROM / 4 RAM is a very capable phone even as old as it is.
Finally mustered the courage and did it. So far, so good. Glad I did. Thanks for the advice!