Database Info

Carrier Unlocking Sprints Photon Q

Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one

Morecrabs said:
Ok, b4 I get 15 people Pointing me to an irrelevant Thread Not related to this Device , Directing someone to a thread where they arent Interested in the device supported in this forum doesnt provide answers lets discuss In detail carrier unlocking this device
1. Can this be accomplished by Flashing a new Radio Firmware? if so does one exist?
2. if this can be accomplished VIA RadioComm Has anyone dabbled in the MPQ Firmware Specificly for US carriers?
3. there are No threads specifically Covering this topic pertaining to this device and Instead of redirecting everyone Lets start one
Click to expand...
Click to collapse
1. No
2. Yes
You need to be on stock ics firmware for the NV edit to succeed and stick.
Use Android 4.0.4 Blur_Version.77.8.14.XT897.Sprint.en.US - http://sbf.droid-developers.org/phone.php?device=3
If you're downgrading from jellybean, you have to remove the line with flash gpt_main0.bin from the xml file, otherwise the flashing via rsdlite will fail.
Code:
[STRIKE]<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />[/STRIKE]
The firmware thread is here: http://forum.xda-developers.com/showthread.php?t=2095536
Then you can follow this (RadioComm):
http://forum.xda-developers.com/showthread.php?t=2166542
or this (CDMA WS) guide:
http://forum.xda-developers.com/showthread.php?t=2386871
After it's done, you should flash the stock Android 4.1.2 via rsdlite, then install CM10.2 (or any other custom ROM) again.

soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?

Morecrabs said:
soo i have reason to believe this device I bought is actually a developer Model under my developer Options it has a development device ID d7vk-gus7-rvcl-s does that mean this unit is already carrier unlocked and i can simply skip the Radio comm steps? Im having a few radio Comm issues that are making me alil squimish it keeps telling me its not loading the card driver, because of a 64/32 bit difference and it tells me that it wont be able to properly enumerate values
any radiocomm setup suggestions?
Click to expand...
Click to collapse
That development ID is simply for identifying your device under debugging circumstances like ADB, every device has them. Also, flashing another ROM changes this value.
Sent from Google Nexus 4 @ CM11

ok so that was a dumb decision to come to, but its not something id ever seen on any of my other android devices, Droid 1,2,4 samsung captivate glide, so i figured it was related to the developer Models
Do I need to run my copy of radio Comm on a 32 bit machine to accomplish this hacking?
my 64 bit machines seem to have driver related issues with the software

was wondering if anyone could help me setup the drivers, I keep getting errors with Radio comm and cdma workshop, and it all boils down to driver issues, with cdma workshop i cant get the QC port setup because IM missing a driver, and with radio comm, I cant get it to communicate properly with the phone once i boot into fastboot any help suggestions? ive installed the moto drivers and setup on a PC with a 32 bit version of win7 starter to allow radio comm to setup properly
In radio comm it will ID the phone as xt897 and i can get software version if its booted into OS, but it will do nothing else

Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http://bork.cs.fau.de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
Code:
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https://github.com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
EDIT2: This is now included as "unlock-us-gsm" in CM12.0 and up on XT897, XT907 and XT926. To use it run "unlock-us-gsm" in a root shell:
Code:
[email protected]_c:/ # unlock-us-gsm
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Reading value of NV-item 8322...
GSM locked in the US: 1
Setting value of NV-item 8322 to 0...
Reading value of NV-item 8322...
GSM locked in the US: 0
Setting logging_mode to usb...
Regards,
Michael

stargo said:
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer
Click to expand...
Click to collapse
Excellent! I picked a good day to try to figure out how to do this, I was making notes of all the various steps (install ics on phone, use radiocomm on pc, install jb on phone, then cm on phone) when I got to this post and realized I won't need to do any of that, thanks much!

