Database Develop

Any change to relock bootloader?

Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!

alexhdkn said:
Is there any chance to relock the bootloader? I don't mind about warranty i just want to make it as much similar to stock as possible!
Click to expand...
Click to collapse
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.

Why would you want to relock the bootloader just to get back to close as stock as possible?

I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
TechSavvy2 said:
NOTE, YES, THIS IS A LONG DRAWN OUT VERSION OF WHAT IS ACTUALLY VERY VERY QUICK PROCESS. This is for reference only. I know there are a few people out there just like me who probably had a few small hickups getting back to stock with the firmware. This is to help "spoon-feed" the instructions to you.
Two Methods-
Method 1 - RSD Lite
Method 2 - Manual Flash
If you cannot get RSD Lite to recognize your device, try Method 2, it works like a charm!
Downloads:
I assume you already have adb drivers if you're even here.....otherwise get them from the latest sdk here: http://developer.android.com/sdk/index.html
Moto Drivers (Motorola Device Manager): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
RSD Lite (I used version 6.1.5): https://dl.dropboxusercontent.com/u/42057363/RSDLite_v6.1.x.zip - Extract and use 6.1.5
Stock Firmware: http://sbf.droid-developers.org/ thanks to Skrilax_CZ and Firmware Team
Moto Fastboot exe: https://drive.google.com/file/d/0B0dUKGxGylgNTk43eU0xc3VLekE/edit?usp=sharing - NOTE - YOU MUST UNZIP AND USE THIS WHERE MANUAL FLASH SAYS "mfastboot"
My Setup: Windows 8 machine <--obvious driver issues as usual
My Device: VZW Moto X
METHOD 1 - RSD LITE
Step One - Download and install RSD Lite. At the moment, I can't find where I got mine from, so anyone who wants to add a proper link to it would be appreciated. I used version 6.1.5 and it worked fine.
Step Two - proper driver installation. If you're like me, you probably at one point got drivers quasi-working but here's what I did that worked - download and install "Motorola Device Manager" and it *should* give you the proper drivers. This was necessary (maybe) because I could get adb to recognize my device, as well as fastboot, however RSD refused to see it. This install fixed that.
Step Three - download and install the proper firmware for your device. NOTE: You MUST MUST MUST choose the right firmware for your device or you will FUBAR your phone.....not my responsibility.
Step Four - Unzip your firmware zip file, open it up through the layers and find the file "VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF" or whatever version/carrier/build number file yours is, its the XML Document file. Right click -> Open with.. -> Notepad/word editor/XML Editor/wordpad and find the line:
<step operation="getvar" var="max-download-size" />
^^^You need to select this entire line and just delete it out of the file. This is the line that gives fastboot flash error. Select it, delete it, then resave the file an exit out of it. Done.
NOTE: This is required or the firmware flash will immediately fail giving a "failed flashing process. Unknown fastboot command. (getvar)"
-For the sake of security, and not messing with important files, I'd actually recommend zipping the file back up after this and keeping as your final version (once you've confirmed yours works correctly)
Step Five - Plug in phone, enable USB debugging, then "adb reboot bootloader" - this will boot you into fastboot mode so RSD will recognize your phone
Step Six - Run RSD Lite - note that some people have had trouble and have to right-click run as administrator. In RSD Lite, make sure phone shows up in slot 1 - mine shows up, under Model, just says fastboot, USB port type, info N/A, important part is that it shows as Connected in status. Select the three-dot browse file button, then you can go down into the unzipped file you created of the XML folder, and select the XML file that we just edited earlier (or select the rezipped package). Select open and flash. (or decompress and flash)
Step Eight - Profit
METHOD 2 - MANUAL FLASHING
Much easier AND don't have to deal with getting RSD Lite to work....
Note - this was done on VZW variant, and based on XML file of that particular firmware. Get these instructions from your firmware package XML file.
Note 2 - VERY IMPORTANT!!! - You MUST use mfastboot (Moto fastboot) for the system.img flash as its too large for standard Android fastboot to handle, your flash WILL fail if you use standard fastboot. Hence why it says "mfastboot" this is not a typo.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
Click to expand...
Click to collapse

