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

[sd_shadow]

I did an RSA and it successfully flashed the latest firmware for my Motorola G Power 2021. But I'm still having "Invalid SIM card" issues. I bought this phone unlocked on ebay. And initially it works with my Tello SIM, but after Android June security update, it seems something trigger it to relock (my guess). I'm seeing "Boost" in the carrier part in RSA (pic). I'm also noticing a My Boost app on the phone even after the RSA rescue flashed.

Can anyone with a Motorola G Power 2021 Unlocked confirm what should the carrier part say?

I’m guessing that someone carrier unlocked it using unofficial methods, and the update flashed over those changes.
No fixing that unless you have the special tools need the change those settings again.

 

[IronTechmonkey]

I did an RSA and it successfully flashed the latest firmware for my Motorola G Power 2021. But I'm still having "Invalid SIM card" issues. I bought this phone unlocked on ebay. And initially it works with my Tello SIM, but after Android June security update, it seems something trigger it to relock (my guess). I'm seeing "Boost" in the carrier part in RSA (pic). I'm also noticing a My Boost app on the phone even after the RSA rescue flashed.

Can anyone with a Motorola G Power 2021 Unlocked confirm what should the carrier part say?

I’m guessing that someone carrier unlocked it using unofficial methods, and the update flashed over those changes.
No fixing that unless you have the special tools need the change those settings again.

To the previously made point about carrier unlock: My Moto G Power 2021 which was purchased officially, new and carrier unlocked (and which still has bootoader locked and is receiving updates OTA) reports no carrier in LMSA/RSA with or without SIM (t-mobile US prepaid). Similarly, a Moto G Power 2020 and Moto G7 Power of similar origins (officially carrier unlocked at point of sale) and with same SIMs reports no carrier in LMSA/RSA.

 

[Teiji]

To the previously made point about carrier unlock: My Moto G Power 2021 which was purchased officially, new and carrier unlocked (and which still has bootoader locked and is receiving updates OTA) reports no carrier in LMSA/RSA with or without SIM (t-mobile US prepaid). Similarly, a Moto G Power 2020 and Moto G7 Power of similar origins (officially carrier unlocked at point of sale) and with same SIMs reports no carrier in LMSA/RSA.

Thank you for the confirmation. Can you please share an image of the Motorola G Power 2021 on the Rescue screen of RSA (with IMEI and SERIAL censored of course). I'm trying to gather proofs for a Paypal case against the seller.

 

[IronTechmonkey]

Thank you for the confirmation. Can you please share an image of the Motorola G Power 2021 on the Rescue screen of RSA (with IMEI and SERIAL censored of course). I'm trying to gather proofs for a Paypal case against the seller.

I don't think a screenshot from me is worth much to supporting your case since it represents a ubiquitous default - that for an officially carrier unlocked phone there should be no provider listed. On the other hand, the screenshot of your device on which the anomaly is represented is significant because it shows that a device which claims to be carrier unlocked still has an association with a carrier. That along with the other details you provided seem like enough to prove your case. Good luck.

If you don't get anywhere with the seller, there are ways to install older stock versions or custom roms which might, or might not, work around the issue.

 

[Teiji]

I lost. Paypal said cause I already used the phone fine (before it got lock). Don't wanna go into too much details because it's all in the past now and stressing me out.

I guess I can buy a Boost SIM and see if it works. Then sell it as a locked Boost phone at a lost. Or any other suggestions?

 

[G.S.T]

I have a lenovo tab m8 3rd gen (TB-8506F) MTK. The device is unlocked and magisk rooted. When i try to apply a system update using instructions from magisk website, its showing ota failed.
Tried with complete magisk uninstallation and still system update is failing.
Updating manually using normal SP flash tool seems to not work when flashing due to some authentication error. The Flash tool zip that's downloaded by LMSA is password protected.
I don't want to erase userdata when doing rescue with LMSA. Any solutions?

 

[amansas]

Hello. I had a rooted Lenovo Tab M10 where I deleted some system apps without knowing their function. I'll be more careful, I promise. Tab is stuck in a bootloop. Logo flashes and device shuts off, then repeat. It doesn't respond to any hardware buttons. I plugged it into my Computer and ran RSA. The rescue got upto 68% before Fail message pops up. Everytime, the QCom port is detected and flashing is in progress, before it fails for some reason.

Help, please. I have the log files of RSA, but they're encrypted so I don't know how to study them.

 

[torresfernando9]

bt20

See my reply here.
https://forum.xda-developers.com/showpost.php?p=82114979&postcount=4

Sent from my ali using XDA Labs

me explicas como lo solucionaste no me toma en bank flash

Mod translation: explain to me how you solved it does not take me in bank flash

 

[sd_shadow]

bt20

