yashsingh1/xdaforums huggingface dataset:
[Moto G5S  Questions & Answers] cheater00:
Thanks a lot for the reply. I have fastboot.exe from the Android SDK.

Do I need to have the Motorola Drivers installed for this? I can't install them. I got the file from XDA from your link here.

I opened the downloaded file in 7zip and double clicked on Motorola_End_User_Driver_Installation_6.4.0_64bit.msi, clicked "Next", "I agree", and "Next", and I was presented with the image "motorola drivers error 1" in the attachment. Clicking through on those continued what you can see in file 2 and 3.

Or should I just run the device in Fastboot mode, connect it via USB, and then run fastboot.exe like you say above? (when I connect the device via USB in fastboot mode, it doesn't get recognized in the Device Manager on Windows. I guess due to missing drivers, but not sure, so I'm just giving you all the information I know)

The PC I am on has Windows 10, but it didn't come with it - I installed it manually. Will that be fine?

I also have an older PC which never had Windows 10 on it (only Linux and maybe XP, not sure). I would run RSD on that too, but it would take a bunch of time to set up.

How would I use RSD Lite for that purpose? Will "without wiping data" also mean photos, as well as Chrome tabs and settings of other apps? (Google Authenticator, Steam Authenticator, Google Keep (notes), WhatsApp, etc)

Chrome on that device is not logged in so the tabs are not in the cloud.

Thanks again for being so nice to help out - that means a lot to me!
[Moto G5S  Questions & Answers] sd_shadow:
Use the newer link

https://mobilesupport.lenovo.com/us/en/solution/MS88481

RSD Lite doesn't work with PCs built for windows 10, not sure why exactly.

I know RSD Lite doesn't like usb 3.0.

I have used RSD Lite on a few PCs that have been updated to 10 that worked fine.

see My flashing guide https://xdaforums.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039

use getvar all to find codename, software channel, and moto blur software version.

You must not downgrade software version.

Downgrade the correct firmware from

https://mirrors.lolinet.com/firmware/moto/

or use LMSA Flash rescue to download firmware

This is the safer option

LMSA will ask to download firmware, after downloading, it will ask to continue with flashing.

Just don't flash with LMSA.

Firmware will be in something like c/program data/lmsa/downloads/romfiles

If you download from Lolinet unzip the file, LMSA shouldn't be zipped.

There should be 2 .xml files in the folder, these contain the flashing commands.

The servicefile.xml does not wipe user data, the flashfile.xml does wipe data.

If you want you can use notepad++ to view the xml file commands.

select the servicefile.xml with RSD Lite and flash.

After flashing with RSD Lite the device should boot, provided there is not a hardware issue.

No guarantees though.
[Moto G5S  Questions & Answers] cheater00:
Thanks again. Highly appreciated.

Unfortunately this results in the same error. I guess RSD Lite and the other software will not work without those drivers. So I might have to build a new windows system for this purpose. I will try to do that asap.

