Develop Bugs

[Guide][WIP][H930EU] Get VoLTE/VoWiFi functional and available

:INTRO:
OK: here's the thread we are talking about and working on getting VoLTE & VoWiFi to work :good:. For now this is for the H930 Open EU variant only, it worked for two peoples incl. me, but I think this is applicable on other variants of V30, with respective edits (/OP, you'll read later), too. Maybe even to other phones? I don't know, LG is sth (=something) special This thread will rise with time I think, with different edits or ways to reach the goal: we want VoLTE/VoWiFi, sth, LG imho should've taken more care of...
I hope, my english is sufficient so everyone understands what's to do And, btw.: you should have "Allow OEM Unlock" switched off.
User @Krekos/CZ/ did help me in a special way: he zipped his modem config files I by accident deleted from my phone and uploaded them :good: Without them I would've not being able to complete this work, and therefore I wanted to say thanks again to him at this point (I think you can't hear this anymore, hm? ). He's btw. the second person for whom this worked, he's got VoLTE&VoWiFi now.
These files should work on other SD835 phones too, I link them here for archival. Eventually we can get a collection from every variant, this way we might be able to activate VoLTE etc. for a carrier on a phone which was not intended to being used with other operators. So a call to other variant users: can you please tar and upload these files to XDA? Procedere is:
Connect your phone via ADB and open a command prompt
type:
Code:
adb shell tar -czf /sdcard/mbn-files.tar.gz /firmware/image/modem_pr/mcfg/configs
Upload this file to your post here in this thread. I'll add it to the list then.
Links to modem cfg files (mcfg_sw.mbn):
H930 EU Open
US998 Open
These files need special permissions, of course... Otherwise it would be boring
The path (on a LG phone) for oreo firmware is as follows:
/firmware/image/modem_pr/mcfg/configs
For pie it's not /firmware/, but /vendor/firmware_mnt/: pls remember to change path in the following process accordingly when using pie.
Permissions are:
files 0440 system:system
folders 0550 system:system
Apply them via terminal emulator or adb:
Code:
cd /firmware/image/modem_pr/mcfg/configs
chown -R system:system * {apply to everything in this folder and subfolders correct user and group}
chmod -R 0550 * {apply to everything in this folder and subfolders permissions}
find . -type f -print0 | xargs -0 chmod 0440 {apply to files only (not directories) in every (sub)folder permissions}
:MAIN PART:
Prerequisites:
- H930 (or variant, later)
- rooted
- File Manager with root privileges
- eventually a decent editor of your choice
- and a little bit knowledge about giving permissions and changing owners/groups, if needed
I won't give help about e.g. files not editable because of problems with filemanagers or root, do the search work for infos and parameters you need, or anything else, sry You have to prepare and maybe investigate some time to find some infos. You have to know, that this can lead to a brick, if you're doing weird stuff
Let's begin with backing up your complete ROM via TWRP, incl. efs, data and all you need. Backup your OP partition too:
Code:
dd if=/dev/block/bootdevice/by-name/OP of=/sdcard/OP.img
It's about 344mb in size and can be restored in recovery or ROM, adb or terminal emulator:
Code:
(adb shell) dd if=/sdcard/OP.img of=/dev/block/bootdevice/by-name/OP
Then gather some infos, for now it looks we only need MNC and MCC, which identifies your operator. Maybe it later turns out that you need parts of your IMSI too. You'll find it in LG's hiddenmenu:
*#546368#*930#
Field Test => SIM Info
You can check, if the IMS Settings are available already. If yes, then there's a high chance you don't need the "some more config" part.
Write it down and have it prepared. Now the editing session begins
First we will load our modem config for our operator. The corresponding script somehow seems broken as it should do its work with files in /data/shared folder, which isn't.
These configs can give some extra parameters and contain infos about your operator / SIM provider etc.: Open your filemanager (and/or maybe editor, if isn't integrated in fm) and open the file "/firmware/image/modem_pr/mcfg/configs/mcfg_sw/mbn_sw.txt". Here find the path for your provider. O2 Germany would be "mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany/mcfg_sw.mbn". Append these = the complete path for your config file.
Code:
/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany
Copy your op config path, you need this for one of the following edits.
Now navigate to the folder "/data/property". There should be three files we need. If they are not there, create them with root:root, 0600 and following content pls:
persist.radio.buffet_mbn_file => the long path you copied before
persist.radio.buffet_enable => enable
persist.radio.sw_mbn_update => 1
Otherwise just edit and save them afterwards. Perform a reboot and then check in hiddenmenu => Field Test = MCFG Buffet, if this file is loaded. Should
Some more config is needed. We now need the before told MNC and MCC and maybe the IMSI. We need to point your ROM in the right direction (modem itself is done): localizing it and giving the exact operator infos. Have a check of following files and a look, if they are configured already correctly for your operator, or you have to edit them.
/OP/client_id.xml:
Is your MNC & MCC inside? If not, copy and paste an example line, edit this one so it suits both.
/OP/OPEN_EU/config/carrier_code.xml:
Same as above, but a little more complicated. Explanation with an example line:
Code:
<profile carrier="O2D" suffix="O2D" carrier_code_fast="" carrier_code_late="TLF" country="DE" mcc="262" mnc="07" mvno_type="imsi" mvno_match_data="26207200xxxxxxx" />
"Profile carrier": you find this in the long path to your .mbn file you copied before O2D is O2 Germany, edit this to fit your sim provider.
"suffix": same
"mvno_match_data": this is part of your IMSI. When your provider is already listed, compare the five numbers after your operatorcode: 26207200xx. This all together has to be the same as the first ten numbers of your IMSI. If not, edit it. This is one of the reasons for VoLTE chaos on O2D, but that's another story.
/OP/OPEN_EU/config/com.lge.ims.rcs.xml
Same as above: copy and paste a line of simoperator section and edit with your operator details. "prefix" is your country calling code.
/OP/OPEN_EU/config/featureset.xml:
Change every item which is "false" to "true"
/OP/OPEN_EU/config/vo_config.xml:
Most likely you need to create an entry for your operator with mnc and mcc. do this and change both variables to "1":
Code:
<info mcc="262" mnc="07"><!-- O2D (you can write anything here or leave it, it's commented out)-->
<prop
support_volte="1"
support_vt="1"
/>
</info>
[b][i]Maybe[/i][/b] for some rare cases this is the only edit you need to do to get VoLTE & VoWiFi running :D
Reboot now, then continue. If sth in custom.prop or build.prop is edited the wrong way, this can cause bootloops, so you don't have to do the beforedone work again. And: when something in general went wrong in /OP directories edits, you can dd your OP partition back.
/OP/OPEN_EU/cust.prop (they're all case sensitive):
ro.lge.capp_cupss.rootdir=/OP/OPEN_EU
ro.build.target_operator=OPEN
ro.build.target_country=EU
ro.build.target_region=EU
ro.product.locale.region=your region, e.g. "DE" for Germany
ro.product.locale.language=your language, e.g. "de" for Germany
ro.lge.cupssgroup=GLOBAL-COM
ro.lge.opensw=EUR-XX
ro.lge.radio_mcfg=1
persist.lg.ims.volte_open=1
Reboot.
/system/build.prop:
ro.product.locale: change to match your language
ro.lge.capp_cupss.rootdir=/OP
ro.lge.capp_cupss.op.dir=/OP
Reboot again .
:0UTR0:
The VoLTE and VoWiFi switches should be present now, a) in Phone Settings (both) and b) in Network Settings (VoLTE). We should now be able to hop into IMS Settings. You find it in LG's hiddenmenu => Field Test => IMS Setting.
First we let the IMS setting show an icon in statusbar, this way we don't need to dial the hiddenmenu code everytime we need the settings. A nice sideeffect: it shows if you're connected or not To do this tip on "Test" and activate "Show Icon". After that go back to the main screen and scroll down to "GPRI VoLTE/VoWiFi". Here you can activate VoLTE/ViLTE/VoWiFi/ViWiFi, depending on what your provider offers in your contract. Go back again to main screen, go into "Test" menu, then "Load Preset Configuration" => "Initialize configuration". Now you can do a reboot and press a thumb: maybe this was it and everything is up and running! Maybe...
For seeing if VoLTE is up you can check "Debug Screen" => "VoLTE Debug Screen" inside IMS setting.
You can also turn on VoLTE and VoWiFi indicators/symbols, which are then on the right side of your statusbar near the clock. In IMS settings: => "GPRI VoLTE/VoWiFi" => "Registration" => "VoLTE" => "Indicate VoLTE", and the same for VoWiFi. To be able to place a call in flight mode but with WiFi calling on, enable "Airplane Mode" in VoWiFi menu.
In case you experiment with IMS Setting and suddenly a com.android.phone (or other) fc occurs, you can boot into TWRP, mount data and delete the directory "/data/user_de/0/com.lge.ims" with its integrated filemanager.
K, you're done :cyclops: Pls give feedback how it went for you!​

Wow. Thank you.

yeah, I hope it's written in a way everyone understands it atm it's more like a dev thread, it will be rewritten for newbies when everything is clear and fully pointed out

.. Uploaded stuff ..
Hi - thanks for this info. I'm trying to work with it, and added my files. + a few extras stuff> actually not really sure how to do this .... any help? ... Thanks I have a US998 phone.: but want to get the Canadian settings all working ; specifically for Freedom Mobile ( aka : Wind ) --- the files are from a saved backup ( dump ) {{ the uploaded files are from a backup of the H933 canada firmware dump }} ... I'm currently using the US998 kdz firmware on the phone ....

let's start with
- do you see "MCFG Buffet" in your hiddenmenu?
- can you list all the content (the main directories) in your /OP folder pls?
- does the firmware modem config folder exist and is your provider inside?
- and where does your ro.lge.cupssgroup point to? (adb shell getprop ro.lge.cupssgroup)
I don't know the specialities of other variants, especially the offered providers. I don't even know if this is possible and which files you uploaded to your phone. can you either list them or point to them with a link eventually?

OK thanks - I'll work on this some more tomorrow -- I don't know where the files I uploaded went to! > but I uploaded >Folders>>> Carrier Config, Modem_pr, qcril_database, vendor, wifi & build.prop. All files were dumped from a working Phone loaded with the Canadian .Kdz H933. ... > ok so I actually took all those files,and overwrote the files om my current phone setup which is US998 .Kdz -- didn't even crash the phone <<< Go figure. I just had to clear the cache and dalvik cache. VoLTE may be working, but my Carrier has a very limited VoLTE service... so I cant check right now. VoWifi is not working. Every setting and menu has it turned "on" but is no working. .... tomorrow I'll follow your instructions after I do a fresh install. of the .KDZ. ..... be well

be warned: this can be time consuming and causing headaches, too stock files would be the best to start with.
is it a native us998 phone? it's the one one can "frankensteining", isn't it? you've overwritten these files and partitions, when I understand you correctly?
you should get hands on following stock partition disk dumps and folders first (kdz won't help as all these files are preloaded and can't be flashed via kdz):
- canadian OP partition (the more important one) (canadian_OP.img <= example filename)
- US998 OP partition (for being able to revert back to stock and trying to get volte/vowifi running with only some edited files on stock us998 partitions, only a few added files or maybe folders from canadian OP partition and only the .mbn file for your provider, taken out of firmware modem config folder). this one shoukd be flashed and worked with.
- stock system image (kdz flash us998)
- clean unencrypted data partition (factory reset and then completely set up with your apps and settings, no db or ither files copied).
- you've got a backup of your stock efs partition?
try to keep your phone as clean as you can as this can only be of help about not being confused. are there gsm/(w)cdma/band differences between us998 and canadian 993?
this could go an interesting way let's see, maybe we get it is wifi calling enabled on your contract? I wasn't able to determine this out of your post.

there's the possibility to edit the thresholds when wifi calling aborts and switches to cell telephony or volte. it's located in /system/etc and inside a filename called "andsf_your_provider_code.xml", for o2 de it's named "andsf_26207.xml". I've set every threshold to -90, this way wifi calling is still working with only one or two bars wifi reception. otherwise it would abort just too early and switches to other telephony bands.

US998 mbn-files

Thanks for the detailed info.
Not working for me. I managed to add my operator and enable IMS but can't figure out how to make IMS register. Might be because my operator is a little more retarded and uses IPv4 only. No idea where to set that policy, it isn't in IMS settings anymore on the V30.

sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?

Hi. Thanks for this. Is there any way that this can be applied to aosp ROMs?

Those mcfg files are found inside the modem partition and you can pull them out from any kdz.
Do you have an idea where this is located? (/nv/)
Edit: Also, added some picture showing volte working... when it's not (switching back to something else)

you're really sure about this? since I've flashed a kdz and a modem and unfortunately this didn't bring back these files on my phone maybe I did sth. wrong, this is really interesting now. thought they were on efs partition; but these nv files should be on efs. I'm not really sure about that, maybe someone other can finally confirm :good:. edit: I remember I've got carrier services installed, would be interesting if this makes a difference. I hardly believe but try it:
https://play.google.com/store/apps/details?id=com.google.android.ims
about aosp: there's much more needed, proprietary files and more config inside sources etc pp. I evtl. wanted to do compilings again in winter, I wanted to try this but I need additional ssd space before

Oh sh*t...
I guess I lost my efs partition then...
I tried a bunch of stuff from your first post... sadly, I don't have an /OP/ directory at all... and when I try to force the mcfg mbn (from my sdcard lol, cauz my carrier is not provided in the us998 modem)
Edited a bunch of stuff in my build.prop to make it look more like the canadian one.. but it still doesn't work (even lost the volte option now in the mobile setting menu..)
Also, I tried to flash my canadian modem files... sadly.. the phone boot but the modem doesn't initialize at all... (no wifi and no mobile network)

aye, sh¡t... and there's no efs backup from your phone done / available as it sounds. you lost your IMEI too??
can you check the directory
/dev/block/bootdevices/by-name
and see if there's an OP "file"? eventually only the script which mounts it is broken. if I remember correctly there was a thread about regathering the IMEI or at least fixing some stuff on efs. maybe this helps you, unfort. I don't know where it was, you have to search yourself.
k, sleeping now, it's hard for me these days after my shoulder operation... hopefully we get your phone back running! I'm optimistic flashing a efs backup and changing the imei back to your original one for example. don't know if this is possible, but how often did I think "sh¡t, now it's over, phone's bricked" and then a solution appears out of nothing. you should've seen my face in the moment volte came.up on my phone xD xD xD
see you later be optimistic!

Oh sorry! I still got my efs partition.. I thought it would get overwritten when doing the frankenstein method.. But I guess not.. Is there any way I can debug why the modem doesnt work at all when flashing the canadian one while using the us998 system?

there is but I don't have it in mind atm it's explained here at xda somewhere, logcat and dmesg is used for that :good: can be that it is bands related? so you have to unlock bands in your modem settings? edit: most likely not as wifi is dead too...

seadersn said:
sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?
Click to expand...
Click to collapse
I already tried to set IPMI with my data like [email protected] but IMS still don't register and the setting doesn't stick. it always reverts to a default like [email protected].
I also created the ims APN but it doesn't help with anything.
I'm still digging but so far I have no clue what's going on.

hmm, did you try configuring sip telephony? for o2 germany the registration looks like
country code + phone number @ telefonica.de = (for germany) [email protected]. have a look at /data/user_de/0/com.lge.ims/shared_prefs/impu_list.xml
(user_de: I don't know if this is indicating the language the rom uses? so for an english language build it can look like user_en? I don't know...).

[IMEI] [FIX] [Noob] [Friendly]

Overview ​
Now, I have seen many people facing problems like lost IMEI or NVRAM warning in their wifi list! Well, these are normal errors when you often flash a custom and wiped system or update using SP Flash Tools. So fix isn't that hard! But still, many people suffer from this! Now, this guide is applicable for every device(MTK) but BPLGU modem file will vary from device to device. I have specially made this guide for Lenovo Vibe K4 Note users!:laugh:
WARNING !!! IMEI CHANGING IS ILLEGAL. THIS GUIDE ONLY HELPS YOU HOW TO RESTORE ORIGINAL IMEI OF YOUR DEVICE! I DONT TAKE ANY RESPONSIBILITY OF ANY ILLEGAL ACTION TAKEN AGAIN YOU! BE AWARE IF YOU ARE NOT SURE FOR WHAT IMEI IS USED FOR ALSO I DONT TAKE ANY RESPONSIBILITY OF DEAD DEVICES/ BRICKS! PLEASE DO SOME RESEARCH IF YOU ARE NOT AWARE OF ANYTHING. HOWEVER, THIS GUIDE WILL HELP YOU DEAL WITH THINGS, IF YOU READ CAREFULLY AND FOLLOW INSTRUCTIONS THEN YOU DONT NEED TO WORRY ABOUT ANYTHING!
Click to expand...
Click to collapse
So lets fix it up !
Required stuffs !
Windows PC (7/8/8.1/10)
Usb Cable
Few tools
Drivers
Your device, ofc !
Download Section !​
1. Scatter files !
2. MauiMETA
3. Temoprary IMEI fix.zip​
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed.
Process !​
Now most of you must have thought hey Max where is NVRAM fix? There was nothing about NVRAM in title Well chill down I will target NVRAM NOW !! So let us begin! Now as you have downloaded entire scatter files so NVRAM needs entire scatter files. "Woosh! Thank god it was useful somehow" most of you must have thought Hehehe Well one more thing if you are using permanent NVRAM fix then use it before you flash IMEI or else you lose it again if you fix NVRAM after IMEI. However, a temporary fix can be flashed later on.
* Now navigate to the firmware folder
* Look for scatter file open it in notepad or notepad ++
* There look for this line, "partition_name: NVRAM"
* There you will also notice, "s_download: false"
* Just change it to, "s_download: true"
* Save and exit!
* Open Sp flash tools and load scatter file(Remember a thing, you will have to use an older version of SP Flash Tools)
* You will see checkbox of NVRAM just choose it and keep rest options unchecked!
* Flash into your device and all set!
NVRAM IS FIXED PERMANENTLY :good:
But now for those who are lazy doing this, there is a temporary zip file which you can flash and NVRAM problem will be fixed for a limited time to do so just go to download section and download temporary fix zip file and flash it into TWRP (Yes, that's why we needed TWRP):angel:
Now before we start doing anything make sure you download everything from the download section. Also, make sure your device is having TWRP installed. (YES AGAIN MAKE SURE YOU HAVE EVERYTHING)
• After that, run Maui META 3G
• Use USB COM
• From Options menu, select “Connect smartphone in meta mode”.
• Press Reconnect and connect the phone in the switched off state.
• Wait for a minute. Your Device automatically boots into meta mode. The blinking led will become yellow and you can see "connected with target"
• Now from the drop-down menu select “IMEI download”. Click ok till you see IMEI download box.
• Click Change NVRAM Database FIle and browse to “MT6753 DB” folder and select the following file.
File\MT6753\
BPLGUInfoCustomAppSrcP_MT6753_S00_K5_ROW_LWG_V56_ 1_lwg_n (BPLGU modem file for mt6753, do a double check as the name might change with firmware versions).
[Well I have not extracted this file yet from stock ROM scatter files. However, I have given you the download link of entire stock ROM look the file there itself !]
• Click ok on any warning.
• Leave IMEI Increasemnt 0.
• Write first 14 digits of your IMEI in IMEI box and last 15th digits will go in checksum(should be entered automatically). Eg:- if IMEI is 123456789123456, write 12345678912345 in IMEI and 6 in the checksum. Do same for Sim_2
[Now most of you must be wondering where is my IMEI. I don't remember it and also it's not there in the list. Don't worry pull your back cover and you will see IMEI sticker there just type the same IMEI]
• Press Download To Flash. You will see Download IMEI flash successfully. Now close the box (or alt+f4 or close from task manager if stuck).
• Restart the phone
• Open Dialer and type *#06# and you will get your valid IMEI number.
* Well if you saw the same IMEI then you are done !!! :good:
Credits : Yaas !! Why not ?
meprakash_pyc
Sahil_Sonar
KM (One who made NVRAM fix for lazy people :silly
If this post was helpful to you just hit :good: below my posts !

Drivers ?
Hey Maxx where are our drivers? Well, come on relax as you have downloaded scatter files all the drivers are there you can additionally get extra drivers from my https://forum.xda-developers.com/k4-note/how-to/bootloader-unlock-t3846902 another post [/url] Yes the same one! TWRP one! I have added ADB Drivers there follow the same process also there is a manual how to install drivers same is applicable for these drivers!

after loading that modified scatter file, it says that it should not be treu value

yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.

royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Actually, I have tested this thing on my own device... No idea what's wrong with you. You can also try notepad c++

jaskoooo said:
after loading that modified scatter file, it says that it should not be treu value
Click to expand...
Click to collapse
royskeyz said:
yes bro, after modifying scatter file, flash tool wont allow to load it. im hoping this will fix my wifi issue.
Click to expand...
Click to collapse
Try older version of SPFT.

I've downloaded your drivers and tried many other drivers,None worked,Please help me.With the drivers i have im able to Flash stock through SP,Device gets detected too,But i dont know y its not working for this tool or SN writer..This is the error im getting..Communication through either RS232 or IPC error,Please reconnect..

JaSomTy said:
Try older version of SPFT.
Click to expand...
Click to collapse
Exactly!

where is nvrm file 's ?
where is nvrm file 's ?

Can anyone tell which version of sp tool worked for them? that would really really be helpful
Edit: Files are no longer available on google drive

Rom Access or advice for TAB S4

My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin

This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.

cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated

Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.

cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained

its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed

The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts

c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false

Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking

c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?

ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!

Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals

Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????

built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be

c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.

ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility

c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.

[solved] Android 9 - no modifications in oem/OP/...

Hello,
since Android 9, there are no modifications (rename, delete, ect) in oem/OP/... allowed.
ex (https://forum.xda-developers.com/lg...-enable-volte-vowifi-uk-mobile-t3835167/page3)
After reboot, the modifications has been recovered by itself.
Can everybody help?
Have a nice day

flash this boot
boot_20b-magisk-op_disabled-1.img
https://drive.google.com/open?id=12htRoR94XKocVQZ4VWubLPsIgjLf3a8B
or
using hex-redactor open your boot.img and change boot.product.lge.op_verity=1 to boot.product.lge.op_verity=0, save and flash it

Great - it works like a charme. I did it by myself with a simple hex-editor (HxD) :good::good::good:

edit
boot_20d_magisk_op_disabled.img
https://forum.xda-developers.com/showpost.php?p=80276083&postcount=12
thanks!!!

help
Can someone help me here pls? https://forum.xda-developers.com/showpost.php?p=80961859&postcount=24

you need to flash respective boot with op dissabled for your especific stock rom
you need open bootloader and caution... you can brick your phone...

Stvn77 said:
you need to flash respective boot with op dissabled for your especific stock rom
you need open bootloader and caution... you can brick your phone...
Click to expand...
Click to collapse
I have LG H930DS, which actually didn't suppose to have unlockable bootloader, but i have unlocked it, and magisk root with this tutorial from ChazzMatt: https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193 , and because of that having access to /OP/OPEN_AME_DS (oh yes, btw, my phone is H930DS, but have AME software version, which stands for United Arab Emirates, latest oreo, and i don't live in UAE, i'm living in Europe, so folders /OP/OPEN_AME_DS and someone who have europe V30 with folder /OP/OPEN_EU actually have little differences, some files related to ims are missing in my one, and some are different from EU folder). My carrier don't have VoLTE and VoWifi, but it have video calling, so i want somehow to activate ims status to be registered to have video calling. If someone have that OPEN_EU(or any other which you have OPEN_) folder, and have ims registered (check your ims status by dialing *#*#4636#*#* and three dots up right corner), and maybe have video calling in dialer, i would be really thankful if someone send me that OPEN_ folder(like zip) to compare with my OP folder, and maybe send me even build.prop

vo_config.xml
Hi all, i have the following situation:
- I've unlocked an LG V40 EBW with LG unlock;
- Extracted boot_a, boot_b image from latest kdz ( 20f) in a Linux VM
- Installed Magisk Manager, patched boot_a with Magisk Manager
- Booted in ADB from magisk_patched.img
- Installed magisk_patched.img in Magisk Manager on slot 1
I have obtained permanent root on the stock rom.
I'm trying to edit vo_config.xml from /oem/OP/OPEN_EN_DS/config for VoWiFi/VoLTE.
It seems this is mounted on /dev/block/dm-0.
Even if i can write to the file, change permissions etc. , the changes are reset after a reboot.
I have already HEX edited magisk_patched.img "judypn androidboot.product.lge.op_verity=0" and flashed it in ADB and didn't solve my problem.
How could this be done? I'm on Android 9, stock rom ( 20f)
Help would be appreciated.

[Guide] Make the Korean Q Great Again [relocalise, volte, wowifi, debloat and more]

IF YOUR BOOTLOADER IS NOT ALREADY UNLOCKED, THIS GUIDE IS NOT FOR YOU.
READ EVERYTHING AT LEAST ONCE BEFORE PROCEEDING!
THIS GUIDE WORKED GREAT FOR AT LEAST 3 PERSONS, THIS DOESN'T MEAN IT WILL WORK ON YOUR PHONE.
This guide exist in case the ULM Q never released
This guide should do the following :
relocalize to your country (I'm only providing the files for canada, usa and eu)
Root and TWRP (useful if any custom roms get released)
debloating
volte/vowifi/vilte/viwifi
Very Good battery (see screenshots down below)
mute shutter camera
4k 60fps video recording (?some people said it wasn't available on the korean Q?)
wifi tethering
and more
WHAT'S NOT WORKING FOR ME :
lg smartworld : meaning no lg app update.. which can lead to the next problem
Drag down for search : working only if you do not update the google app
What you need:
1 to 2hrs of free time
Working QFIL with minimal knowledge
Working Fastboot on your pc (See spoilers)
I did NOT manage to make fastboot work on my amd ryzen pc (3600)
here's what I tried :
- multiple fastboot drivers
(fastboot was kinda working.. now it just never load any driver)
- plugged in a usb 3.0 hub
- FWUL : https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
(the latest version as of 2020-11-25 couldn't even boot on this pc...)
- ubuntu
(crashed the phone to a gray screen)
- all my usb ports : 2, 3 and 3.1​ What I didn't try but could work for you:
- plugged in a usb 2.0 hub
- linux mint?​
Soo... what did I do? I went back to my good ol' intel pc running windows 10 worked like a charm.
Click to expand...
Click to collapse
Also, this guide assume you had working volte/vowifi on your phone at some point...
Because, you will need the carrier folder from the /oem/op/ folder.. should look like this : open_us, vrz_us, open_ca..
Or you will need to retrieve it from your working firmware...
I'll be providing :
- Android 10 - G7 - OPEN_CA (Canadian operator folder) (What I'm using on my phone right now)
- Android 9 - V35 - OPEN_US (ULM/GFi) (Confirmed working by @cmrntnnr)
- Android 10 - G7 - OPEN_EU (untested) (thanks @vlad48)
!!!!!! Before crossflashing to the korean kdz !!!!!!
------------------------------------------------------------------------
Crossflashing can break stuff sometime.. it is advised to do a full backup of your phone using https://github.com/bkerler/edl
if you're feeling lucky and do not want to do a full backup... you should still use qfil to atleast backup the following VITAL partitions : Fsg, modem, modemst1&2, ftm
STORE THOSE FILES PRECIOUSLY
------------------------------------------------------------------------
File you need to download :
To your phone SDCARD :​
OPEN_CA or OPEN_US or OPEN_EU (untested) (Decompress this file, delete the zip)
OPEN_CA is too big, I had to delete apks that weren't from my carrier. (Bell)
(open_ca/apps/ -> kept only bell apks)
debloated-priv-app-RENAME-ME.zip (Decompress this file, delete the zip)
debloated-app-RENAME-ME.zip (Decompress this file, delete the zip)
twrp-installer-v3.3.1-v35_a.zip
Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Magisk
(OPEN_EU only) : voenabler-v1.8.zip
​To your pc:​
vbmeta.img
30b_boot_magisk.img
30b_abl.bin (shouldn't be needed, but provided as backup)
Korean Q 30b (I went with LGU_KR since the other one weren't available back then)
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide​
You need to use SOLID EXPLORER, not esfile or any other since I can not guaranteed it will apply the correct permission to the files and folder.
LGUP > Flash V350N30b_00_LGU_KR_OP_1015.KDZ using partition DL, select everything except FTM
Let the phone boot for the first time and reach setup screen
LGUP > refurbish phone using the kdz (this should fix potential nt error when booting the phone, it did for me)
Let the phone boot for the first time and setup the phone quickly so you can install app. (no lock or fingerprint)
Patching vbmeta to edit the operator/carrier information & patching boot for magisk/root
QFIL > partition manager > abl_a > read, store that file and name it : needed_abl.bin
How to retrieve the file: WIN+R , %AppData%/Qualcomm/QFIL , enter, pick right folder, save and rename bin file​
QFIL > partition manager > abl_a > load > engabl.bin (for fastboot)
QFIL > partition manager > abl_b > load > engabl.bin (for fastboot) (Optional)
This is useful in case you need fastboot in the future, simply boot twrp then change slot from a to b and reboot.
To switch back from fastboot : fastboot --set-active=a​
reboot the phone using vol- + power
command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot oem edl
QFIL > partition manager > abl_a > load > needed_abl.bin
QFIL > partition manager > boot_a > load > boot_magisk.img
reboot by holding vol- + power
[*]
Click to expand...
Click to collapse
Reboot to system, Install magisk manager and solid explorer
Start magisk manager and let it reboot your phone
magisk > modules > install from storage > twrp-installer-v3.3.1-v35_a.zip
SOLID EXPLORER > copy the carrier folder to the oem/op/ partition ('OPEN_CA' in my case)
SOLID EXPLORER > edit oem/op/cust_path_mapping.cfg and replace LGU_KR with OPEN_US ('OPEN_CA' in my case)
If you're still getting nt error at boot, you'll have to fix it in order to make the phone load open_us..
try adding a second line like this :
FFFFFF,84=/oem/OP/OPEN_US
If this doesnt do it, you'll have to share your nt error in the comment.
Click to expand...
Click to collapse
SOLID EXPLORER > Rename the folder /oem/op/LGU_KR to LGU_KRori (this will make your phone lag/glitch/freeze real quick.. proceed with the next step ASAP)
Quickly go in magisk and use the reboot menu to get to twrp. (reboot to recovery)
Format data
Reboot to TWRP/recovery
Flash Magisk-v21.1.zip, if it doesn't flash, reboot using the reboot menu to TWRP/recovery again until it works. (no red text)
Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Reboot to system
if the vowifi toggle is not working for you
For OPEN_CA/OPEN_US :
SOLID EXPLORER > move debloated-priv-app-RENAME-ME to /oem/op/priv-app/
SOLID EXPLORER > Rename the new folder to OPEN_US or OPEN_CA
Reboot
Click to expand...
Click to collapse
FOR OPEN_EU : (these steps are from the v40 community telegram, Quote from Lucky)
magisk > modules > install from storage > voenabler-v1.8.zip
If you transplant the KR OP with OPEN_EU, and are based in EU, this module should add the props that enables the VoLTE and VoWifi options.
Only if this fails, do you need to tinker with the xml files.
Click to expand...
Click to collapse
Optional.
Adding back missing lg apps (I provide QMemo and LG Weather)
you can either install manually the apk from debloated-app-RENAME-ME
or
move the folder to oem/op/app/ and rename it OPEN_CA or OPEN_US
Click to expand...
Click to collapse
Enable LGMessage over Google message and add back LGFMRadio (you'll need to uninstall any sms app you might have installed.. like google message or fb messenger(if used for sms))
Solid Explorer
edit this file /oem/op/open_us/config/custom_apk_list.cfg
change the sign on the following lines (from - to + and + to -)
-com.lge.fmradio:/system/product/priv-app/LGFmRadio
-com.android.mms:/system/product/priv-app/LGMessage
-/system/app/SmartMessagingEngine
+com.google.android.apps.messaging:/system/app/Messages
Example
-/system/app/SmartMessagingEngine
to
+/system/app/SmartMessagingEngine
Reboot
Click to expand...
Click to collapse
Do not forget to enable developer option and adb AND
Plug you phone in computer, open adb shell and type su
on the phone, grant root.
It is useful to have a root shell in case the phone is stuck while booting (not boot looping)
you can also just reboot to twrp and undo your modification from there.
Click to expand...
Click to collapse
Thanks to everyone patient enough to answer my questions and who did provide most of the solution for this guide:
vlad48, Lucky, azitlies, xsavi, kaneorotar and many more..

Thanks for the guide

alonzo_ama26 said:
Thanks for the guide
Click to expand...
Click to collapse
No prob!
Added OPEN_EU files, but they are untested.. no clue if everything will work... Some people in the v40 community got it to work
Good luck everyone

I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.

issc said:
I've completed all the steps (except for lg weather) and I didn't notice anything different in call features until I saw the description of the international roaming setting referenced "outside of US PR etc." instead of "outside of foreign territory or whatever" which indicates a success.
Then I Applied the vomaster.zip from somewhere else (prob the same thing as the OP's not sure) and flipped on wificalling on the settings and got the setup prompt for wificalling from my carrier and later a "wifi setup's been completed" notification, so I guess things are finally good again. Unfortunately RCS doesn't seem to want to cooperate either way =\
Not sure why I did it because korean q on its own was usable, but I did it it anyway and it is nice, performance feels better too but this could be because I went from LG firmware to open_us. Both the incoming and outgoing calls and texts feel much snappier as well and doesn't take 5 seconds to go anywhere. Also it doesn't ask me whether I want to listen to the call recording or not at the end of every phonecalls so that's nice. thank you
-edit
one question, is there any way I can use the korean AOD's? I liked the one that shows calendar and time.
Click to expand...
Click to collapse
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..

[ATTACH

cloud1250000 said:
The V35 engineering abl you got from here : https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145
This file was renamed to engabl.bin in this guide​
Click to expand...
Click to collapse
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?

After step 5 I started to get some weird outputs.
fastboot.exe oem edl
FAILED (Status read failed (Too many links))
fastboot: error: Command failed
Click to expand...
Click to collapse
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.

rpgdev said:
That file is a zip file with two different files in it, do you mean to rename this zip file to engabl.bin?
Click to expand...
Click to collapse
omg no, pick one of the 2 files and rename it to engabl.bin

Blad2301 said:
[ATTACH
Click to expand...
Click to collapse
??????

rpgdev said:
After step 5 I started to get some weird outputs.
Seems like that output is normal because I have the rom rooted and twrped right now but I did have to change the active slot to B at this point because otherwise QFIL wasn't able to read the partitions afterwards. Oddly enough that was the only change I had to make, every other command worked as is referencing abl_a even though I changed the active slot to B (and when I flipped the steps to target slot B instead I just got bootlooped).
Everything's looking good so far. I had not been able to setup twrp on this phone so that's welcome. Hotspot wasn't working on Oreo either so that's another good improvement at least for me. Hopefully, this update ends up being a little bit more stable than Pie.
Click to expand...
Click to collapse
sometime, with both fastboot and qfil/edl.. you need multiple try to get them working

cloud1250000 said:
omg no, pick one of the 2 files and rename it to engabl.bin
Click to expand...
Click to collapse
that's somewhat ambiguous, I ended up putting the abl_a in the a slot and the abl_b in the b slot. Not sure if they're interchangeable or if that's the reason why I experienced the issue I experienced. Shouldn't be but who knows.

I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?

rpgdev said:
I'm noticing that locking the screen takes a while using double tap. At least a second or more before the phone responds and actually locks the screen, is anyone else experiencing this?
Click to expand...
Click to collapse
that's odd mine is almost instantly..

cloud1250000 said:
that's odd mine is almost instantly..
Click to expand...
Click to collapse
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q

rpgdev said:
Apparently it was due to my launcher, they're having some issues with that gesture on Android 10.
The Korean Q is solid, I'm surprised that it's performing better than Pie on this phone. Thanks for doing this guide. Anyways, I still get the camera shutter sound any idea as to why? Also, is there a way to disable the vibration for the fingerprint reader when the read is successful? I managed to do it for Oreo but haven't found a way to do it for Q
Click to expand...
Click to collapse
shutter is muted when I'm on vibration mode

cloud1250000 said:
shutter is muted when I'm on vibration mode
Click to expand...
Click to collapse
Ah, I thought it disabled it on all modes. I didn't get it on vibration. Would be nice to disable it on every mode.

Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol

cloud1250000 said:
Right the thing with the korean firmware usually is.. it's not disabled even in silent mode lol
Click to expand...
Click to collapse
I see, do you happen to know where is the camera shutter sound now? It used to be \system\media\audio\ui\ but it seems that dir was removed on A10.

cloud1250000 said:
odd! you really shouldn't have to flash that vomaster.zip at all if you're located in the US.. honestly.. I don't even know if rcs is available in canada and I'm really not sure how to test this feature.. You might have to toggle wifi calling again if you got the wifi calling activation success notification.. it was the case on my friend phone..
Just to confirm...
volte/vowifi working?
ulm or awm?
carrier?
Looks like the calendar is available with the open_ca files... not sure for the open_us.. sorry..
Click to expand...
Click to collapse
I don't know how to check for volte working, but vowifi is def working at my work with ****ty at&t signals.
awm -> ulm -> korean q.
I get advanced chat features enabled but nothing works =/ maybe its fixable with googling but im reasonably happy with my phone atm, minus lgpay not being accessible for v35 and v30s outside of korea =\

Has anyone passed safetynet using this rom? Some pointers would be appreciated.