Just a question about the bootloader - Moto E4 Questions & Answers

Hello there,this probably has been questioned a lot of times but I will ask it anyway.
I'm new to this so I researched a bit about the subject,already downloadead the files and everything is pretty much ready. The only thing that I can't do right now is the bootloader part,basically I put this code on the prompt "fastboot oem get_unlock_data" and all I get is this message "FAILED (remote: unknown command)".
So what should I do ? Is there an alternate command that I can try ?
My phone i a MediaTek and it's model is XT1763
I don't have much else to say so thank you for reading.

Are you in fastboot (bootloader mode) when you issue the command? Here's the procedure I followed.

Thanks that guide worked,apparently I didn't need the code from lenovo and could already unlock it

Related

Zuk Z1: FAILED (remote: oem unlock is not allowed)

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

Bootloader loop - unable to unlock bootloader

Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
minimale_ldz said:
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
Click to expand...
Click to collapse
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
pldeep said:
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
Click to expand...
Click to collapse
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
minimale_ldz said:
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
Click to expand...
Click to collapse
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
pldeep said:
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
Click to expand...
Click to collapse
You've got instructions in this thread:
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Mind that you'll likely have more system.img_sparsechunk files, so make sure you flash all of them (just change commands accordingly).
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
pldeep said:
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
Click to expand...
Click to collapse
Your emmc ship is corrupt. That means your whole storage is broken and not fixable.
But i am able to flash some of the contents of the stock ROM. I get this "Pre flash validation failed" error only when I try to flash some of the files like (system.img_sparsechunk.0-9,recovery.img and gpt.bin). I even tried to reset the emmc_chip, I says that the command was succesfully executed.
Is there any other option left??
I am fighting this battle since a week now.
pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
kpamkar said:
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
Click to expand...
Click to collapse
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with
HTML:
fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
pldeep said:
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
Click to expand...
Click to collapse
In my case I had. 52 version of the ROM. I had a locked bootloader boot loop. But I was able to fix it using rsdLite. Are you using the latest version of the firmware and connecting the ports at the back of the pc? Also install proper drivers
You need to use RETASIA DS, the most recent version
@pldeep
firmware is here.
minimale_ldz said:
@pldeep
firmware is here.
Click to expand...
Click to collapse
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
try flashing it without gpt.bin and bootloader
Try booting into twrp without flashing it. Use fastboot boot command
---------- Post added at 08:44 PM ---------- Previous post was at 08:29 PM ----------
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
What are you trying to flash?
Same problem over here... Did you solve it?
Downloading right now the latest rom image for Moto X Play from this site.... //firmware.center/firmware/Motorola/Moto%20X%20Play/Stock/XT1563/
Hey install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Then run :- Fastboot reboot recovery.img
It will boot to twrp.
Any update for this? I'm in a similar situation now :-/
Tried RSD, it doesn't see my device (fastboot and adb works fine)
install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Click to expand...
Click to collapse
How can I do that?
Also, someone mentioned emmc_chip reset - how to do that?
Thanks

Problems with unlock/relock bootloader and TWRP flashing

