Quote:
Originally Posted by BenS
Thanks for responding but I was actually just wondering if you had to do anything in particular to apply the update to a rooted phone. I am fully aware that we will lose root access once this is performed. I'm running fresh 1.01 currently and have no plans of losing my root which means I won't be updating. I was mainly interested if you had to say flash a stock rom or something to insure proper installation of the update. I have some friends with unrooted Evo's and I'll push them to do the update so I can check it out on their devices first while custom roms are finalized. I firmly believe that if people do update rooting will be a possibility once again. Sprint/HTC/Android need this to occur so they have free testing and development performed. If anyone thinks for an instance that there aren't any real insiders from these organizations "working" these forums and probably even releasing roms I would say they are most likely mistaken. Free research is done here I guarantee that.
|
As to your conspiracy theories (dont mean that in a bad way-just sayin') all I'll ask is this-why then did the last OTA break root? If Sprint "needed" all of this "free research" why bother breaking root. Not saying they dont reap the benefits of the hacking but IMO it's a bit of a stretch to say they need it. They do lose $ from free tethering.
As far as updating to Froyo-once it's rooted I cant see how the process would be anydifferent than flashing a Beta Froyo ROM now, just wait for the rooted version and then flash your brains out
Quote:
Originally Posted by Mystery
I misunderstood your question. Well when the previous OTA dropped, people with rooted devices who did the update ended up bricking their EVOs, so I would say its better to be in a stock ROM and then do the update just to be safe. Thats if your friends don't care about rooting.
|
Actually the bricking happened on non-rooted devices as well. If you remember, Sprint pulled the OTA and then re-released it. A number of people who got bricked tried the update twice for some reason.
It had nothing to do with being rooted. Plenty of rooted users accepted the upgrade and simply lost root.