I have an X4 Android One and recently switched from stock to Pixel Experience, and now my phone won't work with a Verizon SIM.
While I was using the stock OS it worked fine swapping SIMs from Fi to Verizon. When I unlocked the bootloader and switched to Pixel Experience, the Verizon SIM no longer works.
Could this be due to the Fi vs Retail firmwares?
I went to Verizon and they couldn't figure it out, and even the reps own SIM card didn't work. It's definitely something to do with my phone. I tried LineageOS and that didn't work either. It's odd that it still works fine on Google Fi.
InTheCatBoxAgain said:
I have an X4 Android One and recently switched from stock to Pixel Experience, and now my phone won't work with a Verizon SIM.
While I was using the stock OS it worked fine swapping SIMs from Fi to Verizon. When I unlocked the bootloader and switched to Pixel Experience, the Verizon SIM no longer works.
Could this be due to the Fi vs Retail firmwares?
I went to Verizon and they couldn't figure it out, and even the reps own SIM card didn't work. It's definitely something to do with my phone. I tried LineageOS and that didn't work either. It's odd that it still works fine on Google Fi.
Click to expand...
Click to collapse
Could try reflashing these from retail firmware
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my ocean using XDA Labs
You've probably checked already, but if not, make sure your APN is set to VZWINTERNET. I have had issues with multiple ROMs losing this setting at times and switching me to Straight Talk or Xfinity. Which them breaks mobile data at least until I flip it back to Verizon. I haven't used Pixel Experience, so it may not be an issue on it.
Related
Sorry, i'm not sure how the OTA's work on the Nexus devices, so I have to ask (and haven't found the right discussions which talk about this)...
I have an ATT branded Nexus 6 which has been bootloader unlocked, OEM partition wiped, and flashed with the "for T-Mobile" LYZ28J image. I am using a Verizon SIM in it.
Since there are posts of T-Mobile pushing LYZ28K I was wondering, will get get this OTA? if so when (i.e. does it it matter than I have a Verizon SIM in there when it comes to OTA's? Or do I manually need to load it?
It doesnt matter that it has a vzw sim in it. If youre stock, you may get it, and you can apply it - but when? Nobody can tell you that, you'll get it when you get it.
If you are waiting for Tmo specific firmware on VZW service, that isn't going to happen - you'll never get that since...well...you dont have TMo service...
Lol what's the reason behind an AT&T branded phone with T-Mobile Rom and Verizon sim? Personally I would just manually do it, like the dude with the hilarious name above me said you may get it you may not. If you want it just go manual.
^^ exactly.
Thats what I've always done - if i want it (and since I'm never stock) I have to manually flash the firmware, make my own no-enforced encryption boot.img (kudos to the kitchen) flash that, and start all over.
Thats how it is, I'm used to it. OTA are too slow, IMO, anyway.
EDIT:
I use this name universally online - any forum you see it, XBL, GitHub, reddit... it's me. lol
The Stig 04 said:
Lol what's the reason behind an AT&T branded phone with T-Mobile Rom and Verizon sim?
Click to expand...
Click to collapse
Long story short... its a work supplied device. I asked for unlocked/unbranded and got the ATT branded (but sim unlocked). My primary work line is Verizon, backup/test line is T-MO.
We have others that will likely be in the same boat (ATT branded, sim unlocked, but using other provider).. who are not techie. So rather than flashing or side loading the OTA (which I easily could), I'm waiting to see what happens.
I'm more curious *IF* I should get the update in this state. and if the mix of rom vs sim might cause any delays/issues.
Bottom Line. Verizon and ATT don't usually OTA for 3 months after update release. Once the factory image for Sprint, USC, International drops you can fastboot flash that They gonna use the same and it will work. T-Mobile and FI work better with their drop just because of WiFi calling.
I'd say that because you're using VZW service, it makes absolutely no difference what branding the phone has and doesn't matter what carrier it was purchased for.
If it uses VZW service, you'll only get OTAs that are for that service. You won't get Tmo specific OTAs for a device being used on VZW - when the OTAs are pushed out they are done so by the service the device is registered as using. I don't think you would ever get said OTAs since the device wouldn't need them.
iRub1Out said:
I'd say that because you're using VZW service, it makes absolutely no difference what branding the phone has and doesn't matter what carrier it was purchased for.
If it uses VZW service, you'll only get OTAs that are for that service. You won't get Tmo specific OTAs for a device being used on VZW - when the OTAs are pushed out they are done so by the service the device is registered as using. I don't think you would ever get said OTAs since the device wouldn't need them.
Click to expand...
Click to collapse
Thank you. And that is what I'm thinking, and why I'm asking... because I'd also seen talk about the SIM in the Nexus 6, or the carrier the phone is on, impacting some of the Nexus 6 updates in the past.
But I also remember my Sister-In-Law using an XT1053 on ATT, who did get XT1053 updates.. SO I wasn't completely sure how the nexus updates worked.
Yes. If leave the sim in will get the Verizon OK'd OTA. That has been up to 3 months after the image was posted. Either remove sim and try to force OTA from Google or manually flash the image. We end up always manually flashing due to having root.. 3-5 minutes tops.
iRub1Out said:
It doesnt matter that it has a vzw sim in it.
Click to expand...
Click to collapse
That's not accurate.. On every other android phone it is accurate but not in the nexus 6.
Usually with a GSM phone, the update is pushed by the oem and your current build determined which update you got.. For example, my Three UK s3 would get the Three UK branded rom update. Even if I had an O2 UK sim in it.. If I then flashed a Vodafone UK rom, I would then get those updates.
With the nexus 6 though, this has changed.. For Verizon and T-mobile users, Google now uses the sim to identify which update to get.. They both were sent with an unbranded stock rom then later on, depending on the simcard, got either a t-mob or vzw update.
The problem is though, that each update will only install on a specified build.. So a vzw update will never install on a t-mob rom or vice versa, so it does matter if the build is one carrier and the sim is another as it will never get an update.
That's what I meant, I probably should have worded that differently.
I meant that even though it is using Verizon service you only get updates for Verizon service. If it's branded for X carrier that won't matter - the service its using is what you'll get updates for.
I apologize about that that was a poor choice of wording on my part.
And just an update.... tonight, I got prompted for a 28meg update. After the update I'm on LYZ28K.
So I guess to answer my own question...
Yes, an ATT Branded Nexus 6 flashed T-Mobile ROM with VZW SIM installed will get updated, and stay on the T-Mobile rom.
That is good.
KidJoe said:
And just an update.... tonight, I got prompted for a 28meg update. After the update I'm on LYZ28K.
So I guess to answer my own question...
Yes, an ATT Branded Nexus 6 flashed T-Mobile ROM with VZW SIM installed will get updated, and stay on the T-Mobile rom.
That is good.
Click to expand...
Click to collapse
Should get the Verizon/ATT (Generic ) rom if have Verizon sim. Hopefully you unlocked before taking update. If locked and it bootloops your only option is RTA.
prdog1 said:
Should get the Verizon/ATT (Generic ) rom if have Verizon sim. Hopefully you unlocked before taking update. If locked and it bootloops your only option is RTA.
Click to expand...
Click to collapse
Yup. I unlocked. Actually when I got it, I unlocked it, rooted, cleared the OEM partition (backed it up first), then flashed the T-Mobile rom.... and left it unlocked (but not rooted since I'm using for work)
I've spent the last few days trying to get a correct answer on this. The pages I've read say unbranded nexus 6 doesn't get volte on att. The phone I'm using was purchased through att with att boot screen and logo on the back. Wouldn't this make it a branded phone? My att lg g4 had volte, first I just put the sim card in the nexus hoping to keep the feature, but it didn't work. Today I updated them with my nexus imei and still doesn't work.
Does no version of the nexus 6 get volte on att?
Thanks
Your N6 would be a branded model, but the carrier-specific factory images are only for Android 5.x. The Android 6.x factory images are all universal, and OEM modifications on Android 6.x are only installed if a SIM from that carrier is installed prior to running through the setup wizard.
As to your other question, I can't answer that, as I am on Straight Talk and thus don't have VoLTE.
Strephon Alkhalikoi said:
Your N6 would be a branded model, but the carrier-specific factory images are only for Android 5.x. The Android 6.x factory images are all universal, and OEM modifications on Android 6.x are only installed if a SIM from that carrier is installed prior to running through the setup wizard.
As to your other question, I can't answer that, as I am on Straight Talk and thus don't have VoLTE.
Click to expand...
Click to collapse
This means I need to wipe my phone for this feature to work?
dpalmer76 said:
This means I need to wipe my phone for this feature to work?
Click to expand...
Click to collapse
VoLTE is not supported by AT&T on the Nexus 6. AT&T puts out specific updates for devices they support VoLTE on and the N6 isn't one of them. I've confirmed this with multiple AT&T reps, salesmen, etc.
The only thing wiping your phone will get you is the My AT&T and AT&T All access data monitor apps which you can go get from the play store anyway.
ok so cleaning my house the other day i came across a old phone of mine the Moto X XT1093 Variant (US Cellular) so as i suspected i had unlocked the BL in the past and installed TWRP and i had the stock 5.1 rom and it was rooted, i guess at some point i also installed Xposed Framework...anyways...according to the US Cellular website, this phone is already sim unlocked...so i was thinking , ok cool i can pop a sim from some random prepaid CDMA carrier and it should work...well i flashed dirty unicorns 6.0 xt1095 rom on it and its stable, the US Cellular sim is still in there and its getting a data signal, obviosuly account is off, but then i started reading and i got worried...is it even possible to flash another rom on this phone and it work? like i mean this is a CDMA phone, but i read that all XT1095 is GSM, so is there some rom i can flash that will support some sorta CDMA prepaid? any help or advice here would be appreciated....
https://forum.xda-developers.com/mo...m-xt1096-verizon-flashable-stock-rom-t3327345
I use it with the At&t prepaid sim. I'll look and see if I have some of the files I used to lock on the cdma networks...
DeimosPhobos said:
ok so cleaning my house the other day i came across a old phone of mine the Moto X XT1093 Variant (US Cellular) so as i suspected i had unlocked the BL in the past and installed TWRP and i had the stock 5.1 rom and it was rooted, i guess at some point i also installed Xposed Framework...anyways...according to the US Cellular website, this phone is already sim unlocked...so i was thinking , ok cool i can pop a sim from some random prepaid CDMA carrier and it should work...well i flashed dirty unicorns 6.0 xt1095 rom on it and its stable, the US Cellular sim is still in there and its getting a data signal, obviosuly account is off, but then i started reading and i got worried...is it even possible to flash another rom on this phone and it work? like i mean this is a CDMA phone, but i read that all XT1095 is GSM, so is there some rom i can flash that will support some sorta CDMA prepaid? any help or advice here would be appreciated....
Click to expand...
Click to collapse
Hi all,
I only recently got a new Moto G5s Plus from India (XT1804).
And the first thing I did was unlock the bootloader and root it, unfortunately the second thing I did was try to use Android Pay, at which time I found out that it's not supported with an unlocked bootloader.
In reverting the stock rom (as https://forum.xda-developers.com/showpost.php?p=73795447&postcount=37) it has obviously upset the dual SIM operation, and now I'm down to just SIM 1.
Is the XT1804 stock image available? Or any other ideas for getting the second SIM working again?
Regards,
Bevan
bevanweiss said:
Hi all,
I only recently got a new Moto G5s Plus from India (XT1804).
And the first thing I did was unlock the bootloader and root it, unfortunately the second thing I did was try to use Android Pay, at which time I found out that it's not supported with an unlocked bootloader.
In reverting the stock rom (as https://forum.xda-developers.com/showpost.php?p=73795447&postcount=37) it has obviously upset the dual SIM operation, and now I'm down to just SIM 1.
Is the XT1804 stock image available? Or any other ideas for getting the second SIM working again?
Regards,
Bevan
Click to expand...
Click to collapse
The only mess up happened when u ysed the commands erase modemst1 and erase modemst2.
Had same issue with oneplus2. Had tp get my motherboard replaces as I dint had the EFS backup using recovery.
I think that you will have to-
1. re install twrp and restore your efs if you have a backup,
2. if (1) dosent work, try flashing the available NON_HLOS.bin . {Practically itwould do little help}.
3. wait untill moto releases a firmware with updated modem ( NON-HLOS.bin ) file as it usually has the data stored in modemst1 and
modemst2
4. Relock bootloader and go to the service center. dont mention that u unlocked the bootloader . if they ask, simply deny.
PS -
1. Android Pay isnt yet available in INDIA
2. I hope that when you dial *#06#, u see IMEI1=some value and IMEI2=0
Thanks,
Yeah I guess I'll have to wait for the Oreo update later in the year.
I'm in Australia, which is why Android Pay works.
On doing the *#06# I do actually get two IMEI numbers reported, and I have actually had the second SIM work just recently, so maybe things aren't all so bad.
But it almost seems like it's not using all the bands available in AU (which pretty much matches the bands used in India, although AU has LTE B42 also).
I guess this is part of the modem flash.
So I'd just need the modem stuff from an Indian phone?
I guess I'll check what bands are reported and go from there.
Thanks again.
bevanweiss said:
Thanks,
Yeah I guess I'll have to wait for the Oreo update later in the year.
I'm in Australia, which is why Android Pay works.
On doing the *#06# I do actually get two IMEI numbers reported, and I have actually had the second SIM work just recently, so maybe things aren't all so bad.
But it almost seems like it's not using all the bands available in AU (which pretty much matches the bands used in India, although AU has LTE B42 also).
I guess this is part of the modem flash.
So I'd just need the modem stuff from an Indian phone?
I guess I'll check what bands are reported and go from there.
Thanks again.
Click to expand...
Click to collapse
Dear @bevanweiss,
As both of your IMEI's are intact, I don't believe that its any problem with your phone. your phone is totally fine
I highly recommend you to try switching your sim 1 (putting sim1 as sim2 and sim 2 as sim1)
Moto G has 4G support on both slots however, only 1 slot at a time can stay on 4g.
I say this, because in India , we have a service provider (Reliance Jio) who only provides 4G and no 2g or 3 g bands.
When I first booted up my phne with jio sim in slot 1 and vodafone india sim in slot 2, the voda sim got registered 1st and even though jio sim was in slot 1, it did not have any network. Even if i change prefered network type of sim 2 to 2g or 3g, there was no choice (option) to select 4g on sim 1 as 4g option was still visible in sim 2 settings.
Solution that i used,-
1.removed both sims and inserted just jio sim in slot 1 and rebooted.
2.set it (Jio sim 1) as 4g,
3.pulled out the tray and added voda to sim2
I will be really glad if any of these details help you.
I recommend you to backup your EFS partition asap.
Some interesting stats for some that have bought a Sprint to modify and run on a different carrier.
I have two Moto Z2F phones one of VzW and the other on Sprint BL, Sim Unlocked and rooted stock Rom.
I ran Speed test from home with both phones
Sprint XT1789-03 signal -111dBm Download speed 8.75 Mbps Sprint Sim 4g LTE
Sprint XT1789-03 signal – 99 dBm Download speed 13.85 Mbps Verizon Sim 4g LTE (Still Roaming)
Verizon XT1789-01 signal -110dBm Download speed 58 to 65 Mbps Verizon Sim 4g LTE not Roaming
I’m trying to stop the roaming on my Sprint with VzW sim. I tried a network reset and corrupted my VzW sim, I had to go to the VzW store and get a new sim.
I tried re flashing the stock rom too many times to remember.
I can not get the VzW firmware to work, it will flash ok but set-up keeps stopping so I’m using the Sprint firmware.
The phone is running great, BL unlocked, rooted, Safety net checks ok, I have good Titanium backups, TWRP backups that all work. I don’t know how I did it but the encryption correct with no errors in TWRP.
I just can't get the phone to stop roaming with my VzW sim.
I wonder when I put my Sprint sim in does the chdmod change back??
TwoBuells said:
Some interesting stats for some that have bought a Sprint to modify and run on a different carrier.
I have two Moto Z2F phones one of VzW and the other on Sprint BL, Sim Unlocked and rooted stock Rom.
I ran Speed test from home with both phones
Sprint XT1789-03 signal -111dBm Download speed 8.75 Mbps Sprint Sim 4g LTE
Sprint XT1789-03 signal – 99 dBm Download speed 13.85 Mbps Verizon Sim 4g LTE (Still Roaming)
Verizon XT1789-01 signal -110dBm Download speed 58 to 65 Mbps Verizon Sim 4g LTE not Roaming
I’m trying to stop the roaming on my Sprint with VzW sim. I tried a network reset and corrupted my VzW sim, I had to go to the VzW store and get a new sim.
I tried re flashing the stock rom too many times to remember.
I can not get the VzW firmware to work, it will flash ok but set-up keeps stopping so I’m using the Sprint firmware.
The phone is running great, BL unlocked, rooted, Safety net checks ok, I have good Titanium backups, TWRP backups that all work. I don’t know how I did it but the encryption correct with no errors in TWRP.
I just can't get the phone to stop roaming with my VzW sim.
I wonder when I put my Sprint sim in does the chdmod change back??
Click to expand...
Click to collapse
Have you tried keeping all partitions sprint except system and OEM? (Get to latest sprint stock, then flash latest Verizon system sparse chunks and OEM image). It worked flawlessly on my Sprint Z2 for AT&T
I flashed Verizon system sparse chunks and OEM image.
I changed the Fbat file to the new names (oem.img Sprint, oem.img_sparsechunk.0 VzW etc)
after booting I get "Setup keeps closing" error, I get the same error when I flash just the VzW firmware
I'n not sure whats doing that.
one thing to think about, over the weekend I called VzW. we tried to get my phone to stop roaming, Shutting of roaming helps but i lost all signal/service. the VzW tech said its because my phone is still active on Sprint. The Tech said that my phone is unlocked and will work on VzW but only once I cancel my Sprint account. That test was with the Sprint Firmware.
These are the file names from the VzW Firmware that I replaced with the rest of the Sprint Firmware.
I can’t get past the start menu. The error is “Seup keeps closing” I get the same error just flashing the stock VzW firmware.
I’ve tried downloading the VzW firmware from other sites/mirrors and get the same error msg after the firmware boots and I enter the setup.
oem.img_sparsechunk.0
oem.img_sparsechunk.1
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system_b.img_sparsechunk.0
system_b.img_sparsechunk.1