Related
Maybe someone know or test it already.
4g,3g,2g modem: Intel 7262 + Intel 2230 in all version of ZF2
So, if hardware same, it's possible to change firmware TW on WW or US and it will change supported LTE band? Who have already zf2, maybe you can test it?
I would love to be able to get the correct LTE band. I like the phone i'm just not that happy that its not the right band when the sites I used said it would work. It is my own fault but it still sux.
The Samsung galaxy alpha also uses this modem. As seen here:
https://www.ifixit.com/Teardown/Samsung+Galaxy+Alpha+Teardown/29604
The actual sku is different. This leads me to believe the chips are not the same between regions.
Anyone can test it?
If you want to switch on blocked LTE band
BUT: everything is done at your own risk.
Instruction for variant when you have TW(CN) version and wanna convert to WW bands or US bands.
You need root and /system folder with R/W permission, it's possible to do through Root Explorer
Variant 1:
1) Copy file /system/vendor/firmware/telephony/ze550ml_TW_726x.tlv for backup
2) Copy/system/vendor/firmware/telephony/ze550ml_WW_726x.tlv -> /system/vendor/firmware/telephony/ze550ml_TW_726x.tlv (change, press yes if you will be asked ).
3) reload your telephone and check 4G
If in a system asus have checksum file names, than this variant willn't help, and perhaps you will lose any connection, than just copy back file from step 1 and reload telephone.
Now varina 2:
1) Copy file /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml for backup
2) Copy /system/etc/catalog/V1_DSDA_ZE550ML_WW/telephony_config/V1_DSDA_ZE550ML_WW_726x.xml -> /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml (change, press yes if you will be asked ).
3) reload your telephone and check 4G
One more: You can not copy files, you can open /system/etc/catalog/V1_DSDA_ZE550ML_TW/telephony_config/V1_DSDA_ZE550ML_TW_726x.xml in any text editor and change ze550ml_TW_726x.tlv on ze550ml_WW_726x.tlv
original url: 4pda.ru/forum/index.php?showtopic=657946&st=40#entry39697801
@Fenrisar
applause for your super quick copy-paste of my Russian instruction, but i've posted it already here: http://forum.xda-developers.com/zenfone2/general/how-to-change-4g-bands-ze551ml-t3091869
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.
: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...).
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
rexian said:
Just got the phone bootloader unlocked (thanks to Wh1t3Rose for the guide) and now need to add the LTE bands from L24. Settings > About says the model is BND-AL10, however, HCU client says it's BND-L22 so a little confused. Can't find any fw in firmware finder for L22 so assuming AL10 is the right model.
Can I now safely use HuRUpdater to flash BND-L24C567CUSTC567D1B344 (8.0.0.344) FullOTA-MF on this device? Or I am missing some steps like rooting / installing TWRP etc.?
Another question - what TWRP to use with HuRUpdater? Would the first one from here work for 7x?
Thanks for any comments!
Click to expand...
Click to collapse
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
mrmazak said:
If you need to change model bands , it takes more than that.
If you do like that , the model number doesn't change and modem bands also stay the same. You will need to do what is referred to as "re-brand" which changes the oeminfo file , then flash the l24 full ota.
Changing the oeminfo. Makes bootloader lock again. But the same key is supposed to still work.
It can be easy to make brick during re-brand
. You should Study the bnd-hwota-eng script to understand the process.
Click to expand...
Click to collapse
Thanks mrmazak. Is this a viable option of getting L24 bands on AL10?
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
rexian said:
Found the L24 oeminfo here. Is there a way I can backup the oeminfo from my AL10 just in case I brick it
Maybe installing TWRP and taking a full backup is a better idea but can't find a TWRP img for AL10 Naugat :|
Click to expand...
Click to collapse
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
mrmazak said:
I will look at it tonight when I get home.
I had found good hwota tool with the re-brand script in it. I had to translate from russain and add L24 oeminfo but ithas been used successfully.
I will look at that linked oeminfo and compare to the one I put in the hwota tool.
A search on the 7x main page for "bnd hwota- eng" or similar should show the tool like.
If you don't find Ivan upload again.
Click to expand...
Click to collapse
Thanks again, mrmazak. I saw your post in the other thread while searching but wasn't sure if there is more up to date information or an alternate tool.
Is it possible to just add certain bands to a model without removing existing bands? The only bands of interest are LTE 12 and 17 that are missing in this. The person doesn't really care about Oreo or Nougat - as long as it works with AT&T
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
rexian said:
Thanks mrmazak for updating HWTOA. I'll try rebranding AL10 to L24 tomorrow. Don't see a way to just add new bands so rebranding L24 seems to be the only way for now.
BTW, I took a backup of Boot, OEMInfo, System and modem_fw partitions. For some reason backup of Data partition failed after multiple attempts (unable to find partition for path /system and createTarProcess() ended with error 255). Is Data partition important in this case? The phone has no real data or app installed anyway as it's not in use.
Another question - planning to use HWOTA7 since I have Nougat right now but downloaded BND-L24C567CUSTC567D1B344 (8.0.0.344) full OTA - is this ok? I can't find a Nougat version for L24C567.
Click to expand...
Click to collapse
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Klirensxp said:
I flashed from L21C10 to TL10,before that I saved 8 modem files with L21 to him and the emui tweaker from the phone,then I restored it,and I had 4G+,try so.
Click to expand...
Click to collapse
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
mrmazak said:
There is a nougat full it's. It is labeled for Oreo roll-back. But should work for you . It is found as 'bond' intead of 'bnd'. ( Wait, the rebrand script is looking for three files. I will try and adjust the script to not fault out with just two.)
And link is actually in the hwota thread as a downgrade package.
I do reupload most current hwota file yesterday. I found a bug when I did a downgrade. So I proof read through the files again and re-uploaded.
Also added link to bnd-hwota-eng to the guide thread.
Click to expand...
Click to collapse
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
rexian said:
Ok, will wait for the updated script. I downloaded rest of the files.
In the oeminfo folder I see AL10C00 img but not AL10C675. Trying to root the phone to be able to copy custom.bin/oeminfo so that I can go back to stock later. For some reason SuperSU doesn't work... will try Magisk now
Click to expand...
Click to collapse
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
mrmazak said:
I have been looking at some ways to edit the script to make it automatically adjust if there is only 2 update files. And it will be easier to just manually edit the one script before you run it.
Add a "#" to the front of line 332 of hwota.sh.
"HWOTA_BND\HWOTA7_BND-eng\hwota.sh"
Need to just comment out the line with "$TARGET_UPDATE_DATA"
Code:
echo
echo "Copying recovery files, please be patient and wait...."
$ADB push $RECOVERY $RECOVERY_TMP
$ADB push $RECOVERY2 $RECOVERY2_TMP
$ADB shell "dd if=$RECOVERY_TMP of=/dev/block/bootdevice/by-name/recovery bs=1048576"
$ADB shell "dd if=$RECOVERY2_TMP of=/dev/block/bootdevice/by-name/recovery2 bs=1048576"
$ADB shell "echo --update_package=$TARGET_UPDATE > /cache/recovery/command"
#$ADB shell "echo --update_package=$TARGET_UPDATE_DATA >> /cache/recovery/command"
$ADB shell "echo --update_package=$TARGET_UPDATE_HW >> /cache/recovery/command"
$ADB reboot recovery
$ADB kill-server
Click to expand...
Click to collapse
Cool, done commenting #332. Also was able to root and make a copy of custom.bin / oeminfo.
Now, going to run the script :fingers-crossed:
Alright, an update - it went through lot of steps as expected (including installing oeminfo and unlocking the bootloader) but ended up with "software update failed" error on the phone. On command prompt here is the last few lines of the log -
Use the volume buttons to select YES and press the power button
...
(bootloader) The device will reboot and do factory reset...
OKAY [ 11.001s]
finished. total time: 11.001s
Wait for the device to boot into TWRP.
Press Enter to continue...
Wait for the files to load. Neither of which you do not need to press !!!.
Copying is in progress ....
[100%] /data/update/HWOTA/update.zip
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_data_public.zip': No such file or directory
Copying is in progress ....
adb: error: cannot stat 'D:/UX/HCU-Client/HWOTA7_BND-eng//update/update_all_hw.zip': No such file or directory
Copying recovery files, please be patient and wait....
[100%] /tmp/BND_RECOVERY_NoCheck.img
[100%] /tmp/BND_RECOVERY2_NoCheck.img
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.414091 seconds, 85.5MB/s
35+1 records in
35+1 records out
37109760 bytes (35.4MB) copied, 0.508804 seconds, 69.6MB/s
The system update should start automatically.
Press Enter to continue...
Click to expand...
Click to collapse
Error for update_data_public.zip was expected and on close inspection I noticed there was an extra '.' in the name of update_all_hw.zip. It was update_all_hw..zip.
So, fixed it and put the phone in fastboot mode and re-ran update.bat. It installed recovery and asked me to put into TWRP. I tried but it never went to TWRP started installing the previously copied ZIP files. It took a while but after it restarted, it went to straight to Android (YAY!). Went to Settings > About and say the model as BND-L24 and build number System 5.1.0.98(07DV).
So far it seemed everything was fine - then I inserted the FreedomPop SIM (uses AT&T towers), added the fp.com.attz APN and restarted it - AND the same issue, can't see the carriers and 0 bars
The oeminfo was definitely installed as I see a lot more options in "preferred network mode" but selecting Global or LTE or anything else does nothing...
Since I am not able to boot into TWRP, I wonder if that's causing an issue. Every attempt to boot into TWRP goes into a screen showing "installing update" with 5% status. It eventually (after 10 minutes or so) boots into Nougat.
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
rexian said:
Did you do this to rebrand the phone to support other LTE bands? Or just to get OTA updates keeping the same radios? Sounds like latter.
I am trying to get the US radio bands on my AL10 by rebranding it to L24.
Click to expand...
Click to collapse
It’s just that the L21 is always 4G,and on the TL10 it goes to 3G,I switched from L21 to TL10 because of gestures, now I have 4G+ as well as on L21.
rexian said:
Gave up and started from scratch (after installing TWRP img mount manually) and it completed successfully (with expected error for the missing update_data_public.zip). Build number changed to BND-L24C567B150 so both zips were installed yet the problem remains the same - no cellular connectivity and settings > More > Mobile Network > Carrier remains disabled...
Click to expand...
Click to collapse
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
mrmazak said:
Good catch with the renamed file. You did right thing to start over, because that first build number was not correct.
As far as I know this should have changed the radio files (modem).
I will keep looking for other confirmed way to change the selected bands.
Click to expand...
Click to collapse
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
rexian said:
Thanks mrmazak. What could be the reason behind disabled option? Earlier with AL10, I could go inside and see AT&T listed but selecting that would not help as corresponding radios were not enabled in AL10.
Now, even if L24 radios are not properly installed / enabled, I should be able to go inside and see AT&T listed - makes me wonder if all the radios are now disabled.
Is there another way to check what radios are available in a phone by running some app?
Click to expand...
Click to collapse
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
mrmazak said:
Not sure about other ways to check the bands. There are playstore apps that will show what band you are connected to, but have not seen one that shows which ones you can connect to.
side note::: Funkyhuawei (paid service) says of there rebrand guide, that you must flash the new firmware at least 2 times. So maybe take the flash one more time.
Click to expand...
Click to collapse
I tried once more tonight but the same result - no service and carrier disabled.
mrmazak said:
some general questions about your problem.
On about phone screen, what is shown for 'baseband' ?
does the imei # number show?
are you installing sim into slot #1 ? (#2 does not support 4g)
did you verify freedom pop sim is activated? (tested in other device)
Click to expand...
Click to collapse
There are 2 long numbers for the baseband - both start with 21C60B. Yes, both IMEIs show and are the same as before.
Yes, I always used the dedicated SIM slot as I have a micro-SD inserted for backup.
mrmazak said:
edit:
found few posts in some "rebranding" threads, that say what you want to do might not be possible.
They say on the software side it will have drivers for the correct bands. But he hardware may not suppport it.
here:
https://forum.xda-developers.com/showpost.php?p=76462513&postcount=175
Click to expand...
Click to collapse
I am inclining towards this as well - possibly missing hardware
Now, how do I get back to AL10C675 (don't see a Nougat option in FW Finder) and original radio? HWOTA doesn't have C675 as option, it has C00. I do have the original custom.bin and oeminfo but how do I create a zip to install with TWRP?
For anyone searching..
I was facing the "no caller id issue" on VOLTE/VOWifi calls
The solution for me was always this guide.
However, this wasn't a stable solution for A12, as the made changes to the modem config were gone after a reboot and defaulted back to ROW Commericial. My own network wasn’t available in the PDC list as well (NL KPN)..
Then I recently started playing with the firmware flashable img from xiaomifirmwareupdater.com (fw_alioth_miui_ALIOTHGlobal_V13.0.3.0.SKHMIXM.zip in my case).
I had extracted the modem.img , opened it with powerISO and I found that the PDC tool wasn't showing my specific network because my network wasn't listed in one of the txt files in the folder \image\modem_pr\mcfg\configs\mcfg_sw.
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
So there are a lot more (hundreds) configs available than the PDC tool shows!
Not knowing which txt file I needed to change to add my network, I boldly replaced the default ROW commercial mcfg_sw.mbn file (\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial) with the one I found nested.
- Saved the image file.
- Replaced it in the firmware zip.
- Flashed the edited zip file.
- Boot into system
Success!
I now have a working VOLTE/VoWifi after each reboot!
Checking with the PDC tool afterwards. It showed that my own network was automatically chosen.
No root acces needed!
Good luck!
Hi there landgenoot,
Came across your topic. Facing the same issues overhere with KPN on a Mi10tpro.
Can you tell me how you extracted the modem.img from the firmware. I did my research but not way I could find the modem.img file in the firmware (extracted with winrar)
TY
hi there, problem solved. your solution was great and working for me too!
Thank you very much!
I guess it can easily be an universal for Xiaomi Devices
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Miami_T said:
I also tried this method on a Poco F3 device, but it didn't work. I am from EU\Slovenia and my mobile operator is Mobitel. I found the settings in the file structure
\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\Mobitel\Commercial\SI\mcfg_sw.mbn
and copied them to the
\image\modem_pr\mcfg\configs\mcfg_sw\generic\common\ROW\Commercial\mcfg_sw.mbn
in the modem.img file, but I still get an unknown caller ID when using VoLTE.
I also added the path of my carrier settings to the text files (mbn_global.txt, oem_sw.txt, oem_sw_j11.txt and oem_sw_l3a_global.txt) that were missing at
\image\modem_pr\mcfg\configs\mcfg_sw
hoping that would solve my problem, but the caller id didn't work in that case either.
In order to check if the settings for my operator are correct, I also tried the process with the QPST and PDC tools. This time the caller id works, but the process is really complicated, especially with root access in the ArrowOS I'm using and I don't want to do it every time I upgrade.
Click to expand...
Click to collapse
Sorry it didn't work for you. I assume that you properly replacement the edited modem IMG in the firmware zip and flashed the edited firmware?
Perhaps you can also try again using the same config you chose with the PDC tools
I did try I think three times even with different national mobile providers (A1, Telemach), but it didn't worked. For now it is working because I set it up with PDC tool. I guess I will try again on next update of ArrowOS
Do i need to unlock the bootloader to flash the firmware and how do i flash the firmware?
These instructions are for custom roms only. If you have any of the available custom roms installed for Alioth, you already have an unlocked bootloader. The firmware can be applied in recovery.
EldigoR said:
However, the right modem config file (mcfg_sw.mbn) was available, deeply nested in the generic folder.
(\image\modem_pr\mcfg\configs\mcfg_sw\generic\EU\KPN\Commercial\NL).
Click to expand...
Click to collapse
I've been searching high and low for a solution, and this one is so relatively easy.
There is an other way to do this, if you've already a working connection with PDC.
- extract the correct .mbn file from the firmware with your suggestion.
- start the PDC tool
- chose load and then chose the .mbn file
- activate it on the sub0 and sub1
- reboot your phone and check if it still works.
Thanks a lot!!! Because I used the wrong modem config, it reseted itself on reboot. Had to use PDC every time I rebooted my phone. Now with the right profile, it stays active.