I have a moto z3 play (beckham) and always when I boot it first shows the fastboot screen so then I can select start to boot it. Also, when I run (m)fastboot oem <command> the program just stuck with no response. I tried first oem get_unlock_data and nothing. Then tried oem fb_mode_set/fb_mode_clear and also none of these commands return anything, they just get stuck forever... What can be wrong with the device and how to fix it so I can root it? Thanks in advance.
fabiotk said:
I have a moto z3 play (beckham) and always when I boot it first shows the fastboot screen so then I can select start to boot it. Also, when I run (m)fastboot oem <command> the program just stuck with no response. I tried first oem get_unlock_data and nothing. Then tried oem fb_mode_set/fb_mode_clear and also none of these commands return anything, they just get stuck forever... What can be wrong with the device and how to fix it so I can root it? Thanks in advance.
Click to expand...
Click to collapse
Try LMSA's rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Related
Hello hopefully someone can lend me a hand. I am trying to relock my bootloader on my moto x pure edition 2014. I have downloaded the correct recovery package from Motorola directly. I issue the commands that are needed fastboot oem lock begin and then flash the firmware and then fastboot oem lock. After fastboot oem lock I get SSL error you must enter fastboot oem lock begin before lock is what is shows on the terminal windows for fastboot. On the the device screen if shows cannot validate system image although it is the correct system image. I have tried using the fastboot directly out of the Motorola software I downloaded as suggested by another user and still get the same error. I have worked on this for hours with no avail. Does anyone have any experience in this with the same problem? Thanks
Did you try following the steps listed on Motorola's website?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I believe the "fastboot oem lock begin" was only needed for older devices.
Short story: my phone bootloops (shows the Android One screen for 3 seconds, then reboots), and I cannot unlock the flash in fastboot. fastboot oem unlock fails, fastboot flashing unlock fails, fastboot flashing critical_unlock fails.
What can I do, is my phone definitely bricked?
Long story: I installed september OTA and then rooted with Magisk using the image patch method. Now I wanted to get October OTA, so uninstalled Magisk to recover the unpatched bootloader, but the OTA refused to install. So I tried the flash_all method, but it failed because I did not do the critical unlock. So I tried the fastboot flash critical_unlock, but it continuously refused to work.
So I decided to agan lock flash, and do the oem lock, to restart the unlock procedure from the beginning. But after locking, the phone does not boot anymore (and it was booting fine before!). On top of that, I cannot oem unlock anymore, fastboot oem unlock always fails.
Is there any way to recover the phone?
Try fastboot oem edl
then use mi flash
Thanks for help.
Unfortunately fastboot oem edl fails:
Code:
# fastboot oem edl
FAILED (remote: Device is already locked!)
Finished. Total time: 0.001s
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
doragasu said:
Thanks for help.
Unfortunately fastboot oem edl fails:
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
Click to expand...
Click to collapse
I'll need more info than that
what's the error you get when using oem unlock or unlock_critical?
are you using minimal adb? If so, don't, use this instead https://developer.android.com/studio/releases/platform-tools
Are you using a usb 3.0 port? Switch to a usb 2.0 if you are
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
doragasu said:
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
Click to expand...
Click to collapse
Minimal adb includes fastboot, if you have minimal adb or you installed it from the repo then it's outdated, use the one I linked
Nothing was working for me, so finally I recovered the phone by opening it and using the deep flash method.
Hello, I have a problem with a motorola moto Z3 play of 128gb, as they tell me I was updating and ran out of battery and now starts in red letters that say the following:
Your device didin't start up succesfully
if this a Verizon device, use the Software Repair Asistant on computer to repair your device.
connect your device to your computer, to get the Software Repair Assistant.
if this is not a Verizon device, or Software Repair Assistant did not help for any reason, please contact your customer care center for further asistant.
AP Fastboot Flah Mode (Secure)
SSM: abl csv roll back 0.7
Not bootable A / B slot
Failed to boot Linux, Failling back to fastboot
Fastboot reason: Fail-trough from normal boot mode
when I want to connect it to flash it, the computer does not recognize me fastboot mode, nor adb, I put the commands "fastboot devices" or "ADB devices" and obviously it does not let me do anything, someone to help me out of that state or guide me a little to revive it, please !! ...
Sorry for my bad english.
I have got a Motorola E5 plus device (Model: XT1924-3). Which restarts on logo screen (seems OS crashed).
Able to access the bootloader and recovery mode but oem is locked so can't flash new image using RSD Lite.
Have tried factory reset, wiping the user data and cache nothing works. Also, I have tried using moto smart assistant but it required debugger mode enables but unfortunately it is disabled in my case.
Could anyone help me to identify ways to unlock oem in current case or is there any other way to flash/ recover the OS.
Thanks a lot.
You can unlock the phone through recovery. You can than install twrp and flash a new rom. But did this just randomly happen or did you try and flash something? If it randomly did this than your phone may have a issue.
Smurfy76 said:
You can unlock the phone through recovery. You can than install twrp and flash a new rom. But did this just randomly happen or did you try and flash something? If it randomly did this than your phone may have a issue.
Click to expand...
Click to collapse
Hi! I'm in the same situation as OP. What's the way to unlock through recovery? I've tried adb commands to change the flashing_locked flag using "adb shell setprop ro.oem_unlock_supported 1" and "adb shell setprop ro.oem_unlock_allowed 1". The flags don't get saved after the phone boots again into fastboot.
Thanks in advance!
You unlock it through Motorola website. Plenty of guides for that here.
Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Reznor7 said:
Hello all,
I tried flashing a RR rom, and afterwards it failed to boot AND locked my device again. I have my unlock code still, but when trying to oem unlock in fastboot, I get an error: Check 'OEM unlocking' in Android Settings > Developer Options. Since the ROM won't boot, I can't check OEM unlocking. Is there any way around this? I'm afraid I've had a hard brick on my hands.
Click to expand...
Click to collapse
You can try LMSA's Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Or if you have a pc with windows 7 try
RSD Lite
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before.
Reznor7 said:
I've tried both options, but neither appears to see my device. It's in bootloader mode and shows up in Windows Device Manager as "Motorola ADB Interface".
It's showing 0xFAILED for cid. Here's my current bootloader screen.
https://ibb.co/znCSvMR
I've tried blank flash in both Linux and windows. Both just say "Waiting for device". I've never had a device brick like this before. [emoji3525]
Click to expand...
Click to collapse
Blankflash only works if device is in EDL mode.
Sent from my Moto E (4) using Tapatalk
Edit: I think my issue is that I'm needing the latest firmware (including the May 2020 security update), and I can't find it anywhere. Trying to downgrade (even with an unlocked bootloader) is giving me the preflash validation error when trying to flash bootloader.img. Looks like I need ppws29.183-29-1-19
Final edit: I had to find the latest firmware for my device. Unfortunately, only a paid site had it, but after buying and installing everything is good again!