Develop Bugs

Replaced Evo, nandroid missing files

Recently I had to have my evo replaced because the mic died. sure was nice to spend 35 bucks instead of 400. after a little work i got it rooted and flashed and made a fresh nandroid of the new rom. I noticed that titanium hadn't backed anythingup lately but I had made a nandroid before taking the phone in. After a little research i moved the old nandroid to the new nandroid folder (serial numbers and all that) and proceeded to wipe everything and restore nandroid. Now I have almost everything back... except most of my apps. seems they were on the sdcard and now don't want to play nice. I can go to manage applications and sdcard and they are there but greyed out and unchecked. if I tap on one, it will crash immediately. I tried fix_permissions which ran for a few mins but nothing changed, so i rebooted again. still nothing. is there another solution for this or should I just attempt to pry open the img file and extract my data there? If so, where would said app data be? not the apps, but their data for saves/bookmarks/etc. Any help would be appreciated, this has been very frustrating.

Use Root Explorer to check whether the data's there (in /data/data) and whether the APKs are missing (/data/app if they were stored on the phone, /mnt/asec if they'd been moved to the SD card). You probably just need to reinstall the app, though you should backup the data just in case.

seems that the info is there in data/data, but not in data/apps. mnt/asec is also empty, though I recall moving most of my things to sdcard at one point. how can I copy data/data to my pc? can't seem to mount it where the pc will see it, even through recovery.
I decided since I can't mount it for some reason (lack of knowledge comes to mind) that I would just unyaffs the files. how would I push the data/data files back to the phone?

Restore TWRP .ext4.win to Windows or Linux?