KidJoe said:
There Are three status for the 2013 X boot loader...
Locked Status Code 0
Unlocked Status Code 3
Locked Status Code 2 (aka RELocked).
If the status is Unlocked or Relocked, you'll get the unlocked bootloader warning at boot up.
We do not have a way to toggle back to LOCKED Status Code: 0.
So you could take it back to RELocked, but it won't really matter much. Moto has the steps on their web page https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images and there was a thread here on XDA too http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786
Also keep in mind that if you used Sunshine to unlock, if you do RELocked you will not be able to unlock again. Where as if you unlocked by having the unique code for your phone, you'll be able to rel-unlock using your code.
Click to expand...
Click to collapse
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.

nhizzat said:
Why would you want to relock the bootloader just to get back to close as stock as possible?
Click to expand...
Click to collapse
So i can get Lollipop official!

TheBoiledDogs said:
I recently reset my phone back to the stock ROM after jacking up a kernel (did everything on manual flash with the exception of relocking it). Just follow the steps and you'll get it.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Already done this but it won't relock the bootloader.

alexhdkn said:
I unlocked it with the Motorola code, can i relock it? I've tried fastboot oem lock command and it gives me error.
Click to expand...
Click to collapse
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
alexhdkn said:
So i can get Lollipop official!
Click to expand...
Click to collapse
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.

edit:canceled

KidJoe said:
As I said, if you got your Bootloader Unlock code from Moto (or the former China web site or China Middleman), you CAN relock, then unlock it later.
Did you use mFastboot, and follow the FULL sequence of starting with mfastboot oem lock begin followed by flashing the Stock MOTOROLA rom, and finishing wth the mfastboot oem lock command?
note: some have said the fastboot oem lock command needs to also include the Unique code. ex mfastboot oem lock uniquecode
Being bootloader Unlocked will NOT impact being notified about, or getting the OTA.
But actually installing the OTA will have some conditions... see -> http://mark.cdmaforums.com/MotoX-OTA.html
So WHEN Lollipop for the 2013 X is finally made available, undo any hacks or changes that move you too far from the stock rom, then take the OTA.
And for the record, I have never attempted to re-lock my bootloader. I've been unlocked since late Nov 2013. and I have received the OTA's just fine.
Click to expand...
Click to collapse
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).

alexhdkn said:
Thanks for the answer I will try at home the mfastboot oem lock (i have always wrote fastboot oem lock without the m).
Click to expand...
Click to collapse
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.

KidJoe said:
Again, its MORE than just mfastboot/fastboot oem lock. There is an entire process. And it requires to flash the ENTIRE STOCK OEM SBF to your phone, and this process WILL also erase user data. If you only used FASTBOOT, then you probably didn't follow the process, as it requires flashing all IMG files and other parts included in the SBF, and flashing system.img requires mFastboot.
And relocking the bootloader is NOT needed if all you are trying to do is get the OTA when it becomes available.
Click to expand...
Click to collapse
I know it's an entire process and I did it last night to go back to stock 4.4.4. But I just feel safer (thieves) with the bootloader locked.

Thieves? How will having a locked bootloader protect you from thieves?

Help To Relock Moto X XT1052 Bootloader

Hey guys
I have a Moto X XT1052- The Indian Version.
I rooted my phone a few weeks back and I've decided that I don't want root access anymore.
I have unrooted my phone from the SuperSU app by clicking the clean up button.
Now I can't find anything as to how to relock the bootloader. I don't really need the warranty to be active again but if there is a way to do that it would be appreciated.
Also I need help to remove the bootloader unlocked warning message to be removed as well.
Please be clear in your explanations as I'm new to all this.
I have attached details about my phone to this post.
Thanks in advance

If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.

