First of all Thanks to johndaniel, htcmage, gorEisberg and Forbesii for their amazing work.
Hello, fellow Xperia users like you I had wondered why Sony had to go with this stupid idea of blocking some regions from accessing 5G, if they had played their cards correctly this could have been a huge hit.
Anyway, let's enable 4G+ and 5G
Note: I have tested this on my Xperia 1 III XQ-BC52 with EU firmware, and I have noticed a battery drain using 5G.
Important Note: You don't lose Wide vine if you follow this correctly because I didn't lose mine. BTW I don't take any responsibilities
And yeah you have to do this after every OTA so this is going to be fun.
Prerequisites:
* Xperia 1 III
* Windows Laptop
* Firmware for your device
* USB Cable
Downloading Firmware
Download XperiFirm from https://xperifirm.com/download/xperifirm-v4-6-0/ and Install
Open the XperiFirm and Download the firmware for your device ( check your model number and download the firmware)
Preparing the Device for Rooting
* Back up all the data from your device.
Make sure the device is supported for Bootloader unlock by opening the dialer and enter the code *#*#7378423#*#* and then press Service Info -> Configuration.
If the Bootloader unlock status is Yes, then you’re lucky and continue the rest of the guide.
Visit https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ and Select your device and enter IMEI and get the code.
Enable Developer Options and then Enable OEM Unlocking and USB debugging on your device.
Download Platform tools for Windows using this link
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once it’s in bootloader mode or fastboot mode you will see blue light then type this command on CMD:
fastboot oem unlock 0xYOURKEY
Wait for the reply on cmd and then type
fastboot reboot
Now your device is Unlocked.
Rooting
Open the firmware folder you have downloaded and look for boot.sin file it looks something like boot_X-FLASH-ALL-4BA8.sin with around 96MB size (might look different for other versions and regions)
Download UnSin Exe from https://forum.xda-developers.com/t/tool-unsin-sin-v3-v4-v5-unpacker-v1-13.3128106/ and then drag and drop the boot.sin this will give you boot.img
Rename the boot_X-FLASH-ALL-4BA8.img into boot.img (easier to flash) and then using Magisk Manager to patch it.
Just don’t delete the original boot.img we need that for the re-locking bootloader.
Now copy the magisk_patched.img into the Platform-tools folder and rename it into boot.img
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once in fastboot mode type this command
fastboot flash boot boot.img
Wait for it and then type
fastboot reboot
Open magisk and verify it's rooted.
Enabling 5G
Open CMD and go to the Platform-tools directory and enter the below command:
adb shell
su
setprop persist.usb.eng 1
If the phone, asks for Allow access press Deny.
After that, it should show up 3 Xperia on the device manager and install one by one manually using Qualcomm driver just youtube this part. Use Qualcomm USB diagnostic 9091 or 9081.
Download QPST from https://qpsttool.com/ and install and open EFS Explorer and select LAHAINA if the name is there otherwise try one by one until you see a bunch of folders.
Once all the folders are showing up go to Policyman folder and copy carrier_policy.xml attached in this post and paste it there.
Restart the device.
You should now have the Speed of 5G or 4G+
Don’t stop here.
Time to go back to Stock (Unroot)
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Remember the original boot.img we have before patching copy that file into platform tools and replace it with the patched magisk boot.img
Then type this command:
fastboot flash boot.img
Once that’s done then type this command:
fastboot oem lock
Wait for the response and then type this command:
fastboot reboot
Once that’s done your device should format and bootloader locked and back to stock ROM with 5G.
In case if anyone is facing any issue or have doubts comment down below or contact me on my WhatsApp +97333956356
First comment!
GeramanX said:
First comment!
Click to expand...
Click to collapse
You want now a sticker
alot easier, but i am using another pc .
{
"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"
}
Just curious but would anyone who has done this please type in their phone dialer menu *#*#service#*#* and tell me what there "current modem config" is under the "Software info" menu?
I have managed to get Volte working with Telstra here in Australia but according the above menu it's not using the Telstra MBN file that is loaded on the phone and is instead using "Row Commercial"
Just curious as I think this might be a bug with the menu not showing the correct file or it is something going a bit crazy on my phone. Cheers, Bentree.
Also @arjun_m4 thank you for this nice guide. What changes did you make to the Carrier_Policy.xml file?
Xperia 1iii indian sim volte wifi calling support but Not 5G support
arjun_m4 said:
First of all Thanks to johndaniel, htcmage, gorEisberg and Forbesii for their amazing work.
Hello, fellow Xperia users like you I had wondered why Sony had to go with this stupid idea of blocking some regions from accessing 5G, if they had played their cards correctly this could have been a huge hit.
Anyway, let's enable 4G+ and 5G
Note: I have tested this on my Xperia 1 III XQ-BC52 with EU firmware, and I have noticed a battery drain using 5G.
Important Note: You don't lose Wide vine if you follow this correctly because I didn't lose mine. BTW I don't take any responsibilities
And yeah you have to do this after every OTA so this is going to be fun.
Prerequisites:
* Xperia 1 III
* Windows Laptop
* Firmware for your device
* USB Cable
Downloading Firmware
Download XperiFirm from https://xperifirm.com/download/xperifirm-v4-6-0/ and Install
Open the XperiFirm and Download the firmware for your device ( check your model number and download the firmware)
Preparing the Device for Rooting
* Back up all the data from your device.
Make sure the device is supported for Bootloader unlock by opening the dialer and enter the code *#*#7378423#*#* and then press Service Info -> Configuration.
If the Bootloader unlock status is Yes, then you’re lucky and continue the rest of the guide.
Visit https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/ and Select your device and enter IMEI and get the code.
Enable Developer Options and then Enable OEM Unlocking and USB debugging on your device.
Download Platform tools for Windows using this link
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once it’s in bootloader mode or fastboot mode you will see blue light then type this command on CMD:
fastboot oem unlock 0xYOURKEY
Wait for the reply on cmd and then type
fastboot reboot
Now your device is Unlocked.
Rooting
Open the firmware folder you have downloaded and look for boot.sin file it looks something like boot_X-FLASH-ALL-4BA8.sin with around 96MB size (might look different for other versions and regions)
Download UnSin Exe from https://forum.xda-developers.com/t/tool-unsin-sin-v3-v4-v5-unpacker-v1-13.3128106/ and then drag and drop the boot.sin this will give you boot.img
Rename the boot_X-FLASH-ALL-4BA8.img into boot.img (easier to flash) and then using Magisk Manager to patch it.
Just don’t delete the original boot.img we need that for the re-locking bootloader.
Now copy the magisk_patched.img into the Platform-tools folder and rename it into boot.img
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Once in fastboot mode type this command
fastboot flash boot boot.img
Wait for it and then type
fastboot reboot
Open magisk and verify it's rooted.
Enabling 5G
Open CMD and go to the Platform-tools directory and enter the below command:
adb shell
su
setprop persist.usb.eng 1
If the phone, asks for Allow access press Deny.
After that, it should show up 3 Xperia on the device manager and install one by one manually using Qualcomm driver just youtube this part. Use Qualcomm USB diagnostic 9091 or 9081.
Download QPST from https://qpsttool.com/ and install and open EFS Explorer and select LAHAINA if the name is there otherwise try one by one until you see a bunch of folders.
Once all the folders are showing up go to Policyman folder and copy carrier_policy.xml attached in this post and paste it there.
Restart the device.
You should now have the Speed of 5G or 4G+
Don’t stop here.
Time to go back to Stock (Unroot)
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Remember the original boot.img we have before patching copy that file into platform tools and replace it with the patched magisk boot.img
Then type this command:
fastboot flash boot.img
Once that’s done then type this command:
fastboot oem lock
Wait for the response and then type this command:
fastboot reboot
Once that’s done your device should format and bootloader locked and back to stock ROM with 5G.
In case if anyone is facing any issue or have doubts comment down below or contact me on my WhatsApp +97333956356
Click to expand...
Click to collapse
Hi
Do you have a vídeo, for example in YouTube were can I see steps to do this?
I ask for It becouse I have some doubts about the processing
THX ALOT
There is a wrong comand in the last step.
Right comand is fastboot flash boot boot.img ( two times boot boot)
This is can be a problem with commom user like me.
Time to go back to Stock (Unroot)
Open CMD and go to the Platform-tools directory and enter the below command:
adb reboot bootloader
Remember the original boot.img we have before patching copy that file into platform tools and replace it with the patched magisk boot.img
Then type this command:
fastboot flash boot.img
bentree said:
Just curious but would anyone who has done this please type in their phone dialer menu *#*#service#*#* and tell me what there "current modem config" is under the "Software info" menu?
I have managed to get Volte working with Telstra here in Australia but according the above menu it's not using the Telstra MBN file that is loaded on the phone and is instead using "Row Commercial"
Just curious as I think this might be a bug with the menu not showing the correct file or it is something going a bit crazy on my phone. Cheers, Bentree.
Also @arjun_m4 thank you for this nice guide. What changes did you make to the Carrier_Policy.xml file?
Click to expand...
Click to collapse
Thanks for your post Bentree.
I would be very grateful for your advice as to how to get VOLTE going with Xperia 1 III on Telstra.
I would love to get 5G as well. Has anyone tried this firmware change on a XQ-BC72 and had success in getting 5G in a country where this has been disabled?
rollyk said:
Thanks for your post Bentree.
I would be very grateful for your advice as to how to get VOLTE going with Xperia 1 III on Telstra.
I would love to get 5G as well. Has anyone tried this firmware change on a XQ-BC72 and had success in getting 5G in a country where this has been disabled?
Click to expand...
Click to collapse
I'm at work at the moment but I'm currently using a 1 III with Telstra network (boost mobile sim).I have 5g and volte but no VoWifi. When I get home I'll try and write you up the steps required.
bentree said:
I'm at work at the moment but I'm currently using a 1 III with Telstra network (boost mobile sim).I have 5g and volte but no VoWifi. When I get home I'll try and write you up the steps required.
Click to expand...
Click to collapse
Thanks Bentree, whenever you get a chance. Telstra support have obviously not been helpful nor has Sony Australia. If you have a way of accessing 5G and VOLTE on Xperia 1 iii in Oz that woud be awesome
rollyk said:
Thanks Bentree, whenever you get a chance. Telstra support have obviously not been helpful nor has Sony Australia. If you have a way of accessing 5G and VOLTE on Xperia 1 iii in Oz that woud be awesome
Click to expand...
Click to collapse
Yeah Sony will just straight up tell you that, because they have withdrawn from Oz they can't do nothing. Telstra will just say that they don't support the phone on their network. I'll get to it this weekend. Sunday is my only day off from work so I'll write you up a guide then.
For some reason when i try to copy item file from PC i get an error.
File Copy Error: Carrier_Policy.xml is greater than 2048 bytes. Item File Size Limit is 2048 bytes.
okay so here's my stock file that i can easily transfer between my pc and phone using this method but the moment i try the edited one from the op i get an error about max file size...so far i have tried this with 2 different PC, and also i'm on a custom rom so idk if that's the problem.
Not able to perform this action:
"After that, it should show up 3 Xperia on the device manager and install one by one manually using Qualcomm driver just youtube this part. Use Qualcomm USB diagnostic 9091 or 9081"
Any pointers or exact youtube links?
Related
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
2: Returning to Stock
If for any reason your phone is no longer functioning properly such as a bootloop (the phone is restarting itself over and over), "Can't Load Android System," "Startup Failed", or any such error you can fix this by flashing the stock firmware using fastboot.
I have taken stock firmware version OPW27.113-89 and packaged it with a few extras. XDA Member luiz_neto has provided a modified logo.bin that removes the unlocked bootloader warning during boot. A special thanks to XDA Member lohanbarth for providing the stock firmware. I have included the fastboot file for Windows, Linux and Mac users. Windows users can run the .bat file to execute all the necessary commands. For Linux and Mac users, I have included a bash script. You will need access to a PC and connect your phone via a USB cable.
*Downloads:
Modified Stock Firmware OPW27.113-89: (Download)
MD5: 3a1d984a8a3d0c57fb21931a8004eb27
Instructions:
*On your phone:
2A. With the phone powered off(even if for just a moment between the phone rebooting) hold the Power button and the Volume Down(Vol -) at the same time. You should boot into what is called the bootloader. It should display information on the screen and state "AP Fastboot Flash Mode" in orange lettering.
*On your PC:
2B: Extract the firmware which is in tar.xz container/file extension. Windows user probably need to use Winrar, 7Zip or PeaZip to extract the file.
2C: Using Windows Explorer, navigate to the folder EVERT_OPW27.113-89_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and click on it to open it.
2D: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
2E: You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see. Simply type(or copy and paste) the following command:
Windows:
Code:
flash_rom.bat
For Linux and Mac you need to make the script file executable. It will make the fastboot binary executable for you. From a terminal run these 2 commands one at a time:
Linux:
Code:
chmod a+x flash_rom.sh
./flash_rom.sh
Mac:
Code:
chmod a+x flash_rom_mac.sh
./flash_rom_mac.sh
Your phone should reboot on it's own. If for some reason it doesn't try tapping the enter key on your keyboard or use the volume keys to make sure “Start” is selected on the right side of the phone and pres the power key on the phone. It should successfully boot the stock firmware.
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
carlosgeraldo said:
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
Click to expand...
Click to collapse
Did you try to download the package again?
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Mara-X said:
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Click to expand...
Click to collapse
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
I have never relocked my bootloader so I can't say for sure but this sounds out of the ordinary. Did it boot fine with an unlocked bootloader?
Sent from my Phh-Treble vanilla using Tapatalk
weazie said:
Did you try to download the package again?
Click to expand...
Click to collapse
I found the error: it was in my PC I started a program to fix the registry and after that unzipped the file normally!
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
MrMatnenko said:
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
Click to expand...
Click to collapse
Same problem here. I hate this messages
<bootloader> flash permission denied
friends, any command I give appeared this, someone knows how to solve?
Failed anything I've tried... Can you help @Xplorer4x4 ?
andreym_costa said:
Failed anything I've tried... Can you help @Xplorer4x4 ?
Click to expand...
Click to collapse
Shows the message "Failed Remote ' ' and "Flash permission denied"
andreym_costa said:
Shows the message "Failed Remote ' ' and "Flash permission denied"
Click to expand...
Click to collapse
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
WoKoschekk said:
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
Click to expand...
Click to collapse
I'm trying again... And now seeing this, can you help?
{
"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"
}
andreym_costa said:
I'm trying again... And now seeing this, can you help?
Click to expand...
Click to collapse
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
WoKoschekk said:
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
View attachment 5654883
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
Click to expand...
Click to collapse
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
andreym_costa said:
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
Click to expand...
Click to collapse
No, your bootloader isn't unlocked. The OEM-Unlock toggle would be inactive (greyed out) in case of an unlocked bootloader.
{
"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"
}
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
• ADB and Fastboot on your PC (for example Tiny ADB & Fastboot) [Thread]
•.Stock boot.img of your Device (extract File from Factory Image)
• Magisk Manager [Thread]
• Internet connection
• Bootloader unlocked [Thread]
• Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Tiny ADB & Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Tiny ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Tiny ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
8. Flash the patched_boot.img, type:
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
9. Open Magisk Manager and verify Root
10. Enjoy
K3V1991 said:
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
1. ADB and Fastboot on your PC (for example Minimal ADB and Fastboot) [Thread]
2. Stock boot.img of your Device (extract File from Factory Image)
3. Magisk Manager [Thread]
4. Internet connection
5. Bootloader unlocked [Thread]
6. Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Minimal ADB and Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Minimal ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Minimal ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
7. Flash the patched_boot.img
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
8. Open Magisk Manager and verify Root
9. Enjoy
___
Click to expand...
Click to collapse
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Mohammad Jebreeni said:
I know I can try this method and see what happens and then report back if needed, but I don't think that this is a thing safe enough to test, so I'll ask before I try: is this for any LG G6 version? Does it work on the H870S (Dual SIMs version)?
P.S: I don't think that this version even has the possibility to unlock the bootloader
Also, isn't a phone that has an unlockable bootloader also rootable?
Click to expand...
Click to collapse
Only for H870, H872 & US997
Please file Stock boot.img?
My device: G6 H872 _H87220d
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
CAlbertSM said:
By saying H870, that means any H870 (like one from Central America) or just the same EU H870 that is listed on the LG Developers page?
Click to expand...
Click to collapse
The unlockable G6's
Does this wipe the phone?
EndlessAbyss said:
Does this wipe the phone?
Click to expand...
Click to collapse
Fastboot OEM Unlock will Factory Reset the Phone
K3V1991 said:
Only for H870, H872 & US997
Click to expand...
Click to collapse
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Imran5320xm said:
Will this work on T-Mobile version of LG G6(H872 TM)? Are you sure it will not do any damage to the phone like hard brick?
Click to expand...
Click to collapse
This does not work on H872 period.
You will get
writing 'boot'...
FAILED (remote: unknown command)
Does this work on the H871?
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Could you tell me how did you get the boot.img file? @leonlelion
--Edit--
Nevermind I found it and rooted my device (H870-V30B-EUR) succesfully. If anyone needs it it's inside the ZIP file: https://forum.xda-developers.com/lg-g6/development/rom-lg-h870-eu-30b-rom-t4007979
leonlelion said:
Hi, i did exactly what you explain in your post on my h870 with V30b-EUR and all worked fine. My phone is now rooted an i'm very happy. Thank you very much for your wonderfull work
Click to expand...
Click to collapse
Me too !! :good:
The simplest, best method!
The simplest, best method! The boot.img I got it from this archive: https://drive.google.com/file/d/1Xxoa2KdcoPTPriZL1IZh056J9rQ7NFiV/view?usp=sharing . My phone: H870 with V30b.
Does this work with H872?
I am interested if this will work on my h870s since i am one of the lucky ones who got 'official' bootloader unlock key, and my bootloader is unlocked now. And if it does when i flash this will i be able to safely modify system files.
Thanks a lot! root easy and fast, I used the boot.img file above, fortunately I had an unlocked bootloader
Would anyone know where to find the boot.img for the US997?
Do you have a modem i could just flash with this h873?
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"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"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"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"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?
I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So recently I have been working on flashing mbn files to my phone.
UPDATE:
Everything works fine now. Here's the guide:
FIRST THING FIRST: Data is priceless. Always backup before you modify your phone software.
Disclaimer: Not every carrier in the world support VoLTE or VoWiFi. Please ask your carrier first to get more info if you don't know if they provide support to VoLTE or VoWiFi.
Things you need:
1. PC with windows or bootcamp (virtual machines won't work)
2. An Xperia 1 III with magisk installed (see guide here)
3. A reliable USB-C cable
Software you need:
1. EfsTools (from github)
2. Platform tools (from Google)
3. Qualcomm USB diagnostic port driver
4. QPST (from qpsttool.com)
3. mbn files (extract from your phone)
1. Open command line in the platform tools folder, type
Code:
./adb.exe shell
and press enter, you should see a linux shell on your command line starting with $. Then Type
Code:
su
and a super user window should pop up on your phone screen, after you allowing the permission, the $ should change into #, then type
Code:
setprop persist.usb.eng 1
. If your phone asks "Allow access?", press deny; if it doesn't, go to notification centre, find USB options, and select "No data transfer".
2. Go to your device manage on windows, there should be three "Xperia 1 III"s listed. Choose one, right click, and select "Update driver". In the pop up window, select "Browse my computer" and then "Select one from the available drivers". Find Qualcomm USB diagnostic 9091 and select next. Do the same thing for the rest two. For more details, please check this post and there's a Youtube video demonstration.
3. Open QPST Configurator, check the list and find which COM port corresponds to "LAHAINA". Go to the device manager and disable the rest, ONLY KEEP THE PORT FOR LAHAINA. Quit any QPST tools after this.
4. Open command line in the EfsTools folder, type
Code:
./EfsTools.exe efsInfo
and press enter. No error should occur if you configured correctly, and the COM port in step 3 should be shown.
5. Type
Code:
./EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
and press enter. There is no expected output so that if there's no error message, you are good.
6. Select the mbn file from the mbn folder. Find the mbn file for your carrier. If you're using a secondary operator, please use the mbn file for the main operator (e.g. Koodo -> use Telus mbn). Copy the mcfg_sw.mbn to the root of the EfsTools folder, then type
Code:
./EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
and press enter.
7. After the command line done it's magic, reboot your phone. Type
Code:
*#*#4636#*#*
in the phone original dialler. Select Phone Information, press the dots at the upper-right corner and select IMS Status, you can check if the IMS status is registered.
Now, you can enjoy VoLTE, VoWiFi, and even 5G (depends on your carrier's support). If you don't see VoLTE or VoWiFi toggle in your phone settings, try install VoEnabler in magisk or run these in adb shell:
Code:
setprop persist.vendor.dbg.ims_volte_enable 1
setprop persist.vendor.dbg.volte_avail_ovr 1
setprop persist.vendor.dbg.vt_avail_ovr 1
setprop persist.vendor.dbg.wfc_avail_ovr 1
Sorry for the late posting. I've been finding mbn files for other carriers but it seems there's no specific carrier's mbn files available on Snapdragon 888 (or I haven't found one). I'll update if there's any progress.
{
"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"
}
IMS Status when Wifi is disconnected and connected.
Additional link: Buy me a coffee : )
Interested in the progress of this...if I can get WiFi Calling i would prefer that over LTE calling for when I go to my Sister's Ranch where there's no signal what so ever...
I'm very interested in this, I've been looking for a way to get TMO Wi-Fi calling working on this phone for a while now.
My phone just died today. I’m not sure if the mbn file caused that. I won’t post the guide until I figure it out :-(
Forbesii said:
My phone just died today. I’m not sure if the mbn file caused that. I won’t post the guide until I figure it out :-(
Click to expand...
Click to collapse
Damn fam, hope it works out...i just cross flashed to the US rom from SEA cause I'm on Metro PCS but my modem got ****ed.....so no calling and network is constantly disconnecting
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
thatguy222 said:
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
Click to expand...
Click to collapse
Hmmm I will flash the binaries and see what happens if nothing changes I'll have to get back to Sea
thatguy222 said:
I have the SEA version in the US on T-Mobile. I flashed Ponce's Pixel Experienc GSI and Sony's binaries (no idea if this was necessary) and I have VoLTE and VoWiFi.
Click to expand...
Click to collapse
how did you flash the Binaries?
Delete
Ainz_Ooal_Gown said:
how did you flash the Binaries?
Click to expand...
Click to collapse
fastboot flash oem filename.img
Ainz_Ooal_Gown said:
Hmmm I will flash the binaries and see what happens if nothing changes I'll have to get back to Sea
Click to expand...
Click to collapse
Where might one get these binaries from?
@Forbesii Thanks for starting this thread. I am struggling with the same for my Xperia 5 III. Really Really looking forward to your Complete step-by-step guide and see how I can do this for my xperia as well. Thanks in advance.
Ndlelex said:
Where might one get these binaries from?
Click to expand...
Click to collapse
Sony's website
The guide is done guys. I'm still looking for methods to get mbn files not in the sony firmware.
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
misquia said:
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
Click to expand...
Click to collapse
Yes. I am stuck on the same step. It is returning the below error:
Critical error. Could not find file 'E:\Sony Xperia 5 III\EfsTools-0.14\mcfg_autoselect_by_uim'.
@Forbesii Could you please help/guide on this?
Ignored this step and it still works. The VoLTE and VoWifi both are working now (for Reliance Jio network in India). AMAZING article!
Definitely save it for future.
@Forbesii - On a side note: I am trying to add Airtel mbn (India carrier) file to my Xperia 5 III but it simply doesn't work. Neither VoLTE nor VoWifi. Are there any secondary steps/different command to copy this for SIM 2?
misquia said:
Thanks for the update on the guide. I believe step 5 is missing a part. The mcfg_autoselect_by_uim file is not in the EFSTools download on Github.
Click to expand...
Click to collapse
Thanks for your report, I‘ll update.
anmolkakkar said:
Ignored this step and it still works. The VoLTE and VoWifi both are working now (for Reliance Jio network in India). AMAZING article!
Definitely save it for future.
@Forbesii - On a side note: I am trying to add Airtel mbn (India carrier) file to my Xperia 5 III but it simply doesn't work. Neither VoLTE nor VoWifi. Are there any secondary steps/different command to copy this for SIM 2?
Click to expand...
Click to collapse
I haven’t tested on SIM 2. The second sim at least on Xperia 1 III is not correctly recognized by EFSTools. I might check other methods for the second SIM slot.
Thanks. Will wait to hear back from you.