yashsingh1/xdaforums huggingface dataset:
[Honor 5X Questions & Answers] subodhverma21:
Hi yuweng,

Thanks for such a thread. This is almost all knowledge in one place.

I am thinking of compiling my own ROM. Going through your thread.

Will be installing BBQ Linux very soon.
[Honor 5X Questions & Answers] PalakMi:
Good luck
[OnePlus 3 Questions & Answers] akashyap007:
Hy guys .. can anyone tell me is any ultra power saving mod is available for one plus 3 or not like samsung galaxy s6 type of.. or how can save battery other then the stock power saving mode...

:good: thanks in advance
[OnePlus 3 Questions & Answers] abhibnl:
In OOS, you will find the standard battery saving mod. Use less mobile data and more Wi-Fi, control the sync duration, use medium brightness etc. these could help you with battery life. For me, this is the best battery life i have seen in any phone i have used.
[OnePlus 3 Questions & Answers] ming3r:
I think its called turning off the phone.
[OnePlus 3 Questions & Answers] Joyo-rocker:
Hahaha....!! True that lol
[Nexus 5X Q&A, Help & Troubleshooting] dlegit:
sorry if it seems like this is an easy one at first but i've been having some strange issues here.

i installed the 7.0 OTA on a new 5X that i'm about to switch to (coming from another 5X with a broken mic). both rooted. did a clean wipe on the new one with 7.0. moving data from the old to the new i can't get sms/mms to copy over. using titanium, rom toolbox, and carbon it won't work right. at first when i used carbon it only restored texts up to april this year. so i wiped them out and tried titanium etc. nothing works. then i went and directly copied the mmssms.db (and all the files) from /data/data/com.android.providers.telephony and still nothing. there were no texts showing in messenger app (tried textra too) so i sent a few test messages. those are showing up. but when i deleted the entire telephony folder within twrp, wiped cache and dalvik, rebooted those test messages are still showing up! when i browse to the new telephony folder that android created there's nothing in the folder. yet the text messages are still showing up. also the call log is still full (it actually restored properly with titanium).

i can't find any info that says the texts are stored anywhere besides the mmssms.db file so anyone know what i'm doing wrong?

recap:

-backed up sms/mms with carbon, titanium, rom toolbox (on android 6.0.1)

-fresh install 7.0

-restored with all those apps

-*partial restore*

-wiped com.android.providers.telephony folder

-manually copied backed up files into com.android.providers.telephony folder

-*nothing*

-sent a few texts through the app

-wiped com.android.providers.telephony folder

-*can still see texts with nothing in the folder*

-------------------

SOLVED

found it in /data/user_de/0/com.android.providers.telephony on the device running android N. don't know if it's like that for everyone but that's where it is on mine.
[Nexus 5X Q&A, Help & Troubleshooting] wind0zer:
I used Titanium backup to backup call log/SMS from M and restore in N (clean install) with success.
[Nexus 5X Q&A, Help & Troubleshooting] jsgraphicart:
Does your old phone still have all the texts you want on it? If so, use SMS backup and restore from the play store. Backup on the old phone, transfer the files to the new one and restore. It seems like you're doing more work than you have to just to transfer texts.

https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore&hl=en
[Nexus 5X Q&A, Help & Troubleshooting] dlegit:
yeah i get it. it's a little much. i guess it's become more about how this thing is storing the texts if it's not in the usual place.
[Nexus 5X Q&A, Help & Troubleshooting] dlegit:
well if anyone is interested i found on the device running N that the new location is /data/user_de/0/com.android.providers.telephony. don't know why it's like that for mine but maybe it'll be useful for someone else too.
[Nexus 5X Q&A, Help & Troubleshooting] mrniceguy1437:
I was able to extract the 'databases' folder from this location before restoring, but I'm having trouble restoring. Any ideas to restore these .db files to show in Messages app?

