Database Users

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

Can not unlock bootloader 21s (oem unlock is not allowed)

I have followed the guides to the best of my ablity
This is the procedure I followed: From this thread
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
FAILED (remote: oem unlock is not allowed)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.100s]
finished. total time: 0.100s
I then tried to downgrade to s19, but does not seem to work.
Anyway, if anyone has any ideas it would be welcomed, thank you

Is there an option you can turn on in dev options called "allow bootloader unlocks"? Because my mom's Le 2 has it and I assume it allows the unlock to go through. Are you on a vendor ROM? Flash the original stock Chinese 18s for your device.

Closest setting like that I have is the "OEM unlock" and I have it enabled

Well, did you have it enabled back when you were trying to unlock it? Because not having it enabled is usually what causes the unlock to fail.

Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.

slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
I will try this asap, thanks

Woot! that worked
Hey can i lock the bootloaded after I am done? I want to use like android pay and stuff
Well I figured out I can relock it, bit now my issue is when I am in fastboot mode adb does not see the device...
I installed the drivers, did not work....
Even went to my wife's laptop that I have never once plugged my phone in to... Installed adb, and plugged in the phone in fastboot... Still not being seen when I do an "adb devices"
I really want to use android pay

Don't understand
slgooding said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
Code:
fastboot flash aboot emmc_appsboot.mbn
You may need to do the XBL as well:
Code:
fastboot flash xbl xbl.elf
Then
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
Click to expand...
Click to collapse
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.

bobster82 said:
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure ur files are in the right directory or cd to where they are.

bobster82 said:
Simple fix. You need to manually flash the emmc_appsboot.mbn from fastboot. You can get the file you need in the zip here: https://www.androidfilehost.com/?fid=313042859668275431
You may need to do the XBL as well:
Then
Run
and then
Hi I know this is a older thread but I cannot get past the oem unlock is not allowed on my pro 3. I have all the drivers installed and the cmd recognizes my device but when I try to unlock I get the error. I downloaded the files you provided and when I try to insert from fastboot on command prompt it says the files is not recognized as internal or external command. I don't know what else to do at this point. Any help would be appreciated.
Click to expand...
Click to collapse
You need adb installed on your computer.

You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.

thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?

bobster82 said:
thanks everyone. I tried everything suggested and nothing worked. I switched to my wifes computer witht he same files and seemed tp brick the pro 3. How in the world did I do this through adb?
Click to expand...
Click to collapse
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium

mchlbenner said:
Do you have fastboot yet if not you will have to try to unbrick it.
Which model do you have?
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727

bobster82 said:
I dontI don't its bricked bricked. When I plug it in it comes up as hus9009 ..I have the US model 727
Click to expand...
Click to collapse
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium

mchlbenner said:
Power of push power down and volume down when you are plugged in to your PC.
Make sure you adb installed on your computer.
What did you flash on your phone.
Sent from my LEX720 using xda premium
Click to expand...
Click to collapse
see this the only thing I don't understand. I booted into fastboot and attempted to flash the files eemc and the xl files to unlock bootloader. The first try gave me an error and then the screen went black and has not come back on yet. No vibrations,no lights, no nothing.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
sk8223 said:
You don't need adb installed, you just need platform-tools. https://www.xda-developers.com/install-adb-windows-macos-linux/
You usually have to preface every command with adb shell. So after enabling USB Debugging and connecting to your device (make sure to allow your PC on your phone when the prompt comes up), type adb shell fastboot flash aboot emmc_appsboot.mbn in the terminal.
Click to expand...
Click to collapse
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?

bobster82 said:
I had all the files you listed and followed to a T and for some reason it bricked my device. Any idea how to resurrect it?
Click to expand...
Click to collapse
Well, I simply rephrased slgooding's post in this thread. See the first page. And by brick, I assume you only have fastboot working.
Try the other commands: https://forum.xda-developers.com/showpost.php?p=74123111&postcount=5

hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?

