Database Develop

Questions about verizon PRL on sprint.

I'm new to CDMA tech, I used to be a GSM guy. so this is all new to me. From my understanding PRL is some sort of file that allows you to use specific towers or something, and My intention is to use Verizon towers on my sprint phone as they have great coverage at my location. I did some researching about PRL in this forum and I'v come to the conclusion it is impossible to use a Verizon PRL on a sprint HTC one unless it is rooted. If that is the case I wish to know the answers to the following.
1.Is it possible to use verizon prl on the Sprint htc one without root? "although I know what your answer might be "
2.If root is required. What do you think is the most noob friendly guide to rooting my Sprint Htc One
3.Would I be able to unroot my device once I root it? in case of future sales?
any link you provide me would be great! I'd really appreciate your help and I'll continue to scout the form for more information. I honestly prefer noob guides to rooting such as one click methods to rooting and what not. But if there is no such thing for the Sprint htc one I completely accept that and will be willing to work with whatever guide you think is friendly to new CDMA users.

Cdma is nothing like GSM. You can't use a sprint phone on Verizon or vice versa because the carriers have to register your phone ESN to allow it on its network. Neither carrier will do that. A Cdma phone is locked to the network it is sold on, and its mvno partners like Ting which uses Sprint's network.

thorishere113 said:
1.Is it possible to use verizon prl on the Sprint htc one without root? "although I know what your answer might be "
Click to expand...
Click to collapse
Not as far as I know
2.If root is required. What do you think is the most noob friendly guide to rooting my Sprint Htc One
Click to expand...
Click to collapse
all you need to do is unlock it via htcdev, and flash a custom recovery via 'fastboot flash some-recovery.img' - then flash a superuser zip (though the custom recoveries seem to include this function now)
3.Would I be able to unroot my device once I root it? in case of future sales?
Click to expand...
Click to collapse
Yes, you'll only be able to completely restore it if you are s-off (remove tampered flag, etc.)
---
Notes:
- I'm sure you know this (since you signed a contract that says this), but roaming above 300Mb/month gives sprint the right to terminate your contract at any time without notice
- You'll be able to get more information in the sprint forums
- There's plenty of documentation on root, s-off, changing PRL, restoring to stock throughout the forums.

[Q] Trying to painstakingly make my Unlocked M7 work on Verizon from T-Mobile