me explicas como lo solucionaste no me toma en bank flash

Mod translation: explain to me how you solved it does not take me in bank flash

What does getvar all say? remove imei before posting.

fastboot getvar all

 

[Sadako8888]

I installed Lineage to my Moto Z Play, but due to compatibility problems with apps, I went back to the stock Rom through Rescue and Smart Assistant and the phone lasted 1 day and then it bricked.
Rescue and Smart Assistant sometimes recognizes the phone when I plug it in via USB and tries to recover it, but when the process is finished, nothing happens. Any advice to solve it? Thank you

 

[jay2the1]

Does anyone else have trouble installing the RSA tool? When I double click the exe to install the standard 'Windows security popup' shows which I click "yes" to and then nothing happens no matter how long I wait and nothing in Task Manager

Are there any quirks that this program needs such as a specific C++ Redistributable or .NET version or something?
Last time (late 2021) I tried to install RSA the same thing happened but I've reinstalled the operating system since then so this is essentially a clean Windows install it's failing to install on

Any help would be much appreciated

Update: I've just extracted the Rescue_and_Smart_Assistant_v6.3.2.12_setup.exe to a folder using 7-zip and manually launching the Rescue and Smart Assistant.exe does now launch and open, I assume there would be no issues using the program in this way as a portable application and not "installing" it?

Update 2: It worked using it from an extracted folder, however at first it would detect the phone while turned on but not while it was in Fastboot, I had to install the Motorola_Mobile_Drivers_64bit from Motorola and then it fully worked and Rescued successfully, the process was quick and easy once I had the right drivers

The phone was a Motorola One Action

 

[IronTechmonkey]

Does anyone else have trouble installing the RSA tool? When I double click the exe to install the standard 'Windows security popup' shows which I click "yes" to and then nothing happens no matter how long I wait and nothing in Task Manager

Are there any quirks that this program needs such as a specific C++ Redistributable or .NET version or something?
Last time (late 2021) I tried to install RSA the same thing happened but I've reinstalled the operating system since then so this is essentially a clean Windows install it's failing to install on

Any help would be much appreciated

Update: I've just extracted the Rescue_and_Smart_Assistant_v6.3.2.12_setup.exe to a folder using 7-zip and manually launching the Rescue and Smart Assistant.exe does now launch and open, I assume there would be no issues using the program in this way as a portable application and not "installing" it?

Update 2: It worked using it from an extracted folder, however at first it would detect the phone while turned on but not while it was in Fastboot, I had to install the Motorola_Mobile_Drivers_64bit from Motorola and then it fully worked and Rescued successfully, the process was quick and easy once I had the right drivers

The phone was a Motorola One Action

Thanks for doubling back to share the details of your experience. FWIW, IMO the RSA app is poorly designed regarding a consistent user experience even though it is effective when configured. It requires Internet connection at various points which the user may not know and quickly forgets the login and requires program updates. Unless frequently used, any time you return to use it there may such hiccups with updates and log-ins. That being said, this does not seem to have been the issue in your case which seems to have been the fastboot drivers. On that point I had a similar experience with a Moto X4 (Payton). I could not access that device via fastboot and there was an odd value in one of the descriptions of base-band or modem. RSA was able to see the device but not work with it... until I updated Moto drivers. I did not have such problems with other devices in fastboot or RSA but that X4 was the first A/B device on which I flashed a custom ROM and I probably messed something up, hence the need to restore it which to your point went smoothly once everything was lined up.

 

[Isbra]

Hi everyone! Sticking to RSA topic, I needed to flash stock my XT2113-3 because of a bootloop and everything worked fine, but when the phone reboots it is still stuck on bootloop. What could it be? I also tried fastboot but maybe it's not the right thread to talk about that.

getvar here, maybe it helps.

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) product: kiev
(bootloader) board: kiev
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=16777216
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 10
(bootloader) cpu: SM_BITRA_H 1.0
(bootloader) serialno: ZY22BFMSHS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F316FBCC
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-24-2020
(bootloader) sku: XT2113-3
(bootloader) carrier_sku: XT2113-3
(bootloader) battid: SB18C85232
(bootloader) battery-voltage: 4062
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: timit
(bootloader) ro.build.fingerprint[0]: motorola/kiev_retaile/kiev:11/RZKS
(bootloader) ro.build.fingerprint[1]: 31.Q3-25-15-11/feee1:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-11500-SMxx50.0
(bootloader) version-baseband[0]: M7225_HI251_22.578.01.39R KIEV_ROWDSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue N
(bootloader) kernel.version[4]: ov 15 13:30:36 CST 2022
(bootloader) git:xbl: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:xbl_config: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:abl: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) git:aop: MBM-3.0-kiev_retail-f135681-221115
(bootloader) git:tz: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:hyp: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:devcfg: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:keymaster: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:storsec: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:uefisecapp: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) gitrov: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:qupfw: MBM-3.0-kiev_retail-7a60101-221115
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 2
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86666
(bootloader) primary-display: tm_ft8756_666_1080x2300_vid
(bootloader) secondary-display:
all: listed above

 