bobster82 said:
hey I got it unbricked by using the flash 2.0 method. The only thing is now its reading 720 instead of 727. Also When I get into FASTBOOT it says the bootloader is already unlocked but when I try put twrp recovery into the command prompts its telling me the image file is corrupt. What am I doing wrong with this adb command?
Click to expand...
Click to collapse
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium

mchlbenner said:
Make sure you have correct image recovery for your device.
Redo due unlocking commands you may have flash a bootloader on it.
What build are you on
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Hi I made sure I downloaded the correct twrp recovery and when I command in prompt its telling me now that it cannot load the image error. the build is Le_zl1 -eng 6.0.1 WAXCNFN5841510281D eng.letv.
I'm almost fixing to give up cause no matter what I do I cannot get into twrp recovery

Seems like I bricked my g6 plus...

Hi,
I tried flashing a stock rom of android 9 to my device today and at some point I just couldn't leave fastboot moad anymore. after that I tried using the rescue options on the Lenovo device manager program, but ufortunately It caused even more problems since the device couldn't would just start and at some point say that the device is not to be trusted and that I should try unkocking it. After that I did try unlocking the device but it seems that since I'm not able to access the os itself and enable OEM unlock I can't unlock the bootloader. now the device is just stuck on the fastboot mode withouth being able to do much. I tried reading about how to unbrick but that doesn't seem to be doing anything (the unbrick bat file doesn't detect the device). I feel really confused and frustrated since I have no idea whatsoever on how to continue. Do you guys have any suggestions?
Thanks!

It sounds stupid but there's a great difference between fastboot and mfastboot especially when flashing stock roms on locked devices!
Try to flash the firmware with mfastboot and make sure you have signed firmware files.
Find the download for mfastboot below.
You only have to change the syntax like this:
Instead of
fastboot flash partition ...
type
mfastboot flash partition ...

WoKoschekk said:
It sounds stupid but there's a great difference between fastboot and mfastboot especially when flashing stock roms on locked devices!
Try to flash the firmware with mfastboot and make sure you have signed firmware files.
Find the download for mfastboot below.
You only have to change the syntax like this:
Instead of
fastboot flash partition ...
type
mfastboot flash partition ...
Click to expand...
Click to collapse
Could you explain what you mean by signed firmware files? my phone is an XT1926-7 so I downloaded the latest version of the retail stock rom for that, is that ok?
Thanks a lot!

"Signed" means nothing more than untouched firmware images by Motorola.
https://mirrors.lolinet.com/firmware/moto/evert/official/RETLA/XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the latest release for your device. Try it together with mfastboot.
Good luck!!

WoKoschekk said:
"Signed" means nothing more than untouched firmware images by Motorola.
This is the latest release for your device. Try it together with mfastboot.
Good luck!!
Click to expand...
Click to collapse
Hey,
just tried it, but when I get to the "mfastboot flash boot boot.img" the cdm tells me: "Preflash validation failed" and "Failed (remote failure). later on I get a warning:
(bootloader) WARNING: OEM images are required in the LOCKED state.
(bootloader) Flashing images can result in a non-boot condition.
(bootloader) Flash a proper OEM signed boot.img first.
what should I do?
Thanks a lot!

You flashed the firmware provided by the link, right?
Enter fastboot mode and type:
Code:
fastboot getvar ro.carrier
Code:
fastboot getvar ro.build.fingerprint
Post the results of these two commands, please.
Edit: It seems the firmware isn't the right one for your device because it is signed. So that is not the problem...
In order to find the right one I need to know the command's results.

WoKoschekk said:
You flashed the firmware provided by the link, right?
Enter fastboot mode and type:
Code:
fastboot getvar ro.carrier
Code:
fastboot getvar ro.build.fingerprint
Post the results of these two commands, please.
Click to expand...
Click to collapse
I did flash the firmware from the link. I ran the commands and this is what I got:
Code:
fastboot getvar ro.carrier
ro.carrier: retla
Code:
fastboot getvar ro.build.fingerprint
(bootloader) ro.build.fingerprint[0]: motorola/evert_n/evert_n:9/PPWS29.
(bootloader) ro.build.fingerprint[1]: 116-11-8/fa378:user/release-keys
ro.build.fingerprint: Done

