Database Develop

How to do a complete backup? (lost apps on the internal SD)

So I had my phone working and decided to try a kernel found here.
I went on, flashed the kernel through cwm, and nothing worked (stuck at loading screen with continous reboots).
So I flashed my recovery image, rebooting stopped by stuck it was at the loading screen anyhow.
So, since I could not come out of it, I downloaded a stock rom (I was running stock by the way), flashed it (with smartflash), rooted it (superoneclick), installed cwm (now v5) and I'm back on.
So I flashed the recovery, and most of the data is back but I lost all the apps on the SD card.
The SD card is the same from which I flashed the recovery image through CWM, and all my music is still there.
So might it be possible that the apps are still there too?
What can I do?
Why all the SD apps disappeared?
Edit: ok maybe we're talking about internal SD card... may it be the CWM v5 doing recovery from a v4 zip?

had this problem very, very, often...
nobody really could help me, but i know, its because of problems with the android_secure folder.
so i´m not an expert and i really don´t know what s the reason, but i tried some things and sometimes it helped...
it can appear if something goes wrong when you install an app or move an app from phone to sdcard, or when you want to restore them with titanium or cwm.
the possibiltythat it happens increases when you do both at the same time or, move many apps at the same time p.e. with gemini or install many apps at the same time (p.e. with panda pc suite).
or if something goes wrong with a market update.
mostly, it starts that you can´t install apps anymore. after reboot all apps on sd are away.
with luck you can repair it and get the apps back.
-delete the market cache.
-delete file smdl2tmp1.asec in android_secure folder on sd card or in mnt/... secure.. damn forgot the path of the second folder where this file can be. gotta google for it.
-or create a new android_secure-folder. unmount sdcard. rename android_secure folder to something different, so that there´s no more an android_secure folder. put sdcard back in the phone, reboot the phone. there will be a new empty android_secure folder. shut phone down, put sdcard into pc again, copy all files from renamed folder to the new android_sd folder, put card back into the phone, restart it and wait. with luck, your apps are back again.
don´t now, maybe it helps when you delete dalvik cache and cache before restart. sometimes it worked, sometimes not.
in your case, your apps are away after restore and not because of install/move2sd issues... so in this case its important to completely delete android_secure folder before restore. make a fullwipe. and after fullwipe i would restart phone once, so that a new clean android_secure folder could be created. hope something helps.
edit:
i did a little trick, that my external sd is mounted as sdcard in my phone. so normally the internal sd card is the "sdcard" in the phone. so, cos you can´t put your internal sd into the pc, you gotta mount it with usb connection.

Thanks but I'm afraid in this case the content really got deleted after I reflashed the rom...
IS there a way to really save everything via cwm?
Or should I use another software?
Also if flashing baseband: what will get deleted?

Flashing baseband will wipe /data

Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
And how does /data relate to my problem?
Is /data backed up by cwm or not?
What is not backupped by cwm and how to backup it?

Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
but you can restore it with nandroid, right? it's going to be just as before?

punyategar said:
but you can restore it with nandroid, right? it's going to be just as before?
Click to expand...
Click to collapse
If you mean baseband then the answer is no. It restores your ROM and all the apps including their data.

punyategar said:
but you can restore it with nandroid, right? it's going to be just as before?
Click to expand...
Click to collapse
Assuming you remembered to back it up yeah.
My radio flash procedure is:
NANDroid backup
Smartflash radio
NANDroid restore
Push new RIL
Use phone

Rusty! said:
Flashing baseband will wipe /data
Click to expand...
Click to collapse
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.

You may not think so, but it does.

kitty's_daddy said:
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.
Click to expand...
Click to collapse
Definitely wipe /data
Both Rusty! And myself always test new basebands and it definitely wipe /data.
Edit: sorry I'm referring to smartflash.

temasek said:
Definitely wipe /data
Both Rusty! And myself always test new basebands and it definitely wipe /data.
Click to expand...
Click to collapse
I think you would be correct.
It's only my opinion.

i use kdz tool, no user data will lost, only system(happened on me 2 times). don't use smartflash it will wipe all data

kitty's_daddy said:
I don't think so.
Kdz tool and official updater didn't wipe data. (Aren't you ?)
They did change only baseband and systems.
But you have to nandroid backup to avoid bricked.
Click to expand...
Click to collapse
dont know about kdz, official updater didn't touch my /data at all. i mean, my apps were just as before, the settings...

just use titanium backup and make sure the save location is in the sd card
For certain apps that have their own way of saving data, it might not always work.

I just can't find the correct answer in the posts I've read so far.
If I flash a kernel that doesn't work, and then I restore a CWM backup, why it wouldn't boot again?
If I reflash the stock rom and then restore a previous CWM backup, why something won't be there?
What exactly should I do in CMW to obatin a complete backup?
Or should I use something else?

Custom recovery lost?

Hey guys so i backed up my v20b stock software via cwm and thought that it was going to be stored in some kind of internal storage forever (like cwm itself), but now i realised that after i done factory reset it is probably gone ) Is there a way to create a recovery file for cwm to restore to v20b?Or could i use some elses file?

Your backup is in the internal memory, unless you format or wipe it specifically factory reset will not erase it.
In development section there are a few roms based on official v20b ou can flash thhose if you can't find your backup

Rudjgaard said:
Your backup is in the internal memory, unless you format or wipe it specifically factory reset will not erase it.
In development section there are a few roms based on official v20b ou can flash thhose if you can't find your backup
Click to expand...
Click to collapse
i had 2 backups on stock and i didn't delete any of them, just did the factory reset once. When i go to recovery mode CWM doesn't find any backups on internal storage...So where did they go?

Mount usb storage from recovery and check the cwm folder they should be in there unless you did "wipe data"

did you install any 4.2.2+ rom? if you did, your cwm is reading the "wrong" folder for backups. it's reading under data/media/0/whatevercwmbackupfolderis, instead of data/media/whatevercwmbackupfolderis

Go into custom recovery and select "Restore Back-up". It will work. I had the same problem .

Yeah, i also did wipe data/cache/dalvik/(as you do) before installing 4.4.2 , no backups in data/media/cwm, so i guess my backups are gone?

No, wipe data doesn't wipe internal storage, if formats everything except data/media which is where backups are
You must specifically select "format internal storage" to loose your backups
Is other stuff you had on internal sd still present?

they have to be there, unless you formatted internal sd. try searching around more with file browsers, sorry i cant be of more help

Rudjgaard said:
No, wipe data doesn't wipe internal storage, if formats everything except data/media which is where backups are
You must specifically select "format internal storage" to loose your backups
Is other stuff you had on internal sd still present?
Click to expand...
Click to collapse
no, but i do factory reset every time. Rom manager doesn't find anything, as well as cwm in recovery mode. Searched every CWM,DATA,BACKUP folder, nothing there.
i searched with ES file explorer with root access (i even created a new backup to be 100% sure root access is on, the new backup appeared in data/media). Btw, how much internal storage is there after factory reset? Because with Beanstalk i get 11,8 of 12,2, i was sure those 400mb where my software backups....

TWRP error "E:Unable to mount '/data'"

I have a new LG Optimus L90 (D415) with stock 4.4 ROM, and TWRP 2.8.0.0 (and previously, Philz 6.58.7) for recovery. Obviously, the phone is rooted and now has an unlocked bootloader....
My problem is that neither recovery will back up (or even mount) "/data". Note that I put that in quotes because, without having "/storage/sdcard" or something in front of it, I presume that it's an internal folder and not something to do with the external SDcard.
My first guess would be a problem with encryption, because both the phone and the external SD are using it -- and I never get asked for the password. Either way, the actual error in TWRP says "E: Unable to mount 'data'", while Philz says it can't access /data/philz-touch for the .ini file.
I've made several Google expeditions to find the answer, and have come up empty-handed with all of them. I've seen all kinds of fixes, from claims that I have to run chkdsk against the SDcard, to backing up the entire /data partition with a tar file and reformatting it with command line nightmares.
I'll do what I have to in order to fix this, but I'd rather not embark on an experimental goose chase. Any ideas?

I have this same problem. But only for wiping and flashing.
I have no idea for fix if backup also not working !! (Noob)
1.TWRP click backup. Select all except SDcard.
Finish backup.
2.go to Wipe menu.>advanced wipe>select all except System and Sdcard.
Wipe.
(It will skip the error files)
3.Install menu. Select ROM to flash.
Was what I did.

fear2433 said:
I have this same problem. But only for wiping and flashing.
Click to expand...
Click to collapse
I'm not flashing anything, yet. First I need to make a backup of the entire phone (not including the SDcard). That way, if something goes wrong, I can just restore my old, working configuration -- all at once -- and start over.
I can back up and restore apps individually, using Titanium Backup. But what I need here is a Nandroid-type backup... and that generally has to be done from the recovery partition. There is one other way to backup everything, using a laptop/PC and ADB. But I've never tried it, and it wouldn't protect against a ROM meltdown.

Solved, somewhat...
So I did some further experimentation concerning this error. I did a test run to install CyanogenMod, and I found that I couldn't even factory reset certain partitions because of these "Unable to mount /data/" type errors.
What was ultimately the problem? The encryption. Once I decrypted everything, TWRP was able to see, mount, and backup, those partitions.
But I was under the impression that TWRP handles encryption, e.g. asking for the password, or some such. I mean, how can you do a Nandroid-type backup on a phone, if no recovery can mount those kinds of partitions?
So, for the record: "E:Unable to mount" was definitely due to the encryption being turned on for my internal storage. Thus the solution (so far) is to decrypt storage. A wretched solution, but at least it works for the time being.
BTW, In furtherance of this research, I formatted my internal SDcard to NTFS, just to make sure it wasn't misaligned or whatever when it was just FAT32. And I discovered that NTFS takes forever to format (32GB on the order of a couple hours)., FWIW.

