Database Users

[NOOB GUIDE] Unroot/Relock Bootloader - VZW Developer Edition Moto X

It took me about two days to figure out how to unroot and relock my Moto X. Figured I'd create a total noob guide for those who are also looking to do the same. This is for the Verizon Wireless Developer Edition Moto X ONLY! I have no clue if this will work for other variants like Sprint, AT&T, T-Mobile, etc. So just play it safe and don't...
I've unrooted and relocked my VZW Dev Edition Moto X twice using this method, so as long as you follow the steps below you should be fine. Also please note that I'm not at all responsible for anything that happens to your beloved phone.
Btw, this process wipes your phone completely clean, so back your sh** up.
So here goes.
1. You need a Windows PC.
2. Download and install the Motorola Device Manager (USB Drivers) to your PC. This will allow your Moto X to be recognized by your computer.
3. Plug your Moto X into your PC and let the drivers install automatically.
4. Download and unzip the VZW Developer Edition Factory Image for the Moto X to your desktop.
5. Download both the fastboot.exe and AdbWinApi.dll files and place them in the folder you just unzipped in step step 4.
6. Now grab your Moto X, unplug it from your PC and power it off. Once powered off, press and hold both the Power and Volume Down buttons for about 10 seconds or so to access Fastboot mode.
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Right Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
8. In the command prompt type fastboot devices to make sure your X is being detected. You should see something similar T0620059GA. If you don't see it, then you may have to reinstall the USB Drivers from Step 2.
9. Once your X has been detected by your computer, and while still in Fastboot mode, type the following commands (in the order shown) into the command prompt on your PC:
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
fastboot 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 cache
fastboot oem lock
fastboot reboot
...
That's it! You should now be locked and unrooted; back to the out of the box factory state. Don't forget to hit thanks and share!

Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?

tonyf7 said:
7. Now, back on your PC, open the folder you extracted on Step 4. Hold down the Shift key on your keyboard and Left Click on an empty space within that folder. From the menu that pops up, click on Open command window here. A command prompt window should open. Plug your phone back into your PC.
Click to expand...
Click to collapse
Right click sir.

mschumacher69 said:
Did re-locking ur bootloader get rid of the Bootloader Unlocked Warning Message?
Click to expand...
Click to collapse
Yes.

tonyf7 said:
Yes.
Click to expand...
Click to collapse
Just to make sure we're on the same page here, after re-locking ur bootloader, when u boot the phone, u get the Moto logo instead of the message that says Warning Bootloader Unlocked?
Because many other users said that u would still get this message even if u re-lock ur bootloader.

When I relocked the bootloader and rebooted the phone I didn't get the warning message. Went straight to the Moto logo. But then I immediately rooted and unlocked again. Only reason I unrooted and relocked in the first place was because I flashed a zip file that corrupted and broke Google Voice Search on my phone.
The second time I did this process I stopped right before locking the bootloader since I was going to root again anyways.
So maybe those other people are right. I've only rebooted my phone once since relocking the bootloader.
Sent from my XT1060 using xda app-developers app

If you want to get rid of the warning on startup, just flash the logo.bin. You can do this and remain unlocked. The instructions provided should have your phone looking and acting the same as it did out of the box. However, fastboot may note that it's been unlocked, to the OP, do you recall what status fastboot was reporting?

you need to reflash to stock in order to lock your bootloader? If not, I would appreciate if you separate the steps to just lock your boot loader.
I have my boot loader unlocked and the only reason I am considering to lock it again is so that if the phone is stolen, someone can't reimage it easily. I'm not sure that gives me any sort of protection though. But its just a thought.
In other words, I see unlocking and locking as a switch that stops you from flashing firmware. The OP makes it sound like the switch is tied to the firmware, ie only stock can have bootloader locked. I am not sure which is right.

esidnD Selim
I did it and keep receiving the warning unlock bootloader screen.

lopescesar304 said:
I did it and keep receiving the warning unlock bootloader screen.
Click to expand...
Click to collapse
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?

mschumacher69 said:
Did u re-lock on your phone's ROM or after flashing another carrier's ROM?
Click to expand...
Click to collapse
My phone is Retail, I used the retail ROM to flash.

