yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] hlpain:
Just recover xt1766.

Problem in low-quality unlock from sprint.

You need to make a reelock radio and do it unlock via box.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
hello [MENTION=7383447]MotoJunkie01[/MENTION]

Have you had any other information about the failure of the xt1766?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
No news. The only info I can provide is to flash the firmware in the OP using the supplied instructions, and avoiding bootloader.img and gpt.bin (it is safe to flash adspso.bin.) On initial reboot, complete your setup and accept the OTA. If this doesn't fix it, I'm in hopes that Motorola Mobility pushes out an OTA bug fix soon.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
You can certainly downgrade using the instructions and firmware package in the OP. Just avoid flashing gpt.bin and bootloader.img.
[Moto E4 Guides, News, & Discussion] ozmage:
This is the worst OTA update ever my GSM signal took 40 seconds to get it working
[Moto E4 Guides, News, & Discussion] madbat99:
Yeah, I don't think I've taken an update since the September security patch. My device hasn't exploded or been remotely hacked, or anything. I'll probably update to something a little newer soon.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Guys I have an unofficial firmware package I've compiled for the xt1766 SPerry, for stock Android 7.1.1 (Build No. NCQS26.69-64-8). It is a set of partition dumps in .img format which can be flashed via fastboot. I'll try to post the thread by tonight. (Downgrading will be possible after flashing it by simply skipping the bootloader files and the partition table index (gpt.bin). However, as many have pointed out, this incremental update is nothing remarkable, and has even been problematic for some device owners in terms of modem functionality. I would personally recommend that anybody who has not took the OTA to refrain from doing so until the next incremental OTA is pushed out.
[Moto E4 Guides, News, & Discussion] sidgallup:
Ok just downgraded using your package on first post. After the downgrade and first boot, i went directly to flashing a custom ROM, and it isnt working either, however now the error is "" its doesnt detect a simcard installed"i guess this is a hint as to whats wrong with the latest OTA, it is killing the radios, ive heard the no simcard installed was a common error on this model and they patched it a few months ago.

Anyways, now im going to flash your stock package once again, and this time i will take the latest OTA to see if this time it goes through smoothly.

Noticed something strange on fastboot screen, it says Baseband Not Found. any idea on what went wrong?

EDIT: Ok, i ran your package again, and this time i took the latest OTA and rebooted, now the phone showed baseband, after that i flashed a custom ROM and im at square one once again... no service, emergency calls only and if i try to make a call it says airplane mode is activated but obviously it isnt.

Ill try flashing the 05R modem files you posted a few pages back.

EDIT2: No dice, flashed your package on posts #49 and baseband now is 05U, on latest OTA baseband was 05R i believe, and my other Boost E4 which is working fine on GSM has baseband 02E, so does anyone have the flashable files for baseband 02E? or anyone care to tell me how can i extract them from my working phone using TWRP, i could try flashing that old modem version, im thinking theres soemthing wrong with the 05 modems.
[Moto E4 Guides, News, & Discussion] madbat99:
Well of course they want to destroy the ability for your boost branded device to be activated on a gsm network. I would go so far as to call this "intentional." I don't see them pushing an update to fix a CDMA carrier locked device's ability to be used on a gsm network.
[Moto E4 Guides, News, & Discussion] sidgallup:
Yeah, but the strange thing is that a few people here say they had no problems after the OTA update and are still using it on GSM so, either its a bug in the new firmware rendering people's phones unusable, or its a bug in their "fix" that allows some people to still use their phones on a GSM network.
[Moto E4 Guides, News, & Discussion] ozmage:
mine works after the ota but its virgin mobile not boost but any way its sprint
[Moto E4 Guides, News, & Discussion] madbat99:
I was being s little sarcastic. But I may have to let mine go. The screen is turning grey around the edge, like it's separating. Now I've lost touch on right edge. The entire right edge. I have to flip it upside down to hit send on texts. Thinking about the g6 play. Depending on my bills this week. Maybe the e5 play, lol.
[Moto E4 Guides, News, & Discussion] sidgallup:
are you on a custom ROM? how did you unlock the phone? whats the baseband version on it?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Update: while getting the updated firmware package together, and testing on my own device, I believe I've figured out (fingers crossed) the radio bug with the latest OTA update. If so, my updated firmware package should fix any issues with the broken cell radio. I'll keep the thread updated with progress. Some more testing is necessary, but things are looking up.
[Moto E4 Guides, News, & Discussion] ozmage:
im using stock last version last baseband 05R never been unlocked just opened the box pop in a SIM GSM from Viva My Carrier Here In Dominican Republic And Everything Work nice and dandy until today dont know about tomorrow im not Psychic ......

Virgin Mobile

---------- Post added at 05:00 AM ---------- Previous post was at 04:59 AM ----------

So What Causes The Problem ??

---------- Post added at 05:00 AM ---------- Previous post was at 05:00 AM ----------

---------- Post added at 05:06 AM ---------- Previous post was at 05:00 AM ----------

I just made a custom firmware package and went back to -48 Original Stock for the freely in Rom Apn Edit but i keepd the baseband 05R , i did this because when i turn on the device the apn reset itself to the first one on the list and not the one i added with the method i shared before for apn editing and its tedious to start the phone and dont have lte and need everytime go to settings and set the correct apn because cant delete the first one on the list but with -48 is all ok for me and Guess what now the Cellular Signal from the carrier Gets Faster Than Ever i think the problem was on the rom i mean system and oem because now the signal pick up right away just ends booting and the signal from the carrier enters and bang Lte working with the correct Apn :) L
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Yeah, I also believe the issue was due to the OTA update patches to the /oem partition; namely, the SprintDM process and libs, which was killing the radio due to a misnomer in carrier provisioning. With the firmware package I'm compiling, I have allowed the /oem partition patch by the OTA, but I have reverted the SprintDM application, processes and libs back to the pre-OTA configuration. Thus far, this mod appears to be resolving the cell radio issue brought on by the OTA. Since my device was not negatively affected by my initial OTA update to NCQS26.69-64-8, I had to downgrade and upgrade again in an attempt to force the bug onto my xt1766. Sure enough, once I downgraded and then again installed the OTA, my cell radio broke just as other members have reported. A series of before-and-after logcat readings revealed the issue to be /oem related.
[Moto E4 Guides, News, & Discussion] ozmage:
Ok I See I know there was something in there ::}
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
I think I have the fix completed. Soon as my files upload I'll post the thread and link it here.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
hello [MENTION=7383447]MotoJunkie01[/MENTION]

perform the steps indicated ... and I continue with the failure

when dialing * # * # 4636 # * # * indicates the same Voice service: Radio deactivated

fastboot oem fb_mode_set

...

OKAY [ 0.008s]

finished. total time: 0.009s

c:\55>fastboot flash partition gpt.bin

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.005s]

writing 'partition'...

(bootloader) Flashing primary GPT image...

(bootloader) Flashing backup GPT image...

OKAY [ 0.121s]

finished. total time: 0.128s

c:\55>fastboot flash rpm rpm.mbn

target reported max download size of 536870912 bytes

sending 'rpm' (256 KB)...

OKAY [ 0.012s]

writing 'rpm'...

OKAY [ 0.074s]

finished. total time: 0.089s

c:\55>fastboot flash devcfg devcfg.mbn

target reported max download size of 536870912 bytes

sending 'devcfg' (128 KB)...

OKAY [ 0.009s]

writing 'devcfg'...

OKAY [ 0.063s]

finished. total time: 0.074s

c:\55>fastboot flash tz tz.mbn

target reported max download size of 536870912 bytes

sending 'tz' (1792 KB)...

OKAY [ 0.064s]

writing 'tz'...

OKAY [ 0.243s]

finished. total time: 0.309s

c:\55>fastboot flash boot boot.img

target reported max download size of 536870912 bytes

sending 'boot' (16384 KB)...

OKAY [ 0.560s]

writing 'boot'...

(bootloader) Image not signed or corrupt

OKAY [ 0.540s]

finished. total time: 1.102s

c:\55>fastboot flash modem NON-HLOS.img

target reported max download size of 536870912 bytes

sending 'modem' (102400 KB)...

OKAY [ 3.473s]

writing 'modem'...

OKAY [ 2.639s]

finished. total time: 6.114s

c:\55>fastboot erase modemst1

erasing 'modemst1'...

