--- EDIT ---
On further review, I think that temporarily flashing the T-Mobile modem may have installed the IMS APN profile, and that's what really got it working. Adding the profile might be enough. Here is the profile:
Name: T-Mobile IMS
APN: ims
MCC: 310
MNC: 260
APN type: ims
APN protocol: IPv6
APN roaming protocol: IPv4
leave everything else default
Let me know if it works for you.
--- A method for modifying the OP partition is below, still worth reading ---
This is not a guide. It's just some rough notes for developers only.
I spent half a day getting this working. I'm not 100% sure what worked it in the end, but I have a pretty good idea. Here's some notes in case anyone else is working on it:
starting with V350AWM30c, rooted, noverity, TWRP on slot B
It is necessary to modify the OP partition, but it is tricky. The init script mounts it with verity and the normal patches don't work, but I figured out a workaround. Copy OP from slot B to slot A (slot A is not in use):
dd if=/dev/block/platform/soc/1d84000.ufshc/by-name/OP_b of=/dev/block/platform/soc/1d84000.ufshc/by-name/OP_a bs=4k
Add these two lines to /vendor/etc/fstab.judyp, below the system line
/dev/block/bootdevice/by-name/oem /oem ext4 ro,barrier=1,noatime wait,slotselect
/dev/block/sda24 /oem/OP ext4 ro,barrier=1,noatime wait
Init still mounts the original OP, but then the new one is mounted over it. Now we are using the OP partition from slot A on our slot B system and it can be modified.
mount /dev/block/platform/soc/1d84000.ufshc/by-name/OP_a /OP
Tip: now is a good chance to do some debloating on the OP partition.
modify one line in /OP/ATT_US/cust.prop
persist.product.lge.ims.volte_open=1
replace /OP/ATT_US/config/com.lge.ims.rcs.xml (see attached)
I added some lines from the equivalent file in the T-Mobile V40 firmware
add some lines to /system/build.prop (not sure if this did anything or not)
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
I think that did the trick. There is one other thing that I did, but I doubt it matters. I flashed the modem from the T-Mobile variant LG V40 and let it run for a while. It booted, but the modem didn't work and I ended up flashing back to the stock modem, but I suppose it's possible that running that modem briefly updated some configs.
Notes:
I'm actually using MintMobile, a T-Mobile MVNO.
If you're on slot A, you can just swap _a and _b, and use /dev/block/sda25 in fstab instead.
I discovered that VoLTE was working on TracFone AT&T with stock 30c, but not with 30e. That's why I started with 30c here.
I'm sorry that I don't have the inclination to make a proper guide or flashable firmware. Good luck.
{
"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"
}
Related
Not sure if im experiencing a factory mouse issue or not. No pics in the threads.
Issue: System info window keeps popping up in menu.(check img)
Occured: After flashing a stock Att md5 from liquid smooth ROM
Attempts:
-Reflashed several stock variations of the md5 through odin.
-installed terminal emulator and tried the typical "factory mode" that is pointed to Verizon users. Entering "echo -No...."
-Initiated self doubt then banged head on wall.
-ReReReFlashed stock ATT with injected root (downloaded from XDA thread)
Interesting points: All my roms and stock md5's have been downloaded from XDA. Im 100% sure im using the correct version. I noticed in attempting to finally sign up for XDA I was initially blocked from doing so because "in attempts to block spam, Verizon IPs are blocked" That's Weird because I'm an ATT user and was on my 4g network.
{
"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"
}
SeanMurphy said:
Not sure if im experiencing a factory mouse issue or not. No pics in the threads.
Issue: System info window keeps popping up in menu.(check img)
Occured: After flashing a stock Att md5 from liquid smooth ROM
Attempts:
-Reflashed several stock variations of the md5 through odin.
-installed terminal emulator and tried the typical "factory mode" that is pointed to Verizon users. Entering "echo -No...."
-Initiated self doubt then banged head on wall.
-ReReReFlashed stock ATT with injected root (downloaded from XDA thread)
Interesting points: All my roms and stock md5's have been downloaded from XDA. Im 100% sure im using the correct version. I noticed in attempting to finally sign up for XDA I was initially blocked from doing so because "in attempts to block spam, Verizon IPs are blocked" That's Weird because I'm an ATT user and was on my 4g network.
View attachment 1888641
Click to expand...
Click to collapse
When you have flashed stock through odin or the root injected stock ROM, have you done a factory reset, cleared data, returned it to a completely out of the box state ?
Where did you get the phone ? Is it new or did you buy it second hand ?
I've seen others with this and they can use the phone but the lockscreen is gone and the ppower button menu is gone as well. Is the imei corrupted ?
I bought a T-Mobile branded Note 2 when it was released and I recently switched to AT&T because t-mobile doesn't get service in my apartment. I had to flash the (t-mobile) stock image to get the unlock code to work. After unlocking I was able to get AT&T network connection and 4G data. When I restored the image I had backed up, I could not connect to AT&T's network. I'm was running LiquidSmooth 4.4.2 ( http://forum.xda-developers.com/show....php?t=2151580 ) before the switch.
It doesn't recognize that there is a SIM card in the device. When I go to Settings -> More -> Mobile Plan it says "Please insert SIM card and restart"
What can I do to get this to work on AT&T's network?
ishould said:
I bought a T-Mobile branded Note 2 when it was released and I recently switched to AT&T because t-mobile doesn't get service in my apartment. I had to flash the (t-mobile) stock image to get the unlock code to work. After unlocking I was able to get AT&T network connection and 4G data. When I restored the image I had backed up, I could not connect to AT&T's network. I'm was running LiquidSmooth 4.4.2 ( http://forum.xda-developers.com/show....php?t=2151580 ) before the switch.
It doesn't recognize that there is a SIM card in the device. When I go to Settings -> More -> Mobile Plan it says "Please insert SIM card and restart"
What can I do to get this to work on AT&T's network?
Click to expand...
Click to collapse
Have you checked the APN? Search AT&T APN in the main thread if you need to .
Okay I managed to get a rom that is compatible with AT&T and have an AT&T apn that should get LTE, but I'm only getting HSPA+ speeds. I tried flashing AT&T radios for the i317 from here: http://forum.xda-developers.com/showthread.php?t=1987541 , but those didn't give me any network access at all. Right now I'm on the latest t-mobile modem from here http://forum.xda-developers.com/showthread.php?t=2102380 I know I should be getting LTE because I have an LG G2 right next to me getting LTE
Any ideas?
{
"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"
}
SOLVED
I did not have enough apn types in my apn settings. I used these apn settings and I'm getting LTE
http://forum.xda-developers.com/showthread.php?t=2594719
I searched all forum but didnt get exact information i need , MY G3 is asian 32 GB D855 and SEA firmware , in settings there is no option for LTE , there are temporary ways like enable LTE from service menu or a parmanent method but first get root and delete LTE config apk and odex , My question is if i flash EUR kdz (i am aware i didn't get OTA's) is that possible it show me EUR firmware version in settings and LTE enabled by default in settings ?
{
"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"
}
Sent from my LG-D855 using Tapatalk
Dial *#*#4636#*#* and on preferred network type, choose lte/gsm/wcdma...the other option is to upgrade to V10J from Asia, with complete wipe, this will choose 4G first...
This worked for me. Thank you
mingocr83 said:
Dial *#*#4636#*#* and on preferred network type, choose lte/gsm/wcdma...the other option is to upgrade to V10J from Asia, with complete wipe, this will choose 4G first...
Click to expand...
Click to collapse
10J is not available via OTA
Sent from my LG-D855 using Tapatalk
fix the LTE using Prop.Build
Had the same problem. Found this fix. It is a permanent fix but have be rooted. But seeing as rooting and unrooting so simple, that shouldn't be a problem.
Simply use a Prop Build editor to go into the build.prop and change the "telephony.lteOnCdmaDevice” value from 0 to 1. There are two lines on in the G3 build prop. Make sure both have the value of 1. Then save. Then reboot.
I applied this to my G3 problem and now it is completely fixed!! I can select LTE auto and it stays, even on a reboot! I'll basically have to do this everytime i flash a new rom or update but it works!
I'll probably make a YouTube video later today to share the fix.
TLDR; Soft bricked phone trying to install TWRP, flashed stock rom on it, now phone says its 32 GB when its really 256 GB.
Hi all,
So I got a brand new Note 10+ a couple weeks ago and tried to flash TWRP onto it thinking it was easy like it used to be. Boy i was wrong. Stupid iphone user mistake.
So, I googled how to fix the soft brick. Downloaded the most recent firmware and flashed it via ODIN.
I flashed the following
BL
AP
CP
CSC (not HOME_CSC)
I setup my phone and personalised it like i had before and just now got a notification saying my phone is almost out of storage.
So i click the notification naturally being like what the hell already?
And long and behold my phone is now 32 GB instead of 256 GB.
I googled ways to fix this but all the ways say to flash the regular CSC which i already did!
Can anyone help me?
I've provided screenshots of the DF command and the storage settings.
Screenshots:
{
"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"
}
This could happen if you have flashed standalone AP file without CSC file same time.
Stock AP file must be flash with BL CP and Home_CSC at same time unless it may shrink your data.
Thank you for your response, however i flashed the AP file at the same time as everything else.
If i was to flash the AP file including everything else but change out the CSC file for the CSC_HOME will i keep my data on my phone because it was a pain to set it all back up.
No...
Is there a way to keep my data or no?
JosephShenton said:
Is there a way to keep my data or no?
Click to expand...
Click to collapse
If you use HOME_CSC_* it will not wipe data If you use CSC_* then it will wipe data. But looking to your device issue, probably you need to wipe it.
{
"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"
}
Overview:This guide provides step-by-step instructions for flashing any existing Sony stock rom Android 8 or 9 to the latest Sony stock ROM Android 9 Build v47.2.A.11.228 for use on the MetroPCS network. The finalized flash is a hybrid of Sony UK v47.2.A.11.228-R2C for fingerprint sensor functionality and Sony US OEM v47.2.A.11.228-R7C for the US modem firmware required for T-Mobile MVNO’s (MetroPCS).
A modification is required to instruct the device to recognize a MetroPCS SIM card as a T-Mobile MVNO carrier. Post modification, when a MetroPCS SIM card is inserted into the phone the correct modem files (T-Mobile) necessary for use on the MetroPCS network will be loaded. This modification can only be installed by temporarily flashing the device to an older Sony stock Oreo rom. Installing the modified APK file. Then re-flashing the device with the latest Sony Android 9 Pie build. This guide covers all steps needed to complete the full procedure from start to finish.
On completion, the device will function correctly on the MetroPCS network with the following characteristics:
• VoLTE HD Voice Calling fully functional (greatly improved call quality)• Wi-Fi HD Voice Calling fully functional• Data speeds greatly improved• Fingerprint recognition sensor fully functional• Latest Sony Android 9 build v47.2.A.11.228• Device remains unrooted• Bootloader remains locked• Android Attest Key remains intact• Mobile Hotspot and USB Tethering fully functional
The step-by-step guide in pdf format is attached below.
For those following the manual method:To download only the modified .apk, attached below is the modified com.sonymobile.customizationselector-res-305.apk file for MetroPCS VoLTE functionality. This apk can be used for both Oreo and Pie target platforms.
For those wanting to modify the referenced .apk file for T-Mobile MVNO's other than MetroPCS:Attached is an additional guide 'XZ1 Compact - Modifying the com.sonymobile.customizationselector APK for T-Mobile MVNO's Step-By-Step Guide.pdf' which provides instructions on how to manually modify the com.sonymobile.customizationselector.apk file. This second guide is written for the more advanced technical type. This may (should) work for enabling VoLTE on other T-Mobile MVNO's such as Mint Mobile, Boost, Simple, Ultra, and Tello among others.
Reserved
great work, really nice, thank you!
can support telco volte in my country malaysia.?
mrbaa4 said:
can support telco volte in my country malaysia.?
Click to expand...
Click to collapse
No, this guide is specifically for T-Mobile MVNO's in the US (like MetroPCS).