Hi, I have Asia-Pacific version of the Huawei Mediapad M3 (BTV-W09C209B005). I'm trying to flash TWRP to gain root access, but I'm encountering problems in the preliminary stage. I've searched for similar problems in the forum, but couldn't find a solution that works for me.
So here are the steps I've done:
1. I received the official bootloader code from Huawei.
2. I used ADB and Fastboot to unlock the bootloader, but I noticed something peculiar: the screen says
Phone UNLOCKED
FRP UNLOCKED
I am the first owner of the tablet, so I was surprised to see that it was already unlocked. In any case, I tried the fastboot oem unlock command, and it returned this error:
FAILED (remote: password wrong)
3. I tried to proceed to TWRP flash on the assumption that the phone was already unlocked. But I get this error:
sending 'recovery' (23794 KB)....
OKAY [ 0.740s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished, total time: 0.740s
4. I tried relocking the bootloader, as per several XDA threads, before unlocking again. But I once again encounter an error:
FAILED (remote: stat not match)
I already contacted Huawei to make sure that the unlock code they sent me was correct, but I doubt that it'd be wrong because they probably just paste it after generating it in the system.
Any ideas how to proceed?
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
lilbrat said:
Interesting, first off if you want to check and see if you phone is BL is unlocked go to Settings, Developer Options and see if your OEM unlocking is grayed or doesn't move..if it doesn't move or grayed out then it's unlocked.. if it moves the it not unlocked.. check that your fastboot /adb are set up correctly. Though the easiest way to this ( unlocking the BL and flashng TWRP) would be to get Huawei Multi-Tool v8 by Team MT and use it,, ( grab the one in the Honor 8, as I know it does work) and make sure you ave the correct TWRP for your tablet..
Click to expand...
Click to collapse
Thanks for pointing me the Huawei multi-tool. So I tried that, and as suspected, the device is still locked. I am able to toggle the OEM unlocking and the tool says so through the lock status (oem lock-state info LOCKED). I proceeded unlocking with the tool, but I received the same error: FAILED (remote: password wrong)
The unlock code doesn't seem to be the problem because the tool displayed the corresponding serial number and it was a match. So there's something preventing me from unlocking the bootloader--it's probably the same reason why the fastboot says "PHONE Unlocked" even though it actually isn't. Again, I can't do the relock trick because the device wouldn't accept the Huwei unlock code.
Thoughts?
Hmm, why do some of these seem to be so picky when it comes to unlocking.. The multi too will copy what ever code you but in, sorry for the questions just trying to help narrow it down.. in the developer section there are 3 things that need to be ticked,, OEM unlocking, USB debugging and and allow ADB debugging in charge only mode.. Maybe you software got out of wack.. read here ( https://forum.xda-developers.com/mediapad-m3/help/bricked-mediapad-m3-t3746893) as it may help.. Not sure if HiSuite can restore it.
OEM unlocking and USB debugging are "working" in the sense that I can send commands from the PC via USB. It's just that I can't properly unlock the phone. I updated the drivers to see if that's the problem, but I still encounter the same error. I basically couldn't move forward with the link you sent because the first step was to unlock the device and I couldn't get past that. When I try to unlock the error is still 'FAILED (remote: password wrong)'.
I've seen some threads from other Huawei devices that suggest rolling back the firmware, but this is the first time I'm trying to root this device. And it's still on Marshmallow, which is the version that came with the first release of the Mediapad M3, so basically there's nothing to roll back to.
Why not upgrade to 7 as that is where most of the newer threads are written for plus it will redo your boot loader... giving you a clean slate to work with..and that might be your issue..
I can't update to 7 because Huawei stopped providing updates for my region. I failed to mention that the reason why I'm trying to unlock the device is to change the region and upgrade to 7.
May I ask where you are?
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
So Huawei sent me a new unlock key and it works! Problem solved!
cescpistol said:
From Southeast Asia, but the tablet was imported from China. I planned to convert it to the European version so I can at least upgrade to Nougat. I'm still stuck though.
Click to expand...
Click to collapse
Imy model also seas... Has updated to nougat without changging to us.

Problems with unlocking the bootloader

I have a problem
I want to unblock the bootloader, but when I get to put the code "fastboot oem device-id" it gives the following error "FAILED (remote: unknown command)". No matter how many times you try or the version of windows you use, you still give the same error.
In this guide you can find how to unlock bootloader if you have 2016 model, but beware root method probably don't work so just follow steps to unlock bootloader for whatever reason you want to do that
https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223

unlock moto e4 (woods)

Hello,
the device is listed on fastboot, but when I try "fastboot oem get_unlock_data"
FAILED (remote: unknown command)
I am wondering, a lot of phones are missing here at the "Bootloader Unlock program":
https://support.motorola.com/us/en/solution/MS87215
For example the Moto G2 is missing, I already unlocked this device some time ago.
Con someone explain what is wrong, others already unlocked this device. :cyclops:
Regards
Thread closed at OP request

Categories

Resources