My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?

flavinator said:
My device won't lock. I've run your commands listed, as well as the fastboot oem lock on it's own, and I can't seem to lock the device. Any help?
Click to expand...
Click to collapse
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G

NWKENT said:
Welcome to the "Relock" party..
The OP does not mention (that I can see) what OS version..are you on KK 4.4 and is there a "Factory Image" for KK 4.4 available for your device.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.

flavinator said:
Yes, there is, flashed it, ran commands, and the relock command, multiple times and get:
(bootloader) FAIL: Please run fastboot oem lock begin first!
OKAY [ 0.120s]
finished. total time: 0.122s
Not sure what I am doing wrong.
Click to expand...
Click to collapse
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G

http://forum.xda-developers.com/showthread.php?t=2575586

NWKENT said:
I'd think you ran this as the first flash >> fastboot oem lock begin first!
Then all the OS files and then this for the last command >> fastboot oem lock > as the last command.?
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G
Click to expand...
Click to collapse
I have no clue. At first I just flashed back using RSD Lite. Then I ran the lock command and got that error. Afterwards, I searched online, trying a bunch of different fastboots. That's when I stumbled on this list of commands, figured I'd run it from scratch, see if it makes a difference. Once it got to the relock command though, I got the same issue. And now I'm just frustrated...
---------- Post added at 06:41 PM ---------- Previous post was at 06:36 PM ----------
shane1 said:
http://forum.xda-developers.com/showthread.php?t=2575586
Click to expand...
Click to collapse
I think this might work, thanks shane1

@NWKENT have u managed to re-lock your bootloader yet?

mschumacher69 said:
@NWKENT have u managed to re-lock your bootloader yet?
Click to expand...
Click to collapse
Yes Sir..with Kit Kat 4.4..I have successfully"Unlocked", "Relocked" and "Unlocked" again..my XT1080MDEV (Droid Maxx)..No one could tell me exactly how to do it..Motorola Tech Line was absolutely NO HELP either..SO..after hours upon hours..I did figure it out..Now I'm working on "Relock" on JB 4.2.2
Sounds easy..and many have probably "Unlocked and "Relocked" on JB 4.2.2..BUT..The difficult part is once the XT1080 has been on KK 4.4..is when alot more firey hoops must be jumped thru..
ANYONE can chime in with help on this..NOT ADVICE..but proven procedures..
sent by my 4.3_14.14.14
XT1028 (aka) Moto-G

Yes, thanks guys.

ADB error. Need Help

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (22732 KB)...
OKAY [ 0.489s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.499s
How do i fix this error? It's preventing me from installing twrp on my device. I have my bootloader unlocked and yet it refuses to work everytime.

Bootloader and frp unlock ?

jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
I lost patience and decided to relock my bootloader and unlock it again. Now i face another mess of a problem.

jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.

Ribombee said:
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.
Click to expand...
Click to collapse
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?

dexz said:
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?
Click to expand...
Click to collapse
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.

Ribombee said:
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.
Click to expand...
Click to collapse
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)

dexz said:
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)
Click to expand...
Click to collapse
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.

Ribombee said:
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.
Click to expand...
Click to collapse
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.

dexz said:
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.
Click to expand...
Click to collapse
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?

Ribombee said:
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?
Click to expand...
Click to collapse
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
P/S: You don't need to enable usb debugging to unlock your bootloader.

dexz said:
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
Click to expand...
Click to collapse
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.

Ribombee said:
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.
Click to expand...
Click to collapse
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1

dexz said:
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1
Click to expand...
Click to collapse
Well that just made things ten times better.

I should probably just give up on the phone.

You can just "rollback" to Emui 4.0 and unlock the Oem Unlock setting in Developer Options.

Zenfone 3 ZE552KL RELOCK BOOTLOADER

Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.

Ive tried asking this before for my Ze520kl, someone said it isn't possible to relock the bootloader

