Related
Everytime I try to install the LGMobile Support Tool it won't go any further on the progress bar than just above the 'ob' of LGMobile.
Has anyone else had this issue and managed to resolve it - i know there was a thread back in may but nothing since then
I've tried both on a windows7 x64 and windows xp sp3 machines
regards
this is just a quick update and may help others who end up having same issues - the reason the app freeses during install is because it accesses the internet on port 9002 - once you allow this port outbound on your router/firewall the installation will work fine.
Do not remove the setting otherwise you can't run the app after it's installed as it connects to internet again..
regards
Mine didn't install on win 7 64 bit
Xp sp2 was totally fine
Sent from my LG-P990 using XDA App
Hi i have same problem,but i don´t know how to allow 9002 port a tried to look for tutorials on google but i didn´t find anything that works and i still cant istall lg mobile support tool
What router do you have Branding/model?
internet explorer
sani340 said:
Hi i have same problem,but i don´t know how to allow 9002 port a tried to look for tutorials on google but i didn´t find anything that works and i still cant istall lg mobile support tool
Click to expand...
Click to collapse
hi, i had the same problem and was able to install the update tool on internet explorer instead of google chrome. thought it might be helfull
the thread is written solved but we actually needs step by step guide.
how?????
walkerx said:
Everytime I try to install the LGMobile Support Tool it won't go any further on the progress bar than just above the 'ob' of LGMobile.
this is just a quick update and may help others who end up having same issues - the reason the app freeses during install is because it accesses the internet on port 9002 - once you allow this port outbound on your router/firewall the installation will work fine.
Do not remove the setting otherwise you can't run the app after it's installed as it connects to internet again..
regards
Click to expand...
Click to collapse
HOW do you do that??????
wee2000 said:
the thread is written solved but we actually needs step by step guide.
Click to expand...
Click to collapse
Yes, how did you solve this??
I would like to say some really bad word for the OP, as this kind of behavior is the worst!!!
F YOU MAN!
there is nothing worse than presenting the problem, and telling after that: "ok I solved it, move on ..." << well youare a douche. biggest one there is.
Change hosts file
Hi there all, I had the same problem and solve it while going to hosts file C:\Windows\System32\drivers\etc
Open up hosts file with notepad and delete any line that does not have hashtag "#" in front.
So it should look something like this :
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for
# Windows.
#
# This file contains the mappings of IP addresses to host
# names. Each # entry should be #
# kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding
# host name. # The IP address
# and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on
# individual # lines or following
# the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
#
#
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Save it, File --> Save ot Ctrl+S and close. Double click on B2CAppSetup.exe and let me know if it worked for you.
Cheers
Unable to Install the LG MOBILE SUPPORT TOOL
Klindic said:
Hi there all, I had the same problem and solve it while going to hosts file C:\Windows\System32\drivers\etc
Open up hosts file with notepad and delete any line that does not have hashtag "#" in front.
So it should look something like this :
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for
# Windows.
#
# This file contains the mappings of IP addresses to host
# names. Each # entry should be #
# kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding
# host name. # The IP address
# and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on
# individual # lines or following
# the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
#
#
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
Save it, File --> Save ot Ctrl+S and close. Double click on B2CAppSetup.exe and let me know if it worked for you.
Cheers
Click to expand...
Click to collapse
The above method didn't work for me. Please help suggest an alternate method or another OS build where this might work.
I know it's old post but today i have problem installing lg mobile support tool.
i install lg pc suite first and then voila lg mobile support tool installed.
Igoritza said:
I would like to say some really bad word for the OP, as this kind of behavior is the worst!!!
F YOU MAN!
there is nothing worse than presenting the problem, and telling after that: "ok I solved it, move on ..." << well youare a douche. biggest one there is.
Click to expand...
Click to collapse
WTF are you *****ing about??? He thinks he solved the problem by allowing port 9xxx (it is not the solution, but all the same...) and now you would like someone to solve it for you at your home on your own router?!?!?
F U man!! what else would you like???
in your windows explorer, right click on the downloaded setup file named "LGMobileSupportTool" and go to file properties. In the attributes section, check Unblock. You must have administrator privileges. Run the file as admin.
Hi guys, in my case it was caused by running LG Bridge app on the background so go to tray and kill this app then installer of support tool was able to finish loading.
Hello everyone
I am more than aware that this is a very old thread, so let me explain myself a bit.
Basically, i have an old optimus l7 ii (wrong phone for this thread, ik but where else am i going to ask) that i want to update to kitkat from jb. to do that, i have to install this tool for the cse flash in lg flash tool 2014 to work. problem is the exact same one as in the original post, except none of the methods mentioned here worked for me. not opening port 9002,editing the hosts file, closing lg bridge, running it as admin, nothing at all. i think the reason why it doesn't work might be because the servers needed for the installer to work are down (what with lg now having shut down their mobile division and everything). still though, i need some way for this to actually work (if there is one even at this point)
I typed * # * # 2663 # * # * and clicked update. He showed me the message "Update failed" and does not touch. Help
oh said, you typed touch screen factory version. touch screen firmware was changed. And solution to fix it. But, you can bring your device to service center and talk about fake story. if you lucky, service center will accept wanarity your phone
It's a homemade way to fix this?
Sorry for my English
I try this: http://forum.xda-developers.com/showthread.php?t=1487685
EDIT:// its work!!!
I have problem with WIFI keeps turning on but it never turn on like usual, i tried flash stock rom neswest build and do factory reset it with no luck.
Searching around internet and found that there are some Nexus5 user can fix it by delete folder of mac address (they said it is in /persist/wifi folder) buti cant find that folder in my Marshmallow. Anyone knows how to fix this i think it is something wrong with corrupted MAC address it quite weird that my MAC Address is 20:00:00:00:00:00
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
pradipsoman said:
Got EXACTLY the same issue...I tried to flash all available roms, right from 5.0.0 to the latest 6.0 and no luck...Wifi and Bluetooth are non existent now! Is your bluetooth ok?? And its not 20.00.....its 02.00.00.....pls check again...
Click to expand...
Click to collapse
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
Droidphilev said:
Messed up EFS partition? If you don't have a backup i *think* the device is hard bricked > repair
Click to expand...
Click to collapse
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
pradipsoman said:
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
How can a messed up EFS prevent the WIFI and Bluetooth from working? All other features work well. And if the partition is messed up and device is hard bricked, how does it work and all the other features work...Could you explain please...and if you have the knowledge could you give any tips to get it right?
Click to expand...
Click to collapse
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Droidphilev said:
AFAIK the factory puts files in that partition that includes the wifi MAC, BT MAC, IMEI etc etc. From there the rom reads the mac addresses. If it cannot find these then wifi won't turn on. I may be wrong that this is the case though. I had a problem with a tablet before. Flashing something caused that the permissions of that file became wrong, i had no wifi either. Luckily for me the file was still there and changing permissions fixed it. Is you IMEI still shown correctly in "about"?
Click to expand...
Click to collapse
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
pradipsoman said:
Yes, my IMEI is shown correctly but wifi mac id shown as a bogus number i.e 02.00:00:00:00:00
Click to expand...
Click to collapse
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Droidphilev said:
That's something i guess. Otherwise you wouldn't be able to make calls any further. Hopefully you will find a way to fix. Please report here.
Click to expand...
Click to collapse
Could it be related to the /persist folder
pradipsoman said:
Could it be related to the /persist folder
Click to expand...
Click to collapse
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Droidphilev said:
check PM.
Can you tell us exactly what you were doing when this happened? you flashed a rom or something like that? Would be good to know.
Click to expand...
Click to collapse
I was on 5.1.1 and then everything was working fine...I installed the 6.0 OTA and then this happened....
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
pradipsoman said:
Went ahead and did the hard brick repair method to see if that would help, but even after that the problem persists!
Click to expand...
Click to collapse
the unbrick thing or the persist thing?
you guys do realize that google is using the wifi to figure out your location, right? even if you never ever turn wifi on. you have to disable scanning in the location settings for google not to use the wifi.
none
If you had a hard bricked device you would know it because your phone would have a black screen and you would have a paperweight
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
pradipsoman said:
I did everything...including the persist wipe etc....No use...seems the wifi/bluetooth chip is dead after the 6.00 OTA update
Click to expand...
Click to collapse
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
I have the exact same problem but with a completely stock, never-rooted Nexus 6. Marshmallow 6.0 OTA arrived a week after the 1 year Motorola warranty expired, and problems with screencasting started immediately. But yesterday, the wifi quit, and the phone rebooted itself moments later. The wifi has never come back on since. I also noticed the bogus 02:00:00:00:00:00 mac address, suggesting that something got corrupted. For reference, this phone was purchased directly from Motorola, and is using a VZW sim.
Of course there's nothing Motorola will do, since it's 2 weeks out of warranty. But I'm hopeful that the hardware is still alright since I can still turn bluetooth on and off. Can someone confirm that this phone's BT and Wifi are on the same chip? I suppose there is no reason not to root it now...
I'd like to try to set the mac address using the above code. Can anyone suggest a way to retrieve the old mac? Thanks...
Not working..
toastgodsupreme said:
Have you tried setting a custom MAC yet?
Had this for my old N5:
Code:
cd /persist
rm -rf bluetooth
mkdir bluetooth
chown bluetooth:system ./bluetooth
chmod 770 ./bluetooth
echo -ne '\xBC\xF5\xAC\x70\xA9\x5F' > ./bluetooth/.macaddr
chown bluetooth:system ./bluetooth/.macaddr
chmod 660 ./bluetooth/.macaddr
rm -rf wifi
mkdir wifi
chown wifi:system ./wifi
chmod 770 ./wifi
echo -ne '\x8c\x3a\xe3\x41\x8d\x79' > ./wifi/.macaddr
chown wifi:system ./wifi/.macaddr
chmod 660 ./wifi/.macaddr
Reboot afterwards. Of course you'll need root.
Some things to keep in mind:
1. Not all MAC addresses worked for me. setting 1234567890 would cause wifi to get stuck at turning on. Some MACs work, some don't. Didn't bother to find out why.
2. The addresses above are for my old N5, you're free to try them if you want. That motherboard is toast.
3. My N5 died due to a wifi/bt chip burn out. Manufacturing defect. Hence my investigation into the issue and whatnot.
Click to expand...
Click to collapse
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
Thanks for all supported here, seems so many people got tge same problem as mine.
I never unlock bootloader on this device, im at 5.1.1 and it happens with my wifi shows wrong mac address so i just tried to ota to 6.0 and the issue is still there? Anybody find the cause pf problem here?
pradipsoman said:
Tried changing the mac id as per this method...Does not work..After reboot still shows the bogus id 02:00:00:00:00:00
Click to expand...
Click to collapse
Did you happen to try setting it to its original mac, or to some other valid broadcom mac? Or did it fail after setting a random mac. I ask because I am about to root my wife's phone just to attempt this same procedure...
hi i asking for some guidance here. Anyone with odin flash file with lollipop please give a link. i have a g870a which originally had Android version: 5.1.1 Baseband version: G870AUCU2COJ3 on it but then someone flashed G870AUCU1ANE4 4.4.2 on the phone and now you can hear the phone starting up but the screen just shows lots of dots in various colors. there is no image just dots to full the screen. so i cant do much with the phone cause i cant see whats going on from the screen. please some assistance will be greatly appreciated.
i tried sideload but i keep getting this error:
C:\>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
59fa9633 sideload
C:\>adb sideload c:\update.zip
loading: 'c:\update.zip'
* failed to write data 'protocol fault (couldn't read status): Invalid argument'
*
i also want to mention that you can hear the phone starting up and i am able to get into recovery and sideload by guessing the options.
Hi everyone.
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
First you will need that apps:
EFS Modded 1.2
EFS
mbns-mi9t.zip can use this or can use this Pixel mbns
OEMLogKit_1.0-1.apk
EngineeringMode.apk
NOTE: ON custom ROM OEM and Enginer mode does not work. See step 5.1 for custom ROM.
1. Enter * # 800 # in the stock dialer, and then click oneplus Logkit - next - Function Switch - next - activate VoLTE switch, VoWifi switch and VT switch.
2. Reboot device.
3. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer
4. Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
5. With your phone connected via USB enter *#801# and check Engineer Mode Toggle switch to ON.
5.1. If you are on custom ROM you activate the enginer mode by entering in adb shell and run the next command:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
5.2. Also if you are on custom rom you can use this method or the PDC one, also not using OEM and engineer, just run command from 5.1 and you should see your phone in PDC.
6. You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
Should return something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This should report back some info if everything is working.
7. Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
8. If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Credits to:
HomerSp
jimmy123322
If you manage to activate VoLTE/VoWiFi using this guide please let us know your Country--Carrier--MBNS that you used.
Proof:
Same method worked fine for me, though I got the information and files from different sources, as I have been looking for some days for a solution. Also, it's possible to set the engineer mode using adb, rather then installing the Engineer apk, by writing in adb shell setprop sys.usb.config diag,adb
I used the Telefonika_UK_Commercial mbn from Pixel 4, so far it seems a lot more stable than the one from OOS (on OOS10 it was continuously switching between VoWiFi/VoLTE every few minutes).
Romania - Digi.Mobil - Pixel's 4 EU\Telefonica\Commercial\UK, if it makes any difference.
Thanks. Worked for me.
Qatar > Ooredoo. Used Telefonica Commercial UK. Both Pixel & Mi9 mbn files worked for me, but ended up using the Pixel file because it is a larger file, so thought it might contain more information.
Some notes:
For Ooredoo, dialing "111" will not work while in VoLTE. Have to be on 3G network. I faced the same issue even in Android 10. On an iPhone or Samsung S20 that has VoLTE enabled from the factory, the phone would automatically switch to 3G when dialing "111".
I used PowerShell Window and I had to "./" to the commands from OP (i.e. used "./EfsTools.exe efsInfo")
I first got "Critical error. The requested resource is in use. " when running the "./EfsTools.exe efsInfo" command. Had to open QPST Configuration > at the top clicked Server > then Stop QPST Server. Then it worked.
I have two questions if anyone can answer,
How to revert to stock if we have to?
Is it possible to find and use mbn files from a Samsung Phone? Specifically S20 FE 5G as it is also using a Qualcomm chipset here and VoLTE works fine from the factory for my carrier.
Please please please someone tell me how to get efs to work outside of oos!
The setprop command doesn't work
vladvlad12 said:
Hi everyone.
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
First you will need that apps:
EFS Modded 1.2
EFS
mbns-mi9t.zip can use this or can use this Pixel mbns
OEMLogKit_1.0-1.apk
EngineeringMode.apk
1. Enter * # 800 # in the stock dialer, and then click oneplus Logkit - next - Function Switch - next - activate VoLTE switch, VoWifi switch and VT switch.
2. Reboot device.
3. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer
4. Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
5. With your phone connected via USB enter *#801# and check Engineer Mode Toggle switch to ON.
6. You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
This should report back some info if everything is working.
7. Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
8. If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Credits to:
HomerSp
jimmy123322
If you manage to activate VoLTE/VoWiFi using this guide please let us know your Country--Carrier--MBNS that you used.
Click to expand...
Click to collapse
Did you finally get VoWiFi working? Which profile worked for you?
dilruk said:
Did you finally get VoWiFi working? Which profile worked for you?
Click to expand...
Click to collapse
Only VoLTE, using india Vodafone. Will try some more mbns later today.
Thanks for help! I find one from pixel that let my VoWiFi works! If anyone need to know which one is Pixel/APAC/Airtel/pixel_Commercial/. I am using Vodafone Romania. VoLTE also works!Also VoWiFi work with Airplane Mode on.
vladvlad12 said:
Only VoLTE, using india Vodafone. Will try some more mbns later today.
Thanks for help! I find one from pixel that let my VoWiFi works! If anyone need to know which one is Pixel/APAC/Airtel/pixel_Commercial/. I am using Vodafone Romania. VoLTE also works!View attachment 5200321View attachment 5200323Also VoWiFi work with Airplane Mode on.View attachment 5200325
Click to expand...
Click to collapse
Thanks man. Working great.
Tried it in oneplus 6t on same network, but strange it is not working. The VoLTE and VoWiFi switch appeared under network->sim, but no VoWiFi. Idk about VoLTE, din no try that one yet.
miffymiffy said:
Please please please someone tell me how to get efs to work outside of oos!
The setprop command doesn't work
Click to expand...
Click to collapse
What setprop? To enable diag? Like the one from *#801#?
vladvlad12 said:
Hi everyone.
Code:
/*
* Your warranty is void. Or vaild, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
First you will need that apps:
EFS Modded 1.2
EFS
mbns-mi9t.zip can use this or can use this Pixel mbns
OEMLogKit_1.0-1.apk
EngineeringMode.apk
1. Enter * # 800 # in the stock dialer, and then click oneplus Logkit - next - Function Switch - next - activate VoLTE switch, VoWifi switch and VT switch.
2. Reboot device.
3. Install Qualcomm QPST Diag port x64 / QPST 2.7.474 software on your computer
4. Unzip EfsTools from above, open up a cmd window and cd to the directory where you extracted it. Depending on how you connect to diag you will need to modify EfsTools.exe.config - if you're connecting via USB you most likely won't have to do anything as it will find the port automatically, unless you have more than one port, in which case you can simply change port from Auto to the COM port of the phone (for example COM13).
5. With your phone connected via USB enter *#801# and check Engineer Mode Toggle switch to ON.
6. You can test the connection by running this in the cmd window:
Code:
EfsTools.exe efsInfo
Should return something like this:
View attachment 5200327
This should report back some info if everything is working.
7. Extract efs.zip from above to the same directory as EfsTools.exe, and make sure the mcfg_autoselect_by_uim file is there. Now simply run this in the cmd window, one line at a time:
Code:
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
If everything worked you should see no error messages.
The mbn directory structure is generally laid out like this: <region>/<carrier>/commerci/<country>/mcfg_sw.mbn. For example, the one for my carrier is eu/h3g/commerci/se/mcfg_sw.mbn. Copy the mcfg_sw.mbn file to the same directory as the EfsTools.exe, then go to the cmd window you opened and type this:
Code:
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
8. If it has worked you should see a bunch of output, but no errors. Try rebooting now, and hopefully after it has booted you will have fully functional VoLTE and VoWiFi.
Credits to:
HomerSp
jimmy123322
If you manage to activate VoLTE/VoWiFi using this guide please let us know your Country--Carrier--MBNS that you used.
Proof:
Click to expand...
Click to collapse
Country Bulgaria--Carrier Vivacom--MBNS Vodafone Germany. Volte and vowifi worked.
vladvlad12 said:
What setprop? To enable diag? Like the one from *#801#?
Click to expand...
Click to collapse
setprop sys.usb.config diag,serial_cdev,rmnet,adb
that is the command that is required to enable the serial port to use PDC, which works fine on custom roms, however it does not allow the com port to work on EFS. Which is what I need. Otherwise its back to OOS to do the commands, wiping and resetting everything back up. Its a PITA.
miffymiffy said:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
that is the command that is required to enable the serial port to use PDC, which works fine on custom roms, however it does not allow the com port to work on EFS. Which is what I need. Otherwise its back to OOS to do the commands, wiping and resetting everything back up. Its a PITA.
Click to expand...
Click to collapse
Try this:
adb reboot ftm
Wait about 20-30 seconds, or if you have sounds in windows till you get the device connected one.
adb shell setprop sys.usb.config diag,adb
You shouldn't need all the modes. Also make sure you have the drivers installed (you should see the ports opened in device manager under com ports).
When finished, do adb reboot to exit ftm.
Just noticed you want to do it through PDC? I'm afraid it looks like that doesn't work anymore, you need to use EfsTools.
morphvale said:
Try this:
adb reboot ftm
Wait about 20-30 seconds, or if you have sounds in windows till you get the device connected one.
adb shell setprop sys.usb.config diag,adb
You shouldn't need all the modes. Also make sure you have the drivers installed (you should see the ports opened in device manager under com ports).
When finished, do adb reboot to exit ftm.
Just noticed you want to do it through PDC? I'm afraid it looks like that doesn't work anymore, you need to use EfsTools.
Click to expand...
Click to collapse
Nah mate, thats exactly what i was after. The setprop command doesnt work on efs on aosp roms. just says bad port, even though its correct. ill try this.
miffymiffy said:
Nah mate, thats exactly what i was after. The setprop command doesnt work on efs on aosp roms. just says bad port, even though its correct. ill try this.
Click to expand...
Click to collapse
But set prop should be executed in adb shell, not efs.
I have extracted the MBNs from OP7 Pro. Hope this will help someone.
dilruk said:
I have extracted the MBNs from OP7 Pro. Hope this will help someone.
Click to expand...
Click to collapse
Thanks!
Hi,
there a chance it works with OP8T?
stale86 said:
Hi,
there a chance it works with OP8T?
Click to expand...
Click to collapse
I think it might, you just need to find the right mbn
vladvlad12 said:
I think it might, you just need to find the right mbn
Click to expand...
Click to collapse
iam currently using the old method,
Updates the modem using QPST,
Choose the profile India vodafone,
And the LTE, Vowifi work great,
But the device returns to the default setting Oversea Profile,
from time to time.
in this guide the default profile is what I choose ?
This is doing exact what QPST is doing, so I think you will have same problem. This guide is for those on oos 11 for whom QPST is not working anymore.
stale86 said:
iam currently using the old method,
Updates the modem using QPST,
Choose the profile India vodafone,
And the LTE, Vowifi work great,
But the device returns to the default setting Oversea Profile,
from time to time.
in this guide the default profile is what I choose ?
Click to expand...
Click to collapse