I understand that Verizon LTE allows for GSM phones now. I've upgraded to the M8 so I decided to give my friend on Verizon my old Unlocked M7 (his phone broke and he has a Micro SIM card, specifially a LTE one from Verizon.)
Background info:
When I upgraded to the M8, I kind of just left my M7 abandoned on a dusty shelf (I know, what a terrible person I am.); SIM card still inside of it and everything. The first problem I ran into was that the IMEI of my M7 is still apparently financed... Specifically on my T-Mobile account. I don't know why. I got it from some guy who had used it on AT&T and it worked perfectly. I assumed the IMEI finance thing was some kind of a false positive seeing as even with my old SIM, it has no service. Unless T-Mobile is really screwing me over (which I read is a problem with Unlocked T Mob phones).
I went ahead and popped my friend's SIM card in and it could read his number and all the APNs and what not (I assume that's all stored on the SIM?), but, alas, there was no kind of service. When searching for service, it only found T-Mobile and AT&T networks.
After many hours of tinkering with it to get S-Off, I decided I would change the CID to VZW__001 and the MID to PN317000 (each, respectively, the CID and MID for Verizon HTC One devices). I assumed that if I gave it a Verizon Hboot with a Verizon radio img that it might get service. After I did that, I ran a the stock Verizon 4.4.3 RUU and it failed to do something with the system (I dont rememeber what the error was, but I'm guessing the System partition was rejecting it due to it being for Verizon phones or something). Then, finally, at the end, it got to the rcdata part and failed and came up with an error that said something like "something error: 54 partition is too large". I tried to reboot only to find that I had soft bricked it. From there, I flashed the firewater hboot for the Verizon M7 variant and it fixed the soft boot, however, after flashing the newest TWRP for Verizon phones, it seems there was no OS that would boot despite the fact that something was taking up about 1.2GB on the system partition. I attempted to flash the unofficial CM12 for Verizon variants and it kept failing to mount the system partition, which was weird because it wipes just fine and you can even repair it (as long as you do it before trying to flash the ROM). Now, I decided I would flash the TWRP for the Unlocked variant and download CM12 for M7_UL. It installed fine and boots fine. Up until it gets to the point where it shows the homescreen. Launcher3 stops responding and the phone immediately restarts. That's where I'm at now and I'm unsure if the phone will ever even work on Verizon. I feel like my phone is having an identity crisis and can't figure out what the hell to do with all these mixed carrier signals. In it's heart it knows it's an Unlocked phone... But it knows why it must become Verizon. Yes, I just personified a cellphone.
Anyway, is all this futile or is there actually a way to make the damn thing work on Verizon LTE?

RedDeadDorito said:
I understand that Verizon LTE allows for GSM phones now.
Click to expand...
Click to collapse
Are you sure? Afaik, Verizon is CDMA and will only works with CDMA phones.
The first problem I ran into was that the IMEI of my M7 is still apparently financed... Specifically on my T-Mobile account. I don't know why. I got it from some guy who had used it on AT&T and it worked perfectly.
Click to expand...
Click to collapse
What do you mean by financed? Is the IMEI clean or is it blacklisted? If the IMEI is blacklisted your phone will never connect to a network again.
I assumed the IMEI finance thing was some kind of a false positive seeing as even with my old SIM, it has no service.
Click to expand...
Click to collapse
Is your old SIM still linked to an account? If your carrier gave you a new sim for your M8 they probably disabled that one. If not disabled that could confirm your IMEI is blacklisted
I went ahead and popped my friend's SIM card in and it could read his number and all the APNs and what not (I assume that's all stored on the SIM?), but, alas, there was no kind of service. When searching for service, it only found T-Mobile and AT&T networks.
Click to expand...
Click to collapse
Your M7 is GSM and Verizon is CDMA, not sure if it should see any network with a Verizon sim card and afaik, sim card of CDMA carriers like Verizon and Sprint only are for LTE connectivity only.
After many hours of tinkering with it to get S-Off, I decided I would change the CID to VZW__001 and the MID to PN317000 (each, respectively, the CID and MID for Verizon HTC One devices). I assumed that if I gave it a Verizon Hboot with a Verizon radio img that it might get service. After I did that, I ran a the stock Verizon 4.4.3 RUU and it failed
Click to expand...
Click to collapse
You can not convert a GSM HTC One to a CDMA variant, there are some hardware differences and not even the same partition table. On aa M7_U or UL you can only use M7_U or UL MID (starting with PN071)
I flashed the firewater hboot for the Verizon M7 variant
Click to expand...
Click to collapse
Same here, 1 step closer to a hard brick --> do not flash firmware from an incompatible variant on your phone.
TWRP for Verizon phones
Click to expand...
Click to collapse
Same again, if your phone is a M7_U/UL only use a M7_U/UL recovery
flash the unofficial CM12 for Verizon variants and it kept failing to mount the system partition,
Click to expand...
Click to collapse
Verizon variant doesn't have the same partition table. /system of a GSM variant is partition mmcblk0p35 and CDMA variant /system is mmcblk0p37. So you are flashing /system in /data. Use only rom compatible for you variant.
Now, I decided I would flash the TWRP for the Unlocked variant and download CM12 for M7_UL.
Click to expand...
Click to collapse
Finally something that makes sense
It installed fine and boots fine. Up until it gets to the point where it shows the homescreen.
Click to expand...
Click to collapse
Might be caused by your twrp version (refer to cm wiki)
Maybe because your partitions are now corrupted, should restore your CID/MID and flash a full M7_UL ruu at this point.
I feel like my phone is having an identity crisis
Click to expand...
Click to collapse
I wonder why....
In it's heart it knows it's an Unlocked phone...
Click to expand...
Click to collapse
Not exactly. In its heart, it knows it's an M7_UL and no amount of flashing stuff will make it a M7VZW
Restore your phone with a M7_UL RUU and bring it to Verizon and see what they will say about GSM phones on their network.