I tried to just copy them back to the /data/user_de location mentioned above, but also noticed there was no 'databases' folder there (I'd received one 2FA text from Google since doing the fresh restore) but even with root access couldn't properly create the folder. I then checked the /data/data location mention by OP and noticed there was a 'databases' folder there, I was able to paste my .db files in the folder, but they're still not showing in the Messages app.

Any input is much appreciated. At the least, I have the files, can open them in Windows with text editor and have confirmed there is conversations in there, my mmssms.db file is about 3 MB.
[Nexus 5X Q&A, Help & Troubleshooting] criza:
I had the same problem, so I deleted the *.db-journal files, and after that I could start the SMS app and all messages were there!
[Nexus 5X Q&A, Help & Troubleshooting] ksupreme:
Error.
[Nexus 5X Q&A, Help & Troubleshooting] cyberangel22k:
Have been doing this since CM12 up to CM13. When I tried LineageOS 7.1.1 a few days ago, I restored my mmssms.db backup just like I always do. Found out that it was not located in /data/data/com.android.providers.telephony/database anymore so I found this thread. The problem is, if I put my mmssms.db backup at/data/user_de/0/com.android.providers.telephony/database, my sms app crashes. Tried to delete *.db-journal files too but still my sms app crashes and the only way to make it work again is to wipe my data.
[Nexus 5X Q&A, Help & Troubleshooting] Silly22:
I found that you should delete the contents of /data/user_de/0/com.android.providers.telephony/databases and the app_parts folder, then reboot. Then do the manual move of your attachments (into app_parts) and the .db files (into databases). Then reboot again BEFORE opening your SMS or messaging app. This addressed the messaging app being unable to load MMS for me, but I don't know if this will help your crash problem. I'm on OxygenOS 7.0.
[Nexus 5X Q&A, Help & Troubleshooting] cyberangel22k:
Thanks for your suggestion. I will try this later. :good:

Tried this:

-deleted contents of /data/user_de/0/com.android.providers.telephony/databases

-rebooted. A new set of db files were generated automatically

-overwritten mmssms.db

-rebooted. Messenger app does not crash anymore but cannot load messages and cannot create new message.

-tried steps 1-3 again

-after reboot I cleared the messenger's app data but still same result.

I will convert my backup now to xml and restore it via app until there's another way of restoring it manually.

Using lineageOS BTW. Thanks.
[Nexus 5X Q&A, Help & Troubleshooting] mydeardiary:
I've been able to restore SMS/MMS/APN data from Titanium Backup on LOS 14.1

I just need to copy and keep file modes and ownership of "com.android.providers.telephony" from /data/data to /data/user_de/0 folder. The built in tar command will do that just fine

# tar -C /data/data -cf - com.android.providers.telephony | tar -C /data/user_de/0 -xf -

If you have copied the folder manually, just change the ownership of com..android.providers.telephony to "radio:radio" (user=radio, group=radio). No need to do this with tar command above, since tar when run as root will keep file and folder ownership.

Now waiting for Titanium Backup to support "user_de" system folder backup and restore on Android N based ROMs.
[Nexus 5X Q&A, Help & Troubleshooting] mageus:
Can anyone explicitly confirm this works copying from a <=6.0 system to Nougat?

Here's what I gather:

- Mrniceguy can't get it to work

- criza got something to work

- for cyberangel, it crashed

- silly got it to work on Oxygen

- mydeardiary got tar to work (though your tar command looks a bit funny)

My Droid Turbo's (6.0) screen died, but I can access ADB. I tried copying the mms db to a Galaxy S4 (5.0.1) without success. When I copied the mmssms.db and journal, Messages showed an empty history. I made sure the permissions were set (660, radio:radio). Copying the telephony files over caused the Phone app to constantly spam a FC dialog until I turned the phone off. Restoring the original (S4) files fixed it.

I don't want to risk my shiny new Nexus 5X unless I'm sure that just copying the files over will work.
[Nexus 5X Q&A, Help & Troubleshooting] mageus:
I can confirm that copying the database from an older version to Nougat doesn't work.

- in /data/user_de/0/com.android.providers.telephony/databases:

- backup all files

- delete mmssms.db, mmssms.db-journal

- reboot

- copy in mmssms.db, set permissions 660, radio:radio

- reboot

- run Messages

empty message list

when trying to create conversation: "Failed to create conversation, please try again later."

- restoring original files fixes messaging

I suspect there's something to the format of the mmssms.db file that is different across releases, or between phones.
[Nexus 5X Q&A, Help & Troubleshooting] Serachja:
I finally got it working... I was eagerly ready all the posts here.

Here is my solution:

After freshly installing the new LineageOS I installed Root Browser and BusyBox (obviously you need root permissions for this). Then I opened in Root Browser the location /data/user_de/0/com.android.providers.telephony/databases. I made a backup of the files inside in a subfolder. I copied my old files into the now empty folder (adb root, adb push.....--> six Files: HbpcdLookup.db, HbpcdLookup.db-journal, mmssms.db, mmssms.db-journal, telephony.db, telephony.db-journal). Then I gave to all xyz.db files the read/write permissions for the owner and the group, and for the journals, I gave them only read/write permissions from the owner (I got an error that the permissions couldn't be applied --> ignore it, it does get applied). To all six files, I changed the Ownership from root to radio. --> rebooted --> no crashing but no messages visible --> installed the "SMS from Android 4.4" from the PlayStore--> set this SMS app do be de default one (I set the mark to not delete old messages in the settings) --> this app restored all my SMS that I had lost.

Its quite some trouble to get to the files but in the end it seems to work.

I hope you can reproduce this procedure...
[Nexus 5X Q&A, Help & Troubleshooting] gaglia83:
Same problem here with latest Lineage on a rooted serranoltexx (Samsung Galaxy S4 mini LTE). I think something changed in the last update, but I don't understand whether it's Android's or Lineage's fault.

I give you more information, as it seems like a recent issue which troubles a lot of users - I found many similar threads, but no solution so far.

On my old Samsung S2 I was using the app SlightBackup (free, from F-Droid) to backup SMSs. However, copying the SlightBackup database (.xml format) on my new phone and reinstalling it there doesn't seem to work, so I decided to copy manually the mmssms.db file. Also in my case, the new directory seems to be /data/user_de/0/com.android.providers.telephony/databases (however, there is also a file called telephony.db which has a symbolic link in /data/data/com.android.providers.telephony/databases )

Still, my SMSs do not show up, and moreover the "contacts" app crashes. I tried deleting all the content of the folder and then the messaging app crashes (a full reboot restored the content, however, and the functionality of both apps with it).

Interesting to notice that all the *.db and *.db-journal files in the folder do not change size even if I send/receive SMSs, so I guess they are there just for compatibility, and do not actually store the messages. The "real" database is probably somewhere else, but I have no idea where to look for.

Help would be really appreciated. I'm willing to send 0.01 BTC to the first person who finds a working solution :)

P.S.: yes, I have also taken care of the filesystem permissions of the .db file, which is something only mentioned in this thread amongst all those I've found, but important I think. In my case the .db file is 660 with owner radio:radio, same for the .db-journal but permissions 600.

P.P.S.: installing third-party apps to restore my SMSs is not an option in my case. I know about working apps in the Play Store but I don't want to use them.

P.P.P.S.: yes, my phone is rooted, and I am not using third-party messaging apps, just the default one.

This doesn't work for me.

Thanks for the hint. Your solution probably works because the app "SMS from Android 4" is still using the old location/format of the database. This strengthens my idea that in the last update the situation has changed for the default messaging app (as I said, I don't want to use third-party apps in this case).

That's really frustrating... it's crazy that such a simple thing as the local SMS database creates so much trouble :D
[Nexus 5X Q&A, Help & Troubleshooting] ognevod:
Here is new db location: /data/data/com.google.android.gms/databases/icing_mmssms.db

You can also find a lot of things in that folder :)
[Nexus 5X Q&A, Help & Troubleshooting] gaglia83:
Hey, thanks but unfortunately that doesn't work for me: I don't have that location at all, the only com.google folder I have is com.google.zxing.client.android and that doesn'tcontain the mmssms.db
[Nexus 5X Q&A, Help & Troubleshooting] Lesking72:
It's in the same place on my Galaxy S6. Does this file also contain the APN settings on your phone? I was able to edit it and enable my phone's native tethering
[Nexus 5X Q&A, Help & Troubleshooting] gaglia83:
As I said, unfortunately that doesn't work for me :( I'm using Lineage OS 14.something (nightly). At this point I just gave up and deleted all my old SMSs, there was nothing too important anyway. But it still kinda suck. Well, never mind.
[Nexus 5X Q&A, Help & Troubleshooting] hopkinskong:
I may have a solution for this, i think the best way is to manually upgrade the database to the newer compatible format. There are some vendor specific column in the old message database, for example, I am upgrading my HTC sense ROM (6.0) to a Google Play version ROM (7.1.2), those vendor specific column may mess up with the database.
[Nexus 5X Q&A, Help & Troubleshooting] gaglia83:
Sounds great, please let us know if it works :)

---------- Post added at 08:51 PM ---------- Previous post was at 08:46 PM ----------

Ehm, just to be clear: please consider the bounty expired, because 1) I gave up with this problem on the old database, I am using a fresh install now; and 2) BTC is freakin' skyrocketing, and I only have a few cents left anyway.
[Nexus 5X Q&A, Help & Troubleshooting] hopkinskong:
OK, I knew it was SELinux messing up with me all along. By viewing the logcat, it can be traced that there were SELinux Audit logs indicate that the mmssms.db were tried to be locked by the Messaging app but got denied:

10-25 02:45:46.868 1512 1512 W Binder:1126_5: type=1400 audit(0.0:707): avc: denied { lock } for name="mmssms.db" dev="mmcblk0p47" ino=483781 scontext=u:r:radio:s0 tcontext=u:object_r:system_data_file:s0 tclass=file permissive=0

For others encountering the similar issue, i recommend:

0. Doing this in recovery mode, I really don't like the Android system is messing with the files

1. Try copying your old mmssms.db to /data/user_de/0/com.android.providers.telephony/databases

2. Make sure the permissions for *.db are 660, *.db-journal are 600

3. Make sure owner is radio:radio

4. SELinux Context Check: ls -alZ

The SELinux context type should be "radio_data_file" for all the *.db and *.db-journal, change the context type by:

chcon -t radio_data_file *

This is my permissions, take it as a reference:

drwxrwx--x 2 4096 Oct 24 18:41 u:object_r:radio_data_file:s0 .
drwx------ 5 4096 Oct 24 18:35 u:object_r:radio_data_file:s0 ..
-rw-rw---- 1 57344 Oct 24 18:35 u:object_r:radio_data_file:s0 HbpcdLookup.db
-rw------- 1 8720 Oct 24 18:35 u:object_r:radio_data_file:s0 HbpcdLookup.db-journal
-rw-rw---- 1 770048 Oct 24 18:10 u:object_r:radio_data_file:s0 mmssms.db
-rw------- 1 33344 Oct 24 18:36 u:object_r:radio_data_file:s0 mmssms.db-journal
-rw-rw---- 1 737280 Oct 24 18:51 u:object_r:radio_data_file:s0 telephony.db
-rw------- 1 12824 Oct 24 18:51 u:object_r:radio_data_file:s0 telephony.db-journal

