Hey,
Can someone provide me with the telephony files for Optus?
/data/data/com.android.providers.settings/databases/settings.db
/data/data/com.android.providers.settings/databases/settings.db-wal
/data/data/com.android.providers.settings/databases/settings.db-shm
/data/data/com.android.providers.telephony/databases/telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db-journal
I flashed to ICS and forgot to pull these from my rom. I took a nandroid backup but for some reason it's corrupt, don't know why but now I can't restore my backup
Thanks!
No need to worry, I managed to locate the files on my hard drive!
Related
I flashed my phone to JF 1.5 and in the process some how managed to screw up my sd card and lost all my apps. i did do a nandroid backup of jf 1.41 so i ahve those img files. I tried to restore to that to recover everything but it wont boot past the g1 logo. I tried downgrading firmware to 1.43 (couldnt find 1.41) and using the same restore for nandroid and still wouldnt boot. I also tried jsut applying the user data img to see if i could jsut grab that and it fialed on both firmware revisions 1.5 , 1.43.
In the end im stuck with a backup i cant use, the only thing i need off of it is the apps. I read that you can use the emulator to mount it but i couldnt figure that out. I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Anyone have a simple solution or a complex one i can follow to getting my apps out?
did you follow this?
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
darkrangr said:
I also looked at yaffs extractor from the google code site but i wasnt quite sure how to compile/run it.
Click to expand...
Click to collapse
You go into the source directory, type "gcc -o unyaffs unyaffs.c", then you (create and) go to some directory where you want to extract the contents ("mkdir ~/extract") "cd ~/extract", and finally you extract the image "/path/to/unyaffs /path/to/data.img".
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Unless your backup was corrupted, flashing the backup should have been fine.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata data.img
You said it failed - what error did it give? Did it say it couldn't find the command? Be sure you're running these commands on your PC with your G1 connected via USB, the correct drivers are loaded, and you have the fastboot program.
As for using unyaffs - I don't think you understand what you have to do to use it. You have to compile it on your PC...all you get is the source code. I haven't looked on the google code site, but I would imagine there isn't a version for windows.
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
it didnt fail on the restore with fastboot, it loaded up everything fine and then when i rebooted it just sat on the boot screens forever and never loaded.
I am feeling nice so darkrangr if you want to PM your image files I will unyaffs it on my ubuntu box for you.
TemporalShadows said:
EDIT: After reading your original post for a second time, I have to ask: if you screwed up your SD card and lost all of your apps, does that mean you were using Apps2SD? That's a bit of an important detail to leave out, if so. Unless I'm mistaken (and someone correct me if I'm wrong), your apps wouldn't be in the backup anyway, you're wasting your time. If your backup is just restoring the symlinks to the SD card and the SD card is screwed up, then no wonder it's hanging at boot. You'd need to wipe your SD card and start from scratch. I'd recommend doing that either way - would you rather have to redownload a few apps or continue having a bricked phone for days?
Click to expand...
Click to collapse
no, my apps were installed normally. I am running curent jf firmwar enow while i try to get my stuff back, but some of the apps i had are no longer available or have converted to pay apps, plus i forgot a lot of apps i had.
http://forum.xda-developers.com/showthread.php?t=497034
In the other tools archive on this post you can find the unyaffs tool fully compiled. Just move your image to the same folder, drag and drop it on the unyaffs.exe and watch the files appear.
How about YOU DIDN'T INSTALL GCC!!!
darkrangr said:
I tried the standard nandroid restore and it failed.
Trying the yaffs thing now and i got an error.
I placed the yaffs files all in a folder on the sdcard and put the img in that folder as well.
I open the terminal on the phone and did cd /sdcard/nan nan being the directory i made
I then tried to run that command "gcc -o unyaffs unyaffs.c" and i get gcc not found. what did i do wrong?
Click to expand...
Click to collapse
Hello .
Posting a tutorial on how to create a dump out of your stock rom, in case you delete some apps or modify some settings.
ALRIGHT LETS START:
STEP ONE:
Alright, so you want to make a backup of your phone software, but dont know what to do. Its simple, download the package the Android SDK from google and copy it to C:\ drive. Once you have download it, make sure you have Java installed in your system or else it will not work. After everything is done, open the program and install these two packages:
1. Android SDK Tools, revision 6
2. USB Driver package, revision3 ([COLOR="Red"IMP: Its important that the USB driver installed shows up as Composite Android Debug Device, else it wont work. ][/COLOR]
What Android SDK ?? Read about it here: [url]http://developer.android.com/sdk/index.html[/url]
Why Android SDK ? Because: it has the [COLOR="red"]android debug shell[/COLOR] which you require before communicating with your android phone. So download it ! From here:
STEP TWO:
Download Busybox from here : http://rapidshare.com/files/407238531/busybox What is Busybox ?? Read about it here: http://www.busybox.net/
MD5 Signature: C5B76280434EEF49310AD8F1810B10B2
STEP THREE:
One you have downloaded busybox, copy it to the C:\ drive of your computer and then follow the next step. The next step is to open the Command Prompt ( type cmd in the Run prompt ) if using Vista right click on "Run as Administrator".
Assuming you are the root of C:\
Type: C:\cd android-sdk-windows
-> then
Type: C:\android-sdk-windows\ cd tools
-> if you have android debug shell and USB drivers properly installed
Type: adb devices
Now your device will show up as a binary number .. Success ! if it doesn't show up you need to install the drivers again or something else is wrong.
STEP FOUR:
Now once your device shows up, we will need to download the busybox from the computer to the phone. Since we can write anything in the /data/local portion of the android system we will copy the busybox file to the android device.
Type: adb push busybox /data/local/busybox
Once it has been copied to your device issue this command.
Type: adb shell This coomand is issued to go to your mobile's terminal where you can issue commands internally to the phone.
--> then
Type: cd /sdcard This command is given inorder to go to the sdcard ( i.e the internal storage of your phone )
--> then
Type: chmod 755 /data/local/busybox This command is issued to set user -rwxrwxr-x permissions to the file.
--> then
Finally, issue this command.
Type: /data/local/busybox tar cvf Samsung.tar /system This command is given to copy and tar the system folder where all the stock applications and programs are and to create a dump of that system folder.
STEP FIVE:
Job Done !!
The Samsung.tar file can be copied to the computer now. Have fun.
this is perfect, as i want to create a dump of my original ROM
A dump is simply a backup of your original ROM right?
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
OrionTC said:
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
Click to expand...
Click to collapse
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
is there a way for us to backup the firmware?? (not just stock apps)
tids2k said:
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
Click to expand...
Click to collapse
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
droidwi said:
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
Click to expand...
Click to collapse
Correct. We most likely won't be able to actually perform a complete backup until Nandroid works on the handset.
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
supercurio said:
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
Click to expand...
Click to collapse
im working on creating a stock rom ... may be some happy results and happy faces. who knows . keep sticked !
uploading dump again .. please wait.
So, Can i just select this dump in Odin and it will recover to stock firmware. Quite confused here.
The file size is 275 megs , so is it only for apps? Have you flashed with this dump. Nice work so far. THanks.
Edit: Just realised the dump option in Odin is for dumping my rom , not loading one.
So stuck with this until Samsung update. Huh!
Is this the same procedure as making a backup /efs?
I've been searching the forum for hours and this is the only thing I could find that looked anything like it.
This won't work
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Plinn said:
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Click to expand...
Click to collapse
+1.. The thread is misleading.. This doesn't accomplish anything! You really think people in the "Android Development" section don't know about tar?
Did anyone already managed to get the built-in dump function from Odin working?
With Odin v1.3 there was the possibility to decide whether to dump AP RAM or AP NAND (followed by an ID).
With Odin v1.52 you can't choose this anymore. It will only dump AP NAND.
But my first attempts were unfortunately not very promising
Long story short, I accidentally restored a titanium backup of system settings from a different phone and now several of my features don't work. Could someone please provide me a copy of their settings.db? I think it is located in: /data/data/com.android.providers.settings/databases
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
gale2000 said:
When I try to copy my TWRP backup file to PC only the two boot files will copy. Is there a way around this. How would I pull the files using ADB? I have 4.3 and TWRP 2.6.
Click to expand...
Click to collapse
Same issue....only two files copy over. It has to do with permission changes of the backup files with TWRP version 2.6. I tried doing an ADB pull in Windows, but could not get it to work (Various errors). I would also like to know the proper method to do this.
EDIT: Finally got the adb pull to work and all the files were copied over.
So I was able to do a full adb backup when I was on 4.1.2 before I updated to 4.2.2.. I wanted to do another full adb backup again on 4.2.2 before putting a recovery or custom rom on my device so it would be easy to restore back to my completely stock experience (with root) if I choose. But for some reason after letting it run all the way through (I let it run overnight since it takes so long) the backup is nowhere to be found which leads me to believe it failed somewhere along the way, but no errors are reported. Has anybody had this issue or have any advice on what may be going on? I've tried doing:
Adb backup -all
Adb backup -all C:\Users\Wyth\Desktop
Adb backup -all G:\ (external HDD)
Adb backup -all G:\xtzbackup (in case adb backup had some sort of bug saving to the root of the drive)
If anybody has any help or alternative solutions to creating a full system backup I'd appreciate it! Thanks in advance!
If you are going to supply a path and file name, don't forget the -f switch
dph3055 said:
If you are going to supply a path and file name, don't forget the -f switch
Click to expand...
Click to collapse
Thanks, that was absolutely the issue. I guess I did that the first time around but forgot the second. I ended up making the backup and then unlocking the bootloader. Unfortunately I forgot that it would completely wipe the internal storage rather than just a factory reset, so I lost my titanium backups. Tried to do the adb restore, and every time after the first app it would just reboot the device. After trying it many times I ended up using the adb extractor tool to create a tar from the backup. Apparently however the backup was no good because when extracting the tar after getting to a certain part every time it came up with unexpected end of archive. But I at least got most of the titanium backup folder out. Tried copying that to internal storage and it was permission denied. Copied it to external sd, and then on the tablet transferred it to internal storage. Then every time I restored any of the data, when I rebooted the tablet it would go into bootloops. After many ftf flashes and time wasted copying things back and forth all over the place I finally am basically just resigning to starting over. Boot into CWM and made a backup, and find that it makes the clockwork mod backup folder in data/media rather than the proper place in data/media/0 or even data/media/legacy. The option to backup to external sdcard also doesn't work, as it refuses to mount sdcard or external-sdcard. Needless to say the last 24 hours or so has been massive headaches. Is there a newer version of CWM for the tablet than 6.0.3.2? It seems pretty buggy and hard to believe that it is what everyone has been using as the button combination to reboot to recovery doesn't even work.
Btw, I'm trying to do this on the stock sony 4.2.2 firmware for sgp312.
Using kernel and recovery from here:
http://forum.xda-developers.com/showthread.php?t=2433466
with ftf from here:
http://forum.xda-developers.com/showthread.php?t=2424550