I been performing this myself with great success, but you need ROOT access AND busybox installed. Create a folder on your phone's SD card called tmp. You'll need adb in order to adb shell, and gain root access. (in cmd, adb shell <enter> su <enter> confirm you are on a # prompt not the $ prompt)
Now copy and paste each line, press enter after each line pasted. Confirm the files copied after each line by running ls /mnt/sdcard/tmp/mmssms.db
Code:
cp /dbdata/databases/com.android.providers.contacts/contacts2.db /mnt/sdcard/tmp/contacts2.db
cp /dbdata/databases/com.android.providers.telephony/mmssms.db /mnt/sdcard/tmp/mmssms.db
cp /dbdata/databases/com.sec.android.provider.logsprovider/logs.db /mnt/sdcard/tmp/logs.db
cp /dbdata/databases/com.sec.android.app.memo/Memo.db /mnt/sdcard/tmp/Memo.db
cp /dbdata/databases/com.android.providers.calendar/calendar.db /mnt/sdcard/tmp/calendar.db
Once that is done, mount the phone to your computer and copy the TMP folder to your computer. When you flash the custom rom, you'll have to keep the SIM card out of the phone because you do not want new history items written to the log files.
Next ls -l /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others) to see what permissions/owner they have, if you simply cp the files from /mnt/sdcard/tmp to their locations, you'll get force closes in the application (because it's not able to write log data).
Make note is the owner for each db file. Then back to adb shell, su, cd /mnt/sdcard/tmp (trust everyone knows to copy the tmp folder from PC onto your phone) cp contacts2.db /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others!).
Once the files are copied back to their locations on the device, run the following:
Code:
chmod 660 /dbdata/databases/com.android.providers.contacts/contacts2.db
chown app_15.app_15 /dbdata/databases/com.android.providers.contacts/contacts2.db
Obviously you want to use the app_X.app_X you saw from running ls -l /path/filename before copying the backed up log file.
bravomail said:
This is quick comparative review.
Overall for KB1.
TiBu restore of system setting from JS32.2.1 or JS52.2.1 other than WiFi highly discouraged. I had uncurable Force Close for Browser and for MMS. Say g-bye to your messaging history, or find other ways of transferring it.
Click to expand...
Click to collapse
Original thread is here http://forum.xda-developers.com/showthread.php?t=969343
SMS Backup and Restore is a great app that does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
Call logs backup and restore also does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Both free and developed by the same guy, I've used both many times without a hitch.
I sync my contacts with gmail, so no problem there.
hauj0bb said:
SMS Backup and Restore is a great app that does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.SMSBackupRestore
Call logs backup and restore also does exactly what it's title indicates, without root.
https://market.android.com/details?id=com.riteshsahu.CallLogBackupRestore
Both free and developed by the same guy, I've used both many times without a hitch.
I sync my contacts with gmail, so no problem there.
Click to expand...
Click to collapse
+1
The manual method is pointless and extra work for nothing. These apps work flawlessly. I've used them many times as well.
I know there are apps which backup the same settings, my whole point for posting is I do not backup contacts with Google. So I kept trying different things until putting this together and I know it's a pain but all that really is done is copying and pasting lines into an SU adb shell.
askpcguy said:
I know there are apps which backup the same settings, my whole point for posting is I do not backup contacts with Google. So I kept trying different things until putting this together and I know it's a pain but all that really is done is copying and pasting lines into an SU adb shell.
Click to expand...
Click to collapse
You do not use google account or you just don't use it for backing up contacts...
I use a Google account but not to sync or backup contacts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for good info!
Thanks for good info!
I personally don't care about my SMS history. Other people text a lot.
Another alternative is to use Google backup/synchronization. I never tried it. Anyone?
In my experience, backing up phone contacts using Gmail syncing is not 100%. Some fields in the on phone contact records are not properly carried into Gmail contact records and viceversa.
You'd think since Android is Google and Gmail is Google this would work flawlessly.
askpcguy said:
I been performing this myself with great success, but you need ROOT access AND busybox installed. Create a folder on your phone's SD card called tmp. You'll need adb in order to adb shell, and gain root access. (in cmd, adb shell <enter> su <enter> confirm you are on a # prompt not the $ prompt)
Now copy and paste each line, press enter after each line pasted. Confirm the files copied after each line by running ls /mnt/sdcard/tmp/mmssms.db
Code:
Next ls -l /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others) to see what permissions/owner they have, if you simply cp the files from /mnt/sdcard/tmp to their locations, you'll get force closes in the application (because it's not able to write log data).
Make note is the owner for each db file. Then back to adb shell, su, cd /mnt/sdcard/tmp (trust everyone knows to copy the tmp folder from PC onto your phone) cp contacts2.db /dbdata/databases/com.android.providers.contacts/contacts2.db (and the others!).
Once the files are copied back to their locations on the device, run the following:
[CODE]chmod 660 /dbdata/databases/com.android.providers.contacts/contacts2.db
chown app_15.app_15 /dbdata/databases/com.android.providers.contacts/contacts2.db
Obviously you want to use the app_X.app_X you saw from running ls -l /path/filename before copying the backed up log file.
Click to expand...
Click to collapse
Are you doing all this above because
Code:
cp -p
failed to preserve attributes or something? Or do your fingers like the exercise...
Oh, I bet it's because it is that the attributes are getting scrubbed when they are copied off the device to your computer...
I only do this manual method because I want to retain my history and contacts between Roms.
Sent from my SAMSUNG-SGH-I897 using XDA App
I was asking specifically why you didn't use the "-p" preserve attributes flag when using the cp (copy) command. But I now realize your may be storing your backups in a way that blows away the info anyway. so you need to set ownership and permissions manually after restore..
Because I push the files to an external sd card which is copied to my computer.
Sent from my SAMSUNG-SGH-I897 using XDA App
TiBu does this, too. But thanks for the info. It's good too know how to do things manually, too.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I don't think titanium backup will backup call history. It does get the contacts and calendar though.
Sent from my SAMSUNG-SGH-I897 using XDA App
I found this thread very useful for the restoration of all my recent messages!!
the backup i have done with smsbackup&restore is 12hour before the disaster
what happened? simply after a normal reboot my Desire HD was going to bootloop! i've tried several restore procedures but i find out that /data partition is somehow "bad", don't know why...
the only thing i can do is backup data partition with clockworldmod and unyaff it on a pc;
then i followed the instructions in the OP and i succedeed in making succesfully a backup of all my messages ;
the only difference is the different path in which mmssms.db is located in Desire HD:
i have in /data/data/com.android.providers.telephony/databases/
thank you again mate, very detailed guide
Glad someone found this useful! This is only compatible with Froyo roms, Gingerbread uses the /datadata folder and I haven't needed to manually backup the files because MIUI backup does it so amazingly well!
Well, this is pretty neat. I'm forever reflashing my phone and having to reload everything.
Which is a p-a-i-n..
One question though, is there anyway to do all this using "adb shell"? I'd love to incorporate this into a batch file I'm making, with the proper credits of course, and it'd be nice to press a button and have the PC do all the hard work.
askpcguy said:
I don't think titanium backup will backup call history. It does get the contacts and calendar though.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Super Backup from the Market does all 3:
https://market.android.com/details?id=com.idea.backup.smscontacts&feature=search_result
The apps in post #2 are great too.
Ticklefish said:
Well, this is pretty neat. I'm forever reflashing my phone and having to reload everything.
Which is a p-a-i-n..
One question though, is there anyway to do all this using "adb shell"? I'd love to incorporate this into a batch file I'm making, with the proper credits of course, and it'd be nice to press a button and have the PC do all the hard work.
Click to expand...
Click to collapse
I tried, I had sort of a working bash script but ran into problems trying to get the script root access to do the copying/restoring. Come to think of it, if you wanted to get fancy, you could make a clockwork mod flashable zip. One for backup and one for restore.
-Yes, I know there are apps which might do this however I wanted to learn on my own.
Well, yes, there are backup apps but you have to reinstall those apps and wait while they put your data back in bit by bit. Granted it may not take long but when you're reflashing what seems like once every five minutes, it can take forever!
The zip route seems like a good idea. That way, you can back up, install a rom and restore your details all from one screen. I'll have to have a look at it.
Sent from my U20i using XDA App
Related
Tired of having to redownload and reinstall all of your apps when you reflash your phone? SaveMyApp can help.
This script will setup your phone so that after your flash to your favorite rom, all* of your apps will be install on the first boot. These apps will show up in the market too!
Also, the script will allow you to backup your /data/data folder to your sdcard and then restore it after your reflash. The /data/data is where Most of your user data is stored. This is not guaranteed to fully restore everything. This also does not backup your Google, Android, or Motorola settings; this is to improve compatibility with roms.
*The /preinstall folder is limited to 120MB, so if you have more then of apps this script will not fully work.
This should work with all phones, however it has only been tested on the Droid 2/X.
If you want to test this script on a different phone, let me know the /preinstall size and if it worked or not.
v0.1.4.2 - 11/17/2010
-Improved backup and restore of data
-Improved script usability
v0.1.4.1 - 11/17/2010
-Improve safety of removing /preinstall/app
v0.1.4 - 11/16/2010
-Added option to clear the /preinstall/app folder
-Added messages to support clear /preinstall/app
v0.1.3 - 11/12/2010
-Added backup of /data/data
-Added messages to support Data Backup
v0.1.2 - 11/11/2010
-Added Backup /data/app-private
-Show /data/app size, prompt user for continue
-Additional messages added to improve user experience
v0.1.1 - 11/10/2010
-First Release
-Backup and Restore /data/app
Installation:
WARNING: This steps must be completed as listed, failure to do so may result in unexpected errors which I am not responsible for.
1. Enable USB debugging and make sure Sdcard is mounted on phone
1. adb push apps.sh /data
2. adb shell
3. cd /data
4. chmod 775 apps.sh
5. ./apps.sh
a. Follow the onscreen directions
6. Reboot and proceed to wipe and reflash
7. On boot, wait between 5 and 10 minutes depending on how many apps you have before logging into your account. (30 apps takes about 4-5 minutes)
8. Login to your account
9. Droid 2/X Bootstrapper -> Bootstrap Recovery
10. Enable USB debugging and make sure Sdcard is mounted on phone
11. adb shell
12. tar -xzpf /sdcard/savemyapp/backup.tgz
FAQS:
Market isn't showing apps!
settings->applications->Manage Applications->All->Market->Force Stop, Clear data
Why is there a MACOSX file when I extract the archive?
Because I am lazy and I zipped it using Mac's built in archiver.
The script isn't working right away!
Redownload the newest script, just to make sure
Disclaimer:
You may repost this, but you must quote it as is.
I will only be responding to the threads I started on the Xda-Developers forums.
First!
I'm just holding a parking spot for this post!
What a great idea...thank you for developing this, im so tired of re downloading my apps back and setting everything up...done it about 10 times in the past month between sbfing and updating the fission rom several updates in a row so thank you...will most definitely be using this when I flash roms in the future. Thanks again
Sent from my DROID2 using XDA App
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get errors saying "No space left on device" after every single file it tries to copy. This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code that won't run on windows aside from "du" which isn't even relevant unless my app + app-private folders combined size is over 120 MB (it's not).
I'm also running Epic 2.5 if that has anything to with this.
Any ideas? Am I just doing this terribly wrong?
Thanks!
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
turkeybuzzard said:
If you read the first post it states the /preinstall folder can only hold only 120mb so it you have more than that to backup it won't fully work..I'm guessing that's were the apps are being saved...
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Apps are normally saved in /data/app this script copies those apks to /preinstall so that after a wipe they will automatically be installed on the first boot. Yes /preinstall is limited to about 120MB.
tildaSparky said:
Excellent program! I'm having trouble getting it to work unfortunately. When apps.sh begins to copy files from /data/apps, I get an error saying "No space left on device." This is of course not true since this D2 has over 6 gigs free on the system storage.
I am running this through the window's command prompt, but I don't see much in the code aside from "du" which can't run with windows.
Any ideas? Am I just doing this terribly wrong?
Thanks!
Click to expand...
Click to collapse
Do you get the "No space left on device" message instantly or after some apks were copied to the /preinstall folder?
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
tildaSparky said:
Here's what I get
Working…
cp: /preinstall/app/com.google.android.apps.maps-1.apk: No space left on device
cp: /preinstall/app/com.google.android.apps.translate-2.apk: No space left on device
cp: /preinstall/app/com.google.android.gm-1.apk: No space left on device
cp: /preinstall/app/com.google.zxing.client.android-2.apk: No space left on device
etc.
=(
Click to expand...
Click to collapse
How big is your /data/app folder?
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
tildaSparky said:
OK! I sort of have it fixed. In that I'm not getting my original error.
What I did (which in retrospect was not such a hot idea) was delete the /preinstall/ folder and then created a new one with the subfolders /app/ and /md5/. The logic behind was that I saw the script had nothing in it to clean out the original preinstall folder, and I noticed that it had silly things like NFS in it. As I said, in retrospect I should have just deleted specific items from the folder, but that's what I get for acting without thinking too much.
How bad do you think it is that I remade the preinstall folder from scratch?
Now my preinstall folder is properly populated (I think). But the data won't back up for some reason. I think it might have something to do with the if statements being broken. I'm gonna go ahead and modify your script to bypass the if/else statements and see what happens.
SaveMyApp v0.1.2
By csscmaster3
Your app folder takes up
du: not found
If your app folder is more then 114MB I don't recommend continuing
do you want you to continue? (y/n)y
y
[[: not found
Working…
ignore No such file or directory error if you get it
tee: not found
SaveMyApp has completed your apps
Do you want to backup your data? (y/n)y
y
[[: not found
SaveMyApp has completed.
As an aside my app folder is 28 MB and my app-private folder has only the apkinstaller.
Click to expand...
Click to collapse
The NFS removal is a good call, I will append the script to check the /preinstall folder and prompt to remove the files there
The reason you are having trouble with this script looks it be like because you are not running it on the phone itself...meaning to say you are not running it via a terminal emulator on the phone nor are you running it via adb shell. The backup uses tar, which isn't on windows by default.
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
tildaSparky said:
Actually I'm running everything through the adb shell. It's puzzling to me too. My terminal emulator for some reason doesn't have root access. At this point I think I'm just going to SBF anyway.
At any rate, I just decided to pull /data/data/ from my phone onto my HD and I will replace it after I reflash and install my programs, but before I log into my google account. Do you see any reason for this not to work?
Click to expand...
Click to collapse
Hmmm, you might have to check your superuser app to see if you accidently are denying su access. In adb shell do you have a $ or a #?
Backing up the /data/data folder to your HD then restoring might not work because I am not sure if it will retain the owner, permissions, etc.
I had a # in my shell. There was something slightly wonky about my root I think. At any rate my backup method didn't work so well (as you predicted) - it caused timeriffic to force close when I tried to load in my old settings via /data/data/.
I will try using this again once I've got my shiny new Fission 2.1 set up as I want.
Thanks for your attentiveness!
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
wsfanatic said:
I'm guessing this script should be run AFTER all of the applications have been installed. Is this correct?
Click to expand...
Click to collapse
That is correct
Sent from my DROID2 using XDA App
Ooooo this is getting popularrrr
Is this D2 specific, or would it work on any phone?
theimpaler747 said:
Is this D2 specific, or would it work on any phone?
Click to expand...
Click to collapse
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
csscmaster3 said:
It works with the D2 and should work with the DX, anything else is use at your own risk, if it does work let me know though
Click to expand...
Click to collapse
Might risk it and try it on my hero Regardless, nice work
theimpaler747 said:
Might risk it and try it on my hero Regardless, nice work
Click to expand...
Click to collapse
The only problem I could forsee would be the /preinstall folder being different or something, if you do end up trying the script could you let me know the size of the /preinstall folder?
New 100% reliable "temp root" for Titanium Backup (won't stop working until reboot!)
Hi all,
I grew frustrated by the annoyance of losing root access randomly, when modified files on /system suddenly become inaccessible because of the S-ON lock.
But here's some good news: I came up with a way to get a 100% reliable "temp root" for Titanium Backup.
Advantages:
You will not lose root access until next reboot!
100% reliable, does not modify /system at all.
Drawbacks:
Minimalistic approach with no BusyBox.
Will only work with select root apps.
Tested with Titanium Backup only (for now).
Requirements:
Original "out of the box" Sensation or EVO 3D (untested).
Android SDK tools ("adb" command) on a computer.
USB connection between computer and phone.
Installed Superuser app from the Market.
Initial (one-time) setup:
unzip better-temp-root.zip
adb push fre3vo /data/local/tmp/
adb shell "cd /data/local/tmp ; chmod 755 fre3vo ; ./fre3vo"
adb shell "mkdir /data/bin ; mv /data/local/tmp/fre3vo /data/bin/"
adb push su /data/bin/
adb push root.sh /data/bin/
adb shell "chmod 4555 /data/bin/su ; chmod 755 /data/bin/root.sh"
adb shell "/data/bin/root.sh"
After every reboot:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
The advantage of this method is that /system is not modified, therefore the rooting will be totally stable and will persist until the next reboot
Q&A:
Will it work with other root apps?
This is a minimalistic approach which installs no busybox and does not touch /system, in order to be perfectly reliable. The drawback of this is that it will work only with root apps that are able to find "su" at /data/bin/su, and that don't need a busybox in $PATH. Fortunately, Titanium Backup fulfills both of these criteria. If you know other apps that do, please post about them.
Status:
Titanium Backup (free & pro): works
Root Explorer: works
MyBackup pro: works?
SetCPU: FC
Wireless tether: needs system modification
Greetings go to #teamwin for the exploit, of course.
Have fun !
Great. Good job!
Now where is that test recovery?
If it works well, maybe you should try and pass the files onto agrabren for him to implement into Fre3vo^2 (apk that makes root better like your fix is aiming to).
That way things will move a LOT faster
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Adfree is build to edit files on /system partition which is not possible with temp root
Set-Cpu is working?
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Does barnacle or any WiFi tether apps work with this? Still at work.....
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
madindehead said:
Using this, I can get Titanium Backup to work, but not AdFree. Might just wait for Fre3vo^2.
Click to expand...
Click to collapse
Thanks for your feedback. I hadn't tested AdFree, but I'm not surprised here. This solution is a willful compromise: we refrain from modifying /system, and thus we gain 100% reliability - but at the same time we lose compatibility with some root apps, because they often rely on BusyBox being in /system (or at least in $PATH).
I have contacted @agrabren on Twitter with a link to this thread. I haven't looked into it, but if #teamwin can come up with a way to execute adb commands locally on the phone, it could all be done automatically at boot. Hopefully they'll add a configuration choice such as:
Method 1: Full compatibility with root apps, system BusyBox, "ephemeral" root
Method 2: Compatibility with *some* root apps, no system BusyBox, 100% reliable root
Let's see how it goes... but I know which method I'd personally use
Tiffany84 said:
Sorry for the noob question but where do unzip it to, the computer or the phone?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Unzip to the computer, you'll get 3 files. Go on from there
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
joel.bourquard said:
Unzip to the computer, you'll get 3 files. Go on from there
Click to expand...
Click to collapse
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
DomSim said:
possible to make a script that runs
Code:
adb shell "/data/bin/fre3vo"
adb shell "/data/bin/root.sh"
at each boot automatically?
Click to expand...
Click to collapse
That's the goal - but such a script would not work right now, because: (1) the 1st command terminates the current shell and (2) the 2nd command must be called through ADB.
As far as I see, the 1st command could be invoked automatically from an Android app at boot, but the 2nd one needs to be called through adb, which requires a separate computer right now.
I haven't looked into that - but I think @agrabren / #teamwin are aiming at this (ie: somehow doing the equivalent of running commands through "adb" from the device itself) with Fre3vo^2.
Thanks very much..
Sent from my HTC Sensation Z710e using XDA App
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Same directory
Tiffany84 said:
Ok. So this is where I struggle with adb. So how does it know where the files are at? Do u have to tell it the location of the files or do u put it in the same directory with adb? Again, I apologize when it comes to being clueless with adb.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I run Linux personally, but I think if you just unzip the files into some empty folder, then stay in that same folder and run ADB by its absolute path, it should work fine. Something like:
"C:\Program Files\Android SDK\BIN\ADB.EXE" push xx yy
Maybe a Windows user could give you more precise advice here...
Why would you need barnacle when you have wireless tether built in?
Sent from my HTC Sensation 4G using XDA App
With this,only run fre3vo bat file and all will install
automatically:
Ganii said:
What about this:
Any difference to files/method from first post?
http://www.facebook.com/pages/S-Off-for-Sensation-and-Evo-3d-NOW/117107248377328?sk=wall&filter=1
Click to expand...
Click to collapse
Anyone tried SetCPU ? Which profile did you select, and does it work?
Pinepig said:
Same directory
Click to expand...
Click to collapse
Thanks.
Sent from my PG86100 using XDA App
Greetings,
Just to make things clear, I have used the search feature. However, I am not clear on the answers that I am reading.
I need to restore or export 1 SMS thread (or entire mmssms.db, doesn't matter) from an old ROM.
Last week my ROM crashed, and I had to switch to a new ROM.
It was a Sense 3.0 ROM (phone is HTC Droid Incredible 2). I was playing around with the different lockscreen options, applied the Stocks Lockscreen, and when I locked/unlocked my phone to see how it looked, nothing but My wallpaper and the top status bar showed up. There was no way to unlock the phone. I had to yank battery to reboot. The phone feature still worked, as I could see the text messages come through on the status bar, and my phone rang, but no notifications cam up on the screen. I was stuck. I did a ClockworkMod backup (aka Nandroid?) and switched to another ROM.
I used unyaffs on my Ubuntu Machine to extract the contents of data.img.
I have the mmssms.db file from /data/com.android.providers.telephony/databases backed up.
Using "SQLite database browser" I can see a preview of the SMS thread.
Technically, I don't need the SMS thread on my phone. If I have a .txt that is neat, organized, and readable, that will be fine. I just assume that I should reinsert the thread (or entire mmssms.db) into my current ROM so I can use SMS Backup and Restore.
My ultimate goal is to be able to get the SMS thread into a text document or large screenshot, which I can send to some friends. It involves a joke/prank, and is quite funny....a bit hard to explain.
How can I get the old mmssms.db (or just one thread) into my current ROM, or into a text document (or something of the like)? I have read something that mentions adb...which I am now Googling to find out what it stands for....so you can guess the amount of knowledge I have on it...
I believe I made that clear....if it is not, let me know, and I'll edit/repost.
tl;dr?
* Need SMS message thread from old ROM
* 1) Old ROM crashed.
* a) Can't get in
* i) Made a backup
* 2) Unyaffed backup
* a) Saved mmssms.db
How to get SMS thread (or entire mmssms.db into new ROM or into text document on computer?
Thanks for all the help!
[::AP::]
Try this on your console, if you have usb debugging enabled.
It should let your phone boot without auto activating the lockscreen.
Code:
adb -d shell
# sqlite3 data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=0 where name='lock_pattern_autolock';
sqlite> .exit
# exit
adb reboot
Edit: Wasnt there a post before saying, if you could get in, it would be enough?
Thanks for the response.
Yes, getting into the old ROM would be enough, so I could use a SMS Backup tool, email the texts, and forget about it.
However, I am pretty new to Android. I'm a bit lost with your explanation.
Console meaning....the terminal in Ubuntu (phone connected?)....Android SDK?
If you could go into more detail, that would be great. Thanks.
[::AP::] said:
Thanks for the response.
Yes, getting into the old ROM would be enough, so I could use a SMS Backup tool, email the texts, and forget about it.
However, I am pretty new to Android. I'm a bit lost with your explanation.
Console meaning....the terminal in Ubuntu (phone connected?)....Android SDK?
If you could go into more detail, that would be great. Thanks.
Click to expand...
Click to collapse
First thing you need to do is make sure you have the android sdk. The sdk are the tools that let you "communicate" with your mobile device through the computer. If you don't have it, google android sdk installation and you should be able to fnd the link. I tried to put the actuall link but I was able to because I don't have more than 8 posts, sorry.
Now you can remove and install files from your android device as needed.
1. Connect your phone to your computer.
2. Using your Linux Terminal, change directory to the platform-tools folder. On my Windows computer I type cd c:\android-sdk\platform-tools but your sdk folder might have a different name so you should type something like this: cd /sdk-folder-name/platform-tools
3. Now type in: adb devices and your devices should be listed. If you get a message saying No Device Found then you need turn on usb debug mode or you need the drivers installed on your computer for your phone.
4.If your device is found, you need to back up your current database by typing: adb pull /data/data/com.android.providers.telephony/databases "directory on your linux machine where you want the files to be save"
5. Now type: adb push "path to the mmssms.db file" /data/data/com.android.providers.telephony/databases and do the same for the telephony.db file. Both of these files must be pushed onto your device in order to see the text messeges.
6. You should be able to see your texts from your old rom now on your new rom. Once you're done just push your backed up mmssms.db and telephony.db file from your newer rom back into your phone.
I don't know of a way to combine the text so this is the way I do it. I hope that helps!
Sorry for the late response - I have been quite busy.
I'll try this out and let you know.
Thanks a ton,
[::AP::]
This is an old thread but I'd like to share my recent experience with restoring SMS messages. Today decided to try mod on my Nexus 6 running rooted stock Nougat. Did full backup with TWRP, tried the mod, didn't have use for it and did full restore. All SMS messages were gone. Checked mmssms.db sure enough size was 0. So why TWRP didn't restore is a good question.
The way is was restored is by extracting mmssms.db and journal from TWRP backup using Nandroid Manager and copying to my location /data/user_de/0/com.android.providers.telephony. Started messenger but still no messages. Opened terminal app and changed ownership and group on both files. After that everything was restored to prebackup state.
I'm trying to do the same thing between a Droid Turbo and GS4. The Turbo screen died, but the phone boots and can go to recovery.
VZW GS4 - 5.0.1
VZW Droid Turbo - 6.0
- I copied the entire /data/data/com.android.provider.telephone directory from the Turbo using ADB
- Copied Turbo mmssms.db to the S4 (renamed the old S4 file mmssms.db.bak)
- Set permissions to 660, radio:radio (as per the old S4 file)
After a restart, Messages showed the old S4 text messages, even though I renamed the original mmssms.db file.
In other words, the S4 shows the old message history, even though the mmssms.db file has changed!
- There were two other files, mmssms.db-shm, mmssms.db-wal
- Renamed these to *.bak
After a restart, Messages now shows no text message history.
When I copied the telephony.db files over, the Phone app went into a bootloop, with a constant repeating dialog that it had crashed. I had to go into adb to reset the files.
It looks like something else is needed to make Messages see the new sms db.
Dear Hjicons,
Could you please give exact commands and what to type in adb shell to change the ownership and group of the mmssms.db and the journal?
Thanks in advance.
I did it "on the fly" without adb, only using MiXplorer
On a rooted Moto G XT1032 running KK
Copy (replace) backed up .db files in data/data/com.android.providers.telephony/databases
set permission to 600 rw-rw---- and owner, group to 1001 radio on all newly replaced files
Terminate (kill) message app, relaunch it and you're good to go, without even rebooting.
I set long press back key to terminate (kill) app via GravityBox
The same you can do with phone calls .db (same dir), or Whatsapp .db, in com.whatsapp/databases, permission to 600 and owner/group Whatsapp, then kill and relaunch
all you need to do, is get the permission XML for from face camera device rom (used the one from VIVO), and push it system, via recovery.
adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot
done
....
PROFIT
PS: this is NOT a flashable zip. but anyone wants to make one, be my guest
thanks to Kali- for the tips
Pushed the xml to the permisions folder with no problems. Ran fix_permissions and rebooted, doesn't appear to have done anything. I can verify that the xml is in the correct folder but google + just doesnt want to do hangouts.
Nexus One running CM7
Any ideas?
EDIT: I was wrong, I thought I would be able to start a hangout but once I found an existing one I was able to join no problem. THANKS!
Qestion
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
jossna said:
Will it happen if you copy the "android.hardware.camera.front.xml" in folder "/ system / etc / permissions /" by Root Explorer, and then restart the phone?
Click to expand...
Click to collapse
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Smtih said:
Yes, you'll either need to manually change the permissions in root explorer to match all the other files in there, or run fix permissions as per the guide
Click to expand...
Click to collapse
Thanks, I try it, but doesn't work
This is how I got mine to work
There were some permissions issues and my phone can't adb anymore for some reason (seems common with the Captivate), so I did the following from Terminal Emulator:
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2
# chmod 777 /system
# cp /mnt/sdcard/Downloads/android.hardware.camera.front.xml /system/etc/permissions/.
# chmod 644 /system/etc/permissions/android.hardware.camera.front.xml
[Restart into recovery mode]
[Advanced]
[Fix Permissions]
And it worked! You just can't create your own Hangouts from the phone. You can join others though using your back-facing camera!
Thanks OP!
Jason Schoenbrun
jason schoenbrun gmail
-------------------
Why does xda developers require we create user names? If there's anyone who knows this, please let me know as I'm curious.
I haven't created a non-email username since the days of AOL. Now I have to make a dumb-sounding faux name like "hotmama2385" all over again? I really wish I could use my e-mail address as my persona. If I can't, at least I'd like to know out of curiosity why the design decision was made to exclude that possibility. of course as a protection from spambots I'd want some of my e-mail address hidden behind a CAPTCHA.
I know some people are privacy focused and/or want to be able to troll anonymously. So why not allow a username which can take whatever form we chose - AOL-esque IDs or an e-mail address - as most login services allow?
As an aside, I have the same question for Twitter, which is the reason I haven't signed up for it. I pushed off signing up for XDA by a couple of years until I absolutely had to because of this, and rarely log in because I can't remember that stupid username. (I just started to a little more because of LastPass.)
Nice work... I'll try this one...
hello,
how to fix permission?
with a terminal
I'm not sure what command that is specifically from a terminal, but you can type adb reboot recovery and then fix permissions via menu option once in recovery.
yep, but the problem I haven t a recovery mode. I want to say no menu.
I have an HTC evo 4g with CM 7.2RC1.
I implemented this fix, and rebooted, but still, when trying to do a video call, it stays on "video initializing" and never seems to finish. I have the latest skype from market.
What to do?
just maybe
So I installed the sdk tools, and opened cmd, and then cd to where adb is. I then copy and pasted the entire string "adb reboot recovery; adb shell mount -a; adb push android.hardware.camera.front.xml /system/etc/permissions/; adb shell fix_permissions; adb reboot" and pasted that into cmd is that all I do. I tried dong just "adb reboot recover" and waiting till it entered recovery, but then I couldn't do anything. after I pasted the entire string, my phone rebooted, and took a sec then started back up normally it seemed. So I think I did it correctly.
Perfect!!! Thanks, works like a charm on my Nexus One
great on arc s for hangouts
It's working great on arc s to create hangouts, but it still does not enable video chat in google talk.
I really don't understand why front camera is a pre-requisite for it. I shall be able to see at least the other's video if he has a front cam, even if they don't see me. Any way to workaround this issue of googletalk? (either to trick it to use front cam or just to display an empty frame, but receive other end's video).
I tried the same to see if it would work for Talk on my Defy, but no success
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
knoober said:
Hi, Im new to this device but right after I got it I did the right thing and voided my warranty Rooted and installed a custom recovery. The recovery has been a bit of a pain but that is a story for another thread.
The problem I am having is that when I try to take a backup from recovery it errors (I forget the error, sorry. ) however the backup is still right there in the backup directory. I tried a second attempt at a backup (to see if it would error again) and these two backups filled my remaining memory. lI of course used my file explorer to delete these extraneous backups-- only to see that they are not deletable. I also tried on the PC. The folder lists read and write in the permissions. I am kind of at a loss as to what to do. IIRC correctly from a while back with this issue the answer lies somewhere in CHMOD, but I cant quite seem figure it out. CD to the directory in a terminal emulator and then CHMOD 777? Thanks for your help in advance.
Click to expand...
Click to collapse
If you are using TWRP, It is not possible to delete twrp backup images using normal ways. Either you can install esfile explorer and navigate to device/data/media/0/twrp/backups/ and delete from there. Or use file manager in TWRP to delete the backups. I think there is also another option in twrp to view or delete backups.
Sent from my Moto G using Tapatalk 2
Ill check out the other things you said, but Im actually getting this problem in ESfile... Ill report back if I can get at it through the recovery.
Edit: ESfile works. I followed the path you laid out ad got there just fine I didnt realize Id have to take such a roundabout path. Thank you.