I'm sorry but I have googled and searched here trying to get a clear answer, but I think it comes down to my lack of understanding.
What is the difference between the bootloader being locked vs unlocked and what does that mean for the development? I currently have the Acer Iconia and love it, but if there will be more/better development on the transformer I may switch.
I also want to try and figure this out as I have a Droid X and use the bootstrapper to load ROMS but again I do not have the understanding I think I need for this subject matter.
Thanks all for your work and contributions. XDA has taught me alot and I am trying to further my understanding so please forgive me if this is the wrong forum to ask this in.
Well i downloaded the latest update from asus and applied it to my tablet. I now can't use CWM on my SD, i could before.
There's three types out there right now:
Unlocked bootloader: You can flash whatever you want
Locked bootloader: It verifies a signature before flashing. Usually the signature check isn't all that hard to really defeat (the Thunderbolt's was defeated in somewhere around a day, IIRC).
The Droid X bootloader, on the other hand, is Encrypted, in addition to being Locked. This is the reason that you have to bootstrap custom roms, and can't just install them directly. Motorola is the only one that's using an Encrypted Bootloader, AFAIK.
Well i can help with the unlocking, I just need to know what to do.
KitsuneKnight said:
Motorola is the only one that's using an Encrypted Bootloader, AFAIK.
Click to expand...
Click to collapse
Nop, Sony Ericsson also encrypt their bootloader in all 2010 Xperia Series
Related
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
It prevents root access, you know jail breaking. You can't control your rom. You use the one provided to you by Verizon with all their bloatware. You can't change what software was delivered to you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
It prevents changing boot.img
Sent from my SCH-I535 using xda app-developers app
saucyzest said:
Noob question I know but I've tried reading up on the subject as much as I can - I still don't fully understand what exactly the locked loader does to this phone (aside from making it more difficult to root) and would really appreciate a brief explanation.
As I understand now the phone can be rooted, ROMs can be loaded (but they have to be specific to the VZW S3 right?), and full recovery options as well. Basically wondering what the disadvantages are and if they're more significant than just a little more work to root/mod the phone? Much thanks!
Click to expand...
Click to collapse
A locked bootloader is ultimately intended to prevent you from potentially costing the carrier $money$ by:
Bricking your phone and then playing dumb when you return it for an exchange. (people on xda opening admit to this kind of fraud. kinda sad. you brick it you keep it!, or buy another)
Modifying your phone and then blaming bugs on the carrier. A support vampire.
Assuring content providers they've made exclusive deals with that their content is "secure".
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thank you for this explanation, I found it helpful to hear such an analogy.
jmacko said:
Great Question!
If your phone was a Windows 7 computer....
If you rooted it, you'd have an account with Administrator access.
As for the bootloader... Suppose you wanted to upgrade to Windows 8, even though it hasn't been authorized by your ISP, on this Windows 7 computer with a locked bootloader.
You cant, c:\windows is locked. If you change anything in that directory, your Windows 7 computer will start, but only to display "Invalid System Software Installed! Please shutdown and return this computer to your ISP's store for assistance."
What we have on Verizon, is a phone with admin rights (rooted), where we can't re-install the software needed to boot a different operating system.
If you're interested in more detail on how the hardware prevents the bootloader from being cracked, and what the attack vectors are, you might be interested in the presentation linked from this post http://forum.xda-developers.com/showthread.php?t=1766638
(And yes I know that c:\windows isn't actually the boot partition on windows. Just trying to make it easier for the OP to understand.)
Click to expand...
Click to collapse
Thanks that really helped. So in the example of Jelly Bean -sounds like we need to wait for Verizon to release a version of it? Do all custom ROMs as well have to be based off of the VZW file that checks ok with the bootloader?
I'm really only concerned with Jelly Bean (knowing how long VZW takes to release stuff) and that wifi nag screen, I want to punch someone in the nose every time i see it...I will check out that presentation over lunch, would love to learn all about the details.
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Bfitz26 said:
interesting and helpful topic.. however.. i thought i understood the locked bootloader situation on my droid bionic i could flash any rom i wanted to in conjunction with bootstrap wich i believe to be a bootloader by pass based recovery but no kernals were able to be flashed that is what i understood to be a locked b.l was not overclocking or custom kernals maybe i was wrong this whole time..
Click to expand...
Click to collapse
Weird this is how i understood it as well. I'm coming from the Droid X2 and thanks do DK we had cm9 up and running with ICS but the bootloader was locked down. I took it that bootstrap is a recovery tool that works in a way of when your phone is off and you plug it in you boot up to the bootloader. This would allow you to re-flash a rom if your current one was corrupt.
So in my mind you can run different roms and different android versions its just harder to get them on the phone. But from what i've seen you cant flash a new kernal if the bootloader is locked.
Maybe i miss understood this if so i really would like to know fully how this works
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
droidstyle said:
On the verizon gs3 the locked bootloader is keeping us from flashing a custom kernel thru odin...we can root and flash a custom rom / recovery but it has to utilize the stock kernel currently. Our bootloader debacle is nothing like moto devices and I wish folks would stop comparing the 2!
Click to expand...
Click to collapse
Exactly, what a locked bootloader will allow you to do will vary on different phones and firmwares. I've known some which would not even allow you to flash a recovery.
Sent from my SAMSUNG-SGH-I747 using xda premium
I really hope we get the bootloader unlocked would love to see cm on this phone with some of invisblek's great kernels. btw will I be able to even usrge "set cpu" to overclock and under clock with verizon stock kernal or can this be done with tweaks in the build.prop file, forgive me if this sounds stupid its been a while and I am a samsung's odin first time user.
Sadly this is the outcome of Americans NOT buying a device without a subsidy from the carrier.
Kind of like whining about NOT getting the best Porterhouse steak when buying with food stamps......
I would love to see an end to carrier subsidies.
~~~Sent from the 23rd century, thru a Samsung Onehunglow powered by Walmart brand Higgs Boson particles. (Aisle 27)~~~
I am disappointed in samsung they start to look like Apple can not my apps to my sd card write that they have locked that 2
Hi all,
Im thinking of buying the A210 (the little brother of the 510). However I'm never again going to buy a device which I can't root or which has a locked bootloader.
Since there is no specific info on the A210 yet, I'm wondering how root-friendly Acer as a company is, and if they allow unlocked bootloader with their newest devices. Using the search leads me to believe that unlocking on the A510 is only possible d/t an old firmware version, and not really intented by Acer.
Any comments appreciated, and my apologies if this should be the wrong section.
Thanks!
I think acer is not so strict with root and bootload unlock, don't worry.
I have been able to successfully unlock the bootloader on my up-to-date A510 using fastboot's oem-unlock feature, so I'd say it's definitely possible without any issues
Liquidator said:
I have been able to successfully unlock the bootloader on my up-to-date A510 using fastboot's oem-unlock feature, so I'd say it's definitely possible without any issues
Click to expand...
Click to collapse
Wow thanks guys this is really great - I had the impression that the Acers can only be unlocked by downgrading to older, non-locked firmware versions.
Your experience gives me hope that the A210 bootloader will also not be locked.
maxmax0 said:
Hi all,
Im thinking of buying the A210 (the little brother of the 510). However I'm never again going to buy a device which I can't root or which has a locked bootloader.
Since there is no specific info on the A210 yet, I'm wondering how root-friendly Acer as a company is, and if they allow unlocked bootloader with their newest devices. Using the search leads me to believe that unlocking on the A510 is only possible d/t an old firmware version, and not really intented by Acer.
Any comments appreciated, and my apologies if this should be the wrong section.
Thanks!
Click to expand...
Click to collapse
You can unlock the Bootloader of the A210 easy:
Code:
adb reboot-bootloader
fastboot oem unlock
and then do that what is shown on the Display. Use VOL - to selct und VOL + to confirm!
But no root or custom ROM available currently
Hi xdadevelpers team unfortunately i have installed an unoficial rom for my device from this link http://forum.xda-developers.com/showthread.php?t=2069935 it works very good and no thing wrong with it but i have to send my phone to the Authorized agent here in egypt because of a problem at the sim card place in the phone so i need to get back to the official kernal which is ics is there any way to do this please help me
have you noticed, that this is the Razr HD section ?
And yes. MOAR fonts
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Xadro said:
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Click to expand...
Click to collapse
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
mostafas60 said:
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
Click to expand...
Click to collapse
What do you mean by saved cid? Is your phone carrier locked? Or what are you trying to say? You should pick a stock fw, which is at least your country/region better also from your carrier. It may also not be available at the site i mentioned.
If it is not available you could try and make a request. See the op of this thread
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Uh thanks for the heads up, wasn't aware of that. I assumed that motorola devices would be all similiar with this.
cellzealot said:
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Click to expand...
Click to collapse
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
mostafas60 said:
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
Click to expand...
Click to collapse
guys is there any one can answer me and how to solve this issue
http://forum.xda-developers.com/forumdisplay.php?f=1622
mostafas60 said:
guys is there any one can answer me and how to solve this issue
Click to expand...
Click to collapse
Probably if you go to the right forum man.
Sent from my PACMAN MATRIX HD MAXX
Hey Guys, I decide to unlock the bootloader and root my Moto G so i start to read about it and preparing everything to do it in my pc (drivers, etc)
But when i start to read de Resource Guide Thread in the General forum i read something that confuse me specifically in the Root part that says:
"If you do not have or do not wish to unlock your bootloader then you can opt for @oasoas014 's method ( http://forum.xda-developers.com/showthread.php?t=2583652 ) of bootloader downgrade. You may also visit @Cooptx's more detailed guide ( http://forum.xda-developers.com/showthread.php?t=2585755 ) . Note, with the most recent recoveries, you do not need to downgrade your bootload"
But reading the @Cooptx's method says that need unlock bootloader, i really dont understand the @oasoas014 's method but reading all the comments says also that i need unlock bootloader.
So im kinda confuse here, is that im not reading well? or i just need to unlock it? someone can give me a strait answer?
You must unlock bootloader if you want root, there is not other solution for moto g atm. Maybe in future there will be an exploit to root bypassing bootloader like on moto x but not now.
Thanks you, the info is kinda confuse, im gonna put me in to work. Hope eveything goes well
bozzett0 said:
Thanks you, the info is kinda confuse, im gonna put me in to work. Hope eveything goes well
Click to expand...
Click to collapse
It's not that much work and Motorola makes it really easy to unlock the bootloader If you still need some help or run into trouble let us know!
hey
i tried to unlock bootloader via motorola web site but it says my device does not qualify for unlocking
tried flashing recoveries, root zips and updated to official kitkat, but still does not work
phoned motorola support and they said motorola doesn't guarantee bootloaded getting unlocked, it depends on luck
any suggestion?
Moto XT1033 Dual 16gb BR
pedrofortunato said:
hey
i tried to unlock bootloader via motorola web site but it says my device does not qualify for unlocking
tried flashing recoveries, root zips and updated to official kitkat, but still does not work
phoned motorola support and they said motorola doesn't guarantee bootloaded getting unlocked, it depends on luck
any suggestion?
Moto XT1033 Dual 16gb BR
Click to expand...
Click to collapse
Did they use the word " luck "?
Sent from Samsung Chat
jaspreet997 said:
Did they use the word " luck "?
Sent from Samsung Chat
Click to expand...
Click to collapse
not that word but she said it might work as it might not work, and there's nothing me or motorola could do about it
I became owner of RAZR HD recently, unfortunatelly locked with latest firmware. I have some basic knowledge in reverse engineering and kernel development, so I decided to look into Dan Rosenberg's work. My question is are there any devs/hobbists who played with it? I tried to contact Dan but he's not responding, so I guess I'm all alone with it, am I? I'm especially interested in smc command handling. Any insight would be greatly appreciated.
Regards,
Krystian
krystianp said:
I became owner of RAZR HD recently, unfortunatelly locked with latest firmware. I have some basic knowledge in reverse engineering and kernel development, so I decided to look into Dan Rosenberg's work. My question is are there any devs/hobbists who played with it? I tried to contact Dan but he's not responding, so I guess I'm all alone with it, am I? I'm especially interested in smc command handling. Any insight would be greatly appreciated.
Regards,
Krystian
Click to expand...
Click to collapse
No one is wanting to go back into unlocking another bootloader, rather you should try looking into downgrading the trustzone (tz) partition to the unlockable version. That would be greatly appreciated.
Playb3yond said:
No one is wanting to go back into unlocking another bootloader, rather you should try looking into downgrading the trustzone (tz) partition to the unlockable version. That would be greatly appreciated.
Click to expand...
Click to collapse
You might not want to go back but I do want to go back into unlocking another bootloader. Why do you think downgrading trustzone partition would be easier than exploiting bootloader?
krystianp said:
You might not want to go back but I do want to go back into unlocking another bootloader. Why do you think downgrading trustzone partition would be easier than exploiting bootloader?
Click to expand...
Click to collapse
kexec might be easier than finding another qcom exploit to unlock the bootloader. Hashcode was giving it a shot, but without uart he was working blind and then Dan's exploit changed everything.
Beware of downgrading since you're locked. I remember a few bricking on the Atrix hd.
krystianp said:
You might not want to go back but I do want to go back into unlocking another bootloader. Why do you think downgrading trustzone partition would be easier than exploiting bootloader?
Click to expand...
Click to collapse
The problem is, Dan's work was finding an exploit. Pure and simple. it was not meant to happen, but he found a way to make it happen. Once Moto knew of this, they put out a patch so that anyone in the future who hadn't unlocked their bootloader would never be able to again. That exploit was a million in one chance of being there. It's not like he cracked the encryption key. That's an even more impossible feat.
No developer is going to put their time and effort into an old phone like the RAZR HD.
Kexec would be nice (using Safestrap recovery like on the RAZR and RAZR MAXX XT912 phones), but even that takes time to figure out how to make it work. I doubt people are willing to put much time and effort into this what with all the new phones that have been released since the HD was released.