Thank you. Just to be sure. Using servicefile.xml with RSD Lite will not erase phone logs? Can you tell me about that specifically? The reason is, and I'm not sure if I should be talking about this here, the following. (please let me know and I'll delete this or feel free to edit the post on your own). I'm pretty ill with, well, you can guess what, and I'm quarantined. Since March none the less. So every now and then the police will come checking if I'm home. Apparently last month they couldn't find me on one day. But I did call them back after I woke up. So to prove this I need the phone logs. Otherwise I might go to jail for a month, just because I was sleeping (because after all I'm ill!). So as you can tell this is pretty important... it's not just kitten pictures. I would appreciate if you could let me know.
[Moto G5S  Questions & Answers] sd_shadow:
You could try the google android drivers

https://developer.android.com/studio/run/win-usb

or manually install the old moto drivers.

https://xdaforums.com/showpost.php?p=59139887&postcount=4

As long as the .xml doesn't contain the line

fastboot erase userdata

Call logs, browser history, texts... will still be there.

To be extra safe I would remove the flashfile.xml

Have you tried any fastboot commands?

like fastboot devices, fastboot getvar all ?
[Moto G5S  Questions & Answers] cheater00:
Actually I didn't need to install old drivers. I took the latest msi file and extracted it the following way:

msiexec /a c:\testfile.msi /qb TARGETDIR=c:\temp\test

Note that if the .msi file's file name is too long, msiexec will have issues extracting it. Also, you have to use full path names. If you use relative path names, msiexec will be stupid and think you are using a network file name or something like that. So always start with a drive letter.

The extracted directory structure had a subdir several levels deep called Drivers. I went to the Windows 10 Device Manager, and under "Other devices" (which is stuff that Windows didn't recognize and doesn't have drivers for) there was "fastboot sanders S". I selected "Update Driver" on that item, and pointed the dialog to the Drivers directory, and now the phone is being recognized. It is located under "Android Device" and it's now called "Motorola ADB Interface". The device called "fastboot sanders S" is gone.
[Moto G5S  Questions & Answers] cheater00:
Thank you very much for confirming!

Thank you, it works now! Here's the output.

> .\fastboot.exe devices
ZY32283ZDS fastboot

> .\fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: (removed) (let me know if you need it)
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: (removed) (let me know if you need it)
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: (removed) (let me know if you need it)
(bootloader) meid:
(bootloader) date: 08-10-2017
(bootloader) sku: XT1805
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 0:44:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_n/sanders_n:8.1.0
(bootloader) ro.build.fingerprint[1]: /OPS28.65-36-14/63857:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.271.12.sanders.re
(bootloader) ro.build.version.full[1]: tail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gfde333e (hud
(bootloader) kernel.version[1]: soncm@ilclbld57) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Tue Aug 13 15:23:08 CDT 2019
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=d95e83f
(bootloader) devcfg.git: git=d95e83f
(bootloader) keymaster.git: git=d95e83f
(bootloader) cmnlib.git: git=d95e83f
(bootloader) cmnlib64.git: git=d95e83f
(bootloader) prov.git: git=d95e83f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: protected (1003)
(bootloader) ro.carrier: reteu
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Finished. Total time: 0.110s

Please let me know if you see anything interesting here - or what you're looking for - I'd love to learn more about the topic. Thanks.
[Moto G5S  Questions & Answers] sd_shadow:
codename is sanders

Model is XT1805

Software Channel is reteu

Software Version is 28.65-36-14

so this version should be good.

https://mirrors.lolinet.com/firmware/moto/sanders/official/RETEU/

XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

but I would also see which version LMSA selects.
[Moto G5S  Questions & Answers] cheater00:
Thank you, I'll check LMSA.

What is the difference between SS/DS and OPS/OPSS?
[Moto G5S  Questions & Answers] sd_shadow:
ss should be Single Sim

ds should be Dual Sim

O is android 8 (oreo)

Not sure about the difference between PS and PSS.

But don't think it's anything big.
[Moto G5S  Questions & Answers] cheater00:
I tried LMSA and it says the phone is not supported. If I select the model number manually

Model Name: "Moto G Plus (5th Gen S)"

SKU: "XT1805"

then it says it doesn't match.

If I instead click on "Read current device" then it says it was not recognized.

Pictures are attached.

What do you suggest?

Edit: should I just go ahead with XT1805_SANDERS_RETEU_DS_8.1.0_OPS28.65-36-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip?
[Moto G5S  Questions & Answers] cheater00:
After installing LMSA, it directed me to the Lenovo forums, which I didn't know even existed.

It turns out there are two instances of people's G5S Plus spontaneously developing a boot loop: Thread 1, Thread 2.

In addition to that, the issue with LMSA is known on the Lenovo forums: LMSA not Working for Moto G5s Plus - Motorola Community

Following the advice in that thread, I looked at my LMSA logs. I uploaded them here: LMSA.log.

There are two things that come to mind. Here I quote from the log link above:

It's clear to me that the error is on these lines:

2020-06-29 09:48:52 [26] [INFO] Current_SoftStatusChanged - match rescue resource params: {"blurVersion":"Blur_Version.28.271.12.sanders.retail.en.US","fingerPrint":"motorola/sanders_n/sanders_n:8.1.0/OPS28.65-36-14/63857:user/release-keys","fsgVersion.qcom":null,"roCarrier":"reteu"}
2020-06-29 09:48:52 [26] [INFO] Match - missing parameter when match rescue resource

I do not have US english selected. I have bought the phone in Europe, in Austria (so the code
would be de_AT or de.AT) and I kept using the phone in British English (code en_GB or en.GB
or en_UK or en.UK). So this could be related. Or maybe fastboot not being able to find the
baseband version is an issue.

2020-06-29 09:49:40 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Failed to read [version-baseband] in fastboot, will try again
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband]: <not found>
2020-06-29 09:49:41 [13] [INFO] ReadFsgVersion - [LMSA_Read_Fastboot] Read [version-baseband] finally value:

Note that LMSA also detected OPS28.65-36-14, which is the same version as you suggested. However, the fact that LMSA says the phone is not supported, makes me worried.

If fastboot.exe is not able to detect the baseband, what does that mean? Is that normal, or should I be worried?

Thank you for your help thus far.
[Moto G5S  Questions & Answers] cheater00:
[MENTION=4267571]sd_shadow[/MENTION] just wanted to update, I have tried contacting Lenovo on multiple fronts (someone even put me in touch of the president of Lenovo for north america!) but silence so far.
[Moto G5S  Questions & Answers] cheater00:
[MENTION=4267571]sd_shadow[/MENTION] sorry to bother you again, I was wondering if you had any idea on why LMSA might be saying my phone is incompatible?

fastboot.exe unable to find out the baseband, is that normal, or is this something unusual?

What should I do now - flash with the firmware file you suggested?

Thanks again
[Moto G5S  Questions & Answers] sd_shadow:
Probably because LMSA cannot determine which baseband is needed.

It's not unusual for a device that will not boot.

I would try using RSD Lite.
[Moto G5S  Questions & Answers] cheater00:
[MENTION=4267571]sd_shadow[/MENTION] Thanks again. I tried RSD Lite but on my Win 10 PC it does not recognize my phone. It's just not listed in the lower half of the window. (update: see below) The drivers are installed correctly and the phone shows up in the Device Manager as "Motorola ADB Interface". I turned on the phone into Fastboot mode and connected it via USB directly to the motherboard's USB port. And RSD Lite is launched in Administrator mode. So there's no reason it shouldn't see the device. Is this how the incompatibility you mentioned earlier manifests itself, or is what I am experiencing due to some other issue? Is Fastboot mode the right way to set up the phone for use with RSD Lite? Or should I enter some other mode? Your guides mention entering a "flash mode", but there's no such thing on this G5S Plus.

Edit: I just got a call from a Motorola engineer in the UK who was trying to reproduce the issue. He said that the baseband on my phone corrupted itself and that for this reason both LMSA and RSD Lite will not work, as they require the baseband information as a sanity check. He mentioned that I would have to basically perform all the steps of servicefile.xml myself by hand using fastboot.exe. So I'm going to try to figure out how to do that now. I think I saw this in one of your guides, but it escapes me where.

Edit2: found how to flash with fastboot.exe here: How to Firmware Restore your Motorola Device on Windows 10 without RSDlite
[Moto G5S  Questions & Answers] cheater00:
[MENTION=4267571]sd_shadow[/MENTION] I have one more question if I may. The Moto engineer I spoke to mentioned that re-flashing the baseband could possibly delete the call logs. Also he mentioned that some or possibly most of the apps might not work any more which would be relevant for recovering the rest of the data. However, the baseband is made of multiple partitions, so I thought, maybe the issue is in just one of the partitions, and maybe flashing just that will not overwrite the phone calls / app-related data / other data that I still need. So I was wondering if you'd be kind enough to tell me what the different partitions do? Can I just flash one of the partitions? (noting that system will need all chunks flashed at the same time). Which one of them might contain app-related or system-related personal data like call logs? Do you know where exactly call logs are stored? Thank you very much. Below is a list of the partitions and image files for reference.

partition gpt.bin
bootloader bootloader.img
modem NON-HLOS.bin
fsg fsg.mbn
dsp adspso.bin
logo logo.bin
boot boot.img
recovery recovery.img
system system.img_sparsechunk.0
system system.img_sparsechunk.1
system system.img_sparsechunk.2
system system.img_sparsechunk.3
system system.img_sparsechunk.4
system system.img_sparsechunk.5
system system.img_sparsechunk.6
system system.img_sparsechunk.7
system system.img_sparsechunk.8
system system.img_sparsechunk.9
system system.img_sparsechunk.10
oem oem.img
[Moto G5S  Questions & Answers] sd_shadow:
Try

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
[Moto G5S  Questions & Answers] cheater00:
Hi [MENTION=4267571]sd_shadow[/MENTION], sorry for the longer wait. I tried the following things:

