LG VoLTE FIX [ Rooted Stock Based Rom] [JIO] - LG G5 Guides, News, & Discussion

LG VoLTE FIX [ Rooted Stock Based Rom] [JIO] - LG G5 Guides, News, & Discussion

You are Responsible for what you do to your phone. Don't Blame me for ANYthing. BACKUP before making any changes
NOTE-
-This method consists of Editing Build.prop & Volte configuration file in cust folder.
- This method may not work for all but it will give you some idea about how things are going on.
- Im not a Developer and English is not my native language.
Complete method and explanation-
Step 1- (For fulmics rom you can skip this step as volte in build.prop is already enabled)
Editing build.prop file
GO to build.prop file in System folder via any root explorer and paste this command at last.
Code:
ro.lge.supportvolte=1
After pasting this command , leave a blank line at last and save. Now reboot your phone , it will enable Volte option in call or network setting. Some people achieve volte services only by doing this step but if volte button in setting dont do anything , proceed to step 2.
Step 2(General)-
Editing a file in cust folder.
Go to Cust > open_com >_config > config_open_eu > vo_config.xml
In this file replace MCC and MNC values according to your region and network. Reboot.
Step 2 (For fulmics rom , guided by @xpirt )-
A-Add following 2 lines at the end of build.prop with a blank line at last
Code:
ro.lge.capp_cupss.rootdir=/cust
ro.build.sbp=1
B- Flash the zip in attachment.( It will add cust folder contents with correct permissions. If this method fails or you face any issues you can delete all the files and folders from cust folder)
C- Follow step 2 (General)
Step 2 with Explanation and Guidance
Maximum time we don't have volte services because we are using a phone of different region or with a carrier other than default.
Cust folder consists of settings and configurations related to the region and carrier. Whenever our phone boots up it detects the carrier or region in which we are using our phone and load the settings according to the network or region. For detection and loading desired configuration phone use 2 codes MCC (mobile country code) and MNC (mobile network code ). You can find mcc and mnc from apn setting or just google including your country and carrier.
For example i am having european h850. so the configurations for all the european countries and their carriers are stored in cust folder. Now what if i boot up the phone in the region other than europe or started using a carrier not included in cust folder or delete all files in cust folder. In this case phone loads the " Open Com " configuration which are not specific to any carrier or region.
So for this method our phone must have all files in cust folder ( in fulmics rom cust folder is empty ) and our phone must be booted with 'opencom' configurations . If you are using any customised stock rom (for h850) or if in software version (under 'about phone' ) you see 'euroxx' it may be means your phone is booted up with '' open com '' configurations.
Now via any root explorer go to -> Cust > open_com >_config > config_open_eu > vo_config.xml
In this file replace MCC and MNC values according to your region. and reboot. That's it
All this worked for me on h850. I dont know about other models.. You can use theory in your own way.
Thanks to @xpirt
Hit thanks if helped

Nice explanation.
Im using genisis mm rom with working volte (edited build.prop). I tried to flash fullmics rom & there is no jio network. Edited build.prop as per the steps mentioned but multiple reboots occur.

vignesh_may28 said:
Nice explanation.
Im using genisis mm rom with working volte (edited build.prop). I tried to flash fullmics rom & there is no jio network. Edited build.prop as per the steps mentioned but multiple reboots occur.
Click to expand...
Click to collapse
Thats because you are not on nougat modem.
For coming to fulmics from marshmallow rom... You first have to flash nougat kdz or full 20a nougat zip from autoprime's thread. Instead of flashing full nougat rom you can also try flashing nougat bootloader and modem from same autoprime thread ( but i only tried with flashing full nougat 20a zip when shifting from marshmallow to nouagt )

Volte is just an option to enable from mobile or is it necessary the network should have the support for VoLTE service?
I'm on LTE network, but every time when I receive call it, always shift to 3G or 2G network, but I don't know my network support Volte service.

arfan.chatha said:
Volte is just an option to enable from mobile or is it necessary the network should have the support for VoLTE service?
I'm on LTE network, but every time when I receive call it, always shift to 3G or 2G network, but I don't know my network support Volte service.
Click to expand...
Click to collapse
VoLTE( Voice over LTE)
Volte is an option that can be enabled from handset and it is also necessary that the network should support volte.

Is there any way to obtain volte (reliance jio) in custom roms? Feel stock is heavy.

vignesh_may28 said:
Is there any way to obtain volte (reliance jio) in custom roms? Feel stock is heavy.
Click to expand...
Click to collapse
Not yet.. But i directed some developers to volte patch thread.. At this point all are busy to make custom roms fully stable , once stability is achieved ...they may work to solve volte issue .

akki7636 said:
Not yet.. But i directed some developers to volte patch thread.. At this point all are busy to make custom roms fully stable , once stability is achieved ...they may work to solve volte issue .
Click to expand...
Click to collapse
brother, a long shot im trying this in my g2. It may not work. i understand. but i just dont want to miss the minute chance it might..
the problem is direct flash wouldn`t help as the /cust position is not in /dev/block/bootdevice/by-name/cust. the actual position is in /dev/block/platform/msm_sdcc.1/by-name/ folder. so i changed the flashing script to such a place but it didnt work. besides i tried "dd if= of=" flashing cust.img to /cust. but it didnt help either, now my cust folder seen in root folder in file explorer is empty. i think the mount command is not suitable for g2. please help in changing. thank you

gpkumaran said:
brother, a long shot im trying this in my g2. It may not work. i understand. but i just dont want to miss the minute chance it might..
the problem is direct flash wouldn`t help as the /cust position is not in /dev/block/bootdevice/by-name/cust. the actual position is in /dev/block/platform/msm_sdcc.1/by-name/ folder. so i changed the flashing script to such a place but it didnt work. besides i tried "dd if= of=" flashing cust.img to /cust. but it didnt help either, now my cust folder seen in root folder in file explorer is empty. i think the mount command is not suitable for g2. please help in changing. thank you
Click to expand...
Click to collapse
This method works when volte support is embedded in the rom ( framework). Can you see volte settings in hidden menu ?

akki7636 said:
This method works when volte support is embedded in the rom ( framework). Can you see volte settings in hidden menu ?
Click to expand...
Click to collapse
Yes sir. Cust is also getting flashed with dd command / by your zip. Only problem is the folder doesn't get mounted.I've even tried mount -o remount,rw -t ext4 command. But it doesn't mount. Please help me im a noob in this aspect

gpkumaran said:
Yes sir. Cust is also getting flashed with dd command / by your zip. Only problem is the folder doesn't get mounted.I've even tried mount -o remount,rw -t ext4 command. But it doesn't mount. Please help me im a noob in this aspect
Click to expand...
Click to collapse
Sending PM

akki7636 said:
Sending PM
Click to expand...
Click to collapse
Tried contacting him. No response.

Provide the files
Please provide the files of cust folder who have working voLTE.

braindeductions said:
Please provide the files of cust folder who have working voLTE.
Click to expand...
Click to collapse
Post 1 explains everything.

akki7636 said:
Post 1 explains everything.
Click to expand...
Click to collapse
Did you get it to have a fully functional voLTE?

braindeductions said:
Did you get it to have a fully functional voLTE?
Click to expand...
Click to collapse
Yes..that's why i made this thread.

Link to the rom version you are on
(exact one)
Have tried open_eu versions 20a/c/d
Vdf 20d

braindeductions said:
Link to the rom version you are on
(exact one)
Have tried open_eu versions 20a/c/d
Vdf 20d
Click to expand...
Click to collapse
Im using fulmics rom.
I used this method on v20a and v20d.
You just have to enable volte in build.prop and edit cust folder's according to your carrier configuration. ( explained in first post ). This method not works on tmobile variants having international roms like fulmics. If this method fails for you it means you need extra ims libraries accoring to your carrier.

akki7636 said:
Im using fulmics rom.
I used this method on v20a and v20d.
You just have to enable volte in build.prop and edit cust folder's according to your carrier configuration. ( explained in first post ). This method not works on tmobile variants having international roms like fulmics. If this method fails for you it means you need extra ims libraries accoring to your carrier.
Click to expand...
Click to collapse
I have the same model h850 unbranded variant. I tried with fulmics and edited all those configuration files as mentioned but when I dial the number I don't hear dial tone instead I get pulse tone. the same problem you mentioned earlier in other threads.

braindeductions said:
I have the same model h850 unbranded variant. I tried with fulmics and edited all those configuration files as mentioned but when I dial the number I don't hear dial tone instead I get pulse tone. the same problem you mentioned earlier in other threads.
Click to expand...
Click to collapse
May be you need to modify some extra settings and configurations which i don't know. Im not a developer and found this method by hit and trial after spending many nights by tweaking each and every configuration related to volte.
Dont forget to add cust enabling lines (mentioned in first post ) in build.prop when you u r using fulmics rom

Related

Cricket / MetroPCS Web/MMS Flash 8/9

