So I've been looking into this, it seems it's possible to use flashify which allows you to flash .img files if your bootloader is locked and you have root you can flash twrp this way. Flashify can also make backup of stock recovery and install it, the reason i'm interested in this is security, as unlocked bootloaders have lots of risks.
Another post i was reading a person suggested, different manufacturers have different ways they implement locked bootloaders so some phones recovery might be protected and can't flash twrp while locked others may differ, I'm not sure. I currently have a Samsung S7 Edge Exynos, some people suggested issues around possible hard bricks, suggesting it's more likely to happen with a locked bootloader, then others saying fastboot wouldn't be able to recovery the device if installing a rom failed.
Someone pointed this out about my OEM unlock not been able to enable it to recover, tho odin doesn't require that to be turned on to flash back the stock firmware from download mode so that should fix that. I want to know the risks involved if flashify flashing twrp, kernels and roms while bootloader is locked is likely to work fine, i have seen posts of people who have done it most the comments seem like they could be assumptions best guesses around this type of thing. I can't find much on it.
What i'm thinking is find an exploit to get root, while locked flash twrp with flashify use twrp to flash xposed maybe? then restore stock recovery after flashing all the things i need, so if i loose the phone bootloader is locked and they don't have clear access to twrp, i think magisk is impossible as that modifys the boot which is the locked bootloader i believe so don't know which things magisk or others will or won't work.
I don't believe it's possible to unlock bootloader and install twrp flash everything i need restore stock recovery and relock the bootloader? pretty sure most phones delete all data during both lock, and unlock even so if it didn't delete everything dm-verity would likely prevent any of this working due to it been tied to the locked bootloader.
Appreciate all reply's.
Thanks.
Related
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!
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
I have searched everywhere for a way to get root without unlocking the bootloader. I want to enable double tap to wake on my wife's 6P, but I don't want to wipe her data during the bootloader unlock process. Thanks everyone for any help.
cagmuer said:
I have searched everywhere for a way to get root without unlocking the bootloader. I want to enable double tap to wake on my wife's 6P, but I don't want to wipe her data during the bootloader unlock process. Thanks everyone for any help.
Click to expand...
Click to collapse
No.
Sent from my Nexus 6P using Tapatalk
If you don't unlock the bootloader, you can't flash a custom recovery. If you can't flash a custom recovery, you can't install a custom rom or possibly the su binary. Unlocking essentially bypasses the verify process on boot; it verifies the rom, recovery, etc. is the signed official version. I've understood some tools may be able to allow root on an locked bootloader, but I'm not sure for the 6P.
Unless you care about Pay, just backup the phone and unlock it.
was hoping a dev could figure this out. i just want root for root apps and flashfire to flash things. kind of sucks having a nexus that requires an unlocked bootloader for root but i been on stock rom with locked bootloader after going two weeks with custom roms and no android pay. still hoping it will happen eventually.
rob219 said:
was hoping a dev could figure this out. i just want root for root apps and flashfire to flash things. kind of sucks having a nexus that requires an unlocked bootloader for root but i been on stock rom with locked bootloader after going two weeks with custom roms and no android pay. still hoping it will happen eventually.
Click to expand...
Click to collapse
People have had success using Android Pay on a rooted 6P. I think people use magisk and Phil's SU and they are able to hide root from Android Pay and other apps. You should do a search through the forums. A lot of people talk about doing it successfully.
Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Scandiacus said:
Had some issues with my camera recently and decided to do a nandroid restore. Restore didn't turn out well and I ended up with a factory reset device and here's where things get confusing for me.
1. I'm using the A2017G with B03.
2. TWRP installed and phone rooted, but bootloader LOCKED. Previously followed tenfar's guide back in August 2016.
3. Now my phone still has TWRP installed but no longer has root access. I wish to revert everything back to stock (i.e. stock recovery, everything) and do the proper method according to this guide but I do not know where to start as I don't even know the current state of my phone due to the locked bootloader. I fear that if I proceed with Controllerboy's consolidated guide, I may just brick my phone.
Appreciate any help rendered!
Click to expand...
Click to collapse
You can use the MiFlash file to unlock the bootloader just like Controllerboy says in his guide. You don't need to do the TWRP part since you already have it xd
There shouldn't be any trouble since, if you read his guide, you flash TWRP before unlocking the bootloader.
Edit: sorry he doesn't use MiFlash xd. Should still be the same, just use those images he provides to unlock it.
Otherwise you should be able to use MiFlash with some files that the Russians made, there's one called A2017U_FASTBOOT_UNLOCK_EDL which besides from probably unlocking your device, gives you Fastboot if you are on A2017G.
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.