If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you
AndrewDam said:
If I locked my bootloader, can I update SuperSU (zip) or TWRP (img) using TWRP --> Install?
I'm already aware that it won't allow me to flash custom ROMs, custom recoveries or use fastboot commands.
What does having a locked bootloader prevent me from doing?
Thank you
Click to expand...
Click to collapse
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.
murphyjasonc said:
The better question is why would you have a locked bootloader? If you have any kind of boot loop or error you will end up with a paper weight that will have to be sent off for repairs when its easily fixed with an unlocked bootloader.
Click to expand...
Click to collapse
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
I would say it's much more likely you brick your phone due to having a locked bootloader than someone else getting their hands on your phone and actually having the knowledge to cause trouble for you.
to relock your bootloader you must have FULLY STOCK firmware back on your device, relocking with anything in the phone being custom can result in a paperweight
Having a rooted phone is more vulnerable than a unlocked bl phone. Dont lock bl back unless you are full stock (I would still say dont though)
AndrewDam said:
You're right about having a boot loop problem but isn't the phone more secure with a locked bootloader though? I read that it's recommended that you relock the bootloader if you're done making modifications so that no one can do anything malicious with your phone (to some extent).
Click to expand...
Click to collapse
It's more secure, sure. But if you take care of your phone it doesn't fall into the wrong hands. Plus, if you have TWRP installed still a tech savvy thief (one who understands what a locked bootloader means) can easily flash a ROM and boot into the phone. As sometime else pointed out, the chances of you ending up with a brick are higher than the chances of someone getting your phone.
Sent from my Nexus 6P
Ok that makes sense to not lock the bootloader. Thanks for the information everyone!
Related
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Zalmoxis12 said:
But what is it exactly? What does it mean?
I mean I already did Autorec and all I know is that it downgraded the bootloader. No idea what that actually means, so I can understand what happened and more importantly how can I restore it (i.e upgrade it back) and what are the consequences of these actions.
Any developer around that can actually explain?
Click to expand...
Click to collapse
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
simon_lefisch said:
Jellybean (12B) was the last bootloader to be able to be used with loki (the exploit to be able to flash custom recoveries/ROMs/kernels). Google patched the bootloader in the KitKat update (24A) so loki was useless. You could root, but couldn't flash the previously mentioned items. Being able to downgrade the bootloader allowed this. So even tho you'd be running KK, you're using a JB bootloader.
Click to expand...
Click to collapse
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
http://searchenterpriselinux.techtarget.com/definition/boot-loader
Zalmoxis12 said:
I know this. I was asking what the bootloader actually is and how does it relate and connect with the other partitions.
Is it like some sort of MBR?
Click to expand...
Click to collapse
bootloader loads all the partitions and makes sure they work together, two examples of the stuff bootloader handles:
-bootloader boots
-bootloader then loads kernel making sure nothing wrong and if there is then you get no boot and instead you are thrown to fastboot to fix the problem
-after kernel loads bootloader loads system if corrupted/missing you get stuck in a bootloop unless you have custom recovery then you get stuck in recovery
-bootloader loads rest of partitions while the system/kernel begin to boot rom
when doing ota:
-phone reboots and loads bootloader
-bootloader loads ota into a partition on phone designed to decompile and apply ota into system/kernel partitions
-bootloader makes sure that system/ota are correct and compatible to apply update
-bootloader does root check process in the rtf partition and if rooted bootloader cancels ota process
so in short bootloader is most important asset, it is what decides the kernel to boot(you can mod a bootloader so that you can have too kernels and this is also how you create multi boot for boot more than one rom), it boots the rom, and it handles all other partitions in more than one way
please any body suggest me an easy way(any way) to unlock boot loader and root my device,my ultimate wish is to root my device to remove bloatware. I searched the entire forum for a way to root my device but there are lot of conflicting opinions some say unlocked boot loader is a must for root , some threads say root is required for unlocking the boot loader,i am confused ,please give some advice by witch i can ultimately root my device
my device- ZE550KL
OS - MARSHMALLOW 6.0.1
with locked boot loader and unrooted
2GB ram
I will be grateful to you and ill be glad
I don't know if you can get root if you are on MM without fully switching to CM13.
I think it's pretty "easy", it's depend from the person to person though
There's already thread to unlock BL (no relock atm), and getting root is simply flash supersu.zip
It's just my thoughts, I'm not saying you must do what I'm going to write down here, so I'm not responsible if anything happen
* You need, say TWRP, to get root, how to get TWRP? "flash" recovery right?
* flash custom img (recovery) only possible if BL unlocked, you got bootloop if still locked
* so what if we just boot to twrp? Leave that stock recovery? We don't need that unlocked BL right?
* then the problem come from supersu, default su installation on M+ come in "systemless" mode, which modifying the boot.img, as point 2 above, we can't have non-stock img flashed on locked BL
* so how about make supersu "system", it did work on L with locked BL anyway, it's not modifying any boot.img,
* you could got root w/o unlocking BL by booting twrp, and flash su in system mode
Personally I'm not able to test this, because I love breaking things :silly:
Sent from my ASUS_Z00RD using XDA Labs
testeraphy said:
There's already thread to unlock BL (no relock atm), and getting root is simply flash supersu.zip
Click to expand...
Click to collapse
Can you point me to this? I can't seem to find it
THanks
Brett8187 said:
Can you point me to this? I can't seem to find it
THanks
Click to expand...
Click to collapse
Really? I don't even need the search function to find this
http://forum.xda-developers.com/zen...de-unlock-bootloader-asus-unlock-app-t3405850
*ooh, I should studying using forum tags
Sent from my ASUS_Z00RD using XDA Labs
Hi everyone,
While trying to upgrade my device to stock Android 7.1.1, I've forgotten to flash the boot image. All the other components have been correctly flashed (system, bootloader, radio, etc.), but I was not careful enough and I forgot to flash the boot image. The problem is I've decided to relock my bootloader (silly me) right afterwards and now the device is in a bootloop (as the current boot image comes from the custom ROM that was installed previously). Naturally, I cannot unlock my bootloader again as it says "OEM unlock is not allowed". Am I screwed? Any ideas on how to unlock my bootloader? After many years of flashing, this is the first time I'm in a real trouble. Thanks for your help!
Yup u may at a lose if the Bootloader is locked then I don't think u can flash anything that's why it's recommended not to Relock the Bootloader bc if you phone doesn't boot for some reason then there's nothing u can do but to RMA it if u still have warranty. If not then sell as parts
Sent from my Pixel XL using Tapatalk
Thanks for your input! I will have it RMA'ed, so it's not a huge deal, but I was wondering whether there was a way of troubleshooting this. But I guess that's not possible. Cheers!
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.
matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!
Why do you want to downgrade?
rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.
Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
zroice said:
Hey guys,
want to mod my freshly bought Mi A1 to the max, but I'm not sure if i should OTA first or better start modding right away?
I already unlocked the bootloader and it didnt wipe it - it also has 7.1 installed still. Generally I'm usually reluctant to do official updates because they usually make modding harder - but I tried booting the treble TWRP installer .img through fastboot (without installing it) and it failed because some partition was missing it said.. so I just want to hear if OTA is necessary to use the latest custom roms or if i can keep the old bootloader etc?
Would be cool if someone who knows could say smth about that.
Or is updating through OTA actually recommended even when not planning to ever use stock roms?
Click to expand...
Click to collapse
If security matters for you yes
The only thing you'll share with a custom ROM is the bootloader
Since may update locking or relocking the bootloader will wipe your data
It's your choice
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
You have to enable it in Developer settings.
zroice said:
but it will still work as easy as before to unlock/lock with just a fastboot command, right?
and will a custom rom work with a locked bootloader? Like first unlock, install custom rom + kernel, then relock?
Click to expand...
Click to collapse
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Dead-neM said:
It will always be that easy to unlock and relock the bootloader
No don't relock on anything that is out of stock (custom kernel , magisk, custom ROM etc) this will lead to a softbrick and you'll have to be on edl more to reflash a stock rom
What's the interest of having a locked bootloader with a custom ROM? You won't pass the safety net anyway
Just keep it unlock
You can do ota with an unlocked bootloader
Click to expand...
Click to collapse
alright. thanks very much for explaining in details - exactly what i was looking for.
What's the use of your android one device if you will not update it, that's what you pay for.
HidekiRyuga said:
What's the use of your android one device if you will not update it, that's what you pay for.
Click to expand...
Click to collapse
hahahaaa exactly the point :laugh:
well once you have everything "perfectly set up" updates can ruin it. but yea relocking the bootloader really was a stupid idea - it was the idea to make it tamper proof but since custom kernels wont boot with locked bootloader that wouldnt work.