Develop Bugs

[Q][Marvelc] PagePlus EvDo info for working data

Update:
I've got data working (intermittently, probably due to EvDo vs 4g compatability) and once I'm able to get it going on a non-stock ROM I'll make a guide due to the shear level of effort this takes, you will need at least an intermediate level of android know-how to pull it off..
Question:
I'm currently working on transferring over my MetroPCS Wildfire S to PagePlus and have everything done but data (over radio). Does anyone have the PagePlus EPST Data Profile or EvDo data for this device?
Install Background:
Unlocked phone via HTCdev (hboot 1.10)
Installed TWRP 2.2.1 recovery
Installed CM9.1alpha9 (w/o backing up insert "durr" comments here) and gapps
Attempted to transfer phone to PagePlus (they got MED at their end, minor alpha bug kept me from pressing keys while attempting to activate phone in CM9.1alpha9)
Attempted manual PRL update using ##PRL# (CM9 alpha9 doesn't support/have implemented yet)
Attempted QRST PRL update (failed, HTCdev is only a partial unlock and DOESN'T unlock radio)
S-Off'd my phone (with goldcard, worked very well)
Attempted to install various Stock MetroPCS/Hense ROMs (all failed in TWRP)
Updated to TWRP 2.3.1.0 recovery (still no dice on ROMs, but at least ext4 works now)
Finally found a RUU stock ROM and did a full reset
Updated PRL using *228 (Roaming Issues
Attempted to reload TWRP (failed without an locked/unlocked indicator on bootloader (hboot 1.06))
Updated hboot (1.10.00001) and stock ROM
Updated PRL using ##PRL# and kittywireless provided PRL (over 2 years old, but it works..sadly)
I'll compile the "long story short" files, if anyone expresses interest. Hell if more than one asks I'll make a guide.

Reserved

i have data working on stock metro rom set to roaming but am working on 3g now and if u know of a stripped sense rom that doesnt have the metro settings built in please contact me either here or via pm

[Q] No data on AT&T (did forum searches)

Hello, I recently purchased a rooted and unlocked Tmo T999 on Swappa for use on my AT&T plan. I can get voice and sms, but no data.
The phone I had previously was an HTC Inspire 4G with a data plan, and from what I've read in the forums, the T999 should be able to use the same data plan as the Inspire (no LTE, just HSPA+). I had to get a new SIM card, since the Inspire uses a regular sized card. I called AT&T and had a CSR confirm that the IMEI they had registered for the new Sim matched the T999's. The CSR also provided an APN to try (wap.cingular), but it didn't work. I've also tried the pta and phone APN's, to no avail. I tried each of the APN's on various ROMS (root66's UVDMD5 and UVALH2 rooted stock firmwares (flased via ODIN), CM10.1.3, and LiquidSmooth 2.10). With each firmware I did a full data wipe/cache wipe/dalvik wipe before trying the APN settings. I also did a factory reset (via *2767*3855#) on the UVDMD5 and UVALH2 firmwares. They reset successfully, but still didn't get data. What's strange is that when I did the factory reset on UVDMD5 and UVALH2, the CyanogenMod SG3 bootscreen came up momentarily before resetting, even when I tried using stock kernels. The T999 came loaded with CM 10.1, but I do not know what method was used to achieve root or unlock for the phone. I've been working on this obsessively for three days, and I've read through several posts on this forum and others, but I still can't make this work. Can anybody help me?

If you are trying to use apn's from those T999 roms, you are just getting the T-Mobile apn's all over again.
Go to the AT&T forum and find what their correct apn is, then try that.
Sent from my SGH-T999V using Tapatalk 4
---------- Post added at 01:28 AM ---------- Previous post was at 01:25 AM ----------
Oh and generally it doesn't matter how you factory reset, they all reboot and use the current recovery. Just sayin cause I don't suggest using dialer codes for things like this. Too easy to make a mistake and potentially cause even more problems.
The boot screen comes up because factory resetting reboots recovery. Perfectly normal.
Sent from my SGH-T999V using Tapatalk 4

Verizon to US Unlocked Questions

I've been reading around and mostly want to know everything for this for that time when CM becomes stable.
Anyways:
Do you lose Verizon network functionality? By this I really mean, calls, SMS, SMS, voice mail, and 4G LTE.
When converted...just act like it's the US unlocked model when flashing ROMs? Do I need to flash the Verizon radio?
I'm confused...and the final question..
To convert it requires a SuperCID and then RUU flash, right? I've seen Sprint owners do it and one Verizon owner, but the instructions were all very unclear to me.
Thanks!
Answers are on post #4, tested it out after being sure of how to do this. If you're lazy, click here...

I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.

I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.

Tested it out...
Tarima said:
I've converted my VZW branded 10 to U.S Unlocked. I am NOT using the phone on Verizon network, so I can only answer part of your questions.
To convert, I changed my cid to SuperCID (22222222) and flashed the latest stock RUU.exe from HTC.com for U.S Unlocked. Pretty simple.
I can't tell you if the phone would work on Verizon network, but I would assume it would with a radio flash to get the basic things you mentioned working, as outlined in:
http://forum.xda-developers.com/verizon-htc-10/how-to/vzw-how-to-unlocked-model-vzw-t3376743
Haven't yet flashed any non-stock roms, but I can't imagine why this would be a problem. Also the CM thread has some people who flashed the Unlocked firmware on a VZW phone and got CM working.
Click to expand...
Click to collapse
afuller42 said:
I haven't and probably will never try, but I see advanced feature breaking after you do this like wifi calling and the like. but ive also heard all that's different is the radio. but theres different settings unlocked and hidden between the two that may give issues also.
so just give it a shot if you really want. the worst that would happen is you would need to switch back to Verizon firmware.
Click to expand...
Click to collapse
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.

Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
I was the guinea pig for this in regards to Sprint, but you've seem to partially answer a question I had.
I know that the Verizon and US Unlocked use the same model ID, but the Sprint and internal do not. Leaves me wondering if I could just run the RUU for my Sprint phone.

Ariac Konrel said:
Changed my CID to SuperCID (22222222).
Got the latest Unlocked U.S. FW from the HTC Dev site (RUU EXE) and flashed it.
Flashed a Verizon radio in fastboot. (The same one used to make the actual U.S. Unlocked variant work on Verizon)
Flashed TWRP in fastboot.
Formatted my data.
It booted without issue.
Followed this guide (though, on initial boot it showed 4GLTE active BUT no bars (line through them).
After following the guide, I rebooted.
Testing functions:
Calls: Functional and no delays.
SMS: Functional and fast.
MMS: Functional and fast.
Data connection: Functional.
Behavior after reboot: Starts again with the bars crossed off, eventually comes up and working though. Works after that, calls too. Takes about 45 seconds to connect.
Thing to note: It seems as if my signal strength is lessened. Though, this could easily be placebo, weather, etc. It's 1:31AM and I've never paid attention to it before.
Network comes up as 3107 instead of Verizon Wireless.
HTC software updates seem to be broken, it gives a corrupted error. I'm locked/S-OFF, so dunno.
Final deduction: It seems to functional and all, without hiccup most likely. It takes longer to connect than the stock VZW FW does of course, but after the boot it seems fine.
I'm done testing this for now, but if anyone is wondering yeah go for a it. It seems to be fine besides a slower initial connection. Excited for CM to become stable, then I'll play with this some more.
Click to expand...
Click to collapse
Does your volte work ? Something you can try is flash Viper10 and select as a verizon model instead of the unlocked version, this will add get you on global mode and I think will fix your signal issues. You list your on Viper10 just dirty flash it again selecting verizon version and give it a try. If it does not help you can always just dirty flash again and go back selecting the unlocked version. Just do a back up before doing this and you will covered if you just want to restore the back up. From my experience this might help just do not try running a custom kernel for the verizon version if you converted to the unlocked as your camera may not work and keep forcing close but you can run a custom kernel for the unlocked if you converted to unlocked. My recommendation would be to run the Elite kernel as I have had really good luck with the Elite kernel on the Htc 10 and I think theirs is what I run well on my Motorola nexus 6 also.

Ariac, regarding OTA software updates on the phone, I think you get that "corrupt" message because you flashed a different radio and twrp. Might be worth flashing the original Unlocked radio/recovery back and see if it at least detects the latest update. If it does, you'll also need to remove superCID to be able to take the update.
I reflashed the RUU yesterday, removed superCID and I was able to take the OTA.

Why can't you update PRL and profile in Lineage and other customs - and can we fix it

So as I've looked into it, it appears that nothing has changed here in the 2-3 years since I last explored this issue. I'm talking about the fact that you can't successfully update PRL and profile on CDMA carriers in LOS and AOSP ROMS. The usual behavior if you even have the option in the UX is that you get a force close. I'd love to understand why this hasn't been addressed.. It's a huge reason someone would stay on stock over AOSP/LOS. I saw someone suggesting a Nexus 5 dev had some success using a couple of APKs including OmaDmclient.apk, and a few threads here and on Reddit talking about how it must've been broken by an AOSP contributor, but in any event it still doesn't work. Isn't this something that the LOS team could fix if they wanted to?

The issue with CDMA is that most of the stuff isn't open source. This is why the aosp source code is targeted to GSM. So I sought this will get fixed any time soon.

Same problem... I think
My neighborhood has excellent Sprint 4G LTE coverage and it's much faster than T-Mobile. I happen to use Ting (which allows you to choose between T-Mobile GSM and Sprint CDMA, although to switch from one to the other costs $20). GSM isn't really an option for me.
Anyway, I used to have this problem with my LG Volt LS740. I could work around it by forcing a PRL and profile update on stock and then flashing to Cyanogenmod.
That phone finally bit the dust. I have now inherited my wife's Moto G 2015 (osprey) XT1548. Really nice phone.... but the issue is, the latest stock I can find is Android 6.0. I can activate the phone and get great 4G LTE on stock, but to flash to Lineage OS 14.1 (or AOSP) I have to wipe the device. I simply can't get it to pick up the 4G LTE service on the custom ROM's (tried both). This is a real problem.
As I understand it (admittedly from reading Wikipedia), the PRL contains an "acquisition table" that prescribes the frequencies/modes that the device will communicate on... so I think that's probably my issue. After doing the prescribed wipes in the ROM installation documentation, flashing the ROM, and booting the device, I think I've lost the PRL somewhere in that process.
Is there some way to retrieve the PRL while the device is on stock and put it back when flashing custom? If the PRL is indeed stored on the R-UIM, should I just remove the R-UIM during the first boot? Maybe I'm wrong and the problem isn't really the PRL.
Any thoughts? Please don't tell me to switch to GSM. The GSM coverage here is just plain bad from both carriers who offer it in my neck of the woods.

I have this same exact question. Ting, N910P note 4 that was originally Sprint, and days-old Lineage 16 / Andorid 9.0 . The latest stock rom is 6.0.1, and works fine. Lineage 16 works 99% fine and I'd really rather use that. But LTE doesn't work. If I force it to use 3G only, it actually all works. data, voice, text, bluetooth, gps… and being Lineage, I don't have to try to surgically remove all the spyware and other crapware without breaking it. It's just not in there in the first place. I'd really rather use that.
I would be fine having to extract things from the stock rom and edit files or whatever if it were at least just known what needed to be done. I'm fine with the fact that Lineage nor anyone else can actually include and redistribute any carrier proprietary stuff.

it should be possible
Has anyone figured this out?
I too have devices on ting, fantastically built devices that run amazingly thanks to a solid construction, the support of many many developers who are craft some of the best ROMs for any device I've ever seen, considering the limited specs of the XT1031s. Fortunately/adequately enough though, they only run on 3G Sprint, Boost originally, moved to Ting for their great rates for FreedomPop customers when they bought them out.
Anyway, currently to get a device on ting, I have to flash the latest 5.1 official stock Boost Mobile Rom with the latest radio baseband and firmware and such. A process thats pretty involved. I'm hoping that I can backup the stock image using TWRP, as when I went through the process of reloading the official image through the individual files via mfastboot, I skipped the logo and recovery files, and since I was able to retain my custom logos for boot and bootloaderunlocked screens, and the recovery, I'm hoping to be able to make an image of the stock ROM, which if at all possible, I'm going to do my best to make as bare bones as possible. May start with flashing the bloatware removed version of stock thats available, then going through and removing basically every app on the phone with the exception of settings and anything to do with phone, phone/carrier services, sim toolkit, etc, so I can have the smallest image possible that could maybe be restored everytime/anytime that I want to update the PRL or Profile. Which it looks like theres a new version of each released at a minimum every 3 months, as I just activated another device this way and there was only an incremental update of the last digit. If this works, great. If it doesn't then I hope that theres an answer to the question in the initial post of this thread;
Is there a way to update the CDMA PRL and Profile on a device that is running a custom ROM? If so, is it something the ROM needs to specifically support or is it something that is possible to do with a bundle of apks? Like sim toolkit and the like?
If its ROM related, are there, or would it be possible to take the necessary components from the stock files and install them in Xposed or Magisk? Or perhaps the buttons in the settings panel of the stock rom simply executes a series of commands that can be executed within a terminal CLI on the custom ROM? I assume that since the custom ROM clearly has access to the 3G radio since I can make and recieve calls, I have data, and text messaging (haven't tried MMS, but I assume it works) so why couldn't it do one more thing and initiate the PRL update?
I assume that even the stock rom doesn't ever touch the PRL or Profile, seeing as they remain even after a user data wipe, and are available for the radio to continue to use with custom roms, which means that the radio chip has to be the one storing the PRL Profile, so I bet that the radio also directly downloads those files from the carrier when asked to do so, and the stock rom must only come into play for the base logicstics of it all such as radio-"is this prl/profile a newer version than the one that i have now?" and phone-"yes, download new, purge old, flash new, tell me when done and leave me alone" Since the radio doesn't have its own processor for those sorts of things perhaps? If thats the case, then that should imply that theres nothing particularly proprietary or licensed, etc, that a rom would explicitly need to have in order to initiate these updates since it would never directly need to touch/see the files, just know that they were updated and what version number they are. What also lends me to believe this is the case is the fact that you can't select to downgrade the prl/profile, rollback, or load one manually, at least not that I can see.
So basically I'm saying that I hope it should be something simple to do. And if it is simple to do, you would think that custom roms would be able to read the carrier correctly too? Right now my new device reads "Boost" still. My previous one when I got it on ting I wanna say actually read ting afterwards. But when I loaded ressurrection remix, I had no cell/data/voice nothing, It just kept asking me for a sim card, which this phone doesnt have at all. When I loaded Lineage, everything cell related work. But can't update prl/profile, and carrier reads as "3G Roming Indicator Off" Which idk why thats the case.
Perhaps I'm missing something
Perhaps custom roms are missing a few somethings.
The only sure thing is that carriers need to just not be so greedy/dumb/uselessly difficult, and make giving them money for service easier, preferably without questions. Or at the very least actually provide some security so all this nonsense is at least worth something in the end to the end user, instead of being done so that they can try to spy on your unencrytped texts and calls to sell to advertisers, and selling access to the higest bidders such as the government and bounty hunters, whilst preventing you from restricting that information.

Software update for Boost Mobile

I got the notification today.

guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
Same Here
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
have you saved the 66 mb zip ota update ? can you share it

If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.

sidgallup said:
If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.
Click to expand...
Click to collapse
YES

Welp... today i updated stock ROM to the latest version, after that i unlocked bootloader on Motos website, flashed TWRP, installed LineageOS and coudlnt get signal to connect to GSM, then flashed Resurrection Remix and same problem, everything works except calls, signal bars at at 0, no service.
This reminds me of some issues i had years ago and i needed to flash an older modem for calls to work.
Is anyone else having issues after updating to the latest stock ROM version?
EDIT: just confirmed theres something in the latest OTA that blocks GSM funcionality on custom ROMS, i did the exact same proccess with my brother's phone which is the same as mine, Boost E4, but this time without updating the stock ROM, just went directly to unlocking bootloader out of the box and this time is working perfectly.
I need some help now on how to go back to stock ROM and unlock mine.

It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?

nookin said:
It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?
Click to expand...
Click to collapse
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.

MotoJunkie01 said:
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.
Click to expand...
Click to collapse
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.

nookin said:
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.
Click to expand...
Click to collapse
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.

MotoJunkie01 said:
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.
Click to expand...
Click to collapse
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.

nookin said:
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.
Click to expand...
Click to collapse
Oh okay. That makes things clearer. With Boost Mobile being a Sprint owned subsidiary, and Tello being a Sprint affiliated MVNO, you are correct that with voice being functional, your data connection should likewise work. (Contrary to popular belief, Boost Mobile is not an MVNO and never has been.) I believe that, in your situation, the last OTA is likely not the problem, but rather with your ability -- or lack thereof -- to edit the APN settings. But, on a positive note, with root of the stock OS, using a root file editor can be used to manually modify your apns-config.xml file to add the 4G/LTE data and MMS parameters for Tello. I believe there are also root dependent apps which can edit APN settings.
Since your xt1766 is the Boost Mobile variant, your default APN & telephony parameters are configured specifically for Boost Mobile. I'm making an educated guess that using root permissions to add Tello data and MMS parameters should fix your issue.