The firmware on your device is 116-11-8 but the link only provides 116-11-6. I think that's the reason why flashing failed... Your're on a newer build.
Is it possible for you to boot up in TWRP?
Code:
fastboot boot /path/to/twrp.img

WoKoschekk said:
The firmware on your device is 116-11-8 but the link only provides 116-11-6. I think that's the reason why flashing failed... Your're on a newer build.
Is it possible for you to boot up in TWRP?
Code:
fastboot boot /path/to/twrp.img
Click to expand...
Click to collapse
I tried it just now but It says:
(bootloader) permission denied!
FAILED (remote failure)
Unofrtunately I have't unlocked the bootloader and I can't seem to be able to unlock it without the phone actually booting up as it should :|
Any idea on how to go on from here?

You need the latest firmware 116-11-8. Did you try the RSD-Lite tool? It's a firmware download and flashing tool. Maybe you'll be able to download the right firmware with this tool...

WoKoschekk said:
You need the latest firmware 116-11-8. Did you try the RSD-Lite tool? It's a firmware download and flashing tool. Maybe you'll be able to download the right firmware with this tool...
Click to expand...
Click to collapse
I managed to find the right firmware and flashed and everything worked!
Straight after I went and unlocked the bootloader to make sure I don't get stuck like this again.
Thanks a lot for your help!

I'm glad to hear that! Did you find it with RSD lite?

WoKoschekk said:
I'm glad to hear that! Did you find it with RSD lite?
Click to expand...
Click to collapse
I couldn't figure out how to look for roms on RSD so I had another look at Lolinet and then I suddenly saw it there under retail roms. I couldn't see it there before but maybe I just missed it somehow.

The page was updated two days ago. That was lucky! But it's recommended to flash the right firmware. These Retail versions are a kind of universal solution...

Help !! please my phone crash and now fastboot appears

well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please

Frost817 said:
well hello everyone.
motorola G5 plus XT1681
in recent days my phone failed while charging and the legend appeared to me
start up failed
your device didnt start up successfully
use the software repair assistant on computer to repair your device
connect your device to your computer to get the software repair assistant.
ap fastboot flash mode (secure)
failed to pass validation .... ... etc
I already tried to use the motorola software and it did not work, use tools like mfastboot, adb tools, to be able to repair it and nothing works only it sends me errors that it cannot or is blocked
:crying:
on the fastboot screen appeared
AP Fastboot Flash Mode (secure)
BL: C0.92(*) (sha-3ea8df0, 2018- 07-30 18:29:10)
baseband:
product/variant: potter 000000000000000 32gb p3b
serial number: 9cc....063
cpu: msm853
eMMC: 32GB SAMSUNG QX1 3MB RV=08 PV=07 FV=00000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=1F
CONSOLE NULL : null
tools mode config: disabled
battery ok
oem_locked
transfer mode: usb
the other menus
start in green letters, switch tools mode in white letters, restart bootloader in red letters, recovery mode in red letters, factory also in red barcodes in white, bp tools in red letters just like Qcon
the oem was not unlocked when the phone worked normally so
They told me that I had to unlock the oem somehow, I tried it with a program called mfastboot but it didn't work
only this appeared:
C:\mfastboot>mfastboot oem get_unlock_data
...
(bootloader) Unlock data:
(bootloader) read datablock error
(bootloader) Failed
OKAY [ 0.003s]
finished. total time: 0.006s
I do not know what to do, apart I am a novice in this does not seem very complicated but I already get stuck in the process and I do not know what else to do I hope someone can help me please
Click to expand...
Click to collapse
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
Did you turn on OEM unlocking in Dev options before device failed to boot?
If not you cannot unlock the bootloader.
Did you use LMSA'S Flash Rescue option?
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
If that falls your only option is RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me

