I am trying to get my SMS/MMS messages from an old phone (not rooted) onto my OP8P (rooted). I took a backup from the old phone and copied it over (I've tried this with Swift Backup and also SMS Backup and Restore).
When I restore to OP8P, the messages consistently get associated with the wrong SIM/phone number. I've tried several things - swap the SIM slots and restore, restore with just the target SIM, restore with no SIM and insert the target SIM, swap the target SIM back and forth with the other slot empty, and even wipe data (Titanium Backup) from several system apps with SMS/Phone/SIM in the name.
In Google Messages, if I inspect a message, it will say "UNKNOWN_NUMBER" if I have no SIM or just the target SIM in. As soon as I insert the non-target SIM (alone or along with the target SIM), the messages update to use the non-target phone number. OP Messages app is similar behavior (except the to/from line is missing at first instead of showing "UNKNOWN_NUMBER").
I looked at the XML export from SMS Backup and Restore and noticed it does not save data for the target phone number. So for example, outgoing messages have "address=Foo type=2" and incoming messages have "address=Bar type=1". I tried looking at the Swift Backup but it is an encrypted 7z file and I don't know the password.
I think what's happening is that the OP8P had the non-target SIM card in first and so it set the default number somewhere internally. So now whenever I restore, it's being associated with that default number. Does that make sense? If so, can I somehow clear this default number (without a full factory reset)? And if not, what is going on?
I'm also open to suggestion if there are any backup/transfer apps that can handle this properly.
EDIT: Looking closer, it looks like whatever Swift Backup actually does is a little bit better. Regular SMS messages are associated with the target SIM, but not RCS/MMS.
SOLVED
I did a little more research and digging and was able to fix.
Each SIM card has a "Subscription ID", which persists across reboots and slot changes. This is represented in /data/data/com.android.providers.telephony/databases/mmssms.db as sub_id in the sms and pdu tables.
As it turns out, my target SIM got sub_id = 2 and non-target SIM had sub_id = 1 (probably because I had that one in the phone first). The restore apps I tried did not set sub_id in the tables that matter, so they defaulted to -1. I suppose the messaging apps try to use 1 instead.
Thankfully, the DB is a simple SQLite DB that I was able to modify and put back.
SQL:
update sms set sub_id = 2;
update pdu set sub_id = 2;
Related
Hi,
I have a unrooted absolutely Stock Nexus S T-MOBILE version which I manually updated to Ice Cream Sandwich 4.0.3 using the official update file.
The problem I'm facing is that ever since I upgraded to ICS I'm unable to send SMSs but I can receive SMSs just fine. I did some searches and realized that the SMSC should be a valid number where as mine is showing 00. I tried to edit this by going to *#*#4636#*#* > Phone Information > SMSC update. But every time I try to update it, it says update error.
I'm using the phone in India Mumbai and the SMSC should be +919820005444 (verified on my friend's Android Device.
I also read that this could be an error due to a faulty SIM card but when I used the same SIM card in another device it works perfectly. I also tried other SIM cards in my phone, all of them are unable to send SMSs.
Please help!
Use this guide: http://forum.xda-developers.com/showthread.php?t=979564
I was unable to send/recive mms on ICS if i were on 2g/3g, but wifi worked.
Finally found out how to fix it today (at least my issue).
I wrote down whatever info i had in the APN-settings for wap and mms on my phone and merged them, putting all the mms info in the wap-apn, where none existed and added an extra ",mms" to the apn type-field.
Mine dont work too i am in uk called cs told me tobcheck apn still nothing
Sent from my Nexus S using Tapatalk
I just installed CM 9.1 on my Galaxy S i9000. It's an unlocked model but I'm on T-Mobile. I've had the same SIM since about 2000 or 2001. I had been using Gingerbread until yesterday.
I can't get it to make calls or send texts. Any time I place a call, it beeps and says "Call ended", either immediately or after a few seconds' silence. Messages always fail to send. Anyone calling me gets my voice mail and I don't get any messages. However, it can see the network, the signal is good, network data functions work fine (better than on Gingerbread actually) and Wi-Fi works. When I look in "Settings / About phone / Status", it shows "mobile network status" as Connected. I've tried manually reconnecting to my mobile network several times; it connects, but still can't place calls or texts.
Also, when I go into the phone settings and select "My phone number", I get a "Network or SIM card error" message.
Did you lost your IMEI?
Try this: http://forum.xda-developers.com/showthread.php?t=1841250
1) Download a file explorer with root (Root explorer / ES File explorer) from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
Hit Thanks to xsenman in the thread above
Aviatoru said:
Did you lost your IMEI?
Try this: http://forum.xda-developers.com/showthread.php?t=1841250
1) Download a file explorer with root (Root explorer / ES File explorer) from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
Hit Thanks to xsenman in the thread above
Click to expand...
Click to collapse
Thanks very much - it was indeed the IMEI that was the problem. I posted a comment on the CyanogenMod forum - http://forum.cyanogenmod.com/topic/60867-cm-91-t-mobile-uk-no-calls-or-sms/#entry351510 - and an entry on my blog - http://www.blogistan.co.uk/blog/mt.php/2012/10/22/upgrading-your-android-theres-no-easy-way.
question: how to save network apn on meizu mx
details: meizu mx 032, using flyme 1.1.7(a9904)
with giffgaff sim
giffgaff sim recognised automatically, i.e. shows when i pull down main screen
however giffgaff doesn't show in network > apns
which show under 'apn access point' heading = o2 mobile web, o2 prepay, tesco.. and under 'mms' = o2 mms
the problem is that saving apn (existing of new) corrupts network/apns
tried:
1. with old flyme version (probably 1.1.4 or 1.1.5) with same problem
2. with flyme 1.1.7, if i just open existing apn, say tesco.. and only change the name to tesco2.. and click save.. and restart the android..... then it's all gone.. and problem crept
3. even after factory reset new apn addition, like for giffgaff.. fails. and then it's all gone
4. reset to default doesn't bring anything
5. and neither does restart/reboot
workaround: only factory reset works
debug:
1 wanted to find and edit config file where apn entry resides, but until now couldn't find the config file, as it must be somewhere in system partition as i can't access to it, even after enabling usb debugging, as these partitions aren't visible when i connect to computer... i can see data partition though
2. also disabled flyme sync, and google sync, to ensure that it's not syncing with my old copies of network.. as factory reset followed by sync(may be) caused same problem
3. later on will probably try with o2 sim
4. tried with android apps like 'giffgaff apn', 'apn manager, 'apn backup and restore', etc.. none work.. and these apps do say that this version of android doesn't allow apn 'saving'..or something like that
Hello,
N910C, COJ5, noroot. Suddenly my phone stopped to use fingerprint sensor and backup password I am providing is not being acceptable.
Short list:
- notifications, network, sms and incoming calls are working, BUT nothing else
- after restarts, removing battery, tries to use ODIN(3.07 & 3.10) or TWRP or kernel with permissive - not working (blocked by R/L) - I wanted to use root privileges to remove files in /data/system responsible for fingerprints and backup password.
- ADB is working
- I want to recover data before wipe - some free soft like Android Recovery Tool or sthg like this ?
Any ideas?
Thanks in advance!
--
Szymon
I see three ways:
-Try to unlock with the fingerprint, it will give you the option to enter a secondary password. Put a random pass 5 times until the device blocks you to keep entering wrong passwords. After that, a new button saying "Unlock with your google account" should appear. Touch it, put your email and password and wait for a couple of seconds. The device will unlock and will set the lockscreen to "Swipe".
-If that doesn't work (rare), try this, it shoud work: http://forum.xda-developers.com/not...ass-lock-screen-pattern-password-pin-t2948336 (since your device is locked you can't access to the MTP functions. You have to put the zip file in a external sd card and flash it with TWRP.
-If that doesn't work either (dafuq?), make a data backup in TWRP ("Backup" option, then select data only), wipe your device, flash a rom and then flash the backup again.
Also remember: "Wipe data" option in TWRP erases all ylur apps and configs, but your pesonal info like photos, documents, downloads, etc will still be at there.
galaxynote2 said:
I see three ways:
[...]
Click to expand...
Click to collapse
I see that you did not read my post
All of these 3 options you mentioned are not possible.
Any other ideas?
I just copied via adb in shell all important files from internal memory and now after I wiped it out I got strange info that "This device is locked because of an abnormal factory reset"
I am not using Find My Mobile Samsung service so WTF ?! Why is it asking me for something that I am not using and it will be not working ???
Regards,
add-on: there was a Find My Mobile by Samsung block, but I used some mystery account I forgot about Now everything is up and running
I'd like to use Android Messaging as my default MMS/SMS app but there doesn't seem to be the ability to send group messages. In Android messaging under advanced I don't have an option for group messaging.
The stock messaging app does have options for group messaging and works fine, just not android messaging.
anyone else know how to fix? On T-Mo USA.
Thanks,
I'm interested in this as well. Also using T-Mobile USA. Group messaging splits into multiple sms's and the option for group messaging isn't present in the settings.
For now I'm just using Textra, but I'd love to be able to ditch it.
There are many threads on this all over the place but I'm just going to bump here. If you have root you may be able to do something about this.
As documented here:
https://talk.sonymobile.com/t5/Xper...droid-Messaging-App-missing/td-p/1272979#gref
If your carrierconfig contains enableGroupMms false, then Android Messaging does not display group MMS as an option.
On Android 7.x at least, the base location where carrier config is stored is in /system/priv-app/CarrierConfig/CarrierConfig.apk. Do not modify this. But if you can browse the package with Root Explorer you'll be able to see whether it contains this enableGroupMms false in either of:
res/xml/vendor.xml
OR assets/carrier_config_###### (where ###### is the MMC/MNC number pair for your carrier, e.g. for Telus in Canada it's 302220)
My ROM did not have enableGroupMms false in either of these files for my carrier.
Then there may be additional such configurations in the oem partition, which supersedes the base one:
/oem/overlay/com.android.carrierconfig-res-###.apk (### was 305 for my ROM)
/oem/overlay-###/com.android.carrierconfig-res-###-###.apk (overlay-122 and 310-122 for my ROM)
In my ROM neither of these APKs had an assets folder, but they both had a res/xml/vendor.xml that contained enableGroupMms false.
So the first thing I tried doing was renaming the OEM overlay APK files to .apkz instead. That made no difference. However it is worth noting that this did not seem to create a problem with Magisk systemless root. I still passed SafetyNet check.
Then I read some Android documentation suggesting these values get cached. So I did a more thorough file search and found:
/data/user_de/0/com.android.phone/files/carrierconfig-com.android.carrierconfig-###################-302220.xml where the long string of #s is the IMSI (SIM card number). Bingo! Inside this XML file enableGroupMms was false. I switched it to true, rebooted, and could send group MMS.
Phew!
Try installin carrier services from Google Play Store