5. Reboot and profit

If this does not work, or your Messaging app still crash, I have written a small python script to update the database file to a newer version:

Note that I have ignored two columns in "thread" table, it may or may not cause issue, but I have no issue so far.

https://github.com/hopkinskong/android_message_db_updater

Tested on python2.7 on Windows, not tested on python 3.0.

Generate a newer version of the mmssms.db, and push to the device, modify the permission and SELinux Context as mentioned above.
[Nexus 5X Q&A, Help & Troubleshooting] HondaCivicType-R:
Hi hopkinskong,

I downloaded your Python scripts and the application version 2.7 as well.

I had a look into your main.py file and I understand what you're actually doing with it. But what are the required steps in Python (How To) to convert my old saved SMS database into the new format for Android 7.0 without loosing any data or SMS/MMS? I'm not familiar with Python.

Kind regards,

Manuel
[Nexus 5X Q&A, Help & Troubleshooting] hopkinskong:
Have you tried to modify the SELinux permission first?

EDIT: Usage updated on the github repo.
[Nexus 5X Q&A, Help & Troubleshooting] HondaCivicType-R:
SElinux

Yes, I have.
[Nexus 5X Q&A, Help & Troubleshooting] sjevtic:
Differences in vendor-specific implementations aside, I think there is a bit more going on here. I am trying to migrate my Galaxy S7 from a Marshmallow SuperMan ROM (1.19.1) by [MENTION=5899304]Tkkg1994[/MENTION] to a Nougat SuperMan ROM (2.8.0). Redirecting the restore of databases/mmssms.db* and the app_parts folder from /data/data/com.android.providers.telephony to the new location (/data/user_de/0/com.android.providers.telephony) as suggested earlier in this thread produces a stock messaging app that hangs with a "Refreshing" message; SELinux is permissive by default under this ROM, so I doubt that's the issue.

At a minimum, it looks like the "part" table in mmssms.db would have to be updated for MMS attachments to work right after the migration. Notably, the "_data" field contains the absolute path to the attachment content (if it is not just text stored in the "text" field) at the old location.

Has anyone brought their SMS/MMS data from Marshmallow to Nougat simply by moving the databases with the possible addition of some simple transformations? I'm trying SMS Backup and Restore now, but it's painfully slow.
[Nexus 5X Q&A, Help & Troubleshooting] RamonXick:
sorry if necro but you just save me from major headache and hours of reset/restoring my phone, thanks man
[Moto G Q&A, Help & Troubleshooting] Gache:
The wifi on my Moto G (1st Gen/XT1032) won't turn on - on stock 5.0 and 5.1, the toggle slides across and immediately slides itself back. On Cyanogenmod, the toggle is greyed out altogether.

This sounded pretty similar to the "corrupt /persist partition" type problem. So I rooted the phone, flashed TWRP and tried the replacements for WCNSS_qcom_wlan_factory_nv.bin suggested in various threads here at XDA.