This is for people using Eris on Alternate Carriers i.e NOT FOR PEOPLE USING VERIZON
This Flash will Setup Web/MMS for people on Cricket or MetroPCS. If there are other carriers that use a proxy that the U2NL solution works on, i can modify this approach for them as well.
Requirements:
1. Rooted Rom that supports IPTABLES and has been flashed and booted once
2. Download the file for your carrier from below
3. Flash the file you dowloaded for your carrier from your recovery console (i.e. Amon Ra, Clockwork etc.)
4. Download and install "Autostart (root)" from blank-online.eu in the Marketplace
5. After the phone reboots choose "Always Allow" to the SU prompt
6. Reboot 2x (some froyo roms take 2 reboots)
7. Done
Download:
Flashes For Clockwork Mod Recovery 3 (Edify Scripts)
Cricket v10 (For CWR3) Credit goes to hydrosity for converting to Edify Scripting
Cricket v9 (For CWR3) Credit goes to hydrosity for converting to Edify Scripting
Click to expand...
Click to collapse
Flashes For Clockwork Mod Recovery 2.5 or AmonRA (Amend Scripts)
Cricket v10:
Cricket v9 is currently lost until i can find an archive
Click to expand...
Click to collapse
Notes:
MMS is sent anonymously via this flash, if you need your MMS to show you as the sender before the message has been downloaded you can change your APN to this:
Code:
http://mms.mycricket.com/servlets/mms?X-Cricket-MDN=[COLOR="Red"]xxxxxxxxxx[/COLOR]
Replace the x's with your telephone number.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
MetroPCS no longer requires a proxy.
Please seen Endoki's thread here
He has built a flash that should correct MMS for MetroPCS users.
Click to expand...
Click to collapse
Revol v1:
(Need verification this works for you Revol folks)
i was unable to find the MNC for Revol so MMS may fail on cyanogen based roms, and i did not include U2NL as i could not find that Revol was running through a proxy.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Known Issues:
mms seems to be hit or miss for some people, please post according to the Reporting Bugs section if MMS is not working for you.
Reporting Bugs:
Please specify your:
1. Carrier (i.e. Cricket / MetroPCS etc.)
2. Phone Type (i.e. Eris/Hero/Evo/Droid/Droid X etc.)
3. Current Rom (i.e. DamageControl/EvilEris/Smoked Glass/Toast etc.)
4. Current Flash you are using from me (i.e. Cricket v9 / MetroPCS v3 etc)
5. What is not working
Known Good Roms:
Eris:
Ivan 1.0 Alpha (HTC Eclair)
ErisLightningBolt 2.8 (Eclair)
CELB Froyo 2.8 (Froyo)
Hero:
DamageControl v1.0 / v1.1
Evo:
Jiminy ** FULLY CUSTOM Cricket ROM **
Ava-FroyoV2RC3 ROM
Droid:
Bugless Beast 0.4
Incredible:
Cricket Incredible Rom (Built by me)
Virtuous v2.7
Custom rom for MetroPCS users (Based off CM6) ** CUSTOM MetroPCS ROM **
Click to expand...
Click to collapse
What this flash does:(You don't need to do any of this, it is just outlining what the flash file does)
1. Remove any instances of:
/system/bin/u2nl
/system/xbin/sqlite3
/data/opt/autostart.sh
/data/eri.xml
2. Push and set appropriate Permissions on:
/system/bin/u2nl (the program that makes routing traffic through the proxy possible)
/system/xbin/sqlite3 (some roms include this, but the permissions may not be set correctly)
/data/eri.xml (used to change the Carrier Display name on the lock screen and notification bar)
/data/opt/autostart.sh (used set the iptables and u2nl settings at boot)
3. Drop database tables and replace them with appropriate Carrier Settings in:
/data/data/com.android.providers.telephony/databases/telephony.db (the database that the MMS program looks at for carrier settings)
4. Updates to proper MNC and Carrier name in build.prop and eri.xml
Click to expand...
Click to collapse
Let me know if anything pops up and ill do my best to fix it. Feel free to repost and modify this but please give due credit to the folks on XDA and HoFo.
All of this work derives from The community on XDA and Howard Forums. Original solution was found on Howard Forums for the Moto Droid and i modified their approach into a flash for ease of access.

I just ordered cricket, and would like to have my Eris work on it, Should I follow this?

This is for people using Eris on Alternate Carriers i.e NOT FOR PEOPLE USING VERIZON
This Flash will Setup Web/MMS for people on Cricket or MetroPCS. If there are other carriers that use a proxy that the U2NL solution works on, i can modify this approach for them as well.
Requirements:
1. Rooted Rom that supports IPTABLES and has been flashed and booted once
2. Download the file for your carrier from below
3. Flash the file you dowloaded for your carrier from your recovery console (i.e. Amon Ra, Clockwork etc.)
4. Download and install "Autostart (root)" from blank-online.eu in the Marketplace
5. After the phone reboots choose "Always Allow" to the SU prompt
6. Reboot 2x (some froyo roms take 2 reboots)
7. Done
Download:
Cricket v10:
Cricket v9:
MMS is sent anonymously via this flash, if you need your MMS to show you as the sender before the message has been downloaded you can change your APN to this:
Code:
http://mms.mycricket.com/servlets/mms?X-Cricket-MDN=[COLOR="Red"]xxxxxxxxxx[/COLOR]
Replace the x's with your telephone number.
Click to expand...
Click to collapse
MetroPCS v3:
MetroPCS v3.5 Beta
Please specify you are using this beta if reporting bugs
(im specifically looking to see if you had MMS working prior, and now it stopped working)
Click to expand...
Click to collapse
Revol v1:
(Need verification this works for you Revol folks)
i was unable to find the MNC for Revol so MMS may fail on cyanogen based roms, and i did not include U2NL as i could not find that Revol was running through a proxy.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Known Issues:
mms seems to be hit or miss for some people, please post according to the Reporting Bugs section if MMS is not working for you.
Reporting Bugs:
Please specify your:
1. Carrier (i.e. Cricket / MetroPCS etc.)
2. Phone Type (i.e. Eris/Hero/Evo/Droid/Droid X etc.)
3. Current Rom (i.e. DamageControl/EvilEris/Smoked Glass/Toast etc.)
4. Current Flash you are using from me (i.e. Cricket v9 / MetroPCS v3 etc)
5. What is not working
Known Good Roms:
Eris:
Ivan 1.0 Alpha (HTC Eclair)
ErisLightningBolt 2.8 (Eclair)
CELB Froyo 2.8 (Froyo)
Hero:
DamageControl v1.0 / v1.1
Evo:
Jiminy ** FULLY CUSTOM Cricket ROM **
Ava-FroyoV2RC3 ROM
Droid:
Bugless Beast 0.4
Incredible:
Cricket Incredible Rom (Built by me)
Virtuous v2.7
Custom rom for MetroPCS users (Based off CM6) ** CUSTOM MetroPCS ROM **
Click to expand...
Click to collapse
What this flash does:(You don't need to do any of this, it is just outlining what the flash file does)
1. Remove any instances of:
/system/bin/u2nl
/system/xbin/sqlite3
/data/opt/autostart.sh
/data/eri.xml
2. Push and set appropriate Permissions on:
/system/bin/u2nl (the program that makes routing traffic through the proxy possible)
/system/xbin/sqlite3 (some roms include this, but the permissions may not be set correctly)
/data/eri.xml (used to change the Carrier Display name on the lock screen and notification bar)
/data/opt/autostart.sh (used set the iptables and u2nl settings at boot)
3. Drop database tables and replace them with appropriate Carrier Settings in:
/data/data/com.android.providers.telephony/databases/telephony.db (the database that the MMS program looks at for carrier settings)
4. Updates to proper MNC and Carrier name in build.prop and eri.xml
Click to expand...
Click to collapse
Let me know if anything pops up and ill do my best to fix it. Feel free to repost and modify this but please give due credit to the folks on XDA and HoFo.
All of this work derives from The community on XDA and Howard Forums. Original solution was found on Howard Forums for the Moto Droid and i modified their approach into a flash for ease of access.

oh okay, So This needs to be done first and right after I can do this?

Thanks for trying to give us a solution!
I tried flashing the Metro one, and got this in RA:
E:Syntax error in update script
Installation aborted.

Will this work with revol wireless?
Sent from my FroyoEris using XDA App

jessebwallace said:
Thanks for trying to give us a solution!
I tried flashing the Metro one, and got this in RA:
E:Syntax error in update script
Installation aborted.
Click to expand...
Click to collapse
Ill get this corrected and updated, thanks for trying.
** EDIT **
both scripts initially had an error in my syntax, i have corrected and updated, should be working 100% now. Let me know if it doesnt work

frenize said:
Will this work with revol wireless?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Ill look to see if i can get one working for your carrier.
EDIT:
posted Revol Flash, did not see any indication that Revol goes through a proxy so there were no U2NL or iptables set, let me know how it works out.

Apologies in advance if this is an inane question. Will these procedures also work to get the HTC Hero onto Cricket? Or does this only work for HTC Eris?
Thank you kindly,
Mike

Realm said:
oh okay, So This needs to be done first and right after I can do this?
Click to expand...
Click to collapse
3. PST (dial ##778 on your phone, pw 000000) settings already entered correctly and showing 3G or EV icon >> see guide here: http://www.howardforums.com/showthread.php?t=1630517
Exactly

nofunsally said:
Apologies in advance if this is an inane question. Will these procedures also work to get the HTC Hero onto Cricket? Or does this only work for HTC Eris?
Thank you kindly,
Mike
Click to expand...
Click to collapse
Should work fine for the Hero/Evo/Incredible/Eris As far as i know, let me know if it doesnt work and ill see what i can do.

hello,
thanks for the update. my question it says in the first post that you must remove all the other u2nl, autostart and a few others??? how would i go about removing those in order to put this on my HTC HERO? and How would i put this onto my HTC HERO? i mean would i push it or what? and i forgot the commands if you could list it PLEASE. Thanks in advance man!

t12icky0 said:
hello,
thanks for the update. my question it says in the first post that you must remove all the other u2nl, autostart and a few others??? how would i go about removing those in order to put this on my HTC HERO? and How would i put this onto my HTC HERO? i mean would i push it or what? and i forgot the commands if you could list it PLEASE. Thanks in advance man!
Click to expand...
Click to collapse
This is a flash that you flash from your recovery console in your phone, once you flash this it takes care of the u2nl and autostart and whatnot.
The part you are reading is just me stating what the flash automates.

token419 said:
This is a flash that you flash from your recovery console in your phone, once you flash this it takes care of the u2nl and autostart and whatnot.
The part you are reading is just me stating what the flash automates.
Click to expand...
Click to collapse
ohh...ok cool..so i just need to do the update on the recovery then flash this? BTW thanks for all your help and work on this.
***edit*** from the recovery menu shouldnt i just choose flash zip from sd card? i choose that then it says this
E:failure at line 7:
Copy_dir PACKASGE:system SYSTEM:
Installation Aborted.
WHAT SHOULD I DO?

t12icky0 said:
ohh...ok cool..so i just need to do the update on the recovery then flash this? BTW thanks for all your help and work on this.
***edit*** from the recovery menu shouldnt i just choose flash zip from sd card? i choose that then it says this
E:failure at line 7:
Copy_dir PACKASGE:system SYSTEM:
Installation Aborted.
WHAT SHOULD I DO?
Click to expand...
Click to collapse
I have verified all 3 files flash on my phone, my assumption is your download may have become corrupted, please redownload and try to flash again, also which carrier are you trying to flash to?
Let me know how it works out

token419 said:
I have verified all 3 files flash on my phone, my assumption is your download may have become corrupted, please redownload and try to flash again, also which carrier are you trying to flash to?
Let me know how it works out
Click to expand...
Click to collapse
im already on cricket and have the WEB, talk, text working but dont have MMS so i figured i would give this a try. i will redownload and try it again and let you know..THANKS!
EDIT....ok redownloaded..the file says 25.4kb size and 28kb size on disk. I just tried downloading it 3 times. transferred it over to my sd card so its on there 3 times and tried to flash each file and it still gives me the error i told you earlier. im on French Toast 2.1 if that matters?
AND I FORGOT to tell ya im on the HTC HERO!

Flashing using Amon-RA's recovery? Is Recovery a screen with a bunch of words on it, and it says RA-Recovery or Amon-RA Recovery at the bottom?
It *should* flash on Hero the same as Eris.
You could manually push those files where they're supposed to go.
FIRST do a nand backup from recovery. THEN...
Unzip that .zip file, take all the files out of folders in that .zip, and put them in your android SDK tools folder. So you want the following in your tools folder:
u2nl
sqlite3
autostart.sh
(eri.xml might not be the same for your Hero, that might be for Eris, but I could be wrong - but it's just the 'name' of the carrier anyway, not necessary for functionality)
Get Autostart from the market (from wifi, or find it on the internet, and download it, and put it on your phone from your computer)
Get APN Backup & Restore
Download some working Cricket APNs (see my link above, I should have a link to a working .xml file for that, put it on your SD card in the APNBackupRestore folder, or whatever the folder is called)
Open APN Backup & Restore
Backup APNs
Delete APNs
Restore APNs (select the Cricket APNs you downloaded and put in that folder on your sd card)
Then do the following from command line in your tools folder
adb remount
adb push u2nl /system/bin/u2nl
adb push sqlite3 /system/xbin/sqlite3
adb push autostart.sh /data/opt/autostart.sh
adb push eri.xml /data/eri.xml
adb reboot
Autostart should ask for root permissions, hit always allow
and you should be 100% fully functional on cricket.
Open that Proxy shortcut you have for your web to work, and make the server and port BLANK, you DON'T NEED the wap.mycricket.com port 8080 in there any more.

pkopalek said:
Flashing using Amon-RA's recovery? Is Recovery a screen with a bunch of words on it, and it says RA-Recovery or Amon-RA Recovery at the bottom?
It *should* flash on Hero the same as Eris.
You could manually push those files where they're supposed to go.
FIRST do a nand backup from recovery. THEN...
Unzip that .zip file, take all the files out of folders in that .zip, and put them in your android SDK tools folder. So you want the following in your tools folder:
u2nl
sqlite3
autostart.sh
(eri.xml might not be the same for your Hero, that might be for Eris, but I could be wrong - but it's just the 'name' of the carrier anyway, not necessary for functionality)
Get Autostart from the market (from wifi, or find it on the internet, and download it, and put it on your phone from your computer)
Get APN Backup & Restore
Download some working Cricket APNs (see my link above, I should have a link to a working .xml file for that, put it on your SD card in the APNBackupRestore folder, or whatever the folder is called)
Open APN Backup & Restore
Backup APNs
Delete APNs
Restore APNs (select the Cricket APNs you downloaded and put in that folder on your sd card)
Then do the following from command line in your tools folder
adb remount
adb push u2nl /system/bin/u2nl
adb push sqlite3 /system/xbin/sqlite3
adb push autostart.sh /data/opt/autostart.sh
adb push eri.xml /data/eri.xml
adb reboot
Autostart should ask for root permissions, hit always allow
and you should be 100% fully functional on cricket.
Open that Proxy shortcut you have for your web to work, and make the server and port BLANK, you DON'T NEED the wap.mycricket.com port 8080 in there any more.
Click to expand...
Click to collapse
Thanks for the suggestions.
We got him sorted out in PM's last night, it wasn't flashing due some user made customizations, once those were corrected it flashed fine.
MMS still was not working for him but i have him trying from a fresh flash which i assume should work fine.

yea man and you dont know how appreciated i am..doing your new method of clean install and will let you know in about 30 minutes whats goin on.
Thanks again guys for your help!

I originally used the v2 of this script some time ago, and it worked fine until last night for me, then abruptly web no longer works for my Eris on Cricket--and I didn't change a thing.
Today I tried the v8, and there is still no difference...has there possibly been any change in the proxy IP or something? Or could I possibly have some other problem, such as a hardware issue?
Regular voice and wifi work correctly. Any ideas?
-Ryan
P.S. I'm using Sense-able 3.1.

NTCODE Error Solution

1. Go to secret menu of your phone (*#546368#*850#)
2. Tap SVC menu, then Version Info.
3. In Version info find NT Code.
4. Change wbatever code you have there to "1","FFF,FFF,FFFFFFFF,FFFFFFFF,11" - that is open europe.
After pasting the above code, the NT Code should display something like code write done, or similar, instead of your old NT Code.
This info is from MrBeem, he sent to me. I have this error but it did not work for me, i get Write Error maybe because i I dont have root. If you are rooted can work for you.

I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?

stuclark said:
I get write error too. I think you have to have root to make this work.
Talking of which, has anyone got root on 7.0 yet?
Click to expand...
Click to collapse
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).

Error
yken said:
From Mrbeem:
Hello. Got an update on the version error you have/had.
1. yes, you do have to be rooted, to get root u must het twrp-3.2.0-1-beta1-H850.img and SuperSu2.78 SR4. You flash twrp via minimal adb and fastboot, instructions on XDA forum, after flash, pull battery out, back in and you MUST get to recovery by Vol Down+POWER combination and you only get 1 try. If you don't manage to get to recovery and your system starts booting, you must flash twrp all over again. Once in TWRP, press skip if it prompts for password, enable read/write by swiping right, and install SuperSu zip file you have to have on your external sd card. With all that done, reboot and voila, you're rooted.
2. After boot, go to hidden menu, to ntcode. In the ntcode put "1","FFF,FFF,FFFFFFFF,FFFFFFFF,FF" notice, last 2 are FF, not 11. you should get NTCODE WRITE OK
3. with root acces granted go to cust folder and enable R/W option. I recommend using root explorer 4.0.4
4. Check subfolder list in cust folder. You will have folders like VDF_OP, EUR_OP or something like that. Pick any and memorize its name. this will become your soft ver. after you finish.
5. Find file named cust_path_mapping.cfg and open it with TEXT EDITOR!
6. at the end of the document, add a following line: FFFFFF,FF=/cust/name of subfolder in cust folder you memorized in step 4
7. save file, close it and reopen to check if your added line sticks. if it doesn't you haven't pressed "mount R/W" button in root explorer. Press "mount R/W" and repeat steps 5 to 7 .
8. Reboot, and now you should get your system branded (if you chose a specific carrier subfolder in /cust) or no brand and no version error (if you chose open europe in /cust).
Click to expand...
Click to collapse
Can't pass the step 2, it gives an error.

fmartins29 said:
Can't pass the step 2, it gives an error.
Click to expand...
Click to collapse
You can flash your countries Rom, not EU

I've installed TWRP ans SuperSU as shown above, but I still get Write Error.
Looking in the SuperSU app, it says under "Install SuperSU into /system" - "Not (currently) available in system-less mode".
How can I fix the SuperSU issue, as I'm guessing that's why I haven't got write access to the NTT code?

Hi. What exactly do you get in your ntcode error? Mine was FFFFFF,FF is not a proper code or something like that. Now, if your error is something else but not '0', you can just do the following:
1. Memorize or write down your error code ( in my case it was FFFFFF,FF)
2. go to /cust folder, mount it as R/W
3. Check what carrier subfolders folders you have in your cust solder (i had OPEN_EU, P4P_PL and a couple more)
4. Open file cust_path_mapping.cfg with TEXT EDITOR
5. Change the number/letter string before = of your desired carrier in the above mentioned cfg file to whatever it says in your ntcode error (my error message said FFFFFF,FF, i wanted the P4P_PL to be my carrier so i changed 26006,06=/cust/P4P_PL to FFFFFF,FF=/cust/P4P_PL).
6. Save changes, close, reopen the cfg file to check if your changes stick (if not, make sure you've enabled the R/W option in your cust folder).
7. Reboot
This should fix your problem. I tried this on 5 different devices and always worked.

Help changing NT using SVC menu
yken said:
You can flash your countries Rom, not EU
Click to expand...
Click to collapse
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.

wimmerfield said:
The NT code showing for me on my LG G5 H850 from the SVC menu is
"3","234,30F,
28000000,FFFFFFFF,FF","234,38F,
28000000,FFFFFFFF,FF","234,33F,
28000000,FFFFFFFF,FF"
(I'm on UK Virgin I believe - 234,38) and my stock Android 7.0 Rom is H85020k_00_VMC_GB_OP_0501.kdz Now,
I want to update to Oreo using the open EU oreo kdz H85030a_00_OPEN_EU_OP_0910.kdz as an upgrade file is not yet available for my phone but I get the customer not found errors on boot even if I first flash the phone using the original stock open EU Android 7.0 file H85020a_00_OPEN_EU_OP_1030.kdz.
I have my phone unlock code so if I unlock the bootloader will that allow me to enter a new NT code in the SVC menu to stop the customer error message without me having to root the phone and edit the root CUST folder? Thanks in anticipation.
Click to expand...
Click to collapse
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.

No progress with changing NT code
cancunia said:
Just wondered if you got any further with this? Oreo is now released for VM branded G5, but I'm wanting to use my VM branded phone on Three with WiFi calling. I was thinking about changing 1 of the 3 NT Codes (30,33,38) to 20 for Three but not sure if that's the best path forwards.
Click to expand...
Click to collapse
Sorry - I wasn't able to resolve that issue but as you say the G5 has now received its Oreo upgrade which is really all I wanted. Good luck anyway

Thank you! It worked for me. I have an h850ar running Android 8.0 without root. Finally the damn sign went away every time I started my phone ...

my device 860 h GCC middle East
I FLASH OREO VERSION sg (Singapore)
everything is work but ( NTCODE) PROBLEM ? ANY solution ? your discussion work for my device?
thank you
sorry bad English ?

WARNİNG
1 - WARNİNG - Current version is not available for user. Can't find matched cust for NTCODE = (23430,02)
2- WARNİNG _ Current OP name by Buyer-code is (EEO_GB). But cannot find matched NT-code mcc/mnc (23430), subset (02)
Telefon yeniden başlatıldığında bu hatalar çıkıyor bir çözüm var mı acaba LG G5 H850 model cihaz

Did anyone work out how to change the NT Code via the hidden menu? I tried downgrading to Marshmallow but still get a write error.
Thanks

This is a solution that worked for me, on a Wind branded phone with an OPEN_EU rom (root required):
go to /cust/ folder and edit cust_path_mapping.cfg, adding a new line with the code you see in the NTCODE error (22288,FF in my case), pointing it to the OPEN_COM folder:
22288,FF=/cust/OPEN_COM
Then do the same with open_path_mapping.cfg, but here you should put OPEN_EU instead of OPEN_COM:
22288,FF=OPEN_EU
Then, after saving both files, reboot the phone, and the NTCODE error will be gone.

Any way to unlock the 5GHz WiFi band for US-version?

So the US-version of the Mediapad M3 does not support 5GHz Wifi as stated by Huawei and from my personal experience. Per Huawei's website:
Wi-Fi: IEEE 802.11a/b/g/n/ac at 2.4 GHz & 5 GHz (Products delivered to markets that impose FCC certification requirements do not support 802.11 a/ac at 5 GHz Wi-Fi)
I can't help but think that the hardware is there as I have never heard of a mobile WiFi chip that ONLY supports 802.11 ac at 2.4 GHz. Therefore, is or will there be any way to unlock the 5 GHz band of the WiFi chip assuming the hardware is there?

Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.

Slavon-93 said:
Well, if you have unlocked bootloader, you may try the following:
1) Get root access.
2) Open /system/build.prop and find ro.config.hw_is_hide_wifi_5g=true and change it to "false". Or to true if it's false.
3) If that doesn't work (cause I really don't know what this option stands for), see below.
4) Go into /cust folder and tell us what's in there. Maybe, there's something like "hw" folder with "eu" folder inside.
5) If there is, edit /data/custom.bin and put "hw/eu" there (without quotemarks), and see, if something has changed.
If you don't have "hw/eu" in /cust, you have two ways:
1) Ask me here to give you "hw/eu" folder, put it into /cust and do (3).
2) Find local.prop file (it's usually in "prop" folder, three folders down from /cust, but folders are those you have, not "hw/eu")
3) There you'll find ro.config.hw_opta and ro.config.hw_optb. Change them to 999 and 156 respectively.
If all that doesn't help, we'll need to find another ways.
Click to expand...
Click to collapse
Has anyone been able to try this yet?

the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
C'mon, be the first one
Just another caution.
Please, do a backup first.
I had a factory reset after changing region in custom.bin. I don't know, what was the real cause, and now I don't do anything to my tablet, cause everything it setup and works fine.
You, probably, can avoid it in two cases:
1) Your original recovery was replaced by TWRP
2) You don't change the actual region, changing only the content of your region's folder.

the7thson said:
Has anyone been able to try this yet?
Click to expand...
Click to collapse
Changing ro.config.hw_is_hide_wifi_5g=true to "false" didn't do anything for me.
/cust folder contains /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust. I haven't messed with any of them.

didn't work.
After unlocking the bootloader and getting root access I did the following:
1. Changed /system/build.prop: ro.config.hw_is_hide_wifi_5g=true to "false".
restarted the tablet but it did nothing
2. went to /cust. it contains the following folders: /hw (subfolders /default, /normal, /oversea, and /usa), /lost+found, /preinstalled, and /special_cust (just like for @neo_1221)
edited local.prop under /Cust/hw/usa/prop/ to ro.config.hw_opta=999 (was 567) and ro.config.hw_optb=156 (was 840).
restarted the tablet but it did nothing
What else can be done?

E.Vogel said:
What else can be done?
Click to expand...
Click to collapse
You may try to flash Chinese firmware. It's Something like BTV-W09C233B0xx or BTV-DL09C233B0xx
I don't have any other ideas, really. If even this doesn't help, then 5GHz is locked by OEMInfo or disabled in hardware.
Firmware can be found with this tool

Am confused by this thread. Are you saying you can only connect to 2.4 networks and cannot see 5ghz networks at all?? That normal only happens when a tablet physically does have a 5ghz radio.

The U.S version of the tablet does not support 5Ghz wi-fi.
We are assuming that there is only one variant of the tablet sold world wide (two actually LTE+wifi and wifi only),
and in order to comply with FCC requirements the 5Ghz wi-fi band was disabled by software and not hardware.
If that is the case than the band can be enabled back by flashing different non-U.S rom.
hopefully

It is WORKING!
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back

E.Vogel said:
I downloaded the latest Chinese version using the tool @Slavon-93 linked, version BTV-W09C233B022 from December 16 2016. I flashed it and after restarting the tablet, I have a Chinese version tablet, with 5Ghz band wi-fi working.
I lost custom recovery and root and may reflash them later.
I got some apps back that I previously removed, but happily all my other apps were still installed and configured.
Thanks @Slavon-93
p.s. I re-flashed TWRP and SU and now have custom recovery and root back
Click to expand...
Click to collapse
Can you select english as the language?

Yes you can, and since English was my selected language before I flashed the Chinese ROM it stayed as the selected language, so I never got a Chinese welcome screen and had to find out how to change it to English.

So this is a solution to get the "5Ghz band" working on a US WiFi only?

Those, who have a US tablet, could you please upload your entire /cust folder somewhere? If Chinese firmware is a solution, maybe there is something in /cust, that blocks 5GHz wifi? I wanna compare it to Chinese and Russian versions and maybe find something interesting.

@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.

jmjm003 said:
@E.Vogel forgive me for being new to Huawei way of doing things. You said you flashed the Chinese ROM. Flashing makes me think of my Nexus 7 where I actually flashed the *.IMG files.
I downloaded the file you mentioned and I have update.app after extraction. I recall reading somewhere about creating a folder and transferring said file to device and restarting it. I'm curious if this is the route you took? I personally prefer fastboot flash but will have to do with what works. Thank you.
Click to expand...
Click to collapse
Forgive me for not being @E.Vogel, but let me explain. Huawei devices are not usual in terms of partition structure. For example, they have 2 recoveries, designed for different things. For a Nexus owner their update structure is also strange. Once upon a time, you could create a "dload" folder in /sdcard or in external SD, choose local update in update utility on your device, select update.app or update.zip, reboot and watch the device updating. Now we don't have an option to choose a local update, so the quickest way to install FULL OTA is from TWRP. You just need to put update.zip (~1.8 Gb) somewhere in /sdcard or other place, reboot into TWRP, press the Install button and select this file. TWRP installs it and you get your Chinese firmware. I recommend to make a backup first, in case something goes wrong. After installing FULL OTA you still get your apps and settings in place, but after a factory reset, you will lose Google Play and other a Google apps, and will have to manually install them from HiApp. Also, you will have to reinstall TWRP, root, xposed and other things you probably have flashed before.

I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.

jmjm003 said:
I appreciate the reply all the same @Slavon-93. So creating the dload folder and dropping update.app in it no longer works?
I've not modified anything on my device other than fixing DPI so apps are in tablet mode.
Any idea what each recovery does since it has two of them?
I like to know there's a way out of a screwup if it happens. Nexus 7 was simple to fix.
Thank you.
Click to expand...
Click to collapse
Huawei devices have two recovery partitions: recovery and recovery2.
Recovery has generally all the same features a typical Nexus recovery has, except it doesn't have an option to apply update.zip and has a touch interface unlike the Nexus recovery.
Recovery2, called eRecovery, also has a touch interface and is designed to make a totally screwed up device great work again. It has a button to download full firmware and install it but on my device it said "No firmware found" after connecting to Huawei servers. People in Russian forum say it works only if you're in China and have a Chinese device. Anyway, if eRecovery does nothing, I considered it totally useless and replaced with TWRP: fastboot flash recovery2 twrp.img
Generally Huawei devices can be restored the same way a Nexus device can. TWRP and fastboot work the same. Personally I prefer to make a total backup of all partitions in device with "dd". I think it will give me more flexibility in restoring if something goes completely wrong. On DL09 model, only modem partitions are the problem. You can find fastboot versions of Chinese ROMS easily, but after installing them, I've lost everything related to phone functions. The only way to fix it was installing Full Chinese firmware in form of update.zip with TWRP.
And about dload folder. I have no idea how it works. I am also a former owner of Nexus 7 and the logic of Huawei is new to me, so I don't know some nuances. On earlier devices there was another option to update: you put update.app to dload folder, dial *#*#2846579#*#*, select Software upgrade -> SDCard Upgrade, the device reboots and installs the update. Again, on my device this trick didn't work and update installation stopped at 5%, saying it's incompatible with my device.

@jmjm003, I also come from a nexus 7 and Huawei devices are different.
First of all there is no formal web site with all factory images and/or OTA to download, I had to use a tool an XDA user developed to find the factory image I needed.
The second change is that the factory image (file update.zip) does not contain *.img files inside like in Google images and contains "update.app" 1.8GB file and some other small files.
To flash the ROM I tried to use ADB sideload but got an error message about the file being unreadable, so I copied the file to the tablet and flashed it using TWRP install function like any other zip file.
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.

E.Vogel said:
@Slavon-93, my /cust/hw folder changed from before and now contains only two sub-folders "cn" and "default"
I uploaded the entire /cust folder to Google drive, use this link to download it.
Click to expand...
Click to collapse
Thank you but I know what's inside Chinese /cust folder as I am using Chinese firmware myself. I am interested in untouched /cust of US version of tablet because I think there can be some option in local.prop or somewhere else, that blocks 5GHz Wi-Fi. I can try to look for it by comparing Russian, Chinese and US cust folders.

[GUIDE] Enable VoLTE for your non operator handset

I have finally been able to get VoLTE working on my X Performance despite my carrier never having 'supported' my handset (they never sold it here).
What you will need?
Windows Computer with Flashtool and minimal ADB and fastboot (if you have already downloaded fimrware as below you can use flashtool on whatever platform your prefer)
Bootloader Unlocked
TWRP
ROOT (Magisk Preferred)
VoLTE enabled firmware (not sure about this one I think you can edit build.prop appropriately)
To unlock Bootloader, TWRP, and ROOT follow this guide
I will first describe how I did it and then how anyone else should be able to achieve the same outcome. Now includes a less convoluted way to do this allowing you to keep all data thanks to those who tested
1) First using a root file browser - I recommend this one browse to /system/etc/customisations/modem/
2) Check to see if there is any reference to your operator's modem in your model firmware. They are all in the format of amss_fsg_dora_xxx_tar.mbn
3) Once you have a spotted your operator you need to take note of what's in between 'dora_' and '_tar' so for example if I use china mobile - I would find amss_fsg_dora_china_mobile_hk_ims_tar.mbn I would need to take note of china_mobile_hk_ims
4) Once you have this you need to connect your phone via ADB to your PC (I found this much easier on a computer).
5) Enter the following commands adb root then adb shell
6) mount -o rw,remount /oem
7) vi /oem/modem-config/modem.conf
8) press 'i' on your keyboard to enter edit mode and delete whatever is in the file and replace it with your operator modem from step 3 - (china_mobile_hk_ims in this example) then press 'ESC' and then ':wq'
9) make a backup of your important data
10) Turn off your phone, connect it into Flashmode to your PC (hold vol- while plugging in to the PC)
11) Flash your firmware with these options - do a wipe of all partitions. Tick the OEM box in the 'Exclude SIN' section. Alternatively follow this and avoid factory reset as per @pbarrette and @SGH-i200
12) Once you have completed reboot your phone and you should pickup VoLTE settings at setup.
IF you don't have root follow the guide earlier on how to backup TA, unlock bootoader
Flash a VoLTE enabled firmware. Install TWRP. Enter recovery (hold Vol- and power to start phone) install your preferred root option. Then connect your phone via ADB (step 5) to find your operator modem per step 3. Continue with Step 6&7. Start your phone.
I have tested this using existenZ 5.5. Theoretically should work for any Xperia phones with an OEM partition, however each phone might have a different modem name for the same operator ( I know this to be the case between the XZP and the XXP), however if you get the bit in between 'modelname_' and '_tar' and follow the same process for editing the modem.conf file you should get the same results.
Credit to
@sdugoten for Unlock, TWRP and ROOT guide
@akshay2shah for informing me of the modem selector tool for other Xperias
@VeixES for informing me of the oem.sin partition and modem.conf files
@niaboc79 for existenZ ROM (highly recommended)
@SGH-i200 and @pbarrette for testing and coming up with an easier way to use this (step 11)

Wipe all partition. It's too difficult.

Is it possible to enable VoWiFi for this device.? My phone carrier supports both VoWiFi and VoLTE on newer Sony Model. But only supports VoLTE on X Performance......

would not be a more detailed guide?
do not know how to copy ...
I did not find my operator ,,amss_fsg_dora_xxx_tar.mbn"
there is a link "default"

kodein said:
would not be a more detailed guide?
do not know how to copy ...
I did not find my operator ,,amss_fsg_dora_xxx_tar.mbn"
there is a link "default"
Click to expand...
Click to collapse
Is your operator an MVNO? You could try and see if using the underlying carrier modem is present? Otherwise see if another operator in your country's modem settings work ( unlikely but your only other option is to try till you have a modem setting that works). You could try looking at the apns-conf.xml file and see if there is an operator with similar settings if you know them.

bluesky1126 said:
Is it possible to enable VoWiFi for this device.? My phone carrier supports both VoWiFi and VoLTE on newer Sony Model. But only supports VoLTE on X Performance......
Click to expand...
Click to collapse
I have the same problem. Unfortunately I don't think there is any way unless you know the VoWiFi settings. I'll look into it. For me at least I'm no longer having dropped calls or missing out on important calls

chris_j26 said:
I have the same problem. Unfortunately I don't think there is any way unless you know the VoWiFi settings. I'll look into it. For me at least I'm no longer having dropped calls or missing out on important calls
Click to expand...
Click to collapse
I see......
Well, still congrats to you~

Please flashable zip sir

chris_j26 said:
1) First using a root file browser - I recommend this one browse to /system/etc/customisations/modem/
2) Check to see if there is any reference to your operator's modem in your model firmware. They are all in the format of amss_fsg_poplar_xxx_tar.mbn
Click to expand...
Click to collapse
If the mbn file is not there, can I copy it to this folder? What has to be changed after copying the file threre?

SGH-i200 said:
If the mbn file is not there, can I copy it to this folder? What has to be changed after copying the file threre?
Click to expand...
Click to collapse
If you got an mbn file it might work. However I suspect that it contains modem specific files if you copied it across from one device family (Xperia X , Xperia xz for example) it theoretically could work. I would imagine you would need to set permissions on the mbn file once copied I would think 1744 would do it but I'm not an expert on Android filesystem permissions. You could always do ls -la in terminal on the folder and replicate those permissions.

chris_j26 said:
10) Turn off your phone, connect it into Flashmode to your PC (hold vol- while plugging in to the PC)
11) Flash your firmware with these options - do a wipe of all partitions. Tick the OEM box in the 'Exclude SIN' section.
12) Once you have completed reboot your phone and you should pickup VoLTE settings at setup.
Click to expand...
Click to collapse
A Factory Reset is not needed to switch the active MBN! Please update point 11 to 'Flash cust-reset.ta' (and keep all your data and settings!):
pbarrette said:
I usually just flash the cust-reset.ta file. That clears the unit in the TA partition which holds the current carrier customization information.
Click to expand...
Click to collapse

(How I got) XZ premium Fingerprint Volte & WiFi calling WITHOUT bootloader unlock

*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file

Robin Banks said:
*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file
Click to expand...
Click to collapse
Do we lose drm key? Can I access the / system or use root explorer?

tronganhha29 said:
Do we lose drm key? Can I access the / system or use root explorer?
Click to expand...
Click to collapse
You won't lose any drm keys if you don't unlock the bootloader. I posted screen shots above that show all security keys intact, with locked bootloader. And if you look at the top, the wifi calling icon is there! The "rooting" part I used was only temporary & I only tried 2 modify files in the /OEM folder because that's all I needed for Volte & WiFi calling on tmobile. I had 2 downgrade firmware & run a temp root exploit from j4nn.
His exploit is explained here https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 BUT, instead of unlocking the bootloader I just copied US Xz1c /OEM files into my /OEM folder then set file permissions. That would be awesome if someone could make a script 2 automate this process for everyone!
Remember after your done, your gonna want 2 update to a newer more secure firmware. I didn't have luck with Pie, but it's got some minor bugs anyways (I am running Oreo 47.1.A.16.20 now & I love it). The trick is you MUST DELETE the OEM.sin folder from the new firmware folder before you flash it. Otherwise it will write over your progress.

