Originally Posted by kettir
I get what a bootloader is--the low level programming that checks everything and then boots the OS. And I have read that when they say "locked bootloader" it means "encrypted bootloader".
Have previous bootloaders been un-encrypted and thus made flashable? Or was some "exploit" found that enabled the bootloader to be replaced with one that would be unencrypted and thus ROMs could be flashed?
It sounds like the bootloader being locked/encrypted prevents much being done in the way of custom ROM flashing. So at this point we have Safestrap, unless that doesn't work on the AT&T g900a.
So, what are the designers working on at this time--unencrypting the bootloader, finding a way to simply replace it, or using something like Safestrap to create a space where a different ROM can be placed and the bootloader bypassed in some way?
I suppose I am curious to find out just how tough this locked bootloader problem is for the devs.
Sent from my SAMSUNG-SM-G900A using xda premium
From what I have seen very few bootloaders have ever been unencrypted publicly by the community. There have been some devices although rare that the manufacturer has had a change of heart and allowed to be decrypted in most cases at the cost of your factory warranty.
My last phonetic galaxy s3 was not encrypted and allowed an insecure boot image. This did not check to make sure the rom, modem, or kernel were not signed. The development community is still very alive today years after its release.
Hashcode's safestrap allows for a custom rom but to my knowledge has never allowed a viable custom kernel. He did amazing work with this technology around the Motorola Droid 3 but the community never really built up support for the device.
It's a shame as my old s3 with a good rom and custom kernel is much much faster and more usable than this locked down s5.
Sent from my ASUS Transformer Pad TF700T using Tapatalk