I would like to know if someone has an update about that...
When I tried to root my phone (ZE552KL Androïd 7.0) I installed an app to unlock the bootloader of my phone (ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715). I used it and ever since, when I turn on my device, I get a warning screen saying "Your device software cannot be checked for corruption. Please lock the bootloader." It sends me to this link for information. The notification disappear after 10 seconds and androïd starts.
I was quite stupid to do that because I do not have to knowledge to properly root my device. So I give up, but I would like to get back my device without that security warning.
I have already flashed it from the recovery menu, with an sd card, wiping data and cache. But it didn't work.
Any advice?

my69 said:
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Click to expand...
Click to collapse
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough

Commands do not work.
gkillershots said:
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Click to expand...
Click to collapse
Commands do not work.

myheartloves said:
Commands do not work.
Click to expand...
Click to collapse
well, I think Asus disabled thoose ones
sorry

A2017G fastboot oem lock

Hi
I am trying to relock the BL for warranty.
I did a EDL-FULL-Nougat, then found out that Nougat does not boot into bootloader.
So I downloaded A2017G_NrollbackM from ZTE, which worked nicely. I'm in bootloader now and see
Code:
C:\>fastboot getvar unlocked
unlocked:
finished. total time: 0.008s
which was expected.
... just I don't understand, why I can't lock or get oem device-info
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
please help, thanks alex

did you enable 'oem unlock' on the developer settings?

yes, sorry forgot to add

lxlx said:
yes, sorry forgot to add
Click to expand...
Click to collapse
so i guess you have been able to lock it?

No, I mean I forgot to add that info in my first post.
I can not run device-info or lock, log posted.
Cheers :/

your Fastboot.exe is too old

Choose an username... said:
so i guess you have been able to lock it?
Click to expand...
Click to collapse
but you didn't even respond to my question
did you enable 'oem unlock' on the Developer settings?

skdubg said:
your Fastboot.exe is too old
Click to expand...
Click to collapse
that sounds promising, where to get the up-to-date fastboot.exe?
Choose an username... said:
but you didn't even respond to my question
Click to expand...
Click to collapse
I tried, but my non-native english failed apparently.
So to be clear:
Choose an username... said:
did you enable 'oem unlock' on the Developer settings?
Click to expand...
Click to collapse
yes I had oem unlock in dev-options enabled. Then I tried
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s

Post deleted. Didn't notice you are on mm.

lxlx said:
that sounds promising, where to get the up-to-date fastboot.exe?
Click to expand...
Click to collapse
The 15 seconds ADB installer should install the newest fastboot available. But be sure to get rid of the old installation

How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...

lxlx said:
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
Click to expand...
Click to collapse
This hasn't got anything to do with the drivers. I mean, delete the fastboot.exe and adb.exe that you have, then download the "15 seconds ADB installer" and install it, and try again

OK, a bit more digging.
I have 15sec-adb installed systemwide in C:\adb>
Code:
C:\adb>dir /B
aboot.img
aboot_lock.img
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
strings.exe
as you can see, I put my aboot dumps there as well, and a strings-linux-like tool - after
reading this thread.
so, I got the ZTE driver to have my Axon7 visible to adb/fastboot (otherwise no device) ... and I have the latest 15sec adb here.
Code:
C:\adb>fastboot devices
823b48f5 fastboot
... but that's the only thing that works. not even easy things like this do
Code:
C:\adb>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.015s
quoting the other thread
What’s missing in this list are fastboot oem commands. These commands are specific to Android device manufacturers, and there is no comprehensive list or documentation anywhere for what fastboot oem commands are available.
Click to expand...
Click to collapse
so I'm not sure if my fastboot version is the problem. I rather think that the Nougat->MM stock thingy, overwrite my Axon7 aboot.img with only a small set of fastboot commands available.
in my backup I see
Code:
C:\adb>strings aboot* | findstr /i oem
C:\adb\aboot.img: 04 0004 OEM_ID1
C:\adb\aboot.img: oem unlock is not allowed
C:\adb\aboot.img: oem unlock
C:\adb\aboot.img: oem unlock-go
C:\adb\aboot.img: oem lock
C:\adb\aboot.img: oem device-info
C:\adb\aboot.img: is_oem_unlock_allowed
C:\adb\aboot_lock.img: 04 0004 OEM_ID1
C:\adb\aboot_lock.img: oem unlock is not allowed
C:\adb\aboot_lock.img: oem unlock
C:\adb\aboot_lock.img: oem unlock-go
C:\adb\aboot_lock.img: oem lock
C:\adb\aboot_lock.img: oem device-info
C:\adb\aboot_lock.img: is_oem_unlock_allowed
so in old and new aboot I had oem-commands available, back then...
I'm not an expert, but do you guys really know that my problem is related to the PC-config I have, and not to the device-config?
I can not check aboot on device, as I'm not root.

