yashsingh1/xdaforums huggingface dataset:
[Honor 9 Lite Questions & Answers] Dragonz8413:
I was on latest update on my honor 9 lite , used firmware finder DNS exploit to Downgrade to oldest version which worked and then used dcunlocker and worked instantly .
[Honor 9 Lite Questions & Answers] Abderahmane31:
Any News About How To Unlock The Bootloader ?

I Am On The Lastest Version March 2019 Patch !!
[ZenFone 2 Q&A, Help & Troubleshooting] :
So now, my Zenfone 2 can't connect to PC with error 43 and I am not ready to fix the USB port. So how can I unlock my bootloader without PC?

My phone is in stock MM with locked bootloader.
[ZenFone 2 Q&A, Help & Troubleshooting] EmilioDallaTorre:
I’m quite sure you’d better find a way to connect your ZenFone to pc.

Android bootloader cannot issue fastboot commands directly to himself...

I can advise you to revert back to Lollipop bootloader, and then proceed to the unlock, hoping that this operation will fix the USB port.

:highfive:
[ZenFone 2 Q&A, Help & Troubleshooting] :
My USB port had damaged physically... :(

So far it can charge, but no fast charging with stock fast charger.

Windows show error 43 every time, every cable I do connecting my Zenfone to PC.

How can I revert back to LP bootloader without PC?

Maybe putting a LP ZIP file to recovery will work? Or will just hard brick the phone?

Rooting might be possible without PC but with unlocked bootloader...
[ZenFone 2 Q&A, Help & Troubleshooting] EmilioDallaTorre:
I think you're in a really bad situation.

I changed my USB port on my own, and it worked like a charm... ZenFone 2 is very easy to be hardware-hacked.

DM me if you want, I can support you even substituting your port, if you send me your Zenny and a USB module...
[ZenFone 2 Q&A, Help & Troubleshooting] :
If you are still on Lollipop you can use directly on the phone this official tool: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UnlockApp_ze551ml_20150723.apk

EDIT: Didn't read you are on Marshmallow, sorry...
[ZenFone 2 Q&A, Help & Troubleshooting] :
Then you will see more problems: half damaged screen, both SIM cards not detected, speaker, vibrate and proximity not working...

Just a single drop and all these are the results :(
[ZenFone 2 Q&A, Help & Troubleshooting] EmilioDallaTorre:
Maybe it's easier than it seems. I don't know if you have some skills in this ambhyt, but ZenFone is relatively easy in the inside, maybe is just a connector (one of the SIM slot, the one nearest to the USB port, with the yellow plastico above) which is not well placed...
[ZenFone 2 Q&A, Help & Troubleshooting] :
Finally I will have a new Zenfone 2 tomorrow... Quite cheap. Just 30$ :victory:

My experiments will soon be started... :good:

My old damaged Zenfone 2 will be hardware replacement for my new one if my new one have hardware problems. As they are in the same specifications.

Anyways, thanks for your help!
[Samsung Gear S3] LuchooB:
Hello,

I just bought a gear s3 classic new according to the seller (2nd hand, not official) and I noticed some green pixels at the top of the screen. I dont know if there is any way to fix it or if I should return the watch. I'll live a picture of the screen.

Hope you could help, thanks!
[Samsung Gear S3] adfree:
It could be Battery is blowing... and too much pressure on Display...

So Hardware problem...

https://www.youtube.com/watch?v=eQfb52LQpPA

https://www.youtube.com/watch?v=TMYSm3NoefY

So IMHO test would be to open device... and look if Display is okay...

IMHO 4 Screws to remove... then Rear Case/Baack Cover...

Maybe this is enough to lower Pressure...

Best Regards
[Samsung Gear S3] aloxotls:
I am having the same problem did you ever find a fix?
[Droid Turbo 2 Q&A, Help & Troubleshooting] mattjhsn:
Hello!

My XT1585 with 7.0 shows camera busy whenever I open the stock camera. This first started after a factory reset and auto apps reload. I've uninstalled all of the extra camera apps I had on there. I went to settings -> apps > configure apps -> app permissions -> camera, and turned off all permission except the stock camera app. I see no change after a reboot.. See attached screenshots.

Any ideas?
[Droid Turbo 2 Q&A, Help & Troubleshooting] FirePsych:
Turn on all permissions for Camera

Clear Data in the camera app through settings.

Clear Cache through recovery.

Reboot
[Droid Turbo 2 Q&A, Help & Troubleshooting] mattjhsn:
Thanks FirePsych. I did 1) and 3) but not two. Will report back.
[HTC Excalibur] bbbblack:
Ive searched all over this forum, but i havent found any1 else w/ this problem.

