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.
Related
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?
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
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
babyshark1983 said:
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
Click to expand...
Click to collapse
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
zgfg said:
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
Click to expand...
Click to collapse
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
babyshark1983 said:
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
Click to expand...
Click to collapse
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
zgfg said:
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
babyshark1983 said:
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
Click to expand...
Click to collapse
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
zgfg said:
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
Click to expand...
Click to collapse
hi just bootloader unlock
frp locked
thx
babyshark1983 said:
hi just bootloader unlock
frp locked
thx
Click to expand...
Click to collapse
That is the problem - to flash you need both Bootloader and FRP unlocked but with wrong TWRP or so, you locked FRP
To unlock FRP you would need to boot to System and check OEM Unlock under Developer Options - but if you ccannot boot to System, it is bricked
IMO, no other way now but to buy 15 EUR credit for DC Phoenix, they can unlock (TG, I didn't need to use DC Phoenix , hence cannot help about, you can ask them over their page)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
You can also search here on XDA, there were other users who un-bricked by their tool, if I recall there was also somebody with a similar brick: FRP locked but cannot boot to System
Hey there. So I tried installing eva-L09c432b386 from OTA, which failed. I _believe_ I am on eva-L09c432b383, but I'm not sure. I think I had EMUI 5.0 or 5.1 and the OTA update of b386 was offered. I have TWRP installed and (years ago) I changed back from c900 to c432 .
Stupidly, I wiped data. I do have a Nandroid Backup, which, however fails to restore due to Error 255. (I can't find more detailed logs)
I'm very confused as to which firmware version I need to download and flash, whether or not I need to change to the stock recovery, etc. Could you give a hint? Can I use any version and go directly to Android 8 or something, or do I need b182 (this is what I am frequently reading here...)
Thank you for your help!
You can try to reinstall firmware by eRecovery.
Switch off, connect to charger (!), press and keep pressing Vol+, boot by Pow.
Select Install latest firmware and recovery.
If it succeeds you may do Factory reset (also from eRecovery) before booting to System
If eRecovery won't work, boot to Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot by Pow) and execute (you must have ADB & Fastboot installed on your PC - if not, search for Minimal ADB and Fastboot on XDA and install).
You can copy to bat file and execute:
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot getvar vendorcountry
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
We will see what was your latest firmware (model, cust, build number) installed
Btw, b182 was Marshmallow (EMUI 4) and for Oreo (EMUI 8) you must have unlocked Bootloader and FRP/OEM), working Nougat (EMUI 5), then rebrand and update:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
I unlocked the bootloader using a quick way, which is by pressing the volume buttons up and down and running the script. After that, I had an inscription at startup, in order to start the phone, I had to press the power button again. To get rid of this inscription, I downloaded platform tools and threw into the platform tools folder a file with the name vbmeta.img, which I took from the firmware that I currently have and entered the command when the phone was in fastboot "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img". The inscriptions did not disappear, then on one forum I was advised to enter the command "fastboot oem cdms", I entered this command and the phone started without inscriptions. After that, I patched boot.img from my firmware using magisc and threw the file into the platform tools folder, renaming it magisc_boot.img and entered the command "fastboot flash boot magisk_boot.img". Root rights worked, but I realized that I didn't need root and deleted it using the update item and download the full firmware. Now the bootloader is unlocked on my phone and there is no root. How do I lock the bootloader safely. Current Firmware Indonesia
Only if the phone is not a Chinese version.
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Will there be any problems due to the fact that I unlocked the bootloader in an unofficial way and flashed vbmeta.img from my firmware?
IcePhoenix466 said:
Will there be any problems due to the fact that I unlocked the bootloader in an unofficial way and flashed vbmeta.img from my firmware?
Click to expand...
Click to collapse
Miflash will erase your data.
Normally not but tried to do a test without locking the bootloader.
Or you can use the Bat files included in the extracted folder of the TGZ file, without Miflash.
Guys, I'm scared. I have all banking applications and device search from xiaomi working with an open bootloader. I don't want to turn my phone into a brick.
I won't try to block bootloader.
IcePhoenix466 said:
I won't try to block bootloader.
Click to expand...
Click to collapse
You should know what you want...