The plot thickens. It may not be sufficient just to undo encryption, there may be something wrong with the way that partition was created, or otherwise is constructed.
Even though I now am able to mount /data, I'm not able to format it.... in TWRP it says something like "unknown filesystem 'auto'".
But there is a thread here that describes using Philz recovery to unmount and then format this mess, and I'm about to try it, I just have to flash Philz in place of TWRP. Now let's hope this version works without issues, because I'd have little recourse if things go bad there.

Can't mount /system in twrp 2.8.3.0

I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!

modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.

They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents

Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.

alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161

Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.

Many errors when wiping cache partition in TWRP

Hello,
As stated in the titled I have tried to root my OP 3T and it horribly wrong. First I got the error message telling me it couldn't mount my /system partition. I googled how to fix it and discovered that I had to wipe the partition as it might be corrupt. Just to be sure that it was indeed corrupt. The size was stated as 2913MB but the used space was stated as 1728265MB. I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...The only thing i can boot into was fastboot and recovery. I then tried to install the LineageOS and it worked. I can finally boot to a OS. However when going in the recovery again and wiping the cache I get a slew of errors. Almost all of them are "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)". There is also one other error: "Unable to mount storage"
How do I fix this?

uptivuptiz said:
First I got the error message telling me it couldn't mount my /system partition.
I therefor wiped it and tried to boot. Now I couldn't boot into Oxygen OS...
Click to expand...
Click to collapse
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.

redpoint73 said:
System partition is the OS. So from that fact, it should now be obvious that wiping system (and therefore wiping the OS) will result in not being able to boot to OS.
Not being able to mount system is a little odd. What version TWRP? Current version is typically recommended (currently 3.2.3-1).
You can try in TWRP Wipe section, the "Format data" button. This will often fix corruption issues with data partition (format is not the same as wipe), although I'm not sure how the system partition was affected.
Click to expand...
Click to collapse
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.

uptivuptiz said:
I'm using TWRP 3.2.3-1. I tried to format with the "Format data". It seems that I still can't install the OxygenOS. Also the error "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" still accurs.
I'm still able to install and run LineageOS.
Click to expand...
Click to collapse
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).

Dirk said:
Formatting with 3.2.3-1 will remove the encryption footer. It's basically the only build of TWRP you DO NOT want to use! 3.2.3-10 is the latest but that won't reinstate your encryption footer. My advice is this. Flash TWRP 3.2.3-0, format at least /system, /data and /cache from the Wipe/Advanced screen and then Wipe everything for good measure.
Make sure you are in front of your PC when you do this. Back up everything to PC first as formatting will delete everything from Internal Storage. Make sure you have all your Install zips ready to go on your PC. Whn you're done formatting and wiping you can copy the install zips back to Internal Storage and flash OOS full Zip (or Custom ROM).
Click to expand...
Click to collapse
Thanks! I will try that when i get time tomorrow. There will come an update.

uptivuptiz said:
Thanks! I will try that when i get time tomorrow. There will come an update.
Click to expand...
Click to collapse
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.

Dirk said:
Let me know.
Remember to reboot Recovery once you have 3.2.3-0 installed so that your format operations are carried out with that version.
Click to expand...
Click to collapse
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again

uptivuptiz said:
I have now downgraded TWRP to version 3.2.3-0 and wiped everything. I didn't backup as I don't have anything on there because it's not my main device. After wiping I tried installing OOS again and this time I get the same "Error opening: '/data/local/nhsystem/kali-armhf/dev/xxxx' (Not a directory)" error and now it cant mount the /system partiton again
Click to expand...
Click to collapse
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)

Dirk said:
You're not just wiping, You're formatting. Select each of the partitions (Cache/Data/System) and format in each case. (I recommend EXT4 for Data)
Click to expand...
Click to collapse
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...

uptivuptiz said:
Ok. I tried to format all the partitions with EXT4 and tried to install OOS again with a adb sideload. This didn't work and I got an error "adb sideload cannot read 'OnePlus3TOxygen.zip'". So I tried installing it with a OTG adapter and a USB inside TWRP and it worked. OOS is running and working! Thanks for the help
Now I'm just curios as to why I can't sideload...
Click to expand...
Click to collapse
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.

Dirk said:
A few possibilities:
1) OnePlus3TOxygen.zip of course isn't the name of the file as downloaded, so i assume you renamed it to something more sensible before trying to sideload? Do you have 'Hide Extensions of known filetypes' selected in Windows Explorer? Could it be that what you ended up with was 'OnePlus3TOxygen.zip.zip', which of course wouldn't work if you were trying to sideload 'OnePlus3TOxygen.zip'?
2) You didn't move your download to your platform-tools folder in adb?
3) You didn't open a CMD window in your platform-tools folder?
Anyway, good that you're back on your feet.
Click to expand...
Click to collapse
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.

uptivuptiz said:
Here's what I did:
Moved the zip file to the platform-tools folder.
Kept the stock name of the zip file.
opened CMD window in platform-tools folder.
I still get the error.
Click to expand...
Click to collapse
You wouldn't be the first. It's a common issue. You know you can just move the zip to Internal Storage and flash it with TWRP? The Recovery is MTP enabled. Useful to know for future reference. :good: