Hello everyone, I locked my smartphone and now I want it back. The only way by which I can operate it from the Fastboot mode presents the recovery of stock Cyanogen. From platform-tools, I would like to unlock the bootloader to install a TWRP recovery, but I can not because I get this message FAILED (remote: oem unlock is not allowed) when I enter this command fastboot oem unlock -i 0x2b4c. Could someone help me? Pretty much in advance.
alessio93 said:
Hello everyone, I locked my smartphone and now I want it back. The only way by which I can operate it from the Fastboot mode presents the recovery of stock Cyanogen. From platform-tools, I would like to unlock the bootloader to install a TWRP recovery, but I can not because I get this message FAILED (remote: oem unlock is not allowed) when I enter this command fastboot oem unlock -i 0x2b4c. Could someone help me? Pretty much in advance.
Click to expand...
Click to collapse
Bro How did you solved this ?
Could you please help me.
I am stuck at the same point.
A solution would be to flash a new factory rom through the QFIL tool.
any link for QFIL ROM ?
aamszia said:
any link for QFIL ROM ?
Click to expand...
Click to collapse
I'll give you next week if needed
Related
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
Can you boot into fastboot mode?
If yes...then boot into fastboot mode and reflash stock firmware using fadtboot commands
droider007 said:
Can you boot into fastboot mode?
If yes...then boot into fastboot mode and reflash stock firmware using fadtboot commands
Click to expand...
Click to collapse
For this i need unlock bootloader.
Example:
Device in fastboot mode
Conected in pc
Command in console cmd:
fastboot flash recovery recovery.img
Then
(Bootloader) preloader
FAILED (remote failure)
Errors..
I need help to unlock bootloader of device whitout check allow oem unlock in device because it no power on!!!
Check how to boot (not flash) to TWRP from fastboot. When you get into TWRP do a Factory Reset and reboot.
mausv said:
Check how to boot (not flash) to TWRP from fastboot. When you get into TWRP do a Factory Reset and reboot.
Click to expand...
Click to collapse
fastboot boot recovery.img
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
same issue with me any solution for this.?
m not able to flash stock firmware it says
E:footer
E:signature failure
and when m unlocking boot loder it says oem unlock error
anujanuj said:
same issue with me any solution for this.?
m not able to flash stock firmware it says
E:footer
E:signature failure
and when m unlocking boot loder it says oem unlock error
Click to expand...
Click to collapse
someone found the solution:?
What error in bootloader log?
Enviado desde mi XT1563 mediante Tapatalk
Can you, at least, boot in stock recovery mode? If you can already boot in fastboot mode, you can use volume up and down keys to toggle between all the options, toggle it until you see "Recovery mode" and then push power button. Your phone will reboot in recovery mode and an option to do factory reset should be there. Stock recovery is less powerful than TWRP recovery but, it if you have a hard time installing TWRP, it could be another solution.
OTA possibly flashing, pushing the sd fastboot
Enviado desde mi XT1563 mediante Tapatalk
check this for enable
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
flopezm said:
check this for enable
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Click to expand...
Click to collapse
what if phone shows internal and external memory not mounted
fix of hardbikd ....
here u go ...1st go fastboot mode n flash the stock file on fastboot mode the ...press power bottom 20 time fastly then u see warning bootloder logo the wait 5min after completing go 2 developsr allow oem ........
anujanuj said:
what if phone shows internal and external memory not mounted
Click to expand...
Click to collapse
Can you explain?
Sent from my XT1562 using Tapatalk
K.khiladi said:
Can you explain?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
nothing this is too old post now my issue is solved
anujanuj said:
nothing this is too old post now my issue is solved
Click to expand...
Click to collapse
Mate your posts are everywhere on the forum.. ??
Sent from my XT1562 using Tapatalk
K.khiladi said:
Mate your posts are everywhere on the forum..
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
yes because my phone was dead and i had fade up
Jhornands said:
Motorola XT1563 Bricked
Hi guys, a Motorola XT1563 ( moto x play) was bricked. I try flash a original rom via rsd lite software and fastboot console cmd. No sucess because a bootloader is locked. I have make this steps in the support site oficial of Motorola for get the unike key and done. But... I try send comand fastboot oem unlock (code) when said:
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Well, this phone was bricked and don't boot... Why i check this setting if device didn't power on????
A biggest error of development i think.
Someone help me to find a solution?
Click to expand...
Click to collapse
Just get flash stock android 5.1.1 rom from fastboot if that doesn't work try getting into recovery mode and flashing the stock rom via adb sideload.
motorola x play ...stuck in boot
I am using a Motorola X Play 32 Gb Dual Sim phone with a Marshmallow 6.0.1
I'm now stuck at bootup with Start Up Failed.
Startup failed Error
your device didn't start up successfully
use the software repair assistant on computer
to repair ur device.
connect ur device to your computer to get
the software repair assistant
AP fastboot flash mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
Error: failed to pass validation. backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
pls Help by step by step methods I am Stuck.....Please
scorpionking3010 said:
I am using a Motorola X Play 32 Gb Dual Sim phone with a Marshmallow 6.0.1
I'm now stuck at bootup with Start Up Failed.
Startup failed Error
your device didn't start up successfully
use the software repair assistant on computer
to repair ur device.
connect ur device to your computer to get
the software repair assistant
AP fastboot flash mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
Error: failed to pass validation. backup to fastboot
Fastboot Reason: Fall-through from normal boot mode
pls Help by step by step methods I am Stuck.....Please
Click to expand...
Click to collapse
same thing for me, been weeks cant find any solution
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.
Hi,
I think my P9 Lite is bricked (L31) :crying:
It happened because I've tried to downgrade from Android N EMUI 5 beta to Android M (EMUI 4.1.1) with the dload folder method. I've extracted and put update.app of my B151 firmware inside then 3 buttons and update said successful, but now bootloop and I can't enter recovery or fastboot (vol down + pwr).... I'm stuck in eRecovery and Wifi check for update fails....
>>> EDIT: Okay, good, I can enter fastboot but it says:
"Please connect usb cable, blah blah" (My phone is connected)
Android boot reason
AP_S_COLDBOOT
NA
Volume_down_press_process_func
PHONE locked
FRP Unlock
----
Do I have to unlock the bootloader? If yes, how can I do since I can't boot on Android?
Can I unlock it with fastboot commands or other ways? How?
----
Currently, with fastboot commands, I can't flash system.img or recovery.img. For instance, trying to flash system.img or recovery.img, it says:
C:\Users\Supergren>fastboot flash system "d:/system.img"
target reported max download size of 471859200 bytes
sending sparse 'system' (451070 KB)...
OKAY [ 19.381s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 19.395s
I guess it's because my bootloader is locked...
I'm a bit lost
>>> EDIT 2: to solve the bootloop after downgrading from N beta to M (b151), I just had to:
1- Shutdown my phone
2- Plug to my computer. That's what I forgot previously to be able to start fastboot mode!
3- Press Volume down + PWR
4- Once in fastboot/rescue mode, open cmd window on my PC and type:
fastboot oem unlock <unlock code> . (For instance: fastboot oem unlock 1234567890123456)
5- Follow unlock procedure instructions and then the phone does a factory reset.
6- The phone reboots and it's done
Wood Man said:
Hi,
I think my P9 Lite is bricked (L31) :crying:
I can enter fastboot but it says:
"Please connect usb cable, blah blah" (My phone is connected)
Android boot reason
AP_S_COLDBOOT
NA
Volume_down_press_process_func
PHONE locked
FRP Unlock
----
Do I have to unlock the bootloader? If yes, how can I do since I can't boot on Android?
Can I unlock it with fastboot commands or other ways? How?
----
Currently, with fastboot commands, I can't flash system.img or recovery.img. For instance, trying to flash system.img or recovery.img, it says;
...
FAILED (remote: Command not allowed)
...
I guess it's because my bootloader is locked...
I'm a bit lost
Click to expand...
Click to collapse
Maybe unlocking the bootloader may help. On fastboot you type fastboot oem unlock
Wood Man said:
Hi,
I think my P9 Lite is bricked (L31) :crying:
I can enter fastboot but it says:
"Please connect usb cable, blah blah" (My phone is connected)
Android boot reason
AP_S_COLDBOOT
NA
Volume_down_press_process_func
PHONE locked
FRP Unlock
----
Do I have to unlock the bootloader? If yes, how can I do since I can't boot on Android?
Can I unlock it with fastboot commands or other ways? How?
----
Currently, with fastboot commands, I can't flash system.img or recovery.img. For instance, trying to flash system.img or recovery.img, it says;
...
FAILED (remote: Command not allowed)
...
I guess it's because my bootloader is locked...
I'm a bit lost
Click to expand...
Click to collapse
To unlock bootloader type ,,fastboot oem unlock.......,,(.....is your unlock code)
To unlock the bootloadee you have to type :
fastboot oem unlock 1234567891234
Sent from my HUAWEI VNS-L31 using XDA Labs
You are all gods! It's solved!
Thanks a lot guys! I really appreciate your fast answers :good:
I've read on the web about the "fastboot oem unlock" method but I didn't know if it worked with P9 Lite. I was afraid to totally brick the phone.
See you later!
Edit: I've updated the thread title with [SOLVED] and wrote what I did to achieve this.
Hey ! You got the same problem as me, excuse me how did you get the unlock code if you couldn't boot the phone... I read and read and your problem was the same i have ... but when i got to fastboot i can't unlock, i dont have the unlock code sh**. Thank you and sorry for my english everybody i hope your eyes didn't hurt hehe
EDIT: I just got the unlock code but I think i'm screwed up... When in fastboot&rescue mode it says FRP Lock... sh**
1francis said:
Hey ! You got the same problem as me, excuse me how did you get the unlock code if you couldn't boot the phone... I read and read and your problem was the same i have ... but when i got to fastboot i can't unlock, i dont have the unlock code sh**. Thank you and sorry for my english everybody i hope your eyes didn't hurt hehe
EDIT: I just got the unlock code but I think i'm screwed up... When in fastboot&rescue mode it says FRP Lock... sh**
Click to expand...
Click to collapse
Frp lock means Factory Reset Protection. If it says Phone UNLOCKED means ur bootloader is unlocked.
1francis said:
Hey ! You got the same problem as me, excuse me how did you get the unlock code if you couldn't boot the phone... I read and read and your problem was the same i have ... but when i got to fastboot i can't unlock, i dont have the unlock code sh**. Thank you and sorry for my english everybody i hope your eyes didn't hurt hehe
EDIT: I just got the unlock code but I think i'm screwed up... When in fastboot&rescue mode it says FRP Lock... sh**
Click to expand...
Click to collapse
go to developer option and activate oem unlocking
this will unlock frp
Right. The issue is that phone is stuck on huawei logo
1francis said:
Right. The issue is that phone is stuck on huawei logo
Click to expand...
Click to collapse
Buy DC phoenix 15euros and flash it same happen to me last day
Hi all,
I've unlocked my A2017 Chinese bootloader,
Installed TWRP and B29 base rom.
Everything worked great until I made a mistake and relocked the bootloader.
Now the phone just showing the ZTE blue logo and turn off.
I can boot to the bootloader with holding both volume up+down but when I try to oem unlock it i get:
FAILED (remote: oem unlock is not allowed)
The system is not booting so I can't allow oem unlock from developer menu.
What can I do?
Thank you in advance.
shaigr said:
Hi all,
I've unlocked my A2017 Chinese bootloader,
Installed TWRP and B29 base rom.
Everything worked great until I made a mistake and relocked the bootloader.
Now the phone just showing the ZTE blue logo and turn off.
I can boot to the bootloader with holding both volume up+down but when I try to oem unlock it i get:
FAILED (remote: oem unlock is not allowed)
The system is not booting so I can't allow oem unlock from developer menu.
What can I do?
Thank you in advance.
Click to expand...
Click to collapse
Hi, you need to flash the bootloader accepted recovery.img first. Download the latest B13 chinese official rom and extract recover.img. Use the command to flash it:
fastboot flash recovery recovery.img
Then reboot to this official recovery, and flash the B13 official rom. Now you can restart your previous bootloader unlocking process( actually I have no idea of how you succeed on the A2017 model). Good luck!
----second thought:
I doubt if you can successfully execute the command
fastboot flash recovery recovery.img
since your bootloader is locked. Just wish you good luck!
Hello, I'm new here so if I miss any Forum rules please let me know.
TL;DR: I unlocked the bootloader of my VNS-L31 with PotatoNV and now I get the Message FAILED (remote: 'image verification error')
So, i want to install a Custom ROM in order to get OTG Support for my Smartphone. I'm new to this but as I figured out I need to do the following Steps.
1. Unlock Bootloader using PotatoNV
2. Install TWRP
3. Root via SU
3. Install CustomRom via TWRP
I think I managed to unlock my bootloader as I get the "your device cant be trusted" message every time I boot. I can enter fastboot mode with ADB and my device is recognized when it's in fastboot mode. when I try now to install TWRP (i tried different versions) I get the following message:
J:\Smartphone\TWRP\platform-tools_r31.0.2-windows\platform-tools>fastboot flash recovery twrp-3.1.1-0-venus.img
Sending 'recovery' (24464 KB) OKAY [ 0.648s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed
Reading the Forums suggested to relock the Bootloader and then unlock it again in good old " did you turn it off and on again" manner. but when I googled how to relock and unlock I got the warning that a lot of devices cant be unlocked a second time. So should I try to relock it via fastboot ? if I do so, can I unlock it again with the new unlockcode i set in PotatoNV, or do I need to open my phone for Testpoint mode and unlock it with PotatoNV again?
so hopefully i didn't miss any necessary information and someone here can help me or point me in the right direction
greetings
Elfenfreund
PS: Pardon my Writing. It's late and my English is not very trained.
No need to relock. Just unlock it again using the code given by the Potato. Then try flashing again the image.