[XceS01]

Got a problem, my Lenovo Tab 2 A10-30 (Tab2-X30F) is dead, and the rescue Apps aren't working.
A) Had malware, loaded Stock Rom using QFIL
Tried to update to a LineageOS with a newer Android version
Accidentally marked to wipe the system, so no longer have an OS.
Booted into TWRP, opened terminal and executed "REBOOT EDL"
Tried to push another Stock Rom with QFIL, but this resulted in Errors.
Then tried moving on to the Lenovo Rescue App.
B) The Lenovo "Rescue and Smart Assistant" asks for a serial number, and then just poops out an error "Device not Supported"
C) Attempting older versions of the software, like "Lenovo_Moto_Smart_Assistant_v4.5.0.14" force an update to "Rescue and Smart Assistant"
This older App might work, but it instantly pops up a windows "Update to new Version", if you cancel the app closes (aka this app is now worthless because it FORCES to update to newer software that doesn't work)

So, the device was stuck in EDL mode last night, just black screen, but QFIL found the port but failed to push Stock Rom.
This morning tried to continue to salvage the device, assuming it is still in EDL mode, however:
- Just black screen
- Holding the Power Butten +20secs no longer does anything
- It should be fully charged
- QFIL no longer detects it

So I have a dead device that is unresponsive and Rescue software that doesn't want to support it.
Can anyone provide some Help ?

Update: I did once boot it with VolumeDown+Power, and it booted into some Chinese menu.
The "Rescue and Smart Assistant" does have a note on the bottom of the Serial Entry window stating "Tablets sold in Chinese mainland is not supported currently". Still doesn't excuse older software to forcibly update.
Perhaps this is a device that was made for China, loaded with an english OS en sold in the UK ? Just guessing.
It was bought in the UK though. All text on it is in english.

Another Update, after Re-plugging the device cable for the 17th time, it suddenly popped up again in QFIL [!?] (So it is still in EDS mode, but won't reboot or do anything)
Tried another Stock Rom push (exactly the same as I tried 3 times yesterday, before heading to bed), and this time it didn't error and successfully pushed the Stock Rom ! Rebooted into OS, no longer dead. (What the .. ? Consistency -5)

Final Update: I got the Stock Rom loaded using QFIL, but am unable to use Google Play store, due to a problem with Google Services. This is probably because I am unable to load the GApps after Installation.
The TWRP privided does not seem to work properly for the "Tab2-X30F", It cannot access/edit any of the folders. I tried a "Fix Permissions", but literally anything i try on TWRP just errors. It doesn't seem to be able to access or modify the internal memory or the SD Card. All guides for this device seem to provide the same recovery.img, all are the same TWRP, all experience the same issues: Any action errors out into lack of file access

 

[sd_shadow]

Hi everyone! Sticking to RSA topic, I needed to flash stock my XT2113-3 because of a bootloop and everything worked fine, but when the phone reboots it is still stuck on bootloop. What could it be? I also tried fastboot but maybe it's not the right thread to talk about that.

getvar here, maybe it helps.

(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) product: kiev
(bootloader) board: kiev
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: ROW
(bootloader) storage-type: UFS
(bootloader) emmc: N/A
(bootloader) ufs: 128GB SAMSUNG KM2V8001CM-B707 FV=1500 WB=16777216
(bootloader) ram: 6GB SAMSUNG LP4x DIE=16Gb M5-M8=01 07 01 10
(bootloader) cpu: SM_BITRA_H 1.0
(bootloader) serialno: ZY22BFMSHS
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: F316FBCC
(bootloader) token: inactive
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805306368
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 11-24-2020
(bootloader) sku: XT2113-3
(bootloader) carrier_sku: XT2113-3
(bootloader) battid: SB18C85232
(bootloader) battery-voltage: 4062
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: timit
(bootloader) ro.build.fingerprint[0]: motorola/kiev_retaile/kiev:11/RZKS
(bootloader) ro.build.fingerprint[1]: 31.Q3-25-15-11/feee1:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-11500-SMxx50.0
(bootloader) version-baseband[0]: M7225_HI251_22.578.01.39R KIEV_ROWDSDS
(bootloader) version-baseband[1]: _CUST
(bootloader) kernel.version[0]: Linux version 4.19.157-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Tue N
(bootloader) kernel.version[4]: ov 15 13:30:36 CST 2022
(bootloader) git:xbl: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:xbl_config: MBM-3.0-kiev_retail-93822280-221115
(bootloader) git:abl: MBM-3.0-kiev_retail-45a34bc590e-221115
(bootloader) git:aop: MBM-3.0-kiev_retail-f135681-221115
(bootloader) git:tz: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:hyp: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:devcfg: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:keymaster: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:storsec: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) git:uefisecapp: MBM-3.0-kiev_retail-775ecfe-221115
(bootloader) gitrov: MBM-3.0-kiev_retail-167e1fef-221115
(bootloader) git:qupfw: MBM-3.0-kiev_retail-7a60101-221115
(bootloader) frp-state: no protection (77)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 7
(bootloader) slot-retry-count:_b: 2
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C86666
(bootloader) primary-display: tm_ft8756_666_1080x2300_vid
(bootloader) secondary-display:
all: listed above

• Troubleshooting

 

[sd_shadow]

Got a problem, my Lenovo Tab 2 A10-30 (Tab2-X30F) is dead, and the rescue Apps aren't working.
A) Had malware, loaded Stock Rom using QFIL
Tried to update to a LineageOS with a newer Android version
Accidentally marked to wipe the system, so no longer have an OS.
Booted into TWRP, opened terminal and executed "REBOOT EDL"
Tried to push another Stock Rom with QFIL, but this resulted in Errors.
Then tried moving on to the Lenovo Rescue App.
B) The Lenovo "Rescue and Smart Assistant" asks for a serial number, and then just poops out an error "Device not Supported"
C) Attempting older versions of the software, like "Lenovo_Moto_Smart_Assistant_v4.5.0.14" force an update to "Rescue and Smart Assistant"
This older App might work, but it instantly pops up a windows "Update to new Version", if you cancel the app closes (aka this app is now worthless because it FORCES to update to newer software that doesn't work)

So, the device was stuck in EDL mode last night, just black screen, but QFIL found the port but failed to push Stock Rom.
This morning tried to continue to salvage the device, assuming it is still in EDL mode, however:
- Just black screen
- Holding the Power Butten +20secs no longer does anything
- It should be fully charged
- QFIL no longer detects it

So I have a dead device that is unresponsive and Rescue software that doesn't want to support it.
Can anyone provide some Help ?

Update: I did once boot it with VolumeDown+Power, and it booted into some Chinese menu.
The "Rescue and Smart Assistant" does have a note on the bottom of the Serial Entry window stating "Tablets sold in Chinese mainland is not supported currently". Still doesn't excuse older software to forcibly update.
Perhaps this is a device that was made for China, loaded with an english OS en sold in the UK ? Just guessing.
It was bought in the UK though. All text on it is in english.

Another Update, after Re-plugging the device cable for the 17th time, it suddenly popped up again in QFIL [!?] (So it is still in EDS mode, but won't reboot or do anything)
Tried another Stock Rom push (exactly the same as I tried 3 times yesterday, before heading to bed), and this time it didn't error and successfully pushed the Stock Rom ! Rebooted into OS, no longer dead. (What the .. ? Consistency -5)

I don't have much experience with Lenovo devices.
With Moto devices, a USB cable that works fine with other devices can still cause issues with LMSA/flashing, as with USB ports and PCs.

 

[rotorline]

I'm trying to load an A12 firmware https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on my Moto G Stylus which someone has done previously. And he thought he's done it with the RSA tool.
Just downloaded G Pro A12, placed it in the correct folder, but the assistant won't let me install it. It insists on downloading the last A10 file. Any way to force it to to use the zip file for A12?

 

[sd_shadow]

I'm trying to load an A12 firmware https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip on my Moto G Stylus which someone has done previously. And he thought he's done it with the RSA tool.
Just downloaded G Pro A12, placed it in the correct folder, but the assistant won't let me install it. It insists on downloading the last A10 file. Any way to force it to to use the zip file for A12?

Yes, the folder must be renamed to the same as newest available

 

[rotorline]

Thanks for the reply. This thread has been a amazing resource for anyone unsure about the functions of Rescue and Smart Assistant.
The firmware that RSA downloads as the latest is: SOFIAP_RETAIL_RPRS31.Q1_56_9_15_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
The firmware that I downloaded to try and update to is: SOFIAP_RETAIL_12_S0PRS32.44-11-19-9_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So I should just change my downloaded file to exactly the same as the RSA firmware? I'm asking because of the difference in file extensions. i.e . .xml and .zip
The only difference I see in the files is a Local Disk shortcut file in the RSA file.

 

[rotorline]

I see that there's a folder in c:\ProgramData\RSA\Download\Moto G Pro\RomFiles\ named for the RSA download.
Should I delete the files in that folder and extract the downloaded .zip into it?
Just trying to make sure this is the correct spot to have the replacement firmware placed for RSA to see it.