Terminal Emulator Question
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
download the binary: http //bork cs fau de/~michael/photonq/xt897-fix-usa
copy the binary to /data/local/tmp/
make it executable (adb or terminal): chmod 755 /data/local/tmp/xt897-fix-usa
run the binary (adb or terminal):
[CODE
[email protected]_c:/ $ su
[email protected]_c:/ # /data/local/tmp/xt897-fix-usa
Setting logging_mode to internal...
Creating /dev/diag_tty...
Opened diag...
Getting value of NV-item 8322...
GSM outside USA only: 1
Setting value of NV-item 8322 to 0...
Getting value of NV-item 8322...
GSM outside USA only: 0
Setting logging_mode to usb...
[/CODE]
If you want to reinstate the lock, you can run: /data/local/tmp/xt897-fix-usa lock
You can find the source-code here: https //github com/stargo/xt897-fix-usa
EDIT: Works fine on stock rooted JB, too, and sticks after a reboot.
Regards,
Michael
Click to expand...
Click to collapse
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.

DroidRazrMv said:
I'm trying out this method on my xt897 (Razr M) and Im up to the point where I need to run the binary but I'm not sure how to enter multiple lines into the terminal to run that last step, I've tried searching around and found nothing, any help would be much appreciated.
Click to expand...
Click to collapse
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.

arrrghhh said:
Just FYI, RAZR M is xt907.
Also, I'm not sure what you mean - just run the script/binary from the shell. "su" is one line - gives you root access. The next line just runs the binary, "/data/local/tmp/xt897-fix-usa"
Good luck.
Click to expand...
Click to collapse
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.

DroidRazrMv said:
Ah whoops my mistake, thank you, yeah I definitely meant xt907, I typed that in during my lunch break so I was somewhat rushed. Anywho I meant to try it out according to kabaldan's post on http://forum.xda-developers.com/showthread.php?t=2166542&page=87.
So I'm going to test it out momentarily to see if I can run it on the xt907. Thanks again for your help, I was just somewhat confused about the terminal commands.
Click to expand...
Click to collapse
Still confused as to where you're having issues - we are both talking about the same post. If you look, kabaldan's post redirects to the one I am referencing....

So once these steps are used to unlock the phone, which carriers can be used and how does flashing of carrier info occur?

Just want to say thanks again Michael. I just got my new Photon Q back from having sim card slot installed, ran your program and it worked perfectly on 21OCT2014 CM nightly.
I did also change a couple settings in the phone menu too, cuz I put an AT&T sim card in it, but sprint kept calling me to activate. Seems to be working well now, but not sure I understand everything, does this seem right - in regular CM11 settings menu under Mobile network settings, I set Preferred network type to "GSM/WCDMA Auto".
stargo said:
Hi,
I have written a small application which can be run on the phone and which removes the US carrier lock by sending the NV-commands to the diag-interface directly without the need for an external computer. I did this because the other method did not really work reliable for me (probably because I'm using a virtualized windows-installation).
This program works on the CM-11 builds. I have not tested stock, it may not contain the necessary diag_tty-support in the kernel.
Click to expand...
Click to collapse

VoLTE - i9505 International for Jio - Easy way.

I am not a developer but a HW guy.
This applies only to i9505 international version with Qualcomm processor as tested.
Please note that whoever tries the following, upon failure and/or ending up with bricked phone(s), incurring any loss, implied or direct, resulting from the application of what is described in this post, including but not limited to time, warranty, update from Samsung including security updates, resources, financial or otherwise,etc., does not point a finger in my direction but, does so at his/her own risk.
(Hope I scared a few).
The unit that I used originally had XXUHPK2 - XST firmware.
Whatever given below are personally experienced after quite a bit of searching, testing and few near misses including SIM not being detected or infinite loops when searching for network to register due to my own experimentation with Modem and NON-HLOS files.
But I never once lost my IMEI as the method is fairly straightforward. Always God "ODIN" is there to the rescue.
This applies to those who do not want an "always on" Jio4GVoice app and prefer to stay with stock recovery. Of course custom recovery can always be installed.
I have used PI1_VOLTE_JIO FW available on this forum but had faced few issues related to calling out at times, more so when I travel long distance. If I stay put at certain places it always worked.
Now to the works:
1. Using ODIN install I9505XXUPOL1_I9505PHNPOL1_PHN FW. - Search to download FW.
Nordic version of FW with PI1 modem "may" be used but I found network search for registering yields less number of networks. I have not tried using the Nordic FW.
2. Root the device using CF-Auto-Root.
3. Search for "Volte fix.zip" and download. Easiest way to get links to download is YouTube. In the zip file I used all files have 07-11-2016 as creation date. I found VoLTEFiles zip too with the same dates but did not try it so far.
4. Watch the YouTube, say, at "watch?v=MlkaziK6AkY" or any other relevant VoLTE zip file installation video to get the gist of the method before attempting.
5. The zip contains an Apks folder and a Files folder. Extract APK, csc folder, CSCVersion.txt and SW_Confgiuration.xml to a known folder preferably in ext-sd if available.
6. Install root explorer. It is under extracted Apks folder. Allow for installation of app from unknown sources.
7. Open Root Explorer browse to /system directory. Rename existing csc folder, CscVersion.txt and SW_Configuration.xml with some leading characters as fall back. The csc folder and the files can optionally be deleted as well.
Root Explorer will require the patition to be mounted as RW saying it is Read Only. Say OK to proceed.
8. Copy and paste the above folder and files obtained from zip to /system.
9. Change permissions via Root Explorer as below:
Touch the folder or file under Root Explorer. Once selected touch 3 dots on top right and select permissions. Given numbers can be directly entered using Octal button.
csc folder - 755 octal
CscVersion.txt - 644 octal
SW_Configuration.xml - 644 octal
10. Exit Root Explorer and Reboot. And wait patiently for a while until the two way sign appears on status bar. It really takes a while.
Call Settings - "Outgoing voice call settings" automatically shows "Use VoLTE when available".
Factory reset does not restore VoLTE icon on status bar and calling is not possible as well. Wait for a while for the phone to complete all processes after setting up. Reboot to get VoLTE back.
It seems to take a while and the Sammy phone will show a report being sent when connected to WiFi... to inform you later when you select "Software Update" that the phone has modified in an un-authorized way, etc.
Calling and messaging works even with WiFi ON.
I have not provided any link as the credit should go where it belongs.
See screenshots in the attached thumbnails.
ODIN Version used 3.12.7
CF-Auto-Root available on this forum.
And most importantly thanks to the developer who created the VoLTE fix files. And a special thanks to @dhiru1602 with his PI1-VOLTE-JIO ROM as it was instrumental in making me search and test.

Does this work on other S4 not for JIO and on other networks?

treysis said:
Does this work on other S4 not for JIO and on other networks?
Click to expand...
Click to collapse
Sorry for the belated reply. I was using it on Jio only as no other nw providers were offering VoLTE at that time. Now the unit is with someone else in another country. I learnt VoLTE is available in that country and will request to get it checked. Will revert with results.

hey, no problem and thanks for the help! Have you heard back from your friend yet?

treysis said:
hey, no problem and thanks for the help! Have you heard back from your friend yet?
Click to expand...
Click to collapse
Yes and a No - On one network it does not show the icon. He is not sure if the ISP actually implemented VoLTE though announced last year. On the other he has not tested as yet. Says needs to get the 4G SIM. Will wait for some more time and revert again.

Ok. I know for sure that my network and my SIM support VoLTE, cause I am using it on another Samsung handset and it's working fine. But on the S4 no luck yet.

Btw. I just put a Malaysian SIM and this enabled VoWiFi in the settings. But couldn't try it as the card is not fully active anymore.

[h910] rooted Oreo stock-based - get fingerprints AND radio working (if one isnt)

Hello everyone, I'm a total noob but I solved a problem which I couldn't find the answer to, so I thought I'd share. Please take care following my noob advice, I'm not responsible for anything which goes wrong with your phone (and if it gets complex, I probably don't have the skills to help)!!
What was my problem?
When I went from Nougat to Oreo, my radio broke (no cell reception). However I had the files from LGUP, so I could flash "fsg" "modem" "modemst1" and "modemst2" in fastboot (as explained here) which did indeed fix my modem problem, giving me back radio and data. However, this also made the fingerprint scanner disappear from my phone's settings menu. As far as I could tell, this wasn't a problem related to encryption (as discussed in AO ROM thread a lot, which is what I'm now running), rather 'twas a problem with the firmware! So I was loving Alpha Omega, but left without fingerprint scanner since radio isn't really optional on a phone.
Solution?
Please remember, I'm a noob and have only done this for my own phone, a h910, I don't know if i will work for you or on other models!!
Basically, I mish-mashed the two modem files from Oreo and Nougat, to get both things working!
Steps I took:
1) Use Linux - I couldn't get the files to open properly in windows, and didn't find a way to write to the image files.
2) Find a stock "modem.img" file from Oreo (i searched on google "stock oreo h910 modem and it came straight up) - I think I am too new on this forum to post outside links so you'll have to search for it.
3) Find a stock modem file from nougat (I used my original LGUP dump file from nougat, renamed to .img) I'm not sure if it is important that this came from your phone or not, if you followed all the instructions on the dirtysanta root guide, you'll have this as part of your LGUP backup.
NOTE: both of these files were 86 Mb (helped me feel confident I'd found the right thing on google)
4) Create backup copies of both, and append ".img" to your LGUP "modem" file. Call the backup of your OREO modem (the one you got off of google) "MyModem.img", just to keep it clear for later.
5) Mount the NOUGAT img first in a terminal (might have to make a mount point first), for me this was like this:
Code:
sudo mkdir /mnt/modemfiles
mount -o loop /path/to/your/nougat-modem-file.img /mnt/modemfiles
You obviously have to put the file path to where you saved your NOUGAT modem image - the one from LGUP!
6) You should now be able to see the nougat modem .img mounted as a disk in "places" on your file explorer. Go there, and copy the contents into a new folder somewhere easy to find (make a folder on your desktop called NougatModem.) There are two folders iniside, one called "image" and one called "verinfo".
7) Now you can un-mount, as we have what we need from it, easiest to do by just right-clicking it in file explorer and select unmount.
8) Next we will mount the image which will become your new (hopefully working!) modem, but it has to be writeable, so using the same mount point we would do
Code:
sudo mount -o loop,rw /path/to/MyModem.img /mnt/modemfiles
Remember that "MyModem.img" should be your backup OREO image - where all the firmware works but you don't get radio.
9) Now basically comes replacing a few files in the OREO modem (which we have mounted) with ones from your original NOUGAT backup (which are in that folder on your desktop). I couldn't remember if cp command replaced things with the same name, so I used rm to remove files, and then cp to replace them once they were gone.
a) first it is the folder called modem_pr, inside image
Code:
sudo rm -R /mnt/modemfiles/image/modem_pr/
b)next were all the files in the image directory which were modem.SOMETHING
Code:
sudo rm /mnt/modemfiles/image/modem.*
10) Finally we have to replace those files and the folder with the same things from our NOUGAT folder which is on our desktop, using the copy command. I will put the commands as if you did name that folder NougatModem
a) so first the folder which we removed
Code:
sudo cp -r ~/Desktop/NougatModem/image/modem_pr/ /mnt/modemfiles/image/
b) now all the files again, using the wildcard for the different extensions
Code:
sudo cp ~/Desktop/NougatModem/image/modem.* /mnt/modemfiles/image/
So if all went to plan, you now have an image (which you can unmount), called MyModem.img, which you can flash in fastboot to the modem parition (fastboot flash modem /path/to/MyModem.img) and if it works for you like it did for me, you have cell reception, data (after putting in APN if it's needed) and fingerprint scanner all working on OREO. Again, I'm on Alpha Omega, loving the rom and now going to go play a bit.
I've not been on the forum long, but have just gained a HUGE insight into how much time people put into making guides and helping others learn (this has taken me ages haha). Thanks to everyone for your hard work and community spirit, please let me know if this works for you or if it provides any interesting insight as I really did it blind (I had no idea if it would work, and was just making some slightly educated guesses - I got lucky!). Also, if the instructions are hard to follow and you have a hint, I'm happy to edit them to make them clearer.
ENJOY!!
PS - I know the linux commands could be better haha, using more than one mount point too might have been easier, but I figured that I'd just keep it exactly the same as how I did it since I'm a noob and would be more likely to screw something up in the instructions, if I changed it without trying at the same time!
EDIT: I could also upload my "patched" modem image, but not sure if it will work for other people's phones, or if it has "personal" or unique info in it (basically if it would be safe to do so) - If someone who knows tells me it'd be good to go, I'm happy to share it if it would save people from having to go through the whole process. I guess I hope posting all this will be a learning thing for others too Gotta have some justification haha!!

You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.

ezzony said:
You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.
Click to expand...
Click to collapse
Thank you for the commendation haha! What a mission!
So I'm guessing you flashed a different version's KDZ?? As far as I'm aware from lots of reading here on xda, there are no KDZ files for the h910. For me the kdz from h915 worked perfectly for example, apart from data. And that was the story with a few things I flashed, KDZ or ZIPs, they would break data, I'd flash the modem, and that would break the fingerprint scanner. Hence this long-winded solution lol.
If you have an original h910 kdz that people don't know about that'd be interesting in itself!!

No, I flashed a H910 ZIP that someone kindly uploaded here somewhere. Then I flashed back the modem from a Verizon kdz.

You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.

Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.

Vortell said:
Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.
Click to expand...
Click to collapse
So should I flash the whole ROM or just the modem of us996 to have both working?

DesrtSailor said:
You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.
Click to expand...
Click to collapse
Just wanted to say that made my day when I read that the original post had helped you out Cheers for letting me know

Awesome!! Thanks for this. Where did you get the idea of what files to change? Just curious.
I am still tinkering. I have an LGUP dump from:
ATT Stock
A-O Nougat install
A-O Oreo install
I was mix and matching the modem files with various modemst1 and modemst2 files. I did this because it seemed that I got better signal strength with the A-O Nougat install... but I got the kernel panic/modem crash whenever I lost signal on the phone. But with this hand made modem file - no crash. But now I am going to continue mix/match and see what crashes and what gives the best signal strength.
Anyway thanks a bunch!!

Please give me the patched modem file, please send it to [email protected]

I would root then try activity launcher or some sort if hidden menu launcher to get band menu. Alternatively get Network signal guru and lock bands. That how i did it in los 17.1 not sure if it would work on stock. I went from hspa to lte doing it in h915(it's a Canadian h910). I even crossflashed to us996 and left it that way. Says it even says band 66 was unlocked in the app but it has not been tested yet. Either way I got band 4 and 12 once I did this.

[GUIDE] Enabling LTE on China Telecom (and others) on Pixel 3 XL (Android 10)

Being a huge fan of the Pixel series and living in China is not easy. Just upgraded my XL to 3 XL and naturally I had to enable the LTE to work in China. Regardless what you may see on the Chinese forums (gfan), all the files you need are already present on the phone.
Files you need:
1) The ADB bridge for Windows
2) The most recent factory image
3) Magisk Manager
4) Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (Magisk Manager module) - Github direct: https://github.com/wangdaning/Chinese-Carrier-Pixel-3-xl-LTE-VoLTE-Enabler (big thank you to wangdaning for allowing me to publish it.) Also attached as a zip file to this post.
If you don't understand what these files are for or where to find them, perhaps you should ask a friend to help you. Flashing anything wrong could result in an expensive brick. Always backup your data, never blindly trust a post, and do your research. This post is in good faith and I am not liable for your actions.
Now, I don't have any of the variants of 3 (Pixel 3, 3a, 3a XL) but I would assume it would work in a similar fashion; however, see above and do your research. Check file structures, read some posts, backup data, etc. If someone does try it, please report both success and failure to build the knowledge.
1) We need to ensure our phone has an unlocked bootloader. If your bootloader is locked, you WILL lose all your data. Ensure you backup everything you want to keep. There is no getting around this step. We need to be a developer first. Go to Setting->About Phone->Build number (tap it until it says you are a developer). Then go to System-> Developer options -> OEM unlocking: turn it on. Next we need to reboot to the bootloader by resetting the phone and hold the down volume key as it reboots. In the bootloader, first use the volume keys to find and select the unlock the bootloader command with the power key. Then, we need to send the following command:
Code:
fastboot flashing unlock
You will receive a wipe and security warning. Accept and reboot the phone. It will wipe and reset your phone to factory.
2) I started from a stock image (May update; QQ2A.200501.001.B2). I suggest you start from there.
3) While we have the May update in front of us, we need to extract the boot.img so it can be patched to root the phone. TWRP doesn't support us at the time of writing on Android 10. (Hope that new baby is healthy!) The boot image can be found in the zip image-crosshatch-*release code*.zip/boot.img. Transfer this boot.img to the phone to be modded to enable root.
4) Next the phone needs to be rooted. You need to download the most recent version of Magisk Manager. Once installed, open up Magisk Manager. It will report no Magisk and that's ok, we are installing it now.
5) Tap install on Magisk and it will ask if you want to install, so install. Then you need to select the method. We will choose "Select and patch a file." Tell it where you saved your boot.img and it will patch it to allow us to root the phone. The output file we need is called magisk_patched.img is on the phone. Move it back to your directory with your ADB bridge.
6) Next we need to flash this patched boot file to our phone to complete the rooting process. Reboot to the bootloader and send the two commands:
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Reboot the phone and congrats, you are rooted with an unlocked bootloader.
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
8) Download the LTE_enabler from Github or the zip file here. Open Magisk Manager and open the menu -> Modules -> "Yellow Plus" to add. Point it to the zip file.
9) Reboot and enjoy using your phone as intended.
I tried to be as detailed as I could but not be over verbose either. If any step is unclear, there are more detailed guides on this forum concerning bootloader unlocking and Magisk rooting on Android 10. As a bonus tip, does the "x" showing no data bother you and stop some services from working? If so, this can be fixed by re-pointing your captive portal to something inside the firewall. This can be accomplished with one line of code:
Code:
adb shell "settings put global captive_portal_https_url https://developers.google.cn/generate_204"
Enjoy and if you have questions about Pixel and China, feel free to post them. Support right to repair!