alray said:
Are you sure? Afaik, Verizon is CDMA and will only works with CDMA phones.
What do you mean by financed? Is the IMEI clean or is it blacklisted? If the IMEI is blacklisted your phone will never connect to a network again.
Is your old SIM still linked to an account? If your carrier gave you a new sim for your M8 they probably disabled that one. If not disabled that could confirm your IMEI is blacklisted
Your M7 is GSM and Verizon is CDMA, not sure if it should see any network with a Verizon sim card and afaik, sim card of CDMA carriers like Verizon and Sprint only are for LTE connectivity only.
You can not convert a GSM HTC One to a CDMA variant, there are some hardware differences and not even the same partition table. On aa M7_U or UL you can only use M7_U or UL MID (starting with PN071)
Same here, 1 step closer to a hard brick --> do not flash firmware from an incompatible variant on your phone.
Same again, if your phone is a M7_U/UL only use a M7_U/UL recovery
Verizon variant doesn't have the same partition table. /system of a GSM variant is partition mmcblk0p35 and CDMA variant /system is mmcblk0p37. So you are flashing /system in /data. Use only rom compatible for you variant.
Finally something that makes sense
Might be caused by your twrp version (refer to cm wiki)
Maybe because your partitions are now corrupted, should restore your CID/MID and flash a full M7_UL ruu at this point.
I wonder why....
Not exactly. In its heart, it knows it's an M7_UL and no amount of flashing stuff will make it a M7VZW
Restore your phone with a M7_UL RUU and bring it to Verizon and see what they will say about GSM phones on their network.
Click to expand...
Click to collapse
Verizon uses GSM for LTE phones, the only problem is (and I just figured this out) that Verizon decided they don't want any phones that didn't come from them... so doing what I'm doing is never going to work since it isn't a Verizon branded HTC One (I'm guessing that's why they made subtle hardware changes, those bastards). However, their phones *should* work just fine on other carriers (cause other carriers aren't whiny babies that don't want unbranded phones on their network).
That bit about there being different partitions for Verizon is prolly the reason why all this doesn't work.
Screw you, Verizon, for being so over protective of your devices.
Screw you, T-Mobile, for never properly taking my old M7 off my account (They were probably butthurt that the phone was bought from a 3rd party).
Guess I'm just gonna have to sell it as an awesome MP3 player.

RedDeadDorito said:
Verizon uses GSM for LTE phones, the only problem is (and I just figured this out) that Verizon decided they don't want any phones that didn't come from them... so doing what I'm doing is never going to work since it isn't a Verizon branded HTC One (I'm guessing that's why they made subtle hardware changes, those bastards). However, their phones *should* work just fine on other carriers (cause other carriers aren't whiny babies that don't want unbranded phones on their network).
That bit about there being different partitions for Verizon is prolly the reason why all this doesn't work.
Screw you, Verizon, for being so over protective of your devices.
Screw you, T-Mobile, for never properly taking my old M7 off my account (They were probably butthurt that the phone was bought from a 3rd party).
Guess I'm just gonna have to sell it as an awesome MP3 player.
Click to expand...
Click to collapse
Yes they use GSM signals for the LTE but it is also well known that they have to put the phone on their network for it to work. Also the Antenna in the device has to be able to use their signal bands. Mainly as GSM is only a secondary antenna in the device.The fact that it was not taken off your account has nothing to do with it. If the 3rd party didnt pay their bill then the phone gets blacklisted. Nothing can be done there.

Question about sideloading OTA's

I got my nexus 6 from Google and am using Cricket as my cell provider. From what I gathered carriers are handling the ota's? So I went ahead and decided to sideload a 5.1 update.zip that came from At&t because I didn't want to unlock my bootloader and Cricket doesn't seem to be sending out updates. It works but my carrier is reading as At&t instead of Cricket in which I suspect because its a At&t ota. I want to go back to it saying Cricket instead so I was wondering if I was to just go ahead and flash the update from google's webpage and unlock my bootloader will I be back to stock (the one that it came with from google) and have my right carrier logo be shown? Also I wanted to relock my bootloader so I just need to follow the steps seen in the forums in order to do so? Thanks for your help!

ed12435 said:
I got my nexus 6 from Google and am using Cricket as my cell provider. From what I gathered carriers are handling the ota's? So I went ahead and decided to sideload a 5.1 update.zip that came from At&t because I didn't want to unlock my bootloader and Cricket doesn't seem to be sending out updates. It works but my carrier is reading as At&t instead of Cricket in which I suspect because its a At&t ota. I want to go back to it saying Cricket instead so I was wondering if I was to just go ahead and flash the update from google's webpage and unlock my bootloader will I be back to stock (the one that it came with from google) and have my right carrier logo be shown? Also I wanted to relock my bootloader so I just need to follow the steps seen in the forums in order to do so? Thanks for your help!
Click to expand...
Click to collapse
google sends out all otas, not carriers. carriers have nothing to do with it. its when you put in your sim card, that the rom knows whatvyou are using. you can use any of the factory images, and any if them will work on any carrier. yours says att because cricket is using atts lines.

That's what I figured, the only thing that is bugging me about it is that my friend who is using cricket also next to me is using a nexus 5 and cricket as well and there's is showing up as cricket. I don't get how mine is connecting to At&t and theirs not. I may need to redo my apns perhaps? Thanks for your help

ed12435 said:
That's what I figured, the only thing that is bugging me about it is that my friend who is using cricket also next to me is using a nexus 5 and cricket as well and there's is showing up as cricket. I don't get how mine is connecting to At&t and theirs not. I may need to redo my apns perhaps? Thanks for your help
Click to expand...
Click to collapse
if att isnt billing you, but cricket is, i wouldnt even worry about it. it is a cricket sim, right? it could just be a lollipop bug thats showing you the network instead of your provider.

Problem solved
I unlocked my bootloader, then manually installed the stock 5.1 update following a guide found in the forums. Afterwards I relocked my bootloader ( I like the added security) following another guide in the forums and sure enough the cricket logo is back. I guess sideloading the At&t update made the phone think it was running through At&t radio's? Throughout the day I started to notice problems with my phone thinking it was on At&t's network (idk why) but now everything is working well and even getting a stronger signal. I didn't receive the 5.1 update in over a month and figured somehow it didn't get pushed to me. Either way I'll probably wait awhile longer next time to see if I get 5.1.1 (or whatever the next update will be for the Nexus 6) pushed to me once its released. Thanks for all your help, hopefully if anyone using a Nexus 6 on cricket runs into this problem it will help.

Verizon SIM, T-Mobile ROM, when should I expect OTA updates?

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)

Flashing Roms For Other Carriers.

So I am under the impression reading around on here that even if I SIM unlock a sprint M8 and try to use on T-Mobile' network it wont work. Or maybe to be more exact it doesn't get 4G ect, and will be super limited. Well someone told me that is because of the ROM being carrier apecific and since they M8 is the same for all carriers you can flash a T-Mobile ROM on a Sprint M8 and it will work just fine. Is there any truth to this?

Asterik216 said:
So I am under the impression reading around on here that even if I SIM unlock a sprint M8 and try to use on T-Mobile' network it wont work. Or maybe to be more exact it doesn't get 4G ect, and will be super limited. Well someone told me that is because of the ROM being carrier apecific and since they M8 is the same for all carriers you can flash a T-Mobile ROM on a Sprint M8 and it will work just fine. Is there any truth to this?
Click to expand...
Click to collapse
No it is not. You can only use cross variant stock roms if you have super cid and s-off too. Still i would suggest you to look for more clear answer but as far as i know if the cid and mid of your phone doesnt match with the software version you want to flash it wont do any good.

It's my understanding that you must use a Sprint compatible ROM, even if you are Super CID and SIM unlock for use on another carrier.
Sent from my HTC 10

Asterik216 said:
So I am under the impression reading around on here that even if I SIM unlock a sprint M8 and try to use on T-Mobile' network it wont work. Or maybe to be more exact it doesn't get 4G ect, and will be super limited. Well someone told me that is because of the ROM being carrier apecific and since they M8 is the same for all carriers you can flash a T-Mobile ROM on a Sprint M8 and it will work just fine. Is there any truth to this?
Click to expand...
Click to collapse
Never do that .. Even though you can flash tmobile rom on sprint , BUT NEVER FLASH A RUU . flashing a gsm ruu on cdma device will brick your phone .
Flashing t mobile rom doesn't unlock it or make it work with tmobile .
AFAIK Domestic sim unlocking is not possible for sprint variant.
Sent from my MotoE2(4G-LTE) using Tapatalk