bronko15344 said:
If you are already unrooted than there is no need to go further. The bootloader can be relocked with fastboot like you unlocked the bootloader but its getting back to the state relocked and not locked. That means your warranty's is still voided and the warning message keeps there. To remove the warning there was a tutorial here in the forum. Basically it's just changing the bootlogo.
Click to expand...
Click to collapse
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks

RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as you are re-flashing the EXACT same rom that is on your phone, and your battery is 100% charged before starting. In other words,as always, if the battery goes dead during the process, there is a potential to brick, and DOWNGRADING your ROM is not good.
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.

KidJoe said:
Relocking the bootloader will erase your data. There are serveral threads on XDA about it... here is one -> http://forum.xda-developers.com/moto-x/general/noob-guide-unroot-relock-bootloader-vzw-t2571786 while it says VZW (Verizon Wireless) in the subject, the same steps and info apply to all 2013 Moto X's.
No it will not lead to bricking, as long as your battery is 100% charged before starting. (in other words,as always, if the battery goes dead during the process, there is a potential to brick)
As for changing the logo.bin to remove the unlock warning... see -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961/post53098892 or see the LOGO.BIN info at -> http://mark.cdmaforums.com/MotoX-Bootlogo.htm
As @bronko15344 has already said, your bootloader status will change to "Relocked."
There are 3 states to the bootloader.
1. Locked Status Code 0 (as it ships from the factory)
2. Unlocked Status Code 3 (when the bootloader is unlocked)
3. Locked Status Code 2 (aka RELOCKED, after you use fastboot oem lock command)
If the status is Unlocked or Relocked (code 3 or 2), you'll get the unlocked bootloader warning at boot up. While you can replace the Logo.bin to hide or remove the message, any subsequent flash or ota that replaces logo.bin will cause the warning to return.
We do not have a way to toggle back to LOCKED Status Code: 0 as it came out of the box.
In other words, even relocking doesn't take you back to 100% completely stock.
Keep in mind, I have NOT tried flashing a custom logo.bin to remove the unlocked warning on a phone set as "Locked Status Code 2" (aka relocked). I don't know if you need to be Unlocked Status Code 3 to flash it.
Click to expand...
Click to collapse
Thank you so much

