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)
Related
I noticed there were 2 newer images on the Google developers page and thought I would flash the latest and greatest (MDB08M) since it wasn't coming down OTA. I enabled Developer Options and set USB debugging and OEM unlock, rebooted to bootloader, did a fastboot oem unlock, rebooted then back to bootloader and ran the flash-all.bat from the new image, rebooted and all was well. I re-enabled USB debugging and went back to bootloader to re-lock the bootloader and am getting an error:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Results of fastboot getvar version-main are blank:
version-main:
finished. total time: -0.000s
I rolled back to MDB08K but it made no difference. I then tried rolling back to MDA89D and letting it pull MDB08K OTA but that too made no difference.
Any suggestions?
Are you using the following command after flashing stock images?
fastboot flashing lock
Click to expand...
Click to collapse
Cares said:
Are you using the following command after flashing stock images?
Click to expand...
Click to collapse
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
boofa said:
No, I was trying to do "fastboot oem lock". "fastboot flashing lock" relocked the bootloader, but fastboot getvar version-main is still blank. I suppose I have achieved my goal of relocking the bootloader, but should I worry about the version-main being blank?
Click to expand...
Click to collapse
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Cares said:
That I have no idea. I just know that the fastboot commands have changed so that's why you couldn't relock.
Click to expand...
Click to collapse
Why are you locking the bootloader anyway? If you're flashing system images and then locking the bootloader you are risking having a device with a non-functioning OS and no way to fix it. Either stay locked and wait for OTA's or leave it unlocked.
I was going to root it, but decided against it since I only needed root for Tasker and WiFi hotspot in the past and I get WiFi hotspot at no charge since switching to Fi. I'll just do without the Tasker stuff since alot of what it was doing is probably not necessary any more and was setup back on Jellybean. I wasn't attempting to lock the bootloader until I had done a clean boot and verified basic functionality. I'm all good now though, thanks for the assist.
hi i am new user to mate 8 and i want ask how relock the bootloader because i received unlock i try with fastboot cammand but he write me that
FAILED (remote: Command not allowed)
finished. total time: 0.015s
that i write in cmd to lock is fastboot oem lock and my bootloader code
please help me thanks
winnie19810 said:
hi i am new user to mate 8 and i want ask how relock the bootloader because i received unlock i try with fastboot cammand but he write me that
FAILED (remote: Command not allowed)
finished. total time: 0.015s
that i write in cmd to lock is fastboot oem lock and my bootloader code
please help me thanks
Click to expand...
Click to collapse
fastboot oem relock (+your code )
I think that's the syntax
try my tool [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility
Does relocking get rid of the message saying your device has been tampered with?
somboons said:
try my tool [TOOL] SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility
Click to expand...
Click to collapse
Dont detect my phone.
On command line detect, but in your too,l don't detect on fastboot mode.
ovitaIRC said:
Dont detect my phone.
On command line detect, but in your too,l don't detect on fastboot mode.
Click to expand...
Click to collapse
Type fastboot oem lock
fastboot oem lock does not working, fastboot oem relock does, but after that you will only see relocked in fastboot mode. If you want to send back your phone to the Service in guarantee, you need to have the Locked status (if not, relocked is fine).
To do that, follow this guide:
http://forum.xda-developers.com/mate-8/general/whats-happened-message-boot-screen-t3321943
When I updated the phone software (UPDATE.APP dload method) my phone got relocked
I go from B193 to B320 and go back to B180/193,the Bootloader is “Locked“ after this Procedur.
There is any method to know my phone bootloader is unlocked or not?
I suspecting that my phone is Chinese version and technical from mobile store flash Global firmware on it.
I saw him running my phone on fastboot mode to flash Global firmware.
P/s: I'm using SD variant
While in fastboot mode issue this command
Code:
fastboot oem device-info
It will inform you of the lock status.
https://www.reddit.com/r/Xiaomi/wiki/advanced/bootloader
corkiejp said:
While in fastboot mode issue this command
Code:
fastboot oem device-info
It will inform you of the lock status.
https://www.reddit.com/r/Xiaomi/wiki/advanced/bootloader
Click to expand...
Click to collapse
Thank you.
Code:
C:\Users\Archmage>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.020s]
finished. total time: 0.024s
According from some 'research' I do before, this is locked.
I applied for unlocking bootloader, will have to wait 10 days or something for approve.
Archmage1809 said:
Thank you.
According from some 'research' I do before, this is locked.
I applied for unlocking bootloader, will have to wait 10 days or something for approve.
Click to expand...
Click to collapse
Correct your bootloader is locked.
Getting permission can take up to 2 weeks, but got mine in 2 days.
corkiejp said:
Correct your bootloader is locked.
Getting permission can take up to 2 weeks, but got mine in 2 days.
Click to expand...
Click to collapse
Hi ... a hint about the error of the unlock tool stuck at 50 % ???
gcarmagnani said:
Hi ... a hint about the error of the unlock tool stuck at 50 % ???
Click to expand...
Click to collapse
corkiejp said:
For people stuck at 50%.
Don't know where I read this tip.
Have you got the correct drivers for your device installed.
Try installing English version of MiPCSuite, which will install the drivers for the device as well.
Edit: Or install Miflash which has the RN3 drivers also.
Click to expand...
Click to collapse
Doesn't work for everyone. See this thread for more discussion.
hello guys,
i rooted my phone, but it has a display mistake and i will send it to zte.
i flashed the original stock rom with twrp, and i flashed the stock recovery with twrp! with adb and fastboot not working!!
FAILED (remote: unknown command) by any commands, example: fastboot flash recovery recovery.img the failure!
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
364f5261 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
364f5261 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.016s
i dont know if my bottloader is locked or unlocked and i must locked it because i want to sent my device to zte!
any ideas?
thank you very much
my device axon7 2017G.
If you never connected the A7 to your computer and sent the fastboot command "fastboot oem unlock" to your device, it's still locked.
Additionally, when you reboot into bootloader, it'll display the lock status on the screen.
xtermmin said:
If you never connected the A7 to your computer and sent the fastboot command "fastboot oem unlock" to your device, it's still locked.
Additionally, when you reboot into bootloader, it'll display the lock status on the screen.
Click to expand...
Click to collapse
Hello i rooted My device with the axon7 root tutorial, ADB reboot edl and axon7root.exe and so on.
After that method is the bootloader locked or unlocked?
If i reboot in fastboot modus, there is only a zte Android sign, nothing lock status in screen.
pocco00 said:
Hello i rooted My device with the axon7 root tutorial, ADB reboot edl and axon7root.exe and so on.
After that method is the bootloader locked or unlocked?
If i reboot in fastboot modus, there is only a zte Android sign, nothing lock status in screen.
Click to expand...
Click to collapse
Rooting with axon7root.exe does not unlock your bootloader. If you never followed this guide (http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165) or never sent the fastboot command "fastboot oem unlock" to your device, you're still locked.
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.