- Sep 18, 2020
So guys, not so happy days...
Yesterday I was prompted for an update to 61.2.a.0.410, so I decided to do an install via newflasher.
I deleted all .ta files, i deleted all user data .sin so data wouldn't be wiped, and I also went and deleted all three modem related .sin files. Flashing went on ok, but..
Unfortunately the IMS registration won't go through even after multiple attempts with Shizuku and PixelIMS.
Any ideas for future updates?
Okay, I will do so, and I will keep in mind what you said here by the time the next update comes by.Hmm, that's not the way to do it. All you needed was to remove just modem.sin and choose option (when prompted) on newflasher to keep user data.
Can't 100% say for sure that what you did broke IMS and VOLTE but I'm 99% positive it is what caused it. I honestly can't offer any other steps, other than to start at the beginning and go through the bootloader unlock all again.
Jio 5G and volte WiFi calling work fine in India
Which device? Have you downloaded Xperia Drivers from the Sony website?@Yeme I'm not able to get past below step. those 3 xperia drivers are not showing up. please check image below and can you help to fix it.
View attachment 5904243
Device is XQ-CT54 - Sony Xperia 1 IV. I have downloaded the drivers from sony website but dont know to install it on windows 11. Can I post message you @Yeme for further help!Which device? Have you downloaded Xperia Drivers from the Sony website?
I can't help you man, this guide is only for Xperia III's devicesDevice is XQ-CT54 - Sony Xperia 1 IV. I have downloaded the drivers from sony website but dont know to install it on windows 11. Can I post message you @Yeme for further help!
Okay. Just let me know if these drivers are installed correctly.I can't help you man, this guide is only for Xperia III's devices
Yep, they are installed correctly, you nailed it!. Congrats.Okay. Just let me know if these drivers are installed correctly.
View attachment 5904391
Thank you @Yeme .Yep, they are installed correctly, you nailed it!. Congrats.
I think LAHAINA is only for Xperia III's, check with EFS Explorer the device HW_DSDS_LA and see if the folders policyman and modem appear. If they appear, continue with the guide as normal.Thank you @Yeme .
Now, I checked in QPST but LAHAINA not showing up in active phones. any idea what could be the reason.View attachment 5904417
Hi @Yeme I check HW_DSDS_LA and found some files as below in screenshot. Was able to find policyman. Should I go ahead and continue to add mbn profile?.I think LAHAINA is only for Xperia III's, check with EFS Explorer the device HW_DSDS_LA and see if the folders policyman and modem appear. If they appear, continue with the guide as normal.
Hi @Yeme I check HW_DSDS_LA and found some files as below in screenshot. Was able to find policyman. Should I go ahead and continue to add mbn profile?.
View attachment 5904493
View attachment 5904495
hi @anmolkakkar I'm using Sony 1 IV - XQ-CT54 version. Its supports Jio Volte and Wifi calling on android 13. Phone has one physical sim and one e-sim unlike HK/TW versions having both physical sims. Airtel is supporting only volte out of the box without any bootloader unlock changes. I searched the root folder using root explorer. was able to find only Reliance MBN. Airtel MBN is not present and is shown as ROW_Commercial in service engg mode.@shoaib130088 Can you share the mbn file that makes 5G Jio/Airtel work, with the community here? It will help everyone looking for it.
@ralf_waldo If you have it, please do share it here so that we can also benefit from it.
Yesall in all, to make Jio 5G work, we need to load the Reliance mbn file (as shared by @ralf_waldo) above through that highlighted process and then copy this
carrier policy file into the policyman folder. And reboot.
This should make the 5G work, correct? @shoaib130088 @ralf_waldo?
Koi bhi ek trya kro agar nhi hua to phir dusre file daloBro two different files? which one is what?
Quick update: I got volte working simply by flashing modem and OEM from SEA (AS72) firmware. Vowifi is still non- functional though, I'm on vodafone India. Maybe I'll look for a specific MBN to get this up and running.If you are on A13 on 5 II, the procedure should most likely work. Only you can verify if the steps mentioned in this guide actually work for you.
On the part about obtaining the MBN, there are many links to MBN zip files within this thread that can give you the carrier's MBN you are looking for. e.g. if you are looking for Reliance Jio to work, download the mbn zip from within this thread and search for "Reliance" after extracting the multiple files/zips from within that. Load that .mbn file as guided in the steps and most likely it should work for you. You don't need to use any other phone to extract it's MBN file, the files are already attached in previous posts.
Hope this helps.
./EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Of course I forgot to tell you that I achieve this on Android 13, last security patch. Firmware version 61.2.A.0.388.Amazing detailed guide. Thanks for sharing.
Quick question, can all of this be done on Android 13 now? And does it support 45/5G VoLTE/VoWifi on both SIMs?
I haven't upgraded for almost a year now coz everything was working fine on A12 with 4G VoLTE and VoWifi.
Turns out that is not even needed and just me reading too many guides and confusing things.Mmm I don't remember checking settings while patching the file. Leave everything as it is.
Since I am now at the point where I did everything I can't record it anymore, but the guide is actually very straight-forward and specific about things. I suggest just following step-by-step and asking here if something is not clear.Can you post a tutorial video?
For me and beginner
.\fastboot.exe flash boot .\boot_magisk.img
Yeah each time an update is installed it rewrites the modem file, I think you'd be better off installing via newflasher as you could just remove the modem.sin from the install.So, I just updated to firmware 61.2.a.0.396, and it definitely doesn't work anymore.
I think the update went and rewrote the mbn and xml files.