Related
Hello,
I'm trying to recover the IMEI for my T869 by following this guide:
http://forum.xda-developers.com/showthread.php?t=1867442
The first step is to put the phone/tablet in diagnostics mode. There are two methods described which do this. The first one ( for TouchWiz devices, which should apply for this device ) involves using codes in the dialer to enable a hidden menu. As my tab doesn't have a dialer, this method doesn't work. I've tried 3rd party software that claim to execute codes on the tablet but they don't work.
The second method involves running a script. This fails because/sys/class/android_usb/android0/f_rmnet/transports doesn't exist on my tablet.
So, any ideas how to put my tablet in diagnostics mode or how to fix the IMEI for it ? I don't have a backup of the efs folder and the current IMEI is the generic 004999010640000.
Thanks.
MichaelIvinov said:
Hello,
I'm trying to recover the IMEI for my T869 by following this guide:
http://forum.xda-developers.com/showthread.php?t=1867442
The first step is to put the phone/tablet in diagnostics mode. There are two methods described which do this. The first one ( for TouchWiz devices, which should apply for this device ) involves using codes in the dialer to enable a hidden menu. As my tab doesn't have a dialer, this method doesn't work. I've tried 3rd party software that claim to execute codes on the tablet but they don't work.
The second method involves running a script. This fails because/sys/class/android_usb/android0/f_rmnet/transports doesn't exist on my tablet.
So, any ideas how to put my tablet in diagnostics mode or how to fix the IMEI for it ? I don't have a backup of the efs folder and the current IMEI is the generic 004999010640000.
Thanks.
Click to expand...
Click to collapse
The Dialer is part of Phone.apk, which won't show up on the T869 normally even if its "installed".
There's a file within framework-res.apk (which is found @ /res/values/bools.xml) which essentially tells the Android OS what features the host device does and does not have. The relevant value is <bool name="config_voice_capable">.
By default the T869 will have:
<bool name="config_voice_capable">false</bool>
Changing that to
<bool name="config_voice_capable">true</bool>
Tells the OS that the device is "voice capable", meaning it can make & receive phone calls. This will then allow the Phone.apk features to show up, provided you have Phone.apk installed.
The process of modifying framework-res.apk is somewhat complicated, and your ROM may or may even have Phone.apk present, depending on what you are using. However, at least now you know why you have no dialer.
DivinityCycle said:
The Dialer is part of Phone.apk, which won't show up on the T869 normally even if its "installed".
There's a file within framework-res.apk (which is found @ /res/values/bools.xml) which essentially tells the Android OS what features the host device does and does not have. The relevant value is <bool name="config_voice_capable">.
By default the T869 will have:
<bool name="config_voice_capable">false</bool>
Changing that to
<bool name="config_voice_capable">true</bool>
Tells the OS that the device is "voice capable", meaning it can make & receive phone calls. This will then allow the Phone.apk features to show up, provided you have Phone.apk installed.
The process of modifying framework-res.apk is somewhat complicated, and your ROM may or may even have Phone.apk present, depending on what you are using. However, at least now you know why you have no dialer.
Click to expand...
Click to collapse
I actually did follow your guide here: http://forum.xda-developers.com/showthread.php?t=1872348 to try to get my native dialer but never got it to work. I know that it should work, but I get endless crashes/reboots if I enable voice capabilities for my tab .. All apps crash seconds from startup. What exact ROM do you have which works for enabling the native dialer? I'm running the official ICS build.
MichaelIvinov said:
I actually did follow your guide here: http://forum.xda-developers.com/showthread.php?t=1872348 to try to get my native dialer but never got it to work. I know that it should work, but I get endless crashes/reboots if I enable voice capabilities for my tab .. All apps crash seconds from startup. What exact ROM do you have which works for enabling the native dialer? I'm running the official ICS build.
Click to expand...
Click to collapse
I pretty much only use CM10. Aorth has nightly builds of it. The last "good" CM10 is cm-10-20130118-UNOFFICIAL-t869.zip, which you can get here: http://goo.im/devs/aorth/roms/t869/
I'm curious, what purpose does retrieving the IMEI serve anyways?
DivinityCycle said:
I pretty much only use CM10. Aorth has nightly builds of it. The last "good" CM10 is cm-10-20130118-UNOFFICIAL-t869.zip, which you can get here: ....
I'm curious, what purpose does retrieving the IMEI serve anyways?
Click to expand...
Click to collapse
Well my tablet has the generic IMEI as stated above. Since about 2 days ago, my tablet hasn't been able to connect to the T-Mobile network. I have had the generic IMEI for some time and it has worked. Now either T-Mobile has decided to start blocking the IMEI from the network or my tablet is physically damaged.
I have bars, I can search for networks and it will find T-Mobile and AT&T, I've tried different SIMs with different plans and also checked the SIMs in other phones and they work. Can you connect to the T-Mobile network with the generic IMEI or do you still have your original IMEI?
MichaelIvinov said:
Well my tablet has the generic IMEI as stated above. Since about 2 days ago, my tablet hasn't been able to connect to the T-Mobile network. I have had the generic IMEI for some time and it has worked. Now either T-Mobile has decided to start blocking the IMEI from the network or my tablet is physically damaged.
I have bars, I can search for networks and it will find T-Mobile and AT&T, I've tried different SIMs with different plans and also checked the SIMs in other phones and they work. Can you connect to the T-Mobile network with the generic IMEI or do you still have your original IMEI?
Click to expand...
Click to collapse
I appear to have my "real" IMEI. I have used CM10 nightlies on this tab pretty much since day 1. Have had no problems connected to the T-Mo data network. I would imagine if the IMEI is messed up you should be able to RMA that device, which sucks
find an app called 'any cut' this will allow you to access all the intents and action your device is capable of.
One of them should be service mode.
be careful....
also , if you really want this I would definetly talk to these guys.. http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-tab-plus-imei-efs-repair/
JTAG'd my GT-P6200. I know yours is the Tmobile variant, but he usually has success with new products, etc.
I would ask him.
He is in Texas US of course..
good luck..
Ok, It's confirmed: T-Mobile has started blocking the generic IMEI from their network. At least that's what I conclude from finding a thread on reddit(can't link but you can google the title) from 3 days ago, exactly when I started having the problem:
Anyone else running a custom ROM and have your IMEI reset to 004999010640000? T-Mobile likely blocked your phone today.
DivinityCycle, Just checked again and your bools.xml edit only works with CM10. I've gotten it successfully going on CM10, but the code that gets entered in the dialer only works on a TouchWiz ROM, as noted in the original thread :facepalm:
When I try the same thing on stock GingerBread / ICS I get endless application crashes / freezes so that basically i can't do anything, even launch an app, not to mention enter a code.
chrisrotolo, AnyCut - Managed to install it and create a shortcut to the ServiceMode action but when I execute that shortcut it crashes and nothing happens.
Any other tips?
you could also try factory mode, which will bring up a calculator.
From there enter the *#*# dialer code to get you into service mode...i forget it off hand but i have posted it numerous times,
also if you try another action shortcut, one that is a submenu of the service,mode main menu, such as network, etc.. and that works, you can usually back all the way up to the main menu in service mode.
also CM ROM may have these .apks removed... should be on stock ROM though.
good luck.
chrisrotolo said:
you could also try factory mode, which will bring up a calculator.
From there enter the *#*# dialer code to get you into service mode...i forget it off hand but i have posted it numerous times,
also if you try another action shortcut, one that is a submenu of the service,mode main menu, such as network, etc.. and that works, you can usually back all the way up to the main menu in service mode.
also CM ROM may have these .apks removed... should be on stock ROM though.
good luck.
Click to expand...
Click to collapse
Factory mode worked for me but did not solve my problem. I managed to put the tablet in "modem" USB mode which from what I understand should be diag mode, what I'm looking for, but Windows( All: 7, XP, 32, 64 ) can't find drivers for it. It's showing up as 7 CDCs.
Anyone have any suggestions or knows what "7 CDCs" is and how do I get to an actual working diag mode from that ?
I dialed *#7284#, got this :
i.imgur.com/5W2HSlN.jpg
for drivers, usually you can dowload heimdall and go to 'zadig' (or something similar), with device in download mode: double click zadig.exe it will install drivers
you should see at least one CDC driver possibly a modem driver as well.
Alternatively another good way to install drivers for me has been PDAnet by june fabrics.
find it download .apk it pretty well walks you through set-up.
Thats the right screen for setting usb to modem, etc..
I've had 2 backup's of my EFS folder since day one.
chrisrotolo said:
for drivers, usually you can dowload heimdall and go to 'zadig' (or something similar), with device in download mode: double click zadig.exe it will install drivers
you should see at least one CDC driver possibly a modem driver as well.
Alternatively another good way to install drivers for me has been PDAnet by june fabrics.
find it download .apk it pretty well walks you through set-up.
Thats the right screen for setting usb to modem, etc..
I've had 2 backup's of my EFS folder since day one.
Click to expand...
Click to collapse
Thanks for the suggestions, but I couldn't get them to work. PDAnet requires that the device be put in regular-ADB mode to install drivers - and does install 'normal' drivers but doesn't install the diag mode drivers. zadig installs a driver for the 7 CDCs device but It's listed as a USB device, not as a COM serial port as required by the application.
chrisrotolo said:
I've had 2 backup's of my EFS folder since day one.
Click to expand...
Click to collapse
Do you really need the extra one or can I have it ? :silly:
Still no success so far.
The only possibility I see Is doing a restore using NsPro, which apparently is the only software that supports the T869.
NsPro v6.5.2 released:
-Added I547, T869, T879 support.
Anybody knows how I can try to fix the tab with NSPro without buying the box + 1 year activation ?
Yeah send it to someone who has one...
Have you contacted mobiletechvideos.com yet? They are US based, but one of the best for these types of things..
chrisrotolo said:
Yeah send it to someone who has one...
Have you contacted mobiletechvideos.com yet? They are US based, but one of the best for these types of things..
Click to expand...
Click to collapse
Thanks, didn't know about them. It seems that they require that the device be shipped.
Has anybody dealt with them before ? How reliable are they / where are they located ?
I am not a developer but a HW guy.
This applies only to i9505 international version with Qualcomm processor as tested.
Please note that whoever tries the following, upon failure and/or ending up with bricked phone(s), incurring any loss, implied or direct, resulting from the application of what is described in this post, including but not limited to time, warranty, update from Samsung including security updates, resources, financial or otherwise,etc., does not point a finger in my direction but, does so at his/her own risk.
(Hope I scared a few).
The unit that I used originally had XXUHPK2 - XST firmware.
Whatever given below are personally experienced after quite a bit of searching, testing and few near misses including SIM not being detected or infinite loops when searching for network to register due to my own experimentation with Modem and NON-HLOS files.
But I never once lost my IMEI as the method is fairly straightforward. Always God "ODIN" is there to the rescue.
This applies to those who do not want an "always on" Jio4GVoice app and prefer to stay with stock recovery. Of course custom recovery can always be installed.
I have used PI1_VOLTE_JIO FW available on this forum but had faced few issues related to calling out at times, more so when I travel long distance. If I stay put at certain places it always worked.
Now to the works:
1. Using ODIN install I9505XXUPOL1_I9505PHNPOL1_PHN FW. - Search to download FW.
Nordic version of FW with PI1 modem "may" be used but I found network search for registering yields less number of networks. I have not tried using the Nordic FW.
2. Root the device using CF-Auto-Root.
3. Search for "Volte fix.zip" and download. Easiest way to get links to download is YouTube. In the zip file I used all files have 07-11-2016 as creation date. I found VoLTEFiles zip too with the same dates but did not try it so far.
4. Watch the YouTube, say, at "watch?v=MlkaziK6AkY" or any other relevant VoLTE zip file installation video to get the gist of the method before attempting.
5. The zip contains an Apks folder and a Files folder. Extract APK, csc folder, CSCVersion.txt and SW_Confgiuration.xml to a known folder preferably in ext-sd if available.
6. Install root explorer. It is under extracted Apks folder. Allow for installation of app from unknown sources.
7. Open Root Explorer browse to /system directory. Rename existing csc folder, CscVersion.txt and SW_Configuration.xml with some leading characters as fall back. The csc folder and the files can optionally be deleted as well.
Root Explorer will require the patition to be mounted as RW saying it is Read Only. Say OK to proceed.
8. Copy and paste the above folder and files obtained from zip to /system.
9. Change permissions via Root Explorer as below:
Touch the folder or file under Root Explorer. Once selected touch 3 dots on top right and select permissions. Given numbers can be directly entered using Octal button.
csc folder - 755 octal
CscVersion.txt - 644 octal
SW_Configuration.xml - 644 octal
10. Exit Root Explorer and Reboot. And wait patiently for a while until the two way sign appears on status bar. It really takes a while.
Call Settings - "Outgoing voice call settings" automatically shows "Use VoLTE when available".
Factory reset does not restore VoLTE icon on status bar and calling is not possible as well. Wait for a while for the phone to complete all processes after setting up. Reboot to get VoLTE back.
It seems to take a while and the Sammy phone will show a report being sent when connected to WiFi... to inform you later when you select "Software Update" that the phone has modified in an un-authorized way, etc.
Calling and messaging works even with WiFi ON.
I have not provided any link as the credit should go where it belongs.
See screenshots in the attached thumbnails.
ODIN Version used 3.12.7
CF-Auto-Root available on this forum.
And most importantly thanks to the developer who created the VoLTE fix files. And a special thanks to @dhiru1602 with his PI1-VOLTE-JIO ROM as it was instrumental in making me search and test.
Does this work on other S4 not for JIO and on other networks?
treysis said:
Does this work on other S4 not for JIO and on other networks?
Click to expand...
Click to collapse
Sorry for the belated reply. I was using it on Jio only as no other nw providers were offering VoLTE at that time. Now the unit is with someone else in another country. I learnt VoLTE is available in that country and will request to get it checked. Will revert with results.
hey, no problem and thanks for the help! Have you heard back from your friend yet?
treysis said:
hey, no problem and thanks for the help! Have you heard back from your friend yet?
Click to expand...
Click to collapse
Yes and a No - On one network it does not show the icon. He is not sure if the ISP actually implemented VoLTE though announced last year. On the other he has not tested as yet. Says needs to get the 4G SIM. Will wait for some more time and revert again.
Ok. I know for sure that my network and my SIM support VoLTE, cause I am using it on another Samsung handset and it's working fine. But on the S4 no luck yet.
Btw. I just put a Malaysian SIM and this enabled VoWiFi in the settings. But couldn't try it as the card is not fully active anymore.
Is there any new instruction how to force VoLTE and VoWifi to work on PIXEL3?
Features works great on S9, SIM card is provisioned. The IMS options are blacked out on PIXEL.
Does any Custom ROM forces the feature to work even if carrier says that they don't officialy support it?
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
wangdaning said:
If it is just that your provider does not allow this service on Pixel you could try MagiskHide Props Config module to change device fingerprint to match a phone that is supported by your carrier. Not sure if it will word, but worth a shot.
Click to expand...
Click to collapse
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
mxtuu222 said:
Carrier says that the issue is not on their side, they claim that they have enabled services. I checked on S10 with the same SIM card, both VoLTE and VoWifi works without issues.
The other thing is that I don't want to dive deep into changing factory images to force the features. I would need to unlock bootloader and root phone.
Until now Google does everything just to avoid questions and providing support for modem issues for other carriers than US.
Click to expand...
Click to collapse
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
wangdaning said:
It might have something to do with the modem files in the vendor partition, we have that issue here in China. Only way to fix that is to be rooted and systemlessly make the phone read the files correctly. Custom roms cannot change the vendor.img.
Click to expand...
Click to collapse
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
mxtuu222 said:
;/ so probably there is no easy workaround. Rooting and modem modification makes it too complex. Especially that on Android Q there is a problem with USB debugging mode for Qualcomm in fastboot
PIXEL2: [GUIDE]Enable VoLTE for unsupported carriers
Click to expand...
Click to collapse
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
wangdaning said:
Rooting is not really dangerous, and the modem modification makes no real changes. It is systemless changes, which means no files are actually modified. What carrier do you use, odd that a US carrier would not be supported natively by google.
Click to expand...
Click to collapse
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
mxtuu222 said:
I need to have an option for carrier PLAY in POLAND.
I'm curious if just a root and enabling VoEnabler packet from MAGISK will be enough.
Some of the guys from PIXEL 2 were suggesting to use modem configs with VoLTE, VoWifi from the same chipsets Qualcomm 845 and putting it to PIXEL 3.
Click to expand...
Click to collapse
That is problematic, as looking at the modem files (on my device), their is nothing under the folders for PLAY network. That would mean you could get the modem file from another similar device that has it, but the magisk setup would need to change two files instead of one. You would have to mock load a mbn file for your provider. You would need to change /mcfg_sw/generic/"modem file you want to try" and /mcfg_sw/mbn_sw.txt to include the directory of the file you want to include.
In reality, those mbn files you get might never work. This is google borking their work. For us in China, the modem files are their, they just refuse to reference them. For you the files are not even there it seems.
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
wangdaning said:
Try this. You will need magisk root to do it. You will also need to edit the zip file with the mbn file you can get a hold of. It will go in this file "For Help Pixel 3 LTE-VoLTE Enabler.zip\system\vendor\rfs\msm\mpss\readonly\vendor\mbn\mcfg_sw\generic\EU\Play" directory. It will simlpy load the modem file you need/want/got from a similar device at boot(just name it mcfg_sw.mbn and put it in there replacing the "put mcfg_sw.mbn here.txt"). You also need to delete the files in the description of the module (these are auto generated files) before this will take place. Good luck.
If you are doubtful, have a good look at what I am asking it to do.
Click to expand...
Click to collapse
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
mxtuu222 said:
Great, thank you for all the tips. I will try to find some mbn files from NOKIA modems.
Do you know if it's possible to unlock the bootloader, root, make possible changes, unroot, lock bootloader?
Is the modem file will be permanently on vendor partition even if I install newest OTA?
Click to expand...
Click to collapse
I am pretty sure you will need to keep root, as magisk is mocking the modem file you need. It somehow could cause the phone to connect and after the phone stays connected, but I do not see how that could work.
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Wow! Well done
Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?
Firmware File Location
htcmage said:
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Click to expand...
Click to collapse
Hi there,
How did you find the firmware file? Did you extract the SIN from the localized firmware (for example custom U.S. or via another method? Also does this work for Xperia 1 or only Xperia 1 II
veerasammy778 said:
Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?
Click to expand...
Click to collapse
If you have Xperia 1. Just to enable VoLTE, either flash SEA firmware or Just flash these from the Japanese version.
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe
I'm using Android 9 and Flashed OEMs from Japanese latest .191 firmware which you can get by downloading using XperiFIrm and Newflasher from @munjeni .
@jeoleo7 I have Xperia 1 SO03L docomo version single sim phone. Unlocked carrier for use in India. Currently on android 11 version.
Can I flash below files and enable volte ?. Hope this will not affect sim unlock status to locked again. Need your help !
Quote"
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe"
Will you be able to share the above file because I dont know how to extract it from android 11
@ralf_waldo
I have tried on my J9110 dual.
These files I have listed are just the OEM only and are region specific.
I easily achieved HD voice calls on LTE in my phone when I was using firmware from Ukraine or any other region.
I also tried Single sim variant flashing on my dual sim version.
I tried J8110 EE UK (found the clock and few changes different from my original).
Hence, just flashing these files won't lock your phone since its already unlocked.
You may backup your important things before doing anything.
Customized_JP_OEM_332.zip
drive.google.com
i need enable Volte on Sony experia 1 model : SO-03L please help me.
I just bought a Xperia XZ2 H8276 since the sim pins finally broke in my Xperia X Performance after about 4 year, word of advice don't make a sim work. Was not finding a Xperia XZ2 compact under $200 and the newer 5's are expensive, so that was the choice I made. It did not dawn on me that the move to volte only would make it hard to get newer unlocked phones on a nework. In trun looking into options pertaining to volte, switching to verizon was the only one that seemed to have a viable path. Talked with at&t where I found them unwilling to add my imei and don"t see a mdn that is clear cut for them, do see a mdn for tmobile but no service by my house. Verizon dose have dmd and they got the XZ2 compact, so there was light at the end of the tunel. So got the cheapest volte phone that I could find to activate a sim on, a moto e5 play is what I found. Will get to aguing with them now to add my imei since it work, unsure how that is going to go.
To get statrted a activated sim is needed and was done using the moto e5. After activation, need to talk with someone and have them check that sim the sim is CDMA-less with HD voice only. Best place I found to do that is start a chat with someone on this page, click chat in bottom right.
Verizon HD voice
For how I got the XZ2 to work on verizon gose like this based on many failed attempts. What I ended up doing is flashing H8216 Vodafone_Global_52.1.A.3.49-R9C firmware with H8314 Customized US_52.1.A.3.137-R7C oem sin files with newflasher, you can get these these off xperiafirm.
NewFlasher
XperiaFirm
Now with that in order, the verizon mbn needs added but need root to do so. If you dont have twrp that need installed and be sure to sideload magisk at the same time, other wise you will have boot loop to deal with.
TWRP
Magisk
After the phone has booted into the os, you need to now install the magisk app. Run this from whre you downloaded the application to your pc or install from the browser on the phone, need to cd to the place of download first if using terminal.
adb install Magisk-v23.0.apk
Magisk app
Here is the verizon mbn I pulled from the XZ2c modem sin.
Verizon mbn
That needs copyed to the phone SD card and use Root explorer to copy the mbn where it gose. I tryed PDC but could not get the drivers to work.
Root Explorer
You can you use this to install it if debug is on or down from the phone browser, cd to where you downloaded the file then...
adb install RootExplorer.apk
Now in root explorer, this is the destination to go and can only go there if root has been granted. If you dont get the promt to grant root go into magisk, click the shield at boot then the slider by the app. To copy the generic folder here from the sd card, click and hold it till hilighted where you can click the two papers stacked at the top. There will now be a clip board icon in the bottom right, do to the destination and click it.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw
The internal and external sd card will be one these two locations, ether use "adb push" or mtp to the put the directory on the sd card.
/storage/*-* *=a string of letters and numbers
/storage/emulated/0
/storage/self/primary
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see this under current modem config
row/verizon/vl/us
Now dial this.
*#*#4636#*#*
Under phone information set network type to lte only and should see voice type lte. If all went well, you should now be able to make phone calls.
I would like to move on to installing lineage-os but volte was not working there. I need to use this phone for work, so am not going to get into debuging that. Be my guess to try but Im not sure what brakes installing that.
I got some help from junkie2100 and give thanks to those that have posted info/software that lead me this far in gettting volte working. Here are some the clues that aided in the journey.
clues
clues
clues
As for tmobile, you might be able to replicate this but intead use oem sin's from the xz3 H8416 US along with pulling its mdn out its modem sin. Not sure what is special in the oem sin that pertains to setting up the given carrier, so unsure what is needed to get at&t to work but you free to experiament if you choise just I will not be much help.
Thanks for taking the time to put this together, the information on getting VoLTE working in the US on the XZ2 seems to be pretty scattered across various threads over the last several years, so I appreciate you placing this here.
I am not on Verizon, but I have been trying to figure out how to get this working on T-Mobile. I have followed some other threads that point to downloading the XZ3 OEM sin files as part of its Customized US Firmware like you mentioned, replacing those in the stack for the XZ2 firmware of a matching/similar version, and flashing to my device. I noticed after doing that VoLTE is provisioned (greyed out but turned "on"), but the modem config when checking my settings is still "Unknown." In addition to that, setting the device to "LTE Only" causes calls to not be placed, and "LTE Preferred" leads to calls dropping down to 3G like they originally were before trying to flash anything.
I could maybe use a little help in understanding what you mean be "pulling the mdn out of the modem sin." Is this an additional step to just flashing the two OEM files mentioned above and if so, where would I find it and go about setting it up?
Appreciate it.
The mbn file you need is in the modem sin from the xz3 firmware and this is the binary you need to extract it, put both the unsin binary and modem_X-FLASH-ALL-B6B5.sin in the same folder. This is the config file used by the oem sin to setup the volte.
unsin binary
Now cd to the folder that has both those and run these commands.
./unsin ./modem_X-FLASH-ALL-B6B5.sin
mkdir ./modem
sudo mount -t vfat -o loop modem_X-FLASH-ALL-B6B5.img modem/
You now have the modem sin extracted and the image mounted in folder modem. From there you need a copy of this tmobile folder and move it to the sd card on the phone.
/image/modem_pr/mcfg/configs/mcfg_sw/generic/row/tmobile
Now you can umount the modem image.
sudo umount -t vfat modem_X-FLASH-ALL-B6B5.img modem/
Now on the phone in root explorer that tmobile folder gets copyed to here.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/row
In this file you will also need to add these two lines so the mbn can be found.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw//mbn_sw.txt
mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn
mcfg_sw/generic/row/tmobile/vlvw/us/mcfg_sw.mbn
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see one these under current modem config
row/tmobie/vl/us
row/tmobile/vlvw/us
Would anyone care to guess if a rooted/ rom'ed 8216 model of the XZ2 will work on T-mobile now that they have declared many older phone models incompatible (perhaps related to VoLTE capability)? 1mouse3 does your phone still work on T-Mobile? Thanks!