Database Info

[Discuss]How to Creat a QR-code to register new carrier profile

I had read some articles about eSim
and got the below Conclusion.
Only for docomo(Japan), but I think it maybe same to other countries providers!
1. eSim default has a limited profile.
It's initially stored in the eUICC when it is shipped. It is a limited-application communication profile used only for downloading and switching Operational Profiles for connect to the carrier.
The parameters are:
ICCID, MSISDN(sounds tel-bum), IMSI
2. The profile that be download to eSim, is generated on the server by staff of carrier, and if it's has been registered, it will be deleted.
So, if you want to register to GearS3 with another device's eSim number, you need to ask the carrier to generate profile again.
Embedded UICC Remote Provisioning
https://www.nttdocomo.co.jp/english...echnical_journal/bn/vol16_2/vol16_2_005en.pdf

Many app support to create QR code.
I scan a Germany Carrier's QR code that use for activation,
Got the below URL.
Of course, it lack many parameters that contained by default profile in the eSim.
0$https://prod.aironv4.gi-de.com/sr/rest$3528FF91251647CA130669E2B393584F

The URL OF ESIM server(docomo) is this.
From My asus d01j tablet, I plan to use this esim to register my SM-r765f
https://usmdp-001-prod-muc1-eb.venyonservices.com

Au, Another carrier's eSim, xml
It likes all of them use same site,
venyonservices.com

Many Thank you guys!
Plz refer me more info to creat QR-code to those carriers who don't supply QR for their Lte internet plan!

Another question!
Any guys know how to export an activated eSim profile?
Maybe We can make a dummy profile to download to gear3
A COPY eSim!

1.
Your SM-R765F is allready arrived?
2.
I can upload old/obsolete Firmware from SM-R765F for study...
Maybe you can find which files are eSIM related...
We have also SM-R765T and SM-R765A Firmware for study...
3.
German?
Du kannst nicht aus Versehen mich verstehen?
Best Regards

Dear brother ad free
Yes I receive the sm-r765f ,
buy from a Singapore girl who was luck for hit it in lot, and sell it on BBS.
It's amazing that I got a total brand new one and no registration for esim. Of course the ICCID is Singapore number dummy number(Singapore country code is 525, but this is 033!! ****The first digit of the mobile country code identifies the geographic region : 0 - Test networks***). See attached file.
So I think if can't replace it, maybe I can add necessary parameters to QR-code to overwrite.
Any way to export 765f's firmware? Tell me plz if know.
Thanks a lot.
I'm not Germany,
Even I like Germany's culture and products. ^^

It's much appreciated If you guys upload your own QR-code to study together!!!

Embedded-SIM-Remote-Provisioning-Architecture
https://www.gsma.com/iot/wp-content...ote-Provisioning-Architecture-Version-1.1.pdf

Any kind of progress with your project?
Meanwhile "we" have FT30 Combination Firmware for SM-R765F...
No idea if here something usefull eSIM related possible... :cyclops:
Best Regards

i have my new esim qr code but not able to find a way to register it \ set it up on my r765a any one can assist me please ?

What do manufacterers need to enable VOLTE on devices

Not having VOLTE is quiet an annoyance when you have been using it previously on other handsets.
what are the specifics regarding enabling volte by both carieer and manufacterer?
what information do they need to enable the service?

