friends, I have xt1640, after it upgraded to android 8.1, the cell phone ran out of network service, I downgraded, and nothing ...
the mobile was working perfectly ... after it updated via OTA, for 8.1 it was out of service, the baseband is ok, when I'm going to call it it says to disable the airplane modeWhat does your baseband report in Settings>About phone? Do you see your IMEI in Settings as well?
A side note, if you've downgraded, do not use stock OTA updates. You'll hard brick your device else, and the fix is expensive.
Hmm, that's odd - did you try to re-flash the Oreo stock firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138the mobile was working perfectly ... after it updated via OTA, for 8.1 it was out of service, the baseband is ok, when I'm going to call it it says to disable the airplane mode
I did not delete the modemst, the imei is showing up !! I was researching, and I saw that there are some people with the same problem ...Hmm, that's odd - did you try to re-flash the Oreo stock firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
When you downgraded, did you erase modemst1 and modemst2? Have you verified your IMEI is present and your SIM card is still working (i.e. try it in another device) and you do not have network issues?
I'm not sure if your Oreo modemst would be working with your Nougat baseband if you're still downgraded. You might like to backup your modemst with Lyuu's TWRP (back up your EFS) and then try erasing modemst. The Oreo OTA update would have erased the modemst1/modemst2 (EFS) as part of its update.I did not delete the modemst, the imei is showing up !! I was researching, and I saw that there are some people with the same problem ...
Okay, I installed twrp, to try to backup efs, but the partition does not appear to back up ... could you help me?I'm not sure if your Oreo modemst would be working with your Nougat baseband if you're still downgraded. You might like to backup your modemst with Lyuu's TWRP (back up your EFS) and then try erasing modemst. The Oreo OTA update would have erased the modemst1/modemst2 (EFS) as part of its update.
Did you flash Lyuu's TWRP as I mentioned? https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Other TWRP recoveries may not be able to back up this partition.Okay, I installed twrp, to try to backup efs, but the partition does not appear to back up ... could you help me?
I'm using google translate. Brazil
Okay, I'll do it tomorrow morning and post the result, so I backup efs, I delete the modemst partition, and install the 8.1 stockrom, right? I do not do it now, because of the schedule, it's already late here, but thanks for your attention,Did you flash Lyuu's TWRP as I mentioned? https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Other TWRP recoveries may not be able to back up this partition.
Yeah - so the plan is:Okay, I'll do it tomorrow morning and post the result, so I backup efs, I delete the modemst partition, and install the 8.1 stockrom, right? I do not do it now, because of the schedule, it's already late here, but thanks for your attention,
friend I did what you asked me, and it did not work, I sent you a print for you to seeYeah - so the plan is:
1)Backup your EFS (though it might be already damaged, might as well keep it safe).
2)Erase modemst1/modemst2 via fastboot. Reboot. Test if SIM service is working. Check IMEI and baseband (baseband should be reporting ATHENE_BRAZIL_DSDS_CUST, and ending in 77R if on Oreo, .62.02R if on April 2018 stock Nougat).
3)If device is still not in service, flash stock Oreo firmware. You do not need to re-lock, so you could omit the fastboot OEM lock begin commands to avoid locking the bootloader.
Your baseband, modern or fsg is corrupted, it is reporting DFLT_FSG as the suffix - for your device, it should be reporting ATHENE_BRAZIL_DSDS_CUST or similar. Your baseband clearly is not okay, was it DFLT_FSG also when you updated to Oreo via OTA?friend I did what you asked me, and it did not work, I sent you a print for you to see
https://uploaddeimagens.com.br/imagens/g4-jpg-f5886a19-b5f6-4d4a-83b7-bb6b77bde02c
was updated on the 28th, how can I recover ??Your baseband, modern or fsg is corrupted, it is reporting DFLT_FSG as the suffix - for your device, it should be reporting ATHENE_BRAZIL_DSDS_CUST or similar. Your baseband clearly is not okay, was it DFLT_FSG also when you updated to Oreo via OTA?
You could try this https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?was updated on the 28th, how can I recover ??
Brother, you saved me ... Thank you.I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Can I do this now because recently recovered my phone 8.1.0I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Password please...I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
This file asking password bro...please tell meI am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
This file extract with winRAR.it showing all errorsI am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
I can't extract itCan I do this now because recently recovered my phone 8.1.0
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Password please...
---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------
This file asking password bro...please tell me
---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------
This file extract with winRAR.it showing all errors
And extract the file 7zip aslo all files error
Bro
1) you should be able to use this procedure, this thread you're replying in had a similar scenario to you.Can I do this now because recently recovered my phone 8.1.0
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Password please...
---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------
This file asking password bro...please tell me
---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------
This file extract with winRAR.it showing all errors
And extract the file 7zip aslo all files error
Bro
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
I can't extract it
1 - LATAM1) you should be able to use this procedure, this thread you're replying in had a similar scenario to you.
2) make sure the firmware you've downloaded is the correct size. I've just checked and it's 893 MB in size. The first download I tried failed towards the end.
3)I used the app 7-zipper, with the password lenovo-forums.ru and it seemed to work. Not sure why you're having trouble extracting the files, I'd try to redownload the firmware. I don't know if the script on its own works or if you need the full firmware.
Also, please note these are not real time forums, repeatedly posting will not necessarily make a member post any faster. I get you're frustrated by your device only partially working, please be patient.
Was your device booted to fastboot for this procedure, as requested by the script? Does your device properly communicate with your computer in fastboot (i.e. if you type fastboot devices into an ADB terminal, does your device respond with its serial number)?1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - QUIT
please select region : 2
A - Retail APAC
B - Retail India
C - Quit
Please select carrier : B
Waiting for fastboot enumeration...
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Bro..:crying::crying: