Why are some devices coming with locked bootloaders and others unlocked? All of the Google I/O devices seem to be unlocked, but I've read mixed things on retail devices. Some have locked bootloaders while others have unlocked ones.
Are the locked bootloaders unlockable?
If I understand correctly, devices with locked bootloaders can still obtain root, but the disadvantage is that custom kernels cannot be flashed. Is this a correct assumption?
The truth is nobody knows why some are locked and some are not. And as far as we know, the only way to unlock is by using signed keys from Samsung, which nobody has. As far as root and kernels are concerned, you are right. Locked bootloaders can be rooted, but the kernel cannot be switched out
Sent from my SCH-I500 using XDA App
Thanks for the info.
Can you define custom kernel? My Samsung captivate is locked but I can flash a miui or cm7 kernel as well as the European version kernel of my phone.
I'm locked on the tablet but I can flash pershoot kernel.
Still unsure the disadvantage of my locked bootloader
Sent from my GT-P7510 using XDA Premium App
nakedninja42 said:
Can you define custom kernel? My Samsung captivate is locked but I can flash a miui or cm7 kernel as well as the European version kernel of my phone.
I'm locked on the tablet but I can flash pershoot kernel.
Still unsure the disadvantage of my locked bootloader
Click to expand...
Click to collapse
The only thing you can't do with a locked Tab is use nvflash. The bootloader boots unsigned kernels and initrds. The locked bootloader will even let you ODIN in your own recovery so you can flash unsigned zips.
pokey9000 said:
The only thing you can't do with a locked Tab is use nvflash. The bootloader boots unsigned kernels and initrds. The locked bootloader will even let you ODIN in your own recovery so you can flash unsigned zips.
Click to expand...
Click to collapse
Thanks! I figured out the nvflash the first day trying to root and then later tried to use supercurio kernel, it kept me from flashing. But since I was able to use odin to do everything else and get CWM, I saw no disadvantage.
If I were take supercurio kernel and build it so its zipped for CWM, I can flash the kernel or am I missing the point?
Is there a way to find out of bootloader is locked?
cnewsgrp said:
Is there a way to find out of bootloader is locked?
Click to expand...
Click to collapse
If you use an unlocked padlock during bootup then you are unlocked. If nothing shows up, your locked.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
pokey9000 said:
The only thing you can't do with a locked Tab is use nvflash. The bootloader boots unsigned kernels and initrds. The locked bootloader will even let you ODIN in your own recovery so you can flash unsigned zips.
Click to expand...
Click to collapse
Well screw me. Learn something new everyday!
cnewsgrp said:
Is there a way to find out of bootloader is locked?
Click to expand...
Click to collapse
for the previous version of the tab there was an app developed from rotohammer that would tell you if the bootloader was locked or not. not sure about the 10.1.
I don't think the padlock thing apply to it though... Maybe someone else here has a better answer.
That patch will not work on Galaxy Tab 10.1 ,
I have a Galaxy Tab 10.1 , in which i want to flash a customized kernel (downloaded the source code from opensource.samsung.com) but my bootloader is locked , and I am not even able to get the backup of my kernel image with the help SGS Kernel flasher, does all this because of locked bootloader ?
Any one have any idea how i should proceed to unlock my Tab and flashed custom kernel ?
Related
hey, just wanting to clarify things before i start messing around with flashing. I want to install a custom rom, so ive read guides on rooting and installing recovery, as well as unlocking the bootloader. now i just want to know, if i am rooted and have recovery installed, do i also need to unlock the bootloaders to flash a new rom in recovery, or is that enough to do it. thanks for any feedback
-edit: i noticed looking at the custom roms, it specifies in the topic whether it is for a locked or unlocked bootloader.. so im guessing i just have to choose whether i want to unlock it or lock it depending on the rom i want
That is enough you don't need to unlock bl just be sure to flash a Rom for locked bl
Sent from my X10i using XDA Premium App
I wouls like to install ICS or JB on my Photon.
However, it is 2.3.5 locked BL.
Any version that works with that ?
Thanks
It can't happen. With a locked bootloader you can only use the stock kernel.
why ? My friend have a DROID 3 running ICS
badgett said:
It can't happen. With a locked bootloader you can only use the stock kernel.
Click to expand...
Click to collapse
and the bootloader is still locked.
iaracy said:
and the bootloader is still locked.
Click to expand...
Click to collapse
until an unlocked bootloader is leaked from motorola or someone can find a work around. you will never be able to flash anything other than a stock rom. i think everyone has given up on unlocking the bootloader. the electrify has had a locked bootloader for a year and still nothing. so don't expect anything soon if ever. sorry. :crying:
Is it possible to use custom ROMs without an unlocked bootloader?
Theoretically, yes. I did on my previous phone. A dev would have to cook a Rom with the stock kernel, etc.
tribalartgod said:
Theoretically, yes. I did on my previous phone. A dev would have to cook a Rom with the stock kernel, etc.
Click to expand...
Click to collapse
could you explain a little more?
because i tried running cyanogenmod on my device but it showed up a security error, which i read somewhere is cause by a locked bootloader
dhruvbatra205 said:
could you explain a little more?
because i tried running cyanogenmod on my device but it showed up a security error, which i read somewhere is cause by a locked bootloader
Click to expand...
Click to collapse
Basically, when a ROM is made... It's either made from 100% scratch, or it's made with another ROM as it's base. For example...Paranoid Android used to be CM based... Meaning it used certain aspects of the CM ROM, but with the look/feel/features of it's own. So for this to work ona locked bootloader, the ROM cooker would have to use Stock as their base, and build up from there... I'm not a developer, so I can't go into extreme detail on this, I'm sorry.
But to properly answer your question... Yes, it is possible to do this... Will it happen?? Probably not, unless someone takes the time to port something over.
You got a security error, because CM changes things from the Stock base... So since it's not build from stock, it won't work unless the bootloader is unlocked, OR unless someone rebuilds it with the stock ROM as it's base.
For anyone else reading this... I hear MIUI is relatively easy to port onto a stock base...
okay. last thing. what 'changes' does the locked bootloader detect that it shows up a security error?
Boot.img has to be signed by LG. Not signed= security error. There is probably more to it than that but that is my understanding.
Sent from my LG-P769 using xda premium
Tablechair said:
Boot.img has to be signed by LG. Not signed= security error. There is probably more to it than that but that is my understanding.
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
So, do you think it might not be an unnecessarily tough and time consuming job to port cyanogenmod in such a way that it would work on a locked bootloader device?
dhruvbatra205 said:
So, do you think it might not be an unnecessarily tough and time consuming job to port cyanogenmod in such a way that it would work on a locked bootloader device?
Click to expand...
Click to collapse
It's do-able... But may be pretty time consuming... If you have never ported before, I suggest starting with MIUI v4. From what I read, it's relatively easy. I know for a fact that MIUI, if ported properly, will work on locked bootloader, as my previous phone ran it with locked bootloader.
There is a workaround here. http://forum.xda-developers.com/showthread.php?t=2099238
Artas and markolino had CM9 working on locked bootloader P760. Anyone interested in trying to port a ROM this way should definitely check out that link.
Sent from my LG-P769 using xda premium
I have a doubt reguarding bootloader unlocking.
It is possible to flash custom recovery using fastboot, and then flash any rom using recovery.
Then is there any need for boot loader unlocking specially??
I flashed recovery using fastboot mode without any special steps of unlocking bbootloader.
And plz tell what is the good way of flashing recovery- through stock recovery or through fastboot mode or terminal or certain tools(mtk)
I have rooted my phone oneplus x using kingroot.... It is rooted.... I have checked it with root checker.... I have installed TWRP on my phone too... N i want to flash the paranoid android 6.0.1 on it.... I have downloaded it along with gapps package........ Now i want to flash ut but i am in doubt wheather it will flash properly because i haven't unlocked my bootloader..... So will i be able to flash this rom without unlocking my phone???
If you're higher than vrajb is it possible to unlock the Verizon Note 2 without unlocking the bootloader?
universexda said:
If you're higher than vraljb is it possible to unlock the Verizon Note 2 without unlocking the bootloader?
Click to expand...
Click to collapse
I don't understand. Are you having a problem unlocking your bootloader. Or just don't want to, but want to flash your custom rom. without the bootloader being unlocked you will have to flash certing things like the kernel manually everytime you flash a rom.
dragonstalker said:
I don't understand. Are you having a problem unlocking your bootloader. Or just don't want to, but want to flash your custom rom. without the bootloader being unlocked you will have to flash certing things like the kernel manually everytime you flash a rom.
Click to expand...
Click to collapse
Actually I've already unlocked and rooted using Outler/Radeklav's method, but I'd like to know for other people who have asked if it's possible to root, keep stock ROM and keep the bootloader unlocked for above vrajb phones. (I know you can do it for vrajb phones using the Exynos exploit.)
universexda said:
If you're higher than vrajb is it possible to unlock the Verizon Note 2 without unlocking the bootloader?
Click to expand...
Click to collapse
The only way to root only on VRAMC3 is with the Toolkit, there are mixed results with it though. Some say it works great and some say it doesn't work at all, in the end the people that just want root can try that and if it doesn't work they should just root and unlock the bootloader with CASUAL and if they don't want to mess with flashing they don't have to. There are really no downsides to having an unlocked boot loader aside from not being able to accept and install OTAs, that's a plus in my book though.
Sent from my SCH-I605 using XDA Premium HD app
shangrila500 said:
The only way to root only on VRAMC3 is with the Toolkit, there are mixed results with it though. Some say it works great and some say it doesn't work at all, in the end the people that just want root can try that and if it doesn't work they should just root and unlock the bootloader with CASUAL and if they don't want to mess with flashing they don't have to. There are really no downsides to having an unlocked boot loader aside from not being able to accept and install OTAs, that's a plus in my book though.
Click to expand...
Click to collapse
Thanks for the word.
Hi, sorry but I'm confused reading about rooting in regards to DRM keys, TA partitions and what method works with the latest firmware.
I've upgraded my firmware to the latest generic. 314 AU firmware and my phone came with the bootloader unlocked.
I want to root now and am confused as to whether I will
1.lose warranty
2.be able to restore to factory if I need to send it back for repairs
3.lose anything else
4.what method I need to use to get root with my firmware.
Thanks
Sent from my D6503 using XDA Free mobile app
Do you mean that your phone's bootloader is unlockable (i.e. can be unlocked if you wish) or do you mean that it has already been unlocked?
You'll lose warranty only if the bootloader has been unlocked. If you just root the phone (and keep the bootloader locked), then you still have your warranty.
You can restore to factory simply by using the repair function in PC Companion.
Root will not cause you to lose anything. But unlocking the bootloader will remove the DRM keys and TA partition.
Use the rootkitXperia tool to root your phone.
Sorry, I meant the bootloader is allowed to be unlocked, it isn't unlocked yet.
Do I even need to unlock it seeings as you can get root without unlocking it?
Sent from my D6503 using XDA Free mobile app
kotton666 said:
Sorry, I meant the bootloader is allowed to be unlocked, it isn't unlocked yet.
Do I even need to unlock it seeings as you can get root without unlocking it?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
you do not need to unlock your bootloader for many things
-root
-recovery
-stock based roms
-mods
-root apps
-etc
flashing a custom kernel or non stock based rom requires you to unlock your bootloader, as flashing a kernel or non stock based custom rom will brick your device
Envious_Data said:
you do not need to unlock your bootloader for many things
-root
-recovery
-stock based roms
-mods
-root apps
-etc
flashing a custom kernel or non stock based rom requires you to unlock your bootloader, as flashing a kernel or non stock based custom rom will brick your device
Click to expand...
Click to collapse
Ahh ok. I essentially want root for a couple of mods and root apps as well as ad blocking.
So if I decide in the future to try a custom rom then I should unlock the bootloader before doing so?
Sent from my D6503 using XDA Free mobile app
kotton666 said:
Ahh ok. I essentially want root for a couple of mods and root apps as well as ad blocking.
So if I decide in the future to try a custom rom then I should unlock the bootloader before doing so?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Right. But before unlocking bootloader make sure to backup your TA partition so your DRM keys and other essential files needed for warranty is still intact. You can use TA Backup tool to unlock and re-lock BL.
Re-locking bootloader will bring back your warranty but once you unlock your bootloader and you did not back it up, you cannot bring back and you'll permanently loose warranty.
DrearierJester1 said:
Right. But before unlocking bootloader make sure to backup your TA partition so your DRM keys and other essential files needed for warranty is still intact. You can use TA Backup tool to unlock and re-lock BL.
Re-locking bootloader will bring back your warranty but once you unlock your bootloader and you did not back it up, you cannot bring back and you'll permanently loose warranty.
Click to expand...
Click to collapse
Thanks for the reply guys, much appreciated. It's a lot clearer for me now.
Sent from my D6503 using XDA Free mobile app
Envious_Data said:
flashing a custom kernel or non stock based rom requires you to unlock your bootloader, as flashing a kernel or non stock based custom rom will brick your device
Click to expand...
Click to collapse
I assume you mean, may rather than will?
ghostofcain said:
I assume you mean, may rather than will?
Click to expand...
Click to collapse
i mean Will instead of may.
flashing a custom kernel or non stock based rom to a device with a locked bootloader will brick your device.
english isnt my strong suit, i know that "may" isnt a solid word, will is more solid implying that it will always happen...
Envious_Data said:
i mean Will instead of may.
flashing a custom kernel or non stock based rom to a device with a locked bootloader will brick your device.
english isnt my strong suit, i know that "may" isnt a solid word, will is more solid implying that it will always happen...
Click to expand...
Click to collapse
Flashing a custom kernel on a locked bootloader will fail, not brick your device.
ghostofcain said:
Flashing a custom kernel on a locked bootloader will fail, not brick your device.
Click to expand...
Click to collapse
that doesnt make sense to me
it fails to boot, you can flash a kernel on a locked bootloader, the signature verifacation i do belive just doesnt like non existant or custom signatures
the result is a soft bricked device, its why i said it will brick your device, i may not have specified weather it was a soft or a hardbrick because both can happen from flashing a Rom or a Kernel to a device which its not ment for
im having trouble understanding you here?
my point being that you cant flash a Z2 rom or kernel to a Z1 and you cant flash a Z1 rom to a Z, cross-flashing isnt somethig to ever do
Envious_Data said:
that doesnt make sense to me
it fails to boot, you can flash a kernel on a locked bootloader, the signature verifacation i do belive just doesnt like non existant or custom signatures
the result is a soft bricked device, its why i said it will brick your device, i may not have specified weather it was a soft or a hardbrick because both can happen from flashing a Rom or a Kernel to a device which its not ment for
im having trouble understanding you here?
my point being that you cant flash a Z2 rom or kernel to a Z1 and you cant flash a Z1 rom to a Z, cross-flashing isnt somethig to ever do
Click to expand...
Click to collapse
Sorry it's me who's got it wrong, I assumed by brick you'd meant hard brick and I'd misunderstood the issue with flashing kernel on bootloader locked devices.
So let's agree, Don't try and flash kernels or custom roms with custom kernels on locked bootloader devices.