Related
TitaniumBackup app seems to be Dropbox aware in that it has a button to 'Sync to Dropbox now!' But I am having a terrible time making them work together.
I had a TitaniumBackup folder in the phone from when made before flashing Cog 4.3. I just did another TitaniumBackup to capture all the apps I have added and commanded the 'Sync to Dropbox now!', but I cannot decipher exactly what it did, and where things are stored.
Now,
-my online Dropbox TitaniumBackup folder has some files dated when first backup was made and some from just now.
-same when the Dropbox app is opened on the phone. The TitaniumBackup folder is in the app along with Contacts, Photos, and Public folders.
-same with Dropbox folder on the PC
(I deleted this folder because of the mixed 'versions' of files in it--believing that that deletion would propagate to the phone and to the online store. It didn't. They are still there)
-when I use Root Explorer and look for these files, there is a TitaniumBackup folder in /sdcard/dropbox, and Public is also there, but not Contacts and Photos folders!!! (Why not? they show inside the dropbox app.) This folder also has the mixed dates on the files inside it.
So, I guess my original backup has been destroyed by most of the files being being overwritten (but I do have a copy I saved on an external drive off the home PC).
I just now do not have a feel at all for where the files are created, and where they are copied to if you use the standard "process" ...
When you run TitaniumBackup, where does it put the folder it makes?
When you tell TitaniumBackup to 'Sync to Dropbox now!', what folder (location) does it sync from and to where?
Finally, if you have Dropbox on phone, PC, and the online account, are changes in any of the three locations propagated and to where--the other two? To online only? I ask because the folder deletion on the PC did not get propagated anywhere.
Finally, am I to conclude that your current TitaniumBackup folder should be deleted before you run TitaniumBackup again?
1. when you run a backup the backups are stored in a folder called /sdcard/titaniumbackup
2. syncing to dropbox will only UPLOAD to your dropbox, and not replicate changes BACK to your phone
3. changes all populate through all devices, what you see in /sdcard/dropbox/ are files that you have accessed from your phone and are a local copy, not necessarily a folder that is also replicating to dropbox (from my understanding of using it. i have 30% of 5gb eaten up in dropbox and that folder only contains items that i have opened/uploaded on my phone)
4. NO! you do not need to delete the titaniumbackup folder located in /sdcard/ you can keep appending to it with your sub sequential backups. you just need to understand how to do the batch backups and how to clear out old items that you no longer want in your backup folder (this can be done within the titanium backup app)
Pirateghost said:
...4. NO! you do not need to delete the titaniumbackup folder located in /sdcard/ you can keep appending to it with your sub sequential backups. you just need to understand how to do the batch backups and how to clear out old items that you no longer want in your backup folder (this can be done within the titanium backup app)
Click to expand...
Click to collapse
Thanks; that helps a lot.
On 4, though, I probably want my backups to contain "what the phone looks like right now.' So, I will normally just want to do all apps + data. That is what I did this time, and it seemed to merge the two rather than replace it. That's why I concluded I needed to delete the old backup off the phone, after saving a copy of it somewhere. That brought up the uncertainty then of how the Dropbox synced copies would react.
Wait, wait, wait! I don't understand this...
I downloaded a zip I want to flash to my PC.
I put it into Dropbox folder on PC.
I went into Dropbox app on the phone, the file showed there, press it and it downloads. So far, all is great.
I start ROM Manager to move the file from Dropbox to /sdcard so I can reboot to CWM and flash it.
The zip is not in /sdcard/dropbox !!! But it SHOWS when I open the Dropbox app. What the?
Where is the downloaded zip in the file structure so I can move it to /sdcard?
And arghhhh. Why is this always so hard.
Wtf?
Plug in the phone to your computer and copy the file you want.
You're doing it wrong
Sent from my atrix
Use Dropbox for file syncing, not flashing
I use Dropbox to keep a copy of my backup (created by TiBu). I agree that copying the rom file directly to your computer is far easier than introducing Dropbox.
OK, y'all do it a different way. Mine is wrong because it is different from how you do it. Thanks.
That would still leave my question unanswered...where did Dropbox store the file...why was it not in /sdcard/dropbox?
But later I found it; for some reason, some of dropbox files are where I expected, but THAT download was stored in /external_sd/dropbox for some reason. It is unclear how Dropbox chooses where to put stuff it syncs down.
So I was able to move the file to /sdcard and flash it easily.
This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Nice one
mosen5 said:
This may help anyone who's IMEI got changed or perhaps even deleted by the MIUI MGC 6 or 6.11 update and perhaps even on further updates.
You need "Root Explorer" (or perhaps something similar) from the market and an backup of your original efs folder!
While the initial installation of MIUI there has been a backup folder created on your sd-card. In this folder there is the backup of your IMEI.
To restore your IMEI just copy "nv_data.bin" and "nv_data.bin.md5" files with root explorer to your original efs folder and replace the old files.
After that you must reboot. The IMEI should be restored now.
This worked for me, perhaps it may help you too!
Click to expand...
Click to collapse
This didn't work. I also tried installing EZbase Froyo and the IMEI was still 004999010640000...
Is there a working solution for this yet???
Mosen5, you say to copy to original eds folder. But where is that? Also do I not copy IMEI folder as well (that is within the backup folder)
Its frustrating this as I reflashed this about 5 times now and still stuck with no service.
Updated: Never mind. I found that efs folder (didn't show up with ezexplorer I had used). Pasted those two files and.... it didn't work for me :-(
I even took set it as flight mode, sim out, etc.
I suspect its resetting those files back to what it was because if you try delete them, its back in again straight away. So, pasting those files, would mean it might get reset back to what it had in the first place.
Found a solution. Going along the lines of what mosen5 suggested, but have to use adb command.
Full details here: http://forum.xda-developers.com/showthread.php?t=859914
Important notes the author forget to say:
YOU HAVE TO SET THE PERMISSION ACCODINGLY TO THE OTHER FILES ALREADY PRESENT IN THE EFS FOLDER,otherwise it won't work
Thx
hi every body
plz help me
i want to restor my nandroid back but i cant
( md5 mismatch)
i need it
thankyou
Did you rename the backup folder using a file browser like Root Explorer? If so, you need to change it back.
If you are using CWMR, then the backup name probably takes the format 'MM-DD-YYYY.HH.MM.SS'. Simply browse into the folder, find the earliest modified file or folder and edit the backup folder name accordingly.
Hi all..
So Im pretty new at flashing androids, been using ubuntu for years and am quite familiar with the terminal as well as computers in general. I made the silly mistake of not doing a complete backup of my phone with CWM before flashing with CyanogenMod 9 and now my EFS folder is "empty" but still with Zero free space... giving the "usual" errors":
1) Corrupt or incorrect ( FAKE) IMEI number. (International Mobile Equipment Identity)
2) No Network and Signal ( calls, sms and mobile Internet not working)
3) No base Band or Unknown Baseband
4) Sim card lock missing
as described in the [A.I.O. Helpline] My Android Solutions.
CWM seems to have created a copy/paste backup of my EFS folder (not .zip and not .img, just a folder) on sdcard/efs/backup but the EFS folder is read only and root manager cant paste into it. I've read that deleting the EFS folder should recreate it, I tried in terminal with
Code:
rm -r /efs/*
and got the reply:
Code:
rm failed for /efs/lost+found, Directory not empty
How do I go about restoring the EFS folder?
Finally figured out how to copy/paste into the read only EFS folder! I have searched probably about a million threads, all say to "just copy paste" into the efs folder... but never how to do it when its locked because of read only permissions.
I think im one step closer.. but still not quite there yet.
The way to get write permissions is simply to open terminal and get root access and unmount the efs directory using:
Code:
umount /efs
After that, I could open the efs directory in Root explorer and mount it as R/W. Automatically, I get some default files there created by the system which I can delete and then I could copy/paste my backup into the efs directory. Bang, mobile network running, but baseband version is still unknown. Also, my IMEI number is the generic one, not my unique one
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Snarlster said:
The problem now, is that on reboot my EFS directory goes blank again... anyone know how to continue from here?
Click to expand...
Click to collapse
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
xsenman said:
Solution:- Reason is you had Jumped from GB to JB (should be on ICS before JB), so now you need to
1) Download Root Explorer from Play Store and use it to
2) Search you internal SD card for sdcard/backup/efs
3) Copy nv_data.bin, nv_data.bin.md5 and nv.log paste them into /efs in your Phone memory
4) Reboot to get back your original IMEI
If it gets lost after reboot
Remedies for those who have a efs backup
If you Have a Backup and you want to restore it, this is one method Here or you can use the restore function in the app that you used to back it up
If restoring the efs folder or you have a nv_data.bin backup but if you write nv_data.bin or .nv_data.bak it's being deleted on every boot, than follow this [GUIDE] how to get IMEI to stick across reboots to make it stick.
BUT try this method first
Copy Paste EFS folder with root explorer, after paste , power down phone and reboot into recovery and wipe cache before rebooting....this worked for some
Click to expand...
Click to collapse
Thank you, I had read each thread linking from those threads but it was good for me to do it again!
Flashing the EFS folder with Heimdall gave me the same results as copy/paste, setting the ownership/permissions made no difference in both cases, always empty on reboot.
FINALLY, these are the steps I took to get my phone "working".
1: Odin re-installed the stock I9000JVJV9_OJVJV9_JXJV6.tar file found on sammobile.com as well as the Pit file found on 4shared
2: This gave me an error on bootup... something about "failed to mount dbdata", this was solved with Odin as well by selecting only PDA and using the dbdata.rfs.tar found on hotfile.com.
After this, my phone booted up with the generic imei, a very welcomed change to the previous no imei thats been bothering me! Also, my baseband is showing, the EFS directory is full of files and google play is working... and fortunately, my carrier doesnt seem to care about the generic imei
I'm still going to get my imei back, but first things first! Its time to do some backing up!
Current plan is:
1: Install ClockworkMod
2: BACKUP
3: replace nv_data.bin with the backed up one.
4: reboot / see if my IMEI number is back.
5: BACKUP
6: install CyanogenMod
I hope this helpes someone down the road.. dont be shy on letting me know if my hours of pain helped you!
And... one more thing, my phone is Samsung Galaxy S GT-I9000
Thanks again for pointing me to the right direction
did you only used the PDA included on the I9000JVJV9_OJVJV9_JXJV6.tar file? and how did you use teh dbdata.rfs.tar? thanks.
efs Folder Contents
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
dixielee said:
Hi Guys,
I am hoping you can help me with a problem.
I have a brand new GalaxyS2 i9100, which is on ICS 4.0.4 IMM76XWLPW - XXLQ6 Baseband version, Kernel 3.0.15-1056084 [email protected]#3(SMP PREEMPT Wed Aug 22 2:55:24 KST 2012). The phone is not rooted, but what I did was make a copy of my efs folder to my PC, obviously incorrectly, using My Phone Explorer.
I thought it was just a matter of uploading the folder to my PC and it could be used in an emergency, I thought it would just copy the folder.
What I have discovered, is that all the contents of the efs folder are now on my PC and the efs folder in my phone is empty!!!!
I am now unable to get the files, back into my phones storage.
When I enter *#06# into my phone, the IMEI number shows up and is correct.
I also have a copy of the original efs folder, on my External SD Card.
I have not changed anything else on the phone, other than removing the efs folder contents to my PC. Is there a way, to get all the contents back into my phones efs folder without having to "Root," using say....Emulator or something?
Would a "Hard Reset" on this unrooted stock phone, restore the efs folder to factory settings??
Thank You.
Click to expand...
Click to collapse
I would be careful with that, if you have your efs folder on your sd card, I think it would be better to copy/paste them with root explorer back before reboot... though this is just a guess. In any case, since you have the folder on your PC, then at least you have the backup you need if you get into serious trouble.
If it did reset, please tell us about it in case someone else needs this info later
efs file restore
Thank you so much. After days of not having calling and texting functions available from a corrupted efs folder, who would have thought that a simple copy and paste of the backed up efs to the system would help greatly?
Hey, this worked for me, but I still can't connect to some carriers.
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
lords8n said:
I have a T-Mobile HTC M7 converted to GPE, recently flashed to Lollipop from KK 4.4.4. I use Tasker and OpenRecoveryScript to automate Nandroid backups through TWRP, then use FolderSync to upload said backup to my server over WiFi. My method worked perfectly until I flashed to Lollipop.
Since flashing to Lollipop, whether through Tasker or manually, I get an error in FolderSync saying the Nandroid files can't be read or copied. If I use TWRP's file manager, I can view the Nandroid folders/files, but those same files are not viewable using ES File Explorer in Lollipop. When I navigate to TWRP\BACKUPS\{Serial Number} folder in ES File Explorer, the {Serial Number} folder (where the TWRP backups are) is listed as a 0k(zero) file that can't be read or copied. When I try to create a new folder (in the BACKUPS folder) using ES File Explorer I get an error saying the operation failed.
Just this morning I restored a Nandroid backup using TWRP, and now in ES File Explorer my entire SDcard folder is blank (not true, as all my apps still function), but in TWRP file manager the SDcard folder is fine. At first I thought the problem was with ES File Explorer, but I tried a few different file explorers with the same result (FX File Explorer tells me 'Access was Denied' when trying to view the sdcard folder. ) All file managers I've tried have root access.
I thought Lollipop fixed the sdcard problems from KK, but this is a whole new one for me. Is there an issue with Lollipop not being able to read files that are written through recovery/TWRP? Any help would be greatly appreciated.
Click to expand...
Click to collapse
husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
FAQ
Google Play Edition 5.0.1
SdCard
Q.)
The sdcard not being visible via PC is annoying.
Is there any fix for this yet?
A.)
Yes, here is a work-around
Install Terminal Emulator then type:
Code:
su
restorecon -FR /data/media/0
and sdfix in the play store should do it
husky69 said:
I'm still looking forward to automating my backups and syncing them to my server, but I had a similar problem on my OnePlus One today - the TWRP folder was marked as being a zero byte FILE instead of being a folder. Using Solid Explorer for file management on my devices, and the OPO is running a Lollipop ROM as well. Never saw this on KK ROM or on my Samsung Tablet (KK as well)
So - I'd say it's a good observation that this is likely to be ROM related, not device.
BTW: Would you mind telling me how you automated nandroid and syncing?
Click to expand...
Click to collapse
The issue definitely seems to be related to Lollipop. I didn't have the problem running KK, either. From all the research I've done it seems to be related to Lollipop looking for the sdcard in data/media/0 while KK and TWRP point to storage/emulated/0. The terminal command restorecon -FR /data/media/0 fixed it for me.
As for the automated Nandroid and sync, I use a combination of Tasker, OpenRecoveryScript, and FolderSync on the Android side and a few .bat scripts on the server side.
Tasker deletes the previous backup, copies the OpenRecoveryScript to the proper folder, sets a variable to show backup has started, then reboots into recovery where TWRP then performs the Nandroid and reboots. On reboot Tasker checks that the Nandroid folder exists, triggers a notification saying same, then triggers FolderSync to sync to my server. I only keep one backup on my phone and 2 on my server. I set Foldersync to sync deletions which deletes the previous backup on my server, but I also have my server set to copy the Nandroid to a separate directory, so I always have 2 backups if necessary. I use a script on my server that checks for the newest Nandroid, then copies it to separate directory before deleting the oldest one. When I wake up in the morning I can see Tasker notification that Nandroid file exists and FolderSync notification of successful sync. I also have Tasker set to trigger a notification if Nandroid fails, and Foldersync will also notify if an error occurred during sync. I use a Tasker profile to trigger all of this at 3am but I also have a shortcut that allows me to perform it manually whenever I want, with 1 click.
Note that this method requires the paid version of FolderSync for Tasker integration and is a little involved, but I've tried other methods (Onandroid, etc...), and this one is the most reliable. I know I can count on Tasker and TWRP to do their jobs, no third party necessary. The only redundancy variable I haven't taken into consideration is if the Nandroid backup is corrupt, but TWRP seems pretty reliable in that dept and that hasn't happened yet...
If you're interested, I'll send you the corresponding Tasker profiles and tasks.
lords8n said:
If you're interested, I'll send you the corresponding Tasker profiles and tasks.
Click to expand...
Click to collapse
I am interested
husky69 said:
I am interested
Click to expand...
Click to collapse
Sorry for the delay, been busy with holiday stuff. Here are the Tasker/Nandroid files. Extract the .prf files to /Tasker/profiles and the .tsk files to /Tasker/tasks, then import each into Tasker. You will need to edit (in Tasker) Nandroid_Backup.tsk.xml to reflect your TWRP Nandroid backup folder, and openrecoveryscript (in txt editor) to add/remove backup options if necessary.