- Jul 17, 2010
- 1,060
- 24
- 0
brand new to Android and are rooting using these "one-click" methods and do all these things having no idea what they could be doing to their phones.
I couldn't agree more avl. I feel like this whole thing is a double-edged sword. My only intentions by making this thread were to ward people from the risk involved with accepting an OTA that no one knows the repercussions for. But at the same time I don't want people who are less than informed when it comes to rooting and hacking to rush out and get themselves in a mess. I have been more than willing to help people fix their problems and get through all their situations, but I definitely can see what you mean if it were to come through in floods.
Anyways, at least you know where I'm coming from with this.
If I were to simply wait a couple of days once the OTA update is available, would the hacking community know if the bootloader had changed and what exploits would work?
My plan has been to avoided rooting and running custom ROMs,etc, until after the 2.2 update.
Yes if you gave it a day or two I'm sure the necessary information would be readily available on this forum and many others. The problem is holding off on the OTA until that information is available. Once an OTA is pushed to your phone nothing short of powering it off can really stop it. Hence why I recommend those looking to dip into the hacking scene later down the road, consider taking that plunge now and loading up the leaked 2.2. It prevents the OTA from hitting your phone and effectively gives you unlimited time to let that information hit the net.