I downloaded the zip file but it tells me it's not a module.

jifengSherry said:
I downloaded the zip file but it tells me it's not a module.
Click to expand...
Click to collapse
Could use more details, otherwise it is hard to help. It definitely is a module and installs fine. Something else is going on.

is this for china only? I have a Canadian 3 XL and moved to Bucharest, need to enable VOLTE on Orange Romania. I'm also on Android 11

It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?

wangdaning said:
It should work, but you would have to slightly modify the files. Instead of pointing to the Chinese carrier modem file you would want to point to the orange Romania file. I looked and there is an mbn file for orange Romania, it is just not included in the mbn_sw.txt. Then again, have you made sure Orange has activated VOLTE for your device?
Click to expand...
Click to collapse
I contacted Orange and they say VOLTE should be working, that the issue is my device not being compatible with their network. I also bought a Samsung watch 3 with LTE and can't activate LTE through my phone, i assume it's due to the same issue.
I'll follow your guide and report back.
Should be no issue if i am using Android 11 instead of 10 right?

Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
7) To prepare for the install of the mock files that will point to the files on the phone, we need to delete a few checking files. Using your file explorer of choice that can gain root access delete the following:
/data/vendor/modem_fdr/fdr_check
everything in /data/vendor/radio/ (make the target folder empty)
Click to expand...
Click to collapse
If that does not work then you need to modify the module to include the romania mbn.