update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck

lxlx said:
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
Click to expand...
Click to collapse
Pretty sure miflash cannot lock your bl.

Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.

lxlx said:
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
Click to expand...
Click to collapse
I think it is still unlocked. I read something weird about the message not appearing after having a full stock system
But if you're gonna sell it/claim warranty, who cares?

update, ZTE repaired the display

lxlx said:
update, ZTE repaired the display
Click to expand...
Click to collapse
Did you lock the bootloader after all?
I guess they wouldn't even notice if the 5 sec screen didn't show up lol

BL still unlocked.
I sent it with MM-B10-FULL-EDL, where 5sec screen was not displayed.
And got it back with MM-B06 ... with 5sec screen
so I guess what happened:
- ZTE turns on, does not see 5sec, repairs display, does usual EDR 'update' which is actually a downgrade to MM-B06, then sees 5sec-warn and thinks of what to do now, but as screen is repaired, what else than return
OR
- ZTE repairs screen (VIP) although bootloader unlocked
either way, all good.
what I learned is
- fastboot parameters need to be in aboot.img
- I can't do getvar or oem-lock until I flash another aboot.
Anyone with A2017G and unlocked BL who needs to send back:
EDL to A2017G_B10_FULL_EDL.zip
and hope you also have hidden 5sec screen (BL still unlocked)

PRA-LX1 stuck in bootloop, can't be turned off - locked, access to fastboot only!

Hello xda,
my cousin owns the P8Lite (PRA-LX1) and gave it to me to attempt unbricking it.
The device is stuck in a permanent bootloop, showing the Huawei logo. When pressing the power button for ~10s, it simply turns itself on again (even when not connected to a PC or the wall socket), which to me is very strange behaviour but I do not own a Huawei device.
I can get to fastboot (https://ibb.co/ixPtAn).
ADB does not recognize the device.
Fastboot does not let me boot a temporary recovery (be it the stock one or twrp), neither does it allow me to flash any file.
I have tried downloading the update.app file onto the root directory of the sd card and force the phone into the update mode (power, vol+, vol- at the same time) but to no avail.
Since it is not my own device and I cannot boot into Android at all, I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Is this device permanently bricked and a lost cause or is there still hope?

dejavecue said:
I have no way of getting to the IMEI of the device, which I would need to unlock the bootloader.
Click to expand...
Click to collapse
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH

badhabitsdiehard said:
Hi,
IMEI should be engraved on the lower SIM tray if it's the original one.
HTH
Click to expand...
Click to collapse
Oh yes I got the original one. But since I cannot boot, I cannot get the S/N that is apparently required as well.
Edit: Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website. It still says
PS C:\Users\*\Downloads\unlock bootloader> fastboot oem unlock ************
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\Users\*\Downloads\unlock bootloader>
Click to expand...
Click to collapse

dejavecue said:
Got the SN through fastboot devices.
Now the phone won't accept the unlock code that I got from huawei's website.
Click to expand...
Click to collapse
Hi, sorry for the delay.
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?

Thank you for your comment:
badhabitsdiehard said:
Try this, if not already tried: fastboot oem emmc_diag
It should check the status of emmc and tell you if it's ok.
Click to expand...
Click to collapse
Code:
$ fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.012s]
finished. total time: 0.014s
badhabitsdiehard said:
Does this command: fastboot oem lock-state info work on your phone?
And putting the code Huawei sent you in this one fastboot oem frp-unlock?
Click to expand...
Click to collapse
Code:
$ fastboot oem frp-unlock {password censored}
...
FAILED (remote: password matching failed!!)
finished. total time: 0.211s
It is definitely the code I got from the Huawei Website.