Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)

[rotorline]

I went ahead and deleted all files in the RSA folder and unzipped the other firmware into it.
Ran the rescue function in RSA and I now have a Moto G Stylus with Android 12!

 

[Pintoslp]

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, MOTO phone, Lenovo tablet ) data, flash smart device software, and more Lenovo support functions.​

​

Note: Most Devices Released in 2014 and Newer should be compatible. - 28 July 2021​

Quick Links​

• Download LMSA
• 
  
• Using the Rescue Option -Updated 19 July 2021
• 
  
• Find downloaded firmware Post #5
• Skip data wipe Post #6
• 
  
• Where is the Update option? -Updated 1 Aug 2021
• 
  
• Troubleshooting-Post #13
  • Unable to match the appropriate firmware. Some key information cannot be read from device

Problem: Moto Phone will not update, even though you know that an update is available.​

Solution: Use the Update or Rescue option​

​

Problem: Device will not boot, or you lust want to reflash the firmware​

Solution: use the Rescue Option​

If you have a Verizon Branded Device You may need to use​

Verizon's Motorola Update/Repair Assistant​

​

also see Guide: Flashing Motorola Firmware​

Moto's description of options.

​

• Device Management: connect device via USB cable or Wi-Fi, and then manage Pictures, Videos,
  Music, Contacts, SMS, Files Management, Back/Restore;
• Flash: upgrade device system software to the newest release, and even can rescue device from software caused un-operational status;

How to use Lenovo Moto Smart Assistant

• https://support.lenovo.com/us/en/solutions/HT102605

Download/Install Smart Assistant on PC and User Guide (Win 10/7)

• https://support.lenovo.com/us/en/downloads/ds101291
• Spoiler: skip device check, just click download

  View attachment 5180771
  • Mirrors
    • Smart Assistant: https://mega.nz/#!OX4ARIQB!JT9leqmUkKjArVbQ9wC3GtbqtlPrg3tV33BC_SZXRgE
    • User Guide: https://mega.nz/#!qC4yUAYT!m7pasC7DDfGJ6vzscHeQ4oiE7v0ZUAOwsHDndwJPlIQ

Smart Assistant App
The Smart Assistant App should install automatically after you enable
USB debugging in developer options
It may take a minute
If not install the app from mirror below.


Optional (Needed for manage Pictures, Videos, Music, Contacts, SMS, Files Management)

• Download/Install Smart Assistant (Moto Device)
  Mirror
  • 1.4.1.0272 - https://www.apkmirror.com/apk/lenov...le-assistant-1-4-1-0272-android-apk-download/
    2.1.31: https://mega.nz/#!WH5whIpa!SVoGdKt0kw_FppSkPEVC066zaFpTaUYAiVWT7Na-HyQ

The PC program is not very fast,​

Be patient.​

Using Flash Rescue Option

• Skipping Data wipe using Flashing/Rescue

I cannot change fb mode set, I cannot enter in recovery and boot loader is locker. Can I recovery my phone this way?

 

[sd_shadow]

I cannot change fb mode set, I cannot enter in recovery and boot loader is locker. Can I recovery my phone this way?

In most cases, yes

 

[Pintoslp]

In most cases, yes

How?

 

[a273k]

my phone is unable to update via the rescue option, it detects the phone and downloads the firmware but when i press the rescue button the following appears:

 

[IronTechmonkey]

How?

Follow the instructions in the interface and respond to the prompts which occur during the process. As the process moves along you may have to interact with both computer and the phone at various points.

 

[IronTechmonkey]

my phone is unable to update via the rescue option, it detects the phone and downloads the firmware but when i press the rescue button the following appears:

It would help to know the details of the device as well as any modifications you may have made in the past including that time you bricked and un-brick the device and the other time when you flashedvsomething separate from the ROM (which BTW are visible when viewing your past posts. )

It's not that the modifications you may have done are necessarily the cause of the problem nor am I certain they are from the same device but absent more details, they could be a factor so it could become a waste of time for people who chase information about this on your behalf thinking it's a normal situation. Relocking a boot loader would also be in this category of potential past modifications.

As to devices which Moto supports and are in reasonably functional condition, for what this is worth setting expectations, I have successfully restored several Moto devices including some before the G8 and one from after, some of which were running stock and some of which were running LineageOS, most of which had been rooted, and all of which had unlocked boot loaders that had never been relocked.

 

[a273k]

