My former boss (actually now a current boss again since I’m working for him once again) has a T-Mobile Samsung Galaxy S5. On occasion, he has had me root his phone. And usually what happens after I root it, he then looses root the next time he downloads an update. Which isn’t necessarily a bad thing. He usually just runs the stock, factory ROM (I’m just rooting his phone, I’m not installing recovery, nor am I flashing a custom ROM). The main reason why I’m rooting his phone is so I can install adaway and use the HOSTS file to block the ads on his phone. Generally when he upgrades his phone, since he’s just running the factory software, he loses root, and I have to re-root it. Very recently, he upgraded his phone to Lollipop. And so, I was asked to come in and root his phone. Again. So, I got my laptop and headed up to root it. And halfway through the process, the phone wouldn’t boot up. After some digging, I realized that there was no root yet available for his phone (there may be a root available for it, I’ll have to do more research). Fortunately, he is sufficiently computer literate that he was able to recover his phone.
Why am I writing this? This is a lesson I’ve learned since I got my first Android phone. That you never update your phone as soon as the update comes out. Inevitably there are going to bugs and/or you’ll lose root (not that I’m concerned about that since I’m S-off). For my HTC One, I'm currently running Venom. Currently, it’s KitKat (Android 4.4.3), but Lollipop should be coming shortly. I’m probably not going to be jumping at the bit to update it. It’s sometimes best to wait and see if there any bugs…
This is yet another lesson learned…
No comments:
Post a Comment