I have the kavana 6.1 rom (best one to date) on my excalibur. Everything is great, but i noticed when i receive a text from someone, it will look like this:

person1: (8.08 pm) :

hey !

me: (8:06 pm) :

whats up !

As u can see i obviously responded "after" the person, but my time is logged as though i sent the message prior to them. sometimes this screws up the order when i go back into earlier convos. I tried jumping my clock ahead 3 minutes, works for like half a day, then it starts f'in up again. And no, i am not texting someone out of the country. Thanks in advance. And if someone has already posted this problem, i apologize
[HTC Excalibur] bbbblack:
oops

i didnt mean 2 post the thread twice, i thought when u click on post you would get a chance too preview it before confirming
[Magisk] SirLoinOfBeef:
Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.

I'm running a Pixel XL.
[Magisk] zen kun:
Same in my pixel 2 XL

I tried patching the boot.img and I got an error
[Magisk] uodii:
I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.
[Magisk] joderme:
Having the s ame issue. Can't unpack and patch boot.img.
[Magisk] SirLoinOfBeef:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
[Magisk] zen kun:
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/
[Magisk] TENN3R:
For me works with no problems.

I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).

Booted twrp img, then in recovery:

- flashed latest twrp.zip

- rebooted recovery

- I flashed Flash Kernel just because I like it

- Straight after magisk 16.4

- rebooted.

Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.
[Magisk] joderme:
Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.

I get:

- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed
[Magisk] djuniah:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
[Magisk] joderme:
I assume you installed through TWRP?
[Magisk] djuniah:
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.
[General Questions and Answers] eplerd:
I have a sim unlocked AT&T Galaxy S8 Active (SM-G892A) that I've had number-ported over to T-Mobile for a month or so now.

as it has firmware G892AUCS2BRD4 on it now I wasn't able to update it to T-Mobile's firmware as they WERE on Bootloader V1.

Well today on TMO web site I saw they now have G892USQU2BRE3 out and I was trying to use a modded Odin 3.13.1 to update it.

I previously used this Odin to flash two S7's from AT&T firmware to T-Mobile with no issues so I thought Odin was okay

When I attempted to do this on my S8 Active I get the following:

<ID:0/005> Odin engine v(ID:3.1301)..

<ID:0/005> File analysis..

<ID:0/005> Total Binary size: 4306 M

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Set PIT file..

<ID:0/005> DO NOT TURN OFF TARGET!!

<ID:0/005> FAIL!

<ID:0/005>

<ID:0/005> Re-Partition operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

I re-downloaded the firmware using SAM-FIRM to ensure it was Legit and got same error.

What am I missing here?

I think I even tried to select Re-partition in odin once (tired and went thru a lot of retries tonight).

Do I need a Super-Special Odin for this newer firmware?

Is it AT&T's darned bootloader causing issues?

Thans in Advance

Dave in Tampa
[General Questions and Answers] pwoolston:
Im getting the same error trying to load a custom rom from PartyCyborgROM over G892USQU2BRE3. I had to revert back to the exact stock rom. If you find anything let me know.
[General Questions and Answers] eplerd:
RATS - saw the reply and got excited thinking someone had a fix :crying:

Still Hopeful...
[General Questions and Answers] pwoolston:
CF-Root

