Yesterday, we reported that Dan Rosenberg achieved the one task for the Samsung Galaxy S4 that many new Android device owners are always looking for — he has unlocked the device’s bootloader. The deed was done on an AT&T Galaxy S4, but the exploit is expected to be in all versions of the American Galaxy S4. So why can’t Rosenberg release the method just yet? His reasoning is quite noble, really — he wants to wait until Verizon’s version of the device is out.
Carriers and OEMs have a tendency to race to patch exploits either ahead of launch or on launch date, so Rosenberg wanted to make sure Verizon didn’t catch wind of the exploit ahead of its launch. The carrier would certainly have enough time to do something about it seeing as it’s not slated to launch until the very end of this month.
I know it’s hard to think that you’ll have to wait another 28 days to unlock your phone, but in the end it will be for the greater good of the Android community. No one should be denied the ability to unlock their devices, and with this high profile release it’s necessary to tread carefully to make sure an entire group of folks aren’t eventually left out of the fun.
There’s no guarantee Verizon would patch the exploit ahead of launch date if they found it, but there’s no guarantee they wouldn’t either. It’s better to be safe than sorry, so mark your calendars and let the waiting game begin.
- Android Lollipop on Galaxy S4
- T-Mobile pushes out software updates for HTC
- Samsung GS4 Google Play edition removed from Play Store
- Another Samsung Galaxy S4 fire
- Check out the Samsung Galaxy S4 forums, see the specs, or find news and reviews.
TAGS: Samsung Galaxy S4