Robin Banks said:
You won't lose any drm keys if you don't unlock the bootloader. I posted screen shots above that show all security keys intact, with locked bootloader. And if you look at the top, the wifi calling icon is there! The "rooting" part I used was only temporary & I only tried 2 modify files in the /OEM folder because that's all I needed for Volte & WiFi calling on tmobile. I had 2 downgrade firmware & run a temp root exploit from j4nn.
His exploit is explained here https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 BUT, instead of unlocking the bootloader I just copied US Xz1c /OEM files into my /OEM folder then set file permissions. That would be awesome if someone could make a script 2 automate this process for everyone!
Remember after your done, your gonna want 2 update to a newer more secure firmware. I didn't have luck with Pie, but it's got some minor bugs anyways (I am running Oreo 47.1.A.16.20 now & I love it). The trick is you MUST DELETE the OEM.sin folder from the new firmware folder before you flash it. Otherwise it will write over your progress.
Click to expand...
Click to collapse
Can you help me on activating VoLTE? I read in the above tutorial just talking about backup and restore TA partition. Sorry for my English not good. Thank you!

tronganhha29 said:
Can you help me on activating VoLTE? I read in the above tutorial just talking about backup and restore TA partition. Sorry for my English not good. Thank you!
Click to expand...
Click to collapse
Are you in the US, & want Volte on Tmobile?

Robin Banks said:
Are you in the US, & want Volte on Tmobile?
Click to expand...
Click to collapse
No, I'm in Vietnam, i'm using G8141 with custom CH firmware

tronganhha29 said:
No, I'm in Vietnam, i'm using G8141 with custom CH firmware
Click to expand...
Click to collapse
I am sorry, I am not familiar with any phone providers in Vietnam. I don't think there is an easy fix because I haven't seen Vietnamese Volte modem files in any XZp firmware. I could be wrong tho, so maybe someone will correct me & also help you out.
The only reason this works for tmobile is because Sony included built in support files for some providers, like tmobile in the US. But, it's only their XZ1c phone that will actually load the correct modem file & trigger Volte & WiFi calling features out of the box. Only a couple files need to be changed on the XZp.
Problem was, it always required a bootloader unlock to change those files.
This is not a problem anymore... Because it can now be done with temproot thanks to j4nn!

Robin Banks said:
I am sorry, I am not familiar with any phone providers in Vietnam. I don't think there is an easy fix because I haven't seen Vietnamese Volte modem files in any XZp firmware. I could be wrong tho, so maybe someone will correct me & also help you out.
The only reason this works for tmobile is because Sony included built in support files for some providers, like tmobile in the US. But, it's only their XZ1c phone that will actually load the correct modem file & trigger Volte & WiFi calling features out of the box. Only a couple files need to be changed on the XZp.
Problem was, it always required a bootloader unlock to change those files.
This is not a problem anymore... Because it can now be done with temproot thanks to j4nn!
Click to expand...
Click to collapse
I worry about losing drm key. I was on the xzc and I had a camera error.
Thank you !

tronganhha29 said:
I worry about losing drm key. I was on the xzc and I had a camera error.
Thank you !
Click to expand...
Click to collapse
The only way you can lose your DRM keys... Is unlocking your bootloader. I did not want to do that. But, I wanted Volte & WiFi calling. This thread is about how I got those features WITHOUT unlocking my bootloader. And yes, of course I still have my DRM keys.
You said, that you had a camera error on an XZ1c? Assuming, you unlocked the bootloader. Did you get Volte working in Vietnam after you unlocked it? If not, then none of this will help you with your XZp. because they are very similar & they use the same provider modem files.
From what I understand, the Pie update fixes the green picture camera error. Have you tried updating your XZ1c to Pie? That should atleast make your camera work again.

Good idea, i'm using others country rom because my country update speed suck ... (Due to the carrier) , so i lose feature like WIFI calling and VoLTE. Gonna try this.

vyis said:
Good idea, i'm using others country rom because my country update speed suck ... (Due to the carrier) , so i lose feature like WIFI calling and VoLTE. Gonna try this.
Click to expand...
Click to collapse
This is what people in the US with the XZ1c have been doing because they want to enable their Fingerprint sensor AND have the US Volte settings.
So if your provider already supports Volte.. Flash that firmware first so your volte works. Then before you flash the country you want to use. Just delete the new OEM.sin file out of the folder. That will make a perfect mix of the two.
It will only keep your volte provider settings from old firmware. You don't even need temp root.
But I doubt Volte setting would survive an OTA update. It also will work with two different build versions. I don't know if this is possible with oreo/pie mix tho.

Robin Banks said:
*This would not be possible without j4nn & his amazing temp root https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510 please thank & donate 2 him!*
This is not really a "how 2 guide" because I am not good at explaining things like this. But I will try & explain how I did it. Because I have seen a lot of other people also searching for working Volte without unlocking their bootloader.
First I used j4nn's temp root guide & flashed old firmware & ran his magic program. Then I backed up my DRM keys (incase I want to unlock my bootloader someday). Then I stopped. And instead of unlocking my bootloader & while still in temp root.. I thought, maybe I can write to the OEM folder? So I typed
'mount -o rw,remount /oem' and that worked!
So.. I used another command window without closing the first one and pushed a new OEM folder to /data/local/temp
(I got the new OEM folder from US XZ1c firmware. you can also get that folder by searching for TMo-VoLTE-fix-v3.zip & unziping it)
Then, I went back to the original temp root command window & used the 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder. I re-set the owner & file permissions rebooted.
After testing it, I was able 2 flash the latest (non US for working fp) Oreo by flashing like normal with Newflasher except I deleted the OEM.sin file, so it wouldn't write over my new one! Finally I disabled auto update.
Now my XZp is still bootloader locked, running 47.1.A.16.20 with Fingerprint, Volte & wifi calling all working on tmobile in the US.
I can actually receive calls at home now!! Before this, most of my calls went 2 vm, after a long pause.
I did also try it with pie & it didn't work for me. But, ymmv. I am sure it's possible tho. I was not impressed with pie anyways & I really hate that new volume popup window that covered my home & back keys in landscape mode.
One other note is because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims". I am not sure this is actually necessary tho because I have since looked in other ds Volte firmwares like Taiwan. And they don't use "dsds" in their modem.conf file
Click to expand...
Click to collapse
You are awesome! Can you please write specific commands you used to
1) push a new OEM folder to /data/local/temp
2) 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder.
3) I re-set the owner & file permissions rebooted.
Thanks!

VBBoston said:
You are awesome! Can you please write specific commands you used to
1) push a new OEM folder to /data/local/temp
2) 'cp' command to copy that new OEM file from data/local/temp over to my /OEM folder.
3) I re-set the owner & file permissions rebooted.
Thanks!
Click to expand...
Click to collapse
I will try. But, like I said. I am not that great at step by step instructions. It would be awesome if someone made a better guide or a script 2 run after temp root.
So, AFTER you already have temp root. Open another command window (keep your temp root window open!) assuming you have the new OEM folder in your command line root dir.
Adb push OEM /data/local/tmp
Then using the temp root window from earlier exploit.
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp - R * /oem
chmod 755 /oem/modem-config
chmod 755 /oem/modem-config/408
chmod 644 /oem/modem-config/408/modem.conf
chmod 755 /oem/overlay-408
chmod 644 /oem/overlay-408/android-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.carrierconfig-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.phone-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.settings-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.systemui-res-310-408.apk
chmod 755 /oem/system-properties/408
chmod 644 /oem/system-properties/408/config.prop
Done. Reboot. You might half to take out your Sim card & reinsert it. Or factory reset. To get volte setting to take. You will know because it will say something like restarting to update carrier configuration.
Then of course you can update, but be shure to delete the OEM.sin file before flashing newer firmware! I tried this with pie once & it did not work for me. But ymmv. Right now I like oreo better anyways
I have included the zip file I found here on XDA & used it. It's meant for bootloader unlocked so just Unzip it & only use the OEM file.
Please let me know how it goes or if I forgot something!

Robin Banks said:
I will try. But, like I said. I am not that great at step by step instructions. It would be awesome if someone made a better guide or a script 2 run after temp root.
So, AFTER you already have temp root. Open another command window (keep your temp root window open!) assuming you have the new OEM folder in your command line root dir.
Adb push OEM /data/local/tmp
Then using the temp root window from earlier exploit.
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp - R * /oem
chmod 755 /oem/modem-config
chmod 755 /oem/modem-config/408
chmod 644 /oem/modem-config/408/modem.conf
chmod 755 /oem/overlay-408
chmod 644 /oem/overlay-408/android-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.carrierconfig-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.phone-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.settings-res-310-408.apk
chmod 644 /oem/overlay-408/com.android.systemui-res-310-408.apk
chmod 755 /oem/system-properties/408
chmod 644 /oem/system-properties/408/config.prop
Done. Reboot. You might half to take out your Sim card & reinsert it. Or factory reset. To get volte setting to take. You will know because it will say something like restarting to update carrier configuration.
Then of course you can update, but be shure to delete the OEM.sin file before flashing newer firmware! I tried this with pie once & it did not work for me. But ymmv. Right now I like oreo better anyways
I have included the zip file I found here on XDA & used it. It's meant for bootloader unlocked so just Unzip it & only use the OEM file.
Please let me know how it goes or if I forgot something!
Click to expand...
Click to collapse
Thank you!!! just needed to edit command cp - R * /oem to cp -R * /oem

