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.
Related
Hello all. Been a computer geek for 25+ years, and an android geek for a little over a year. I have done numerous flashes on Continuum, Fascinate, Nexus, and various other phones. I cannot seem to get a "clear and defined" answer on this question:
I have a TOTAL nandroid backup via ClockworkMod Recovery v6.0.1.2
I have a TOTAL system & app backup via Titanium Backup Pro 6.0.1
I am rooted with Chainfire's SuperSU v1.34
Phone
Sprint Samsung Galaxy S3 SPH-L710
Android Version:
4.1.2
Baseband Version:
L710VPBMD4
Kernel Version:
3.0.31-1130792
Build Number:
JZO54K.L710VPBMD4
Hardware Version:
L710.14
I did ALL the OTA updates from 4.0.1 to 4.1.2 prior to PagePlus flash. Had phone flashed to PagePlus with 100% working 3G, text, talk, and MMS. IF I flash a custom ROM (ie: CyanogenMod Nightly build, MOAR, etc...) will it render my PagePlus inoperable or require reflashing to PagePlus with every custom ROM flash? At $50.00 per flash that can get expensive. IF it DOES screw up the PagePlus flashing, can I just do either of the previously mentioned backups, and have my PagePlus flash settings magically re-appear? Or will it require a visit to my local PagePlus retailer for another flashing? My previous phones didnt require "flashing to PagePlus" since they were verizon phones and can be updated by simply dialing *228 or *22890.
Short answer: No
You don't lose your phone number when flashing roms, right?
APN settings may need to be modified manually though for MMS, etc
PagePlus flashing woes.....
TODAY 11:20 AM
CNexus
Short answer: No
You don't lose your phone number when flashing roms, right?
APN settings may need to be modified manually though for MMS, etc
-----------------------------------------------------------------------------------------------------------
I knew you didnt lose your number or carrier settings when you flash a custom rom to a verizon based 3g phone (not sure about verizon 4g LTE phones tho), since PagePlus uses verizon towers, and to update roaming capabilities, and PRL is easily accomplished by the *228 or *22890. BUT when using a Sprint based 4g phone, if you flash a new rom, or go backwards to an older oem rom, I was under the impression that EVERYTHING goes back to the default Sprint settings, and that the PagePlus side of things is forever gone. But noone can give me a definitive YES or NO on this, and at $50 a pop for mistakes can get expensive quickly
I have flashed the following Verizon phones with with "multiple" OEM & Custom ROMS with NO problems: Continuum SCH-I400, Fascinate SCH-I500, Droid X, HTC Incredible, HTC Vogue Touch (installed android instead of win 6.x), Verizon Nexus SCH-I515 . None of these required anything other than OTA programming to work 100% with Page Plus (except the Nexus which I could NEVER get on PagePlus no matter how hard we tried).
You may want to check out THIS THREAD.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Page Plus Mystery Solved?
First off..... sorry for posting in the "general" area with a question. I'll try to be more careful in the future......
Second.... Answer to my own question, and for anyone else in the "not knowing".
I bit the bullet yesterday and flashed 3 custom roms. Cyanogenmod, Miui, and MiBox, and then flashed back to my nandroid oem 4.1.2 JB I had 100% working Talk, Text, and MMS on ALL 3 roms, as well as the oem.
So, the answer to my question, YES, you can flash custom roms without losing PagePlus flash. I did NOT do an Odin flash, but I did do a factory reset, and still had all my settings intact.
Thanks to all the helpful people who gave opinions/pointers. Your work with the devices is GREATLY appreciated!!!! Keep up the good work.
Al
alaneddy said:
First off..... sorry for posting in the "general" area with a question. I'll try to be more careful in the future......
Second.... Answer to my own question, and for anyone else in the "not knowing".
I bit the bullet yesterday and flashed 3 custom roms. Cyanogenmod, Miui, and MiBox, and then flashed back to my nandroid oem 4.1.2 JB I had 100% working Talk, Text, and MMS on ALL 3 roms, as well as the oem.
So, the answer to my question, YES, you can flash custom roms without losing PagePlus flash. I did NOT do an Odin flash, but I did do a factory reset, and still had all my settings intact.
Thanks to all the helpful people who gave opinions/pointers. Your work with the devices is GREATLY appreciated!!!! Keep up the good work.
Al
Click to expand...
Click to collapse
I'm hoping you can help me with my similar question. I have a used Verizon Galaxy Nexus (SCH-I515) that I successfully programmed to use Page Plus. (I have no idea what I actually did, but I was able to follow the instructions I found online with no problems.) It's currently running JB 4.2.2 and Paranoid Android 3.6, and I'd like to get JB 4.3 on it.
I don't really understand flashing and all that (for instance, what ODIN is or what the ramifications of different operations are), and I can't seem to get an answer to my question.
Ideally, I'd like to get JB 4.3 on it (either stock/rooted or using one of the stable ROMs out there (CM 10?)), AND I'm hoping I don't have to reconfigure all the settings I've spent the last two weeks setting up.
Any insight? Thanks!
For some reason, every time I try to install a sense based rom, it never boots.
I'm fairly new to flashing, and have flashed 4 or 5 aosp roms. Every time I install one of those, it always works correctly, no issues.
I have tried to flash several Sense based roms, such as ARHD 20.1, Insert Coin, and nv, and each time, it never works. I always do a factory wipe beforehand as well as a wipe in the aroma installer. It will go thru the process and install, and then prompt me to reboot, which it does. Once the screen comes back onm however, it just hangs on the white htc screen with the red development text. When i get back to the hboot, itll show nothing for os.
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom. Also, I just tried the NV rom which is based off my firmware, and it still gives me the same trouble. Does anyone know what I'm doing wrong?
I'm running an ATT Htc One m8, rooted, unlocked, s-off with sunshine, twrp recovery
mattprice86 said:
I thought the issue may be that i dont have the latest firmware, but even people that dont have the latest firmware still are able to boot into the rom.
Click to expand...
Click to collapse
Give the ROMs about 10 minutes, and I bet they will boot. The extremely long boot time, and lack of boot animation (another symptom of this issue) makes a lot of folks believe the phone is stuck/frozen, when in fact its just taking a reeeeeally long time to boot.
If its true that the ROMs in fact never boot, it might just be an issue with your recovery. fastboot erase cache and either re-install recovery, update to the latest version, or try another recovery (Philz).
Even if the Sense ROMs boot, you might find some serious things are broken with your outdated firmware, such a broken WiFi. So I suggest either update your firmware or stick or ROMs based on your present firmware.
Ok thanks, i will try again. Ive read a bunch of threads about updating my firmware but couldnt find an answer to a question I have about it.
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
mattprice86 said:
If I upgrade my firmware to the latest WWE 3.28.401.6, will it mess up my ATT settings like the bands? Also, will it erase my internal sd card?
Click to expand...
Click to collapse
Firmware includes the radio baseband, so it may cause issues with reception on AT&T. It seems at least a couple folks have been flashing the 3.28 firmware, but I haven't seen enough reports to give me a warm and cozy feeling. With S-off (which is required to flash the firmware, anyway) you can always revert. But still, basic reception is more important to me than a couple updated features. Personally, I'll probably wait until the 3.x firmware specific to AT&T starts rolling out.
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Leads me to believe that the radio does not matter like the N5 where the 820 and 821 radios were interchangeable.
HTC One M8
Thanks redpoint, you were right, I gave it some time and it did come on. You always seem to be the one answering my questions, I appreciate it.
As for the new fw, I was thinking that would happen too from what I've read, I just needed someone more experienced to confirm that. I think I'll wait as well.
Thanks again
Elisha said:
It seems like the M8 is radio agnostic like the Nexus 5 based on my experience.
I am on Rogers and flashed the latest firmware and my LTE works no issues.
The latest firmware is supposed to be EU so technically those North American bands are not supported but it works no issue.
Click to expand...
Click to collapse
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
mattprice86 said:
So what is the latest firmware I can flash that's been known to work? I've seen that viper one is based off the 2.xx fw so do you know of anyone who's flashed it with att variant without any problems?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
No probs.
redpoint73 said:
On the 2.x firmware, some folks in North America (I can speak mostly of AT&T specifically, although there are a lot of network similarities with Rogers) had varying degrees of issues with the "international" firmware. For some, the reception was worse, and others had NO SIGNAL whatsoever. Probably depended on what bands AT&T was using in their specific market.
Can't say whether 3.x firmware is the same way. But in my experience (or at least, reading reports by others here), I would have to disagree this phone is in any way "radio agnostic", at least from a software perspective (as the hardware is common among at least GSM versions, and baseband software is the only difference - but that is a slightly different topic).
Click to expand...
Click to collapse
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former. For the record, my M8 is a "whelp", and I had to pay for Sunshine.
OMGMatrix said:
For the record, I have an AT&T model and am using the 3.xxx.xxx.6 firmware with absolutely Zero issues as far as signal. I get the exact same reception I did stock, and Very, Very similar reception to what my old Optimus G did in the same locations.
This indicates that there must be either a difference in hardware revisions (related to how some M8's can be firewater'd, whereas others need Sunshine), Or, the int'l radio firmware may not support the bands that are used on some towers in some locations. I'm leaning toward the former.
Click to expand...
Click to collapse
My guess would be the former as well. Keep mind that AT&T uses five different bands for LTE depending on your market region. Also keep in mind that travelling to another location may result in losing LTE reception (when you otherwise would have LTE on a AT&T specific radio).
Although none of this explains why I've seen some folks get NO SIGNAL whatsoever on AT&T's network after flashing the international firmware (2.x version, haven't seen any complaint yet on 3.28). Even if no LTE, those folks still should have been able to get HSPA and/or GSM since those AT&T bands appear to be supported by EMEA specs. So it leads me to believe there is something else going on aside from just band compatibility. Such as the network not falling back properly to HSPA/GSM.
I certainly don't have an issue if folks want to experiment with the 3.28 firmware on the AT&T network (as long as you know what you are doing, and are aware of the possible issues). Its certainly tempting with the 3.x based custom ROMs coming out. I might even experiment myself if I free up some time. But that spare time is a bit of a premium for me right now; and I also can't really afford ATM to have the possibility of reception issues or no service.
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
mattprice86 said:
I was able to successfully upgrade my firmware to the 2.xxx by using skull dreams' method. As soon as my rom loaded, however, WiFi and data weren't working. I read through the thread and found that clearing cache and dalvik would fix it, so that's what I did and it worked. (initially I tried to wipe both at the same time, but it gave me errors; further reading showed I needed to wipe cache first and then dalvik).
I would now like to upgrade to the 3.xxx fw so I can install arhd 20.3, but want to know, if I upgrade my fw and it messes up, can I just do the same renaming and putting it on ext SD card to downgrade back to the 2.xx fw?
Click to expand...
Click to collapse
You could always restore the backup you should be making before you do any mods on your phone. That would be the safest way.
So if I upgrade my fw then restore a backup, I will lose my fw changes?
I make nandroid backups before I do any, so I have approximately 60gb of backups on an external HD, and I always keep 1 or 2 on my internal and external storage
Hello,
I just got and Samsung galaxy S3 from a family member. And first thing I did, was reset it to factory settings. Which went ok.
Now I would like to update the phone. Current android version is 4.1.1. When I go into update section of the phone I get message that current phone version is up to date, but I read on the internet that latest version is 4.4.2. How should I best proceed in order to update the phone.
Also, I have several questions which I've been wanting to find out (Please note that I'm quite new to android):
1. This phone was rooted. It appears that after factory reset it is still rooted (According to Titanium Backup) is that how it should be? I thought that after factory reset phone would not have root access. Also what is strange, that after performing a factory reset I already had quite old version of Super Su pre-installed and CyanogenMod file manager, why is that?
2. I have an AT&T version of the phone. But I live in Europe where there is no sign of AT&T. Is it possible to remove AT&T branding? Also this phone has some kind of custom Adnroid software update "AT&T software update", which always tells me that v4.1.1 is the latest version of android available for my phone. Is it possible to revert back to native software update?
3. I did a factory reset on the phone about 30 minutes ago, how it already has 5.5 GB of free space used? - For some reason factory reset didn't remove music and photos.
4. I found the application named "System app remover". Can I trust its judgement on which apps are safe to remove?
5. How can I make sure if I have 2core processor or 4 core processor? - I downloaded this program "CPU / RAM / DEVICE Identifier", I have 2 core snapdragon processor
Hi Viltnieks!
You are correct: there have been newer Android updates released for the Samsung Galaxy SIII (SGH-i747/SGH-i747M variants). I know you tell you got an AT&T variant of the phone, but just to make sure, please double-ckeck under the Phone Settings --> About Phone that your device model is the SGH-i747 one. This info can also be found on a sticker under the battery. If you have another SGSIII device model, you are in the wrong forum.
I'm not exactly sure to pinpoint your phone's current state. At one point, you say that it has the AT&T Updater, but it also has been rooted, and contains CM file manager... As you want to update the phone's OS (ROM) to a newer version and would like to remove AT&T branding, I'll just straight skip to your second point:
viltnieks said:
2. I have an AT&T version of the phone. But I live in Europe where there is no sign of AT&T. Is it possible to remove AT&T branding?
Click to expand...
Click to collapse
There are basically three kinds of ROMs:
1. the official, carrier's ROM;
2. custom ROMs based on the carrier's official ROM. Those are ROMs created by the community, but are build on the carrier's one;
3. custom ROMs based on the Android Open Source Project, or one if its derived ROMs.
If you flash the first kind of ROM, you will have all the official stuff provided by AT&T, exactly as if the phone was brand new, out-of-the-box; this also imply that you will get all the AT&T stuff (AT&T Updater, AT&T-related softwares, AT&T branding...). If you flash the second kind of ROMs, you may get some of the AT&T stuff, though generally speaking ROM developers do a pretty good job at removing unneeded carrier junks and branding, or allow the user to choose which of the carrier-apps he wants to install or not. The third kind of ROMs are the cleanest kind looking at carrier-related stuff: it does not have those kind of things.
I have not given you a straight answer, as it is not my place to choose for you what you want. Still, I believe if you want to get rid of AT&T's branding, you would be more interested in custom ROMs, either carrier-based ones or AOSP/CM-based ones. For this reason, I would suggest you take a look around in the Android Development and Original Android Development sub-forums, where lots of custom ROMs are published by developers. Read the first posts of the threads, you will find what ROMs have to offer, what they look like, if they are based on stock or on AOSP/CM, if they are debloated, etc. The first posts also contain informations on how to install, so carefully read them.
You need to be running a completely stock ROM in order to receive OTA updates. This mean you cannot be rooted, stock apps should be present, and stock recovery.
Thank you for replying!
After double checking I can verify that model number indeed is SGH-i747. I also get AT&T logo before samsung logo when powering up, AT&T phone book and some other AT&T applications.
It has the AT&T updater, yes, but it isn't working. I always get "Software update interrupted. No update is available.." Or "Current software is up to date. You may check again in 24 hours"
And, indeed it has CM file manager and Super SU app installed, even If I do factory reset, these apps show up without installing. I guess it means that this is some kind of custom rom based carrier's ROM?
If I have a rooted phone, is it normal that it will stay rooted after factory setting reset?
I'm quite new to this, I wanted to clarify, ROM is like a version of android os?
I don't really need any of the carrier's stuff, so I guess 3rd kind of ROM would be best for me.
Is this the place where to look for roms - http://forum.xda-developers.com/galaxy-s3-att#romList?
Preferably I would like the phone to have global ROM, the one that comes with samsung galaxy S3, before carrier's add their stuff.
Factory reset will not remove the CM File Manager or SuperSu because they were probably installed via custom recovery or Odin. Only apps installed from the ROM itself will be removed.
I suggest installing the Samsung Phone Info app from the Play Store to determine the bootloader and modem installed on your phone and report back. The bootloader version is important to know before flashing anything.
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.
Hey guys! I have an LG G8 Thinq (LM-G820UM), stock OS, no root. I use Mint Mobile in the US.
I configured the APN settings according to Mint's website and I can call, send SMS/MMS, and get internet access just fine. But, I can't seem to use WiFi calling (though it's enabled on my Mint account) and I have not received a software update since March of 2021.
It says I am on the latest software version, but I have Android 10, and I've heard other Mint users are on 11 or even 12 with the same phone.
What can you recommend for me to make this work? I'd prefer not to root, but I am willing to. Can anyone ELI5 or link me a guide to fix this?
Thank you!
KillerTuxedo said:
Hey guys! I have an LG G8 Thinq (LM-G820UM), stock OS, no root. I use Mint Mobile in the US.
I configured the APN settings according to Mint's website and I can call, send SMS/MMS, and get internet access just fine. But, I can't seem to use WiFi calling (though it's enabled on my Mint account) and I have not received a software update since March of 2021.
It says I am on the latest software version, but I have Android 10, and I've heard other Mint users are on 11 or even 12 with the same phone.
What can you recommend for me to make this work? I'd prefer not to root, but I am willing to. Can anyone ELI5 or link me a guide to fix this?
Thank you!
Click to expand...
Click to collapse
Well first, Mint is not a carrier, they are an MVNO. They 'resell' T-Mobile network. So, it's not Mint that would update the OS, it would be whatever OS was originally (or rather currently) on the device.
So Mint doesn't care what OS variant you're using (Sprint, VZW, ATT, etc), but that' doesn't mean all the features will work (like vowifi).
I use Mint and have found that crossflashing my Sprint device to the latest US Open OS version (a11), everything will work; VoLTE, VoWifi, data, sms/mms, etc.
Mostly, the only way you would see an OTA update is if you are using the correct OS and that carriers network. That's not completely accurate though, some carriers will send an update over wifi without a (usually needed) carrier specific sim card, but that's hit or miss, no guarantees (I've had a Sprint phone that did it, but ATT is known to never do it).
You don't have to root to crossflash. But it's a real good idea to back up your entire rom before doing anything, or at the very least the essential partitions that are specific to your phone.
cheers
AsItLies said:
Well first, Mint is not a carrier, they are an MVNO. They 'resell' T-Mobile network. So, it's not Mint that would update the OS, it would be whatever OS was originally (or rather currently) on the device.
So Mint doesn't care what OS variant you're using (Sprint, VZW, ATT, etc), but that' doesn't mean all the features will work (like vowifi).
I use Mint and have found that crossflashing my Sprint device to the latest US Open OS version (a11), everything will work; VoLTE, VoWifi, data, sms/mms, etc.
Mostly, the only way you would see an OTA update is if you are using the correct OS and that carriers network. That's not completely accurate though, some carriers will send an update over wifi without a (usually needed) carrier specific sim card, but that's hit or miss, no guarantees (I've had a Sprint phone that did it, but ATT is known to never do it).
You don't have to root to crossflash. But it's a real good idea to back up your entire rom before doing anything, or at the very least the essential partitions that are specific to your phone.
cheers
Click to expand...
Click to collapse
Thanks so much for the explanation and the advice! I will begin researching crossflashing, pretty sure I've seen a couple of detailed posts here about it.
Is there a method to backup my ROM without root? I'm familiar with the process with TWRP installed, but not sure how to do it without. Would it be easier to just unlock the bootloader, flash TWRP + Magisk, backup, and then crossflash, rather than do it all without root?
Also, were you able to get an OTA update from Mint/T-Mobile once you crossflashed to the US Open OS version? Or would I have to flash an Android 12 ROM to upgrade?
Thanks again for the help, apologies for my newbieness. Just trying to get all my ducks in a row before I get hasty and brick my phone. lol
KillerTuxedo said:
Thanks so much for the explanation and the advice! I will begin researching crossflashing, pretty sure I've seen a couple of detailed posts here about it.
Is there a method to backup my ROM without root? I'm familiar with the process with TWRP installed, but not sure how to do it without. Would it be easier to just unlock the bootloader, flash TWRP + Magisk, backup, and then crossflash, rather than do it all without root?
Also, were you able to get an OTA update from Mint/T-Mobile once you crossflashed to the US Open OS version? Or would I have to flash an Android 12 ROM to upgrade?
Thanks again for the help, apologies for my newbieness. Just trying to get all my ducks in a row before I get hasty and brick my phone. lol
Click to expand...
Click to collapse
No worries, all good questions and not that easy to find the answers.
The best back-up method, imho, is to use the bkerler edl utilities (g search that, you'll find the github page).
Using twrp, what you can backup will be limited, but you can use dd commands to backup via twrp adb interface, but that's very time consuming.
I've never gotten an OTA update on LG phone if not running their specific OS, and not rooted or crossflashed to it. But, no big deal as pretty much now, there are no updates. Only the available KDZ and after flashing / xflashing to one of them, there won't be updates to it.
At this time, LG has not released any a12 roms, afaik. There are supposedly 'plans' to do so, but I'd bet it never happens.
cheers