I am going to try CF-Auto-Root for Nougat to see if it works on Oreo Cookie. It's worth a try I guess.
[General Questions and Answers] eplerd:
Yeah - I don't wanna root my phone - no need, just want AT&T Bloatware that's useless now gone, and T-Mobile apps on my cell - like I did for friends S7's
[General Questions and Answers] eplerd:
Has ANYBODY done this?

I really NEED to get this done as I'm missing phone calls and can't afford a new cell now.

Sure wish I had bought a cheaper S7 as converting it to a T-mobile model was easy on my friends 2 phones.

I'm now wondering IS the S8 active the same across cell vendors (T-mobile, ATT, Sprint, etc) like the S7 is??
[Moto G5S Plus Questions & Answers] marcdw:
I have a strange issue where some ROMs have stopped syncing contacts. Didn't really notice until I made changes to some contacts on another phone. Jumped around from ROM to ROM on all the devices (multiboot on each) to check. Only on this device do I have this behavior.

Stock Nougat. Good.

AOSiP, microG, Google sync. Good.

Bootleggers, microG, DAVdroid. Good.

FrankenROM, OpenGapps. Last sync May 22.

GZOSP, Pixel-GApps. Last sync May 23.

Xtended, OpenGApps. Last sync June 3.

If there's a problem one usually gets an exclamation mark in the spinner and a message at the bottom. Nothing here. Doesn't even attempt to sync.

I've cleared cache and/or data of contacts items, forced Sync Now, removed & re-add account, to no avail. Not sure what's going on yet.

When I first installed the latest Pixel Experience ROM it also wouldn't sync contacts at all. On a later installation it did.

Four ROMs on the Axon 7 (Nougat and Oreo), two on the G3 (Lollipop). Contacts are good.

Reckon I better generate and peruse some logs.

Moto G5s Plus XT1806, MSM Xtended v2.0 ROM, MultiROM, Tapatalk 4.9.5
[Moto G5S Plus Questions & Answers] plusminus_:
I'm still having contact sync trouble with my phone too (Sony Z5 Compact) - last synced on the 9th of June. I tried syncing contacts on my tablet a couple of days ago and it worked as expected, which made things more confusing for me, but I've tried to look for any differences between the devices.