started with: device in boot loop

.\fastboot.exe flash modem .\NON-HLOS.bin
.\fastboot.exe reboot

outcome: still in boot loop

.\fastboot.exe erase modemst1
.\fastboot.exe reboot

outcome: still in boot loop

.\fastboot.exe erase modemst2
.\fastboot.exe erase modemst1
.\fastboot.exe erase modemst2
.\fastboot.exe reboot

outcome: still in boot loop

.\fastboot.exe erase DDR
.\fastboot.exe reboot

outcome: still in boot loop

.\fastboot.exe flash logo .\logo.bin
.\fastboot.exe reboot

outcome: still in boot loop

.\fastboot.exe flash dsp .\adspso.bin
.\fastboot.exe reboot

outcome: still in boot loop

After erasing modemst1 and modemst2, the IMEI hasn't changed (I can see it in the fastboot environment by looking at the "barcodes" option). I am hesitant to flash fsg, because it contains the backup of modemst1. On some devices, the IMEI is contained on a separate partition called efs, but sometimes what would normally be inside the efs partition is located in modemst1. It's safe to erase modemst1, because fsg (the "file system gold copy") contains a backup of modemst1 and efs according to this document *. But I'm not sure if overwriting fsg will lose me the IMEI. could you confirm? The issue is that official android docs on Keystore Attestation say the following:

Could you please answer the following 4 questions?

If I understand correctly, if the IMEI changes, the attestation will become void, and therefore the encryption store will become void and I will be unable to access data encrypted using File-Based Encryption (FBE). Do you know if this is correct?

Does the Moto G5S Plus, after upgrading to 8.1, use FBE, or does it use Full-Disk Encryption (FDE)?

Does the Moto G5S Plus have a separate efs partition, or is the IMEI stored on modemst1?

Will reflashing the efg lose the IMEI?

* note: read the "editing" version of this wiki page, because the rendered wiki version eats the line breaks and everything is on one line
[Moto G5S  Questions & Answers] sd_shadow:
I have used flash fsg fsg.mbn many time on multiple devices, and never lost IMEI.

fastboot flash fsg fsg.mbn

it's included in every standard Motorola flashfile.xml and servicefile.xml

It's not uncommon for IMEI to show as 0 or missing after flashing a custom rom,

or wifi stops work

If this happens flashing the following often fixes the issue.

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn

As far as I know they do not affect encryption on Motorola devices.
[Moto G5S  Questions & Answers] cheater00:
(deleted)
[Moto G5S  Questions & Answers] cheater00:
Thanks [MENTION=4267571]sd_shadow[/MENTION]. After performing these steps, the device is still in a boot loop. Can you suggest further steps please? I don't know what the next thing might be that I could try.
[Moto G5S  Questions & Answers] TwoPointZero:
On the fastboot screen (AP Fastboot Flash Mode (Secure)), does it list your device

product/variant: sanders XT1805 (good)

or product/variant: sanders 000000000000 (bad)

Second, LMSA (Rescue and Smart Assistant) detects the model when you plug the phone in. Therefore, if it's already plugged into the computer, first unplug then replug and it should be detected.

Third, if you have a micro-sd card in the slot, you should try booting the restored stock rom without any sort of external SD, fused storage or not. If the moto logo stays on-screen for longer than usual it's a good sign (firstboot)
[Moto G5S  Questions & Answers] cheater00:
Thanks for your reply. I'm not sure what you are instructing me to do. Would you mind clarifying please? My device does have an external SD card slot, but no card is inserted. What should I do? [MENTION=4267571]sd_shadow[/MENTION] what are your thoughts? Thanks.

Regarding LMSA,

fastboot getvar all

does not list the baseband version (the output is blank for that variable); having spoken with a Motorola representative who works on their Android software, he said that he doesn't know why this is the case, and that in this case LMSA will not perform any flashing will and reject the device. That's what happens indeed: LMSA says that the device is not supported. Unfortunately, I cannot reach the person any more to ask for any more advice as they have called me.
[Moto G5S  Questions & Answers] cheater00:
Thanks for your reply.

