Related
Hi,three monts ago i broke my screen,and than after the repair i would unlock the bootloader for changer Rom,but i followed all the tips,and the command : "fastboot oem get_unlock_data" doesn't still work, i tried all the options but no one worked,adb devices works,fastboot devices too,just this doesn't work.
Here is the code :
C:\Users\Desktop\adb>fastboot devices
TA39100VMQ fastboot
C:\Users\Desktop\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.235s
Let's see a screenshot of your bootloader screen
your boaterload is not possible to unlock, they put another plate, already went through this
What do you mean by another plate?
Sent from my XT1572 using XDA Free mobile app
If I'm not mistaken, if you bootloader was unlocked they have to replace it with one that is unlockable. You depend on is as your a dev...... Nowhere have I seen they made it not unlockable.
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
SeaVanquish said:
Hi,three monts ago i broke my screen,and than after the repair i would unlock the bootloader for changer Rom,but i followed all the tips,and the command : "fastboot oem get_unlock_data" doesn't still work, i tried all the options but no one worked,adb devices works,fastboot devices too,just this doesn't work.
Here is the code :
C:\Users\Desktop\adb>fastboot devices
TA39100VMQ fastboot
C:\Users\Desktop\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.235s
Click to expand...
Click to collapse
Does
Code:
fastboot reboot
Work, or give the error? In developer options, is "OEM unlocking" on?
gokart2 said:
If I'm not mistaken, if you bootloader was unlocked they have to replace it with one that is unlockable. You depend on is as your a dev...... Nowhere have I seen they made it not unlockable.
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
Does
Code:
fastboot reboot
Work, or give the error? In developer options, is "OEM unlocking" on?
Click to expand...
Click to collapse
Yes,it works,and yes, i've enabled OEM unlocking.
SeaVanquish said:
Yes,it works,and yes, i've enabled OEM unlocking.
Click to expand...
Click to collapse
Are you using a Windows or Linux PC?
SeaVanquish said:
Hi,three monts ago i broke my screen,and than after the repair i would unlock the bootloader for changer Rom,but i followed all the tips,and the command : "fastboot oem get_unlock_data" doesn't still work, i tried all the options but no one worked,adb devices works,fastboot devices too,just this doesn't work.
Here is the code :
C:\Users\Desktop\adb>fastboot devices
TA39100VMQ fastboot
C:\Users\Desktop\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.235s
Click to expand...
Click to collapse
I changed the screen once and it seems that they change the plate too, and put a board that is not possible to unlock the boaterload, so this error, you can not unlock unless to replace the card with a unlockable
gokart2 said:
Are you using a Windows or Linux PC?
Click to expand...
Click to collapse
Windows
SeaVanquish said:
Windows
Click to expand...
Click to collapse
Ok.... I had some weird fastboot issues with Linux. Was gonna see if that fix would work for you if you were on Ubuntu.
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)
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.
Hello, i have a serious problem with my U Ultra.... Last night I unlocked the bootloader, I installed TWRP(lastest version from official site), before all this I made backup (with TWRP) of every partition and then I make back-up of system, data, boot I think, I have everything on my laptop.
But I wanted to back on stock (Don't ask me why...) and i restored a back-up, a full back-up of every partitions. Everything great, but google play didn't had Device Certification: Uncertified like in this pic and I tried to do this method and it didn't worked and I don't know why I thought that if I will relock the bootloader, everything will be okay :| and now I don't have TWRP anymore and of course neither stock recovery, but the stock rom boots but the password I have made it, is not working.
Tried to unlock bootloader but this error shows up
Code:
diesel-X550CL Downloads # fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Now how can I solve this problem?
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
QDT said:
How did you did the bootloader relocking?
For what purpose you need the Google Play certification?
Click to expand...
Click to collapse
Through fastboot with this command:
Code:
fastboot oem lock
I don't need it for a special purpose but some apps don't work and I saw that was the solution, anyways I don't need that no more, I just want the phone to work....
Just go to fastboot mode perform oem unlock and reinstall the twrp
QDT said:
Just go to fastboot mode perform oem unlock and reinstall the twrp
Click to expand...
Click to collapse
Code:
fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1578400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.006s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
I can't because oem unlock is not turned off
kempactick said:
I can't because oem unlock is not turned off
Click to expand...
Click to collapse
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
QDT said:
You don't need to use the HTC file. Your phone is permanently hardware unlocked since the first flash.
All you now need to do is simple
Code:
fastboot oem unlock
Click to expand...
Click to collapse
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
kempactick said:
i tried this one too...
Code:
diesel-X550CL Downloads # fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.005s
This error are just because of oem unlock from developer settings.. How can I trick this?
Click to expand...
Click to collapse
In what mode are you?
QDT said:
In what mode are you?
Click to expand...
Click to collapse
I'm on download mode, bootloader mod ain't for flashing
kempactick said:
I'm on download mode, bootloader mod ain't for flashing
Click to expand...
Click to collapse
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
QDT said:
Then what I can only advise is getting RUU of your system's current or newer version and force to reflash everything including bootloader.
Click to expand...
Click to collapse
Tried to flash RUU but is not working too, i'm trying with htc sync right now
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
iAlcatrazZ said:
I have the same issue after relocking my phone. Before I decided to lock my phone to downgrade to nougat, I did flash twrp and a rooted stocked oreo rom. After locking my phone using fastboot my phone stuck into download mode bootloop, I was able to get into download mode properly but I couldn't afford to download ruu from easy-firmware to flash in ruu mode
Click to expand...
Click to collapse
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
kempactick said:
I couldn't solve the problem myself, so I went to a gsm service and they couldn't solve it, 1 month of trying and one day my dad told me to go to the warranty service and I didn't, he went there and I don't know how they accepted the phone with the another reason and in a hour they solved the problem. I'm still using the phone and I can't wait to get rid of it.
So... I don't know how to help you, you should go to a gsm service, regards!
Click to expand...
Click to collapse
I managed to restore my phone :v, I could partially remember how I did it, I'm still gathering resources so that I can write a complete guide for everyone
rom unbrick Mi6x LINK : drive.google.com/file/d/1fZyJ2orTrMpsNzWbhKGR8kvSYf-8KGRS/view?usp=sharing
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
mrdamnguyen said:
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
Click to expand...
Click to collapse
Guys does this actually unbrick a converted mi 6x wayne locked bootloader arb 4???
Quantumkk123 said:
Guys does this actually unbrick a converted mi 6x wayne locked bootloader arb 4???
Click to expand...
Click to collapse
the thing is that if it is a rom.zip, with yr situation how can you flash it when yr bootloader is locked and no twrp.
Or u try first and let people know
I want to unbrick on pie, need developer version for 9.0
jaggyjags said:
I want to unbrick on pie, need developer version for 9.0
Click to expand...
Click to collapse
You don't need it your gonna have to downgrade back to Oreo it's same arb so nothing bad will happen XD
Quantumkk123 said:
You don't need it your gonna have to downgrade back to Oreo it's same arb so nothing bad will happen XD
Click to expand...
Click to collapse
then why do I get this message with oreo MIUI 10.2 rom?
View attachment 4727603
jaggyjags said:
then why do I get this message with oreo MIUI 10.2 rom?
Click to expand...
Click to collapse
If your bootloader is locked that's the reason why ,if it's not then you haven't put your phone into fastboot oem edl
Quantumkk123 said:
If your bootloader is locked that's the reason why ,if it's not then you haven't put your phone into fastboot oem edl
Click to expand...
Click to collapse
Code:
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.011s
this is weird
jaggyjags said:
Code:
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.011s
this is weird
Click to expand...
Click to collapse
its because your doing it via fastboot and because you have arb it won't permit what your gonna do now is go on to your cmd or whatever type this command
.\adb fastboot oem
then hit refresh on mi flash then click flash if that still doesnt work then i am afraid you need to open up your device mate
Quantumkk123 said:
its because your doing it via fastboot and because you have arb it won't permit what your gonna do now is go on to your cmd or whatever type this command
.\adb fastboot oem
then hit refresh on mi flash then click flash if that still doesnt work then i am afraid you need to open up your device mate
Click to expand...
Click to collapse
opening up my device is not a problem. Can you guide me on what to do with the mainboard?
HTML:
C:\Users\jags1\Desktop\wayne\ADB>.\adb fastboot oem
adb: usage: unknown command fastboot
C:\Users\jags1\Desktop\wayne\ADB>.\adb fastboot oem
adb: usage: unknown command fastboot
C:\Users\jags1\Desktop\wayne\ADB>fastboot oem
fastboot: usage: empty oem command
C:\Users\jags1\Desktop\wayne\ADB>
your command was correct?
thankyou for your help
jaggyjags said:
this is weird
Click to expand...
Click to collapse
Ok you seems to be lost lol ? emm chat to this group on telegram and I will guide you ... https://t.me/A2_6X
password
mrdamnguyen said:
link : drive.google.com/file/d/1dyaJr1IgS8Rwk0GI-BJJ-SaKdWWVnk8o/view?usp=sharing
Click to expand...
Click to collapse
give mepassword