It would help to know the details of the device as well as any modifications you may have made in the past including that time you bricked and un-brick the device and the other time when you flashedvsomething separate from the ROM (which BTW are visible when viewing your past posts. )

It's not that the modifications you may have done are necessarily the cause of the problem nor am I certain they are from the same device but absent more details, they could be a factor so it could become a waste of time for people who chase information about this on your behalf thinking it's a normal situation. Relocking a boot loader would also be in this category of potential past modifications.

As to devices which Moto supports and are in reasonably functional condition, for what this is worth setting expectations, I have successfully restored several Moto devices including some before the G8 and one from after, some of which were running stock and some of which were running LineageOS, most of which had been rooted, and all of which had unlocked boot loaders that had never been relocked.

OMG im such a fool. I'm so sorry, i've been tryiing all night to get my phone back that i didn't even realize i posted without providing any other info, I am so sorry!

My current device is a Motorola G51 5g (XT2171-1) It was purchased less than a year ago, and i was able to Root the device successfully/ I was then planning on getting another device, so I unrooted and installed the original stock firmware. I ended up keeping the device, and never rooted again. but this time, i was trying to actually change the firmware to see if it would pick up another carrier here in mexico where i live, during this process my dumb self flashed the firmware and before even checking to see if it worked locked the oem flashing by mistake. I then tried to turn the phone on and realized the firmware was apparently not the right one, as i was met with a message that says "no valid operating system could be found the device will not boot" OS Fingerprint: 0xC2224571"

and now the only thing i can do is get into fastboot mode, because it wont even boot or turn on. I have attached the text of what appears when i use the getvar all command.

 

[IronTechmonkey]

OMG im such a fool. I'm so sorry, i've been tryiing all night to get my phone back that i didn't even realize i posted without providing any other info, I am so sorry!

My current device is a Motorola G51 5g (XT2171-1) It was purchased less than a year ago, and i was able to Root the device successfully/ I was then planning on getting another device, so I unrooted and installed the original stock firmware. I ended up keeping the device, and never rooted again. but this time, i was trying to actually change the firmware to see if it would pick up another carrier here in mexico where i live, during this process my dumb self flashed the firmware and before even checking to see if it worked locked the oem flashing by mistake. I then tried to turn the phone on and realized the firmware was apparently not the right one, as i was met with a message that says "no valid operating system could be found the device will not boot" OS Fingerprint: 0xC2224571"

and now the only thing i can do is get into fastboot mode, because it wont even boot or turn on. I have attached the text of what appears when i use the getvar all command.

Those additional details are informative. First a disclaimer, I don't have the experience to interpret all the details of getvar or other flashing related logging, so I'm applying other troubleshooting experience to a logical testing framework (and perhaps someone else can provide "real" answers based on your info ).

OK, you've gone back and forth between stock and custom before (so, unlocked bootloader) then after flash of wrong version = boom, and although RSA/LMSA can see, download and attempt to install, there is the reported error. Ideas:

- Wait for someone who has actually experienced this or has the knowledge to get into deeper troubleshooting. IE maybe this can be fixed by some command that changes the region or something like that

- Check the LMSA download folder to see if all the requisite material is there and that it matches the device. It may also be helpful to compare file names and total size with what is available at https://mirrors.lolinet.com/firmware/motorola/.

- Poke around in fastboot to see if there are any odd or blank values for "modem, "base-band", etc. (this is more for potential later troubleshooting and might be in getvar)

- Try to boot to TWRP from a computer via fastboot poke around in there..

- Can any ROM be flashed or restored to the device? If yes then maybe LMSA doesn't like a region setting or partition arangement.

- If you've got access to a Windows 7 computer you might be able to try restore to stock using an older utility (RSDLite) which can flash the material from lolinet (at least up to Moto X in my experience).

 

[a273k]

Those additional details are informative. First a disclaimer, I don't have the experience to interpret all the details of getvar or other flashing related logging, so I'm applying other troubleshooting experience to a logical testing framework (and perhaps someone else can provide "real" answers based on your info ).

OK, you've gone back and forth between stock and custom before (so, unlocked bootloader) then after flash of wrong version = boom, and although RSA/LMSA can see, download and attempt to install, there is the reported error. Ideas:

- Wait for someone who has actually experienced this or has the knowledge to get into deeper troubleshooting. IE maybe this can be fixed by some command that changes the region or something like that

- Check the LMSA download folder to see if all the requisite material is there and that it matches the device. It may also be helpful to compare file names and total size with what is available at https://mirrors.lolinet.com/firmware/motorola/.