Frost817 said:
I didn't activate it before the device failed, so I guess from your answer I can't unlock it
the rescue tool uses it but it jumps the message of "error when combining files" and if I give the button to read my device then it still gives me an error and tells me that the device is not supported
I will try to use the other tool that you tell me
Click to expand...
Click to collapse
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
I suggest you to use this method to flash stock ROM.
https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
and use the latest firmware for your country.
https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I tried the method but just send me this
[LEFT]commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]

Frost817 said:
I tried the method but just send me this
[LEFT]commands:
update reflash device from update.zip
flashall flash boot + recovery + system
flash [ ] write a file to a flash partition
erase erase a flash partition
format format a flash partition
getvar display a bootloader variable
boot [ ] download and boot kernel
flash:raw boot [ ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s specify device serial number
or path to device port
-l with "devices", lists device paths
-p specify product name
-c override kernel commandline
-i specify a custom USB vendor id
-b specify a custom kernel base address. default: 0x10000000
-n specify the nand page size. default: 2048
-S [K|M|G] automatically sparse files greater than
size. 0 to disable[/LEFT]
Click to expand...
Click to collapse
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
That just means you used wrong command, but fastboot.exe rarely works with locked Motorola bootloader anymore
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?

Frost817 said:
mmm I see, that you told try with RSD Lite but the device does not detect me, install the motorola drivers and everything but nothing.
check the windows device manager and it came out as unknown device and restarted the pc again after it appeared
android device
motorola adb interface
I returned to the RSD Lite and still nothing appeared in the box where the device information should appear and in the command prompt if the serial number appears
I use a Windows 10 PC, does that influence or have I skipped a step?
Click to expand...
Click to collapse
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs

sd_shadow said:
RSD Lite doesn't work with Windows 10
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result

Frost817 said:
ok well i changed my pc and i used the RSD Lite again, and this time if the device recognizes me and everything
only that the information of the device appears as N / A in the window and in the list when I run the file of the firmware it sends me
Failed flashing process. 2/22 oem fb_mode_set -> Phone returned fail
while on the phone screen it says
Bootloader logs
cmd: getvar:max-sparce-size
cmd: oem fb_mode_set
I already tried several compatible firmware and all give me the same result
Click to expand...
Click to collapse
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs

sd_shadow said:
Try
Unzip the .zip
Select flashfile.xml using RSD lite
It doesn't use the fb_mode_set
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
well don't use the fb_mode_set but it keeps sending me Failure
failed flashing process 1/24 flash partition gpt.bin -> phone returned Fail
bootloader logs:
cmd: getvar- max sparce size
cmd: getvar- max download size
cmd: download 0000b600
cmd: flash: partition

after seeing your post I also believe my phone moto g5 XT1686 failed not able to start, the same issue I tried everything all tools and commands. In a final conclusion Buying Motorola devices is a waste of money.
feeling dishearted...

[MI A1] [locked] [bricked][EDL] flash

Dear mates,
2 days I am trying to find answer to my problem and finally decided to start new post on exact issue I faced.
device is MI A1 with android one and current version on it was according to picture attached from recovery was tissot_10.0.19. when I took this phone from my mate to fix it was not booting with first MIUI page stacked on the screen.
fastboot output were saying:
--------------------------------------------------
C:\WINDOWS\system32>fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.058s]
Finished. Total time: 0.059s
------------------------------------------------
getvar is attached
i tried to flash using miflash ver 2020.3.14 in fastboot mode but it was not successful because of locked bootloader and "locked everything".
i tried to load OTA updates using embedded recovery, but not successful, screenshot attached.
i got the error " E:Error in sideload/package.zip (Status 1)
and all time repeating error : fail to clear BCB message fail to fsync /dev/block/bootdevice/by-name/misc: operation not permitted
any option from recovery meny does not provide any result. wipe data/factory reset were stucking with erasing data notification for hours without result.
at the end i cam to EDL mode by shorting hardware test point. quallcomm driver was ok at computer Device Manager, miflash and QFIL are identifying device on com port 20 but flashing does not finish successfully , it stop at 12 sec in Miflash, and at 1,46% in QFIL. verbose log for QFIL is also attached .
main concern in QFIL log file is "IGNORING UNRECOGNIZED Attribute" stats for attributes from TARGET. my impression is phone is asking to send data in rawmode <?xml version="1.0" encoding="UTF-8" ?><data><response value="ACK" rawmode="true" /></data> and Qfil is ignoring this attribute. as the result file copy finish with error
23:37:45: INFO: TARGET SAID: 'Finished sector address 131072'
23:37:45: DEBUG: XML FILE (92 bytes): CharsInBuffer=92-92=0
-------------------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?><data><response value="NAK" rawmode="false" /></data>
and we have repeating replies from Target as this : <?xml version="1.0" encoding="UTF-8" ?><data><log value="0 bytes received, 1048576 sectors more to go" /></data>
sorry for long explanation, the goal is to share as clear picture of the situation as possible.
i tried the same procedure with QFIL on other computer and had the same result.
now phone is in all time EDL mode. i suppose it is because i checked "erase all before configuration" option in QFIL firehose configurations.
Thanks to everyone in advance for your time and help if you could provide your suggestions how to solve the issue.