Based on this thread I have a suspicion that it is a problem with Google Play Services. Both my devices have Google Play Services 12.6.85, but different subversions (if that's the right word to use?).

The tablet, which syncs correctly, has 12.6.85 (040300-197041431) which appears to be the package for arm-v7a, while my phone has 12.6.85 (040406-197041431), for arm-v7a + arm64-v8a.

I can see a newer version on APKMirror so I will try it and see if that fixes things. - No improvement with 12.6.88 :(

edit: Before I do that, when I try to sync manually this error shows up in logcat: (SyncManager) failed sync operation ... com.android.contacts ... reason: 1000 [ numIoExceptions: 1] - unfortunately I have no idea what reason 1000 is!
[Moto G5S Plus Questions & Answers] marcdw:
[MENTION=8705151]plusminus_[/MENTION], with no responses I assumed maybe it was just a me thing. Couple of days ago I wiped out all of the ROMs except for the one using microG.

Started fresh. Flashed four ROMs w/gapps but none were able to sync contacts. Searched the G5s+ Telegram group and discovered there's a fix. So I guess it is/was a known issue.

Flashed it and now syncing works. Bad timing though, finding the fix right after erasing the ROMs. ?

The fix copies a device_key to the Play Services data. Safe to assume only for this device (sanders).

https://drive.google.com/file/d/132ghcwBSOF5TJk69RjuyT5QQhEvx3SH-/view?usp=drivesdk

ZTE Axon 7 A2017U, Project New World, Multiboot, Tapatalk 4.9.5
[Moto G5S Plus Questions & Answers] plusminus_:
I'm glad you got sync working again!

I can't access the file, but I doubt I would be able to use it anyway, thanks though :p
[Moto G5S Plus Questions & Answers] plusminus_:
I finally got my contacts to sync, and indeed it was the missing device_key file that was causing the problem! I came across this post this morning and fiddling with Xposed sorted things out. This is what I did (for future reference perhaps)

1. Disable Xposed Framework in Magisk and Xposed Installer (I think disabling it in the Installer was not needed but I'm replicating my steps here)

2. I also disabled one of the Xposed modules I was using, No Device Check

3. Clear Google Play Services data (Settings > Apps > Google Play Services > Storage > Manage Space > Clear All Data)

4. Reboot

5. Let the phone sync

6. Check that /data/data/com.google.android.gms/files/device_key exists now (I also backed it up)

7. Enable Xposed Framework in Magisk

8. Reboot

9. Enable Xposed Framework in Xposed Installer

10. Reboot again...
[Moto G5S Plus Questions & Answers] marcdw:
[MENTION=8705151]plusminus_[/MENTION], nice find.

I always flash Xposed with a new ROM. On the next one I try today I'll wait and install Xposed after the ROM and Google are setup and sync is working.

Even though I have that fix zip I'm curious.

Never occurred to me that Xposed would mess with syncing.

Moto G5S Plus XT1806, Resurrection Remix ROM, AL-ice Kernel, MultiROM, Tapatalk 4.9.5
[Moto G5S Plus Questions & Answers] gmikhail:
/data/data/com.google.android.gms/files/device_key not created :(

Can I somehow generate it manually?
[Moto G5S Plus Questions & Answers] marcdw:
Depends. What is your device? If it's the G5S Plus you can use the zip I linked earlier. Flash it after you've been in the ROM at least once and after you've set up Google (otherwise the directory won't exist yet).

If on another device you can try some or all of what [MENTION=8705151]plusminus_[/MENTION] posted to see if it shows up.

Moto G5S Plus XT1806, Lluvia OS v1.4, TridentExperience, MultiROM, Tapatalk 4.9.5
[Moto G5S Plus Questions & Answers] gmikhail:
I came across a topic from Google. My device is Lenovo P70-A, LOS14.1 (android 7) but I had the same problem with contacts synchronization.
[Miscellaneous Android Development] LluisR98:
" #DroidOnTime "

* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.

dotOS is an Android Rom which focuses on performance and stability. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get most out of his/her device.....

CLEAN FLASH :

Download the latest build and GApps

Reboot to recovery

Make NAndroid backup (Not Necessary)

Wipe System, Data, Cache , Dalvik

Flash the latest build and GApps

Reboot

DIRTY FLASH :

Download the latest build

Reboot to recovery

Flash the latest build

Wipe Cache

Reboot

Note : GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.

Download ROM:

DotOS v2.4 ROM

Download Gapps:

OpenGApps​

Note : Pico, Nano or Micro Gapps are recommended.​

[LIST]
[U][B]STATUSBAR:[/B][/U]
[*]Battery Icon Style
[*]Clock and Date
[*]Statusbar icons
[*]Traffic indicators
[*]Misc

[U][B]Navigation Bar:[/B][/U]
[*]Navbar modes(Stock, Smartbar, Fling)
[*]Smartbar tweaks
[*]Navbar Pulse
[*]Fling mode gestures
[*]All DUI nav tweaks

[U][B]QUICK SETTINGS:[/B][/U]
[*]Brightness slider toggle
[*]Titles visibility
[*]Tiles track accent color toogle
[*]Quick pulldown
[*]Smart pulldown
[*]Rows and columns tweaks

[U][B]RECENTS:[/B][/U]
[*]Memory bar
[*]Immersive recents
[*]Clear all fab
[*]Clear all fab location

[U][B]LOCKSCREEN:[/B][/U]
[*]Double-tap to sleep
[*]Lockscreen Tuner
[*]Charging info
[*]Media cover art toggle

[U][B]BUTTONS:[/B][/U]
[*]Powermenu tweaks
[*]H/W keys customisation
[*]Volume button tweaks

[U][B]MISC:[/B][/U]
[*]Launch music app on headset connection
[*]Battery light charging customisations
[*]App Ops
[/LIST]

dotOSteam

AOSP

JDC Team

Aosp Extended And all other open source Devs/Teams.​

Mohan CM - Owner/Lead Developer

Ganesh Varma - Developer/Contributor

Kuber Sharma - Developer/Contributor

Sam Grande - UI Developer/Contributor

Iacob Ionut - UI Developer/Contributor

Hari Ambadi - Core GFX/Visual Designer

Special thanks:

Alexcbrookes - Arts & Wallpaper Designer

Important Links

dotOS source

dotOS-Device Sources

Google Plus Community

Telegram Group

Telegram Channel

Website

REPORTING BUGS!

As soon as the problem occurs, take a logcat!

​

XDA:DevDB Information

dotOS, ROM for Piccolo (BQ Aquaris M5)

Contributors

LluisR98, Aymen7, Aquaris-Dev and Other

Source Code: DotOS

Device tree Source: GitHub

Kernel and Vendor Source: GitHub

Version Information

ROM Firmware Required: 5.1.0 or 5.2.0 BQ Stock

ROM OS Version: 8.1.0r36 Oreo

ROM Kernel: Linux 3.10.x

Based On: AOSP

Status: Work in progress

Current Stable Version: v2.4

Device: Piccolo

Maintainer: LluisR98

Build Status: UnOfficial

Created 2018-06-06

Last Updated 2018-07-23
[Miscellaneous Android Development] LluisR98:
Changelog

* [06/06/2018]: 1st ZIP.

* [08/06/2018]: Update to v2.3.

* [13/06/2018]: Fix: Music playback from sdcard and others.

* [23/07/2018]: Update to 8.1.0r36 and DotOS 2.4
[Miscellaneous Android Development] LluisR98:
Reservado: OTROS
[Miscellaneous Android Development] DanipunK1:
Hola, muchas gracias por la rom. Cuales son los bugs que tiene? Funciona todo?
[Miscellaneous Android Development] LluisR98:
Not counting the dotOS bugs with music playback from an SD card, and a slight battery drain.

In principle this is mitigated in the new versions of LineageOS, when I can do the new Zip.

Enviado desde mi Aquaris X Pro mediante Tapatalk
[Miscellaneous Android Development] DanipunK1:
Ok, then, see you soon here, when the battery is a little more stable.

Thanks!
[Miscellaneous Android Development] mtnez.david:
Hola, he estado probando esta ROM esta mañana y en terminos generales funciona muy bien, no me ha dado tiempo a probarla en profundidad, pero hay un fallo recurrente en esta rom, comun a las rom de AymenDe.

This event can be found in the logs:

07-30 12:07:05.782 3128 3362 D DcNetworkAgent: NetworkAgent: DcNetworkAgent: [unwanted]: disconnect apnContext={mApnType=dun mState=CONNECTED mWaitingApns={[[ApnSettingV3] SFR option modem, -1, 20810, websfr, , , , , , 0, dun, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false]} mApnSetting={[ApnSettingV3] SFR option modem, -1, 20810, websfr, , , , , , 0, dun, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false} mReason=connected mDataEnabled=true mDependencyMet=true}
[Miscellaneous Android Development] LluisR98:
Me temo que eso no es un bug como tal... Es un tema un poco complicado. Te comparto enlace:

https://android-review.googlesource.com/c/platform/packages/apps/Settings/+/464023

Enviado desde mi Redmi 5 Plus mediante Tapatalk
[Miscellaneous Android Development] mtnez.david:
Lo se, pero el caso es que no estoy intentando añadir un nuevo punto de acceso o editarlo.

El punto de acceso esta configurado correctamente por defecto para mi operadora tal y como se indica aqui: https://communaute.red-by-sfr.fr/t5/Utiliser-mon-mobile/Configurer-internet-et-MMS/ta-p/404

Por lo tanto el commit que citas no deberia afectarme. Sin embargo unos segundos despues de activar el punto de acceso obtengo el mensaje de error que he mostrado arriba.

Buscando en los logs encuentro esto (que creo que no deberia suceder...):

07-30 12:07:05.782 3128 3362 D DcNetworkAgent: NetworkAgent: DcNetworkAgent: [unwanted]: disconnect apnContext={mApnType=dun mState=CONNECTED mWaitingApns={[[ApnSettingV3] SFR option modem, -1, 20810, websfr, , , , , , 0, dun, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false]} mApnSetting={[ApnSettingV3] SFR option modem, -1, 20810, websfr, , , , , , 0, dun, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false} mReason=connected mDataEnabled=true mDependencyMet=true}
[Miscellaneous Android Development] LluisR98:
Podrías enviarme el log? Envíamelo vía Telegram a [MENTION=8501773]LluisR98[/MENTION], gracias!

Enviado desde mi Redmi 5 Plus mediante Tapatalk
[Miscellaneous Android Development] LluisR98:
Instalar la v2.3, no voy a actualizar más la ROM.

Enviado desde mi Redmi 5 Plus mediante Tapatalk
[Miscellaneous Android Development] ArturoRos:
Problem

Hola, esto no sé si sea bug de la rom o de mi celular pero al mandar un mensaje de voz se escucha muy fuerte el audio, y aparte cuanto intento rotar mi celular de vertical a horizontal en youtube o cualquier otra apk, no responde, tengo que desactivar el modo autorotacion de pantalla para hacerlo manualmente, podrían darme una solución por favor?:(:confused:
[Moto G5S Plus Questions & Answers] mabvmet:
Hi everybody!

I have a problem with my Moto G5s Plus.

I can't get security updates through OTA, the last one that my phone have installed is from December 2017.

When I try to update the phone, it says that the last update is already installed.

Is it posible to install security updates manually?

if yes, Where can I find those files?

Or, How to fix this issue?

What can I do?

My phone details:

Phone Model: Moto G5s Plus (XT1800)

Android: 7.1.1

Software Channel: openmx

Security Patch: December 01 2017

Compilation Number: NPS26.116-61

Base Band: Sanders-LATAM

If any other info about my phone is required, please tell me!

Thanks in advance!
[Moto G5S Plus Questions & Answers] Adi5:
Fastboot and flash newest

But u have branded phone so won't get ony otas....Only fastboot
[Moto G5S Plus Questions & Answers] mabvmet:
All this started because I rooted the phone and then i

I flashed it back. Before the root process I had OTA updates. After the flash I wasn't able to have them by OTA
[Moto G5S Plus Questions & Answers] ____Mdd:
That means you flashed wrong fastboot ROM, that was not meant for your region/country or device model..

Now you have to find correct version of fastboot ROM.

Do you have any backup of stock ROM ?

EDIT: build version NPS26.116-61 was indian/asian update for december, definitely you are on wrong build.
[Moto G5S Plus Questions & Answers] mabvmet:
So, I need the rom for The Americas / LATAM / México.

Does someone know what build/compilation is?
[Moto G5S Plus Questions & Answers] Aptony:
Do you have a backup?
[Moto G5S Plus Questions & Answers] mabvmet:
No :(
[Moto G5S Plus Questions & Answers] Adi5:
26-116-61-8 I guess

U have phone from operator or retail?
[Moto G5S Plus Questions & Answers] mabvmet:
These are the available files for the moto G5s Plus in the firmware.center website, we know that the NPS116-61 is for the indian market... Do you know what market are the other files for?

*Picture included
[Moto G5S Plus Questions & Answers] Aptony:
Maybe someone from Mexico and same software channel but on stock can help you.

Something like this would help.
[Moto G5S Plus Questions & Answers] mabvmet:
I bought it from Amazon and is opened to any carrier...