Manufacturers have to include the proper configuration for VoLTE/VoWifi in their devices, e.g. ISM, Gateways, etc.
VoLTE/VoWifi has to be configured a little different than the usual VoIP like e.g. SIP.
The GSM Association has a Device Settings Database (where telco's can provide the needed information for handset manufacturers/OEMs), into slides can be found here: www gsma com/futurenetworks/wp-content/uploads/2017/02/Device_Settings_Database.pdf (insert dots after www and before com)
Sadly, I guess the database is for registered vendors/telcos only..

RipperFox said:
Manufacturers have to include the proper configuration for VoLTE/VoWifi in their devices, e.g. ISM, Gateways, etc.
VoLTE/VoWifi has to be configured a little different than the usual VoIP like e.g. SIP.
The GSM Association has a Device Settings Database (where telco's can provide the needed information for handset manufacturers/OEMs), into slides can be found here: www gsma com/futurenetworks/wp-content/uploads/2017/02/Device_Settings_Database.pdf (insert dots after www and before com)
Sadly, I guess the database is for registered vendors/telcos only..
Click to expand...
Click to collapse
is it the responsibility of the MNO to liaison with the phone manufacturer to provide the VOLTE / VOWIFI settings? (or atleast make available) and thus the manufacturer would update the settings via an update?
is it possible to get the settings manually via a device that already has volte?
what im trying to figure out is this
i have two phones. a huawei p20 and a oneplus 6
they both support the same bands so no issues there
volte works on my p20 and not my oneplus 6 - this is confusing.
my operator clearly favors huawei (as they sell it in store) so they provide the required information (or do they add configuration to the network) to get the volte working
my p20 was not purchased via my telco so there is no telco based firmware required to get it working.
if possible can we pull the information required from the phone / telco and make available for others to enable VOLTE?

From what I think I read: MNOs: At least the three big players here in Germany whitelisted tested handsets until about beginning of 2017 - then I guess they decided they tested their networks enough and now you can read on their pages that it's (solely?) the OEMs part of work to include the correct config tu support VoLTE/Wifi in their Firmware (e.g. Android release).
In principle, the MNOs should send the needed details how to configure for VoLTE/VoWifi to GSMAs database, where the phone manufacturers could access it to implement in their phones - so there's no contact between MNO and phone OEM necessary at all.
Of course, if a MNO sells a branded phone, they make sure that phone had that specific MNOs VoLTW/VoWifi settings embeded (and maybe ONLY for that MNO ) .
Maybe if we find a Qualcomm Snapdragon 845 based phone we'd be able to copy the configs for other providers. Seems the OP6 currently (5.1.8) has these configs included:
OnePlus6:/data/vendor/radio/modem_config/mcfg_sw # cat mbn_sw.txt
cat mbn_sw.txt
mcfg_sw/generic/apac/airtel/volte/mcfg_sw.mbn
mcfg_sw/generic/apac/idea/commerci/mcfg_sw.mbn
mcfg_sw/generic/apac/reliance/commerci/mcfg_sw.mbn
mcfg_sw/generic/apac/vodafone/volte/india/mcfg_sw.mbn
mcfg_sw/generic/china/cmcc/commerci/volte_op/mcfg_sw.mbn
mcfg_sw/generic/china/cmcc/lab/conf_vol/mcfg_sw.mbn
mcfg_sw/generic/china/cmcc/lab/nsiot_vo/mcfg_sw.mbn
mcfg_sw/generic/china/cmcc/lab/tgl_comb/mcfg_sw.mbn
mcfg_sw/generic/china/ct/commerci/hvolte_o/mcfg_sw.mbn
mcfg_sw/generic/china/ct/lab/cta/mcfg_sw.mbn
mcfg_sw/generic/china/ct/lab/volte_co/mcfg_sw.mbn
mcfg_sw/generic/china/cu/commerci/volte/mcfg_sw.mbn
mcfg_sw/generic/eu/ee/commerci/mcfg_sw.mbn
mcfg_sw/generic/eu/elisa/commerci/fi/mcfg_sw.mbn
mcfg_sw/generic/eu/h3g/commerci/denmark/mcfg_sw.mbn
mcfg_sw/generic/eu/h3g/commerci/uk/mcfg_sw.mbn
mcfg_sw/generic/eu/telefoni/commerci/uk/mcfg_sw.mbn
mcfg_sw/generic/eu/telia/commerci/norway/mcfg_sw.mbn
mcfg_sw/generic/eu/telia/commerci/sweden/mcfg_sw.mbn
mcfg_sw/generic/na/att/volte/mcfg_sw.mbn
mcfg_sw/generic/na/tmo/commerci/mcfg_sw.mbn
mcfg_sw/generic/oem/lab/volte_pt/mcfg_sw.mbn
mcfg_sw/generic/oem/lab/volte_te/mcfg_sw.mbn
mcfg_sw/generic/oem/oversea/commerci/mtnl_bsn/mcfg_sw.mbn
mcfg_sw/generic/oem/oversea/commerci/mcfg_sw.mbn
mcfg_sw/generic/sea/chunghwa/commerci/tw/mcfg_sw.mbn
mcfg_sw/generic/sea/fareasto/commerci/mcfg_sw.mbn
mcfg_sw/generic/sea/tm/commerci/mcfg_sw.mbn
mcfg_sw/generic/sea/ytl/commerci/mcfg_sw.mbn
Click to expand...
Click to collapse
The files seem to have a digital signature, so it's unlikely that we'd be able to edit them, even if we would just know the correct parameters. Also, not everything is for VoLTE/Wifi.

RipperFox said:
From what I think I read: MNOs: At least the three big players here in Germany whitelisted tested handsets until about beginning of 2017 - then I guess they decided they tested their networks enough and now you can read on their pages that it's (solely?) the OEMs part of work to include the correct config tu support VoLTE/Wifi in their Firmware (e.g. Android release).
In principle, the MNOs should send the needed details how to configure for VoLTE/VoWifi to GSMAs database, where the phone manufacturers could access it to implement in their phones - so there's no contact between MNO and phone OEM necessary at all.
Of course, if a MNO sells a branded phone, they make sure that phone had that specific MNOs VoLTW/VoWifi settings embeded (and maybe ONLY for that MNO ) .
Maybe if we find a Qualcomm Snapdragon 845 based phone we'd be able to copy the configs for other providers. Seems the OP6 currently (5.1.8) has these configs included:
The files seem to have a digital signature, so it's unlikely that we'd be able to edit them, even if we would just know the correct parameters. Also, not everything is for VoLTE/Wifi.
Click to expand...
Click to collapse
mcfg_sw/generic/eu/h3g/commerci/uk/mcfg_sw.mbn
It seems my network three uk is included, however VOLTE doesn't work for me.

See my last sentence in my last post
Those modem configs seem to include seperate config files for selecting the correct bands, etc.
I'd guess that mostly the directory entries with "volte" contain VoLTE settings

virtyx said:
is it the responsibility of the MNO to liaison with the phone manufacturer to provide the VOLTE / VOWIFI settings? (or atleast make available) and thus the manufacturer would update the settings via an update?
is it possible to get the settings manually via a device that already has volte?
what im trying to figure out is this
i have two phones. a huawei p20 and a oneplus 6
they both support the same bands so no issues there
volte works on my p20 and not my oneplus 6 - this is confusing.
my operator clearly favors huawei (as they sell it in store) so they provide the required information (or do they add configuration to the network) to get the volte working
my p20 was not purchased via my telco so there is no telco based firmware required to get it working.
if possible can we pull the information required from the phone / telco and make available for others to enable VOLTE?
Click to expand...
Click to collapse
Hey mate, can you upload your p20 mbn files?
I need specifcally bouygues .
If you guys need, I have pixel 3(snapdragon 845 as well) and i can upload all my mbn files for reference?

Verizon SM-T387V to T-Mobile SM-T387T (carrier cahnges)

Hello all,
I always root my phones and tablets, unlock bootloaders and install custom roms; but only doing with my ex carrier big red vzw; I finally left and switch over t-mobile.
I was able to unbranded my vzw HTC 10 and now it’s fully unlocked. My question now is for my Samsung tablets:
I was reading and learning about Samsung CSC codes on droidnews site; and it says this:
https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/
What’s CSC on Samsung?
CSC is the abbreviated form of “Consumer Software Customization” or “Country Specific Code “. CSC is an essential component of Samsung firmware binaries and it contains customized settings, system configurations, localizations and geo-specific things such as the system language, APN settings, and carrier-branding.
That’s is say, Samsung may release the same model of a phone in a country or region with different CSCs. For example, if you live in the United States and own a Samsung Galaxy phone, the CSC or product code of your device may be one of the following depending on the fact whether it is unlocked, open or carrier branded.
Here is my question:
Is it possible to flash the full t-mobile software (all4 files) and change my vzw tablet to t-mobile?
Like it says above “Samsung may release the same model of a phone in a country or region with different CSCs.”
Original Verizon model SM-T387V
Original T-Mobile model SM-T387T
Thanks

Many websites not working on Smarty/Three network

Hello,
I recently signed up to the SMARTY UK phone network, which is owned by and operates on Three. Great value, but for some reason I'm having issues connecting to many sites and apps - half the internet works, half doesn't! Their customer service haven't been able to help. So if you're up for a challenge, I've listed below the details and everything I've tried so far. Hopefully someone with the technical understanding will be able to advise what is happening here.
Issue: Many websites return the following error...
This page isn’t working
yahoo.com didn’t send any data.
ERR_EMPTY_RESPONSE
Click to expand...
Click to collapse
Note: This is a generic error meaning it can't connect to the website.
My phone: Samsung Galaxy S9 - from Australia, where I recently returned from, but is the G960F "Global/Europe, single SIM" model (specs here). Android 10.
Network: SMARTY. They use frequency bands 1 (2100MHz), 3 (1800MHz) and 20 (800MHz) according to 4g.co.uk. All these are supported by my phone if I'm not mistaken.
Network status: I have a strong, 4G connection in London E10 with the recommended APN settings. The default APN is three.co.uk but their site says to use mob.asm.net. I've tried both, restarting phone each time. Also tried the APN Type as both 'Default' and '*'. The networks adult filter is turned OFF.
What about other UK SIMs?
Asda Mobile (EE) and Giffgaff (O2) both work fine in the phone.
What about when you try it in a different phone?
When the SIM is in my partners iPhone, all websites work.
Running through a list of most popular websites, as well as others I've tested, here's some websites that do and do not work, to see if anyone can identify some trends:
Examples of websites that load successfully:
Google.com, Google.co.uk
Wikipedia.org
Duckduckgo.com
Reddit.com
Qq.com (China)
Microsoft.com
Bing.com
Ebay.com, ebay.co.uk
Indeed.co.uk (not dot com)
Examples of websites that fail to load:
Yahoo.com
Amazon.com
Google.com.hk (Hong Kong)
Baidu.com (China)
Vk.com (Russia)
Indeed.com
Example.com
Avforums.com
xda-developers.com
Androidforums.com
DNS
I've tried using different DNS servers - Google Public DNS (8.8.8.8), OpenDNS, 1.1.1.1, etc. and restarting to no avail.
Tor
When I connect through Tor (e.g. Orbot app), as I am now to post this, all sites work.
Many thanks,
Chris

CellBroadcast and Emergency Warnings on Android - is it a mess?

Hey,
Germany is implementing EU-Alert (ETSI TS 102 900 [1]) at the moment and referring to the local News, it is a huge mess [2].
But let's start at the beginning.
CellBroadcast is a core component of each mobile network generation (2G,3G,4G,5G,...) and part of the 3GPP spec. CellBroadcast basically allows the network to send a simple SMS to all mobile phones connected to a specific base station. Thes SMS-CB are sent with a Message Identifier (aka Channel, aka Topic) which gives them a special purpose by convention. e.g. ID / Channel 50 is often used for area related information [3], while channel 207 might broadcast local weather information. Since not all Channels are standardized, there is also the option to broadcast an Index that lists all channels with a description. And since users probably don't want any message broadcasted, users have to subscribe to these channels.
Since decades now, CellBroadcast is also used for public Emergency Warnings. This means that, by definition of a country, a specific channel is used to broadcast Emergency Warnings. Long time ago, in many countries it looks like Channel 919 was used for this purpose. For this to work properly, mobile phones were instructed to subscribe to channel 919 by default and also use a special ringtone (even if muted) to alert such a message.
Later - over 12 years ago - additional channels from 4370-4399 were standardized in ETSI TS 123 041 [4] for public warning systems like CMAS, EU-Alert, KPAS. All using the same channels which is beneficial for global roaming.
Android of course supports these public warning systems specified in ETSI TS 123 041 [4] since at least Android 4.2.2 [5]. And nations that use these systems already, like CMAS in the US, report very high and reliable coverage.
However, referring to German news [2] and government, not many phones that are currently on the market will actually support EU-Alert in Germany, despite already supporting EU-Alert in Netherlands or CMAS in the US.
How is this possible when exactly the same SMS-CB is broadcasted, just in a different country?
Golem [2] says that Samsung and Google already confirmed that EU-Alert is currently not supported in Germany, but updates will be rolled out to recent devices.
This strongly suggests to me that OEMs like Samsung and Google actually added country specific filters/configurations for these public warning systems to their phones without deploying a reasonable fallback. Public warning systems based on ETSI TS 123 041 [4] thus may only work in countries that were known to use these systems when the phone was released.
Isn't this an obvious issue?
Google said, starting with Android 11+ it will be possible to update the CellBroadcastReceiver App via Google Play. So devices with Android 11+ will likely receive an update to support EU-Alert in Germany. For Android 10 and older, OEMs will have to supply updates.
What also confuses me is the fact that all Android Phones I own (Nexus 4 with Android 5, Nexus 5X with Android 8, Pixel 3a with Android 12) here in Germany do actually offer the setting for Emergency Warnings and they are already enabled by default. So I assume they would work? Did Google actually deploy a sane default configuration here already?
But if they did - why isn't it working on ALL Android 11+ Phones already? I'm pretty sure my Pixel 3a uses Googles CellBroadcastReceiver App which is provided through the Play Store. So all Android 11+ phones should already use the exact same App?! Or am I wrong here? So what is this update Google actually needs to provide?
And does this also mean that with Android 11+ OEMs are not allowed / cannot implement their own Emergency Warning CellBroadcastReceiver?
This topic is really confusing to me
Shouldn't it be really simple?
All phones, regardless of the OEM, should have a proper SMS-CB Application which allows you to subscribe to custom channels, view the index, and manage your SMS-CB Messages.
Phones should also be aware of special channels to apply special ringtones etc if needed, but they should have a sane fallbacks!
A phone that knows about NL-Alert and CMAS may call messages on Channel 4370 received in the Netherlands "NL-Alert". But when it receives the same message in Germany, it shouldn't just drop it! It should display it as warning and call it whatever it wants. And if it doesn't know about CMAS / EU-Alert, it should just receive it as regular SMS-CB.
Can't be that hard?
Interestingly enough, Samsung phones allow you to subscribe to custom channels. Google phones do not :/
Should there be a better / more enforced standard, so that a country that wants to implement CMAS/EU-Alert in the future doesn't have to rely on OEMs help?
And finally some technical Questions:
I found zero Apps for Android that would allow me to subscribe to custom CellBroadcast Channels on my Google Android phones. Is this even possible?
Also, is it possible to test these CellBroadcasts somehow? Is it possible to write an App that can inject SMS-CB into the system?
Sorry for the long post, but I think this an important Topic.
Let me know what you think
Do you have experience with these Emergency Warnings already?
[1] https://www.etsi.org/deliver/etsi_ts/102900_102999/102900/
[2] https://www.golem.de/news/cell-broadcast-warum-es-am-warntag-ruhig-bleiben-koennte-2206-165822.html
[3] https://source.android.com/devices/architecture/modular-system/cellbroadcast#channel-50
[4] https://www.etsi.org/deliver/etsi_ts/123000_123099/123041/11.04.00_60/ts_123041v110400p.pdf
[5] https://cs.android.com/android/plat...ternal/telephony/gsm/SmsCbConstants.java;l=58

Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).

Shooting Star Max said:
Hey! I was just researching something about this. Thanks for your detailed post.
I am from Chile and, in my case, my operator had subscriptions to two channels: 919 and 920.
In order to see the Cell Broadcast menu in the Messages app, I had to override a CSC setting (I use a Samsung device), particularly "CarrierFeature_Message_DisableMenuCBMessage") because it seems some Chilean operators ordered Samsung to hide it.
Even then, the Google Cell Broadcast app would not let me modify settings other than test alerts.
In my country these emergency alerts are quite unreliable and are often sent by mistake or to the wrong place (i.e. sending a tsunami alert to an area more than 100 km away from the coast).
Click to expand...
Click to collapse
Can you explain how you disabled this CSC setting and on what samsung phone/os?
You can see Googles/Androids latest default configuration for Chile (MCC 730) here:
https://cs.android.com/android/plat...apps/CellBroadcastReceiver/res/values-mcc730/
The config.xml really has some restrictive features enabled :/

