This thread is dedicated to those users with a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow) Moto G3 (xt1548) who wish to convert their device into a Virgin Mobile Data Done Right variant by means of a full partition flash. In other words, a complete partition dump from a Data Done Right Moto G3 can be flashed to a Sprint, Boost, TextNow, or Virgin Mobile USA variant for full conversion to a Data Done Right variant. This conversion, due to MEID and other device IDs, is limited in terms of its ability to be activated on the Virgin Mobile DDR network. In other words, a converted device will not register in Virgin Mobile's system as a DDR device. However, your converted device can nevertheless connect to the DDR network with a properly provisioned and paired UICC. (Note: this method does not alter, modify, edit, change or otherwise clone any device IDs such as MEID, IMEI, MAC Address, etc, and is otherwise fully compliant with XDA rules and state & federal law). This thread is also dedicated to general topics regarding the xt1548 Moto G3 Virgin Mobile Data Done Right variant, which is a separate variant from the Moto G3 Virgin Mobile USA device.
Also, as this thread grows, so will the abundance of information and available firmware files needed for this task. This thread is not geared toward instruction or guidance on the notorious Data Done Right loophole. Upon converting your device to a DDR variant, connecting to the DDR network, UICC provisioning, etc., is entirely up to the user. I will not provide information on subjects regarding the DDR loophole. However sparse, there are a few threads here on XDA which provide information on that particular subject.
Sent from my MotoG3 using XDA Forums
First, it is noteworthy in opening this thread to point out that the APN Settings for Internet and MMS for the Data Done Right network are not the same settings as the Virgin Mobile USA variant. Your Data Done Right (hereinafter "DDR") APN Settings for LTE/4G Data and MMS should be set as such:
Virgin Mobile LTE
APN: n.ij.ispsn
Username: Sprint
Password: *
MMSC: http://mms.sprintpcs.com
MMS Proxy: 68.28.31.7
MMS Port: 80
APN Type: mms,default,fota,supl,hipri,dun
APN Protocol: IPv4
APN Roaming Protocol: IPv4
Bearer: LTE
(Any fields not noted should be left blank or default).
A common misconception of Virgin Mobile USA and Virgin Mobile DDR is that the two are the same network and utilize the same APN & Network Settings. In fact, Virgin Mobile DDR is a completely separate network from Virgin Mobile USA and the two are not compatible or transferrable from one to the other. Although both are MVNO subsidiaries of Sprint, they are two separate and distinct entities in regards of networks. So, a Virgin Mobile USA account on a Moto G3 can not be transferred to to a Virgin Mobile DDR account and vice versa. Although the DDR line of devices were discontinued from retail sales from Walmart around a year or so ago, the network itself is still in full operation and its plans are still fully available. As such, Virgin Mobile retailed two variants of its Moto G3 xt1548: the Virgin Mobile USA variant and the Virgin Mobile DDR variant. Owners of the DDR variant can reach Customer Service at 1-844-326-1261.
MotoJunkie01 said:
APN Type: mms,default,fota,supl,hipri,fun
Click to expand...
Click to collapse
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
I'm sure it's a Typo.
By the way, is the topic interesting enough to you, where you'd like to help out and be a contributing force to it.
I've read a few of your undertakings and your GOOD :good:
would be a pleasure to see your expertize and talent here in helping out with the thread.
Me (I'm) a nobody here or anywhere, but I've PM'ed MotoJunkie01 much, and he's knowledgeable and helpful - just as you are, as I've read your Threads and helpful posts. So how about it, would that sound like something you'd be interested to do in helping develop this thread. I know MotoJunkie01 was looking for help to co-chair this topic along I think you're just that person he's looking for.
Thanks for considering it. . .
ResistanceIsFutile said:
I'm sure it's a Typo.
By the way, is the topic interesting enough to you, where you'd like to help out and be a contributing force to it.
I've read a few of your undertakings and your GOOD :good:
would be a pleasure to see your expertize and talent here in helping out with the thread.
Me (I'm) a nobody here or anywhere, but I've PM'ed MotoJunkie01 much, and he's knowledgeable and helpful - just as you are, as I've read your Threads and helpful posts. So how about it, would that sound like something you'd be interested to help develop this thread. I know MotoJunkie01 was looking for help to co-chair this topic along
Thanks for considering it. . .
Click to expand...
Click to collapse
Projects like this interest me... swapping ROMs, tweaking settings, etc... So that lead me to read the thread, and I would help where I could. My issues is I don't have a CDMA Moto G, in fact I don't even have Sprint service in my area without traveling 200 or so miles, so I don't know how much help I would be.
Under the hood princples
acejavelin said:
Projects like this interest me... swapping ROMs, tweaking settings, etc... So that lead me to read the thread, and I would help where I could. My issues is I don't have a CDMA Moto G, in fact I don't even have Sprint service in my area without traveling 200 or so miles, so I don't know how much help I would be.
Click to expand...
Click to collapse
I'm sure this is better discussed with @MotoJunkie01 through PM's, though you both share the love for Moto's, and any knowledge brought to light will help that part of Moto users on the CDMA side. Besides anything you guy's could learn/exchange between yourselves would help all Moto users - Yes?
acejavelin said:
Projects like this interest me / I would help where I could / I don't have a CDMA Moto G, so I don't know how much help I would be.
Click to expand...
Click to collapse
{Please forgive me for taking your words out of context}
In the areas of tweaks and of their under the hood principles related to all Moto's, in a threads structure and content to it's beneficial coverage for the reader, answering of questions where your knowledge is greater, I see many areas you could be very helpful. Then think about some friends or far off relatives that may have need to the knowledge that this thread will cover. In that of Data Done Right.
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
Good catch on my "fun" entry. Great eye for detail
acejavelin said:
APN Type 'fun' ?!?! lol... I think you mean 'dun', I have never heard of a APN type of fun, although it was enough to give me a chuckle reading it.
https://tamingthedroid.com/apn-type
Click to expand...
Click to collapse
Your contributions to this thread would be invaluable, and enlightening to many. Would love it if you were on board. Thanks for your consideration regardless of your decision.
Sent from my MotoG3 using XDA Forums
Moto G3 Virgin Mobile DDR Modem [Radio) Firmware Files
As always ....you flash these files at your own risk. ALWAYS make a full Nandroid backup before proceeding with firmware flashing or major configuration changes.
The following link is for the Modem [Radio] Firmware which comes stock on the Virgin Mobile DDR variant of the Moto G3 (xt1548). More specifically, this modem firmware is from the final Stock Android 5.1.1 Lollipop Build - the build next preceding the Android 6.0.1 Marshmallow OTA. (Android 5.1.1 LPI23.72-32-S.28_cid9) Included in this link are three raw partition .img files: /modem & /fsg (classified as modem [radio] firmware) and /persist, which encompasses vital network and telephony configurations specific to the Virgin Mobile DDR network, including unrestricted enabling of Mobile Hotspot, USB Tethering and Bluetooth Sharing of your high speed 4G/LTE Data. There are also telephony configurations in /persist which are unique to DDR. Again, it should be noted that these particular firmware partitions and network configurations are specific to the DDR variant, and are not the same as those partitions and configurations on the Virgin Mobile USA variant.
DOWNLOAD LINK:
https://drive.google.com/folderview?id=0B4PvIFOs0G3jVmF1dXloWFpLZzA
These partitions may be flashed via a number of different methods. Flashfire by @Chainfire, Partition Backup & Restore by @wanam, and Rashr are all capable of flashing these partitions. Preferably, and arguably the best method, is to install Minimal ADB & Fastboot on your PC (and also the most current version of Motorola Device Manager, to ensure the correct and most current USB drivers for your Moto G3 are installed on your laptop or PC). Put your device into AP Fastboot Mode by powering off your device, and then holding the Power button and Volume Down button of your device simultaneously until the fastboot menu appears. Connect your Moto G3 to your PC or laptop with an OEM or equivalent in quality micro USB to USB charge/sync cable. Place the three .img files you downloaded in your adb/fastboot directory and open a command window in that directory. Execute these commands:
First, type fastboot devices. Your device Serial Number will appear in the command window if you are properly connected with the requisite USB drivers installed. If you do not see the Serial Number or if you see a message "Waiting for Any Device" in the command window, try switching USB Ports, reinstall the Motorola Device Manager, and/or try a different sync cable. Execute these commands to install the DDR Modem Firmware on your device:
fastboot oem fb_mode_set
fastboot flash modem modem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.img
fastboot oem config fsg-id virgin
fastboot oem config carrier virgin
fastboot flash persist persist.img
fastboot oem fb_mode_clear
Your Moto G3 will now be running the DDR modem firmware and is configured to the carrier specific parameters of the DDR network. Again, these firmware dumps are from Stock Android 5.1.1 (LPI23.72-32-S.28_cid9). This firmware can be used while running any stock or custom ROM and, to the best of my knowledge and experience, on any version of Android. However, if any members want the more recent Android 6.0.1 modem firmware, just request it and I'll post a link.
This firmware can be used while running any stock or custom ROM and, to the best of my knowledge and experience, on any version of Android.
Click to expand...
Click to collapse
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
ResistanceIsFutile said:
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
Click to expand...
Click to collapse
Yes. This thread is focused on the Sprint compatible variant of the Moto G3, the xt1548 Variant -- Virgin Mobile USA, Virgin Mobile Data Done Right, Boost Mobile, Sprint, TextNow, FreedomPop, etc. For members that need it, I will be posting a download link in the next day or so of the stock Android 5.1.1 ROM shipped on the DDR variant.
ResistanceIsFutile said:
While still keeping in mind that of a Sprint compatible (Sprint, Boost, Virgin Mobile USA, TextNow)-Variants- of the Moto G3 (xt1548) is needed here.
Click to expand...
Click to collapse
By the way, glad you finally drummed in with some input. Haha. Good to hear from you as always.
MotoJunkie01 said:
Yes. This thread is focused on the Sprint compatible variant of the Moto G3, the xt1548 Variant -- Virgin Mobile USA, Virgin Mobile Data Done Right, Boost Mobile, Sprint, TextNow, FreedomPop, etc.
For members that need it, I will be posting a download link in the next day or so of the stock Android 5.1.1 ROM shipped on the DDR variant.
Click to expand...
Click to collapse
That's good - but maybe @acejavelin and yourself, and others might consider if it's possible to do this mod on any device variant, that would be of a VM USA, Boost, Sprint, TextNow, FreedomPop, with the Snapdragon 410, msm8916 Baseband used.
It's way over my head, but wouldn't any device (branded from any of the above) with the Snapdragon 410, msm8916 Baseband work for this? This ideal then ported to them? I know it's drifting away from your "Virgin Mobile Data Done Right Moto G3" - thread title, maybe you could add others too, in the title - if this application fits.
EDITED - Removed content not being directly related to the Threads Title.
MotoJunkie01 said:
By the way, glad you finally drummed in with some input. Haha. Good to hear from you as always.
Click to expand...
Click to collapse
But Friend, I had posts #4, and #6 before post #10- eerie of that addition factor to math. . . adds up to the post you've quoted
I highly doubt this would possible with any other device that doesn't have a DDR variant... The Moto G 2015 is kind of unique in that we have the radio firmware and other vendor specific files for the DDR variant and a way to flash them. Few other devices could fit that criteria.
acejavelin said:
I highly doubt this would possible with any other device that doesn't have a DDR variant... The Moto G 2015 is kind of unique in that we have the radio firmware and other vendor specific files for the DDR variant and a way to flash them. Few other devices could fit that criteria.
Click to expand...
Click to collapse
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite.
MotoJunkie01 said:
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite. But I must admit I once thought the exact same thing on the msm8916 Snapdragon 410 devices.
Click to expand...
Click to collapse
Your analysis is exactly what I once theorized -- that the "trick" was in the construction of the device -- That the msm8916 was necessary for the loophole to work. In fact, many DDR devices have the msm8916 under the hood. But there are also others with different basebands which also attain connectivity.
MotoJunkie01 said:
I agree. The msm8916 baseband seems to be significant to the data loophole yet it is not. I once thought this myself until I discovered the single thread that makes the loophole possible. It lies in the network itself -- and the DDR Moto G3 can connect to this loophole --- as @acejavelin noted --- due to the unique nature of the radio firmware. I have the radio firmware to other DDR devices as well -- the G3 just happens to be my favorite.
Click to expand...
Click to collapse
Slowly this is sinking into some logic for me, as I've never rode a twisting, turning, bucking bull - I guess I'll have to learn to stay on this too, as the wild ride that bull would of been.
Ok radio firmware then - is anyone on XDA up to understanding fully the principles here, and if any mod's are possible to that kind of a nature in porting any values out? Looking at it another way is there a possibly of a DDR firmware porting in (changing) the value in that firmware to be used on a different msm8916 baseband device variant? Someone with a good knowledge could compare different DDR radio firmware to other DDR or NON-DDR devices and see common points of interest in them? What's possible here?
MotoJunkie01 said:
But there are also others with different basebands which also attain connectivity. /-\ It lies in the network itself.
Click to expand...
Click to collapse
Others as in what kind of reference - non DDR devices? What are the other basebands that are useful to the network?
I know I can come up with the questions, but I have no knowledge to find the answers yet. Hopefully my line of questions spurs someone into thinking along these lines and then does have some knowledge to experiment.
Radio firmware is not open source, it's binaries... You can't really just open and compare it to another radio. Radio firmware is proprietary, it just talks to the RIL and kernel, it's part of Android we don't get get the source for.
acejavelin said:
Radio firmware is not open source, it's binaries... You can't really just open and compare it to another radio. Radio firmware is proprietary, it just talks to the RIL and kernel, it's part of Android we don't get get the source for.
Click to expand...
Click to collapse
That's interesting and a good point made Sir.
If it's talking to the RIL and kernel - can one trap this conversation?
If it's talking in binaries then is it possible to be converted to something understandable or at least viewed? Does it talk differently to both or say
more less the same thing to both (RIL and kernel) ?
Thanks
ResistanceIsFutile said:
That's interesting and a good point made Sir.
If it's talking to the RIL and kernel - can one trap this conversation?
If it's talking in binaries then is it possible to be converted to something understandable or at least viewed? Does it talk differently to both or say
more less the same thing to both (RIL and kernel) ?
Thanks
Click to expand...
Click to collapse
The communication by the firmware isn't relevant to the loophole. Trust me when I say the loophole lies in the network itself. The DDR devices can connect to this loophole due to known configurations in radio firmware.
Related
Hello,
This is a newbie question. Is it possible to convert Cricket Samsung Galaxy S4 SCH-R970C to a TMobile version of S4. I know Cricket uses CDMA and Tmobile uses GSM but someone told me that S4 is the same device and only software is different between carriers. Can someone let me know if this is even possible?
thanks
amags
The guy at cricket told me they use a different type sim card so I don't know if it's possible
DNA420 said:
The guy at cricket told me they use a different type sim card so I don't know if it's possible
Click to expand...
Click to collapse
I believe it is safe to assume you may add t-mobile elements software wise but the radios are different the cricket version is CDMA and T-mobile runs off of GSM which is completely different technology, so compatibility is a no go its litterally two different devices at that point, may be able to flash to sprint or verizon that works with cdma but even that im not too sure with
Hope that helps
cybertang said:
I believe it is safe to assume you may add t-mobile elements software wise but the radios are different the cricket version is CDMA and T-mobile runs off of GSM which is completely different technology, so compatibility is a no go its litterally two different devices at that point, may be able to flash to sprint or verizon that works with cdma but even that im not too sure with
Hope that helps
Click to expand...
Click to collapse
why don't you just decompile a Tmobile ROM and just take the system.img.ext4 and recompile it? I did that to a USCC stock ROM and flashed it over to my Sprint L720 and it works perfectly.
amags said:
Hello,
This is a newbie question. Is it possible to convert Cricket Samsung Galaxy S4 SCH-R970C to a TMobile version of S4. I know Cricket uses CDMA and Tmobile uses GSM but someone told me that S4 is the same device and only software is different between carriers. Can someone let me know if this is even possible?
thanks
amags
Click to expand...
Click to collapse
no bueno homie
you cannot use the T-mo version on CKT, or vice-versa
This is an old thread I know,.
Is there anymore information on this? I have read it can be done.
From cricket to t-mobile galaxy s4
cricket galaxy s4 schr970c
I would love to take this phone to a different carrier. I realize that the cdma is an issue but there had to be another carrier that I can switch to. Does any one know how I can switch carriers using this same phone?
Yeah, i have the same question as this. Would i risk bricking my phone if i tried loading a tmobile rom and modem to my cricket phone?
Bumping this older thread cuz I see no resolution and I have a similar question...
In my research I found this thread: http://forum.xda-developers.com/showthread.php?t=2409392
-The OP flashed an i9505 rom onto his R970C cricket GS4, but apparently he found it doesn't alter the modem/radio firmware, and THAT is what is different in our Cricket phones.
However, I personally am looking NOT to use this phone on a GSM network (T-mobile)..but on a CDMA (ideally Page Plus/VZW)..for that it would seem the radio is the same! -And actually I found this quote on a different forum (cricket user one):
"Cricket Galaxy S4(SCH-r970c) uses MDM9615M RF chip which includes GSM functionality which is the same chip found on Verizon Galaxy S4(SCH-i545)
Anyone try flashing a VZW firmware and also VZW modem firmware? -risk to brick it I'm sure..but, then again..maybe it just works!
"Cricket Galaxy S4(SCH-r970c) uses MDM9615M RF chip which includes GSM functionality which is the same chip found on Verizon Galaxy S4(SCH-i545"
Anyone try flashing a VZW firmware and also VZW modem firmware? -risk to brick it I'm sure..but, then again..maybe it just works!
Where can I find modems. For sch-r970c the old ones.
kalanir said:
why don't you just decompile a Tmobile ROM and just take the system.img.ext4 and recompile it? I did that to a USCC stock ROM and flashed it over to my Sprint L720 and it works perfectly.
Click to expand...
Click to collapse
this sounds very interesting, can you please give us step by step instructions on how to do this.
yearner said:
this sounds very interesting, can you please give us step by step instructions on how to do this.
Click to expand...
Click to collapse
Aloha brother!
I haven't done that in a long time. If you are interested in it, let me know. It's a little bit more complicated to do especially with the bringing of Samsung Knox but I feel I can try my best to help. If you still need my help, reply to this and I'll offer as much help as I can. Making far balls is easy; but getting them to be applied with correct settings is a pain the the you know what.
Mahalo,
Kalanir
R970c in others networks
kalanir said:
Aloha brother!
I haven't done that in a long time. If you are interested in it, let me know. It's a little bit more complicated to do especially with the bringing of Samsung Knox but I feel I can try my best to help. If you still need my help, reply to this and I'll offer as much help as I can. Making far balls is easy; but getting them to be applied with correct settings is a pain the the you know what.
Mahalo,
Kalanir
Click to expand...
Click to collapse
I am interested, please help me tanks.
SimplifyLife said:
Bumping this older thread cuz I see no resolution and I have a similar question...
In my research I found this thread: http://forum.xda-developers.com/showthread.php?t=2409392
-The OP flashed an i9505 rom onto his R970C cricket GS4, but apparently he found it doesn't alter the modem/radio firmware, and THAT is what is different in our Cricket phones.
However, I personally am looking NOT to use this phone on a GSM network (T-mobile)..but on a CDMA (ideally Page Plus/VZW)..for that it would seem the radio is the same! -And actually I found this quote on a different forum (cricket user one):
"Cricket Galaxy S4(SCH-r970c) uses MDM9615M RF chip which includes GSM functionality which is the same chip found on Verizon Galaxy S4(SCH-i545)
Anyone try flashing a VZW firmware and also VZW modem firmware? -risk to brick it I'm sure..but, then again..maybe it just works!
"Cricket Galaxy S4(SCH-r970c) uses MDM9615M RF chip which includes GSM functionality which is the same chip found on Verizon Galaxy S4(SCH-i545"
Anyone try flashing a VZW firmware and also VZW modem firmware? -risk to brick it I'm sure..but, then again..maybe it just works!
Click to expand...
Click to collapse
I'm curious were you ever able to flash it to vz firmware?
Unlock sim card
Hello,
As soon as I can I'll unlock the sim card for SCH-R970C?《S4 CRICKET》it will work like version?
Good luck, XA1?
---------- Post added at 06:57 AM ---------- Previous post was at 06:51 AM ----------
Hey every one?,
I've TWRP backup for jfltecri, S4 Cricket.
Works smoothly?, with open gapps.?
I'll upload it as soon as I can,
Note?:-
It's only for Yemen??
Good luck,
XA1?
I have a G900V bootloader unlocked currently running CM 13 and I would like to add Sprint CDMA & LTE bands so I can use a The Peoples Operator SIM card in an area that has better Sprint coverage than VZW. I read over this Guide on adding GSM & LTE Bands to the G900V and calculated the binaries to add the bands:
CDMA 0,1,10
LTE 2,4,13,25,26,41
CDMA Binary 10000000010
LTE Binary 100000000000000110000000000010000000010100
All set to go but I can't seem to get figure out how to get into USB Settings to change from AP to CP and MTP + ADB to RNDIS + DM + Modem, the dialer codes just don't seem to work even after changing efs/carrier/hiddenmenu from OFF to ON. I took a look at EFS Pro but it doesn't seem to have an option to Change from AP to CP. Any help would be greatly appreciated.
If your trying to get into diag mode this will do it running cm13.
http://forum.xda-developers.com/showthread.php?t=1626638
jbgtenn said:
If your trying to get into diag mode this will do it running cm13.
http://forum.xda-developers.com/showthread.php?t=1626638
Click to expand...
Click to collapse
Thank yo for the link. Sadly I couldn't get the scripts to work on my G900V S5 CM13. But that link ended up leading me to this one CM13 QPST Editing files is a little above my paygrade so to speak, I've been following directions for years but still a total newb at most of this stuff but I am hoping I'm on the right track.
twolostminds said:
Thank yo for the link. Sadly I couldn't get the scripts to work on my G900V S5 CM13. But that link ended up leading me to this one CM13 QPST Editing files is a little above my paygrade so to speak, I've been following directions for years but still a total newb at most of this stuff but I am hoping I'm on the right track.
Click to expand...
Click to collapse
It should work. Are you running the diag.sh script? I have same phone and cm13 and it works for me.
jbgtenn said:
It should work. Are you running the diag.sh script? I have same phone and cm13 and it works for me.
Click to expand...
Click to collapse
I run DIAG.SH and it just hangs there. I think I am going to do a fresh install of CM13 later this week and give it another shot.
this is what i'm trying to figure out, because i can get a good local S5 VZW but SPR use different LTE bands.
i know typically the saying is never flash anything for a different carrier of your model, but some people seem to do it with a ymmv statement, wondering if this may be the easier route to get it to just work like a native phone.
i've read several threads from people talking about carrier rom swap, some casually saying sure it can work, but no updates from OPs or others that said they would try, definitively saying that it worked or failed.
so... has anyone literally gotten something like the Odin flashable firmware at sammobile or someplace for the Verizon VZW sm-g900v and flashed it with the Sprint SPR sm-g900p stock firmware, completely changing its baseband, modem, everything so it now identifies and works the same as a Sprint phone?
or should i just keep waiting for another similarly cheap S5 bundle in a Sprint flavor?
Did you try *#0808#
Sent from my SM-G955U using Tapatalk
twolostminds said:
I have a G900V bootloader unlocked currently running.......
Click to expand...
Click to collapse
I've never added any bands to my G900V myself but, I do know that it's plausible to do this.
From what I can tell, the only bands that are needed that the SM-G900P has vs the SM-G900V are specific to the 4G LTE.
Though I did confirm this using a few different locations, I believe that the following link is the best choice in viewing the comparisons between the two devices.
https://www.phonemore.com/compare/p...m-g900v-vs-samsung-galaxy-s5-sm-g900p/4561723
With that guidance...
The following link is one of the Guides available on the forum for adding Bands to a GS5. It was closed but, not because it wasn't working. It was closed because of the negative interactions from various members in there but, the guide and downloads are still good.
https://forum.xda-developers.com/showthread.php?t=2886059
Please Note the success stories on the second post...
The following is another guide as well. Though, it's located within the Galaxy Note 4 area, you could say that the Galaxy Note 4 is the "Note" counterpart to the Galaxy S5.
https://forum.xda-developers.com/showthread.php?t=3160864
Please Note that the OP does reflect some S5 information as well...
Those are just 2 thread examples to help accomplish what you're looking to do.
I do wish you the best of luck and hopefully the next post here will reflect your success!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
thanks for the double check.
it looks like those are some of the threads and sites i've looked through already as i wanted to be sure i had the proper lte bands that the Sprint model came with, and it seemed possible.
however, with the increasing coverage of cybersecurity, i am increasingly hesitant the more closed source and leaked tools are involved (especially when i see some thread guides that have a mod edit for malicious download link removal).
i suppose i should just pass on the Verizon listing, and wait to spot a similarly good deal from a local person selling their personally cared for Sprint S5 plus spare battery charger case and 2nd battery all under $100 (i'm sure you can understand why i wanted to "make it work", hehe).
So Ive had this Verizon Note 3 since day one. Finally unlocked my bootloader... What are the rules on what I can and can't do now. Can I install any Android rom? Can I only install note 3 roms from any carrier... Can I install only Verizon note 3 roms? Or is it a hybrid... I can install any rom if I replace the firmware and or modem.
I really want something on 7.1 but I'd rather take 6 and have something custom... Fast and responsive.
Thanks community.
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Normally, when a dev ships a "ROM", there are two important pieces: the /system image (what some folks call "the ROM"), and the boot image. The boot image is what some folks erroneously call "the kernel"; but it is really a combination of kernel + ramdisk. The ramdisk has all the scripts in it that the "init" process reads to start up all the low-level daemons and services... as well as the Android UI as well.
The kernel is very tightly tied to the specific hardware in a given handset - both the processor/gpu and all the sensors/leds/peripherals.
So that's the reason you can't just flash any old ROM. In the least bad case, your device wouldn't boot; in the worst bad case the kernel would boot up far enough go off in the weeds and possibly damage some of your hardware.
You might be tempted to think "we'll, what if I find a boot image for the "hltevzw" SM-N900V device... can I flash that after I have flashed 'any old Android ROM'? Won't that take care of things?"
Well, not really. The system library binaries in /system are possibly compiled with instruction-set optimumization tweaks that are only supported by specific CPU and GPU hardware chips. Moreover, other peripheral chips such as GPS have unique "downloadable" vendor firmware in the system image... so again, there's the issue of hardware dependencies of the /system image.
Beyond that, there's carrier-specific "setup and activation" software that differs between ROMs, so even using ROMs that are from a different carrier's version of the exact same handset hardware might not work fully - specifically in the telephony function areas. Everything else might work fine though. For instance if you wanted to use the device as a WiFi-only unit for kid's games etc.
Note BTW that the "International" Note 3 GSM phones are not the same hardware - they use an Exynos processor.
good luck in your quest
Thanks
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
cyberoptics said:
That was very helpful... Looks like Araya is my best bet. I'll leave jasmine rom to try it.
I was hoping that I could get another note 3 rom on this forum and flash the CDMA modem for networking... But doesn't seem like that's an option.
Click to expand...
Click to collapse
I might have very slightly overstated the case for pessimism. There is a "consolidated" Verizon Note 3 Forum which is meant for devs to provide development tools and even ROMs that could potentially be used on devices from more than one carrier. But the world being organized the way it is, that means that you are more likely to find multi-carrier GSM ROMs over there than multi-carrier ROMS which support GSM and oh by the way CDMA and LTE as well.
If you want to fool around over there, I recommend that you proceed with great caution to make sure that the ROMs you choose specifically target Qualcomm MSM8974AB Note 3 handsets, and you should read the developer notes very carefully to see whether you need to flash an "hltevzw" kernel separately. If the dev does not mention "supports hltevzw" or "supports N900V" (for example here) you might be taking chances with your hardware.
I suppose it is possible that the radios are 100% "software defined" in the sense of which bands they can support. Maybe you can get what you want by simply flashing the desired carrier's "modem" firmware, but I have never done that so I can't say for certain whether that works or you are risking a brick (or hardware damage) by doing that. I simply don't know (e.g.) if the chips and antennas in a T-mo version of the Note 3 are identical or different from a Verizon Note 3's hardware
cyberoptics said:
If I'm still stuck to Verizon Note 3 rom... What is the purpose or benefit of unlocking the bootloader... Was that really just to avoid Odin so I can flash my couple rom choices easier?
I appreciate your time!
Click to expand...
Click to collapse
Well, for one - having a custom recovery allows you to make backups - even if you never change ROMs
People don't think of backups as being "sexy", but they allow you something which is really valuable: freedom to mess around and experiment with the knowledge that "if something goes wrong, I'll just restore the backup".
And with Odin, you only had the choice of Stock Roms. Now you have a few more.
cheers
Yes you can install Any rom for note3
Here is my experience with installing roms on note 3 after unlock bootloader
you should Flash twrp-2.8.7.0-hlte-4.4.img by ODIN for the hlte roms or twrp-2.8.7.0-hltevzw-4.4.img if you looking to flash verizon roms ,
im on Phronesis Rom N7 now and i tryed many roms
AryaMod N7 & S7 Edge
MagMa-NX from NXT TEAM
Resurrection Remix Nougat 7.1.1
CM 13 ROM 6.0.1 for Trader418
Purify CM13 6.0.1 ( the best CM13 till now )
and more ...
i have only one problem that i cant get LTE in mobile network always on H+
i tryed to add screenshot but i couldn't its my firist reply :laugh:
@ALPHA85
Pretty informative first post - thanks, and welcome aboard!
Are you on a Verizon SIM? If not, have you been flashing modems from other Note3 devices?
Just curious; I don't have much experience with radio issues or carrier activation issues. Trying to port a carrier-specific ROM elsewhere (esp starting from a VZW ROM) looks like a massive pile of interlocking software dependencies, though. My respect to anyone who can succeed at it.
Feel free to write a brief summary about what's broken in each - any of them have NFC working? I was on CM13 (trader418) for a long time and would have been happy to stay there were it not for all the GPS issues.
Thank you ,:angel:
i dont use Verizon SIM becouse im from egypt, i bought my verizon note 3 by wrong , when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
i'm on OF1 bootloader unlocked and i flashed PL1 Modem i thought maybe it help me to get LTE but still the same H+
about NFC i really didn't try it at all , i always disable it by titanium pro
ALPHA85 said:
when i bought it i saw N9005 under the battery and in the boot screen also inside the rom ,it was lollipop 5.0 ,but sinse i did factory rest i surprised it change to N900V even the imei changed , till now i cant understand how they flashed N9005 rom for N900V device with locked bootloader
Click to expand...
Click to collapse
When you first got it, did it appear to have a Verizon ROM on it? (For instance, the Verizon splash screen?) Or some other carrier's logo?
Actually, that cleared something up for me. Well, except for the part about the IMEI changing
Apparently there were both LTE and GSM models of the "Note 3" that were sold in international markets. I understand the LTE version was originally sold in China, but the GSM model is more common?
The SM-N9005 is an LTE phone (I don't know about CDMA) with the Qualcomm MSM8974 processor
and the N9000 is the GSM model with an Exynos 5420 processor
So that probably explains the binary compatibility of the SM-N900V and the SM-N9005 - same processor, and both phones were designed for LTE service.
But your report should give @cyberoptics a little less pessimistic view of things; thank you for that.
But I wouldn't go so far as to say you can flash ANY Note 3 ROM. Even though both the Exynos and Qualcomm processors use ARM cores, they are fairly different - the Exynos has 8 cores, half of which are Cortex-A15, and the MSM8974 has only four cores which are Krait- something or other. I think they are not quite compatible. Note that in theory, ARM code that was compiled to earlier standards (e.g. thumb, armv5) would certainly work on both devices - but if they compiled ALL the code in ROM libraries that way they would be giving up a lot of performance on either device. So.... to the extent that they target processor specifics for either Cortex-A15 or Krait, they will be incompatible.
cheers.
bftb0 said:
You are in luck. :crying:
There's hardly anything to choose from; maybe 3 or 4 ROMs and about the same number of kernels.
AFAIK, there are no Nougat ROMs and only one Marshmallow ROM (AryaMod6.6).
Click to expand...
Click to collapse
bftb0 I just wanted to thank you once again for your consistently helpful, verbose posts about the N900V. I've been using CM13 thinking it was the best thing going, when, as nice as it was at the time, it doesn't hold water compared to AyraMod, which I switched to yesterday after reading this thread.
Now my GPS won't take me sailing past Easter Island when en route to a noon meeting downtown. Maybe Google Cardboard will even work, now that NFC appears to.
Thanks again, and please don't ever bore of being a great and helpful resource, we need you!
I am troubleshooting some minor data connectivity issues on 7.x while using Sprint (att/tmo/vz unaffected). Issue is a long hesitation when reconnecting to cell data even when there is perfect signal for voice/text, might be something to do with the SprintDM subsystem or APN settings, maybe roaming settings or the eHRPD-LTE handoff, trying to figure that out!
But I wanted to see if there is any official (or working modified) version newer than M8992_1255331.29.01.88.02R SUPER NA ?
Obviously a North American radio firmware. Thanks in Advance.
another thing....I have some good insight on how to potentially fix this problem but I do not know how to dump/decompile the radio firmware to look at it and make adjustments. I could use some suggestions on software for this? I used QPST plenty in the past but since LTE came out this is a whole new level for me.
adrenatek said:
I am troubleshooting some minor data connectivity issues on 7.x while using Sprint (att/tmo/vz unaffected). Issue is a long hesitation when reconnecting to cell data even when there is perfect signal for voice/text, might be something to do with the SprintDM subsystem or APN settings, maybe roaming settings or the eHRPD-LTE handoff, trying to figure that out!
But I wanted to see if there is any official (or working modified) version newer than M8992_1255331.29.01.88.02R SUPER NA ?
Obviously a North American radio firmware. Thanks in Advance.
Click to expand...
Click to collapse
You have the newest radios until the Nougat update releases.
I would love to know too, I've been having so much connection issues it's ridiculous.
adrenatek said:
another thing....I have some good insight on how to potentially fix this problem but I do not know how to dump/decompile the radio firmware to look at it and make adjustments. I could use some suggestions on software for this? I used QPST plenty in the past but since LTE came out this is a whole new level for me.
Click to expand...
Click to collapse
To my knowledge, you can't extract the radios in the device... you can get the NON-HLOS.bin and fsg.mbn files from the current factory images (possibly the OTA's as well, but I haven't looked into them, often times they are no complete images but binary difference images)... the "modem" in modern Moto devices is in 2 pieces, NON-HLOS contains most of the LTE, GSM, and WiFi "modem" while a critical piece is in fsg.mbn, unfortunately there isn't much documentation on what these pieces are and how to edit them. QPST changes on modern devices are much more problematic than older ones.
This is troubling. I wonder if my noticing of this issue on Sprint is only because Sprint's network is more 'cobbled together' in terms of radio frequencies and technologies. Definitely no issue in any 6.x ROM, but 7.x has delays in bringing back data connectivity after certain network changes. I am not even certain it's the modem files causing this, but perhaps something to do with APN settings and how they are auto-selected in 6.x versus 7.x. At any rate, this is a very annoying issue that I am disappointed in Motorola for not addressing, or at least releasing a developer bulletin on how to troubleshoot. Makes me pretty certain I'm gonna go to some other company for my next device unless they come out with an update.
There has to be a solution to this. It could even be related to the DMservice/SprintDM/etc apk files that control provisioning and not the modem itself. Although only a guess, I am fairly certain this is why they have not released an official 7.x OTA. How deep can I really go with this without permanently bricking my device's modem? I can probably restore the IMEI if I need to, but my thoughts have been: find these "dm-service apk files" from a 7.x device and use them on the XT1575, flash a modem from a 7.x Moto device or another device that uses the same SoC and runs 7.x, or find another component in Android that puts the 6.x radio functionality into 7.x without back-dating the entire kernel or something. There will probably come a point soon enough where I won't care about bricking my phone in the name of solving this, but I could use all the info I can. Nothing out there like QPST or a qualcomm modem binary editor that works for LTE devices?
Can somebody point me to a thread that contains, or upload a copy of these files from a 7.x Motorola device:
-any/all system APK's that contain the word: "omadm" in the process name (examples are SprintDM, Carrier Provisioning Service, DMService, etc)
Something I thought might be worth pointing out.
(omitted out, I was wrong about this)
Still troubleshooting this issue....
Hi,
I recently bought a T-Mobile S5 (SM-G900T). It's unlocked and I rooted and de-bloated the stock marshmallow ROM. The phone works wonderfully and it was nice getting a brand new phone that meets all my criteria (runs Google Maps fine, removable battery, SD Card, rootable) for under $150.
I use AT&T for my service. I'm wondering if anyone can tell me how to get AT&T Wifi calling working on this phone. The phone is rooted so I'm sure it's definitely possible with enough work but I'd like to know if anyone has already done this.
Thank you.
PS: please don't ask why I didn't get an SM-G900A. I didn't and what's done is done. Return/exchange period is over
If your on ATT prepaid as I am, same phone, they do not support it, only post paid can use that service. Was just at ATT store changing a battery and asked while there.
shellcode said:
Hi, I recently bought a T-Mobile S5 (SM-G900T). It's unlocked and I rooted and de-bloated the stock marshmallow ROM...
Click to expand...
Click to collapse
I don't have this variant myself but, you have a few options.
You can try looking at the following threads/link that's specific to your device for some of those options...
https://forum.xda-developers.com/showthread.php?t=2800402
https://forum.xda-developers.com/showthread.php?t=3736650
https://forum.xda-developers.com/showthread.php?t=2723817
https://forum.xda-developers.com/showthread.php?t=2770849
https://forums.androidcentral.com/t-mobile/421217-wifi-calling.html
... or you could use some type of VoIP (Voice over IP) or SIP (Session Initiation Protocol) app.
Here's a few links to help you with this option.
https://www.androidauthority.com/be...p-calls-wi-fi-calling-internet-calling-87396/
http://www.toptenreviews.com/services/articles/best-voip-app-apple-android/
I don't use any of the above myself but, those would be a good start for you...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
ahvamaria said:
If your on ATT prepaid as I am, same phone, they do not support it, only post paid can use that service. Was just at ATT store changing a battery and asked while there.
Click to expand...
Click to collapse
I am on a post-paid family plan. Wifi calling is definitely supported. I've used it on other AT&T devices.
Ibuprophen said:
I don't have this variant myself but, you have a few options.
You can try looking at the following threads/link that's specific to your device for some of those options...
https://forum.xda-developers.com/showthread.php?t=2800402
https://forum.xda-developers.com/showthread.php?t=3736650
https://forum.xda-developers.com/showthread.php?t=2723817
https://forum.xda-developers.com/showthread.php?t=2770849
https://forums.androidcentral.com/t-mobile/421217-wifi-calling.html
... or you could use some type of VoIP (Voice over IP) or SIP (Session Initiation Protocol) app.
Here's a few links to help you with this option.
https://www.androidauthority.com/be...p-calls-wi-fi-calling-internet-calling-87396/
http://www.toptenreviews.com/services/articles/best-voip-app-apple-android/
I don't use any of the above myself but, those would be a good start for you...
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
Thanks but I don't see any mention of AT&T Wifi calling on any of those T-Mobile ROMs. Maybe I missed something? In either case, I'd prefer not to switch ROMs but I could use it to see what was done to make AT&T Wifi calling work.
I'm not actually interested in phone calls with wifi calling. I want to receive text messages at work where I have no signal.
shellcode said:
Thanks but I don't see any mention of AT&T Wifi calling on any of those T-Mobile ROMs. Maybe I missed something? In either case, I'd prefer not to switch ROMs but I could use it to see what was done to make AT&T Wifi calling work.
I'm not actually interested in phone calls with wifi calling. I want to receive text messages at work where I have no signal.
Click to expand...
Click to collapse
When you say you'd prefer not to switch ROMs, is it because you prefer running the stock / official ROM? Or is it because you don't want to go through the process?
The US Snapdragon variants of the S5 have the same hardware, they're just tuned differently via the EFS/modem settings and run different firmware images based on carrier. You can run a different carrier firmware on your device just fine. I recently completed a switch over on a SM-G900P (Sprint variant) to the SM-G900T (T-Mobile) software. All T-Mobile specific features, including Wi-Fi Calling, are functional as if it was a T-Mobile variant.
What I'm proposing is, if you like the stock software, you can have it, with AT&T features instead of T-Mobile. It'll function exactly as if it were an AT&T variant, purchased as such, rather than as a T-Mobile variant.
The process I used should be applicable to any Snapdragon variant, however. As I had to figure out much of this process for myself, there's no guides or information out there presently. But if you'd like, I could help you through the process.
Moved to Q&A
Arbiter said:
When you say you'd prefer not to switch ROMs, is it because you prefer running the stock / official ROM? Or is it because you don't want to go through the process?
The US Snapdragon variants of the S5 have the same hardware, they're just tuned differently via the EFS/modem settings and run different firmware images based on carrier. You can run a different carrier firmware on your device just fine. I recently completed a switch over on a SM-G900P (Sprint variant) to the SM-G900T (T-Mobile) software. All T-Mobile specific features, including Wi-Fi Calling, are functional as if it was a T-Mobile variant.
What I'm proposing is, if you like the stock software, you can have it, with AT&T features instead of T-Mobile. It'll function exactly as if it were an AT&T variant, purchased as such, rather than as a T-Mobile variant.
The process I used should be applicable to any Snapdragon variant, however. As I had to figure out much of this process for myself, there's no guides or information out there presently. But if you'd like, I could help you through the process.
Click to expand...
Click to collapse
Now, there's an interesting suggestion! Are you saying I can get the SM-G900A firmware from sammobile (or some other source) and just ODIN flash that to my SM-G900T? If so, that would give me AT&T wifi-calling. I was under the impression that there were hardware differences and that you couldn't flash firmware from one variant to another or you'd end up with a brick. I guess that's not true?
I don't particularly *like* the stock firmware but I just want something that will work well with the least amount of tweaking. I'll de-bloat myself it but top speed is not as much of a priority as battery life and all phone functions (camera, bluetooth) working as it did from the factory. So, (debloated) stock is good enough for me.
Thanks!
shellcode said:
Now, there's an interesting suggestion! Are you saying I can get the SM-G900A firmware from sammobile (or some other source) and just ODIN flash that to my SM-G900T? If so, that would give me AT&T wifi-calling. I was under the impression that there were hardware differences and that you couldn't flash firmware from one variant to another or you'd end up with a brick. I guess that's not true?
I don't particularly *like* the stock firmware but I just want something that will work well with the least amount of tweaking. I'll de-bloat myself it but top speed is not as much of a priority as battery life and all phone functions (camera, bluetooth) working as it did from the factory. So, (debloated) stock is good enough for me.
Thanks!
Click to expand...
Click to collapse
Well, any stock firmware is as close to factory functionality as possible. When switching carrier firmware, you gain the features of the target firmware, without any bugs or other problems.
You do have to take care in doing it correctly. It's not meant to be done on an S5, and there's no documented method out there, such as Prince Comsy's Odin for the S7, for example. Also in regards to that, the flash is not done via Odin. There's some parts which require it, however, there's no way to flash a full other carrier firmware via Odin on an S5, as far as I know. The device bootloader rejects the firmware due to a software check failure.
That aside, if done correctly, it functions identically to the desired firmware variant in my testing.
There are only two things you need to concern yourself with. The first is whether your device presently has the proper frequencies activated in its EFS configuration. If not, you won't receive coverage where the bands used aren't active on your phone. If this is a problem, it is possible to manually activate additional frequencies via QPST and QXDM. You may also desire to do this anyways, for increased roaming compatibility and coverage. This is another thing you have to be careful while doing, however.
The second thing to consider, is whether you care about OTA updates. Or more precisely, that you won't be able to use them. This is arguably of little consequence, as its unlikely anymore updates will be released for the S5. But if there is an update, you'll have to apply it manually by the same process used to convert your firmware variant. If you were to accept an OTA, it could brick your phone. This is due to the fact that we don't flash the boodloader from other variants, for safety reasons. An OTA update would likely apply (or attempt to apply) the bootloader from the converted firmware. The outcome of this is unknown. It's possible that it works without issue, but if it doesn't, it has the potential to hard brick the device. For this reason, I haven't tested it, as other firmwares can be loaded by a mismatched bootloader without issue. Due to that, I recommend disabling all OTA checks / settings for additional safety. As a note, updates via Kies, Smart Switch, Odin, or any other utility are also a no-go. Updates must be applied manually if you want them.
If neither of those two things is a problem for you, then you might be happy with converting your firmware to another variant. It does work quite well when done correctly.
If you're interested in doing this, I could guide you through the process. It would be more convenient via instant messaging, so we could directly communicate in real time for the parts that will be specific to your device.
If you would like to, send me a PM to coordinate IM details. I use Telegram and Wire, and if neither is suitable for you, and you're okay exchanging phone numbers, I also use Signal if you'd prefer. I also use some other services as well, though I less prefer them. If none if the above are suitable, perhaps we can find one we have in common.
shellcode said:
Now, there's an interesting suggestion! Are you saying I can get the SM-G900A firmware from sammobile (or some other source) and just ODIN flash that to my SM-G900T?...
Click to expand...
Click to collapse
I could be wrong here but, based upon what I had read (my take on it), I don't believe that @Arbiter was recommending that you install the stock firmware rather an option that Arbiter had suggested to see if the WiFi Calling option is made available (based upon that members experience).
Am I correct @Arbiter?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I could be wrong here but, based upon what I had read (my take on it), I don't believe that @Arbiter was recommending that you install the stock firmware rather an option that Arbiter had suggested to see if the WiFi Calling option is made available (based upon that members experience).
Am I correct @Arbiter?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
To clarify, I'm suggesting that if you want all carrier specific features (including Wi-Fi Calling), it can be done by cross-flashing the target carrier's firmware.
If the target firmware is correctly installed, and the corresponding CSC is properly installed in both the support files and configured in EFS (a simple three letter change to a file on the EFS partition), then all features for that carrier will be available.
This is the only way I know to achieve full functionality with another carrier's features. There doesn't appear to be any available research or success in simply transplanting the necessary programs and libraries to handle carrier features on a non-carrier ROM for the S5.
Arbiter said:
To clarify, I'm suggesting that if you want all carrier specific features (including Wi-Fi Calling), it can be done by cross-flashing the target carrier's firmware...
Click to expand...
Click to collapse
I apologize for my misunderstanding but, I will have to "Respectfully Disagree" with you.
Though Custom Firmwares may be lacking some/many of the carrier specific apps and those features these apps utilize but, there's ways to obtain them either directly or indirectly via installing, flashing and/or porting them to a device.
Just to clarify... I'm not stating that this applies to all carrier specific apps and/or features but, I've seen this done for many of them on a Verizon S5 device with a custom firmware installed.
Maybe we just have to end this respectfully with "Agreeing to Disagree"... :thumbup:
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I apologize for my misunderstanding but, I will have to "Respectfully Disagree" with you.
Though Custom Firmwares may be lacking some/many of the carrier specific apps and those features these apps utilize but, there's ways to obtain them either directly or indirectly via installing, flashing and/or porting them to a device.
Just to clarify... I'm not stating that this applies to all carrier specific apps and/or features but, I've seen this done for many of them on a Verizon S5 device with a custom firmware installed.
Maybe we just have to end this respectfully with "Agreeing to Disagree"... :thumbup:
~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Since you've seen this done, would you point us towards the correct direction in order to get at&t wifi calling on a G900T-based stock (or non-stock) OS? I have been trying different techniques and have only succeeded in causing bootloops :\
I don't want to use a bootloader locked G900A OS.