RohanAditya said:
It is possible to unroot from the SuperSU app isn't it? That's what I did.
But I want to relock the bootloader.
Does it erase data on the phone?
Will it lead to bricking or any other problems?
And could you explain the procedure in detail please?
And could you give me a link to the guide you mentioned?
Thanks
Click to expand...
Click to collapse
If you used the "Full Unroot" option in the app it should revert all changes which are made during the root process. To be sure that your system partition is completely stock you can flash it with fast boot (this won't delete your installed apps and data)
To do this look into this guide
guide-moto-x-return-to-100-stock
Short version:
1.
Download and extract the sbf flies matching your phone and carrier from here:
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
To decide which file you need to download:
info-tip-web-sites-official-leaked-roms
2. (this step is necessary to remove your warning message)
ghost-original-bootanimations-unlocked
download the standard boot animation and extract the logo.bin and overwrite the logo.bin from the sfb files.
3.
now flash the system partition, kernel, recovery and the new logo (without the warning) with the following commands: (Note: For flashing system.img you MUST use mfastboot instead of fastboot. It's to big for the normal fast boot. So no typo here)
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
Don't execute the following command as this will delete all your data/installed apps etc.
Code:
fastboot erase userdata
That should be sufficient to revert everything what was changed during the root process. Check if everything looks like it was was on stock rom (including the recovery and the bootlogo)
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
But actually I would not relock your boot loader since you gain nothing and if you want to unlock it again all your data will be erased during the unlock process. and since you are not rooted you can't backup everything before...
Edit: Like @KidJoe said. If you accepting an OTA than the warning comes back. so if you relock your bootloader you can't hide that message without unlocking (and loosing all your data) again. Just stay on the unlocked bootloader

bronko15344 said:
Now you can relock your boot loader using one of the these commands (I'm not sure which one it was but it should be the first one. If that is giving you a error than try the second one)
Code:
fastboot oem lock
fastboot oem relock
.
Click to expand...
Click to collapse
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.

KidJoe said:
On the 2013 X, if you just do Fastboot OEM LOCK, it will prompt you with "ready to flash signed images."
The info in the thread I posted a link to are accurate. You must fastboot oem lock begin, flash full stock rom (using mfastboot), erase cache and user data, then fastboot oem lock.
Click to expand...
Click to collapse
Oh wasn't aware that you directly have to flash a firmware to relock the bootloader. Thank you

hey how u do u unlock ur moto x t1052 .

Help with unlocking bootloader on the 626g+

Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?

xdafanboii said:
Basically "fastboot oem get_identifier_token" doesn't work, outputs
"FAILED (remote: unknown command)"
Flashing recovery doesn't work either "partition 'recovery' not support flash" but that's probably because the bootloader is still locked. I've rooted this phone with Kingoroot but not having a TWRP recovery bothers me a lot, since this device would most likely get bricked if factory resetted because Gapps were deleted. Also Kitkat is outdated for 2018.
Is there any possibility to get the identifier token, so as to unlock this bootloader on 626g+ dual sim version?
Click to expand...
Click to collapse
there is a firmware for the phone
unpack it
u will find there file Checksum.ini
and unlock‐secro.img(or diferent name point is unlock)
rename checksum.ini on checksum.oem
then turn off all checks in flashtool leave marked only SECRO line
u must choose unlock‐secrom.img for SECRO line
once u'll flash SECRO u will have to flash twrp, to do that u must turn off all checks except RECOVERY, for RECOVERY u must open recovery 1.72.img then flash it, after u can just flash supersu.zip via twrp
i've done it all on my 1.76 device it will also work on 1.79
twrp u can find here(u need to register on that forum)
https://4pda.ru/forum/index.php?showtopic=756527&view=findpost&p=53228248

Huawei p9 recovery fail!

I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected. Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

khangkhong said:
I have a Huawei P9 and I rooted this previously and installed TWRP. Everything was fine and and just recently I flashed stock recovery so I can update my phone and relocked bootloader. When I locked it, it tried to restore to factory settings as it usually does and I get a prompt “wipe cache partition” or wipe something. I now can’t remember as I just absently tapped “yes.” And after that the phone was bricked. It tries to restore using eRecovery but always fails. I can’t flash through fastboot as the phone can’t be detected.
Click to expand...
Click to collapse
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?

zgfg said:
What was your last action before you went to (re)lock Bootloader:
a) Flashing stock Recovery, and in that case did you unroot and are you sure it was correct Recovery version for the stock firmware you were running
or
b) Updating Firmware, and in that case by which method did you update (OTA, eReovery, HiSuite, DLOAD, Firmware Finder + DNS, HWOTA...)?
What is your model L09 or L19, your cust c432 or else, what was your full build name/number (like EVA-L09c432b504 or what)?
Click to expand...
Click to collapse
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.

khangkhong said:
I tried updating my phone using the dload method but it kept failing. I also used a lot of firmwares. Btw my phone is EVA-L19 and I live in the Philippines and got my phone here. I only used the Asia firmwares as I can't seem to find a Philippine specific firmware. I did not unroot before relocking the bootloader.
Click to expand...
Click to collapse
Before relocking Bootloader you must make sure that you have stock Recovery, stock Boot/Ramdisk image (that is, must be unrooted), stock Kernel (if you experimented with custom Kernels).
Unfortunately, if you didn't have, Factory reset as part of relocking Bootloader fails and may cause brick
Don't know what is the cust for Philippines/Asia and what are its latest firmware versions, and do they allow DLOAD installations (only firmwares named as FullOTA-MFPV on Firmware Finder can be installed by DLOAD, those with MF but without PV cannot be).
Btw, what is the cust for Asia you were flashing with, EVA-L19cXXX?
If eRecovery cannot recognize the phone model, it might be due your attempts to flash various firmwares by DLOAD
Can you boot to Fastboot and connect by Fastboot from PC (probably no more since you attempted to relock Bootloader, which disabled OEM Unlock and USB debugging):
- Switch off, connect by USB to PC, press and keep pressing Vol- and press Pow button.
If you could boot to Fastboot, there are Fastboot commands to read what the phone thinks it is its latest cust and build number, that can help to unbrick.
Also, it helps to DC-Phoenix (paid tool for unbricking)
PS: Don't know why people go for relocking Bootloader. There have been so many posts here and there with users who bricked their phones when attempting to re-lock Bootloader(because they had TWRP, they did not unroot, they had custom DOMs, etc).
Besides:
- Unlocked Bootloader DOES NOT prevent/affect OTA upgrades
- relocked Bootloader is different from originally locked Bootloader and Huawei service can still recognize that Bootloader was unlocked and relocked
- Some new stock firmwares automatically lock (not relock) Bootloaders upon upgrades

I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”

khangkhong said:
I can boot to fastboot but all of the tutorials I’ve read says that the bootloader needs to be unlocked in order to upgrade firmware or unbrick. And the only commend I can do in fastboot is “fastboot devices.”
Click to expand...
Click to collapse
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION

zgfg said:
What does it respond you on commands
Code:
fastboot oem get-bootinfo
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number
fastboot oem oeminforead-SYSTEM_VERSION
Click to expand...
Click to collapse
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398

khangkhong said:
fastboot oem get-bootinfo = (bootloader) unlocked
fastboot oem get-product-model = (bootloader) EVA-L19
fastboot getvar vendorcountry = vendorcountry: hw/spcseas
fastboot oem get-build-number = (bootloader) :EVA-L19C636B398
fastboot oem oeminforead-SYSTEM_VERSION = (bootloader) :EVA-L19C636B398
Click to expand...
Click to collapse
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware

@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?

misagh72 said:
@zgfg sorry for disturb
can u help me i dont want make new thread
here is my problem
i unlock boorloader and install TWRP and use stock fraimware i use for while but i want to factory rest my phone after that my phone cant boot up
still i can access to TWRP
what can i do ?
can i use system recovery on hi suite?
Click to expand...
Click to collapse
People, this has been written in many other threads and posts:
- Before doing Bootloader relock or Factory reset, you must unroot, restore stock Recovery, otherwise it bricks.
You can try to reinstall by using eRecovery.
But since you still have TWRP, read my post #8, you have link and instructions to the HWOTA method.
Of course, I have described to the other user who has L19c636, you must flash by HWOTA for your model L09/L19 and your cust cXXX - I gave instructions in the posts #4 and #6 how to boot to Fastboot and which Fastboot commands to use to obtain info for your phone

zgfg said:
As per your Fastboot - your Bootloader is still Unlocked
Hence flash TWRP for Nougat (from Fastboot) and use HWOTA method:
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
to flash EVA-L19C636B398.
It must be FullOTA-MF, it is explained in the link above what you need to prepare (HWOTA folder on the SD card, that contains three PROPERLY renamed update*.zip files that you must find and download by Firmware Finder, you can use FF on PC).
It can be any other NOUGAT stock firmware (not necessarily b398) but it must be for EVA-L19c636 (by HWOTA alone you cannot rebrand to eg c432) and it must be FullOTA-MF (or MFPV), usually 2+ GB, not some OTA-MF of only 300 MB or so.
You must use the same TWRP for Nougat that you will find in the post #1, from the same thread as above, where is HWOTA method describef in the post #3.
If you use Windows 10 on the PC, (by default it hides file extensions) make sure that you do not rename some of the three update*.zip files to have 'double' zip extensions like update*.zip.zip
In HWOTA method, TWRP will execute a shell script and files and folders must be named exactly as described in the given OP post, otherwise HWOTA method (its shell script) will fail to flash the complete firmware
Click to expand...
Click to collapse
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.

khangkhong said:
I followed all the steps and downloaded all files and put them into HWOTA and rebooted. Nothing happens. I tried Vol+, Vol-, and Power button to force to install files but I get install failed. BTW when I boot I'm always on eRecovery and cannot boot to TWRP.
Click to expand...
Click to collapse
>> downloaded all files and put them into HWOTA and rebooted. Nothing happens
Nothing can happen by itself
>> . I tried Vol+, Vol-, and Power button to force to install files
This is HWOTA, not DLOAD.
It's desrcribed in the HWOTA tutorial that you must boot to TWRP, and TWRP has Install tab where you choose Storage (SD card), Zip installation, and then select the script from HWOTA folder, and then Swipe to start flashing
>> when I boot I'm always on eRecovery and cannot boot to TWRP
I wrote you in the previous post that you must first install TWRP. Your Bootloader says it is unlocked.
You must install TWRP from the thread I gave you the HWOTA link - do you know how to install TWRP from Fastboot?
Have the HWOTA folder ready on the SD card, so that when you install TWRP from Fastboot, you must immediately reboot from Fastboot directly to TWRP, then navigate in TWRP to it's Install option and proceed by HWOTA installation as described in its OP post

I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.

khangkhong said:
I tried installing TWRP in fastboot mode using “fastboot flash recovery” command but it always fails. Btw I can only boot to eRecovery so the developer options and usb debugging that needs to be toggled cannot be done. Cause in all tutorials to flash TWRP, usb debugging needs to be toggled.
Click to expand...
Click to collapse
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)

