Related
Hi dev's,
I've troubles with my mt3g(vf) after flashing a new rom or doing a wipe.
Because I've no data rate everytime a new rom starts up I'm spending up to 5 € on a few seconds of data connection, till i can go to flymode/change apn/use a data block app...
And no - I don't need some offers of data rates (in my area I have wifi nearly everywere)
Maybe there is a way to stop the android connecting to 3G, like an adb command (usb debug is off?) or a way to change the apn by accessing the system before booting (in fastboot e.g.) or editing the apn in the rom-file before...
If you have any ideas to handle this, leave a comment please!
I'd like to test more of your rom's this way and instead of paying my provider for nothing, the money is much better invested by buying you a "beer"
so maybe anyone knows how i can pass the romfile check in recovery (while flashing the zip). I can edit the apns in /system/etc/apns-conf.xml ,but i need to pass this check while flashing...can't find any kitchen or so...must be only a little tool...give me a hint, please
This thread should be in the general section. Call your provider and ask them to turn off your data connection. I had to do it some time ago.
Remove SIM card BEFORE flashing a new ROM?
Taknarosh said:
Remove SIM card BEFORE flashing a new ROM?
Click to expand...
Click to collapse
Thanks for your help!
I tried this once, but can't then sign into g-account (was neccessary) but good idea, maybe with 2.1 now it will work (you can sign in later).
will try this next time, but it can't be so hard to edit a rom? Because i have done it...only want to make a working rom out of that, which passes the file-check in the recovery... maybe it does a md5-check or somthing else...
btw i think this is in the right category, i try to flash a rom and preventing 3g to connect by adb commands or by editing a rom!
Hello,
When we start for the first time the TF101 (after buying or flashing with a new rom after a wipe data), a setup wizard asks us for some options. In these options there is a choice for enabling 3G/Wifi or only Wifi.
I would like to know how to start again this setup wizard without wiping data!
How can I do?
Regards,
kasi
Why? Not trying to be rude, but anything you can do in setup wizard you can do already outside of that. I always delete setup.apk and setupwizard.apk from all my devices because the life of it is over after we use it initially.
because i would like to have the 3G option back ;-) And it's the only first time to have this choice.
so you tell that files are named setup.apk and setupwizard.apk ? But which one is the real file I need?
Are these files deleted after the first boot?
Those options are inside of Settings > Wireless & Networrks > Mobile Networks.
Nope.
These options were in my Settings but disapeared after Prime v1.6 update.
So to get back this Mobile Network option I have to wipe data and then restart my TF101. The setup wizard will ask me what I want to use and then I will have it.
But for the moment I lost it.
So I would like to start again the setup wizard without wiping my data.
I have the same problem, it seems that we have to go back to prime 1.5 via Nvflash for access to 3G/Wifi model. is there any way? restart to factory is not useful.
piromoplus said:
I have the same problem, it seems that we have to go back to prime 1.5 via Nvflash for access to 3G/Wifi model. is there any way? restart to factory is not useful.
Click to expand...
Click to collapse
Indeed. I've tried, after backing up my app/data, to wipe data/factory reset and same thing.
This option is no more in Settings!
Yes of course we can do a nvflash with Prime 1.5 but.... I think there is another thing to do....
Kasimodo said:
because i would like to have the 3G option back ;-) And it's the only first time to have this choice.
so you tell that files are named setup.apk and setupwizard.apk ? But which one is the real file I need?
Are these files deleted after the first boot?
Click to expand...
Click to collapse
I delete those two files by hand with root explorer..they are NOT deleted after you run them. They are no good anyway after you use the setup wizard the first time. I don't have a clue what could be your problem since just use wifi only. I would start from the very beginning and put in a rooted stock rom. Sometimes trying to save data is not worth the hassle of trying to repair the problem.
Thx for your reply life64x.
I've already tried to restore, to flash again and even to wipe/data.
But even after wiping data/factory reset the setup wizard doesn't ask me anymore to choose between "3G and Wifi" or "Wifi only".
For the apk file (setupwizard), I found it and launched it. Installation seemed to be ok but can't find a shortcut neither in Apps nor in Settings. Not even in Listed Apps for uninstall.
I think there is something missing in the Prime v1.6
Try asking the Prime author is he removed those options?
O? You bought the 3G version?
I didn't know 3G model is available any where but Italy at the moment,
sorry if I misunderstood, but why else would you want to enable 3G on a wifi only device?
andyxover said:
O? You bought the 3G version?
I didn't know 3G model is available any where but Italy at the moment,
sorry if I misunderstood, but why else would you want to enable 3G on a wifi only device?
Click to expand...
Click to collapse
no, rightnow there is not any 3g model available anywhere. but, there was a setting in previous version of prime rom, If we would be able to active 3g/wifi in setup, we can use 3g usb modems(dongle).
I assume you have ADB already, then type this line: "adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity"
:good:
Hmmm... question from 2011.... I found since.... ^^
Thx
...you need to make sure you can make it through this checklist.
This isn't a "how to" -- there are plenty of threads about that and stickies and search work pretty well, as does the SGS4G Wiki.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here.
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA.
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings.
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software.
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first.
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least:
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings.
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
6) Have you installed and know how to use
Better Battery Stats
aLogcat
aLogrec
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)?
8) Have you already downloaded the "back-to-stock" package for your phone?
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system?
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)?
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)?
12) Do you have a copy of all of these on something other than the phone and the microSD?
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone.
If you weren't able to check off all the above. STOP NOW.
OK -- backups in hand, power down your phone. Pull the SIM. Boot into recovery. Do a full backup of everything there as well. This is a "nandroid" backup. (If you're on "stock" without a kernel with custom recovery already flashed, you won't be able to create a nandroid backup.)
Flash the back-to-stock package according to the instructions. Were you able to do that successfully? Did your phone boot? Failure? Read the thread on the back-to-stock package carefully. They really are pretty bullet-proof. You're going to get terse responses if you have problems with the back-to-stock. If you fail here, restore that nandroid backup in your recovery. Go back and make sure you understand how flashing works and re-read the instructions.
Once you can go back-to-stock, make sure you can restore from your backups from steps 9-11. Yes, your SIM is still out, that way you won't be changing anything important on your phone. If you can't, restore the "nandriod" backup. Yes, go back and re-read things again until you understand and can do this reliably.
Made it to here? Go ahead and follow the flashing instructions for your ROM that are in its Development thread, generally in the first couple posts. You did read the entire thread, yes?
Restore your data from backups, if needed. Once you're confident it is running properly, power it down, and now insert your SIM again. Power it up and enjoy your new software.
Have a problem with a ROM or a piece of software? Remember that the problem basically doesn't exist until a dev can reproduce it, or see logs of it happening. Need a hint? See steps 5 & 6 here.
Sticky please.
Thread stickied... but let me run through my answers...
jeffsf said:
...you need to make sure you can make it through this checklist.
1) How long have you owned your phone? If it is brand-spanking new and your carrier will exchange it if it turns out to be defective, stop here. SGSIII - less than an hour...
2) Why are you contemplating installing whatever it is? Are you confident that the developer knows what they are doing? There is a wide range of skill and an even wider range of testing of things you might find on XDA. I want to play!...
2) Do you understand that virtually all ROMs, tweaks, kernels, what have you that you find on XDA, are all experimental, without warranty, and may turn your phone permanently into an expensive paperweight? Yes you can literally fry the innards of a phone with bad software, or even inappropriate user settings. YUP
3) Are you prepared to be without your phone being functional for hours, days, or longer? Expect it. You're thinking of flashing experimental software. Hope not!, but sure... read user comments (thread) before flashing...
4) Is your computer stable and reliable? Do you have or have you ever had any issues with USB or Internet connectivity? Fix those first. Motherboard bluescreens once a month randomly... gotta replace that soon....
5) Have you already installed and know how to use adb? Have you confirmed that it works with your computer, cable, and phone? This means understanding and having used at least: Never used ADB personally... for my captivate or SGSIII
adb push
adb pull
adb shell
adb logcat
adb remount
as well as shell commands including at least
# logcat
# dmesg
# cat /proc/kmsg
# mount -o rw,remount /system
# mount -o ro,remount /system
Shell redirection to a file, for example, # dmesg > /sdcard/dmesg.today.txt
Using crtl-C to terminate the foreground process in a shell
Yes, "this ain't no iPhone" when you start installing custom ROMs, tweaks, or whatever. You should be prepared to deal with the Linux part of the phone; you're often installing a new operating system and may have to deal with its underpinnings. Not a Linux fan....
No, your GUI-driven "root explorer" really isn't the right tool. You have to be very careful with Windows text editors too. You're lucky I'm not asking you to learn vi.
"Root explorer" app works great. But i would hardly call it GUI driven... lol
6) Have you installed and know how to use
Better Battery Stats Never heard of it
aLogcat NOPE
aLogrec NOPE
7) Have you installed Heimdall, and confirmed that the drivers work for your system (very important for Windows)? Hate Heimdall, odin works just fine. Its samsungs offical software, i think it should work. (It does). Chickens.
8) Have you already downloaded the "back-to-stock" package for your phone? Yes before i bought the phone.
9) Have you installed Titanium Backup, preferably Pro, and have complete backups of your system? Yes but after flashing first phone few times...
10) Have you backed up your Contacts (you can use the phone's Contact app to do this)? Sync to google account. no back up needed. figured that out before i found xda.
11) Have you backed up your phone logs and SMS/MMS (you can use Backup SMS & Restore and Call Logs Backup & Restore)? Titanium backup does this as well
12) Do you have a copy of all of these on something other than the phone and the microSD? Some... AND Titanium backup can sync to dropbox account or box account.
13) Have you read both the thread in Development and the thread in Q&A for the back-to-stock package as well as what you are about to flash? Really, I mean it. Yes, the whole thing. If you don't have time to read the threads, you probably shouldn't be flashing your phone. Yup
If you weren't able to check off all the above. STOP NOW.
Click to expand...
Click to collapse
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
TRusselo said:
Thread stickied... but let me run through my answers...
8 out of 13... damn. i should stop flashing and give my recognized developer status back... LOL
Click to expand...
Click to collapse
Heh, we gotta get you an sgs4g and have you show me how to get this crap working without using logcat or reading dmesg.
Trying to install jelly bean on my sgs4g
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
salutparis said:
so far i did everything that's on this page for post 1 http://forum.xda-developers.com/showpost.php?p=21953587&postcount=1
now i want jelly bean what do i do please helpp
Click to expand...
Click to collapse
This really isn't a support thread. It's more of a PSA.
If you want help, I'd suggest searching in the Q&A forum.
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
I just bought a Xperia XZ2 H8276 since the sim pins finally broke in my Xperia X Performance after about 4 year, word of advice don't make a sim work. Was not finding a Xperia XZ2 compact under $200 and the newer 5's are expensive, so that was the choice I made. It did not dawn on me that the move to volte only would make it hard to get newer unlocked phones on a nework. In trun looking into options pertaining to volte, switching to verizon was the only one that seemed to have a viable path. Talked with at&t where I found them unwilling to add my imei and don"t see a mdn that is clear cut for them, do see a mdn for tmobile but no service by my house. Verizon dose have dmd and they got the XZ2 compact, so there was light at the end of the tunel. So got the cheapest volte phone that I could find to activate a sim on, a moto e5 play is what I found. Will get to aguing with them now to add my imei since it work, unsure how that is going to go.
To get statrted a activated sim is needed and was done using the moto e5. After activation, need to talk with someone and have them check that sim the sim is CDMA-less with HD voice only. Best place I found to do that is start a chat with someone on this page, click chat in bottom right.
Verizon HD voice
For how I got the XZ2 to work on verizon gose like this based on many failed attempts. What I ended up doing is flashing H8216 Vodafone_Global_52.1.A.3.49-R9C firmware with H8314 Customized US_52.1.A.3.137-R7C oem sin files with newflasher, you can get these these off xperiafirm.
NewFlasher
XperiaFirm
Now with that in order, the verizon mbn needs added but need root to do so. If you dont have twrp that need installed and be sure to sideload magisk at the same time, other wise you will have boot loop to deal with.
TWRP
Magisk
After the phone has booted into the os, you need to now install the magisk app. Run this from whre you downloaded the application to your pc or install from the browser on the phone, need to cd to the place of download first if using terminal.
adb install Magisk-v23.0.apk
Magisk app
Here is the verizon mbn I pulled from the XZ2c modem sin.
Verizon mbn
That needs copyed to the phone SD card and use Root explorer to copy the mbn where it gose. I tryed PDC but could not get the drivers to work.
Root Explorer
You can you use this to install it if debug is on or down from the phone browser, cd to where you downloaded the file then...
adb install RootExplorer.apk
Now in root explorer, this is the destination to go and can only go there if root has been granted. If you dont get the promt to grant root go into magisk, click the shield at boot then the slider by the app. To copy the generic folder here from the sd card, click and hold it till hilighted where you can click the two papers stacked at the top. There will now be a clip board icon in the bottom right, do to the destination and click it.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw
The internal and external sd card will be one these two locations, ether use "adb push" or mtp to the put the directory on the sd card.
/storage/*-* *=a string of letters and numbers
/storage/emulated/0
/storage/self/primary
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see this under current modem config
row/verizon/vl/us
Now dial this.
*#*#4636#*#*
Under phone information set network type to lte only and should see voice type lte. If all went well, you should now be able to make phone calls.
I would like to move on to installing lineage-os but volte was not working there. I need to use this phone for work, so am not going to get into debuging that. Be my guess to try but Im not sure what brakes installing that.
I got some help from junkie2100 and give thanks to those that have posted info/software that lead me this far in gettting volte working. Here are some the clues that aided in the journey.
clues
clues
clues
As for tmobile, you might be able to replicate this but intead use oem sin's from the xz3 H8416 US along with pulling its mdn out its modem sin. Not sure what is special in the oem sin that pertains to setting up the given carrier, so unsure what is needed to get at&t to work but you free to experiament if you choise just I will not be much help.
Thanks for taking the time to put this together, the information on getting VoLTE working in the US on the XZ2 seems to be pretty scattered across various threads over the last several years, so I appreciate you placing this here.
I am not on Verizon, but I have been trying to figure out how to get this working on T-Mobile. I have followed some other threads that point to downloading the XZ3 OEM sin files as part of its Customized US Firmware like you mentioned, replacing those in the stack for the XZ2 firmware of a matching/similar version, and flashing to my device. I noticed after doing that VoLTE is provisioned (greyed out but turned "on"), but the modem config when checking my settings is still "Unknown." In addition to that, setting the device to "LTE Only" causes calls to not be placed, and "LTE Preferred" leads to calls dropping down to 3G like they originally were before trying to flash anything.
I could maybe use a little help in understanding what you mean be "pulling the mdn out of the modem sin." Is this an additional step to just flashing the two OEM files mentioned above and if so, where would I find it and go about setting it up?
Appreciate it.
The mbn file you need is in the modem sin from the xz3 firmware and this is the binary you need to extract it, put both the unsin binary and modem_X-FLASH-ALL-B6B5.sin in the same folder. This is the config file used by the oem sin to setup the volte.
unsin binary
Now cd to the folder that has both those and run these commands.
./unsin ./modem_X-FLASH-ALL-B6B5.sin
mkdir ./modem
sudo mount -t vfat -o loop modem_X-FLASH-ALL-B6B5.img modem/
You now have the modem sin extracted and the image mounted in folder modem. From there you need a copy of this tmobile folder and move it to the sd card on the phone.
/image/modem_pr/mcfg/configs/mcfg_sw/generic/row/tmobile
Now you can umount the modem image.
sudo umount -t vfat modem_X-FLASH-ALL-B6B5.img modem/
Now on the phone in root explorer that tmobile folder gets copyed to here.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/row
In this file you will also need to add these two lines so the mbn can be found.
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw//mbn_sw.txt
mcfg_sw/generic/row/tmobile/vl/us/mcfg_sw.mbn
mcfg_sw/generic/row/tmobile/vlvw/us/mcfg_sw.mbn
Now restart and dial this.
*#*#7378423#*#*
In service menu - service info - software info you should see one these under current modem config
row/tmobie/vl/us
row/tmobile/vlvw/us
Would anyone care to guess if a rooted/ rom'ed 8216 model of the XZ2 will work on T-mobile now that they have declared many older phone models incompatible (perhaps related to VoLTE capability)? 1mouse3 does your phone still work on T-Mobile? Thanks!