Related
Disclaimer: with easy I mean easier than I thought, it still a risk involved and ATM you will loose your installed programs. I am not responsible if this bricks your device, kills your cat or starts World War 3!
Update 12: Signal strength Display now works (On 3.2 for now). So have a look here and have fun.
Update 11: This thread is obsoleted by the fully flashable 3.2 update.zip you can find here
Update 10: Seems like you do not need (some users even point out that you shouldn't as it caused them FCs) to copy the ressources if you use the AU-Images. You can add you APN manually. You should copy the build.prop, if you want to use regional features of your device, as I think that market and other apps pull information out of it. Also as mcfish pointed out, you have to re-root afterwards by pushing su and Superuser.apk back to the Device with adb.
Update 9: Thanks to Simba90 there is now a complete set of working instructions to get the AU images on your XOOM with Nandroid. Read here
Update 8: I now extracted the AU images and put them in the thread here along with instructions how to apply them. You will loose all your data if you do that, but you will have a working UMTS 3.1 on your XOOM, which shows the right Signal Strength and you can run American Applications like Books on it. Follow the instructions in the thread to the letter and then copy the databases and the frankenrom as described here and voila it works. I dont know if I will build a hybrid of those two anymore or just try to build from the AU Release only, but I will tell you about my experiences here.
Update 7: It seems that with Tiamat 1.4.4 the 3G Blackouts some Users experience are less likely (and in my case gone for the last 9 days). Now that we have the Deodexed Version from here I will experiment a little and maybe I can switch out some of the system apps so that we finally get the Signal Strength displayed right.
Update 6: Seems the pushing of the telephony db did not help after all. I had the 3G Data loss again today, but luckily I did not reboot and still have it that way. So I can now analyze further. The tool I wrote to give out the network stats pointed me in the direction, that the telephony manager is gone, because it only reports null stats. I will investigate and we'll see, maybe I can find a final fix for that issue.
Update 5: Some users (including me) have had 3G breaking down sometimes. In case that happend, you did not see any network indicator and internet was gone. Once that happend and you opened the APN-Settings, all APNs were gone. I now think I have a remedy for that. I pushed the telephony.db and the telephony.db-journal from my backup and now I have it working for 3 consecutive days without a hiccup (except that one time the network Indicator was gone, but the internet was still there and a few minutes later the indicator was back). Pushing the db files goes like that:
Code:
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
After that it should work. The only remaining issue now is that the Network Signal Strength is not displayed properly. I wrote a little app to test all the Information you can get from the Telephony API, but from there the Signal Strength and Network Type are displayed properly. So this seems to be only a Display Issue in the Status Bar. If you have this display bug you only have half the network strength displayed and 0 dBm 4 asu in Settings -> About Tablet -> Status -> Signal Strength. I now am sure that this is only a Display and not a Network Issue. I tried 3.0.1 and 3.1 on different places with different types of networks and the Signal strength and download capacity were the same.
Update 4: As an Idea, if you have your settings.db files and your build.prop from your vanilla 3.0.1 (and your frankenbuild works with them) you could send it to me with the name of the Provider and the XOOM Type and I could build a database in this post where users could get those files to flash their XOOMs. Tell me what you think.
Update 3: Always try to use the db files from your own device or a device from the same country/provider, I am not sure if they differ from country/provider to country/provider. Also be sure to disable PIN lock before starting the device the first time with 3.1. And if you have 3G working and want to use another kernel, be aware, as it seems one member had problems flashing the Tiamat kernel and loosing WiFi. (I used Tiamat Version 1.4.2 -- 1.5 Ghz Overclock for Honeycomb 3.1 Only and it worked)
Update 2: As I saw the question pop up if you can flash a custom kernel after this procedure. Yes you can. I am using Tiamat with 1.5 OCed from http://forum.xda-developers.com/showthread.php?t=978013
Update: If you pull the databases you can test if they are healthy by using sqlite. In case of settings.db and telephony.db the tables command should show the tables in the db. If it shows the error message something went wrong. I dont know what the wal and shm files are for, but they can not be opened by sqlite.
Code:
sqlite3 settings.db
SQLite version 3.7.5
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
// In the error case it displays
sqlite> .tables
Error: database disk image is malformed
// if it is okay it shows
sqlite> .tables
android_metadata bookmarks system
bluetooth_devices secure
Prereq:
Unlocked and rooted Euro XOOM with clockwork recovery and PIN entry for you SIM Card disabled (Some users report that if PIN is enabled there is no 3G as it seems that the PIN Entry Util is not part of the CDMA packages)
Instructions:
1. Get the needed files
There are two ways to do this, the first one (a) was used by me, and is the one I can tell you it works for sure. The second one (b), I think should also work, but I havent tested it. I think some of the members who postet here have, though.
a. Make a nandroid Backup and copy data.img from that backup to your PC. Then unyaffs it.
(If you want to build your own build prop you need system.img as well)
Code:
unyaffs data.img
// Only if you need your own build.prop
unyaffs system.img
b. Get the needed files with adb.
(You need root and read permission for that)
Code:
adb remount
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
adb pull /data/data/com.android.providers.settings/databases/settings.db-wal settings.db-wal
adb pull /data/data/com.android.providers.settings/databases/settings.db-shm settings.db-shm
adb pull /data/data/com.android.providers.telephony/databases/telephony.db telephony.db
adb pull /data/data/com.android.providers.telephony/databases/telephony.db-journal telephony.db-journal
// This step is only necessary if you want to build your own build.prop
adb pull /system/build.prop build.prop
2. Flashing 3.1
Flash the 3.1 US image from http://forum.xda-developers.com/showthread.php?t=1074609 following the Guide with all steps (even the ones in red which it says are only for verizon) but skipping Step 1 (flashing the recovery)
3. Frankenrom build.prop
There are two ways to get a working build.prop
a. Download the build prop from http://toshsoft.de/xda/build.prop.frankenrom and copy it to your device
Code:
adb push build.prop.frankenrom /system/build.prop
b. Build your own build.prop. To do this first remove all the lines starting at
Code:
# RIL and telephony related settings
to the point where the OpenGL string starts and replace them with the same lines in the build.prop you copied from the unyaffed system.img. Then comment out the line with
Code:
ro.cdma.otaspnumschema
4. Push the Stuff back
Push all databases from /data/data/com.android.providers.settings/databases/ from the data.img backup (Those are - settings.db settings.db-shm settings.db-wal telephony.db telephony.db-journal) and the new build.prop to your device.
Code:
adb remount
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
adb push settings.db-wal /data/data/com.android.providers.settings/databases/settings.db-wal
adb push settings.db-shm /data/data/com.android.providers.settings/databases/settings.db-shm
adb push telephony.db /data/data/com.android.providers.telephony/databases/telephony.db
adb push telephony.db-journal /data/data/com.android.providers.telephony/databases/telephony.db-journal
adb push build.prop /system/build.prop
5. Finishing up and rebooting
Et voila, after a reboot everything works. (including books)
Code:
adb reboot
Proof:
{
"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"
}
Genial! Gut gemacht!
Danke für deine Arbeit!
Fantastic !
Very good news.
i cant find the Databases "pushed all databases from /data/data/com.android.providers.settings/databases/ from my backup to the new one"
I can't make a nandroid backup cause I have no external sd. Is there a way to do it with adb?
Hi, I updated the guide, because I used the wrong img file name in the text. The databases are in the data.img If you have no sdcard I think it should be possible to pull the files from your device before flashing. But I don't have the names of the database files here. I am on the move at the moment. Once I get home, I will update the guide with all necessary file names and thread links.
oh :-( i cant unyaffsen :-(
i'm on Windows :-(
There is a prebuilt unyaffs for windows at http://boomtopper.blogspot.com/2009/10/unyaffs-windows-binary.html
Thank you so much for this. Will try when I get home.
Edit - noticed your screenshots show Edge reception, you have achieved HSPA using this method too, right?
Sent from my Xoom
From the US 3.1 instructions do we do steps 2-7 including step 4 (for Verizon 3G users) ???
Thanks
You're just asking for trouble with this, I know the kind of impatient people that will boot loop their devices wth this and come back complaining its bricked.
Simple theory though, flash US images, restorevthe databases and then fix your build prop to get your 3g radio and market location back.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
alias_Neo - That's what disclaimers are for. And here we have some good guides here for unbricking. I did this not because I am impatient. I did this because I wanted the books app and the tablet tab in the market, which we will not get with the euro 3.1 release.
Tyrannos - yes I get hsdpa reception, but @ home my network only does edge.
Andypotts - yes, you follow them to the letter and end up with a 3.1 us XOOM with no 3G then you follow the steps from there and push back the prop and DB files and there you are.
lowtraxx said:
alias_Neo - That's what disclaimers are for. And here we have some good guides here for unbricking. I did this not because I am impatient. I did this because I wanted the books app and the tablet tab in the market, which we will not get with the euro 3.1 release.
Tyrannos - yes I get hsdpa reception, but @ home my network only does edge.
Andypotts - yes, you follow them to the letter and end up with a 3.1 us XOOM with no 3G then you follow the steps from there and push back the prop and DB files and there you are.
Click to expand...
Click to collapse
Naw, disclaimers are inconsequential, im talking about stressed people with messed up xooms, not trouble for you. Its a pretty clean cut guide. As for the tab, we may get the tablet tab, we have to some day, as for books.. I can do without cause I use other things.
I just don't want people to make a mess of things cause they're getting impatient about the 3.1 update.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
Hi and thanks for the infos!
On my device the SHM and WAL file are:
settings.db-shm
settings.db-wal
"-" not "."
First I've backuped my 3.1(german t-mobile mz601) without 3g working wit CW, then used the guide "from 3.1 to 3.0.1". Then I had to unlock and root it once again and was able tu pull the 4 files. Then I've used CW to restore my former 3.1 system and continued with the steps. If anybody wants to have the 4 files(settings.db-shm,settings.db,settings.db-wal,settings.db-shm,build.prop), pm me.
greetings from Berlin
B3rlin3r said:
Hi and thanks for the infos!
On my device the SHM and WAL file are:
settings.db-shm
settings.db-wal
"-" not "."
First I've backuped my 3.1(german t-mobile mz601) without 3g wit CW, then used the guide "from 3.1 to 3.0.1". Then I had to unlock and root it once again and was able tu pull the 4 files. Then I've used CW to restore my former 3.1 system and continued with the steps. If anybody wants to have the 4 files(settings.db-shm,settings.db,settings.db-wal,settings.db-shm,build.prop), pm me.
greetings from Berlin
Click to expand...
Click to collapse
I wouldn't recommend handing out your DB files without checking what's in them first. Im not at a computer to check myself.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
Thanks for your advice,
but the only "personal data" I entered in the "restocked" XOOM, before I pulled the DB-files was the PIN for my SIM Card...
B3rlin3r said:
Thanks for your advice,
but the only "personal data" I entered in the "restocked" XOOM, before I pulled the DB-files was the PIN for my SIM Card...
Click to expand...
Click to collapse
Cool, better safe than sorry. Applies to everyone else that may want to pull the files too.
Macbots drool as I XOOM through the Galaxy to my hearts Desire.
Hi,
Sorry, the XOOM seems to have replaced the - with a . I will update the Guide accordingly
Hello
Can anyone supply me with a copy of the system and data img as I have 3.1 already installed on mine.
Thanks
Hello
Ignore the last post as another member kindly supplied me with the needed files. Have pushed all the files to my xoom then rebooted but no 3g still. Thinking im missing something here.
UPDATE: There is a much simpler solution that anyone can use without learning Linux commanline or file permissions. See this thread for details:
http://forum.xda-developers.com/showpost.php?p=54462957&postcount=13
WARNING: If you do not understand every step of these low-level Linux command-line technical instructions, then do not attempt this method or you may brick your phone! These instructions are written for people who understand android developer tools, Linux command-line tools, and file permissions. If you do not understand these Android development basics, then find another walkthrough.
I got my phone up and running and text messaging, 4G LTE data connectivity, and phone calls worked just fine, however, I noticed I was unable to send and receive MMS messages (picture messaging). I tried every solution I could find on the web for changing the APNs on my rooted LG Optimus G Pro E980, and by trial and error, I discovered the following solution:
The stock Android ROM supplied by AT&T for the Optimus G Pro - Android 4.4.2 (Build E98020G), has disabled the ability to add working APN settings through the system APN settings dialog by defaulting all new APNs to have the (apn) type="default,dun". The settings screen does not let you change this value, so you have to edit the values directly in the SQLite database.
None of the free SQLite-database-editors in the Android market were able to edit the read-only /data/data/com.android.providers.telephony/databases/telephony.db file (after following instructions for editing the APN in the database in the folder where it is stored).
So, using ES File Manager (search for "com.estrongs.android.pop" on google play), I copied it to my SD-Card, copied to my computer and edited it with SQLite Database Browser (a SourceForge project identified as sqlitebrowser).
VERY IMPORTANT: The permissions change when copying the file from your computer to the SDCARD and when copying it from the SDCARD to the /data/data/com.android.providers.telephony/databases/ folder. So, I had to set the permissions back to the original telephony.db permissions & owner. The permissions should match all of the other .db files in the /data/data/com.android.providers.telephony/databases/ folder, like so:
RW-RW----
VERY IMPORTANT:Change the file owner back to "radio" from "root". Change the group back to "radio" from "root". If you do not change the owner and group back to "radio" after you copy the telephony.db file back to the /data/data/com.android.providers.telephony/databases/telephony.db path, the phone.apk process will repeatedly crash until it restarts your phone (and your phone will keep rebooting until you delete the telephony.db file that has incorrect permissions or incorrect owner). To boot, the phone.apk runs under the "radio" group and needs the critical Android OS file: telephony.db to be owned and accessible by the "radio" group.
After creating an APN per Straight Talk's instructions, changing the type field in the carriers (APNs) record stored in the telephony.db, copying over the new telephony.db (and overwriting the original), changing the permissions & owner of the copied file, and rebooting the phone, I was able to send and receive text messages and picture messages (MMS) to myself.
Note: My phone came with the correct "Service Center Address" setting, because it was an AT&T branded phone before I brought it to Straight Talk. However, you may need to change this setting if you came from another carrier with your phone. The correct setting for Straight Talk customers on the AT&T LTE network should be (the same as it is for AT&T customers on an AT&T plan):
Code:
+13123149810
Although the /system/etc/apns-config.xml file has several, misleading APN values in it, this file is not used to store the APN records in Android 4.4.*. Instead, APNs are stored in the /data/data/com.android.providers.telephony/databases/telephony.db SQLite database.
Also, there is a rumor spreading around the internet that you cannot send MMS messages when your WIFI is connected (instead of a 4G LTE connection). That is false: my phone sends and receives MMS messages while the WIFI is connected.To make it easier for you to change your APN settings on your phone, I have attached my working telephony.db file. It contains only one APN record for Straight Talk on AT&T's LTE network. I deleted all of the other APN records from the database, per Straight Talk's APN instructions.
If you are curious, I also attached the database dump of the attached telephony.db, which was auto-generated by SQLite Database Browser. It is a text file called "telephony-dump.sql".
Hi, I tried this step by step and now my phone does nothing but crash repeatedly. Any way to fix this?
How to unbrick your phone if you missed steps in the instructions
l337m45732 said:
Hi, I tried this step by step and now my phone does nothing but crash repeatedly. Any way to fix this?
Click to expand...
Click to collapse
If you do not understand every step of the above low-level Linux command-line technical instructions, then do not attempt this method or you may brick your phone!
It sounds like a permissions issue - the android operating system is crashing because it does not have permission to read the critical OS file: telephony.db. Did you set the owner, group, and permissions on the telephony.db file correctly? If you are unable to change the permissions back on the telephony.db, then follow the instructions above to fix your problem:
ratkiley said:
VERY IMPORTANT: The permissions change both when copying it to and when copying it from the SD-Card. So, I had to set the permissions back to the original telephony.db permissions & owner, (matching the other .db files in the /data/data/com.android.providers.telephony/databases/ folder):
RW-RW----
VERY IMPORTANT:Change the file owner and group back to "radio" from "root". If you do not change the owner and group back after you copy the file back to the /data/data/com.android.providers.telephony/databases/telephony.db path, the phone.apk process will repeatedly crash until it restarts your phone (and your phone will keep rebooting until you delete the telephony.db file that is owned by "root").
Click to expand...
Click to collapse
If you don't know how to delete the telephony.db file, then you can flash the stock AT&T android Operating System image file to unbrick your phone. There are many tutorials and walkthroughs on this topic on xda developers. This walkthrough is pretty comprehensive:
http://forum.xda-developers.com/showpost.php?p=44983841&postcount=1
WiFi Fix - always all channels on 2.4 GHz
IMPORTANT:
Only for advanced users!
You are an advanced user if you know exactly what you are doing.
You are an advanced user if you know what to do if something went wrong.
You are NOT an advanced user if you know how to do copy+paste.
You can bring your smartphone into a state, so it no longer works.
I am not responsible for anything. The following instructions are only suggestions.
Hello,
I want to show you a way how you prevent your LG G4 to limit wireless channels to 1-11.
This happens when no SIM card is inserted or if the airplane mode is activated.
You get messages like:
"Some Wi-Fi networks unavailable due to unknown location" (English)
"Einige Wi-Fi-Netzwerke sind wegen des unbekannten Standorts nicht verfügbar" (German)
"Algunas redes Wi-Fi no están disponibles debido a una ubicación desconocida" (Spanish)
I studied the log entries and found a line that said "[LGE_PATCH] For Country code DC. ....".
After a long search in the code I have discovered the place that is responsible for the limitation.
It is located in the wifi-service and it sets the WifiCountryCode to "DC" if your location could not be obtained.
For me living in Germany it should be "DE".
The WifiCountryCode named "wifi_country_code" is stored in the "global" table of "/data/data/com.android.providers.settings/databases/settings.db".
Changing it has no effect as it is overwritten instantly.
So we need to modify the program code of "wifi-service".
According to this post: http://forum.xda-developers.com/showpost.php?p=64636618&postcount=8
this guide seems to work on other models from LG and newer Android versions too.
You have to search for the wifi-service.odex file and replace "DC" with your two-letter country code.
Alter the paths of the instructions if you use another phone than LG G4 with Android 5.1 Lollipop!
The following instructions show how to do it on the LG G4 with Android (5.1) Lollipop.
Prerequisites:
ROOT
USB debugging enabled
Procedere:
Connect your G4 to your computer.
Open the command promt and enter the following lines:
Code:
adb shell
mkdir /sdcard/wifi-service
cp /system/framework/arm64/wifi-service.odex /sdcard/wifi-service/64wifi-service.odex
Now a file named "64wifi-service.odex" is on your internal memory located in the folder "wifi-service".
Copy the file to your computer.
Now you have to edit the file.
Don't use the "editor" on windows, use Notepad++
With Strg+F search for "DDD".
You will find exactly one line that contains this::
"DATE_TIME DBG DC DCM DDD DDFName"
Change the value "DC" to "DE" for example (search the internet for the two-letter country code of your country (ISO 3166-1 alpha-2))
"DATE_TIME DBG DE DCM DDD DDFName"
Save the file.
Delete the file "64wifi-service.odex" on your smartphone.
Copy the edited file from your computer to the folder "wifi-service" on your smartphone.
Go back to the command prompt and type this:
Code:
su
You should see an confirmation promt on your smartphone that asks to grant root rights.
Confirm the message.
The command promt should change from $ to # now.
To verify your rights type this:
Code:
id
You should see "uid=0" etc.
Now type in the following lines (I recommend to execute each row seperately):
Code:
mount -o remount,rw /system
cd /system/framework/arm64
cp wifi-service.odex /sdcard/wifi-service/64wifi-service.odex.bak
rm wifi-service.odex
cd /sdcard/wifi-service
cp 64wifi-service.odex /system/framework/arm64/wifi-service.odex
cd /system/framework/arm64
chown 0:0 wifi-service.odex
chmod 0644 wifi-service.odex
echo "restart device"
Check the outputs. There must be no errors!
After hitting the Enter button the last line should output "restart device".
In the folder "wifi-service" on your internal storage you find the original "wifi-service.odex".
It is named "64wifi-service.odex.bak".
Restart your smartphone now.
As from now it does not matter whether a SIM card is inserted or if the airplane mode is activated.
The WiFi channels are no longer limited to 1-11. You can now always use 12 and 13.
Did the instructions help you?
Please give a "Thanks!"
Thank you
For users who speak German:
I wrote this guide in German at first. You can find it on android-hilfe.de
Title: "LG G4 WLAN Fix - immer alle Kanäle"
http://www.android-hilfe.de/thema/lg-g4-wlan-fix-immer-alle-kanaele.710265/
I am using Ultraedit. Nevertheless I only see a hex file and I can not locate a string: "DCM DDD DDFName" Any suggestions?
It is also passible with your editor.
There are two ways:
1. In HEX mode (default mode)
After hit "Strg + F" enter the string "DDD"
Activate the checkboxes "ASCII suchen" and "Groß-/Kleinschreibung beachten".
You will find excatly one result. (DC is in line 00c6e40h)
2. Deactivate HEX mode (Strg + H)
After hit "Strg + F" enter the string "DDD"
The first result is what you need. (line 10528)
Change "DC" to "DE". Don't change anything else!
Hope I could help.
You are also on V10c? Otherwise line numbers will differ.
Tip:
Make a system.img with "dd" of your current system partition.
If it don't work or you did something wrong you can simply copy it back with "dd".
dominik-p said:
It is also passible with your editor.
There are two ways:
1. In HEX mode (default mode)
After hit "Strg + F" enter the string "DDD"
Activate the checkboxes "ASCII suchen" and "Groß-/Kleinschreibung beachten".
You will find excatly one result. (DC is in line 00c6e40h)
2. Deactivate HEX mode (Strg + H)
After hit "Strg + F" enter the string "DDD"
The first result is what you need. (line 10528)
Change "DC" to "DE". Don't change anything else!
Hope I could help.
You are also on V10c? Otherwise line numbers will differ.
Tip:
Make a system.img with "dd" of your current system partition.
If it don't work or you did something wrong you can simply copy it back with "dd".
Click to expand...
Click to collapse
Thanks for all the help! I switched to notepad ++. Found the entry
Code:
DATE_CLASS DATE_KEY DATE_TIME DBG DE DCM DDD DDFName DEBUG
in line 17126 though. Changed it successfully! Copied successfully to my phone! No effect! Still no channel 13 without sim. Double checked (copy wifi-service.odex to pc) and look for
Code:
DATE_TIME DBG DE DCM
.
It IS in there. Somehow not taking effect? I had problems when doing "chown 0:0 wifi-service.odex" It tells me "read only file system". I did set the owner and permissions with ES File Explorer. TO: root, root and Read, write; read; read.
OK I think you are an advanced user. (aren't you?)
You did it right with your app, but it should be possible with the shell too.
Readonly means you are not "su" in shell or/and did not "mount -o remount,rw /system".
Check su with "id" (uid=0) and mount should output something like this:
Code:
/dev/block/bootdevice/by-name/system /system ext4 [B]rw[/B],seclabel,relatime,data=ordered 0 0
Please check that /system/framework/arm64 has only one file named wifi-service.odex in it.
While testing I got to a point where I had two "wifi-service.odex" files with different file permissions in it.
Post an "ls -l" of the folder please.
After removing the SIM card and rebooting your phone look in the "global" table of settings.db and check that "wifi_country_code" is set to "DE".
Please also use catlog to check if wpa_supplicant sets the CountryCode to DE.
PS: for me it's line 17073 in notepad++ Don't know why lines differ.
Filesize of wifi-service.odex is 3903976 bytes for me. You are also on V10c?
Thanks for this! just fixed my G3 Marshmallow,
I'm using another region rom, and i think sim country is not properly detected.
Thanks for reply.
Didn't know that the G3 has this "problem" too and that my solution works on Android M.
I guess it's not the same line "DATE_TIME DBG DC DCM DDD DDFName"
but also a line with the value "DC"?
dominik-p said:
Thanks for reply.
Didn't know that the G3 has this "problem" too and that my solution works on Android M.
I guess it's not the same line "DATE_TIME DBG DC DCM DDD DDFName"
but also a line with the value "DC"?
Click to expand...
Click to collapse
I just noticed the problem when updating to 6, its another line but very similar:
the full path for the file is /system/framework/oat/arm/wifi-service.odex
Line is 24139
values for the line are "DATE_CLASS DATE_KEY DATE_TIME DATUM_WIDTH DBG DC DCM DD DDD DDFName "
Just changed DC to BR.
Perfect.
Thank you.
dominik-p said:
Perfect.
Thank you.
Click to expand...
Click to collapse
Hello, I know that the thread is quite old, but I have a small problem with the wifi-service.odex file on my phone. Looks scrambled in n++. Is there any setting for n++ that I should use?
My phone is a Le Max2 and I don't have GSM signal at my workplace. The routers are set to automatic and they also use channels 12 and 13.
From what I understand by the commands, you are just pulling the file from system to internal storage, and copying it to the computer, changing it with n++ and copying it back to system. There is no transformation to .jar as I can see...
The file is about 4mb.
Can you provide any help please?
valy_cta said:
Hello, I know that the thread is quite old, but I have a small problem with the wifi-service.odex file on my phone. Looks scrambled in n++. Is there any setting for n++ that I should use?
My phone is a Le Max2 and I don't have GSM signal at my workplace. The routers are set to automatic and they also use channels 12 and 13.
From what I understand by the commands, you are just pulling the file from system to internal storage, and copying it to the computer, changing it with n++ and copying it back to system. There is no transformation to .jar as I can see...
The file is about 4mb.
Can you provide any help please?
Click to expand...
Click to collapse
Hi,
you already created a thread here: https://forum.xda-developers.com/le-max-2/help/wifi-channels-12-13-unable-to-t3773144
Please stay at your own thread for further discussion. This thread here is only for LG devices and the provided fix is only working on some LG devices.
You're right, the odex file looks "scrambled" in Notepad++, but that's no problem. We only had to change one or two letters.
I will answer at your thread "WiFi channels 12 and 13 - unable to see them". (https://forum.xda-developers.com/showthread.php?t=3773144)
For all other users, please read these threads to understand the problem:
WiFi regional problem on Android https://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android
[GUIDE] WiFi Country Problem Solving for AOSP, MIUI & others https://forum.xda-developers.com/showthread.php?t=2368501
Double post by mistake - slow internet connection
Worked cool on LG G4 Stylus
Just a few "logistics" to comment:
-on some devices/models seems to be that /sdcard is no possible to access. Instead, /storage/emulated/0/ or the real path /data/media/0
-when copying the modified wifi-service file to /system/... folder, step on with a "Permission Denied" message. I was Root and /system was mounted as wr. Finally continued by copying using a root explorer and then continuing in the shell.
-after i rebooted, tried to connect on a channel 13 without sucess. I had plain mode. I put off plain mode, changed the country in wpa_supplicant.conf file and rebooted again. After that, all went good
DarkBader said:
Just a few "logistics" to comment:
-on some devices/models seems to be that /sdcard is no possible to access. Instead, /storage/emulated/0/ or the real path /data/media/0
-when copying the modified wifi-service file to /system/... folder, step on with a "Permission Denied" message. I was Root and /system was mounted as wr. Finally continued by copying using a root explorer and then continuing in the shell.
-after i rebooted, tried to connect on a channel 13 without sucess. I had plain mode. I put off plain mode, changed the country in wpa_supplicant.conf file and rebooted again. After that, all went good
Click to expand...
Click to collapse
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?
dominik-p said:
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?
Click to expand...
Click to collapse
LG G4 Stylus H635 LL 5.0.2
Thank to you for the good work
Question!
dominik-p said:
Thanks for your feedback!
Would you please share your model number and Android version of your "LG G4 Stylus"?
Click to expand...
Click to collapse
I had a situation i yet did not solve.
Yesterday i went to some friend's house, where before i could not see their wifi network. And i still can not see it ! :0 :0
I know this method worked, because changed the channel on my router to 12 or 13 and i can see them and connect. Also country code show as i changed it in Wpa_Supplicant and in CountryCode in Android.Providers. I also know is not a hidden network, as my friends can see it and connect normally without problem. Also tried with WPS button, and nothing.
.
-As the "problematic" network is a 5G, maybe is something related with this? lack of technology as my phone model is a bit old nowadays?
But what i understood about 5 G, is that they assure backwards compability :/
.
Maybe u see something i am missing?
I found through some searching the location of the telephony.db file in Android N and I was successfully able to edit it to enable the native hotspot.
Here's a poorly written guide:
1. Using a root browser or ADB shell, copy /data/user_de/0/com.android.providers.telephony/databases/telephony.db to the root of the internal storage (/storage/emulated/0)
Code:
adb shell su
cp /data/user_de/0/com.android.providers.telephony/databases/telephony.db /storage/emulated/0/
exit
If you have the premium version of jrummy's root browser, it has a built in database editor and you may use it. Edit: You can't edit the file in place, you must copy it to /storage/emulated/0 to edit, then copy it back.
2. Copy the telephony.db file to your computer
Code:
adb pull /storage/emulated/0/telephony.db
3. Using a SQLite editor on your computer, open the telephony.db file, and open the "carriers" table.
4. Find "APN2 LTE internet" and in the type column add "dun" to the end, so it should read "default,mms,dun"
5. Do the same with "APN2 EHRPD internet"
6. Write the changes to the database.
7. Put the file back on the phone's storage
Code:
adb push telephony.db /storage/emulated/0/
8. Rename the telephony.db in "/data/user_de/0/com.android.providers.telephony/databases/" to telephony.db.bak
Code:
adb shell su
mv /data/user_de/0/com.android.provicers.telephony/databases telephony.db.bak
9. Copy the telephony.db from the storage to "/data/user_de/0/com.android.providers.telephony/databases/"
Code:
(adb shell su if you exited the shell previously)
mv /storage/emulated/0/telephony.db /data/user_de/0/com.android.providers.telephony/databases/telephony.db
exit
10. Reboot. Tethering should now work.
I'm not sure if this adds the hotspot icon to the quick settings or if the icon is left over from a failed attempt to get the hotspot working. (Edit: button seems to always be there)
Note: Updating your profile may reset the APN settings. If so, you should be able to follow this guide again.
Edit: At some point my profile updated or something and disabled the hotspot. I did this procedure again and it worked.
tdhite's SkyHigh kernel does this automatically but it breaks private mode and I kind of wanted that.
Credit where it's due: This thread is where I found the location of telephony.db
Thanks! I'm quite happy with tdhite's skyhigh kernel atm which has hotspot built in, but its great to know that if for some reason I cant use skyhigh in the future, there are still alternatives for getting hotspot!
remove root
I am not able to get this to work. Hangs at Samsung portion of the boot.
trendkilla254 said:
I am not able to get this to work. Hangs at Samsung portion of the boot.
Click to expand...
Click to collapse
I'm sorry to hear that. I'm not a developer or anything so I couldn't tell you exactly what went wrong. Are you using the stock ROM?
I found some interesting info on this and was actually able to edit the apn and get my phone to boot. I just moved the file to the SD card and used sqlite editor. The key is after you copy the file back to original folder set permissions rw_rw__ just like the other files. Change both owner and group back to radio.
I get no signal in my house so I have to wait till I get to work tomorrow to actually test the Hotspot.
Sent from my SM-G925P using Tapatalk
baknblack said:
I found some interesting info on this and was actually able to edit the apn and get my phone to boot. I just moved the file to the SD card and used sqlite editor. The key is after you copy the file back to original folder set permissions rw_rw__ just like the other files. Change both owner and group back to radio.
I get no signal in my house so I have to wait till I get to work tomorrow to actually test the Hotspot.
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
For anyone interested. This actually works for me.
Sent from my SM-G925P using Tapatalk
I dont see "APN2 EHRPD internet" in telephony.db on my S6 Edge Sprint Nougat phone.
potolok said:
I dont see "APN2 EHRPD internet" in telephony.db on my S6 Edge Sprint Nougat phone.
Click to expand...
Click to collapse
Here's mine if the link works
https://drive.google.com/file/d/17pSf3NBbxImTvHhAMclSwtSNF30rl-qY/view?usp=drivesdk
Sent from my SM-G925P using Tapatalk
Tried all the ways of activation Hotspot on Nougat (QC7), fixes, changing CSC etc.... But all without success
Can anyone confirm this works with QJ1 stock that has been rooted?
baknblack said:
Here's mine if the link works
https://drive.google.com/file/d/17pSf3NBbxImTvHhAMclSwtSNF30rl-qY/view?usp=drivesdk
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
I don't think sharing your own APN database is a good idea.
potolok said:
I dont see "APN2 EHRPD internet" in telephony.db on my S6 Edge Sprint Nougat phone.
Click to expand...
Click to collapse
Make sure you're looking in the "carriers" table. For me they are the last two. They might not say APN2, but they should have "EHRPD internet" and "LTE internet" in the name and under type by default should say "default,mms"
Thank you so much for posting this, Man!! I had been searching all over the web for answers!! Hotspot working perfectly now.
I just used root explorer, and sqlite editor, and followed your steps. Thanks again =)
:INTRO:
OK: here's the thread we are talking about and working on getting VoLTE & VoWiFi to work :good:. For now this is for the H930 Open EU variant only, it worked for two peoples incl. me, but I think this is applicable on other variants of V30, with respective edits (/OP, you'll read later), too. Maybe even to other phones? I don't know, LG is sth (=something) special This thread will rise with time I think, with different edits or ways to reach the goal: we want VoLTE/VoWiFi, sth, LG imho should've taken more care of...
I hope, my english is sufficient so everyone understands what's to do And, btw.: you should have "Allow OEM Unlock" switched off.
User @Krekos/CZ/ did help me in a special way: he zipped his modem config files I by accident deleted from my phone and uploaded them :good: Without them I would've not being able to complete this work, and therefore I wanted to say thanks again to him at this point (I think you can't hear this anymore, hm? ). He's btw. the second person for whom this worked, he's got VoLTE&VoWiFi now.
These files should work on other SD835 phones too, I link them here for archival. Eventually we can get a collection from every variant, this way we might be able to activate VoLTE etc. for a carrier on a phone which was not intended to being used with other operators. So a call to other variant users: can you please tar and upload these files to XDA? Procedere is:
Connect your phone via ADB and open a command prompt
type:
Code:
adb shell tar -czf /sdcard/mbn-files.tar.gz /firmware/image/modem_pr/mcfg/configs
Upload this file to your post here in this thread. I'll add it to the list then.
Links to modem cfg files (mcfg_sw.mbn):
H930 EU Open
US998 Open
These files need special permissions, of course... Otherwise it would be boring
The path (on a LG phone) for oreo firmware is as follows:
/firmware/image/modem_pr/mcfg/configs
For pie it's not /firmware/, but /vendor/firmware_mnt/: pls remember to change path in the following process accordingly when using pie.
Permissions are:
files 0440 system:system
folders 0550 system:system
Apply them via terminal emulator or adb:
Code:
cd /firmware/image/modem_pr/mcfg/configs
chown -R system:system * {apply to everything in this folder and subfolders correct user and group}
chmod -R 0550 * {apply to everything in this folder and subfolders permissions}
find . -type f -print0 | xargs -0 chmod 0440 {apply to files only (not directories) in every (sub)folder permissions}
:MAIN PART:
Prerequisites:
- H930 (or variant, later)
- rooted
- File Manager with root privileges
- eventually a decent editor of your choice
- and a little bit knowledge about giving permissions and changing owners/groups, if needed
I won't give help about e.g. files not editable because of problems with filemanagers or root, do the search work for infos and parameters you need, or anything else, sry You have to prepare and maybe investigate some time to find some infos. You have to know, that this can lead to a brick, if you're doing weird stuff
Let's begin with backing up your complete ROM via TWRP, incl. efs, data and all you need. Backup your OP partition too:
Code:
dd if=/dev/block/bootdevice/by-name/OP of=/sdcard/OP.img
It's about 344mb in size and can be restored in recovery or ROM, adb or terminal emulator:
Code:
(adb shell) dd if=/sdcard/OP.img of=/dev/block/bootdevice/by-name/OP
Then gather some infos, for now it looks we only need MNC and MCC, which identifies your operator. Maybe it later turns out that you need parts of your IMSI too. You'll find it in LG's hiddenmenu:
*#546368#*930#
Field Test => SIM Info
You can check, if the IMS Settings are available already. If yes, then there's a high chance you don't need the "some more config" part.
Write it down and have it prepared. Now the editing session begins
First we will load our modem config for our operator. The corresponding script somehow seems broken as it should do its work with files in /data/shared folder, which isn't.
These configs can give some extra parameters and contain infos about your operator / SIM provider etc.: Open your filemanager (and/or maybe editor, if isn't integrated in fm) and open the file "/firmware/image/modem_pr/mcfg/configs/mcfg_sw/mbn_sw.txt". Here find the path for your provider. O2 Germany would be "mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany/mcfg_sw.mbn". Append these = the complete path for your config file.
Code:
/firmware/image/modem_pr/mcfg/configs/mcfg_sw/generic_/joan_glo/eu/o2d/o2d/germany
Copy your op config path, you need this for one of the following edits.
Now navigate to the folder "/data/property". There should be three files we need. If they are not there, create them with root:root, 0600 and following content pls:
persist.radio.buffet_mbn_file => the long path you copied before
persist.radio.buffet_enable => enable
persist.radio.sw_mbn_update => 1
Otherwise just edit and save them afterwards. Perform a reboot and then check in hiddenmenu => Field Test = MCFG Buffet, if this file is loaded. Should
Some more config is needed. We now need the before told MNC and MCC and maybe the IMSI. We need to point your ROM in the right direction (modem itself is done): localizing it and giving the exact operator infos. Have a check of following files and a look, if they are configured already correctly for your operator, or you have to edit them.
/OP/client_id.xml:
Is your MNC & MCC inside? If not, copy and paste an example line, edit this one so it suits both.
/OP/OPEN_EU/config/carrier_code.xml:
Same as above, but a little more complicated. Explanation with an example line:
Code:
<profile carrier="O2D" suffix="O2D" carrier_code_fast="" carrier_code_late="TLF" country="DE" mcc="262" mnc="07" mvno_type="imsi" mvno_match_data="26207200xxxxxxx" />
"Profile carrier": you find this in the long path to your .mbn file you copied before O2D is O2 Germany, edit this to fit your sim provider.
"suffix": same
"mvno_match_data": this is part of your IMSI. When your provider is already listed, compare the five numbers after your operatorcode: 26207200xx. This all together has to be the same as the first ten numbers of your IMSI. If not, edit it. This is one of the reasons for VoLTE chaos on O2D, but that's another story.
/OP/OPEN_EU/config/com.lge.ims.rcs.xml
Same as above: copy and paste a line of simoperator section and edit with your operator details. "prefix" is your country calling code.
/OP/OPEN_EU/config/featureset.xml:
Change every item which is "false" to "true"
/OP/OPEN_EU/config/vo_config.xml:
Most likely you need to create an entry for your operator with mnc and mcc. do this and change both variables to "1":
Code:
<info mcc="262" mnc="07"><!-- O2D (you can write anything here or leave it, it's commented out)-->
<prop
support_volte="1"
support_vt="1"
/>
</info>
[b][i]Maybe[/i][/b] for some rare cases this is the only edit you need to do to get VoLTE & VoWiFi running :D
Reboot now, then continue. If sth in custom.prop or build.prop is edited the wrong way, this can cause bootloops, so you don't have to do the beforedone work again. And: when something in general went wrong in /OP directories edits, you can dd your OP partition back.
/OP/OPEN_EU/cust.prop (they're all case sensitive):
ro.lge.capp_cupss.rootdir=/OP/OPEN_EU
ro.build.target_operator=OPEN
ro.build.target_country=EU
ro.build.target_region=EU
ro.product.locale.region=your region, e.g. "DE" for Germany
ro.product.locale.language=your language, e.g. "de" for Germany
ro.lge.cupssgroup=GLOBAL-COM
ro.lge.opensw=EUR-XX
ro.lge.radio_mcfg=1
persist.lg.ims.volte_open=1
Reboot.
/system/build.prop:
ro.product.locale: change to match your language
ro.lge.capp_cupss.rootdir=/OP
ro.lge.capp_cupss.op.dir=/OP
Reboot again .
:0UTR0:
The VoLTE and VoWiFi switches should be present now, a) in Phone Settings (both) and b) in Network Settings (VoLTE). We should now be able to hop into IMS Settings. You find it in LG's hiddenmenu => Field Test => IMS Setting.
First we let the IMS setting show an icon in statusbar, this way we don't need to dial the hiddenmenu code everytime we need the settings. A nice sideeffect: it shows if you're connected or not To do this tip on "Test" and activate "Show Icon". After that go back to the main screen and scroll down to "GPRI VoLTE/VoWiFi". Here you can activate VoLTE/ViLTE/VoWiFi/ViWiFi, depending on what your provider offers in your contract. Go back again to main screen, go into "Test" menu, then "Load Preset Configuration" => "Initialize configuration". Now you can do a reboot and press a thumb: maybe this was it and everything is up and running! Maybe...
For seeing if VoLTE is up you can check "Debug Screen" => "VoLTE Debug Screen" inside IMS setting.
You can also turn on VoLTE and VoWiFi indicators/symbols, which are then on the right side of your statusbar near the clock. In IMS settings: => "GPRI VoLTE/VoWiFi" => "Registration" => "VoLTE" => "Indicate VoLTE", and the same for VoWiFi. To be able to place a call in flight mode but with WiFi calling on, enable "Airplane Mode" in VoWiFi menu.
In case you experiment with IMS Setting and suddenly a com.android.phone (or other) fc occurs, you can boot into TWRP, mount data and delete the directory "/data/user_de/0/com.lge.ims" with its integrated filemanager.
K, you're done :cyclops: Pls give feedback how it went for you!
Wow. Thank you.
yeah, I hope it's written in a way everyone understands it atm it's more like a dev thread, it will be rewritten for newbies when everything is clear and fully pointed out
.. Uploaded stuff ..
Hi - thanks for this info. I'm trying to work with it, and added my files. + a few extras stuff> actually not really sure how to do this .... any help? ... Thanks I have a US998 phone.: but want to get the Canadian settings all working ; specifically for Freedom Mobile ( aka : Wind ) --- the files are from a saved backup ( dump ) {{ the uploaded files are from a backup of the H933 canada firmware dump }} ... I'm currently using the US998 kdz firmware on the phone ....
let's start with
- do you see "MCFG Buffet" in your hiddenmenu?
- can you list all the content (the main directories) in your /OP folder pls?
- does the firmware modem config folder exist and is your provider inside?
- and where does your ro.lge.cupssgroup point to? (adb shell getprop ro.lge.cupssgroup)
I don't know the specialities of other variants, especially the offered providers. I don't even know if this is possible and which files you uploaded to your phone. can you either list them or point to them with a link eventually?
OK thanks - I'll work on this some more tomorrow -- I don't know where the files I uploaded went to! > but I uploaded >Folders>>> Carrier Config, Modem_pr, qcril_database, vendor, wifi & build.prop. All files were dumped from a working Phone loaded with the Canadian .Kdz H933. ... > ok so I actually took all those files,and overwrote the files om my current phone setup which is US998 .Kdz -- didn't even crash the phone <<< Go figure. I just had to clear the cache and dalvik cache. VoLTE may be working, but my Carrier has a very limited VoLTE service... so I cant check right now. VoWifi is not working. Every setting and menu has it turned "on" but is no working. .... tomorrow I'll follow your instructions after I do a fresh install. of the .KDZ. ..... be well
be warned: this can be time consuming and causing headaches, too stock files would be the best to start with.
is it a native us998 phone? it's the one one can "frankensteining", isn't it? you've overwritten these files and partitions, when I understand you correctly?
you should get hands on following stock partition disk dumps and folders first (kdz won't help as all these files are preloaded and can't be flashed via kdz):
- canadian OP partition (the more important one) (canadian_OP.img <= example filename)
- US998 OP partition (for being able to revert back to stock and trying to get volte/vowifi running with only some edited files on stock us998 partitions, only a few added files or maybe folders from canadian OP partition and only the .mbn file for your provider, taken out of firmware modem config folder). this one shoukd be flashed and worked with.
- stock system image (kdz flash us998)
- clean unencrypted data partition (factory reset and then completely set up with your apps and settings, no db or ither files copied).
- you've got a backup of your stock efs partition?
try to keep your phone as clean as you can as this can only be of help about not being confused. are there gsm/(w)cdma/band differences between us998 and canadian 993?
this could go an interesting way let's see, maybe we get it is wifi calling enabled on your contract? I wasn't able to determine this out of your post.
there's the possibility to edit the thresholds when wifi calling aborts and switches to cell telephony or volte. it's located in /system/etc and inside a filename called "andsf_your_provider_code.xml", for o2 de it's named "andsf_26207.xml". I've set every threshold to -90, this way wifi calling is still working with only one or two bars wifi reception. otherwise it would abort just too early and switches to other telephony bands.
US998 mbn-files
Thanks for the detailed info.
Not working for me. I managed to add my operator and enable IMS but can't figure out how to make IMS register. Might be because my operator is a little more retarded and uses IPv4 only. No idea where to set that policy, it isn't in IMS settings anymore on the V30.
sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?
Hi. Thanks for this. Is there any way that this can be applied to aosp ROMs?
Those mcfg files are found inside the modem partition and you can pull them out from any kdz.
Do you have an idea where this is located? (/nv/)
Edit: Also, added some picture showing volte working... when it's not (switching back to something else)
you're really sure about this? since I've flashed a kdz and a modem and unfortunately this didn't bring back these files on my phone maybe I did sth. wrong, this is really interesting now. thought they were on efs partition; but these nv files should be on efs. I'm not really sure about that, maybe someone other can finally confirm :good:. edit: I remember I've got carrier services installed, would be interesting if this makes a difference. I hardly believe but try it:
https://play.google.com/store/apps/details?id=com.google.android.ims
about aosp: there's much more needed, proprietary files and more config inside sources etc pp. I evtl. wanted to do compilings again in winter, I wanted to try this but I need additional ssd space before
Oh sh*t...
I guess I lost my efs partition then...
I tried a bunch of stuff from your first post... sadly, I don't have an /OP/ directory at all... and when I try to force the mcfg mbn (from my sdcard lol, cauz my carrier is not provided in the us998 modem)
Edited a bunch of stuff in my build.prop to make it look more like the canadian one.. but it still doesn't work (even lost the volte option now in the mobile setting menu..)
Also, I tried to flash my canadian modem files... sadly.. the phone boot but the modem doesn't initialize at all... (no wifi and no mobile network)
aye, sh¡t... and there's no efs backup from your phone done / available as it sounds. you lost your IMEI too??
can you check the directory
/dev/block/bootdevices/by-name
and see if there's an OP "file"? eventually only the script which mounts it is broken. if I remember correctly there was a thread about regathering the IMEI or at least fixing some stuff on efs. maybe this helps you, unfort. I don't know where it was, you have to search yourself.
k, sleeping now, it's hard for me these days after my shoulder operation... hopefully we get your phone back running! I'm optimistic flashing a efs backup and changing the imei back to your original one for example. don't know if this is possible, but how often did I think "sh¡t, now it's over, phone's bricked" and then a solution appears out of nothing. you should've seen my face in the moment volte came.up on my phone xD xD xD
see you later be optimistic!
Oh sorry! I still got my efs partition.. I thought it would get overwritten when doing the frankenstein method.. But I guess not.. Is there any way I can debug why the modem doesnt work at all when flashing the canadian one while using the us998 system?
there is but I don't have it in mind atm it's explained here at xda somewhere, logcat and dmesg is used for that :good: can be that it is bands related? so you have to unlock bands in your modem settings? edit: most likely not as wifi is dead too...
seadersn said:
sounds like setup session in IMS setting. go into gpri volte/vowifi setting and try enabling volte and vowifi only, then tap on "call" menu entry. choose "volte" and tip "use sip preconditions" there, use the same setting for "vowifi". check "subscription" in main menu and "IMPI" there: is there a connection adress inside? example:
your_imsi@ims.mncXXX.mccXXX.3gppnetwork.org
replace mnc and mcc with yours but add a zero at the first place of your mnc. for o2 de's mnc which is 07 it looks like
your_imsi@ims.mnc007.mcc262.3gppnetwork.org
then try test menu and restart ims process. or perform a reboot.
but you'll have to investigate more, for yourself. what's your exact provider and mnc mcc?
edit: can be you need an IMS apn for your provider. in it you can set the protocol versions. what's logcat telling?
Click to expand...
Click to collapse
I already tried to set IPMI with my data like [email protected] but IMS still don't register and the setting doesn't stick. it always reverts to a default like [email protected].
I also created the ims APN but it doesn't help with anything.
I'm still digging but so far I have no clue what's going on.
hmm, did you try configuring sip telephony? for o2 germany the registration looks like
country code + phone number @ telefonica.de = (for germany) [email protected]. have a look at /data/user_de/0/com.lge.ims/shared_prefs/impu_list.xml
(user_de: I don't know if this is indicating the language the rom uses? so for an english language build it can look like user_en? I don't know...).