OKAY [ 0.062s]

finished. total time: 0.064s

c:\55>fastboot erase modemst2

erasing 'modemst2'...

OKAY [ 0.062s]

finished. total time: 0.063s

c:\55>fastboot flash fsg fsg.img

target reported max download size of 536870912 bytes

sending 'fsg' (8192 KB)...

OKAY [ 0.280s]

writing 'fsg'...

OKAY [ 0.339s]

finished. total time: 0.620s

c:\55>fastboot flash system system.img

target reported max download size of 536870912 bytes

Invalid sparse file format at header magi

c:\55>fastboot flash oem oem.img

target reported max download size of 536870912 bytes

Invalid sparse file format at header magi

sending sparse 'oem' (504128 KB)...

OKAY [ 18.481s]

writing 'oem'...

OKAY [ 12.916s]

finished. total time: 31.399s

c:\55>fastboot erase DDR

erasing 'DDR'...

OKAY [ 0.008s]

finished. total time: 0.010s

c:\55>fastboot erase carrier

erasing 'carrier'...

OKAY [ 0.124s]

finished. total time: 0.125s

c:\55>fastboot erase userdata

erasing 'userdata'...

OKAY [ 0.251s]

finished. total time: 0.253s

c:\55>fastboot erase cache

erasing 'cache'...

OKAY [ 0.020s]

finished. total time: 0.021s

c:\55>fastboot oem fb_mode_clear

...

OKAY [ 0.006s]

finished. total time: 0.007s

c:\55>fastboot reboot

rebooting...

finished. total time: 0.006s
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
On first boot, after flashing the files, perform a ##72786# network reset. From your flash log, it appears that everything installed normally and without incident. I'm beginning to think your UICC may be corrupt or malfunctioning. Do you have another UICC you could install just to see if the radio will power on? (I realize that a mismatch will occur between the device and the ICCID, but it should work for radio testing purposes).
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION]

the indicated code does not do anything on the phone ... it should not be *
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Ok. So if ##72786# is not triggering the SCRTN reset mode, the device is not seeing your UICC card. Have you cycled your device on and off a couple of times with the card removed?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
You can do a manual network reset by going to Settings>More and selecting Network Settings Reset.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
[MENTION=7383447]MotoJunkie01[/MENTION]

I just did it 3 times and the same thing I still do with the failure ... Can you explain why this fails after updating? What has Motorola done about it?
[Moto E4 Guides, News, & Discussion] sidgallup:
Ok im downloading this as a type. As a side note, something else i noticed today when i was playing with settings and radio modes, i noticed the IMEI was just a long string of 0s ending with a 1 like this 000000000000001, baseband was fine and updated to the latest 05R build.
[Moto E4 Guides, News, & Discussion] carlosvinuezap:
I did the network restoration and it's the same, nothing has changed with the new flash
[Moto E4 Guides, News, & Discussion] sidgallup:
Same here, still no radio signal, however i noticed that the baseband shows as 05E and from the instructions on your latest package it should be 05R. Is this a typo?

EDIT: ok this is weird, in the bootloader baseband shows as 05R, but in systems settings> about phone it shows as 05E. WTF

EDIT2: I think i know what im doing wrong, after flashing your latest package i flashed Resurrection Remix and i think that ROM includes an older modem.img and thats why it was showing build 05E on system settings, so i just reflashed latest package and now on stock ROM it is showing latest baseband build 05R.

Now phone is saying invalid simcard since my phonje isnt unlocked on stock firmware but now when i try to make a call it says voice calls are unsupported, previously it said turn airplane mode off so this means radio is actually activated, problem is here in Mexico we dont have any CDMA carriers so i cant find any signal when i run the "search networks" option.

The only way i could be absolutely sure radio is now working is by flashing a custom ROM with GSM enabled, and without an older modem version so the phone can stay on the latest 05R.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Strange bug indeed. Just like the OTA itself, this is fixing some devices but not others. I've run out of ideas on my end. Hopefully Motorola will roll out an OTA bug fix soon, as many device owners are being adversely affected by the latest update.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
On the baseband version, the latest OTA updated it to 05R. The baseband from the previous firmware build, NCQS26.69-64-5 ended in 03R. No typo in instructions. 05R is correct.
[Moto E4 Guides, News, & Discussion] sidgallup:
Got it. Its really strange how when i flash a custom ROM baseband changes to 05E on both Lineage and RRemix, on bootloader it stays at 05R, but when phone boots it changes to 05E and theres no service, radio off.

