Database Users

if you root a sprint hero will you still get the android 2.0 update

just rooted my sprint hero and now wonder if i can still update when they come out with the android 2.0 for my phone. i didnt flash to a new rom or anything just rooted the device. any one know thanks

anyone feel free to correct me but i don't see why not...
but if you use the update from them you might loose root
and you might not be able to get root back if they fixed how ever we were able to root originally... ( but it prob wont be long untill someone finds a new way)

Confused by the correct order of updates: OTA, Root, Froyo?

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?

[Q] Some Questions About Software Update

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.
.

[Q] Android L: Available Without OTA Update?

Hey guys. First off, I'm new (this is my first post) so if I say/ do something wrong, please be considerate.
So I read somewhere that the new version of Android, Android L, might be coming out as early as December for the Samsung Galaxy S5. Earlier this year I got a Galaxy S5 and as it is my first Android, I wanted it to be the best it could. After a while I decided that it would be a good idea to root it, but as it is a Verizon model, it didn't look like I was going to be able to since the bootloader is locked. Luckily once towelroot came out I was able to root it, thankfully.
A month or two later, an OTA update came out, for Kitkat 4.4.3, and after several tries at installing it, I figured out the hard way that once you root your phone, OTA updates don't work anymore.
With all this being said, I'm a little concerned that I wont be able to get the next version of android on my phone. Even if it does come out in an OTA update, I know I wont be able to install it and since the bootloader is locked, I wont be able to flash it onto my phone.
Is there any hope that I'll be able to get Android L, or am I going to be stuck with Kitkat 4.4.2?

omega_927 said:
Hey guys. First off, I'm new (this is my first post) so if I say/ do something wrong, please be considerate.
So I read somewhere that the new version of Android, Android L, might be coming out as early as December for the Samsung Galaxy S5. Earlier this year I got a Galaxy S5 and as it is my first Android, I wanted it to be the best it could. After a while I decided that it would be a good idea to root it, but as it is a Verizon model, it didn't look like I was going to be able to since the bootloader is locked. Luckily once towelroot came out I was able to root it, thankfully.
A month or two later, an OTA update came out, for Kitkat 4.4.3, and after several tries at installing it, I figured out the hard way that once you root your phone, OTA updates don't work anymore.
With all this being said, I'm a little concerned that I wont be able to get the next version of android on my phone. Even if it does come out in an OTA update, I know I wont be able to install it and since the bootloader is locked, I wont be able to flash it onto my phone.
Is there any hope that I'll be able to get Android L, or am I going to be stuck with Kitkat 4.4.2?
Click to expand...
Click to collapse
I don't know anything about L coming out but you can get all the updates you want. All the info you need is in threads here and in the general forum. You can always odin back to stock and take OTA updates. Or you can install which ever version you want via odin and then root from there.
Edit: In reading an article a while ago over @ techradar, I think we'll be seeing L sooner than you think. The thinking seems to go that when the Note 4 drops with L on it, Sammy will push it to their top tier phones right away after that...

Questions about rooting before I buy a note 4

I'm looking to buy a note 4 now that custom roms and perm root has been achieved. I already know to make sure the android version is no more then 5.1.1, but one thing was throwing me off in reading up on this.
Some guides mention to "make sure the CID starts with 15". Others don't. I may be entirely wrong here, because I don't know what CID stands for, or what it is, but I'm getting the impression that CID 15 is a software number for the developers model of the phone. I've also read it's possible to convert the note 4 into thinking it is a developers model of the phone. So that would mean I don't need to worry about buying a model that's already CID 15, because it will be taken care of later. Is this correct?
My questions are....
How do I prevent my phone from starting up, and immediately downloading 6.0 or 6.1 or whatever the latest update is, before I root? How do I block those updates without root?
Whats the best newb friendly guide on this forum for going from day 1 bought, to custom roms and perm root? Basically an "everything at once" guide. Assuming I don't even have the phone yet, don't have temp root, haven't changed the CID yet, ect ect ect. I want to start reading these guides so I can get myself familiar with the process.
I read either here or on reddit that kingroot puts spyware on the phone. Is this true?
Anyone know a good place to buy the note 4? I'd be looking for the verizon version.
Anything I should know that I don't even know to ask about? My last (current) phone is on it's dieing legs. It's an HTC thunderbolt from 2011. I was running android 2.2. Yes, I know. It's old. I haven't experienced a post 2.2 android OS, so this is going to be basically 5 years worth of "HOLY **** LOOK WHAT THEY ADDED!!!" moment for me.
What are the differences between different model numbers. I keep seeing (SM-N910V) in the videos I've been watching, but I have no context as to if that's good, or bad, or what it means.
Will this fast charging thing work with ROMS?

I recently decided to completely start fresh with my rooted Note 4 (I have a N910H - Exynos). I factory reset, wiped, then downloaded the latest firmware from Sammobile. I thought I just go completely stock.
After flashing through ODIN I was on MM 6.0.1, stock.
Then I wanted to root. It was easy, so I don't think to have to worry about updates or anything, it is easy to root, whatever version (AFAIK for the Exynos versions)