I understand that, but he was making it out to be a problem with bootloaders. I have never heard of anything like what he was talking about. There are a few trojans roaming around Chinese third-party app stores that do not require an unlocked bootloader to infect your phone though.Oh and the only people that could be at risk of those Malicious attacks are root users and you would have to first give the code permission open bootloader isn't a big security hole
My phone booted in recovery by default. I didn't need to do it manually from the application.I'm not saying that motorola won't release gb for the d2 I pretty much know it will get it. I was simply using gb as an example
and bootstrap doesn't work if your phone won't boot into android (hosed system) sbf without the phone bootable pain in the but and it often fails. Because you may not have all the stock Apps
If they even gave me a choice between AOSP and Blur I would probably buy the Bionic. The locked bootloader wouldn't matter to me that much in that case.If only Moto would give the choice to use Blur or not. All I want is a choice and to make my device MINE, not Motos.
If they even gave me a choice between AOSP and Blur I would probably buy the Bionic. The locked bootloader wouldn't matter to me that much in that case.
They should definitely do a thing like the S-OFF option for the Nexus One. If you turned that off, it would unlock the NAND and enable ROM flashing, but you basically voided your warranty by doing so.
My phone booted in recovery by default. I didn't need to do it manually from the application.
HTC does not do anything even close to what Motorola does to discourage ROM development. A locked bootloader is much, much more difficult to get around than a NAND lock. The original time that it took for the dev community to get NAND unlocked for the Evo and Incredible was around two months. New HTC phones get S-OFF hacks within weeks. The bootloader for the Milestone still hasn't been fully unlocked yet and that phone is over a year old. The D2 and DX will probably never have their bootloaders unlocked because of eFuse.
What was with their statement about working on a solution for people interested in unlocked bootloaders? Why would they even make a statement like that?
I don't think HTC is immune to that either. Its never happened to me, but I've heard of some people's devices hanging on the white HTC screen. I'm guessing at that point they had to flash the RUU file. Which is sorta the HTC equivalent of Moto's SBF.If you can't boot past the m, you can't load bootstrap yes bootstrap works on bootloops, but it needs android to load to take over. In simple terms of your phone can't get to the boot animation get the sbf ready