zgfg said:
Please describe how flashing TWRP fails - what exactly does the Fastboot respond to the command.
Please copy/paste your command and the Fastboot response from the PC
And please upload also a photo of the phone Fastboot screen, what exactly it says on the bottom (Phone unlocked...)
Click to expand...
Click to collapse
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:

khangkhong said:
This is the prompt.
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY [ 0.558s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.586s
On my phone in fastboot mode:
View attachment 4755207
Click to expand...
Click to collapse
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate over the Web links, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp

zgfg said:
From your Fastboot screen photo:
- Phone relocked (green)
Hence Bootloader is really relocked, but this is in contradiction to
>> Bootloader unlocked
what was reported by Fastboot interrogation from the PC side, post #7
Btw, you see that Fastboot screen says Phone (=Bootloader) relocked (it was unlocked and then locked) clearly distinguishing from the originally locked phone (Bootloader) ;-(
Fastboot also shows
- FRP locked (green)
which confirms that OEM is locked.
Btw, did you maybe locked OEM from Settings, Developer options before you went to relock Bootloader by Fastboot?
Unfortunately, you got what you wanted, the locked Bootloader and also locked OEM - but since the phone is bricked (you didn't prepare to have stock and unrooted firmware with stock Recovery before attempting to relock Bootloader), you cannot unbrick the phone now:
- Methods require to have or to flash TWRP (like HWOTA)
- Or to flash stock Recovery, etc:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
https://forum.xda-developers.com/p9/how-to/unbrick-huawei-p9-eva-l19-100-t3628656
https://forum.xda-developers.com/p9/how-to/huawei-p9-brick-easiest-to-unbrick-t3662348
- Or to flash no-check Recovery:
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But you locked Bootloader and they cannot flash anything.
Because OEM is also locked, you cannot unlock Bootloader.
And you cannot boot to System to unlock OEM (on the bricked phone).
Btw, it was much more useful working phone with unlocked Bootloader and OEM (bothering with a Notice on the start screen) but available for unbricking (just in case), than now the phone with locked Bootloader and OEM albeit bricked ;-(
I hope, somebody else a wannabe with the relocked Bootloader will read this (they don't, every month or so another one does the same or similar and only then turn to XDA asking for help)
---
Anyway, you can try:
1) Download by Firmware Finder (from another phone, needs not to be Huawei, you can install FF from GStore to any Android) or from PC, EVA-L19c636b395 FullOTA-MFPV (package number #114776, 2.5 GB) as on the screenshot.
Try to DLOAD.
No guarantee that it could work (your phone remembers b398 and there is no MFPV with c636 but b398 or higher)
2) Try to rollback to Marshmallow, maybe it will allow you to do it by DLOAD:
https://forum.xda-developers.com/p9/help/finally-downgrade-huawei-p9-android-t3868721
Once on Marshmallow (but with unbricked phone), update by OTA back to Nougat
Sorry, I don't know any other (free) method (all others require flashing, but you cannot since the Bootloader OEM are locked)
You can try paid services, people were able to unbrick (with locked Bootloader and OEM) by using their tools, but you must directly communicate to them, pay them and ask for instructions:
3) DC Phoenix:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
4) Ministry of Solutions:
https://ministryofsolutions.com/paid-services/amp
Click to expand...
Click to collapse
Thanks for the reply. I’ll try your suggestions.

Moto G6 Bricked NEED HELP!!!

ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
ibb.co/QmnK1cB)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd

pyschodelicbros said:
ibb.co/qMypk9M)
ibb.co/SPB646j)
ibb.co/Y823s3r)
[Copy link and past without the )]
I relocked my oem and cant unlock it again. Says feature disabled
Tried potting and restocking but its not flashing because of oem being locked.
Any Ideas?? This is my first rooted phone and I’m new. I had magisk installed earlier but had to reinstall due to android system apps like media storage crashing.
Thanks
Click to expand...
Click to collapse
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291