Robin Banks said:
[...] because I have the dual sim XZp I changed my modem name in the modem.conf file from "tmobile_us_ims" to "dsds_tmobile_us_ims".
Click to expand...
Click to collapse
Since my G8342 does not load the correct 'Current Modem Configuration' (see screenshot from G8341) I can force this by editing the 'modem.conf', right?

SGH-i200 said:
Since my G8342 does not load the correct 'Current Modem Configuration' (see screenshot from G8341) I can force this by editing the 'modem.conf', right?
Click to expand...
Click to collapse
I am just gonna guess that your running a single Sim firmware & you want 2 load a dual sim modem? I am pretty shure that won't work. You can use a single Sim firmware & modem file on a dual sim phone. But the other sim slot won't function. But it looks like you already know that. I am using a dual sim firmware (and phone g8142). But there is no official Volte tmobile firmware for the XZp. Even tho the correct tmobile modem is baked into all the XZp firmwares. It needs the OEM.sin to provision volte & WiFi. It sets "IMS" true or something like that. So I used an oem.sin config file from a single Sim Xz1c. But the rest of my firmware is still XZp dual sim. I originally changed the part where it loads the correct modem & added "dsds" to the beginning because that's what the tmobile modem in my firmware is named. That worked. But it turns out, I didnt even half 2 do that. It still loads my "dsds_tmobile_us_ims" modem. Even tho I just have "tmobile_us_ims" in my modem.conf file. If you were gonna try and load a diffent modem it would be under /oem/modem-config/310/modem.conf because 310 is the customization that your running (in your thumbnail). So, yes you can force it 2 load whatever modem you want.. But only try the modems that are included with your current firmware. I wouldnt copy an actual dual sim modem into your single sim firmware. It *might* work. More then likely would brick it. Lemme know if you have any other questions & I will help ya if I can

Robin Banks said:
I am using a dual sim firmware (and phone g8142). But there is no official Volte tmobile firmware for the XZp. Even tho the correct tmobile modem is baked into all the XZp firmwares. It needs the OEM.sin to provision volte & WiFi. It sets "IMS" true or something like that. So I used an oem.sin config file from a single Sim Xz1c. But the rest of my firmware is still XZp dual sim.
Click to expand...
Click to collapse
This is the way I did it, too!
Robin Banks said:
[...]still loads my "dsds_tmobile_us_ims" modem. Even tho I just have "tmobile_us_ims" in my modem.conf file.
Click to expand...
Click to collapse
Flashing the OEM.sin is not enough in my case (G8342) because the modem file is missing!?
Robin Banks said:
But only try the modems that are included with your current firmware.
Click to expand...
Click to collapse
Is it possible to "look" into a SIN file without flashing it, to see which modem files are included, without flashing the firmware?

SGH-i200 said:
This is the way I did it, too!
Flashing the OEM.sin is not enough in my case (G8342) because the modem file is missing!?
Is it possible to "look" into a SIN file without flashing it, to see which modem files are included, without flashing the firmware?
Click to expand...
Click to collapse
The actual modem files are in modem.sin and you could unpack them and take a look. But, if your using a single sim xz1 OEM.sin that supports your carriers volte settings.. I think you should be able 2 just flash the whole firmware. I have flashed a single Sim firmware on my XZp and back to dual sim. You will loose your second sim functionality. But you can always flash a dual sim firmware back & it will be good has new. Do you really use 2 sim cards? Check out the 7th post in this thread (user rafi.mv6) about Xz1 single Sim flashing. https://forum.xda-developers.com/xz-premium/how-to/xzp-volte-firmware-t3631276

I used j4nn bindershell version of the temp root and Your guide to activate VoLTE and VoWiFi for Vodafone CZ not for the temp root supported Oreo, but for the actually last available Pie firmware 47.2.A.10.107 Customized CE1 (1308-5321) for XZ Premium single SIM G8141
I am about to write down the detailed guide soon. It is based on info from j4nn post #9 in his bindershell version temp root thread.

XZ Premium Vodafone CZ Volte & WiFi calling in Pie WITHOUT bootloader unlock
THE STORY BEHIND
As I have very poor telephone signal inside the building of our veteran garage due to combination of a garage-to-BTS distance and very thick walls of an old building and many calls to me ended up with "The number cannot be reached, try again later" and me receiving the SMS with info about missed call, I wanted to use last issued Android for my Xperia XZ Premium single SIM G8141 and to have available VoLTE and VoWiFi for my provider Vodafone CZ. Then I started to investigate, which version of the phone and which customization I have exactly. I found, that despite being located in Central Europe, my phone customization was to my surpise of South Africa (1308-5324 Customized ZA 47.2.A.10.107). To achieve activation of the VoLTE and VoWiFi I thought, it could be enough to flash the Central Europe customization (1308-5321 Customized CE1 47.2.A.10.107), as special Vodafone CZ customization was not showed by XperiCheck, and it will all work seamlessly then. I could not be wrong more. After quite weak search for the info, I downloaded and flashed that Pie CE1 customization, with skipping userdata, all TA files and persist.sin to keep all data and settings not erased, there was no VoLTE nor VoWiFi available anyway. Then I started to investigate the possibilities more intensively. What I found, there was no direct option to have VoLTE and VoWiFi activated somehow on Pie, as the temp root and modification guides was available just for Oreo. But there were some hints within those threads, that pointed me to the possibility to achieve to have that function on Pie as well. Despite there were infos, that the intended sequences did not worked for some members trying it for Pie, it was not detailed enough to be clear, how they proceed. So I started to think about that all the time and based on number of Xperia XZ1c/XZ1/XZp threads, I considered many ways how to achieve my goal. Finally, the resulted steps were none of my ideas, I just collected all the wisdome from those threads and I just put them into the right sequence, that worked for me. If being on temp root supported Oreo firmware when started, it could be a path without loosing any user data, but as I was on last Pie, I had to backup every possible data and settings and to proceed the downgrade from Pie to Oreo with factory reset. There is no known way to me to downgrade with user data being kept, as despite I was warned, I tried it and I got the "promised" bootloop of course.
THE BASIC INFO
- SONY Xperia XZ1 (G8341), SONY Xperia XZ1 Compact (G8441) and SONY Xperia XZ Premium (G8141) are very similar phones with almost identical hardware. Therefore their firmwares do not differ much, at least in the text config files content manner. Hinted by XDA users, there can be the config files adapted from one of those devices to another easily. Many of them tested that for the Oreo and it worked fine for them.
- There exists Vodafone CZ customized Pie firmware for both XZ Premium friendly phones and they differ to their CE1 customized Pie firmware version just in the config settings part of oem.sin file and all modem definitions present inside in the system.sin are the same, so to change active modem, there is just config files modification needed that can be achieved through the temp root
- Using UnSin and ext4 image mounting SW investigate the files content, location and presence and try to figure out, which files could work for Your phone
- when flashing firmware, all excluded *.sin files/partitions will be not overwritten by new data and kept in the phone in current status and content. This is used in described steps to transfer changes from firmware supported by temp root to target firmware.
THE DESCRIPTION
The VoLTE and VoWiFi config files are in the /oem folder's subfolders. The content of the /oem folder can be kept when upgrading from lower to higher version of the Android by excluding the oem*.sin file when flashing. I disliked the idea to have oem settings from Oreo in the Pie and I tried to modify Pie's /oem folder within the Oreo firmware. Based on the info from this forum and by comparing all the firmwares content, I prepared (copied from CZ customized Pie firmware version of friendly phone G8341 XZ1) few files, that I identified to be important to change the modem file choosing by the system in XZ Premium Pie. So I prepared my own custom Oreo temp root supported CE1 customized firmware, excluded the XZp Oreo oem.sin and included the XZp Pie oem*.sin. I prepared the files to be changed in XZp Pie's /oem folder and the XZp Pie firmware with oem.sin excluded as well. I flashed first the hybrid XZp Oreo-with-Pie-oem-folder firmware to my phone successfully, started the XZp with Android Oreo. I cancelled all automatic updates, activated developer menu item and set the USB debugging ON. With using ADB I ran temp root, injected modified files into the /oem folder and set their rights. Rebooted and with temp root again I checked the injected files presence in /oem folder. Then I flashed CE1 customized XZp Pie firmware with its oem.sin excluded and rebooted XZp to Pie. I cancelled all automatic updates again and checked the modem and VoLTE settings. There was VoLTE option switch inside the service menus in blue color and actitaved with the VoWiFi option greyed out but set to ON. There the Enable VoLTE menu item appeared in the Network settings and it could be switched ON. In the Call settings, the Wi-Fi calling menu item appeared there in Advanced settings and could be activated. The service itself appeared and started to function after activating the service inside the provider Self service web portal.
THE PRINCIPLE
- I wanted VoLTE and VoWiFi for Vodafone CZ on SONY Xperia XZ Premium single SIM G8141
- To let it work, I had to modify Pie's /oem folder
- it is posible to modify it only when rooted or temp rooted
- I do not want to root it
- the only temp root is for Oreo
- I prepared and flashed hybrid firmware, Pie /oem with the Oreo main system - this trick was my only invention to this and it fortunately worked !
- I modified Pie /oem folder inside Oreo firmware temp root to support Pie's VoLTE and VoWiFi for Vodafone CZ
- I flashed latest Pie excluding the oem.sin to keep modified /oem settings then
- I switched the device settings ON and I activated the provider support for Vodafone CZ VoLTE and VoWiFi in Self Service portal
- Now I can enjoy Vodafone CZ VoLTE and VoWiFi on SONY Xperia XZ Premium single SIM G8141
WHAT TO DOWNLOAD
- To investigate Your phone version settings (not needed to follow my steps)
Download UnSin (UnSIN 1.13 (Win x64).zip)
Download SW for mounting and explore ext4 partition (ext2explore-2.2.71.rar)
Download the firmware for the other phones to look for setting files. In my case, it was G8341 Vodafone CZ customized Pie firmware (XZ1 G8341_Vodafone CZ_47.2.A.11.228-R2C)
- To activate VoLTE and VoWiFi for Vodafone CZ on SOMY Xperia XZ Premium single SIM G8141 (enough to follow my steps)
Download ADB (platform-tools_r33.0.2-windows.zip)
Download newflasher (newflasher_v52.zip)
Download the j4nn temp root alternative solution for G8141 (bindershell)
Download the G8141 j4nn temp root supported Oreo firmware in the same customization, as the later Pie to minimize issues (XZ Premium G8141_47.1.A.16.20 Customization CE1)
Download the G8141 CE1 customized Pie firmware (1308-5321 Customized CE1 47.2.A.10.107)
Download the G8141 Vodafone CZ customized Pie /oem fodler files (attached here as G8141_Vodafone_CZ_Modded_Pie_OEM_folder.ZIP)
THE PREPARATION
- if You want to proceed for phone different to G8141 and Vodafone CZ, check with xpericheck all three phone versions firmwares, whether there is any that contains customized version for Your provider, if there is one for Your phone, just flash that customization and You go
- if there is customized version of the firmware for Your provider for any of the other two phones, investigate the content of those firmwares oem*.sin and system*.sin files and try to match the proper files to copy/modify for Your phone (use UnSin and ext4 explorer for this task), the content of modem.conf file in oem.sin file, modem-config folder holds the short name of the modem *.mbn file in system.sin file, etc/customization/modem folder. For example, if modem.conf file contains "vodafone_czech_volte_vowifi" text, it defines using the "amss_fsg_maple_vodafone_czech_volte_vowifi_tar.mbn" modem files, that allows function of VoLTE and VoWiFi for Vodafone CZ. If Your firmware in system.sin contains modem file with the same name, You can modify /oem part of the firmware to select this modem and activate VoLTE and VoWiFi for Your phone/provider combination as well. I was inspired by Robin Banks files copied and I identified and copied several relevant files from G8341 Vodafone CZ firmware's /overlay folder as well. Try to add similar files for Your phone version as well.
- Prepare the XZ Premium single SIM G8141 temp root supported Oreo firmware into folder "01 not full Oreo downgrade with Pie OEM"
- exclude the Oreo oem.sin to allow using Pie oem.sin
- exclude the following Oreo firmware files as well: see content of the folder "01b not used Oreo files" (for the list see attachement file G8141_Vodafone_CZ_mod_FoldersContent.TXT)
- do not exclude userdata.sin when downgrading or else You get the bootloop (tested by myself )
- copy inside the folder the Pie's oem*.sin (oem_X-FLASH-CUST-42E5.sin)
- copy inside the folder the newflasher.exe file (to ease the process)
- extract ADB files into its folder, c:\platform-tools\ in my case
- copy content of the "02 adb push files" folder into c:\platform-tools\, extract it from the attached G8141_Vodafone_CZ_Modded_Pie_OEM_folder.ZIP
- copy bindershell file from j4nn for Oreo temp root into c:\platform-tools\
- Prepare the XZ Premium single SIM G8141 last Pie firmware into folder "03 Pie flash without OEM"
- exclude the Pie oem.sin
- exclude the following Pie firmware files as well: see content of the folder "03b_not_used_Pie_files" (for the list see attachement file G8141_Vodafone_CZ_mod_FoldersContent.TXT)
- copy inside the folder the newflasher.exe file too
- check both firmware folders to have their boot_delivery.xml file in boot folder and partition_delivery.xml file in partition folder for the flash to end correctly
- check the G8141_Vodafone_CZ_mod_FoldersContent.TXT and compare the folders' content to match
THE STEPS (Windows PC)
#01 - have Your phone charged, all data and settings backed up (including trim areas) and all phone drivers installed, this is a good way to start
#02 - go to "01 not full Oreo downgrade with Pie OEM" folder and run newflasher.exe inside, it will open a command line window, stay in this window
#03 - switch off the phone, hold volume down key and connect it to PC, wait for green LED ilumination and release volume down button
#04 - type 'n' + ENTER to skip install of GordonGate flash driver (You have them already installed, see step #01)
#05 - type 'p' + ENTER for poweroff after flash
#06 - type 'n' + ENTER to skip of dump trim area backup and the Oreo with Pie oem.sin flash will start, wait several minutes for process to finish
#07 - when flash finished, disconnect phone, close command line window
#08 - switch ON the phone and start Oreo system fully, disable any automatic updates ASAP, to stay on temp root supported firmware version of the Oreo
#09 - become a Developer and in Developer menu switch USB debugging ON
#10 - connect the phone to PC and allow connection
#11 - go to c:\platform-tools\ in Explorer and using SHIFT+right click open e.g. first PowerShell window from this folder
#12 - in PowerShell window type 'adb push bindershell /data/local/tmp' and press ENTER to copy bindershell file to the phone
#13 - if You do not have ADB fully installed and You just have drivers copied into the c:\platform-tools\ folder, type the command like this './adb push bindershell /data/local/tmp', add the './' before ADB commands in future, if this error repeats
#14 - in PowerShell window type 'adb shell' (or add ./ in the front of the command again) and press ENTER to run shell in the phone, the command prompt will change from PC:/platform-tools> to the name of Your phone, e.g. G8141:/ $
#15 - get a simple temp root shell according j4nn HOWTO
G8141:/ $ cd /data/local/tmp
G8141:/data/local/tmp $ chmod 755 ./bindershell
G8141:/data/local/tmp $ ./bindershell
#16 - You will know to have a temp root, when the prompt character changes from $ to # (like G8441:/data/local/tmp #), keep this first PowerShell window open
#17 - open a second PowerShell window from the same folder as the first one (c:\platform-tools\) using SHIFT+right click
#18 - in the second PowerShell window type 'adb push OEM /data/local/tmp' and ENTER to copy your modified files from c:\platform-tools\OEM folder on the PC to /data/local/tmp/OEM folder in the phone (in case of error add the './' before the command), after finishing, You can close this second PowerShell window
#19 - activate the first PowerShell window with the temp root still active and type following commands (these are the Robin Banks commands he wrote in the post #13 modified for my XZ Premium single SIM Vodafone CZ version)
mount -o rw,remount /oem
chown root.root /data/local/tmp/OEM
cd /data/local/tmp/OEM
cp -R * /oem
chmod 755 /oem/modem-config
chmod 644 /oem/modem-config/modem.conf
chmod 755 /oem/overlay
chmod 644 /oem/overlay/android-res-305.apk
chmod 644 /oem/overlay/com.android.carrierconfig-res-305.apk
chmod 644 /oem/overlay/com.android.settings-res-305.apk
chmod 644 /oem/overlay/com.android.systemui-res-305.apk
chmod 755 /oem/system-properties/
chmod 644 /oem/system-properties/config.prop
#20 - for You own setup, remember to set rights 755 for any folder name and rights 644 for any file name copied from /data/local/tmp/OEM to /oem folder inside the phone
#21 - Done. Reboot the phone into the Oreo with now modified Pie /oem folder. Close PowerShell window.
#22 - You can repeat temp root now to check, If Your files are really present inside the phone /oem folder and You proceeded well.
#23 - do not panic, if You check the Service info/Software info menu item now by dialing *#*#7378423#*#* and there is still recent modem *.mbn file selected, do not care about it as it is prepared for Pie and You are still on Oreo firmware now
#24 - go to "03_Pie_flash_without_OEM" folder and run newflasher.exe inside, it will open a command line window, stay in this window
#25 - switch off the phone, hold volume down key and connect it to PC, wait for green LED ilumination and release volume down button
#26 - type 'n' + ENTER to skip install of GordonGate flash driver
#27 - type 'p' + ENTER for poweroff after flash
#28 - type 'n' + ENTER to skip of dump trim area backup and Pie without oem.sin flash will start, wait several minutes for process to finish
#29 - when flash finished, disconnect phone, close command line window, now there is complete Pie system with VoLTE and VoWiFi modified /oem folder installed on Your device and all should work from now on
#30 - switch ON the phone and start Pie system, disable any automatic updates ASAP to keep Your modification in tact and not overwritten by future possible updates, if You want, regularly check for the firmware updates manualy and if there is a newer firmware You want to run, be prepared to proceed the whole this procedure again with newer firmware and test if it works for it as well
THE CREDITS
- j4nn for the XZp temp root alternative
- Robin Banks for the original How To
- chris_j26 for information in his [GUIDE] Enable VoLTE for your non operator handset thread (this needs Unlocked BL)
- pbarrette for the info to flash the cust-reset.ta file to clear the device current carrier customization information
- and credits for the SW creators (UnSin 1.13 - IgorEisberg, newflasher v52 - munjeni, Ext2Explore - rcrajesh & regmi_manish)
- and all the others forgotten...
THE DOWNLOAD
Here You can find
files list with the folders structure for all steps described above and compressed modified OEM folder to push to G8141 XZp single SIM Vodafone CZ
- all files used by me listed with their folder structure in TXT file
- a zip file with XZ Premium single SIM OEM folder modified for Vodafone CZ VoLTE & VoWiFi
- pictures
01 original ZA customization info
02 target CE1 customization info before MOD
03 final CE1 modded to CZ customization info after MOD
04 *#*#4636#*#* telephone info after MOD
05 WiFi calling menu item after MOD

Database Users

welcome