Related
Can any one provide the stock Single Sim modem file.I need to enable single sim in Dual sim
I have European xt1562
https://www.dropbox.com/s/zv8k5zqj2yo3qhw/modem.bin?dl=0
sjaakd said:
I have European xt1562
https://www.dropbox.com/s/zv8k5zqj2yo3qhw/modem.bin?dl=0
Click to expand...
Click to collapse
Is ur model single sim
anadarco7 said:
Is ur model single sim
Click to expand...
Click to collapse
Yes it is
sjaakd said:
Yes it is
Click to expand...
Click to collapse
Thanks
Make sure to backup and then erase the two modem data partitions as well. You can find the fastboot commands in the XML of the firmware packages.
Without behaviour might be not what you are looking for...
I worked for me thanks
Modem file for dual sim
Can anyone please share modem file for dual sim model as I've accidentally selected radio band as USA and hence won't get the network in sim slot 1. Also, if possible, please share link to a step by step tutorial as I'm a novice. Also plz tell me if flashing is possible without using a pc and will the warranty of the phone get void. A prompt response will be highly appreciated.
Thanks
I think Flashify can flash without an external device BUT having the OS (Android) running with all the options for locks and alarms would scare me.
I do _think_ that flashing original Motorola signed binaries will not void anything, to be more precise: With a locked bootloader such procedure should be impossible.
Before you flash a baseband (modem; for which we'd need your current version - see "my phone"), I would recommend just erasing modem setttings. I suspect this is where the modem config is permanently stored so erasing it should set this to default.
fastboot erase modemst1
fastboot erase modemst2
I would assume that after you boot, your device crashes once - so it does for me after flashing the modem. Happens when I make the first call. So just try calling your mailbox or something.
Again, I can't and I won't gurantee anything. You warranty is void!
Here's the version of baseband my phone has got.
tinypic.com/r/2ntb49c/9
I strongly suggest you try the fix above before going after this. This reflashes your modem which might be unnecessary.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
The modem files are in the download, the ones you are looking for are in:
X_Play_France_Retail_XT1562_LPD23.118-10_CFC.xml.zip
See:
http://forum.xda-developers.com/moto-x-play/general/official-stock-firmwares-added-xt1562-t3195364
http://www.filefactory.com/file/e92ibmowiq5/X_Play_France_Retail_XT1562_LPD23.118-10_CFC.xml.zip
Thanks a lot, erasing the modems did it for me.
Many thanks mate.
Great. You can hit the "Thanks" button if you appreciate it.
I could fix my phone by erasing modems, after doing that I performed a factory reset, but now I've another problem. Installing apk files takes longer time than it would take earlier, does it have to do anything with the problem I was facing earlier?
That does not make sense - it just takes longer on the Moto X; I've experienced the same...
But it was pretty fast before doing the reset, I tried further resets, both hardware as well as software, but to no avail. The installation process is very slow, it took Facebook app atleast 5 minutes to install from apk file. Even installs from market take time and it's annoying.
See my other thread just posted. Assume this is because installs need to be converted from Dalvik to ART.
I know it was a lot faster under e.g. 4.4.2. But you sure it was also for any device with 5+?
I used this device for 2 days before messing up with radio band, i didn't face this problem during those 2 days and i used a Moto g3 for three months, didn't face this problem with that either. And it's dead slow, like currently my fb app is updating in background, it already has taken 12 minutes and is asking for another 3 minutes for a 45mb update.
I guess getting this phone replaced is the safest bet for me, as i have witnessed one more problem. When i keep the phone aside and pick it up after some time i see some strange coloured vertical lines on display at the right with rest of the screen being black. It gets right only when i lock and unlock the screen with power key. Any idea what it could be?
Hardware issue?! I would try and see what happens when you reflash it to full factory but that's of course only what I would do.
So I got my H910 back from LG. and of course it had the latest firmware -- so dirty cow was patched.
Thanks to a discovery by @smitel and then @Prowler_gr doing the dirty work of patching it for our device, LG UP is now able to easily flash firmware from other variants.
So, with this patched copy I proceeded to flash the H915 v10e KDZ -- which IS rootable.
The H910 and H915 are the same phone (at least as far as the FCC is concerned). It worked flawlessly -- except I had no service. No big deal, just need the modem firmware (I hope). In order to flash said modem firmware, I would need a rooted device, so I proceeded. Again, @me2151's dirtycow worked great -- phone rebooted as it was supposed to, I rebooted to recovery and proceeded to flash SuperSU.
Everything went as it should -- till it rebooted. Now I get a green screen of death. The text is too small (getting old), so it is hard to make out, but I can see:
Apps FIQ: NOC Error!
Press vol down if you want to reboot
Reset reason -- some strings with hex values
Board info
a bunch of stuff, but the interesting bit here is:
secure: enabled
Then there is a stack dump.
I know with the engineering aboot, that if you do a fastboot oem device-info that it showed as locked, but this is curious that the XBL thinks that it is secure.
I have tried flashing several kernels, and flashing back the stock system partition, to no avail.
Before I started over in the hopes that I maybe there was a bad flash along the way, I figured I would see if anyone else had a hint.
Thanks,
-- Brian
The good news (I think) is that I can still get into recovery and download mode, so I don't think I bricked my phone yet again.
Its always said secure for the engineering aboot. The engineering aboot allows modified partitions but still considers itself secure(but its not). So you dont need to worry about the aboot saying secure. As for green screen im pretty sure green screen is related to modem. have you tried replacing the modem?
@me2151 First, thanks very much for replying -- I know you are out of the V20 scene.
I haven't been able to get anyone to dump the H910 modem for me yet, and I am now sure you are right.
With an AT&T SIM, it boots, but with a T-Mobile SIM it green screens. Do you know if the SIM dictates what bands are used? If so, I am guessing that T-Mobile is trying to use a band that the H915 firmware isn't aware of:
SIM: Tune to channel 6!
Modem: Uhh no, there is no channel 6!
SIM: Do it anyway!
Modem: Uhh -- how about I just green screen instead...
Thanks again dude. Now I just wait for some kind soul to dump their firmware.
-- Brian
I got a lot of those on my first effort to root. Fastboot was failing to flash TWRP, so I was booting with stock kernel getting all sorts of crashes (green screen & black screen). Once I successfully flashed recovery & flashed @emdroidle 's kernel for H990Ds it was all smoothe. Maybe you need a new kernel...
I did have the stock H910 kernel still sitting around from before I bricked it, and had to send it to LG. I also tried the Werewolf kernel, and even the H918 stock kernel.
I am pretty sure that @me2151 is correct since it will boot with no SIM or with an AT&T SIM -- it is only when I put in the T-Mobile SIM that it green screens.
I need the H910 modem anyway since the H915 modem is a no go...
-- Brian
runningnak3d said:
@me2151 First, thanks very much for replying -- I know you are out of the V20 scene.
I haven't been able to get anyone to dump the H910 modem for me yet, and I am now sure you are right.
With an AT&T SIM, it boots, but with a T-Mobile SIM it green screens. Do you know if the SIM dictates what bands are used? If so, I am guessing that T-Mobile is trying to use a band that the H915 firmware isn't aware of:
SIM: Tune to channel 6!
Modem: Uhh no, there is no channel 6!
SIM: Do it anyway!
Modem: Uhh -- how about I just green screen instead...
Thanks again dude. Now I just wait for some kind soul to dump their firmware.
-- Brian
Click to expand...
Click to collapse
runningnak3d said:
I did have the stock H910 kernel still sitting around from before I bricked it, and had to send it to LG. I also tried the Werewolf kernel, and even the H918 stock kernel.
I am pretty sure that @me2151 is correct since it will boot with no SIM or with an AT&T SIM -- it is only when I put in the T-Mobile SIM that it green screens.
I need the H910 modem anyway since the H915 modem is a no go...
-- Brian
Click to expand...
Click to collapse
yes and no. the simcard would call for a band but usually the phone would ignore it if it is disabled on the phone. Whats probably happening is the tmo simcard is calling for paramaters that are different than the h915 modem and its crashing the modem.
Edit: My original post is contained below. I have edited since I now own the US Cellular variant, and want to share some information about it, and to help clarify some of the rooting process. I ran into some snags that may be obvious to the pros, but for the noobs and novices, a little more detail can be helpful. Also, this information should be useful for either USC or Retail variants.
First, the USC Moto E4 appears to be very much the same as the Retail Unlocked E4 being sold for $130. It has the same SKU of XT1768, can be bootloader unlocked, rooted, and appears to work with most carriers out of the box. I picked up my USC variant for $50 on eBay, and, as of this post, USC has them for $20 plus $35 for 1 month of service. Quite a deal if you can get one.
My thoughts/experiences are:
1. The USC Moto E4 (XT1768) appears to be fully unlocked*.
A. Out of the box it worked with my Tracfone AT&T sim for calls, text, and data WITHOUT having to configure anything.
B. It passed IMEI checks for Page Plus , Verizon, and Tracfone Verizon.
C. It passed IMEI checks for Ting GSM.
D. It, however failed for Tello, which is Sprint only.
EDIT - Thanks to @shogunreaper. He says the phone is compatible with Sprint & Tello once you ask Sprint to add the imei to their list. See here.
* Conclusion: The US Cellular E4 is almost fully unlocked. The retail version says it’s compatible with Sprint, but the US Cellular does not appear to be. It seems that it would/should work for all the other carriers. There is speculation that Moto may have not yet released IMEI numbers to Sprint yet, thus the reason the IMEI is failing for Tello/Sprint. Apparently this was the case for previous unlocked Moto phones. Not a problem for me as I will likely never use Sprint.YMMV.
2. BOOTLOADER UNLOCKING
I followed these instructions.
Unlocking the bootloader will cause the bootscreen to display "Bad Key" when you turn on the phone. THIS IS NORMAL. It will boot normally and your phone will work fine. Currently looking for a method to replace the bootscreen so "Bad Key" isn't displayed.
3. Flash the US Retail Stock Firmware
I did this to see what would happen, if anything, and to de-brand the phone as much as possible. To be fair the USC E4 only comes with 4 bloat apps and a modified Boot Animation with the US Cellular logo. The Retail Stock firmware removes all that. THIS IS OPTIONAL. To flash the retail firmware:
A. Download RSD Lite. This is similar to Odin, for those that have/had Samsung phones.
B. Downloaded firmware. I used the “Retail” version.
C. Unzip firmware to separate folder, install RSD Lite, & put phone into fastboot mode, & connect to PC. In RSD Lite, search for folder with firmware and select the “Flash” file. Process should take about 10-20 minutes.
4. Installed TWRP
A. Used the TWRP image from @squid2. I permanently flashed it with twrp-perry-3.1.1-r2.img
B. It wasn’t obvious to me, but the TWRP image should be placed on your PC, in the same folder you run ADB from, meaning put the TWRP img to be flashed in "platform-tools" for ADB. I originally placed the TWRP image on the phone’s SD card and it didn’t work. Don’t be dumb like me!
C. When you enter the command fastboot flash recovery twrp.img, make sure the twrp.img part matches the file name you downloaded, such as fastboot flash recovery twrp-perry-3.1.1-r2.img or fastboot flash recovery twrp-perry-3.1.1-r3.img.
D. Flashing TWRP to your phone will cause the bootscreen to display "N/A". THIS IS NORMAL. Currently looking for a method to replace the bootscreen so "N/A" is no longer displayed.
5. Root
Followed @KyleBryant guide (bottom of Post #1).
A. Download pph’s su zip.
B. Download no-verity-opt-encrypt.zip.
C. Flash both Superuser & No-Verity in TWRP.
D. Reboot the phone and INSTALL phh’s SUPERUSSER FROM PLAY STORE.
@KyleBryant says to format data in TWRP, reboot to TWRP, then flash the zips. I wound up doing this because after flashing the zips, Root Checker said I didn’t have root…but I think that’s because I didn’t install the SuperUser apk. DUH! Also, formatting data wipes your phone clean. Wasn’t a problem for me as I was doing this on a new phone. So…decide if you want to format data or not. For a new phone it’s not a big deal. If you’ve been using the phone for a while and have all your data, etc…, backup what you need first before formatting data.
6. Remove N/A on boot image
Thanks to @mikaleee, we now have a template to replace the logo.bin. Guide is here.
7. Disable/Remove Increasing ringtone. I posted the procedure here.
Hopefully this helps.
ORIGINAL POST
On another forum, it is mentioned that US Cellular also has the E4 for $20, and reported to be SKU XT1768. Comparing the specs on US Cellular (features tab) to GSM Arena, it appears to have the same bands, specs, etc... However, it has US Cellular bloat. The one user with the US Cellular E4 confirms that his phone works with AT&T WITHOUT sim unlocking. Unfortunately, nobody can confirm if the US Cellular E4 can be bootloader unlocked. I contacted an eBay seller that has several for a really good price, but he can not confirm about the boootloader either. So...does anyone have the US Cellular Moto E4? And does it qualify for bootloader unlocking?
I went so far as to order one from US Cellular, but was rejected because my mailing address is not in their service area.
Thanks,
mn1968 said:
On another forum, it is mentioned that US Cellular also has the E4 for $20, and reported to be SKU XT1768. Comparing the specs on US Cellular (features tab) to GSM Arena, it appears to have the same bands, specs, etc... However, it has US Cellular bloat. The one user with the US Cellular E4 confirms that his phone works with AT&T WITHOUT sim unlocking. Unfortunately, nobody can confirm if the US Cellular E4 can be bootloader unlocked. I contacted an eBay seller that has several for a really good price, but he can not confirm about the boootloader either. So...does anyone have the US Cellular Moto E4? And does it qualify for bootloader unlocking?
I went so far as to order one from US Cellular, but was rejected because my mailing address is not in their service area.
Thanks,
Click to expand...
Click to collapse
I don't have a US Cellular E4, but a couple years ago I was messing around with E2s, (Moto e 2015). Started with a Sprint version, which was bootloader unlockable but not SIM unlockable. Switched to USC version, which was also bootloader unlockable, and also is running on AT&T. There was a little trickery required to get it to see the AT&T SIM iirc, but it's been a while since I've messed what it / used it as a phone. Still sees regular use as a media player.
My guess is the USC one will be unlockable. I looked on USC site, can get it here, but it appears I have to sign up for a month of prepaid service too for another $35. If I can find one for $20 with no commitment I'll grab it and test.
If it is an XT1768 and the bootloader is unlockable, you can flash the retail version firmware which supports AT&T out of the box.
I have a US Cellular version that worked with no tweaks using a GSM BYOP TracFone SIM. Activated immediately.
I'll try and unlock the bootloader tonight and let you know.
yes it is I had one a few weeks ago and got the code from Motorola if you go to settings>about phone>tap build number 7 times then go to developers settings then you sill see allow oem unlock
allc0re said:
I have a US Cellular version that worked with no tweaks using a GSM BYOP TracFone SIM. Activated immediately.
I'll try and unlock the bootloader tonight and let you know.
Click to expand...
Click to collapse
That would be awesome. I ordered one from eBay for $50. Figured it was cheap enough to take a gamble on. I should get it tomorrow.
mattvail692 said:
yes it is I had one a few weeks ago and got the code from Motorola if you go to settings>about phone>tap build number 7 times then go to developers settings then you sill see allow oem unlock
Click to expand...
Click to collapse
Sweet! Did you follow through and root as well?
I haven't rooted yet it seems like things are still in the early stages but will once things start looking more built together this is still a new device so things are going to be a little rough but I will root eventually
I just unlocked the bootloader. It's a go!
(bootloader) Bootloader is unlocked! Rebooting phone
OKAY [ 0.697s]
finished. total time: 0.699s
allc0re said:
I have a US Cellular version that worked with no tweaks using a GSM BYOP TracFone SIM. Activated immediately.
I'll try and unlock the bootloader tonight and let you know.
Click to expand...
Click to collapse
Do you want to say that it's factory unlocked?
Could you try with another GSM SIM card and confirm?
Thanks!
Deleted. Was just a rehash of 1st post.
The only reason I said to format data is to wipe encryption so you can mount the system. Nice guide too, thanks for the mentions.
Sent from my Moto E (4) using XDA Labs
Nice tutorial. Thanks
mn1968 said:
Deleted. Was just a rehash of 1st post.
Click to expand...
Click to collapse
Can you explain the N/A on point 6? "Remove N/A on boot image."
Metconnect2000 said:
Can you explain the N/A on point 6? "Remove N/A on boot image."
Click to expand...
Click to collapse
It's an attempt to remove/hide the N/A that is displayed when bootloader is unlocked/TWRP is installed. If it works, you'll know.
EDIT - It did not work.
mn1968 said:
It's an attempt to remove/hide the N/A that is displayed when bootloader is unlocked/TWRP is installed. If it works, you'll know.
EDIT - It did not work.
Click to expand...
Click to collapse
Sorry to hear that. But this would only possible an issue if you want to turn the device in for warranty purpose. Am I missing something? Also over at the Slickdeals, there are so many people debating on the band 12 for this phone. Do your carrier support that and if so can u test? Thanks
Metconnect2000 said:
Sorry to hear that. But this would only possible an issue if you want to turn the device in for warranty purpose. Am I missing something? Also over at the Slickdeals, there are so many people debating on the band 12 for this phone. Do your carrier support that and if so can u test? Thanks
Click to expand...
Click to collapse
The N/A on the boot screen is a cosmetic thing. Once you unlock the bootloader through Motorola, you agree that you are forfeiting your warranty.
As far as band 12, that's a T-Mobile thing. I use AT&T, so I can not test.
How can I flash retail rom? I have a sprint version xt1766 and tried to flash retail and other roms many times, and every time it fails to flash bootloader and gpt.bin, boot.img. I really would like to have a rom without all sprint bloatware....Do you think sprint version is flashable with retail rom? what am I missing? Many thanks!
@fountain1
1. Is it bootloader unlocked?
2. Does it have the fingerprint reader as well?
3. How are you attempting to flash? RSD Lite appears to be the preferred method. See post #1 for link.
4. It just may not be possible.
5. That's all I have. I can't be of any further help.
Yes, bootloader is unlocked, I am trying to flash it with fastboot cmd, rsdlite doesn't detect my phone on my Windows 10...I am not sure if it has a fingerprint scanner, cannot find it in settings....
Burguitox said:
Do you want to say that it's factory unlocked?
Could you try with another GSM SIM card and confirm?
Thanks!
Click to expand...
Click to collapse
The only other GSM SIM I have to test with is a micro while the E4 takes a nano. Sorry, but I can't test that.
Hi all,
I picked up a used G5 Plus (XT1687) on eBay, with the bootloader already unlocked. I immediately installed AICP ROM with a VZW SIM from a working G4. The phone showed LTE for data, but no voice service. That started a long series of firmware changes that saw me trying Pixel Experience, and a few stock ROMs, having my IMEI show as 0 a few times as well.
I'm at a point with the phone now where I'm on the latest retus channel stock ROM (POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with the bootloader locked. The phone now connects with 1xRTT for voice and EvDo (3G) for data. If I swap this SIM into my other phone (Pixel XL) I get full LTE in the Pixel but still 3G only in the G5+.
The only other standout item is in the BP tools SIM menu, where I get the following errors.
Phone ICCID Compare with SIM ICCID: ERROR
and
PHONE ICCID: PHONE_ICCID_UNKNOWN
I feel like with all the flashes I may have really screwed things up. does anyone have any recommendations on what to try to get LTE service back?
TIA!
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
[email protected] said:
I am in the exact same boat. Searching around the web, there are several reports of this model phone not switching properly, from EvDo revA to LTE channels. Many of these are from non bootloader unlocked phones, and Verizon {and other carriers} pass it off to Lenovo and vice versa. I unlocked mine myself, but being an Ebay phone and knowingly unlocking it, I realize their is no recourse, except hoping for a proper modem software fix from moto. I've been able to get LTE/4g working a couple times, but it doesn't last, so it is a 3g phone for now.
Click to expand...
Click to collapse
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
bra1niac said:
glad I'm not alone here. I'm surprised to hear it happens to phones that have never been unlocked and Moto isn't forthcoming with a fix.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
It seems they would rather replace than fix.
Same with my phone. It has been unlocked and I've been on numerous variations of ROMs stock and custom. Everything was smooth with no issues until I decided to flash an Oreo 8.1 ROM. Immediately after I was greeted with 3G EVDO-Rev A./1xRTT mode with no access to 4G/LTE on Verizon. Sim Card status is screwy with some apps seeing it, albeit improperly configured, most not able to detect it at all. If I return to any ROM below 8.1 I have no data service whatsoever. Hoping a fix is found as all the workarounds do nothing.
Also like the OP, I can get LTE to stick sometimes by messing around with Radio Bands and switching options around in the 4636 menu. But that leaves me without voice/text/mms service.
[email protected] said:
It seems they would rather replace than fix.
Click to expand...
Click to collapse
sad but true
Sent from my Pixel XL using Tapatalk
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
[email protected] said:
I came from a Droid Turbo [quark] and have always liked the motorola phones, in my remote area, for the superior radio reception. My Galaxy S4 dropped calls and data in many of the remote areas, so the Turbo was a welcome upgrade. However, even the with the Turbo, there were Roms that we had to clean and flash updated modems for, when they became balky. I wonder if someone with more engineering knowledge than I have, could look at these twrp flashable modem files, and convert to these G5 plus modems.
Click to expand...
Click to collapse
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
bra1niac said:
Yeah it seems like there should be some way to un**** the phones after flashing an 8.1 ROM. I just don't know enough about the innards of the ROMs either. I had to follow the instructions here https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808 in order to fix an issue with the phone showing an IMEI of 0. There you end up deleting modemst1 and modemst2. I guess they get replaced by the stock or custom ROM, but I have no idea where you would get copies of those from a ROM that would fix this issue, if such a thing exists.
Click to expand...
Click to collapse
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me
this zip will "erase" format the modem status partition:
mdm1m9kefs1 = modemst1
mdm1m9kefs2 = modemst2
Click to expand...
Click to collapse
Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
[email protected] said:
Flashing the modem bin. "NON-HLOS.bin" then erasing modemst1 & 2 gets the 4g/lTE back for some, but has never worked for me. The quark modem we installed the "clean modem" zip which according to the read-me Then flash the modem according to rev of the rom, which included META-INF file folder, boot.img, emmc_appsboot.mbm, fsg.mbn, gpt.bin, logo.bin, modem.img, rpm.img, sbl1.mbn, sdi.mbm, and tz.mbn files.
Click to expand...
Click to collapse
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Archangel said:
It is weird that out of the blue I flashed a 8.1 rom,,,after flashing different 8.1 roms before that,,,I lost VZM service all together. Was able to get back 4G data service only, no voice service. However, after a few mins voice service comes back. Never happened the numerous times I flashed 8.1 before so wonder why it happens all the time now? Makes me think there is a design flaw with the internal radio,,,not the modems software? Would really be nice to see an 8.1 update from Moto,,,may help solve these problems.
Click to expand...
Click to collapse
yeah a factory Oreo ROM would probably help straighten a bunch of things out.
Sent from my Pixel XL using Tapatalk
bra1niac said:
Hm so you're saying to do this:
Flash NON-HLOS.bin from the stock ROM zip
erase modemst1
erase modemst2
reboot
And that might restore LTE? I've never just flashed that bin and erased.
In the info file in the stock ROM I'm using, it shows modem version M8953_37.46.07.47R. In the ROM zip I have
boot.img
fsg.mgn
gpt.bin
logo.bin
missing from the list are
emmc_appsboot.mbm
modem.img
rpm.img
sbl1.mbn
sdi.mbm
tz.mbn
I wonder if the stock ROMs from OTA only include the files that changed, so an older stock ROM might have one or more of those missing files. Or those files just don't apply to the G5+ but do to the Quark.
I'll try downloading a bunch of the older stock ROMs and unpacking them and seeing if any of them contain files that aren't included in the one I've been using.
I've also been ignoring this, but I believe these two steps in the stock ROM reflash have always failed for me:
fastboot erase customize
fastboot erase clogo
I'm not sure what they do so I'll have to dig into that.
Click to expand...
Click to collapse
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
A little research into the baseband processor and its radio firmware RTOS [real-time operating system,] shows it to be closed source, proprietary, yet full of flaws. It is even susceptible to the long standing "Hayes command set" but I don't believe this to be where our particular problem lies. Because it is so closed, it is doubtful the Oreo roms were able to inadvertently touch anything inside this secondary operating system all phones have. It is more likely it is the communication between our android firmware, and the radio firmware, but why the restoration back to stock, doesn't remedy it, is a mystery. The devs that adapted the Oreo roms to this device, missed this link or they would not have written to that area, I'm sure.
You guys are a lot smarter than me,,,it just scared the heck out of me. I flashed a 8.1 rom like I have done at least a dozen or so times on this phone and then suddenly no signal at all,,,then just 4g data and no voice service. I went back to a 8.1 back up that I have and within a few mins everything came back. Now, I am afraid to flash anything rom wise for fear of not getting any signal back.
Something like this really deserves an official statement by Lenovo, Motorola or Verizon. Even if that statement is an unfortunate "you knew the risks associated with unlocking the bootloader and flashing ROMs / modems". Even if none of the three know what exactly is going on they should at least let us know.
Is this problem something that happens with all carriers and their LTE signals? Am I right in thinking that using Verizon is currently the only carrier in which the issue can't be fully repaired?
I havent yet restored my partially working (3g/1x) EFS backup to a stock Nougat Rom yet as I want to have 4G working as well if I do that. If the other carriers can be fully repaired I'll just switch carriers until I get a new phone.
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
[email protected] said:
I think those errors are normal, at least with some stock roms.
Those extra files were from the quark modem files, which is an older modem/radio, so the drivers are going to be different. By the way, I have flashed the modem, flashed the erase modemst1 & 2 and every combo, yet no luv.
This problem can be attributed to one of 2 things. First would be hardware, but by selecting LTE only in the testing menu, I was able to get data in LTE. So the radio's frequency band that supports LTE from Verizon in these phones does work. The Motorola Moto G5 Plus TD-LTE 32GB XT1687 which I have, supports 4 GSM bands, 5 UMTS bands, 15 LTE bands, and 3 CDMA bands. My carrier Verizon uses 3 LTE bands and 2 CDMA bands. The way I understand how it works, is by default, all 4g/LTE capable phones look for a signal in the bands, approved by your sim, in the LTE range first. If not found, it switches to 3g or CDMA , and if that isn't found, 2g. If we are correct in assuming the radio's ability to receive the 3 LTE bands is still functional, it stands to reason the driver that auto switches to CDMA is corrupt. I lost my 4g/LTE on the Pixel Rom, and not by reverting back to stock. It was the only Rom I had ever flashed on the phone after unlocking and installing twrp recovery. I have since gone back to stock and relocked the bootloader, hoping the next ota will jog the drivers to look for LTE before passing off. The times I have briefly had 4g kind of reinforces the theory that the drivers that pass off to 3g are corrupt.
Click to expand...
Click to collapse
Yeah that all seems to make sense. Something we broke with a software change should be fixable with a software change. Hopefully the next OTA isn't too far away.
[email protected] said:
There have been some reports around that putting in a GSM sim even temporarily brings back LTE. I haven't had access to one to try.
Click to expand...
Click to collapse
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
bra1niac said:
That's interesting. My wife is on T-Mobile and was using a Moto G4, now a Pixel. I'll have to snag her SIM for a few minutes to see what happens later this afternoon. I'll report back. :good:
Click to expand...
Click to collapse
It might pay to remove your sim, flash the
Code:
fastboot erase modemst1 fastboot erase modemst2
and then insert her sim. I'm just thinking that would clear the modem for the new bands to set themselves.
I originally bought an X1607 because it was SIM unlocked (or at least wasn't enforced) in 1/2017.
As of an Android update to 7.1.1 in 6/2018, the newest radio firmware either enables SIM locking to Consumer Cellular SIM cards only, or at least enforces it if previously enabled.
My phone essentially became a brick, as I wasn't able to use it as a phone or an LTE device.
First I tried to just buy an unlock code from eBay. Nobody at the time of this posting was able to generate the unlock code. Consumer Cellular was of NO HELP at all, I'd rather bang my head against a wall than talk to them again.
Luckily for me, BOTH of my parents also had this phone, so I had a few phones to work with and try to get it working.
NOTE: Do NOT just unlock the bootloader and install Lineage, that will not make it work.
It took some doing, but this is how I fixed the issue. It works with a stock phone with a locked bootloader.
1) Download the official image for "harpia" at the link. [mirrors.lolinet.com/firmware/moto/harpia/official/]
2) I used the "Consumer Cellular" version, but I hope that it will work with the others. The "CCAWS" version was the one that I used. (NOTE: If this is not in fact the "Consumer Cellular" version, it did work with my phone version).
3) Copy the following 2 files out of this zip file.
NON-HLOS.bin
fsg fsg.mbn
4) Perform the following commands from your command line.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
5) Reboot, and you should have it working now.
6) Turn off all Automatic Updates, you don't want to do this again.
Please let me know if you have any issues and I'll do my best to help you out.
Great timing, a friend just ran into this issue and I will now be able to help them out...hopefully
Thx
mrpickem said:
Great timing, a friend just ran into this issue and I will now be able to help them out...hopefully
Thx
Click to expand...
Click to collapse
Glad to help.
If you have any issues, PM me and if I am needing to add or improve the OP, I'll edit it in there.
Worked great, thx.
Have you tried flashing other carrier firmware, like maybe the unlocked version? Or do you have to unlock bootloader to do that?
mrpickem said:
Worked great, thx.
Have you tried flashing other carrier firmware, like maybe the unlocked version? Or do you have to unlock bootloader to do that?
Click to expand...
Click to collapse
You're welcome. Glad to have helped.
Good question on flashing to another carrier.
Just took a look, and didn't see anything that is obviously looking like it is T-Mobile. They might not even have a G4 Play version. I was just irked that it had worked for so long that they just now decided to lock it, and then were completely unwilling to unlock it now that I'm well outside of the return window.
Thanks for posting the guide! Worked great!
Might want to post this to the Moto G4 Play forum, because this forum is for the OG Moto G.
But otherwise, nice guide!
Many Thanks
I haven't tried this unlock yet but regardless...A big thankyou for your listing
did not work for me
DarkMeans said:
I originally bought an X1607 because it was SIM unlocked (or at least wasn't enforced) in 1/2017.
As of an Android update to 7.1.1 in 6/2018, the newest radio firmware either enables SIM locking to Consumer Cellular SIM cards only, or at least enforces it if previously enabled.
My phone essentially became a brick, as I wasn't able to use it as a phone or an LTE device.
First I tried to just buy an unlock code from eBay. Nobody at the time of this posting was able to generate the unlock code. Consumer Cellular was of NO HELP at all, I'd rather bang my head against a wall than talk to them again.
Luckily for me, BOTH of my parents also had this phone, so I had a few phones to work with and try to get it working.
NOTE: Do NOT just unlock the bootloader and install Lineage, that will not make it work.
It took some doing, but this is how I fixed the issue. It works with a stock phone with a locked bootloader.
1) Download the official image for "harpia" at the link. [mirrors.lolinet.com/firmware/moto/harpia/official/]
2) I used the "Consumer Cellular" version, but I hope that it will work with the others. The "CCAWS" version was the one that I used. (NOTE: If this is not in fact the "Consumer Cellular" version, it did work with my phone version).
3) Copy the following 2 files out of this zip file.
NON-HLOS.bin
fsg fsg.mbn
4) Perform the following commands from your command line.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
5) Reboot, and you should have it working now.
6) Turn off all Automatic Updates, you don't want to do this again.
Please let me know if you have any issues and I'll do my best to help you out.
Click to expand...
Click to collapse
Hello, I have two Consumer cellular in android 6.0.1 and followed the steps you provided, downloaded the ccaws version but it keeps on prompting the unlock code, I wonder why you used CCAWS if phone is consumer cellular and that is the firmware presumed to be the carriers, it wouldn't make sense to use the same model's modem to unlock it. Any other suggestions?
Goodnight. update the phone that was unlocked did not request sim code. Now on reboot I am left with network blocking. What would be the solution?
DarkMeans said:
I originally bought an X1607 because it was SIM unlocked (or at least wasn't enforced) in 1/2017.
As of an Android update to 7.1.1 in 6/2018, the newest radio firmware either enables SIM locking to Consumer Cellular SIM cards only, or at least enforces it if previously enabled.
My phone essentially became a brick, as I wasn't able to use it as a phone or an LTE device.
First I tried to just buy an unlock code from eBay. Nobody at the time of this posting was able to generate the unlock code. Consumer Cellular was of NO HELP at all, I'd rather bang my head against a wall than talk to them again.
Luckily for me, BOTH of my parents also had this phone, so I had a few phones to work with and try to get it working.
NOTE: Do NOT just unlock the bootloader and install Lineage, that will not make it work.
It took some doing, but this is how I fixed the issue. It works with a stock phone with a locked bootloader.
1) Download the official image for "harpia" at the link. [mirrors.lolinet.com/firmware/moto/harpia/official/]
2) I used the "Consumer Cellular" version, but I hope that it will work with the others. The "CCAWS" version was the one that I used. (NOTE: If this is not in fact the "Consumer Cellular" version, it did work with my phone version).
3) Copy the following 2 files out of this zip file.
NON-HLOS.bin
fsg fsg.mbn
4) Perform the following commands from your command line.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
5) Reboot, and you should have it working now.
6) Turn off all Automatic Updates, you don't want to do this again.
Please let me know if you have any issues and I'll do my best to help you out.
Click to expand...
Click to collapse