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.
Related
So I've got a US Moto X Pure, XT1575, currently running TruPure XMM 2.9, just installed a few days ago, and while driving around with my brother I've noticed that my 4G switches to 3G and loses conncections all the time, while his Verizon LG V10 maintains a rock-solid LTE connection. I've also found that in many, many areas, if i run a speed test, most of the time it tells me less than 1mbps down, and usually 0-0.02 up, his get's normal speeds. I've even found areas where I get 40+ mbps down, 0 up.
Is it the modem firmware? Did I break it? I have opened it up a few times but I was always very gentle and triple checked all connections before re-installing the casing.
Is it because of the CDMA/GSM thing? My old Note 3 before this phone didn't have any of these problems, my brother's V10 doesn't either.
I'm losing my mind trying to fix it and nothing's worked.
TallgeeseIV said:
So I've got a US Moto X Pure, XT1575, currently running TruPure XMM 2.9, just installed a few days ago, and while driving around with my brother I've noticed that my 4G switches to 3G and loses conncections all the time, while his Verizon LG V10 maintains a rock-solid LTE connection. I've also found that in many, many areas, if i run a speed test, most of the time it tells me less than 1mbps down, and usually 0-0.02 up, his get's normal speeds. I've even found areas where I get 40+ mbps down, 0 up.
Is it the modem firmware? Did I break it? I have opened it up a few times but I was always very gentle and triple checked all connections before re-installing the casing.
Is it because of the CDMA/GSM thing? My old Note 3 before this phone didn't have any of these problems, my brother's V10 doesn't either.
I'm losing my mind trying to fix it and nothing's worked.
Click to expand...
Click to collapse
Have you tried going into fastboot and erasing modemst1 and modemst2?
hbar98 said:
Have you tried going into fastboot and erasing modemst1 and modemst2?
Click to expand...
Click to collapse
Not yet. First time I'm getting this advice. What does erasing them do?
TallgeeseIV said:
Not yet. First time I'm getting this advice. What does erasing them do?
Click to expand...
Click to collapse
Well, as far as I can tell it erases the info in the modem partitions. I'm not really sure. But when people have gps or lte issues, erasing them seems to help. I've been on a flashing binge lately, and I erase them pretty much in between every flash with no issue.
hbar98 said:
Well, as far as I can tell it erases the info in the modem partitions. I'm not really sure. But when people have gps or lte issues, erasing them seems to help. I've been on a flashing binge lately, and I erase them pretty much in between every flash with no issue.
Click to expand...
Click to collapse
Ok, does it need to be done before flashing a new modem? Or do you erase them after so it rebuilds them automatically or something?
I flash the modem, then erase modemst1, modemst2.
Ok, so let's see if I did this right:
I went and extracted 'NON-HLOS.bin' and 'fsg.mbn' from the latest stock firmware in this post: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Then I booted into fastboot mode and used these commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I found these as a fix for a Moto X Style having similar connectivity issues in this post: http://forum.xda-developers.com/moto-x-style/help/baseband-imei-t3283141
Then i rebooted and i've got signal but nothing seems any better. The only difference, which i'm hoping has been the issue all along, is that now under Settings>More>Cellular Networks>Preferred Network Type I'm able to select CDMA and have it maintain signal. Before, whenever I clicked that I would lose all data signal and it wouldn't come back. Gsm sort of worked but cdma would never work, it does now.
I can't really test it right now since I have crap signal at my house either way, but does this sound like I've solved something or is this just the placebo effect?
Well, that made it waaaay worse. A lot of new gps issues now....
Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.
MrFarquad said:
Hey all,
So, a little backstory: I got this HTC 10 from Sprint not too long ago, and little did I know that I would be stuck with Sprint unless I reflash the phone firmware. (after research, asking HTC and Sprint, I received misinformation from reps stating that the phone would work on Verizon with just a carrier unlock issued over the air). Moral of the story: don't rely on customer service :silly:.
Fast forward to now, and I have rooted (temporarily to run Sunshine), S-OFF'd (using Sunshine), changed the CID (for Verizon), and flashed the newest Verizon RUU that developer Dottat kindly posted here.
That worked, full LTE, but then whenever the camera or GPS were accessed by any application, the phone would freeze with a black screen (though it seemed something was still running in the background, as notification sounds would still play, and I could exit by pressing the home button and waiting about a minute). After this, I tried flashing the Viper ROM just for kicks, but then the cellular radios only functioned with 3G coverage (no LTE in a coverage area), and GPS was still broken (the camera issue was fixed with this flash for some reason).
Unfortunately (or maybe not), I am pretty sure /system has been wiped multiple times. I also ran
Code:
htc_fastboot erase modemst1
htc_fastboot erase modemst2
after each install of a new ROM, then performed a factory reset from recovery (just a factory reset, nothing more).
Now I went ahead and used an official ROM from HTC's website in an attempt just to get full functionality working on any carrier. I flashed the USA unlocked variant (and changed the CID to BS_US001. MID is still 2PS650000), but now I am experiencing more missing functionality. The camera and GPS are still missing, and now the SIM card is not detected (when entering the access point names dialog, a message pops up stating that there is no SIM, or SIM error when I am using an activated AT&T SIM). When I enter the test menu (*#*#4636#*#*) and select any option for network mode other than what is default (LTE/CDMA), the new option won't 'stick' (it returns to default after a few seconds).
This sounds to me like there is stale firmware on the device from a previous flash, or that the firmware for these core peripherals is corrupt. Is there a way I can get these devices working again? Or am I now stuck with a bricked device ? I do still have a backup I took of what was installed stock by Sprint (all except for /data...but I don't need that partition, right?)
EDIT: Mods, I am terribly sorry! I meant to post this in HTC 10 Q&A. I don't see a way to delete a thread, so hopefully we can move it.
Click to expand...
Click to collapse
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)
If your trying to use the phone on Verizon I would do the following:
1) Change your CID to Super, 11111111
2) Flash the US Unlocked RUU, http://www.htc.com/us/support/rom-downloads.html#unlocked
3) After it fully boots, reboot into the bootloader & flash the Verizon radio, http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
4) Make sure the Preferred Network is set to Global, Settings>Mobile data>Preferred Network
5) Get to the secret menu *#*#4636#*#*, and set the preferred network type to "CDMA/EvDO/GSM/WCDMA/LTE Auto"
I use a Verizon model with the US Unlocked firmware. As far as custom ROMs, some work with Verizon's network and some don't. I'm sure theres a workaround but I've stuck with the US Unlocked firmware, and just use Xposed for any tweaks/mods.
If your trying to use it on AT&T and the radio from the US unlocked RUU should work.
andybones said:
A MOD should move it soon.
I am not the best here, but hopefully can be of some help.
I would just superCID, save a step for flashing RUU's.
So, when you flash the Verizon RUU, does camera work?
(if you RUU and only have 3g, wipe the modems to get 4g back)
Click to expand...
Click to collapse
Used to be a guy around here we could trust to help.
Sent from my HTC6545LVW using Tapatalk
Just picked this up today because of it being SIM unlocked out of the box. I am having a hell of a time getting calls to keep working though. Most of the time it will cut all cell service while in the middle of a call and not go through or it will go through, just with no sound both ways. I've tried *#*#4636*#*# and the network app but to no avail. I've also tried the old adb global settings as well, and that didn't work. Trying to use it on T-Mobile.
Update: took a shot in the dark and flashed the stock XT1607 rom on it and it looks like I can make calls normally now. The software channel still states USC though.
had the same issue. flashing the modem/radio files from the stock firmware fixed it for me:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
picked up the consumer cellular version and planning to use on mint sim (TMO MVNO). what exactly do i have to do to make it work? i'm a newbie and need some guidance please.
tia
m
I am having the same issue with a consumer cellular xt1607. Data/text works fine but sometimes the mic and speaker aren't working when making and receiving calls at times. Where is the most trusted place to get the firmware? How do I know the firmware hasn't been tampered with? Thanks.
miserly said:
picked up the consumer cellular version and planning to use on mint sim (TMO MVNO). what exactly do i have to do to make it work? i'm a newbie and need some guidance please.
tia
m
Click to expand...
Click to collapse
I'm not sure if consumer cellular leaves their phones network unlocked like USC does. Consumer cellular should allow you to unlock the bootloader, but unlocking the network for use on another carrier besides CC may not work. You can try unlocking the bootloader and flashing another radio/modem/baseband to see if you can get it to work (if it isn't network unlocked out of the box), but I tried this with an older Moto phone before and as of recently it seems like you are unable to replace those partitions mentioned, even with an unlocked bootloader
chadrebuck said:
I am having the same issue with a consumer cellular xt1607. Data/text works fine but sometimes the mic and speaker aren't working when making and receiving calls at times. Where is the most trusted place to get the firmware? How do I know the firmware hasn't been tampered with? Thanks.
Click to expand...
Click to collapse
I can't find any places off hand for the xt1607 CC model, but if I see anything I'll let you know. Honestly, it may seem like a pain, but if you haven't messed with your firmware at all I'd send it back for warranty if I were you
EDIT: found a place to download firmware here:
https://firmware.center/firmware/Motorola/Moto G4 Play/Stock/XT1607/
There is no firmware for the CC model specifically, but there is the RETUS which is the generic, straight-from-motorola xt1607 firmware. You can try to flash RETUS to see if it works if you want, but I can't guarantee it will work or not mess more things up. Like I said before it seems like your safest option would be to return for warranty since you haven't messed with the firmware in any way (side note: flashing the RETUS firmware, if it even flashes, should not count as "messing with the firmware" since it is stock Moto firmware, and if it still doesn't work afterwards you should still be OK to send it back for warranty)
Thanks for the reply. I actually have the US Cellular version (for some reason I had Consumer Cellular in my head). The other night I went ahead and followed an unlock guide and installed only the modem drivers as suggested above using these commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I grabbed these files from the retus firmware file as I assumed that was intended for the unlocked 1607. It has worked just fine since that point.
This Worked!! THANK YOU I'm on Mint-sim calls are working now!!!
files-moto-g-play-xt1607.zip | Mirror | Mirror | Mirror
Hello, everyone! I was hoping maybe you could give me your opinion on the following issue:
About a year ago I purchased a Moto X Play XT1562 in Europe with dual sim support (Asian ROM). I knew beforehand that I'd probably have limited LTE coverage in my country (Argentina), since the bands used by carriers here are B4 and B28, and XT1562 only supports B28 (which is used mostly for coverage in suburbs and rural areas). Band 4 is the main band used in Argentina for LTE coverage in cities and XT1563 is the model that supports it.
For quite some time I've had the theory that most phones should support more bands than they show, and that the differences between various models of the same phone are there to introduce region restrictions, which in turns means that some LTE bands are disabled and that it should be possible to somehow enable them by tweaking the software. For what I've read, there seems to be some support for my theory: there's a thread in this very same forum which claims that it should be possible to unlock all LTE bands in devices with Qualcomm processors by rooting the phone, installing a custom ROM and kernel and changing a few values.
LINK: https://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Now, I'd really want that to be the last thing I try. I've rooted my phone before and I even unrooted it by flashing stock ROM, so I know my way around, but flashing a custom ROM and kernel are things I'd rather not do right now.
So, that brings me to my second theory: since XT1562 and XT1563 are basically the same device, their hardware specifications are the same and only differ in the LTE bands they support... and since LTE bands seem to be software-restricted...
1) Could it be possible to unlock Band 4 by flashing XT1563 stock ROM to my XT1562 Moto X Play?
2) Has anyone tried to do that (even by mistake) without bricking the device?
3) If there's no option but to flash a custom ROM and kernel, does anyone know for sure if LTE bands in Moto X Play are software restricted? Or is there a hardware limitation?
Probably my secornd theory won't work because I don't think the solution would so simple, and there would be threads about it... but I guess I don't lose anything by asking
Thank you!! =)
Just realized this thread shouldn't go in General. Could someone please move it to Q&A? Thanks!
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
DragonClawsAreSharp said:
The frequency bands that your phone supports is region specific (as you guessed) and has legal implications. And just like your device IMEI, these values are found in the non-volatile memory of your phone. The values are basically on partitions that are much secure and not so easily editable (like by fastboot or recovery). But nevertheless, the values are "software" only, and so it must be possible to edit the values anyway (just like it is possible to edit the IMEI), one way of doing so is using Qualcomm software as in the link you had posted.
But this varies from device to device, vendor to vendor, so your second theory could actually work on our phones (really don't think so though).
While it might be possible to run ROMs for XT1563 on XT1562, the baseband/ modem for XT1563 would not work on XT1562; it would probably make your device show "unknown" for IMEI, and so you would get no SIM network. Flashing back the modem for XT1562 would probably fix it.
You could always try and find out...
You would need the NON-HLOS.bin and fsg.mbn files from the XT1563 stock image to try, and the same files from the XT1562 stock to revert back.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
There's chance that you would be stuck with an "unknown" IMEI and then you would have to manually edit volatile memory values after all. This all is just theory, someone who has tried or someone who has more knowledge will be able to help you better.
Click to expand...
Click to collapse
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
floydian86 said:
Thank you for your kind reply =)
So, if I understood correctly, there's no need to flash the full XT1563 stock image. I'd just have to flash those two files from XT1563 stock rom, and then if it doesn't work then I'd just flash the XT1562 files again, which I already have. Seems worth to try and with low risk of bricking my phone.
Now, if that doesn't work, then my only option would be to use the other method. I don't want to try that one yet because I don't have everything figured out: I'm stuck in step 6, "Open the USB settings screen on your phone." I haven't yet found the correct code to input in the phone's dial screen to edit USB settings. I think in Android 6 the USB options have all been moved to developer mode, but I'm not 100% sure yet.
Click to expand...
Click to collapse
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
DragonClawsAreSharp said:
At step 6, you are basically trying to connect the phone to your PC in a vulnerable mode (Modem + Diag mode) so you could access the NV. On Moto phones this is not really possible by dialing a service code I think.
Did you try to boot your phone in BP tools (or QCOM?) mode from fastboot? Then connect to PC and it should be connected in diag mode (check in Device Manager to confirm). You might need some specific drivers, see last thread, or may be Google.
There is a lot of discussion about this on the internet (for other devices, mostly). Mostly because people with locked devices that work only on specific carriers use a similar edit of values in NV of the phone to get out unlocked.
I think you should Google and try out some of the things people have been suggesting.
Read here, post number 21, for example (the entire thread is pretty informative): https://forum.xda-developers.com/moto-x/moto-x-qa/unlock-lte-bands-moto-x-t2933475/
And here (for Moto X Play),
http://forum.xda-developers.com/moto-x-play/help/trouble-writing-nv-settings-moto-x-play-t3368261
Edit: Most of these NV and QPST threads do seem to repeatedly point out that writing on the NV is extremely risky.
Click to expand...
Click to collapse
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
floydian86 said:
Thanks again!
So, I flashed the XT1563 modem files. It took me a while because when I unrooted my phone, I also locked the bootloader (I honestly don't know why I did it), so I had to unlock it again and of course make a back-up.
While at first it seemed that I'd be stuck with "unknown" IMEI just as you said, after a minute or so both sim cards started working. I still don't know if it worked, though, because I haven't yet seen the 4G sign on my phone, but I did notice a change: after flashing the files I started getting the H+ sign (H was the best I'd get before, both here and in Europe, even after flashing an XT1562 stock image). So, it wasn't a complete waste of time
It could be that LTE reception is just bad where I live, but I doubt it because other phones have 4G connection here. I'll see what happens tomorrow in another place, but but most likely I'll have to try with a custom image and kernel, so I'll take a look at the links you have provided.
EDIT: in Europe the best I'd get was 4G, of course. What I wanted to point out was that H was the best 3G connection I'd get anywhere.
Click to expand...
Click to collapse
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
DragonClawsAreSharp said:
Dial *#*#4636#*#* (4636 stands for INFO) on dialer and you can select LTE only from network modes to force 4G detection. In this mode, it will pick 4G network (4G only, even if its weak), whenever it's available.
To really check supported bands by your phone, I think you would need to use the QPST app, it was possible earlier by *#*#SERVICE#*#*, the service menu. Maybe somewhere in *#*#2486#*#*?
Edit: I can think of two scenarios now. The sad one... while you flashed the XT1563 modem (that supports LTE Band 4, 8, etc. (values on the lower row, check attached), your NV still says it supports 19 and 8 and so on (not 4). This could mean you are now able to use only 8 (and the other common bands supported by the two variants) and neither of 19 or 4.
Or, Moto X Play decides which bands it supports depending only on the modem files, and you actually managed to get working LTE band 4 on your XT1562. .
Click to expand...
Click to collapse
I did try to select LTE only, but it didn't work.
I also tried using service menu, but I didn't find any of the tests to be useful to check which LTE bands are supported.
About the scenarios you propose, I also thought maybe all I achieved was to restrict LTE bands to the ones supported by both models :S. At work my phone picks band 28, but both models support it, so there's no way to check it by discarding...
There's a third possibility, though, which is that both models' modems are exactly the same and bands are only limited by NV.
After work I'll see which custom roms and kernels are there for X Play and start studying the process to edit NV. Still it might not be possible to do so because the post claims that rom and kernels must be compiled from source code, so the ones made from stock won't work... That means I depend on there someone making a rom and kernels that meet those requirements.
In the second link, the person says he can't save the changes he makes to the NV, which is what is supposed to happen if you're using stock rom and kernel, according the link I've shared.
So, I ended up editing the NV in order to remove Band 4 restriction. It took me a while because I had to figure out how to bypass all the obstacles I found on the way but, once everything was set up, the process was quite simple.
I had to boot my phone in BP Tools mode and configure the QC Diag port driver correctly. Also, I had to use a newer version of QPST because the one I donwloaded first didn't work.
The tutorial claims that your phone must be rooted and that you need a custom rom and kernel in order to avoid the "anti-tamper" mechanisms in newer Qualcomm devices. My first approach was not to do such things (i.e.: unrooted phone with stock rom and kernel).
I edited the NV values as suggested in order to enable Band 4. The good news are that the custom values that I added didn't revert back to the original ones after I rebooted and also that I didn't brick my phone and it's working properly
Right after I rebooted my phone, it picked 4G signal, but after just a few seconds it switched to H. I forced my device to LTE only, and it connected to 4G, but then again it completely lost signal. My phone does pick LTE Band 28 sometimes, but not at my place, so I thought that I must have been picking up Band 4 (I tried to leave it set to LTE only, but it picked no signal at all).
Also, when I'm at work, it sometimes picks Band 28, but signal must be very weak because it never lasts more than a few minutes, after which goes back to H.
So far I'm not sure if the mod worked because I can't find a way to see which bands my phone currently supports or which LTE band it's connected to. I tried an app called LTE Discovery, but it labels it as "unknown band" (I suspect that my phone needs to be rooted in order for that feature to work).
Right now, I'm thinking of three possible things that could have happened:
1) The mod worked and LTE signal is just very poor by my place.
2) It worked and it connected to Band 4 for a few seconds, but then the anti-tamper mechanism detected that situation and software-blocked it (without reverting NV changes I made). In this case, I'll have to flash a custom kernel and see what happens.
3) There's a hardware limitation after all, in which case there's nothing I can do (I don't think this is the case)
Right now I'm at work and my phone has been picking up 4G for over an hour already. Since it usually only lasts a few minutes (connected to Band 28), then I guess there are reasons to be optimistic that it worked after all and it is currently using Band 4.
If I succeed, I'll open a new thread with a tutorial for Moto X Play.
I'll keep updating my progress on the issue in order to leave a record of everything I tried. Also, it could be helpful to other people who are trying to do the same thing or maybe someone who has done this before will see this and point me in the right direction . Again, if I succeed I'll write a more detailed guide.
I can confirm that what I did so far didn't work, I've modified the necessary NV values and even flashed Squid kernel, but still no success: I'm definitely not picking Band 4 anywhere, only Band 28.
While flashing the custom kernel, I also wanted to use the opportunity to root my phone, but for some reason I soft-bricked it in the process, so I had to flash XT1562 stock rom again (with XT1563 modem). This reverted the NV values to the default ones, so I had to customize them again.
The user fffft says that custom rom and kernel are needed in order to avoid the anti-tamper code, but also that it is most likely in the kernel. I could try another kernel, maybe Phoenix, but if that doesn't work either, then we can confirm that the anti-tamper code is actually in stock rom.
This leaves three final possibilities to succeed in unlocking LTE Band 4:
_Flashing another custom kernel
_Flashing a custom rom
_Flashing the whole XT1563 stock rom, as I proposed at first, and see what happens. If this works, this should both set the NV values to enable XT1563 default LTE bands (which includes Band 4) and also set a different anti-tamper code, which should not bother. Worst case scenario I'll soft-brick my phone again and I'll have to flash XT1562 rom.
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
floydian86 said:
Daily update:
First thing I tried yesterday was what I wanted to do from the beginning, which is to flash the whole XT1563 rom on XT1562. Kids, don't try that at home! At first it looks like it's working and that the device is going to boot normally, but then it gets stuck in the apps configuration screen or after the boot animation.
The only thing left now was to try with a custom rom, so I flashed Cyanogenmod 13 and Squid kernel. This, however, brought other issues: for some reason, when booting the phone in BP tools mode or Qcom, the device's QC Diag Port isn't detected by PC. It seems to be something implied to happen with custom roms: https://forum.xda-developers.com/moto-g-2014/help/diagnostic-mode-moto-g-flashing-cm-12-1-t3254756
Has this happened to any of you? Is there a way around it?
I also found this: http://www.howardforums.com/showthread.php/1692461-HTC-Evo-and-Cyanogenmod-Diagnostic-mode
There they mention that changes should be made on stock image and just then install the custom rom. That would mean to flash stock image, then change the required NV values, and finally install the custom rom.
That makes some sense, but unless I can find a way to enable Diag mode on Cyanogenmod, this will be the last thing I try and if it doesn't work then I'll give up
Click to expand...
Click to collapse
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
DragonClawsAreSharp said:
On step 14 of the first post you shared, it says you could check the active bands on your phone. Do you see something useful there?
AFAIK, once you successfully edit the NV Memory, the changes are there to stay, even if you reflash stock ROM.
I can confirm one thing. BP tools + stock ROM gives you diag mode, but that doesn't work on AOSP based ROMs. And it seems not even on CM based ROMs. However it should be easier to do it on custom ROMs, try enabling and looking into Developer Options. Or may be some service code in phone app?
https://forum.xda-developers.com/showthread.php?t=1626638
On my phone running an AOSP based ROM, I have files that indicate a possible diag mode at /system/sys/class/Android_USB. Need to dig in more.
If you are not able to get your phone connect in diag mode successfully, the route I would now suggest is this:
1. Flash stock ROM (for XT1562)
2. Flash custom kernel
3. Root the stock ROM (use Magisk)
4. Edit NV Values, make sure it is successfully done (step 14 on the first post you shared?).
5. Check if its working.
6. Format /system, /data, and cache partitions, and flash ROM. So your baseband files (and ofc NV memory) is not affected.
7. Try again.
Click to expand...
Click to collapse
Thanks!
When I edited the NV, the changes were saved (I closed QPST and QXDM, then rebooted my phone and checked the values). However, when I flashed stock rom, the values reverted to the original ones. I also thought that shouldn't happen, but nevertheless it did :S
About getting Diag mode on custom roms, I took a quick look at developer options but I didn't see anything useful. I read a few posts that claim it can be done using a terminal emulator, so there has to be a way around it.
The steps you mention are the ones I had in mind, except for rooting. Do you think it's really necessary? (phone will be rooted after flashing custom rom, anyway).
I'll try it tonight and see what happens =)
EDIT 1: If I understood correctly, step 14 of the thread I've shared is only for 3G bands, so I don't need to change anything there. LTE bands NV's can only be seen and modified using QXDM and that's where I checked if the changes were saved. However, I have seen that there are a few holes in the tutorial, some of which I had to figure out myself. Maybe there's one extra step I'm missing on QPST? Step 24 seems to indicate otherwise.
EDIT 2: I've found this thread. It's about a Lenovo phone, but chances are they are the same: http://www.teamsuperluminal.org/forums/topic/open-diag-port-in-cm-12-1-for-qpst/
This is what it says: "To open the diag port, connect the phone to a PC and use ADB:
adb shell
su
setprop sys.usb.config diag,adb"
Changing the NV and then flashing custom ROM didn't work (I deleted system, data and cache before but still didn't work).
I tried enabling diag mode using ADB with the code I found but it didn't work. No diag port gets enabled.
I'm ready to give up. It seems it can't be done, at least not on X Play
Unless maybe someone know how to use diag mode on Moto X play running Cyanogenmod?
I have been getting terrible radio drops on baseband 03.84. I am on Oreo with the latest November security patch. I downloaded several older radio img files to try. I also found an app called FlashFire. Is anyone familiar with it. I wanted to know if I can flash the radio img files using it without problems. Thanks.
Don't do it with flashfire !!!!!!!! I did flash the bootloader two days ago with flashfire and had a hardbrick. ( Like a lot of other people trying to flash bootloader and radio with flashfire )Yesterday I spent a lot of hours of reading and with big luck i got my phone unbricked, but that's not always the case.
Don't be lazy like me, flash bootloader and radio only with fastboot to be safe. For the rest flashfire is a good app.
cigator said:
I have been getting terrible radio drops on baseband 03.84. I am on Oreo with the latest November security patch. I downloaded several older radio img files to try. I also found an app called FlashFire. Is anyone familiar with it. I wanted to know if I can flash the radio img files using it without problems. Thanks.
Click to expand...
Click to collapse
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
v12xke said:
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
Click to expand...
Click to collapse
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
cigator said:
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
Click to expand...
Click to collapse
I'm not us citizen and not using Verizon, but may the radio of this factory image gives you a good connection, just an idea.
7.1.1 (NUF26N, Mar 2017, Verizon Only)
cigator said:
Thanks to both posters for stopping me from using Flashfire to flash radio. I appreciate your questions, if you can offer any help that would be great. I'm on Verizon, in the Orlando Fl area. I have tried new sims, the one I have now was a replacement from about 2 months ago. I looked at LTE Discovery, sitting in my living room I'm at -114 dBm. What other data is useful for me to look at. The issue I have is many times I go to 0 bars of signal and calls drop or I can't connect to call. Looking for any solutions to this. I like my 6p, had it for 1.5 years, I would like to keep it longer but not if it keeps performing like this on phone calls.
Click to expand...
Click to collapse
Very few on Verizon complain about signal strength. They do rightfully complain about the many other things the Red Devil does, but signal strength is usually not one of them. I've found LTE Discovery to be useful in knowing what band I am on, what tower I am connected with, best signal strength location within my home/office/pub, what bands work best and when I get stuck with ****ty signal.... I can reset the network and it locks to a different band. This happened at my local pub all the time until they got excellent wi-fi. The phone would not give up (release) a poor connection and search for a stronger one. You can play around with Open Signal as well. They have a signal strength coverage map that is real-time crowd sourced rather than carrier propoganda. Once you have collected your data trends, you could then also try a different carrier for a day or two. Those Verizon specific images/radios simply contain additional support for Verizon specific add-ons like VVM and HD calling, etc. They won't make your signal better.
v12xke said:
No. FF is a great app for updating your phone(s) every month, retaining root and custom recovery. That said, it is not intended for flashing protected partitions (like bootloader and modem) and Chainfire explicitly points this out in the documentation. A different radio is unlikely to help you. You may want to lay out what carrier you are on, your geographic location and what you have tried already such as swapping SIMs from a different carrier, and signal data you get from a app like LTE Discovery.
Click to expand...
Click to collapse
v12xke said:
Very few on Verizon complain about signal strength. They do rightfully complain about the many other things the Red Devil does, but signal strength is usually not one of them. I've found LTE Discovery to be useful in knowing what band I am on, what tower I am connected with, best signal strength location within my home/office/pub, what bands work best and when I get stuck with ****ty signal.... I can reset the network and it locks to a different band. This happened at my local pub all the time until they got excellent wi-fi. The phone would not give up (release) a poor connection and search for a stronger one. You can play around with Open Signal as well. They have a signal strength coverage map that is real-time crowd sourced rather than carrier propoganda. Once you have collected your data trends, you could then also try a different carrier for a day or two. Those Verizon specific images/radios simply contain additional support for Verizon specific add-ons like VVM and HD calling, etc. They won't make your signal better.
Click to expand...
Click to collapse
Thanks, I flashed an older radio and don't see any improvement. When I use LTE discovery and cycle the radio on and off it changes the band and my signal seems stronger, but then it reverts to the weaker band. Is there some way to lock it to the stronger band?
cigator said:
Thanks, I flashed an older radio and don't see any improvement. When I use LTE discovery and cycle the radio on and off it changes the band and my signal seems stronger, but then it reverts to the weaker band. Is there some way to lock it to the stronger band?
Click to expand...
Click to collapse
I've read of a root hack but can't remember where exactly. I think it was in one of the Indian threads. I'll look around. I still believe this is probably down to the carrier vs. hardware.
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
zeeshanalpha said:
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
Click to expand...
Click to collapse
Which stock image did you flash?
Sent from my Nexus 6P using XDA Labs
mdfarazb2 said:
Which stock image did you flash?
Click to expand...
Click to collapse
NJH47F 7.1.2 Nougat Stock Firmware
zeeshanalpha said:
NJH47F 7.1.2 Nougat Stock Firmware
Click to expand...
Click to collapse
Try the latest 8.1
Sent from my Nexus 6P using XDA Labs
zeeshanalpha said:
What does radio image normally include ? Does it have a solution for my WiFi problem? I have been asking this on several forums but unfortunately I get no reply, my N6P is no more detecting WiFi signals. I literally get only loading screen on my WiFi panel and end up loading at the end only. I flashed stock images as referred by one of my friend but unfortunately nothing happend N6P without a WiFi is boring guys please help.
I don't get Bluetooth signals also
There is also no IP address seen and it is showing unavailable and MAC address in 20:00:00:00 from long time
Some screenshots below
Click to expand...
Click to collapse
Do you have any efs partition backup with TWRP, if yes, try to restore it with TWRP.
Edit: for some guys it help to remove simcard and reboot the phone without, don't ask me why.
Edit: and some solutions from a n6 thread with the same issue, if the issue still persist
https://forum.xda-developers.com/nexus-6/help/wifi-mac-address-200000000000-t3257465
zeeshanalpha said:
NJH47F 7.1.2 Nougat Stock Firmware
Click to expand...
Click to collapse
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Didn't even see that, guess there's no explanation
SlimSnoopOS said:
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Where ? No I didnt flash Pixel images why would I even do that to my N6P. It was the latest stock nougat firmware for N6P which I flashed !
I cycled through different ROMs thinking that it might solve the issue but nothing happend. I even tried flashing radio images but no sign of wifi. Not getting the exact problem
Tried through different forums
---------- Post added at 05:16 AM ---------- Previous post was at 05:13 AM ----------
SlimSnoopOS said:
Could you explain why you flashed a Pixel XL factory image or radio onto your Nexus 6P?
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Its actually 7.1.2 N2G48C if I was wrong cuz I reverted back into RR and still no signs of Wifi.
---------- Post added at 05:20 AM ---------- Previous post was at 05:16 AM ----------
coremania said:
Do you have any efs partition backup with TWRP, if yes, try to restore it with TWRP.
Edit: for some guys it help to remove simcard and reboot the phone without, don't ask me why.
Edit: and some solutions from a n6 thread with the same issue, if the issue still persist
https://forum.xda-developers.com/nexus-6/help/wifi-mac-address-200000000000-t3257465
Click to expand...
Click to collapse
My EFS backup is done after flashing the stock firmware. But even the stock OS isn't showing any signs of WiFi so I guess if I restore through its of no use I still won't get the WiFi bruh
zeeshanalpha said:
My EFS backup is done after flashing the stock firmware. But even the stock OS isn't showing any signs of WiFi so I guess if I restore through its of no use I still won't get the WiFi bruh
Click to expand...
Click to collapse
Maybe I'm not understanding you correctly, but the modemst1 and modemst2 partitions are not part of any Google image, they are protected and unique to your phone. You may or may not have backed them up previously with TWRP. If you did back them up, you can restore just those two partitions. If you did not back them up previously, you can try deleting them and letting them rebuild as in this article.
v12xke said:
Maybe I'm not understanding you correctly, but the modemst1 and modemst2 partitions are not part of any Google image, they are protected and unique to your phone. You may or may not have backed them up previously with TWRP. If you did back them up, you can restore just those two partitions. If you did not back them up previously, you can try deleting them and letting them rebuild as in this article.
Click to expand...
Click to collapse
Didn't work bro
But unique method though. I literally had high hopes on this technique of restoring efs files I.e modemst1 and 2
Still facing the same WiFi loading issue and disabled on the main screen. I really dont wanna give up on my N6P its a lucky one for me
I hope I get the solution early for this
Thanks btw
zeeshanalpha said:
Didn't work bro
But unique method though. I literally had high hopes on this technique of restoring efs files I.e modemst1 and 2
Still facing the same WiFi loading issue and disabled on the main screen. I really dont wanna give up on my N6P its a lucky one for me
I hope I get the solution early for this Thanks btw
Click to expand...
Click to collapse
So you used the fastboot method and deleted the partitions, and it completed on reboot (re-wrote) the partitions... what confirmation did you get it was successful?
At this point, and in order to rule out hardware, you should fastboot format system, userdata and cache. Use the latest 8.0 full image with the included flash-all.bat script. Until you do this (including formatting the partitions) you cannot rule out the motherboard. If this does not fix it, the problem is hardware related and not worth repairing on a used 6P.
v12xke said:
So you used the fastboot method and deleted the partitions, and it completed on reboot (re-wrote) the partitions... what confirmation did you get it was successful?
At this point, and in order to rule out hardware, you should fastboot format system, userdata and cache. Use the latest 8.0 full image with the included flash-all.bat script. Until you do this (including formatting the partitions) you cannot rule out the motherboard. If this does not fix it, the problem is hardware related and not worth repairing on a used 6P.
Click to expand...
Click to collapse
Is 8.0 full image stable ? I guess its still in developer preview right ? Get me the download link if possible.
Thanks