- Poke around in fastboot to see if there are any odd or blank values for "modem, "base-band", etc. (this is more for potential later troubleshooting and might be in getvar)

- Try to boot to TWRP from a computer via fastboot poke around in there..

- Can any ROM be flashed or restored to the device? If yes then maybe LMSA doesn't like a region setting or partition arangement.

- If you've got access to a Windows 7 computer you might be able to try restore to stock using an older utility (RSDLite) which can flash the material from lolinet (at least up to Moto X in my experience).

Thank you, so much for your reply, i appreciate it alot! im hoping this will get cracked or at least put to rest so im not trying to do something impossible.
I wasnt able to find a twrp that matched my device, so i tried the first twrp that i could find that seemed to work with android 12 and gave it a tried to boot but get this :

.\mfastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.898s]
booting...
(bootloader) Fastboot boot command is not available in locked device
FAILED (remote failure)


I tried to unlock the bootloader but was met with this message:

PS C:\mfastboot> ./mfastboot oem unlock
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
............

I The firmware that LMSA downloads is the same size as the one on https://mirrors.lolinet.com/firmware/motorola/. And even replacing the firmware that LMSA downloaded with the one on the website, it wont flash and give me the same message about going to a customer center.
.........
No other roms can be flashed at least the ones I've tried all from the loli website., and no windows 7 to use either :/ just my luck.

Something i did find odd was that every time i would connect to LSMA and looked at the BOOTLOADER LOGS it would constantly spit out the following commands on its own:

cmd: getvar : slot-count
cmd: getvar : all
cmd: getvar : slot-count
cmd: oem hw dualism
cmd: getvar : slot-count
cmd: getvar : dualsim
cmd: getvar : slot-count
cmd: oem hw dualism
cmd: getvar : slot-count
cmd: getvar : dualsim

when i try to run these same commands i get the following:

slot-count: 2

(bootloader) dualsim: false

and then

(bootloader) dualsim: not found
getvar:dualsim FAILED (remote failure)




then when checking online on

IMEI CHECK - Free Online IMEI Number Checker | IMEI.info

Check IMEI Number and find out hidden info. Check hardware specification, warranty or BLACKLIST status and more for FREE. Over 110 mln checked IMEI's in our database.

www.imei.info

it states that my phone is a DUAL SIM, which is not true, it is only a one sim phone from what i can tell. So it has me thinking if LSMA is looking for a dual sim when its not. But i didn't have this problem in the past using LSMA for some reason now it wont let me flash its recommended firmware.

It really has me puzzled, I haven't been able to flash,, format, or boot anything. The commands run but it just returns to "no valid operating system could be found the device will not boot" OS Fingerprint: 0xC2224571" screen. Im open to any more suggestions and in the mean time keep poking around until i find something that gives me some sign of life. I hope someone out there may be able to help.








*Edit: I tried to flash the firmware myself but wasn't able to, this is what returned:

./fastboot flash partition gpt.bin
Sending 'partition' (206 KB) OKAY [ 0.005s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed

./fastboot flash bootloader bootloader.img
Sending 'bootloader' (21676 KB) OKAY [ 0.534s]
Writing 'bootloader' (bootloader) Validating 'default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'default.xml'
FAILED (remote: '')
fastboot: error: Command failed

----------
I then decided to compare the bootloader files and it seems that the LSMA bootloader file is different than the one on the phone.

BOOTLOADER ON PHONE
(bootloader) version-bootloader: MBM-3.0-uefi-51fb89de16b-221130

BOOTLOADER ON LSMA FILE
MBM Version: MBM-3.0-uefi-ff43dd709-221130

Could this be the issue? Do i need to download each loli firmware file individually to find the matching bootloader file to be able to flash it?











*Edit 2: I stumbled upon another post, in which the user apparently has a very similar bootloader file to mine. Just wondering if this is anything i should be looking into. This is the post im speaking of:

Moto G51 - Softbrick

Hello everybody, I can't find correct subforum for Moto G51. Hope I can get some help here. I have softbricked my phone by doing two mistakes: 1) Trying to flash the software for XT2171-2 on my XT2171-3 2) Forgetting to switch on "OEM...

forum.xda-developers.com

 

[Jhon ti]

OMG im such a fool. I'm so sorry, i've been tryiing all night to get my phone back that i didn't even realize i posted without providing any other info, I am so sorry!

My current device is a Motorola G51 5g (XT2171-1) It was purchased less than a year ago, and i was able to Root the device successfully/ I was then planning on getting another device, so I unrooted and installed the original stock firmware. I ended up keeping the device, and never rooted again. but this time, i was trying to actually change the firmware to see if it would pick up another carrier here in mexico where i live, during this process my dumb self flashed the firmware and before even checking to see if it worked locked the oem flashing by mistake. I then tried to turn the phone on and realized the firmware was apparently not the right one, as i was met with a message that says "no valid operating system could be found the device will not boot" OS Fingerprint: 0xC2224571"

and now the only thing i can do is get into fastboot mode, because it wont even boot or turn on. I have attached the text of what appears when i use the getvar all command.

Telegram: @flashing_locked

 

[motog31user]

Is there any way to download specific versions of the firmware with LMSA? Perhaps a way to spoof the current version? My current installed ROM is Android 12 and I want to get the firmware for Android 11

 

[IronTechmonkey]

Is there any way to download specific versions of the firmware with LMSA? Perhaps a way to spoof the current version? My current installed ROM is Android 12 and I want to get the firmware for Android 11

The software will download the latest available firmware, (which in some cases as I've seen on one device might actually be newer than the last OTA depending on your OEM). You can also get the stock material from other places and populate the folders. I've never done that but there are some notes in this thread from people who have done that.

 

[motog31user]

The software will download the latest available firmware, (which in some cases as I've seen on one device might actually be newer than the last OTA depending on your OEM). You can also get the stock material from other places and populate the folders. I've never done that but there are some notes in this thread from people who have done that.

Thanks for the info. Would the LMSA be able to downgrade from Android 12 to 11 if I did find the right Android 11 stock rom?

 

[IronTechmonkey]

Thanks for the info. Would the LMSA be able to downgrade from Android 12 to 11 if I did find the right Android 11 stock rom?

I'm not sure. I've only used it to restore latest stock. I'm fairly sure others have tried to do it but don't recall if they've shared the result. Maybe someone posted about that, comb the thread.

 

[sd_shadow]

Thanks for the info. Would the LMSA be able to downgrade from Android 12 to 11 if I did find the right Android 11 stock rom?

Bootloader needed to be unlocked.
I don’t recommend downgrading, especially the bootloader.img

You just need to remove the new firmware folder from the LMSA folder.
Place the unzipped older folder in the LMSA folder
Then rename the older firmware folder the same as the newer firmware folder

 

[zequinhaBR]

Obrigado, muito obrigado pela sua resposta, eu aprecio muito! Estou esperando que isso seja quebrado ou pelo menos colocado para descansar, então não estou tentando fazer algo impossível.
Não consegui encontrar um twrp que correspondesse ao meu dispositivo, então tentei o primeiro twrp que encontrei que parecia funcionar com o Android 12 e tentei inicializar, mas consegui isso:

.\mfastboot inicialização twrp.img
baixando 'boot.img'...
OK [ 0,898s]
inicializando...
(carregador de inicialização) O comando de inicialização rápida não está disponível no dispositivo bloqueado
FAILED (falha remota)


Tentei desbloquear o bootloader, mas recebi esta mensagem:

PS C:\mfastboot> ./mfastboot oem unlock
...
(bootloader) Marque 'Desbloqueio OEM' em Configurações do Android > Desenvolvedor
(carregador de inicialização) Opções
FAILED (falha remota)
............

I O firmware que o LMSA baixa é do mesmo tamanho daquele em https://mirrors.lolinet.com/firmware/motorola/ . E mesmo substituindo o firmware que o LMSA baixou pelo do site, ele não pisca e me dá a mesma mensagem sobre ir a um centro de atendimento ao cliente.
.........
Nenhuma outra rom pode ser atualizada, pelo menos as que eu tentei todas no site loli., e nenhum Windows 7 para usar também :/ apenas minha sorte.

Algo que achei estranho foi que toda vez que eu me conectava ao LSMA e olhava para os BOOTLOADER LOGS, ele constantemente cuspia os seguintes comandos por conta própria:

cmd: getvar: contagem de slots
cmd: getvar: todos
cmd: getvar: contagem de slots
cmd: oem hw dualismo
cmd: getvar: contagem de slots
cmd: getvar: dualsim
cmd: getvar: contagem de slots
cmd: oem hw dualismo
cmd: getvar: contagem de slots
cmd: getvar: dualsim

quando tento executar esses mesmos comandos, recebo o seguinte:

contagem de slots: 2

(carregador de inicialização) dualsim: falso

e então

(carregador de inicialização) dualsim: não encontrado
getvar:dualsim FAILED (falha remota)




então, ao verificar online em

IMEI CHECK - Free Online IMEI Number Checker | IMEI.info

Check IMEI Number and find out hidden info. Check hardware specification, warranty or BLACKLIST status and more for FREE. Over 110 mln checked IMEI's in our database.

www.imei.info

, ele afirma que meu telefone é um DUAL SIM, o que não é verdade, é apenas um telefone sim de o que eu posso dizer. Então, isso me faz pensar se o LSMA está procurando um dual sim quando não está. Mas eu não tive esse problema no passado usando o LSMA por algum motivo, agora ele não me permite atualizar o firmware recomendado.

Isso realmente me deixou intrigado, não consegui piscar, formatar ou inicializar nada. Os comandos são executados, mas ele apenas retorna para "nenhum sistema operacional válido pode ser encontrado, o dispositivo não inicializa" Impressão digital do SO: tela 0xC2224571 ". Estou aberto a mais sugestões e, enquanto isso, continuo bisbilhotando até encontrar algo que me dê algum sinal de vida. Espero que alguém possa ajudar.








*Editar: tentei atualizar o firmware sozinho, mas não consegui, foi isso que retornou:

./partição flash de inicialização rápida gpt.bin
Enviando 'partição' (206 KB) OK [0.005s]
Escrevendo 'partição' (bootloader) Validando 'gpt.default.xml'
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) Cancelando 'gpt.default.xml'
FALHA (remoto: '')
fastboot: erro: Falha no comando

./fastboot flash bootloader bootloader.img
Enviando 'bootloader' (21676 KB) OK [0.534s]
Escrevendo 'bootloader' (bootloader) Validando 'default.xml'
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) permissão de flash negada
(bootloader) Cancelando 'default.xml'
FALHA (remoto: '')
fastboot: erro: Falha no comando

----------
Decidi então comparar os arquivos do bootloader e parece que o arquivo do bootloader LSMA é diferente daquele no telefone.

BOOTLOADER NO TELEFONE
(carregador de inicialização) versão-carregador de inicialização: MBM-3.0-uefi-51fb89de16b-221130

BOOTLOADER NO ARQUIVO LSMA
Versão MBM: MBM-3.0-uefi-ff43dd709-221130

Seria este o problema? Preciso baixar cada arquivo de firmware loli individualmente para encontrar o arquivo bootloader correspondente para poder atualizá-lo?











*Edit 2: Me deparei com outro post, no qual o usuário aparentemente tem um arquivo de bootloader muito parecido com o meu. Apenas querendo saber se isso é algo que eu deveria estar olhando. Este é o post do qual estou falando:

Moto G51 - Softbrick

Hello everybody, I can't find correct subforum for Moto G51. Hope I can get some help here. I have softbricked my phone by doing two mistakes: 1) Trying to flash the software for XT2171-2 on my XT2171-3 2) Forgetting to switch on "OEM...

forum.xda-developers.com

Same problem, putting Ward.

 

[cnsultnt]

I have the Moto G Play 2021, XT2093-7. Unlocked with the AT&T app. I wasn't getting system updates, I was stuck on Android 10 (reported no updates available). I flashed the latest version with RSA, and it went smoothly. But, Checking for Updates now fails. Is it because I am up to date? Could it be some ATT apps I disabled?
If I go to RETUS version, will I get future updates? I there a howto for change carrier version? I haven't unlocked the bootloader or rooted.

 

[Brizu.pa]

I went ahead and deleted all files in the RSA folder and unzipped the other firmware into it.
Ran the rescue function in RSA and I now have a Moto G Stylus with Android 12!

Hey, was your bootloader unlocked or not? i want to do the same but my phone's never been touched before.

 

[Brizu.pa]

Bootloader needed to be unlocked.
I don’t recommend downgrading, especially the bootloader.img

You just need to remove the new firmware folder from the LMSA folder.
Place the unzipped older folder in the LMSA folder
Then rename the older firmware folder the same as the newer firmware folder

Sorry to bother you, I just saw you clearly know how to use this tool.

Can i UPGRADE from a12 to a13 by just replacing the A12 RSA downloaded with A13 firmware from lolinet WITHOUT UNLOCKING BOOTLOADER? thanks in advance man