nothing is off the table as long as it gets the phone booting again and gives access to the user data.

Where is that stated? Could you point me to that please? Thanks!

No, just normal output as you get when flashing with fastboot.exe.
[Moto G5S  Questions & Answers] TwoPointZero:
Regarding IMEI in persist, investigations in this thread: https://xdaforums.com/g5-plus/how-to/dev-fixing-baseband-t3806064/post76901785#post76901785 led to this KB article https://xdaforums.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 by NZedPred, rachitrawat

Well, if you're willing to unlock the bootloader, there's an official method that 'voids' warranty (not that it applies in EU mind you)

It's all feasible via fastboot (oem get_unlock_data), you'll need to register for the procedure proper is at https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (https://support.motorola.com/us/en/solution/ms87215 for other Moto models). The unlock key is mailed to you after accepting the terms.

Unfortunately unlocking wipes the device therefore it won't be good for your case. Sorry :rolleyes:
[Moto G5S  Questions & Answers] cheater00:
Yeah, unfortunately the data is necessary. I am trying to figure out the next steps. Thank you for the links, I will read them as soon as I can.
[Moto G5S  Questions & Answers] IAmHum@n:
I had my phone boot up and the screen flashed on and off a few times. It was sitting on the Motorola logo for a while. Then it was stuck on the Lenovo logo. As of this writing the battery is only 78% charged. I am going to charge to 100% and see if it boots then.

I have a Motorola G5S. So its similar I'm guessing?

Btw what is SoC?
[Huawei P20 Themes, Apps, and Mods] Ices_Eyes:
Ok, so, I really like the new EMUI 10 default theme, but since I started using EMUI there is oone whing I completely dislike and that's the messy icon shape of the variuos app. sometimes they are EMUI like, other are completely squared, other are circles...

I noticed that by using some themes, all icons become of the same shape, either those not present on the theme icons folder. So, is there a way to create a theme that just make alll icons same shape (maybe circle)? I tryed to create a theme with just the icon zip file in it, with the various icon_mask, icon_border, icon_* file in it, but while many icons go circle, not all of them do... :(

What am I missing? :confused:
[Xiaomi Mi Mix 2S Guides, News, & Discussion] Sophon Wu:
An explain goes first:

This may surprise a lot of people, "Whaaaat? Isn't UEFI a kind of BIOS on PC?" Well, it can also be on your phone too, in fact.

This is an EDK II (UEFI) port for Mi Mix 2S. Currently it's incomplete, but already usable.

What is this port for?

This is an UEFI port, so there are many possibilities. As a second-stage bootloader, it can boot any ARM64 OSes that support UEFI.

At this point, both upstream Linux and Windows on arm are capable of booting. The UEFI firmware itself is very broken, so you should only use it as something which can help you boot OSes.

Status of this UEFI implementation:

Working:

Framebuffer

MMU

UFS

Not Working:

Everything else lol

Status of OS booting

Windows PE arm64 boots with the embedded broken ACPI tables, but nothing is working. You are welcomed to fix the ACPI tables if you can.

Ubuntu 20.04 unmodified iso (kernel 5.4) boots with the broken device tree that I writes.

See GitHub README.md for more details.

Some releases will be provided in the GitHub repo soon.

Source: https://github.com/edk2-porting/edk2-sdm845

Some pictures are provided in the GitHub repo.
[Xiaomi Mi Mix 2S Guides, News, & Discussion] Sophon Wu:
You are welcomed to share your experience here if you have had a try.;)
[Xiaomi Mi Mix 2S Guides, News, & Discussion] Sophon Wu:
Seems that I can upload photos now.:)
[Xiaomi Mi Mix 2S Guides, News, & Discussion] korale:
Nice project. Looks promising. I didn't test it yet and I'm no developer to support the project. just wanted to say to keep up with your work.
[Xiaomi Mi Mix 2S Guides, News, & Discussion] kissamopo:
This is amazing!
[Xiaomi Mi Mix 2S Guides, News, & Discussion] amir-456:
wow thanks. thats so cool.

keep up the good work waiting for a working release.