At first this didn't have any effect. I tried changing permissions on the file with chmod +x & wipe cache, which resulted in wifi coming back on, but after rebooting it was back to "off" again. This process didn't work when I rpeated it, either.

Some threads suggest editing the file to insert the phone's MAC address. Unfortunately I don't have this as one of symptoms is MAC "unavailable" in Wifi -> Advanced. Also, looking at the file in a hex editor it's not clear where the MAC should go if I had it!

As wifi did come on properly once I hope it's not a hardware failure. I can get adb logs or whatever might help diagnose the problem, just let me know. But I'm at a loss for what to try :(

Does anyone have any suggestions?
[Nexus 6 Q&A, Help & Troubleshooting] dberthia:
I've been avoiding all the N developer releases. Once I get the official N installed, what's the best root method? Can I just flash SuperSU with TWRP like on M? I'm on TWRP 3.0.2.0, but thought I read something about needing a new version for N. 3.0.2.0 looks like it's the latest release for the N6.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Waiting for a prerooted stock based rom is an option.

Twrp 3.0.2.0 seems the latest Shamu version.
[Nexus 6P Q&A, Help & Troubleshooting] thomase00:
http://forums.androidcentral.com/nexus-6p/715068-immersive-mode-quick-settings-tile-nougat.html
[AT&T Note 7  Questions & Answers] username1988:
Can someone point me to a list of packages/ apps that users can disable (ATT Note 7)?

If something like that doesn't exist, please post the packages to disable and i'll keep updating the first post with all your answers.

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] CalauDude:
So I did manage to root it and installed TWRP 2.8.7.0 and e.g. flashed the darklord rom with twrp on boot but then on reboot I only get the message like "could not boot normal" odin active

is there a dummy solution how to prepeare and check my note 3 so I can flash custom firmwares
[Galaxy Note 3 Q&A, Help & Troubleshooting] manne48:
Did you flash a kernel after rom flashing?

Note 3x
[Galaxy Note 3 Q&A, Help & Troubleshooting] CalauDude:
no

I didnt find any link where to download that DL Kernel 2.0
[Galaxy Note 3 Q&A, Help & Troubleshooting] CalauDude:
ah I understand for GPL reasons here is no kernel included so better searth for the rom on other site whrere its "complete "
[Galaxy Note 3 Q&A, Help & Troubleshooting] DaOldMan:
Search for Darklord or Lss kernel in our thread. Install rom and don't reboot. Flash kernel immidietly then you can boot.

Good luck!

Phronesis team member
[Galaxy Note 3 Q&A, Help & Troubleshooting] CalauDude:
I found the Darklord rom with included Kernel which worked out of the box with a single flash
[Xperia Z3 Compact Q&A, Help & Troubleshooting] House3272:
Been on a custom Loli rom since a year or so ago when I first got the Z3c.

Lately too many things stopped working on it so I figured it was time to upgrade to a Marshmallow one.

Went with this: http://xdaforums.com/z3-compact/orig-development/rom-t3435264

got the latest flashtool and flashed the latest stock rom 23.5.A.1.291 for USA as per the instructions

but none of the root options worked , so I started using adb and did some command line stuff and now nothing works except fastboot.

Flashmode doesn't even register anymore as upon inserting the usb with device off and vol.down held, the led blinks to red for bout half a second, then flashes to green for about a nano second before turning off.

Is there a combination of boot.img/recovery.img that'll bring this back into working order?

I haven't touched this stuff in over a year so forgive me for my ignorance~

Update:

I flashed TWRP via command line and was able to boot into it!

But /system, /cache, and /data are all broken (failed to mount & invalid argument?)

Also, the command I used was

fastboot flash recovery twrp.img

but I remember using

fastboot flash FOTAKernel twrp.img

before, when I did this for the first time. Is there any difference between FOTAKernel and recovery?

Update 2:

Managed to fix the partitions errors, just kept doing formats and wipes and reformats while flashing random ROMs in between.

So I can install ROMs now but Flashmode still doesn't work????

Additionally, I don't think it's charging while powered off either.

Update 3:

Flashed latest TWRP, a MM ROM, and GApps. Seems to be working fine.

Phone is also now charging when powered off again, completely with battery icon animation.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Didgesteve:
There's a hard reset button under the sim flap (tiny red red square, you need a pin to push it)

Try that.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] nzzane:
Hey there,

Follow this LINK

It may help in fixing your problem
[Xperia Z3 Compact Q&A, Help & Troubleshooting] House3272:
Nah mate, Flashmode doesn't work at all.

All I have or had, was fastboot mode.