Develop Bugs

Bootloader unlock

So I've finally decided to unlock my bootloader so I've been reading a few threads about it but I want to be sure that I'll do it right.
I want to use this method:
http://forum.xda-developers.com/showthread.php?p=12873655
But since I'm on a branded phone I understood that I'll have to flash a generic Rom first to allow the unlocking to be done, am I correct?
I do understand that I'll lose the DRM's and stuff and that while on an unlocked bootloader I cannot use official SE programs (PCC & SEUS) because it will brick the phone correct?
After the unlocking is done I'll still have a fw installed right?
And finally, after unlocking bootloader I'll flash roms in flash mode and kernels and baseband on flashboot mode right?
Thanks for the help guys!
Sent from my LT18i using XDA

Stock ROM Bootloop unless bootloader is unlocked

I restored the newest stock Android One ROM using MiFlash, but the phone only boots if the bootloader is unlocked. I need the bootloader to be locked for various apps. Can someone help me
I haven't found any threads that talk about this issue so I have no idea of what to do

Regarding your signature, I believe you have Magisk installed ? If you have Magisk or TWRP installed or if you've changed anything in the system, you can not lock the bootloader, as it will prevent the device from booting. All the partitions of the device should be stock and you should not have root, in order to lock the bootloader. My advice is to flash the stock rom via MiFlash again, but choose 'Clean All and Lock' option while flashing.

Install stock 10.0.13 version with edl mode:
fastboot oem edl , and flash with miflash,then reboot the system in fastboot mode to lock bootloader with : fastboot lock oem , then boot the system and update your device with ota.

Question How to reset back to factory, after rooting???

Need back to 100% stock. I am returning, so how to unroot, and lock BL??? Thanks!

Factory reset and flash stock image from Google directly. Finally lock bootloader
Code:
fastboot flashing lock

miravision said:
Factory reset and flash stock image from Google directly. Finally lock bootloader
Code:
fastboot flashing lock
Click to expand...
Click to collapse
Is factory reset really needed for unrooting ?
Why wouldn't just flashing the original boot.img and re-locking the bootloader be enough ?,
considering you haven't changed any system files with root.
Maybe also "fastboot flash vbmeta --enable-verity --enable-verification vbmeta.img" before
locking the bootloader to enable verity.

andreipaval said:
Is factory reset really needed for unrooting ?
Why wouldn't just flashing the original boot.img and re-locking the bootloader be enough ?,
considering you haven't changed any system files with root.
Maybe also "fastboot flash vbmeta --enable-verity --enable-verification vbmeta.img" before
locking the bootloader to enable verity.
Click to expand...
Click to collapse
Changing the status of the bootloader - from either locked to unlocked - or unlocked to locked, wipes the phone, so same as a factory reset. Also, if they're returning the phone, they'd want to factory reset anyway.
I'd also suggest Official Google Android Flash Tool, and my understanding of flashing vbmeta.img is that if you don't have it set to disable, then by default it's enabled, although using the switches might work fine too.

Can't flash TWRP with odin after flashing stock ROM with odin

Hoping to get this fixed, after flashing a twrp tar file my phone cannot boot to rom or even recovery, but bootloops, is there a potential fix? Do I need to bootlock and unlock my phone?

What do you mean by "bootlock"?
Did you unlock your bootloader before flashing?

V0latyle said:
What do you mean by "bootlock"?
Did you unlock your bootloader before flashing?
Click to expand...
Click to collapse
Yes I did unlock my bootloader before flashing, what I mean by bootlock is locking the bootloader through download mode.

wavetsuname said:
Yes I did unlock my bootloader before flashing, what I mean by bootlock is locking the bootloader through download mode.
Click to expand...
Click to collapse
Never lock your bootloader unless you have flashed back to factory stock. Locking the bootloader on modified firmware will brick your device.
When you are in download mode, look at the upper left corner of the screen. There should be a line that reads OEM LOCK. Is this ON or OFF?
Which TWRP build are you using?

Factory stock is the only firmware I'm able to flash successfully, in download mode it says "OEM LOCK: OFF(U)", I attempted to flash TWRP 3.5.2, here's the file if needed, I have also attempted to flash other TWRP versions, but none worked.

I managed to get orange fox working, and it turned out I flashed the wrong stock ROM for my phone.

To flash TWRP with odin - one of previous version of stock ROM required. On the latest versions of stock ROM it is impossible to flash TWRP - the device goes into the bootloop.

Question Can't boot CPH2451

So I wanted to relock my bootloader so that I could use Netflix, Hulu, etc... When I fastboot flashing lock it only boots to bootloader. I can't flash anything with bootloader locked. When I unlocked again and flashed the stock boot and init_boot and stock recovery image I just get a bootloop into bootloader. I think the recovery image I flashed is not good. I can't even power the phone off through the bootloader power off option, it just reboots back to bootloader.
Can I get back to original stock rom and recovery?

Update. So now I'm completely bricked. I managed to switch the active slot to a, relocked the bootloader and now I just get a boot screen with red text that says the boot/recovery images have been destroyed and can not boot.

This happened because you failed to restore to full stock before locking locking bootloader. Well you could unlock bootloader again and fix it.

MrSteelX said:
This happened because you failed to restore to full stock before locking locking bootloader. Well you could unlock bootloader again and fix it.
Click to expand...
Click to collapse
Thanks for the reply. I can't unlock again because it's stuck in a bootloop and won't boot into bootloader.

I will point out that recover and kernel both live in boot.img since there is no custom recovery for our phone.

MrSteelX said:
I will point out that recover and kernel both live in boot.img since there is no custom recovery for our phone.
Click to expand...
Click to collapse
recovery is it's own file, not part of boot.img. at least that's what the rollback and developer preview is showing.