On stock ROM after flashing your latest package, baseband stays the same 05R on bootloader and system settings, but phone says invalid simcard since my phone isnt unlocked.

And to think all i needed to do was not updating my phone, always liked Motorola and ive been using Moto phones since the first Moto X, oh well, guess thats what happens when a company is sold to Asia and quality control goes to the ****ter.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
That's also the odd part -- everything that was changed by the OTA which is relevant to the radio can be undone. All patches can be removed and /system, /boot, /recovery, /modem and /fsg can be reverted back to pre-OTA state. Yet that doesn't fix the problem. This is probably extremely simple and we are all overlooking it. I just have that feeling.
[Moto E4 Guides, News, & Discussion] madbat99:
Gsm unlock was just side effect of custom roms. I don't think it was intended. And it's reading different between system and bootloader for modem, likely, because of buildprop edits. Just changing what's displayed in system settings leads me to think that.

The device trees for the custom roms were never perfected, a few ppl have tried to update them further. But they were common trees for a few devices with the same board and are, likely, buggy.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Contrary to popular belief, the majority of Motorola phones and tablets are not manufactured in Asia, nor is Motorola Mobility LLC owned by a Chinese or Asian company -- at least not by a majority share. Most Moto devices are now manufactured out of the Chicago, Illinois branch of the company. While the Chinese owned company Lenovo did technically purchase Motorola from Google in 2014, two more spin-offs occurred from that deal: Motorola Solutions, Inc., and Motorola Mobility, LLC. While Lenovo is the 49% owner of Motorola Mobility, LLC, the true 51% owner and shareholder is the US based LLC entity itself. There have been so many mergers, acquisitions and piece-mealing of Motorola over the last 15 years, even top execs are sometimes unsure what will happen next.
[Moto E4 Guides, News, & Discussion] ozmage:
There Is Something Really Wrong With this Ota i Flashed The New Lineage OS Build Of Today And Now the Modem its Broken ,

I have no signal here ......

---------- Post added at 01:58 AM ---------- Previous post was at 01:21 AM ----------

No Service And The simcard its detected And the Carrier Apns But no Service
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Yeah you guys are not fu@king kidding. This is the most perplexing and puzzling bug I've ever seen brought on by an OTA -- period. Sure, OTAs cause bugs all the time on various devices and OEMs. But this is the first and only bug I've ever encountered that cannot be fixed by simply reverting to pre-OTA state. A thought on that however -- there are three partitions that cannot be downgraded/reverted due to the OTA install -- /tz, /devcfg, and /rpm. Since /rpm is the primary bootloader, we can rule it out. The /tz (Trust Zone) partition is also bootloader related. The /devcfg (device config) partition is classified by Motorola. No clue what it does or why it's there, but it was flashed by the OTA, and since it's not safe to downgrade it, the problem has to be there. All other partitions can either be reverted back to the prior build or are insignificant bootloader partitions. While I did find a bug in /oem, in the SprintDM app and lib, fixing the bug is not fixing you guys' radios. If somebody wants to take one for the team and risk a brick, we can try to downgrade /devcfg and see if the radio issue is fixed.
[Moto E4 Guides, News, & Discussion] ozmage:
I Think This Was Made On Purpose To Disable GSM UNLOCK Or Any Unlock ON CUSTOM ROMS , Sprint Sucks

After Going Back To Stock Radio Is ON Again , What We do Now , No Way To use Custom Roms Now . This Suxx........
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
[MENTION=8371146]ozmage[/MENTION], the Sprint xt1766 is not SIM locked. At least not in the traditional sense. The stock ROM restricts GSM functionality of course, but once a custom ROM is flashed, the device will recognize a GSM SIM. From there you must set your network mode, APNs, etc. There is a thread on GSM support for the xt1766 here on the device forum. I can only confirm AT&T functionality, but any GSM provider should work.
[Moto E4 Guides, News, & Discussion] ozmage:
Not Working Anymore As You Can See On The Screenshots After Flash/take LAst Ota Everything was ok for me because i was using the stock but i wanted to try last LOS with august android security patches , never noticed that until today after the release of the last build of lineageos i flashed and not radio on for me well i flashed crdroid too and radio is off too and everything was working fine before this hell. :eek:
[Moto E4 Guides, News, & Discussion] ozmage:
Hey does this menu works on custom roms?

