My wife and I both have an Inspire 4G. Both on the same contract and both on the same version of ROM and software. Now here's the thing, she recieved the "sideload" update on her phone but I haven't...WTF? how is AT&T rolling out this update?
I never even received a "push" notificiation of the OTA Update (1.84.502.11). I ended up just grabbing the update via my city's free WiFi this morning.
No word yet on the AT&T "sideload" update. I'm not overly concerned, since the Wonder Machine installs my free Amazon Apps without a hitch.
I been on that version for a while and sitll don't have the sideload option.
I just got off the phone with AT&T about the "Allow Unknown Sources" being on my wife’s phone but not mine. Apparently they are having issues internally with pushing out this update. They are working on the problem and those who have not received the update will....eventually.
Hey everyone I've run into a problem and have not clue how to fix it. I had purchased a Rogers s3 and unlocked it with an unlock code and currently use it on the Bell network. I had my phone rooted so when the service provider was rolling out the jelly bean updates I missed mine. So I flashed the new OS onto the phone myself (the one from Bell) and it seems I no longer get LTE speeds. I was wondering if anyone else has gotten these problems with the new OS. Also should I be installing Rogers updates or Bell updates? It's the same model.
Lastly a buddy recommended juice defender to help with the battery life. When I use it at times when I unlock my phone to use it I don't get any reception whatsoever or the data doesn't turn back on. I need to reboot time get service and data back.
So I was helping a friend with his Pixel he bought from the Google Store. He wanted to install the new update. However, when I took a look at his build number, it was NDE63X not NDE63V. I remind you that he bought his phone directly from Google and not from Verizon. I do remember that when he set it up and put his Verizon sim in, he had to uninstall a couple Verizon apps. Could this have anything to do with him being on the wrong build? Also how can I get him off the Verizon build? Can I just sideload the NDE63V OTA or do I have to use a factory image?
The November update sent X to google store phones if they had a Verizon sim in them.
Same thing here, play store device but on Verizon, when the OTA pushed it was X.
atlp99 said:
The November update sent X to google store phones if they had a Verizon sim in them.
Same thing here, play store device but on Verizon, when the OTA pushed it was X.
Click to expand...
Click to collapse
If we bought a phone from Google, have a Verizon sim, and are on build nde63x, can we and should we push a different build? Also, can we push the new build?
kenjoma said:
If we bought a phone from Google, have a Verizon sim, and are on build nde63x, can we and should we push a different build? Also, can we push the new build?
Click to expand...
Click to collapse
You can flash another build, but there isn't a reason to. Only reason I can think is relevant right now is you want to get to the new ota that got pushed to Canadian phones for the new features. In that case you would need to move to the nde63v build, then sideload ota. If you're not doing that, then there is no reason.
If you are concerned with the "Verizon Pixel vs Google Pixel" discussion, then you have bought into the internet hype. Tsst. Your Google store Pixel is identical to a Verizon Pixel. There is a server side whitelist / blacklist that gives users the ability to toggle oem unlock or not(based on CID I think). That is all. Firmware (nde63x vs nde63v) is independent of where you bought the phone from or whether you can unlock your bootloader. Nde63x likely has some minor changes in it that Verizon and Google think will work better on their network (wifi calling changes, advanced calling tweaks, or something else). Pop a ATT or Tmobile sim in your phone and you will eventually be prompted to update to the unlocked build. Pop your VZW sim back in and it will try to go back. No big deal.
I have a bl unlocked Verizon Pixel, flashed the V build over P, then sideloaded the Canadian J build just for the new features. Now I'm on J with root and unlocked bl on Verizon. . So yeah, you can do whatever you want.
dbrohrer said:
You can flash another build, but there isn't a reason to. Only reason I can think is relevant right now is you want to get to the new ota that got pushed to Canadian phones for the new features. In that case you would need to move to the nde63v build, then sideload ota. If you're not doing that, then there is no reason.
If you are concerned with the "Verizon Pixel vs Google Pixel" discussion, then you have bought into the internet hype. Tsst. Your Google store Pixel is identical to a Verizon Pixel. There is a server side whitelist / blacklist that gives users the ability to toggle oem unlock or not(based on CID I think). That is all. Firmware (nde63x vs nde63v) is independent of where you bought the phone from or whether you can unlock your bootloader. Nde63x likely has some minor changes in it that Verizon and Google think will work better on their network (wifi calling changes, advanced calling tweaks, or something else). Pop a ATT or Tmobile sim in your phone and you will eventually be prompted to update to the unlocked build. Pop your VZW sim back in and it will try to go back. No big deal.
Click to expand...
Click to collapse
So just to be clear (cause I don't wanna **** up my friend's phone) I can side load the NDE63v OTA on the NDE63x pixel? Or do I have to use some other method?
FrostedWaffle said:
So just to be clear (cause I don't wanna **** up my friend's phone) I can side load the NDE63v OTA on the NDE63x pixel? Or do I have to use some other method?
Click to expand...
Click to collapse
No. I haven't tried it myself but others reported side loading 63v from 63x errors out. YMMV on that. The otas that are available are good for moving from a certain build to another. Not any build to 63v. I don't think you can get the ota that takes you from 63x to 63v.
If it was my friends phone, I would flash the factory image if you want to move to the other build. Edit the flash all script so it doesn't wipe data if he wants to keep apps and settings.
dbrohrer said:
No. I haven't tried it myself but others reported side loading 63v from 63x errors out. YMMV on that. The otas that are available are good for moving from a certain build to another. Not any build to 63v. I don't think you can get the ota that takes you from 63x to 63v.
If it was my friends phone, I would flash the factory image if you want to move to the other build. Edit the flash all script so it doesn't wipe data if he wants to keep apps and settings.
Click to expand...
Click to collapse
OK thank you I will try that.
I purchased my OnePlus 7 Pro from T-Mobile. I am switching over to AT&T today. My question is, since I am switching to a different carrier, will i still be receiving OTA Updates from T-Mobile since the phone contains their firmware/ROM version of OOS or will the updates be from OnePlus? All this may be moot if I decide to convert over to the international version, but I would still like to know.
You should switch to the international firmware. That way you get "ota" straight from oneplus and also get rid of the T-Mobile bloat thats on the phone.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-international-firmware-install/
gunfan said:
You should switch to the international firmware. That way you get "ota" straight from oneplus and also get rid of the T-Mobile bloat thats on the phone.
https://www.xda-developers.com/t-mobile-oneplus-7-pro-international-firmware-install/
Click to expand...
Click to collapse
I actually already had it converted, then i had to go back to the T-Mobile firmware in order to SIM unlock my phone so I could switch carriers. I was considering staying with the T-Mobile firmware only because it's such a pain in the a$$ to have to install the backup and re-sign in on all my apps, and re-setup the phone. But the advantage of converting to international and getting updates right away is really making me lean towards reinstalling the international firmware. One thing I did notice though was that on the international version my 4G LTE signal lost signal frequently, but once I went back to the T-Mobile firmware I didn't lose signal as much, so I'm not sure what is going on with that. I don't know if anyone else has experienced weaker signal on the international version but it should definitely be addressed because I 100% was getting a weaker signal on the international version, that is part of the reason why I decided to switch to AT&T because I thought my T-Mobile coverage sucked, well it turns out that probably wasn't the case.
hey there as title says i brought phone from verizon to straight talk,was wondering if i were to flash TracFone's software on if i should start receiving updates as they roll out? sense now when checking says network unavailable sense im no longer on verizon phone is a samsung s10+