Hey Everyone,
I am new to XDA forums,(have used it for troubleshooting in the past but just registered today)
I am also new to android and linux, personally i don't use my phone for anything other than calls or games(i mostly do pc's), however my wife does a lot, she has written her own code, does mods, etc...., and we are both stumped. I am asking this on her behalf, due to a terminal illness she has lost the ability to do several things. On April 30th the lollipop update was pushed to her Note 4 (T-mobile US branded) and it wiped out all of her app data as well as her entire SD card. My question is in 2 parts one regarding the TWRP backup for this phone, and another regarding recovering the SD data from this phone(please let me know if i need to break this out into multiple sections of the site).
We have a TWRP backup that was compressed and loaded onto her cloud storage on 4/27/15, and we are unable to figure out how to get TWRP to recognize it without giving an error about the binary code or just not working period. Here is what we have tried(On advice not just from other XDA posts but various android forums as well)
Using TWRP(7zip for unpacking and repacking)
1. Downloaded the TWRP back up into windows
2. Renamed all files of the back up to be .tar, with the exception of boot which was converted to .img
3. Added Meta-Inf file from what was suppose to be stock ROM( she was not running a custom on this phone)
4. Re-archived everything back into Zip and sideloaded.
result : Error in binary code
Using Odin
1. Converted recovery (file only from backup) to md5 using Cygwin
2. Flashed using Odin
Result: Gained back a few programs but no app data or text histories
We have also tried varying versions of this, i.e. converting extra files or renaming extra files and receive the same issue. I am wondering if it is just an issue with the cloud stored compressed backup(or more likely i dont know what im doing)?
Second question comes from above, I was able to recovery all of the data from the SD card(everything was stored here, app data, recovery files, imgs, everything). When recovering the data it split everything up so all the sub peices of each recovery file are spread out is there a way to combine the individual file parts that were recovered from the SD card into functional android files again?
As i mentioned before i have never really dealt with this type of thing before but i want to try and fix this for her as between the 2 issues she has lost 5 years of data.
Thank you so much for your responses.
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
ShrekOpher said:
Also if the TWRP backup was for a kit at build it will not restore on the lollipop baseband. You will need to Odin back to the kitkat NK4 build them you should be able to take the data.
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
YrrchSebor said:
Hi, what you need to do is put the backup back into the exact same form it was before, an uncompressed, unzipped folder, then put it into the exact directory where TWRP puts backups when it makes them, and then in TWRP choose the option to restore. If you put the backup in the correct directory, TWRP will see it and allow you to choose it to restore it. Basically you just wanna put the backup back where it was before and then restore it in TWRP.
I wasn't sure if you had done this or not. If you have the backup folder with all the contents in their original form, it should work. I've even moved a backup from one phone onto another phone, exact same model of course, and then restored that backup onto the new phone!
I've never converted a backup into another form to be flashed another way, like Odin or as a zip in TWRP. Although I guess it could be possible it seems like it could be pretty messy.
Click to expand...
Click to collapse
Thank you both for the suggestions i will give them a try shortly and i will provide an update on how things go.
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
YrrchSebor said:
Yeah, if you put the backup folder in the right directory, which is either internal or external sdxard/TWRP/BACKUPS/serial #/, you could restore just the data at least and it ought to be mostly ok. You ,might need to clear data in an app here or there if they force close.... or if it's too much then yeah, Odin back to KitKat and restore the desired components of the backup.
Click to expand...
Click to collapse
Thank you for this, i double checked we had it in the right directory, but it still failed. At first it said something about a missing md5, but i tried again and i was able to get the log for the failure though. (attached below)
Hmm, I looked at the logs trying to make sure you chose to Restore in TWRP and not Install. If so it's possible the backup could have gotten altered or corrupted in the transferring back and forth. If you get it intact as it was, it SHOULD work, but I'm but sure what else to do at the moment. I hope you get it working
Sorry for the delay
Hey Everyone,
Sorry for the delay its been a long week, bad thing after bad thing kept happening. I was able to try your suggestions and i put together some additional information in hope this might help us try and figure it out.
*I must figure out how to recover, texts, contacts, call locks. My default texting app was google messenger.
So I figured I would start with the phone
I am using a Samsung SM-910T on 4.4.4 (build *ANK4) It was pretty Vanilla -> rooted, but running the stock ROM
1. The phone was set to do a full internal backup nightly using the online nandroid backup (by H3r3T1L)
2. Backups were set to be in TWRP backup format and to save to an external SD card, then to compress before being uploaded to google drive
3. Backups were set to delete from SD card after the upload was finished.
What happened
1. When stock 5.0.1 firmware OTA came out i was trying to dismiss the notification but apparently hit "accept" by mistake, causing the system to crash.
2. While restoring the phone, i attempted to download the most recent backup from the google drive and flash the zip to restore my data.
3. This Zip would not install, and i noticed all of the backups uploaded had the same anomally-a few of the files were 0 bytes
4. I downgraded the phone to ANK4 based on the above recommendation but it has made no difference.
5. I still get updated binary error and each time i flash the zip, my OS gets wiped.
6. I have tried instructions to just unzip and flash , to put zips in twrp backup folder, to build new file with meta-inf, etc. and nothing seems to work.
When the SD card got deleted I was able to retrieve some data from the deleted SD card, but don't know where the text messages are located or how to combine them back into a usable format. Or at the very least be able to extract the SMS/MMS history.
I hope this extra information helps. In any way im am desperate to try and fix this for my wife.
I believe you can use Titanium Backup to extract files from a TWRP image. If you can't extract anything from the backup it's either corrupted, in the wrong place, or in the wrong form - that is due to the compression decompression not being compatible (all zip programs are not equal). Best of luck.
BTW, you must restore TWRP files not install them.
Sent from my SM-N910T using XDA Free mobile app
Related
Hi,
Ive always used CWM to make my recoveries. But now, with Nexus 7 (CWM touch 6.0.1.9), Im unable to locate the backup files. There is no BACKUP folder in the clockwork folder and while I did a search using google and found many answers for my question, none of them was right. And I didnt make update from 4.1.2 - I cleaned the whole device and flashed stock 4.2.1 via fastboot, so I dont believe there is some directory tree change mess. And there is no BLOBS folder either.
I just flashed the ROM, rooted it using Toolkit, flashed CWM, made a backup - and boom, nothing there, while it is visible in both CWM recovery and ROM manager. I tried renaming the backup in ROM manager and searching for its new name using File Manager (with root privileges), but I was unsuccessful ...
So, please help me or provide me with a relevant link as I dont like TWRP ...
EDIT: I deleted the /SDCARD/CLOCKWORK folder and flashed TWRP. Now, I returned to CWM, made a backup using CWM and not only I dont see the backup itself, it didnt even recreate the CLOCKWORK folder. I just made a full search in the whole filesystem and there is nothing with "clock" in name (nothing relevant). Where is the backup hidden?????
Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app
r3a1ist said:
Tried using it today. Its in some God forsaken rabbit hole. First enable root in es file explorer settings. Then look in system for data, media and eventually clockworkmod. That's the help I can give u.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that not the place for me. /data is empty and the only folder found containing "clock" in the file structure is /sstorage/emulated/0/clockwork ... the same as /sdcard/clockwork I was talking about. only three small files and thats it, no BACKUP or BLOBS.
GOT IT!!! I dont know why it wasnt visible with rooted File Manager, but I tried ES and its there ... bam ... THANKS A LOT!
Now, whats the best way to save this stuff to a computer?
its because Jellybean 4.2 uses diff storage paths...
Android 4.2 significantly changes the way how sdcards are handled internally, your data is moved from /sdcard/ into /sdcard/0 on first boot (0 is the 'home directory' of the default user). If you go back to 4.1.2: Don't forget to move the data in 0/ back to the root of your sdcard.
Click to expand...
Click to collapse
Ather said:
its because Jellybean 4.2 uses diff storage paths...
Click to expand...
Click to collapse
Well, Im aware of that. But that doesnt explain why the files are under /data/media/clockwork. Neither it does explain why it wasnt shown/found by File manager with root privileges - although I guess its the problem of the File manager, as ES File Explorer sees that without any problems ...
Now, I switched CWM to save to TAR and made a backup. It created a folder "/data/media/clockwork/backup/2013-01-08-1214" with 9 files, size about 1,1GB. Is it sufficient for me to copy this file to my computer? Im talking about backing up the backup (heh) ...
Also, is it ok that files cache.ext4.tar, data.ext4.tar and system.ext4.tar are 0mb? Thanks!
EDIT: I tried moving a backup folder to my pc, making factory reset, copying it back to where it was and restoring - everything works fine. Although I dont get why google messed the sw insides so much - my Nexus S seems to be much better in the matter of directory tree - and doesnt wipe all my files when doing stock restore from PC ...
Please help me! I was on Sense 5 rooted with twrp installed. Decided id try out the new CM 10.1 for the HTC ONE. So i backed up my system, data and everything else and proceeded to install CM. Decided it wasnt for me, went to TWRP, went to restore and there are no files there? What happened? I can see I only have 6GB storage available so the file is there somewhere!! How do i flash the backup? i read about a twrp utility or that the file structure is off?
Thanks for your help!!
UPDATE: When I go into a file manager, the backup from today is there.. it is in TWRP> BACKUPS> HT34JXXXXXX> (2013-05-14 @ 8:06 AM)
and inside that folder are the usual backup files. BUT IT STILL WONT SHOW UP IN TWRP WHEN I PRESS "RESTORE"
Anyone? I'm dieing here!!!
Reflash recovery, and see if now work.
I've restored yesterday my backup and no prob with TWRP.
And search your file in sdcard/0
If it will not work, reflash rom.
Don't know if this happened but I had a galaxy s3 before I got the htc one and I understood that cyanogenmod is a 4.2.2 type of rom and we have a 4.1.2 rom. A lot of peeps in the galaxy's forum would have trouble going back to touchwiz roms because the say flashing a 4.2.2type of rom partitions the memory files differently so then the 4.1.1 stock or custom roms. You may have to somehow unroot the phone and "push" the phone back to stock using your computer. People had to do that before with the s3. Hope that helps maybe. I have to go to work now. Good luck
Should I try to flash clockwork mod? Just go into the play store, download and flash from within the app? I don't understand I made a full nandroid it is in my phone and on my computer.. Why can't twrp recognize it?
Okaay said:
Should I try to flash clockwork mod? Just go into the play store, download and flash from within the app? I don't understand I made a full nandroid it is in my phone and on my computer.. Why can't twrp recognize it?
Click to expand...
Click to collapse
CWM can't restore TWRP backup.
If you backupped your rom with TWRP, this will restore it.
Did you try to see in sdcard/0?
Guich said:
CWM can't restore TWRP backup.
If you backupped your rom with TWRP, this will restore it.
Did you try to see in sdcard/0?
Click to expand...
Click to collapse
This is in the stock cm10 file manager. This is the exact backup I'd like to restore but when I go into the recovery and press on restore, nothing shows please keep responding!!!!
For team win recover the files need to be in /sdcard/0 the number zero or it won't be recognized. Move the directory structure to /sdcard/0. Also copy the directory with the backup to your computer in case.
Can we see the whole directory structure of where these files are located? like /recovery/2012305/ or where ever it happens to be?
nullkill said:
For team win recover the files need to be in /sdcard/0 the number zero or it won't be recognized. Move the directory structure to /sdcard/0. Also copy the directory with the backup to your computer in case.
Can we see the whole directory structure of where these files are located? like /recovery/2012305/ or where ever it happens to be?
Click to expand...
Click to collapse
Yeah man, I'll post the pics. Here they are looks as though it is in 0/
I just backed up the cm ROM just to see what would happen and now when I go to restore, the cm10 backup is the only one there and I can't locate it in file manager anywhere
Sent from my HTC One using xda app-developers app
Okaay said:
Yeah man, I'll post the pics. Here they are looks as though it is in 0/
I just backed up the cm ROM just to see what would happen and now when I go to restore, the cm10 backup is the only one there and I can't locate it in file manager anywhere
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Search the SD card for boot.emmc.win you should get two results one from the original backup and one from the new one. You need to get both the backups together. Also copy your original backup to your computer so you have a copy of it in case you need to wipe or something.
nullkill said:
Search the SD card for boot.emmc.win you should get two results one from the original backup and one from the new one. You need to get both the backups together. Also copy your original backup to your computer so you have a copy of it in case you need to wipe or something.
Click to expand...
Click to collapse
This is what I see... Someone please help, the backup I wanna restore is already I'm TWRP folder on the internal storage but no files show up when I try the "restore" option in the recovery
Sent from my HTC One using xda app-developers app
Okaay said:
This is what I see... Someone please help, the backup I wanna restore is already I'm TWRP folder on the internal storage but no files show up when I try the "restore" option in the recovery
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK so did you copy your backup to your computer yet???? Well if not now would really really be the time to do that. Looks like there is a issue with how CM is doing the SD card and TWRP. So first copy the backup off of your phone. Should I say it again? COPY THE BACKUP OFF YOUR PHONE. Now go get the correct RUU for your phone. Run that sucker and restore the phone to stock. You will need to relock your bootloader. Once that is done put TWRP back on your phone and copy your backup to the phone.
Ran into this myself. Because of 4.2.2's support for multiple users, it segments the internal storage into pieces(i.e. 0 for first user, 1 for second user, 2, 3, so on). I didn't realize this and had to start from scratch.
Copy your TWRP backup(and anything else you don't want to lose) to your computer and delete the 0 file. Re-add your files to the internal storage(be sure to keep a copy on your computer). Then reboot into bootloader, fastboot erase cache, reflash, and reboot into recovery. Don't let the CM10.1 ROM start up, otherwise you'll be doing it again.
Alternatively, use the All-In-One toolkit to adb sideload a non-CM10.1 ROM onto your phone, delete the 0 folder(after transferring to your computer what you don't want to lose, of course), reboot recovery, and attempt to restore.
Thanks guys, got it working
Sent from my HTC One using xda app-developers app
This is the same problems people with the GNex came across moving back from 4.2.2 to 4.1.2 last year - you have to remember the internal memory changed and manually move fles to the non-0 folders! You guys should read up more before jumping head long into a new Android version!
Glad it's sorted now though
nullkill said:
For team win recover the files need to be in /sdcard/0 the number zero or it won't be recognized. Move the directory structure to /sdcard/0. Also copy the directory with the backup to your computer in case.
Can we see the whole directory structure of where these files are located? like /recovery/2012305/ or where ever it happens to be?
Click to expand...
Click to collapse
OOPs--sorry this must be an HTC specific problem--sorry for poking my Samsung nose in...
Maybe I am not understanding the thread but--
In my Galaxy Note2 all my TWRP backups, and I have about 5, are all in ext.sd. card and I have used it to restore on several occasions--could be a device specific situation, but in Note2 it's fine to have them in ext.sd card.
I have an "almost perfect" stock Nandroid build of 4.06.1540.3. Right now, I have not installed any of my own data, except for Contacts and preferences at the Google Play Store. I have also installed a custom recovery (TWRP 2.6.3.3) and rooted the device.
I think my previous backups may have contain corrupted data, as I got multiple error messages when trying to connect to Google and restore contacts. So, I went back to an earlier backup and restored from there. Everything is working now, and I don't want to "screw up"!
What I would like to learn how to do is to make a reliable - i.e. "no corrupted data"- stock backup with a stock recovery so that I may restore it if necessary. Also, would like to be able to take this Nandroid backup and save to a PC so that I can restore from it later.
Please tell me how to do this! Also, will I need to know how to save the file to the computer - as a zip file or as an image file. Right now, I don't know how to do either of those things! TWRP saves the backups as multiple archives rather than as a single zip file or image. Also, which is the preferable method to save the backup as - zip or image file? I would very much like to make this file available to the Developers on this forum as I know that they do not have this particular OTA Nandroid backup posted and I want to help them out! But I think that they would prefer the zip format of the file with the stock recovery.
Please advise! I would be most appreciative, truly!
gingerlindsey said:
I have an "almost perfect" stock Nandroid build of 4.06.1540.3. Right now, I have not installed any of my own data, except for Contacts and preferences at the Google Play Store. I have also installed a custom recovery (TWRP 2.6.3.3) and rooted the device.
I think my previous backups may have contain corrupted data, as I got multiple error messages when trying to connect to Google and restore contacts. So, I went back to an earlier backup and restored from there. Everything is working now, and I don't want to "screw up"!
how to do is to make a reliable - i.e. "no corrupted data"- stock backup with a stock recovery so that I may restore it if necessary. Also, would like to be able to take this Nandroid backup and save to a PC so that I can restore from it later.
Please tell me how to do this! Also, will I need to know how to save the file to the computer - as a zip file or as an image file. Right now, I don't know how to do either of those things! TWRP saves the backups as multiple archives rather than as a single zip file or image. Also, which is the preferable method to save the backup as - zip or image file? I would very much like to make this file available to the Developers on this forum as I know that they do not have this particular OTA Nandroid backup posted and I want to help them out! But I think that they would prefer the zip format of the file with the stock recovery.
Please advise! I would be most appreciative, truly!
Click to expand...
Click to collapse
your too late the developers already have it
InsertCoin 7.0-6 | Stable | Mods | Performance | Sense 5.5 | Android 4.4 | KUSTOMIZER 1.2.2 | 4.06.1540.3
The Next Chapter! v1.0[4.06.1540.3][APM][HEQS]
SkyDragon v 4.0 4.06.1540.3 ANDROID 4.4 KIT KAT-Live Support!-OTA-SDHUB
if you just want a copy of it for yourself for later just hook to the PC and copy it from TWRP/Backup/HTxxxxxxx/2013-12-xx to your PC
Thank you, very much for the reply, cisA! I really wanted to help out, here! As for backing it up to my computer, how do I save as a zip file? Recompile it into a single image from the multiple archived files and then zip it? Sorry, for being such a noob!
Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.
Curious D said:
Hi. I'm new to rooting and flashing ROM's. I have had a Samsung Captivate (Gingerbread) that I haven't been using for quite some time and I thought I might try to update it to KitKat. I have read that it would be important to back up the EFS file so that I can keep my IMEI info. I rooted my phone using the tutorial on these forums and tried to use EFS Pro, but was not able to get past "the device is not perm rooted". Various threads suggested changing adb status, but I could not find that information (though I was able to find the USB debugging selection). I know that the phone is rooted so I looked for an older copy of EFS Pro in case the newer versions had dropped support for the Captivate. I couldn't find one so I looked at other ways to back up the files, but most information was for other (newer) Samsung phones. I could not install Samsung Tools. I really don't want to proceed with installing KitKat before backing up the EFS information. How do I go about doing this? I have tried the search function on the forum for this device and couldn't find what I was looking for (or maybe I didn't understand the information). Any thoughts?
I hope flashing KitKat will be easier than this issue...
Thanks.
Click to expand...
Click to collapse
You could just manually backup your efs folder using a root explorer or through adb. Have that backup on your pc in case you lose your IMEI.
That being said, when it happens (which is fairly rare), a flash back to stock (KK4) usually fixes it and then you're fine to update/flash again.
Other EFS backup options would include:
1) EFS☆IMEI☆Backup by wanam >> his xda thread, his playstore listing.
2) [HOWTO]Comprehensive IMEI/EFS Backup lists two simple ways to permanently backup up IMEI on your phone. One is with adb, the other is with Terminal Emulator for those with rooted devices. The commands used are said to be based on "Samsung's built in backup." The thread is in the SGS3 forum, if nothing else is an excellent source of background information for backing up and restoring nvdata.
I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?
Curious D said:
I tried to copy the efs folder using Root Browser because the adb method looked very involved. When I started Root Browser, it was able to see a Titanium backup that I had placed into the SD card even though I had formatted the SD card. I figured that the format didn't wipe the information so I proceeded to copy the efs folder over. However, after copying the folder, I stuck the card into my computer and did not see the folder and could not copy the folder over to my computer. Is it because the card is formatted differently than my computer or is it that the file is not compatible with Windows given that it is an Android folder?
Will copying the folder be enough for backing up? If it is this easy to restore the efs, why use EFS Pro? Is there something else with the folder that needs to be present in order to restore a phone that loses IMEI information?
Click to expand...
Click to collapse
If you have it on your SD card, it should be fine. The idea is to have it on something else than your device's internal memory in case something goes wrong and can't get it there.
As for efs pro, some devices can't manually backup like the Cappy or is not enough. But once again, it doesn't happen very often that you lose your IMEI.
Okay. That's great. I guess I can try my first ROM flashing to KitKat. Thanks.
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work. Chmod 755 and 777 doesn't do anything. I was able to initially copy the TWRP folder into the downloads folder in the TWRP file manager, but now it just hangs there if I try to move it again.
How do I get access to my backup?
evanft said:
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work.
How do I get access to my backup?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
6Binford said:
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
Click to expand...
Click to collapse
Unfortunately, there aren't any solutions in that thread.
evanft said:
Unfortunately, there aren't any solutions in that thread.
Click to expand...
Click to collapse
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
josephpalozzi said:
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
Click to expand...
Click to collapse
I didn't even see GeoFX's post for some reason. That looks like it worked. Thanks!
TWRP and NAND Backups
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Florestan2 said:
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Click to expand...
Click to collapse
The way I understand it, and I might be wrong, is that before Android 4.0 (or maybe 5.0), the partition containing user data was called /sdcard and apps were stored in a separate partition. The partition where apps went was significantly smaller, which could result in people running out of space for apps while still having a ton of free user data. To remedy this, the newer version of android places apps and user data in the same partition (called media). The /sdcard that you see is a symlink (shortcut) to this new partition, and is included so that older apps that were designed to expect the /sdcard partition to be there will still work.