wangdaning said:
Should be fine, you just need to make sure that you modify the mbn_sw.txt file to include the location of the Orange Romania mbn file. You might just try this first:
If that does not work then you need to modify the module to include the romania mbn.
Click to expand...
Click to collapse
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!

angeluszero said:
Dude i love you! worked perfectly. I followed the guide to root Pixel 3 on Android 11 and then your steps, didn't modify anything and now i have VOLTE enabled!
thank you so much!
Click to expand...
Click to collapse
ok i spoke too fast, while VOLTE is enabled now in the settings, when i make a call, it switches to H+ which means its not using VOLTE. any idea? I modified the .txt file to include the location of the romania .mbn file, i modified the file directly on the phone though, after installing the module with magisk manager

Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.

wangdaning said:
Not sure, to many variables at play. I mean it could be that orange Romania only has VoLTE in certain areas/cases. Try using *#*#4636#*#* and phone information, see what it says.
Click to expand...
Click to collapse
I did that, both VOLTE and Wifi calling say provisioned. I guess it might be something on Orange's end.
I saw a reddit post for a Pixel 3 having the same issue and the carrier ended up doing something on their side.

Confirmed working on Pixel 3 w/ Android 11!

Can this patch work on Pixel 4 as well? Thank you

duffercn said:
Can this patch work on Pixel 4 as well? Thank you
Click to expand...
Click to collapse
You would have to find the location of the files on the Pixel 4 as I am not sure where they are. Then modify the module to point to the correct location.