I have a backup made with TWRP 2.6.0.0 of boot/data/system that were saved as .ext4.win files by booting into TWRP and doing a backup.
However, when I tried to browse the file using Nandroid Manager 1.4.1, most (but not all) of the app directories in /data/data/{packagename} are missing their actual data. They have a lib dir that's a <link>, but nothing else. However, some apps DO appear to have their normal and expected data. I could understand if NONE of them did... but I'm mystified as to how SOME could have data, but others that I know for a fact store data in /data/data/{packagename} are coming up empty.
I can think of a few possibilities:
* For some bizarre reason, TWRP didn't back up the files for certain apps. Unlikely, unless Illusion 4.2.2 (based on SlimRom/AOSP 4.2) was doing something weird with symlinks that confused it.
* Nandroid Manager 1.4.1 mangled the backup files while uncompressing them. Oh ${deity}, I hope this isn't the case. It never even occurred to me that it might try to uncompress the originals "in-place" and delete the original copy when I ran it and gave it the OK to uncompress them first.
* Nandroid Manager 1.4.1 uncompressed them fine, but for whatever reason can't explore the uncompressed backup properly.
I copied the .ext4.win files to Windows and tried finding something that can explore them, but I'm coming up blank. I tried ext2explore from Sourceforge, but it silently ignores me when I try to browse to the .ext.win file as a filesystem to mount.
Any ideas what to try next, either Android-side (Nandroid Manager 1.4.1 itself is the problem, and hopefully didn't mangle the backups themselves by attempting to uncompress them) or Windows-side?

Update: I have another theory. At the time I did the backup, my phone was bootlooping (it made it up to the converging-diverging RGB spotlight animation, then stayed there forever). To reboot, I had to 3-finger it (power+home+down or up, don't remember which one I used at the time).
I'm wondering whether it might be a case of TWRP backing up the raw image of a dirty ext4 partition that had uncommitted data in the journal, and the recovery tools that I'm using to explore it for individual files are blindly mounting it like an ext2 volume & causing any file written by an actively-running application to show up as "gone" instead of showing the old version.
If that's the case, would treating the .ext4.win file like the output of 'dd', then running an ext4 repair tool on it, be likely to fix it? I'm somewhat familiar with issues like this, but I've never actually had to deal with one head-on, so I'm a total n00b when it comes to the details of mounting a Linux filesystem from a dump file and allowing Linux to fix it as if it were rebooted into a dirty filesystem.

[Q] Strange file directory structure

I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:
Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​
Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica

re: nandroid backup/restore
verngator said:
I’m rooted and using CW for my recovery. I’m using a pre-owned phone that I (thought) I wiped before rooting. I am running stock 4.2.2, baseband MDL.
Initially all I wanted to do was nandroid to my SD card in preparation for flashing a custom ROM. I have a 32GB card that my phone recognizes just fine, so I thought it would make sense to put the backup there. So I enabled Use External Storage in ROM Manager settings and tried to begin the backup process.
First I tried it using the ROM Manager itself. Got this error message:Unknown volume for path [/external_sd/clockworkmod/backup/name of the backupfile here]
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log
Please open ROM Manager to report the issue​Then I tried doing it by going straight into Recovery and initiating it myself. That was in the Backup and Restore menu. The Backup location options were
/sdcard
/storage/sdcard1
Neither of those is the external card. Then I looked at the Advanced menu but there was no option that mentioned the external card. So it seems that the Recovery doesn’t see my external card. And the subdirectory options that Recovery wants to use do not exist on my phone.
At first I thought it was my SD card. I removed it, re-formatted it (non-Quick) on my computer, etc. I was still not able to save my recovery to my SD card. Again I see that CW want to put the recovery in a subdirectory that does not exist.
I was able to nandroid to the internal memory, so at least there’s that. But the file directories on my card are a mess that make no sense and don’t seem to match what I’ve seen on multiple forums.
Using ES File Explorer I see this from the root directory -
/storage/emulated/0
/storage/emulated/legacy
/storage/extSdCard
/storage/sdcard0 – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
/storage/container – this one has a little arrow at the start of the pathname. Does that make it a shortcut?
Also from the root directory I see this –
/sdcard/ – this one has a little arrow at the start of the pathname
Then there are these –
/mnt which seems to have copies of sdcard and extSdCard
/mnt_1 which just has extSdCard, sdcard_1, sdcard_2, and sdcard_3
I’m running 4.2.2, baseband MDL. What I would like to do is get the directory structure back to stock and remove all the multiples of data and folders that I am seeing.
1. If I totally wipe the phone, will the stock file structure be restored?
2. If the answer to #1 is “yes”, what happens if I do an Advanced Restore, restoring Data from a nandroid created with the screwy structure? Does the screwy structure return?
Thanks,
Veronica
Click to expand...
Click to collapse
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!

Misterjunky said:
If you wipe the phone using it's internal "factory data reset"
(settings>accounts>backup and reset>factory data reset)
It will restore the stock phone's internal sdcard's structures, directories and folders.
But what I would suggest is to download and odin flash the TWRP custom recovery,
that way you will not loose any data or user files and you will not have any problems
making or restoring nandroid backups.
TWRP is really easy to use and basically self-explanatory.
Here is the direct download link for TWRP: http://techerrata.com/get/twrp2/jfltetmo/openrecovery-twrp-2.6.3.1-jfltetmo.tar
Good luck!
Click to expand...
Click to collapse
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?

verngator said:
Thanks!
Are you saying that using TWRP will preserve the file structures and that CW has some kind of effect on them...or that CW is the reason I can't put my backup on my SD card?
Click to expand...
Click to collapse
CWM or TWRP do not effect the file structures.
All I am saying is create a nandroid backup using TWRP and then restore
the backup. Then if it works properly for you then keep using twrp.
You will be pleasantly surprised how well twrp works and how easy it is to use.
Good luck!

[Q] Phone's internal memory system messed up after installing ROM

Hi,
I flashed last night Temasek's CM11 4.4.2 ROM (http://forum.xda-developers.com/showthread.php?t=2596887), wiping user data, caches, etc (I was on a rooted stock 4.1.2 ROM).
Everything is working great so far, I love this ROM, I just noticed a problem that it's quite annoying: it seems that the internal user data file system (which would be the /sdcard folder in my old ROM) is all messed up and replicated. Here;s what happens:
I created a backup of the current ROM with Online Nandroid backup. If I use a file explorer from my phone (X-plore) and go to the "partition" /storage/emulated/0 I can see the backup created in /storage/emulated/0/clockworkmod/backup/.
However, if I connect the phone to my PC and browse the contents, the partition that I see isn't that same partition, it's an older one with older files (for example it has a clockworkmod folder but the backup isn't there, and some folders are different). What;s worse is that I can't find this "old" partition when browsing my phone with X-plore. These are the palces where I've looked at:
- /storage/emulated/0 (shows the partition where the backup I just created went, I can see the backup there)
- With root privileges:
- /data/media (shows an older second partition with different folders)
- /data/media/0 (shows the "right" partition, where the backup is)
- /sdcard (again, shows the "right" partition)
- /storage/sdcard0 (same here, shows the "right" one)
So to sum up, it looks like I see at least 3 diffent partitions:
1. From my PC, I see an older one that I can't see from X-plore (I tried Cyanogenmod file explorer too)
2. From my phone, I see the one that has the backup I just created
3. From my phone too, I see a second old partition (different from the one I see from my PC)
So what I would like to know is:
1. How can I transfer the backup to my PC if I can't see the partition that holds it from there?
2. Is it safe to just delete all those folders in both old partitions? I'm sure they're taking space unnecessarily
Any help would be much appreciated!

After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK

Bajanman said:
After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK
Click to expand...
Click to collapse
Thanks for the reply! I'll try this as soon as I get home!

Bajanman said:
After flashing any CM/AOSP Rom. They actually create a different folder set up. That's because of the ability of different users...
You need to apply the restore SD card after downgrade.
Found HERE:
http://forum.xda-developers.com/showthread.php?p=36873319
After that^^^^^^^^^ just make sure you copy everything you want.. Then you can delete all those other folders you don't need.
SENT FROM MY SAMMY i317 USING TAPATALK
Click to expand...
Click to collapse
Hey! So it seems that did it!!! Now I can see ALL the contents in the /sdcard partition (X-plore shows it as /storage/emulated/0)
So my question is (I'm still pretty noob at all this): all the files/folders shown there shouldn't be critical for the OS to work, right? They should all be stuff saved by apps, that if they get deleted the worst thing that will happen is that those apps will lose that info, right? I ask because I can recognize most of them, but not all of them, so I'm not sure, and I would like to remove as much stuff as possible.
One file that makes me doubt specially is /sdcard/clockworkmod/download/download2.clokworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-t0lteatt.img. Is that the actual CWM recovery that I have in my phone? Or just the installation image that can be removed?
Thank you very much for your help!

I ended up deleting everything from the sdcard partition and restoring the stuff that mattered to me, and everything seems fine now. The only weird thing is that when I create a backup with Online Nandroid backup (which gets stored in /sdcard/clockworkmod/backups), I can't see it when connecting my phone to my PC. I can see everything else in the sdcard except the backup. I've tried unplugging and plugin again the phone, rebooting it, rebooting my PC... but nothing. However, if I zip the backup folder with X-plore, leaving the zip file in the same folder as the backup folder, my PC can see it...
Weird thing but oh well!

TWRP Recovery Nightmare Scenario..

I am stuck in a confusing situation I cant get out of and am in serious trouble.
My work Galaxy Tab Pro 8.4 LTE (T325), after more than 2 years of perfect service fell to the ground and broke in a million pieces this morning. I had CM11 on it and had done a TWRP backup just yesterday onto the external MiniSD Card. So, I went to a second hand shop phone shop in the afternoon and found another T325 just like mine in good shape with stock 4.4.2 Samsung TouchWiz ROM.. just white instead of white, but no matter. I immediately rooted it and flashed TWRP.. all good.
I booted into TWRP and first thing I did was to make a backup of the stock ROM to the internal SD Card and also the external MiniSD Card (just to be safe). But after I made the safety backup, when I went into restore, TWRP CANT find it the old backup of my other Tab on the external MiniSD Card. It can only see the new backup I had just made, both on the internal and external memory!
Confused, I booted up the Tab again, and using Root Explorer (with full root access) the first strange thing I noticed was that inside the TWRP folder on the root directory of the internal SD card, its "empty".. but the new backup I just made is actually there.. if I go to the root folders under MNT, there I can see perfectly the very same TWRP folder with the backup sub-folder inside! So why its not showing up when browsing \Emulated\0 TWRP folder? I dont understand this one. Anyway, next I went into my external MiniSD Card, and indeed I have now 2 backups inside the TWRP folder, the old backup from my old Tab that I want to restore and the new backup I had just made, each in their own sub-folder structure as they should be.
So, I rebooted into TWRP recovery and again and I can ONLY see both the new internal and external backups I just made, but NOT the old backup I need to recover from.. it just doesn't show up! Such a mystery has never happened to me before. This is the same Tab, same model, same old TWRP version (2.7.1.0) and using the original external MiniSD Card. Where am I going wrong? I can see the file names inside the new and old backup are different.. is this the problem? Why is the same TWRP version on a new Tab generating different file names than the same TWRP of the old Tab?
To be specific, the new (recoverable) backup folder has the following files:
\TWRP\10d401a5\2014-02-05--07-03-30 KOT49H.T325ZSU1B0B4\
boot.emmc.win
data.ext4.win
system.ext4.win000
system.ext4.win001
recovery.log
The old (not-recoverable) backup folder that I want to restore from, has the following files:
\TWRP\d59ee67a\2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00\
boot.emmc.win
data.ext4.win000
data.ext4.win001
system.ext4.win
recovery.log
Any advice on this is greatly appreciated and I apologize in advance if its me missing something obvious or just being plain stupid!
Thanks again!!!

I suspect the d59ee67a \ 10d401a5 are generated from the tablet serial number, so twrp will only look in the folder for the current serial number match, which is why it won't show the other backup.
I would assume you could copy the file contents from your old backup into the new twrp folder then restore, as long as you are sure the tablets are identical, have the same bootloader and same memory sizes...etc
so basically try to copy the folder "2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00" to TWRP\10d401a5\

otyg said:
I suspect the d59ee67a \ 10d401a5 are generated from the tablet serial number, so twrp will only look in the folder for the current serial number match, which is why it won't show the other backup.
I would assume you could copy the file contents from your old backup into the new twrp folder then restore, as long as you are sure the tablets are identical, have the same bootloader and same memory sizes...etc
so basically try to copy the folder "2014-03-09--08-44-04 cm_mondrianlte-userdebug 4.4.4 KTU84Q b9f00" to TWRP\10d401a5\
Click to expand...
Click to collapse
Wow, yes, thank you very much for the reply! I had no idea that each hardware generates a specific number by which TWRP tags the folder. This is why the backup of the old Tab is not found because its inside the folder with the number of the older hardware. I followed your recommendation and simply moved the old backup into the subfolder of the new backup I had made and instantly TWRP could see it and I made a successful restore!
This is a very import tip to know and I cant thank you enough for sharing it with me! Thanks again