Thanks for your reply!
Please note that all the following information assumes you have rooted your device. It's impossible to override this configuration otherwise.
My device is a Galaxy Note20 Ultra (Exynos version, SM‑N985F) running Android 12, One UI 4.1.
As you might know, Samsung devices include several packages named “CSC”, which define settings according to a sales code matching with a region. For example, a device sold in Chile without a carrier uses the sales code CHO, while one sold by operator Movistar uses the sales code CHT.
In the Galaxy Note20 Ultra, the CSC packages are stored in /optics/config/carriers/single (older Samsung devices might use /omc/).
Once you find the sales code matching with your current configuration, you can grab two files: cscfeature.xml and customer_carrier_feature.json. Taking CHO again as an example, the files would be /optics/config/carriers/single/CHO/conf/system/cscfeature.xml and/optics/config/carriers/single/CHO/conf/system/customer_carrier_feature.json.
These files are encoded, but OmcTextDecoder can take care of that.
In the case of CHO, customer_carrier_feature.json has the value "CarrierFeature_Message_DisableMenuCBMessage":"TRUE", which hides the cell broadcast menu in the stock Messages application. Just replace “TRUE” with “FALSE”, save the file and push it to its location. The next time you reboot your system, it will be applied.
Regarding the link you sent, I think we could get around that configuration by decompiling the GoogleCellBroadcastApp.apk through Apktool, modifying the restrictive values, and then pushing the APK to the device, replacing the original version.

Thank you!
Let me know if you managed to patch your original CellBroadcastReceiver.apk!
I actually tried using Runtime Resource Overlays (RROs) which is described on the official docu about CellBroadcast in Android.
You can find the result here: https://github.com/xsrf/android-de-alert
However, I didn't quite get these RROs. It looked like in Oreo you can use RROs to overlay any resource of any app without any permissions or matching signatures, which is quite a surprise to me?!
On my phones with more recent OS, I get signature mismatch errors and also it looks like apps now have to define what resources can be overlayed ...