VOLTE Success, Activation without Firmware Replacement (Sony Mobile withdrawal area)

I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.

Wow! Well done

Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?

Firmware File Location
htcmage said:
I wrote the method in 1 II for your reference.
The Qualcomm Diagnostic Port command in Xperia 1 is as follows.
(setprop sys.usb.config rndis,eng_mode,adb)
And use the EFSTOols.exe program.
It's easier than I mk2.
Screenshot is
1 and 1 MK2
Hello Xperia users! In the meantime, I finally solved the VOLTE problem! I approached Qualcomm's diagnostic port-active-efsExplorer and solved the problem by inserting a VOLTE profile from my carrier
Sorry, this is Korea and I am Korean.
However, I will write down the method in English.
Unlike previous 1&5, Qualcomm's diagnostic port cannot be opened.
opening command
I don't even know. I don't think so.
So it's a little different from before.
I tried to force it open.
debugging connection
Open the Command Proposal window.
adb shell input
su input
Do you want to allow shell on your phone?
prompt acceptance of permission
Then the $ shape changes to #.
Now
setprop persist.usb.eng 1
Copy paste entry. Please enter
And you're gonna be out there during tethering.
In My Computer Item
View Device Manager.
Please turn debugging back on.
Of course, no access.
If you turn on debugging again,
I've already set it up, so it looks like that.
Among them, there is a product model named XQ-AT52.
There are four yellow exclamation points in total.
Manually update driver Press [port] to list the manufacturers
It's called Qualcomm hs-usb-diagh and 9091. with this
I need a manual update. gogo
Now run the EFS Express.
Press 0 on the ROW and OK.
(ROW or SF_Default)
Oh, it takes a long time. I thought it stopped.
It opens if you stay still. LOL
It's open. How nice to see you here!
I am the Korean telecommunication company EFS file extracted from xperia1.
I used it. If you need VOLTE,
XPERIA1 (Modem).Extract from SIN file
I will use the Korean communication file.
Just drag it and put it in a folder.
v check and Yes
There'll be folders that don't exist while you're pulling them in.
Then make it and put the file in.
In the folder where you can view this red file,
Drag and drop the file twice.
The reason is that once you do it, you just go in.
The red file is not updated.
That's how the numbers at the back change when you renew.
So make sure to put it in twice.
Files beginning with NV do not have folders.
Put it on top.
It's over now!
Volte Success ^0^ About IMS
VOLTE OK
Confirm Video Calls
It was such a hard time for me!
I was sad because I couldn't get help.
With 5G mobile phones in 2020,
It was terrible to be on the 3G phone.
If there's someone like me,
This information will help you a lot.
Finally, Marktu
Buy! Buy two! I love it.
Click to expand...
Click to collapse
Hi there,
How did you find the firmware file? Did you extract the SIN from the localized firmware (for example custom U.S. or via another method? Also does this work for Xperia 1 or only Xperia 1 II

veerasammy778 said:
Root question
Is there a way to do this without root by using say newflasher and just changing the SIN file?
Click to expand...
Click to collapse
If you have Xperia 1. Just to enable VoLTE, either flash SEA firmware or Just flash these from the Japanese version.
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe
I'm using Android 9 and Flashed OEMs from Japanese latest .191 firmware which you can get by downloading using XperiFIrm and Newflasher from @munjeni .

@jeoleo7 I have Xperia 1 SO03L docomo version single sim phone. Unlocked carrier for use in India. Currently on android 11 version.
Can I flash below files and enable volte ?. Hope this will not affect sim unlock status to locked again. Need your help !
Quote"
Put these in a New folder.
oem.map
oem_other.map
oem_other_X-FLASH-CUST-A2CD.sin
oem_X-FLASH-CUST-A2CD.sin
newflasher.exe"
Will you be able to share the above file because I dont know how to extract it from android 11

@ralf_waldo
I have tried on my J9110 dual.
These files I have listed are just the OEM only and are region specific.
I easily achieved HD voice calls on LTE in my phone when I was using firmware from Ukraine or any other region.
I also tried Single sim variant flashing on my dual sim version.
I tried J8110 EE UK (found the clock and few changes different from my original).
Hence, just flashing these files won't lock your phone since its already unlocked.
You may backup your important things before doing anything.
Customized_JP_OEM_332.zip
drive.google.com

i need enable Volte on Sony experia 1 model : SO-03L please help me.