Related
OK, so I have a Moto X Developer Edition (rooted, stock 4.4.2) that I recently requested a replacement for from Motorola. I took a full Nandroid backup on the old phone and restored it on the new one. After ironing out the initial kinks on the original phone (disabling Xposed and removing PIN) and trying again, the new phone looked to be at 100% until I tried setting my PIN up again. Whenever I try to go to the Security settings, I get an "Unfortunately, Settings has stopped" message. One suggestion I found was to re-flash system.img, which I did to no avail. This page gives a way to fix the issue by fixing permissions of a file, but it seems to be specific to the Nexus 4 as the Moto X does not have the file specified (or at least I can't find it).
The only other potential means to fixing this that I can find is to wipe the data partition, but that means I can't use my Nandroid backup, which means more work I'd like to prevent if possible. Of course, I still have both phone for a limited time, so if there's something I can do on the original phone that will make my backup usable, that would also work.
Thanks!
If they are both rooted etc backup everything with Titanium backup then restore to the new phone everything except settings related apps.
Not saying that's the fix but it's definitely what I would try next. If it doesn't work the first time. Factory reset the phone, wipe caches, confirm settings works then restore again. If that doesn't work let me know, we'll troubleshoot some more.
That error is likely related to a mismatch between /system and the modem/radio version.
I am guessing you restored the 4.4.2 nandroid to the phone while it was running 4.2.2. This will not flash the modem, but you can manually flash the corresponding modem for your build of android using fastboot.
Ctrl-Freak said:
That error is likely related to a mismatch between /system and the modem/radio version.
I am guessing you restored the 4.4.2 nandroid to the phone while it was running 4.2.2. This will not flash the modem, but you can manually flash the corresponding modem for your build of android using fastboot.
Click to expand...
Click to collapse
Yeah, that's exactly what I did. Where can I get the modem/radio image file? I have the zip from the latest version but I don't see it in there.
Platypus222 said:
Yeah, that's exactly what I did. Where can I get the modem/radio image file? I have the zip from the latest version but I don't see it in there.
Click to expand...
Click to collapse
The modem is called NON-HLOS.bin. Also, I believe that "fsb.mbn" is related to the modem, and I update mine whenever I update the modem.
Here are the commands for motorola's fastboot (do not use a generic fastboot exe):
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Ctrl-Freak said:
The modem is called NON-HLOS.bin. Also, I believe that "fsb.mbn" is related to the modem, and I update mine whenever I update the modem.
Here are the commands for motorola's fastboot (do not use a generic fastboot exe):
Click to expand...
Click to collapse
Thank you! So far as I can tell that worked perfectly!
I was using rooted stock rom lex526. I installed shortcut master lite apk though play store. While browsing though secret code in it, I somehow messed up mbn test configurations .
Now I can only use 4g sim only in either sim slot. Other Vodafone sim is not detecting in any sim slot .
I tried flashing firmware through twrp by Rishabh Rao . But after 15℅ phone reboots. So I guess I can't flash firmware through twrp.
Then i get back to stock by flashing original stock rom , but still I can only use one 4g sim .
If anyone can please help me out . And guide me how make both sim working.
Thanks in advance.
https://drive.google.com/folderview?id=0B2O8PS66A_T-a05FQUEyRFNWa1U
Shall I flash baseband ? Which and how ? Please guide me.
I am using 5.8. 019s rom.
Wipe data system cache
Flash any ROM (eUI preferred)
Flash baseband, flash modem
superGuyAdi said:
Wipe data system cache
Flash any ROM (eUI preferred)
Flash baseband, flash modem
Click to expand...
Click to collapse
Can you please explain more in detail how to flash baseband and modem .
I have stock rom downloaded from leeco official website as well as twrp back with firmware. Though I tried restoring backup but it doesn't change anything .
While searching for Network it shows 2g ,3g 4g ranges only if 4g Jio sim present , second sims simply not showing up at all.
Please check Google drive image attached in first post for more information.
http://forum.le.com/in/index.php?th...king-hard-bricked-dead-bricked-devices.17253/
Try following the post worked for me when I hard bricked my le 2, but be cautious and follow steps correctly
Went to fastboot
Fastboot erase modemst1
Fastboot erase modemst2
Reboot twice
And boom ..
Both sim showed up ..working normally.
Moto G5s Plus Xt1802 does not work!
My most Moto G5s had a loop problem. It would call itself, switch off and restart itself. It had a own life.
1
Then I got the bootloader after tried several methods. I got the code with a Motorola support.
2
I cannot root! Keep trying, but no success.
3
I already tried to use GZOSP, Liquid Remix, Pixel, Zero, and even return to Original Stock, but I can not. I tried via TWRP or via Prompt ADB.
4
If any ROM is installed, in the first start, this message appears: the password is correct, but unfortunately your data is corrupted. The message is the same, if I type correct password or not.
5.
If an installation is successful, the IMEIs disappear and I cant use the simcard.
The file system is as ext4, but sometimes it appears as e2fs. Could this be wrong? How do I setup this, can you install one of these cost roms? How to mount it correctly?
How should I proceed?
So, I ask for the help of these master experts, because I still can not solve it. Since then I cant use the device, cant enjoy anything of it.
Best Regards, guys!
Always take a backup using twrp before doing anything, keep it safe.
First Make sure that you are using latest TWRP 64 bit recovery.
Download latest Custom ROM and flash it..
For password problem..Wipe Data.
Now check that your IMEI number is OK..and you are getting signal.(if there is no 4G signal.. reply here)
Caution: While flashing Stock Don't use modem erase Commands , otherwise IMEI will be Null..skip these.
If possible take a backup of efs and persist partition..will be helpful in case of emergency.
Avoid volte fix.
crazytech2 said:
Always take a backup using twrp before doing anything, keep it safe.
First Make sure that you are using latest TWRP 64 bit recovery.
Download latest Custom ROM and flash it..
For password problem..Wipe Data.
Now check that your IMEI number is OK..and you are getting signal.(if there is no 4G signal.. reply here)
Caution: While flashing Stock Don't use modem erase Commands , otherwise IMEI will be Null..skip these.
If possible take a backup of efs and persist partition..will be helpful in case of emergency.
Avoid volte fix.
Click to expand...
Click to collapse
Ok, Crazytech,
Your tips have helped a lot.
I installed and am testing Frankenrom.
I noticed that the LTE 4G is not operating, only the 3G +
mdr1982 said:
Ok, Crazytech,
Your tips have helped a lot.
I installed and am testing Frankenrom.
I noticed that the LTE 4G is not operating, only the 3G +
Click to expand...
Click to collapse
Is your IMEI number is visible..*#06#
If yes..Do one more thing..
Restart your phone into Bootloader mode..
Pass these two Commands..
fastboot erase modemst1
fastboot erase modemst2
Reboot Now..and Check 4G signal..!
crazytech2 said:
Is your IMEI number is visible..*#06#
If yes..Do one more thing..
Restart your phone into Bootloader mode..
Pass these two Commands..
fastboot erase modemst1
fastboot erase modemst2
Reboot Now..and Check 4G signal..!
Click to expand...
Click to collapse
Great !!!!
Now LTE 4G works as well.
Sincere thanks.
Someone can remove the message: Your device has been unlocked and can not be trusted. To learn more, visit: motorola.com/unlockbootloader?
mdr1982 said:
Great !!!!
Now LTE 4G works as well.
Sincere thanks.
Someone can remove the message: Your device has been unlocked and can not be trusted. To learn more, visit: motorola.com/unlockbootloader?
Click to expand...
Click to collapse
Now...if you want to flash stock again skip modem erase Commands.. always..!!
Otherswise Null IMEI will be there..!!
What about volte..right now..??
crazytech2 said:
Now...if you want to flash stock again skip modem erase Commands.. always..!!
Otherswise Null IMEI will be there..!!
What about volte..right now..??
Click to expand...
Click to collapse
Well,
I think this Frankenrom ROM has not, I have not seen it yet.
I am paying attention to Motorola's message , to remove this.
mdr1982 said:
Well,
I think this Frankenrom ROM has not, I have not seen it yet.
I am paying attention to Motorola's message , to remove this.
Click to expand...
Click to collapse
Flash a Custom logo.bin..this message will be hidden..no more visibility..!!
crazytech2 said:
Flash a Custom logo.bin..this message will be hidden..no more visibility..!!
Click to expand...
Click to collapse
Im Trying, but no success:
"flashboot flash logo logo.bin"
dont work
mdr1982 said:
Im Trying, but no success:
"flashboot flash logo logo.bin"
dont work
Click to expand...
Click to collapse
Right now..on which rom are you trying this. ?
Check this may be helpful..
https://forum.xda-developers.com/moto-g5s-plus/themes/logo-bin-nice-bootloader-images-t3692228
https://forum.xda-developers.com/mo...ove-unlocked-bootloader-message-moto-t3672419
crazytech2 said:
Right now..on which rom are you trying this. ?
Check this may be helpful..
https://forum.xda-developers.com/moto-g5s-plus/themes/logo-bin-nice-bootloader-images-t3692228
https://forum.xda-developers.com/mo...ove-unlocked-bootloader-message-moto-t3672419
Click to expand...
Click to collapse
Solved logo problem.
I used Motorola Logo Maker and created my own logo
And then flash with fastboot.
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667
mdr1982 said:
Solved logo problem.
I used Motorola Logo Maker and created my own logo
And then flash with fastboot.
https://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667
Click to expand...
Click to collapse
Fantastic..!
Enjoy..!!
Some custom ROMs have some password even if u don't put them ..... So flash the lock fixer zip from twrp
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?] EDIT: NO. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted. EDIT: I think I didn't wait long enough.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick). EDIT: TWRP backup does not work. I'll eventually file a bug about this.
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway? EDIT: Nobody ever got back to me about this.
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible? EDIT: The ext4 partition must have been made with slightly different options that allowed everything to be packed into the tiny partition
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone? EDIT: I may have flashed to _b instead of _a. In any case I was later able to fix this by flashing the newer firmware quoted below.
SojPapus said:
Hey, sorry if this information is posted elsewhere, I haven't been able to find it with any google or forum searches. I have an Android One moto x4, on google Fi. I've unlocked the bootloader, and rooted the phone (with magisk). Before doing all this (before rooting, after unlocking), I had used TWRP's backup function.
I decided to try to get the 8.1 update [side question: I was only offered OPW28.1; would OPW28.2 have been offered to me without first updating to 28.1?]. I know that I need to remove root to successfully update the phone, so I used the in-app uninstall function of Magisk, and then rebooted the phone. I tried to run the system update afterwards---and it failed, about halfway through installing. Since this point I cannot get Android to even see there is OPW28.1 , much less OPW28.2. So, I think "That's cool. I have a backup, I'll just restore from that." So, I made another backup, and then tried to restore just the system and system_image (in TWRP---this was probably a mistake). It didn't work---and I don't remember if the phone even booted.
So I tried to restore the full backup---and it failed restoring the "bluetooth" partition: it runs out of space (!?)[1]. The phone did not appear to be able to boot after that (it spent a long time at the "Android One" screen, with the color bar oscillating). The good news for me is that I tried a factory reset (all data, I think the option was "user data and customization", the third option), and the phone starts (hooray, no brick).
Rebooting the phone, it looks totally new (but it remembered my google account name ?? what ??). However, it still isn't letting me update (still isn't seeing the new version is system updates). I tried the dialing "*#*#checkin#*#*" and it says it succeeds, but even after a reboot it doesn't do anything. I cannot find a "google services framework" (or motorola update services) to clear data on in the apps list, but shouldn't that have been reset in both the factory reset and my failed restore attempt anyway?
Sorry for the length of this, I'd really appreciate any input.
[1] adb shell during the TWRP restore session, "tar_extract_file(): failed to extract /bt_firmware//image/crbtfw21.tlv !!!". df /bt_firmware shows 100% use. Why would that even be possible?
EDIT: I downloaded the original Fi firmware from firmware.center /firmware/Motorola/Moto%20X4/Stock/, and flashed the bluetooth partition (after confirming that the the files in that image are bit identical to the backup I made). Bluetooth still doesn't seem to be turning on. Should I just reflash everything? Can I restore my data partition and expect a functional phone?
Click to expand...
Click to collapse
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
ptn107 said:
Go here: androidfilehost.com /?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Thank you. Do you happen to know how I can go about checking the cryptographic signatures for these downloads? EDIT: I never managed to do this. I'm considering re-locking my bootloader, which should presumably allow this guarantee to be made. But then I risk bricking the phone. I'm not afraid to go digging around a little bit in the images (I can mount an ext4 filesystem or run simg2img no problem). EDIT: I did go mucking around, and I don't have the public key to go about verifying the bootloader. So that's probably a dead-end.
Also, is resetting user data after every upgrade just SOP when running rooted? Is there some approach to making that less painful that I don't know about? EDIT: NO CLUE. Nobody helped me with this. Also, TWRP doesn't seem to support encryption after the upgrade, so I wasn't able to try restoring from my backup. EDIT ON EDIT: Restoring a TWRP data backup went fine. However, right now TWRP 3.2.1-1 isn't supporting decryption for OPW28.1, so that's another complication. (Just remove the password, and everything seems to work)
EDIT: I've tracked down otacert.zip (containing ota.x509.pem), the key presumably used to sign the OTAs, but the images on firmware.center and androidfilehost don't seem to be signed. Were those signatures stripped out? Is it possible for me to capture those OTA directly (my phone should be receiving these)? My question still stands: how do I force my phone to download the new OTA. I'll deal with flashing it once I can get my hands on it. ANOTHER EDIT: I was able to capture the OTA, but it still isn't installing.
EDIT2: I think I've got a better link.
ptn107 said:
Go here: https://androidfilehost.com/?w=files&flid=229118
Download PAYTON_FI_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Flash it and you're good to go. Definitely wipe your userdata as part of the instructions.
Click to expand...
Click to collapse
Flash how? From TWRP?
edufur said:
Flash how? From TWRP?
Click to expand...
Click to collapse
from fastboot
TWRP will be removed upon flashing.
ptn107 said:
from fastboot
TWRP will be removed upon flashing.
Click to expand...
Click to collapse
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
This is not an update zip or rom that can be flashed from TWRP. You will have to do the following:
1. Flash this firmware via fastboot which gets you 8.1.0 w/ April update. (Note: you will lose TWRP and root)
2. Boot the new stock 8.1.0 and take the may security update which will be offered almost immediately.
3. Once on 8.1.0 may update you may reinstall TWRP and a root solution. Be aware that if you do then OTAs from here on won't work. So if you want the June update you will have to re-flash stock 8.1.0 and start over.
Flashing stock will automatically remove whatever twrp or root you have.
To flash this firmware:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash logo logo.bin
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
ptn107 said:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
edufur said:
So here is my situation. I already rooted and TWRPd my stock phone when it was Oreo 8.0
I would like to get it up to current but stay rooted and TWRPd. Is it possible to flash it from TWRP and then immediatly reflash TWRP and ROOT?
If not, when is the right method in fastboot to go back to stock (keeping in mind I have TWRP right now along with root)....?
Click to expand...
Click to collapse
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
SojPapus said:
Is there a reason you are suggesting reflashing the partition table? That would seem to expose a flasher to more risk that needed.
Granted, I'm not able to OTA to OPW28.2. But the android update engine doesn't reflash the partition table, as far as I can tell.
Could you let me know if you are able to OTA to OPW28.2 afterwards? I was not able to after reflashing.
Click to expand...
Click to collapse
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
edufur said:
Well, now I am afraid to flash since there is a question as to why the partition table was recommended. I almost want to hold out for an official flash to stock tool from motorola.
Click to expand...
Click to collapse
I had no problem getting the 28.1 flashable firmware (cited earlier) working on my phone. I would be sure to only flash to the currently disabled slot--and I'd also be sure to backup the data partition before-hand (and move it off-phone). If you're not touching your active slot, there really shouldn't be any way to mess up the phone (just make sure you're able to get into fastboot with both slots first). If something goes wrong, you can just reset the active slot to the old one.
28.1 doesn't have functioning ADB, so you might also consider setting up Termux and an ssh server on the phone so you can still get a command line on it if needed.
Hello,
i have had couple issues so here are my findings, most of them are already nicely described in many topics.
Bricked phone?
For me worked QFIL version 2.0.0.5, using the installer, by the "portable version" errors can be generated:
A nice video tutorial how to use QFIL and restore the image, QFIL and QUALCOMM driver included:
https://www.techpoison.in/2017/12/how-to-flash-letv-le-2-x526-stock.html
To enter the "flash" mode: Press and hold at the same time VOLUME UP, DOWN, POWER for like 10 seconds until you see that the device manager recognized new "hardware". For a detailed tutorial plase follow the video tutorial in the above link.
Should you have problems during the flash process, disconnects and so on, try to use USB 2.0 port.
Version 13s will be restored, please download thee X526 restore image from the Unbrick section or the Indian sparse image from the link above.
Baseband issues after restore / general baseband issues:
After restore "unknown baseband"? Just reset the factory settings on the 13s and let it reboot couple times, it will reboot automatically each 2-3 minutes - let it reboot after the restore 3-4 times. Afterwards copy the stock 21s to internal storage and rename it to update.zip, go to settings,system update and select local update, it should reboot automatically. Its possible that you will get an error message after the 1st reboot - APK not found. Reboot it to OS and delete the update.zip from the internal storage, maybe its not necessary to delete it, but i did it and copied it back, selected local update and voila system updated to 21s, my baseband was back and sims were "fully" functional, 4g/LTE didnt work - baseband was MPSS.TA.2.1.C7-68083.
"I tried to reflash back the stock version using TWRP, stock recovery and also the chinesse TWRP - didnt work at all. "
4g/LTE issues, only 3g works (tested in EUROPE)?
I have flashed all of the modems, bootloaders, different ROMs but it didnt help at all. So i rebooted the phone to fastboot and using the ADB minimal from the CMD i erased both modems, please be sure you have the package of your phone with both IMEIs, in some cases its not necesssary. WCDMA 3G worked fine, i had only issues with 4g/LTE.
IMEI TOOL + drivers link:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
Imei restore on EUI and other ROMs:
https://www.gizmochina.com/2017/02/17/leeco-letv-imei-repair-qualcomm-models/
Commands to erase the modems: fastboot erase modemst1 and modemst2. I did it on 21s and reflashed the phone using QFIL back to 13s and both sims were already fully functional and 4g/LTE too.
If you do not see any IMEI use the Qualcom Imei Restore application - unbrick section, baseband was back, but i just had to restore the IMEIs, but i saw it only on MIUI 10 8.8.9 global - on MIUI enable the diag port using MINIMAL ADB from the commandline:
MIUI is prerooted, so there shouldnt be issues with root privileges.
Commandline - minimal adb:
adb shell
su
setprop sys.usb.config diag,adb
and run the IMEI restore tool.
In device manager you should see the qualcomm diag port - if you need the qualcomm driver please see the unbrick section.
Before i also tried to type in the dialer *#*#4636#*#* and tried to change the network manually, didnt help at all, tried like 3 sim cards from various operators here supporting 4g with a good coverage.
My phone is fully functional now and 4g/LTE works perfectly.
During all my tests, flashing and so on, if you have issues with a bootloop /custom rom/ and you have flashed already different modems = for me worked the 21s bootloader + modem, fixed most of the bootloops.
Link 21s bootloader + modem:
https://drive.google.com/file/d/0B_RkWxhSoWNLWmJJYmFxTGxlMHM/view
Sorry for my bad english, i am not a native speaker All the links are not mine.
ok ... first of alll ....thank for your effort to explain..........
i have tryed most of your solution on my leeco le 2 X526 version and didn't work for me to have a stable 4G signal on my digi mobil carrier from Europe (signal is dies inside house) ......but ...... can you please be a little more precise ?
//// you say that i should restore 13S stock version , take care of my IMEIs , install version modem MPSS.TA.2.1.c7-00008-8976_GEN_PACK-1.64611.1.68083.1 (your download with (TWRP ycjeson or 3.2.1.0) or fastboot flash modem non-hlos.bin if i have custom rom -RR 6.0 my case as a first try) .....and then remain on eui 13S or custom rom (miui version ??? . or other ) ?
perhaps is no need a step by step ....... but .... still ........ with your help .....maybe will be a real solution ...... thank you in advance .