*#*#4636#*#*

on this menu radio can be turned on/off

my questions is is there something similar on lineageOS?

---------- Post added at 12:54 PM ---------- Previous post was at 11:57 AM ----------

UPDATE: YEs it work but the radio switch its a placebo cant turn it on the Voice Radio this is really wrong ......
[Moto E4 Guides, News, & Discussion] ozmage:
https://xdaforums.com/moto-e4/moto-...blankflash-motorola-moto-e4-qualcomm-t3830983 BlankFlash for our phone maybe now someone wants to flash {devcfg}
[Moto E4 Guides, News, & Discussion] sidgallup:
So you were on stock ROM with the latest OTA and GSM signal was working fine, then you flashed custom ROM, and on boot now it doesnt get GSM signal and says radio off?

Now you went back to stock and signal is back. maybe the problem is on the actual custom ROM's package? i noticed that on latest package from a few pages back, phone's radio was actually ON but since my phone isnt unlocked on stock ROM, i couldnt get GSM signal, and theres a mismatch on the baseband version build on bootloader and system settings, latest baseband should be 05R, but on custom ROM it shows as 05E, theres has to be something in the custom ROM package causing the radio to die and thats why baseband shows as a different build version.
[Moto E4 Guides, News, & Discussion] ozmage:
yes if i flash back stock everything just work fine i have a backup on twrp i just restore it and everything works on stock.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Ahhh. I see what you're saying. One thing is nearly 100% for certain -- the problem has to lie within the /devcfg partition.
[Moto E4 Guides, News, & Discussion] ozmage:
Im Trying to downgrade the modem baseband i have flashed 2 diff modems versions and the baseband still 05R .......
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
The bootloader version misnomer is a fairly common occurrence, dating all the way back to the 1st Gen Moto E and Moto G. It is also very common for AP Fastboot mode to show the baseband version as "Unknown" after flashing /modem, /fsg and /ssd.
[Moto E4 Guides, News, & Discussion] ozmage:
so no way to downgrade the baseband now ? just for testing
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Sure you can downgrade, but device info will not necessarily reflect the correct baseband version. As long as Fastboot is giving you a pass, you have downgraded, regardless of the baseband version you are seeing.
[Moto E4 Guides, News, & Discussion] ozmage:
ok so is downgrading but keeps saying 05r this means it downgraded ok , but dont work .... no service imei null 0 voice no sim card those are the messages i receive but when i flash my backup of the modem 05R all goes to normal way but only on stock not on lineageos or crdroid something its missing that needs to be flashed along with the old modem to reflect it as 03R or whatever

.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Are you flashing both the /modem and the /fsg partitions?
[Moto E4 Guides, News, & Discussion] ozmage:
Yes
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
This phone gets stranger every day. Are you erasing modemst1, modemst2, and DDR?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Hey [MENTION=8371146]ozmage[/MENTION], are you erasing modemst1, modemst2 and DDR when you flash the baseband?Also, who is your provider? Boost?
[Moto E4 Guides, News, & Discussion] ozmage:
im only erasing modemst1, modemst2 but not DDR

im here in dominican republic my carrier its viva but my phone its sprint virgin mobile
[Moto E4 Guides, News, & Discussion] sidgallup:
I did try to downgrade the moden by flashing both files and ereasing what MotoJunkie says, and i ended up with an unknown baseband, and IMEI was corrupt and showing as a string of onlu 0s, the only fix was to flash full package from this thread.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Ok. Let s try to configure your radio firmware to the base carrier. Try:

fastboot oem fb_mode_set

fastboot oem config fsg-id sprint

fastboot oem config carrier sprint

fastboot oem fb_mode_clear

Then reboot and check radio.
[Moto E4 Guides, News, & Discussion] ozmage:
none of that work nothing work
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Somebody is going to have to try downgrading the /devcfg partition.