I can't solve this problem for more than 4 days and I have android 8.1 and it gives the same problem, you can do the easiest thing, as they say, edl test point, you can try but I don't recommend how you can mess up something if you were able to solve the problem, please tell me how to solve it

Try to flash stock rom via MiFlash Tool. Make sure to see COM port on MiFlash tool (press refresh to detect com port). Then after you see COM port. Flash it with "clean all" option(on the bottom). If you connect to EDL mode properly, process will be finished succesfully. But if you get some "Invalid argument, unknown error" errors, you are not connected to edl mode.
try to enter edl mode with this code in fastboot
Code:
fastboot oem edl
If it give OKAY, then you are ready to flash with Miflash tool.
There is another way to flash img files with fastboot mode. If you dont success, write here.

atc mode is not worked and I don't want to enter the testpoint, how can I tell you and the loader is not open, so this is also not a small problem as you look at it, so if there are other ideas, please send them to me
PLEASEEEEE

Testpoint is a final way. even if you cant enter testpoint, you cant do more

ivomin said:
It's ALIVE!.
Just to update that after debugging the whole windows com stack I struck on a wall and it seems that windows 7 and 10 block something there (I manage to get out of the driver to win kernel on debug but then it fails and didn't had any more nerves to deal with and I'm not a windows guy myself).
So the only solution for low lvl writing is to use linux with point boot to EDL. It seems that for mi A1 even if Qualcomm's boot chain is broken (https://blog.quarkslab.com/analysis-of-qualcomm-secure-boot-chains.html) it should fall to EDL in most cases but in our phone (global version at least) it goes to diagnostic mode (not to be confused with Download mode) regardless of drivers in windows - this is hardwired in the chip. So under linux you should fall in to download mode with hardware short of motherboard points to fall in to the correct mode. You should forget about windows as it depends too much on the selected driver (yes you can manually change driver and fu** the whole chain of communication). You need to hardwarely go to Download mode. Don't believe what windows reports.
From there you can use QDL (check documentation on how to install (you'll also need to install gcc (ubuntu - apt get install gcc) https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md).
Then download a full firmware flash from xiaomi (that's for MiFlash) and use the files in the images folder for the command ( for instance to be more easy copy images folder to qdl folder and:
./qdl --debug --storage emmc --include 'images' 'images/prog_emmc_firehose_8953_ddr.mbn' 'images/rawprogram0.xml' 'images/patch0.xml')
This will fix the first part of the qualcomm bootchain from there you will have access to fastboot and then use all other tutorials concerning fixes from fastboot.
If enough ppl want it I'll write extended tutorial in the other section.
Click to expand...
Click to collapse
Try this. It should bring you to mostly original state and from there you can fastboot unlock and proceed with installing shrp or twrp.