AgentICS said:
You should download the stock firmware from here and following this guide to restore to stock firmware. Even if the rest of the commands don't work, the first two should reset the bootloader and partition tables and make it bootable or maybe unlockable again. You can also maybe try to boot TWRP but I don't know if that'll work because the boorloader is acting odd
Click to expand...
Click to collapse
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?

pyschodelicbros said:
I heard that once u relock bootloader, your unlock feature gets disabled for a few days. Anyone know if that is true?
Click to expand...
Click to collapse
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request

AgentICS said:
I'm pretty sure it's because the bootloader can't contact the OS correctly and therefore can't validate the request
Click to expand...
Click to collapse
mfastboot oem lock
mfastboot oem lock
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash boot boot.img
mfastboot oem lock
I did this to lock the bootloader, not knowing my OS wasnt installed properly so theres no OS and my bootloader is locked.
"fastboot oem unlock"
says bootloader feature disabled
Picture of my bootloader log
[Copy link and past without the )]
ibb.co/QmnK1cB)

Ragarianok said:
You should be able to flash official firmware even if the bootloader is locked. Do you still have the original unlock key you received from Motorola to unlock the bootloader? You'll have to use that to re-unlock your bootloader.
Code:
fastboot oem unlock UNIQUE_KEY
Replace UNIQUE_KEY with the unlock key you received.
EDIT: It just occurred to me that "OEM unlocking" is probably toggled off since you re-locked the bootloader. That's why it says "feature disabled".
You could also try to restore stock firmware using Lenovo Moto Smart Assistant. It has a Rescue option that does that.
https://support.lenovo.com/us/en/downloads/ds101291
Click to expand...
Click to collapse
Lenovo Moto Smart assistant says device isnt recognize, it might be USB debugging due to not being able to get into the OS.
I tried getting the unique key using "fastboot oem get_unlock_data" but i get this in my CMD
[Copy link and past without the )]
ibb.co/QHD0ZcS)
I do have my orginal unique key saved in a file from when i first unlocked my bootloader and when I tried to flash it I get bootloader feature disabled.
[Copy link and past without the )]
ibb.co/0MPsZrp)
I heard that the oem unlock gets disabled for 7 days after relocking wondering if that is true???