Related
made you look :twisted:
now to the q in hand
I brought my xda second hand - the previuos owner had saved all his contact info on 'permanant save' so when I restore from 'permanent save' I get all his contact details.
How can i delete his contact stuff off 'permanently save' :twisted:
Hard reset :?
roko: that doesn't erase those
Jacko: made look ))))))) if you want to get rid of his contacts, check the box in permanent save and click ok, your contact will be copies to rom and his contacts will be synchronized with them. Now you need to uncheck the box again, thus erasing all contacts in ROM.
Now you have nothing in ROM and all yours and his contacts in RAM. Delete them and re-synchronize from desktop (make backup copy in case your activesync desides that it will replace desktop with mobile device )
Changed the subject, santizing the ROM, adding files
Made me look, and I've added a little to the subject...
I must admit it was the first message I read, so the strategy worked. However: this is a very busy forum, and if we are to use it to find information in such a way that we're not all re-inventing wheels all the time, we do need somewhat descriptive subjects.
On the topic of ROM contacts: this point was driven home to me as well when I copied someone's ROM. Maybe we need a tool to sanitize ROM images, to be incorporated in the XDA ROM Image Tool ?
Has anyone (possibly with platform builder experience) taken a good look at these images, and determined what's where? I wouldn't mind being able to add files (SMS fix, etc) to an image. Maybe we could even create an XDA-developers special edition ROM...
Hiya there sorry about the description wont happen again
Jacko: made look ))))))) if you want to get rid of his contacts, check the box in permanent save and click ok, your contact will be copies to rom and his contacts will be synchronized with them
>this part is fine
. Now you need to uncheck the box again, thus erasing all contacts in ROM.
>whenever you go to 'permanant save the box is always unchecked anyway kinda confused on this part
do you mean save all my info on desktop - delete all my contacts and then save on to permanent save thus saving no info... thus having nothing in rom (sorry about the thus's its late in the evening)
shock
/|\
,/\,
I just got my Atrix yesterday, I seem to have the issue where it wont successfully log in to google talk which also means that I cant download apps. I've tried making a new account which also failed to work. Are there any ideas out there for how I could fix it?
Can anybody help me?
I had the same problem and figured out that it was Droid Wall keeping Gtalk from connecting. Make sure Talk can access the network freely.
Sent from my Nexus S using XDA Premium App
Real solution
Gibsonflyingv said:
I just got my Atrix yesterday, I seem to have the issue where it wont successfully log in to google talk which also means that I cant download apps. I've tried making a new account which also failed to work. Are there any ideas out there for how I could fix it?
Click to expand...
Click to collapse
After cloning a samsung gio s5660 through a CWM backup I started experiencing the same issue. Heres What REALLY happens.
Google authenticates you in their services trought unique "keys" which are automatically generated upon system installation / factory reset, so if you clone your device or install a rom which has these "keys" pre-installed, obviously, your rom will only autheticate you in google servers if your phone is the only one using the service at that given time... Upon failure, your phone assumes to be the one who's wrong, and google servers won't autheticate you until you either tell your phone he is not wrong (by deleting the data from play store, which resets its status and errors) or you change the "keys". SO, what can we learn from this? deleting the play store data IS a temporary solution, and won't solve a thing. Let's delete the duplicated keys shall we?
Navigate with your favourite folder explorer on your android (I use X-plore, you can tell me anything, there's nothing better) to the following directory:
- "(root)/data/data/com.google.android.gsf"
Now you have two real options, either you may delete the all folder, which was the perfect solution for me, since my rom is prepared to re-create it upon phone restart and new keys will be generated, OR, you might want to just delete the contents of app_sslcache inside com.google.android.gsf whish are THE KEYS I HAVE BEEN TALKING ABOUT THIS ALL TIME, YEEEIHHHH and reboot your phone...
Needless to say, take a nandroid backup before you do any of this...
Thank me later
For those who remember me from symbian s60v3 phones, yes, it is me, I'm back, and I've moved to the droid world, it's much better indeed
Let me just say, I have no idea why this thread was moved or resurrected. Whoever did so was about a year and a half too late. Please close/delete this thread.
I got my motorola photon from japan, and it has been locked on au kddi network.
I have unlocked it to work in Croatia, where i need it.
I can make and recieve calls, and receive sms, but sending sms seems to be locked somehow.
I can't send sms from "go sms" as well. All i get is "sending sms not available". I even made my own app, and no luck, same message appears. There is no sms icon in contacts, and in default sms app, there is no option to make new sms or anything usefull.
Sms center is loaded correctly from my sim card.
I have set up apn-s, but i don't think thats relavant.
So I rooted my device, and now I'm in search of how coud I make this sms to work.
So I ask you, what settings should I look for, and shoud I replace something with something from verizons photon android?
Have you tried downloading Google Voice? It uses a completely different service, but if you had a Gvoice number, and an account, you could send SMS that way. It should work fine out of country. I use Gvoice whenever I travel because it's cheaper.
Thank you for suggestion, but I mainly use sms for paid services like public transportation, parking, etc... so I really have to enable native sms service.
Currently I'm exploring: system/framework/framework-res.apk
As I've seen in this thread
http://forum.xda-developers.com/showthread.php?p=17578600#post17578600
I've unpacked apk, but there aren't any permissions explicitly set as in this thread.
But I found some file in apk, under raw folder which states:
com.kddi.android.intent.action.LOCKSMS_RECEIVED,com.kddi.android.permission.RECEIVE_LOCKSMS,2,0x000E,0x00,,,,,,
com.kddi.android.intent.action.KUPSMS_RECEIVED,com.kddi.android.permission.RECEIVE_KUPSMS,2,0xFFFF,0x01,0,3,0x000701,,,
com.kddi.android.intent.action.UNSUP_SMS_RECEIVED,com.kddi.android.permission.RECEIVE_UNSUP_SMS,0,0xEF43,0x00,,,,,,
com.kddi.android.intent.action.UNSUP_SMS_RECEIVED,com.kddi.android.permission.RECEIVE_UNSUP_SMS,0,0xEF40,0x00,,,,,,
com.kddi.android.intent.action.UNSUP_SMS_RECEIVED,com.kddi.android.permission.RECEIVE_UNSUP_SMS,0,0xFFFF,0xFF,0,2,0xEF44,0,2,0xEF55
,,1,0xFFFF,0xFF,0,2,0xEF56,0,2,0xEF7E
,,1,0xFFFF,0xFF,0,2,0x0002,0,2,0x005F
,,0,0xFFFF,0xFF,0,2,0x0060,0,2,0x00AF
com.kddi.android.intent.action.UNSUP_SMS_RECEIVED,com.kddi.android.permission.RECEIVE_UNSUP_SMS,0,0xFFFF,0xFF,0,2,0x00B0,0,2,0x00FF
com.kddi.android.intent.action.ESIGNAL_RECEIVED,com.kddi.android.permission.RECEIVE_ESIGNAL,0,0xFFFF,0x01,0,10,0x5349474E414C5549443A,,,
So I guess this is step forward... now I'm not sure is this just a log, so I have to find and kill this process, or just delete this file...
I will update when I find the time to deal with this problem.
Any advise would be greatly appreciated
Bricked it! help needed
OK, i succesfully bricked my phone by changing that file.
Now my question is how to get adb access with bricked phone.
It is in infinite boot loop, but I can access recovery options, fastboot and others. But adb don't reckognise it. It is only recognised in some usb mode but as offline.
I tried factory reset and wipe, but that is something differnet i guess. Probably my phone is unrooted again too.
I have backup of original framework-res.apk file I just need to push it but don't know how... please advise.
majkell27 said:
OK, i succesfully bricked my phone by changing that file.
Now my question is how to get adb access with bricked phone.
It is in infinite boot loop, but I can access recovery options, fastboot and others. But adb don't reckognise it. It is only recognised in some usb mode but as offline.
I tried factory reset and wipe, but that is something differnet i guess. Probably my phone is unrooted again too.
I have backup of original framework-res.apk file I just need to push it but don't know how... please advise.
Click to expand...
Click to collapse
can not reach adb? change the usb mode to storage maybe ok
i have sam,e problem too. whoever can help me in this situation. please contact me,
Please share how did you solve it?
Please tell how did you solve it?
I am facing same problem. I m having Japanese Motorola (Au-kddi). I have unlocked it using paid service and rooted also.
But I can NOT send SMS. (I can receive SMS)
Please help.
I hope you will reply positively.
Thanks.
ubiecau volatile
rajmicro30 said:
Please tell how did you solve it?
I am facing same problem. I m having Japanese Motorola (Au-kddi). I have unlocked it using paid service and rooted also.
But I can NOT send SMS. (I can receive SMS)
Please help.
I hope you will reply positively.
Thanks.
Click to expand...
Click to collapse
I had the same problem. try to update by setting>about phone>software>update software.
After reboot on dislpay yuo will see "android au" in orange color .you will go to choose gsm/umts antenna and now you will able to send sms
Greetings.
I'm having a problem restoring my messages using adb method in Nougat. I have done it before in CM12 and CM13 with no problems but since I flashed LineageOS 7.1.1, I had problems with it. First was the location. Before it was located in /data/data/com.android.providers.telephony/database. After googling around, I found a this thread. Turns out it was now located in /data/user_de/0/com.android.providers.telephony. So I go ahead and pushed my mmssms.db backup to that location but still my messages did not appear. Worse is my SMS app crashes every time I open it. Did a reboot, wiped cache/dalvik cache, tried to delete the *.db-journal files as mentioned in the thread but still no luck. I had to wipe the data again to regain my SMS app. I hope someone can help me. TIA
Bump
I have the same problem...
Yep same problem here. The /data/user_de location doesn't really seem to work either
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 not mentioned in any other thread I 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.
I'm struggling with something that never happened to me, I'm unable to restore my database to my recently upgraded Samsung J3 2016 - is running LineageOS 14.1 now
The phone was running stock Android 5.1.1, version J320FXXU0AQI1, nothing fancy here.
Made some research about what ROM to use and decided to upgrade to LineageOS 14.1, I'm really sick and tired of Google spying my steps, my contacts and the number of times i take a piss every day, and so on. Right now I don't have any Google account associated with the mobile (could this be the problem, since this is a custom ROM?)
Everything ran smoothly, backed up my contacts, call logs, SMS, pictures and the ENTIRE Whataspp folder. This method always worked fine on several phones I've upgraded or simple swapped equipment to a more up-to-date hardware. Everytime worked like a charm, restored logs, contacts and so on, in what it concerns to Whatsapp i simply moved the ENTIRE folder to the new phone (or upgraded phone), installed the Whatsapp app and is just straight forward for the app to ask me for a SMS code to activate the software and then asked me to restore my backed up database. It has been very simple so far, but not this time:
When it reachs the point to detect and restore my database Whatsapp states that can find one Database from 1970 (???? WTF) with 0 bytes, and after that it fails to restore my data (not strange, 0 bytes is no data). I've already tried earlier versions of Whataspp, tried different databases (there are 7 in my folder, i don't believe all of them are corrupted). I'm reaching 0 ways to explore. BTW, i dont use Google drive to store my backups because its enough for Google to know how many times i take a piss everyday, i rather have the backups with me, on my phone (thanks any way Google), but the files are safe in my desktop and on my phone for now, inaccessible so far but their're there.
Can any one point me some way to try to revive my database? Just a note, i have an older phone that still have Whatsapp there, i didn't erased it, maybe it's there something of interest for this situation?
Thanks so much in advance for everyone that can help, any hint can be helpful.
Update!
I've managed to get another phone, exactly the same, Samsung J3 201 J320F.
I've sent my whatsapp folder to the phone, signed in to my google account, installed whatasapp and, like 98% of the times my backup is ok and is restored. Now I have two phones:
1- one with Whataspp working fine (the one with Stock ROM 5.1.1 J320FXXU0AQI1
2- another one, the main phone, where i want to put my whataspp backup working but it simply doesnt work (previous post). Everything elese is settled and working just fine. Maybe whatasapp doesnt like Custom ROMs??
So, I'm sure that my backups are fine, right now I have access to anything that i may need i guess. I don't believe that Im the first person not beeing able to restore whataspp backups in LineageOS.
Please help
New developments.: I've installed Ressurection 5.8.5, the latest available for this phone. It runs ok, but Whataspp problem is still there, the backup is marked to have 0Kb, somehow Whataspp simple doesn't want to recover my backup if I'm using a custom firmware (I receive a warning about no support from them if I have problems at the beginning of the startup process).
So far this method didn't work (Whatsapp shows my Backup with 0Kb):
1) Copy your latest crypt 12 file to /sdcard/WhatsApp/Databases/
2) Install / Activate WhatsApp
3) WhatsApp will retrieve the key from their server and restore your backup.
I've tried this method that appeared to have some success in same cases. Followed everything but no luck, Whataspp detects a 0Kb backup also.
Meanwhile I still don't believe that I'm the very 1st person that this happens, I'm still very impressed with this. If the OP thinks I'm in the wrong Topic please feel free to move it to the right place, maybe there I'll have better luck.
Not that I have much knowledge in that direction, but the issue sounds more like it is about the file than Whatsapp itself. Maybe some permission issue? If you use a filemanager app like total commander, can it read the file fully? I found a topic that had 0 byte filesize issue and a simple reboot apparently fixed it.
musschrott said:
Not that I have much knowledge in that direction, but the issue sounds more like it is about the file than Whatsapp itself. Maybe some permission issue? If you use a filemanager app like total commander, can it read the file fully? I found a topic that had 0 byte filesize issue and a simple reboot apparently fixed it.
Click to expand...
Click to collapse
Hello musschrott, and thanks for replying.
I've tried moving the database file, erase it, changing it's name and the android system allows me to do it, i think the file itself is free to be read by Whataspp, but your other tip, the permissions in system made me google around (even more..) about it and I found here on XDA this. : "The privacy protection in the drop down menu and the permission in the app settings." (credits to LegoTechniker). On the privacy protection is all ON but in the Permission is all OFF and Whataspp nor the System ask me to turn it ON and it can result on whatasapp reading files with 0Kb from 1970.
I'll give a try but only tomorrow because the code/phonecall from Whataspp have a 48h delay and keeps increasing everytime I try a different method to solve this issue.
musschrott, thanks again!
tomalamix said:
Hello musschrott, and thanks for replying.
I've tried moving the database file, erase it, changing it's name and the android system allows me to do it, i think the file itself is free to be read by Whataspp, but your other tip, the permissions in system made me google around (even more..) about it and I found here on XDA this. : "The privacy protection in the drop down menu and the permission in the app settings." (credits to LegoTechniker). On the privacy protection is all ON but in the Permission is all OFF and Whataspp nor the System ask me to turn it ON and it can result on whatasapp reading files with 0Kb from 1970.
I'll give a try but only tomorrow because the code/phonecall from Whataspp have a 48h delay and keeps increasing everytime I try a different method to solve this issue.
musschrott, thanks again!
Click to expand...
Click to collapse
For everyone and specially those who helped (musschrott).
This has worked for me: giving full permissions to Whataspp in "Settings - Privacy" and in "Settings - Applications" worked like a charm, you have to do it BEFORE you start Whatsapp.
Best regards to everyone and thanks once more!
Make sure the WhatsApp backup file is in internal storage, and rename the backup file to msgstore.db.crypt.
After upgrading to LineageOS 14.1,install WhatsApp.When asked to restore from backup,choose the "msgstore.db.crypt" file.
mango9 said:
Make sure the WhatsApp backup file is in internal storage, and rename the backup file to msgstore.db.crypt.
After upgrading to LineageOS 14.1,install WhatsApp.When asked to restore from backup,choose the "msgstore.db.crypt" file.
Click to expand...
Click to collapse
Yes,
Those are the basic steps, but BEFORE running Whatasapp for the 1st time you have to give permissions in the system to Whatsapp because these are all OFF and the system doesn't ask to turn them ON when the permission is needed, simply presents you a file with 0Kb from 1970 and that's it. Again, you have to do this BEFORE the 1st Whatsapp startup and everything should run well.
Best regards
My issue is I gave full write permissions but then it goes straight to the Google Drive restore and does not show my local backup.
When I followed this by Rahil:
https://www.reddit.com/r/whatsapp/comments/np2zjp
"So today I finally fixed the issue myself
Click to expand...
Click to collapse
Steps: 1)make sure you rename the database as it should be.
2)Install whatsapp
3)Insert your number when asked
4)Use Otp/code
5)Then the app will ask you for google drive permission ,click allow/ok
6)Then the app will ask for contact permission ,simply deny this permission (very important)
7)Then the app will ask for storage permission ,hit allow (very important)
8)Then you will see your local storage behind the popup saying allow google drive and crap You will need to press add account and have your fingers ready for instant tapping between add account and instant tapping restore button ,and out of 10-30 times doing this practice, you will luckily hit restore button, I know this sounds confusing, And I can make a tutorial video if you want ,this works 100%
9)once it is restored ,you will still see app asking google drive option, don't click skip (this will reset the app ,leading to nothing restored) , So when the app is asking to restore from google drive, close the app right away (very important)
10)open the app ,and the app will ask you to set name ,set your name ,and you'll see all your backup"
Click to expand...
Click to collapse
It works but then it shows my local backup as 0k and from 12/31/1969
This is Driving me wild and now I have to wait 12 hrs to try again. Has anyone solved this ridiculous error?
dpoverlord said:
My issue is I gave full write permissions but then it goes straight to the Google Drive restore and does not show my local backup.
When I followed this by Rahil:
https://www.reddit.com/r/whatsapp/comments/np2zjp
It works but then it shows my local backup as 0k and from 12/31/1969
This is Driving me wild and now I have to wait 12 hrs to try again. Has anyone solved this ridiculous error?
Click to expand...
Click to collapse
Did you find a solution to this? I have the exact same problem