I just got this phone and while I would like to keep it completely stock for a while, I would prefer unlocking the bootloader immediately.
The reason for it is that I would like to avoid the hassle of getting everything back after a complete wipe and also avoid dealing with the bank for their app.
What are the consequences of only unlocking the bootloader but keeping stock recovery?
I've read about the FP issue but it's supposed to be fixed now I assume?
If it's only about losing Widevine security, then I wouldn't mind it, but are there other drawbacks?
Related
Hello Guys
Do you relock the bootloader after root of nexus 6?
It's probably not the best idea. Though now the "OEM unlocking" option seems to stick after a reboot on 5.1+ it's probably not as risky as it was.
Oniska said:
Hello Guys
Do you relock the bootloader after root of nexus 6?
Click to expand...
Click to collapse
I'm going to go ahead and just say no. No reason to relock other than RMA or resale. Best to leave unlocked just because if you run into issues, it's much easier to recover if your bootloader is unlocked.
Never relock unless you are on a stock image
I have never relocked a bootloader, ever.
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Rakeesh_j said:
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Click to expand...
Click to collapse
the problem is if your bootloader is locked, and you ho into a bootloop for amy reason, and your oem unlock option is not enabled in the developer options, then you bricked your phone. most people that lock their bootloaders, or have them locked, dont enable the oem unlick option. if thats not enabled, and youre in a bootloop, you cant flash a factory image or do anything else to fix it.
Rakeesh_j said:
Old thread I realize, but wouldn't this be useful to keep the anti-theft feature intact while rooted? And furthermore, does it actually work? I.e. does it leave root intact after it's locked but forbid flashing new roms to circumvent anti-theft. (I own a Nexus 6P by the way, but imagine the regular 6 has an updated bootloader with the same features.)
Click to expand...
Click to collapse
If you are encrypted, the only thing a locked bootloader adds is the ability to flash a custom boot.img that can decrypt your data (which doesn't exist). It's a very hypothetical scenario. The problems with locking the bootloader are as mentioned above by @simms22
So, I have a Global MI 8, with stock rom, on MIUI 10.2.3, locked bootloader.
I was contemplating rooting, since i always have rooted phones.
Was looking into some tutorials, and i have a couple of questions, that are still the things that are preventing me to move on with this.
1) In some tutorials, as part of the process to Flash Magisk, it is mentioned a flashing of a script that removes encryption, but some others tutorials don't. So... question would be... is it alwasys necessary? Or just if you encrypted your phone or something?
2) Since unlocking your bootloader makes some thigns not working (like the Find my device thing and other banking things...) i was wondering if the bootloader can be re-locked. I plan to stay with the stock Android, but i assume i have to drop the root? So...maybe re flashing stock rom/recovery/bootloader and re-lock after? I'm not clear with this part, so if anyone can shed some light on it, it's very appreciated.
Thanks
Any way to hide above error message on boot? Kinda ugly & sucks, running LineageOS (17?) or Android 10.
For this device, as it stands no. Unless someone has found a way and just not posted how in previous threads asking this. Annoying but kinda a non-issue. Pretty sure the only way is going back to stock and re-locking bootloader.
I think no one knows or there's no way. Even if you go back to stock and relock the bootloader. Also, relocking the bootloader just seems to only block flashing stuff the phone and not actually oem locking the phone, which are different things.
Hello guys, I am a bit lost reading all about this.
I understand that after unlocking bootloader we loose L1, as it is downgraded to L3. Also, from other phone forums, I understand the only way to restore L1, is by making a backup of our persist.img, which you can only do if you are root.
So, unlocking, installing TWRP, rooting, restoring stock bootloader, and locking bootlaoder. Will then have L1 back while being rooted? Is there any risk on this operation, I have seen people bricking their phone while locking the bootloader, why is this happening?
Thanks a lot.
The only way going back to L1 is to relock your bootloader. This is an EXTREMELY risky operation, as you can end up a hardbrick if theres ANY system/boot/recovery change after unlocking the bootloader. I strongly recommend you NOT to relock the bootloader until there is a flash tool from Realme which is expected to be puclished within this month.
Im trying to relock my bootloader for trade-in as Ive upgraded to the P5.
When locking bootloader, it shows its locked, but then displays "cant find valid os" screen when trying to boot. I can still go back and unlock bootloader and boot back up just fine. I just cant relock it for some reason. Ive done this before on past Pixels, I dont know what the problem is.
Any ideas? What am I missing?
JJT211 said:
Im trying to relock my bootloader for trade-in as Ive upgraded to the P5.
When locking bootloader, it shows its locked, but then displays "cant find valid os" screen when trying to boot. I can still go back and unlock bootloader and boot back up just fine. I just cant relock it for some reason. Ive done this before on past Pixels, I dont know what the problem is.
Any ideas? What am I missing?
Click to expand...
Click to collapse
It's annoying when that happens.
What normally works for me is factory reset it, let it boot to setup then lock.
did you try the original download software?he have the lock/unlock option for bootloader and flash os you want.
If the above advice fails to get you the results you want...
I would go download the latest factory image and flash it with the -w still in the script. Let it do it's thing and reboot, it'll reset everything to stock. Do a factory reset afterwards for good measure. Once that is done, go ahead and lock the boot-loader. Just beware that if the phone is not completely stock when relocking, it potentially could brick the phone.
Flashing factory image did the trick. Thanks
im also here. just bought a new pixel so i gave my pixel 4xl to her. So i relocked the bootloader to set it up as "new"
no i cant find valid os, bootloader is locked. and i cant unlock it... what have i done =)
solved it with flashtool.
I just wanna use this thread as an opportunity to give some old-school advice... Unless you are selling or retuning for warranty, there is no good reason for relocking the bootloader. In my opinion the risks outweigh the rewards.
Carry on... Lol
CyberpodS2 said:
I just wanna use this thread as an opportunity to give some old-school advice... Unless you are selling or retuning for warranty, there is no good reason for relocking the bootloader. In my opinion the risks outweigh the rewards.
Carry on... Lol
Click to expand...
Click to collapse
☝☝☝☝ This! ☝☝☝☝
CyberpodS2 said:
I just wanna use this thread as an opportunity to give some old-school advice... Unless you are selling or retuning for warranty, there is no good reason for relocking the bootloader. In my opinion the risks outweigh the rewards.
Carry on... Lol
Click to expand...
Click to collapse
Wholeheartedly agree, with one caveat. With Google's implementation of their hardware attestation shenanigans earlier this year (which checks to see if the bootloader is unlocked), there might be some that don't want to root and use the various mods or use a custom kernel to bypass that so they can pass ctsProfile and use banking apps, etc., and thus may want to go completely stock and relock their bootloader.
But yeah, in general it's a bad idea.