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?

do cwm backups keep the file system?

If I have to switch file systems but I don't wanna lose data will recovering backups restore the filesystem of the backup too?

-sandro- said:
If I have to switch file systems but I don't wanna lose data will recovering backups restore the filesystem of the backup too?
Click to expand...
Click to collapse
In theory the latest CWM (5.0.2.0 as of this moment) should be able to restore the filesystem as well as the data. In practice however this doesn't work yet. (At least not for me if trying to restore an ext3-backup on an ext4-phone.)
That's not really a concern though, because you can revert from ext4 to ext3 by running/installing "r1_backtoext3-2x-unsigned.zip" (search for it) before restoring the backup, or install another .zip which will convert ext3 to ext4 without data-loss if going the other way. (Cannot remember the filename right now, never used it myself.) I think Rusty packaged that one.

CMW can backup the whole rom /system included. I always change into CM7 and the Leaked GB via the backup/restore.

[Q] CWM error

I get this error while backing up using CWM
Error: Ext sd cannot be backed up, your device may not support backup of Ext sd!!!
And when restoring i get
Error: Ext sd cannot be found.
Why does these errors occur?

At a guess you are on an ics ROM?
Why do you want to bloat a nandroid with a back up of an external sd?, just copy contents to pc if you want to format it
Sent from the depths of despair

slaphead20 said:
At a guess you are on an ics ROM?
Why do you want to bloat a nandroid with a back up of an external sd?, just copy contents to pc if you want to format it
Sent from the depths of despair
Click to expand...
Click to collapse
came back to stock GB Rom. Some apps were FCing so decided to reset.
Missing Ext_Sd didn't cause any trouble.
All went well now need to check if those app work or or not.
But one question:
I have a really nice backup with all the installed apps and there data but couldn't restore it correctly as i forgot the kernel that i flashed with CWM using odin.
The backup file looks like a CWM 2 & i remember it was green CWM, but when i use any other kernel with CWM 2 other than the one used to back it up the files isn't restored properly. But i restored it once properly but forgot to see which kernel it was.
Is there any way to find out the kernel & CWM and restore it back properly?
How to find the real CWM used to backup those file?

[Q][SOLVED] Bricked with EMMC bug I think - Anyone have .pit file

Hello
I'm pretty sure that my /data partition was corrupted. Not sure how, maybe using a custom recovery with the ICS kernel, maybe some other way, but it can't be formatted, copied to etc.
I've been reading on some other devices about editing the .pit file after finding out where the corruption is. I'm having trouble using LInux tools since using adb, I don't get the root command prompt, just a $.
Anyone have experience on a P7300 about how to work around the corruption, identify, perhaps run a fsck on the partition?
I'd also be willing to pay a $50 reward for anyone who can get it running again, even with a reduced size data partition, but ideally I'd like to try repairing the damaged partition first.
Thanks
Harry

check "Guide & ToolKit" thread
http://forum.xda-developers.com/showthread.php?t=1406137

SOLVED
Discovered after reading the Toolkit and guide that it wasn't an EMMC bug hard brick, thank goodness. I was directed in post #250 to one specific stock ROM to install with ODIN, that supposedly, was the only stock ROM that when you did a wipe data/factory reset, actually recreated the partitions and reformatted them. It is P7310XARLA3_P7310UELA3_HOME.tar.md5
But I had nothing to lose, so I installed the stock ROM with ODIN, booted the stock recovery, did the wipe, and for the first time in about 10 hours of trying this, it was able to format the /data partition, and installed the bootable ROM. After that, I installed a CWM recover in the tar format, and now about to put my old ICS ROM back on, the one in the development section that came from an OTA leak.
Thanks, I hope this helps someone who has problems accessing their /data or /sdcard directories..

Lost my efs backup.. can I use another one?

So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?

(°_o) said:
So basically I dont have my efs backup..
and twrp messed up my efs partition..
Is it possible to use another efs?
Click to expand...
Click to collapse
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue

MYEUHD said:
I have had a similar problem recently: I corrupted my EFS partition
and I didn't have a buckup but I kind of solved the issue
I advice you to do a TWRP backup including only the /data partition as the screenshot below shows
Then you should install a stock rom ( then flash cf-auto root through Odin), reinstall your daily rom and before letting it boot for the first time, make sure to restore the /data backup you made earlier
Hopefully this should fix your issue
Click to expand...
Click to collapse
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.

(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)

MYEUHD said:
According to @xc-racer99 , When you install a custom ROM for the first time, it actually copies the EFS partition and leaves the original untouched. This way, when you go back to stock and then re-install a custom ROM it, takes a copy again from the original
I downloaded Gingerbread 2.3.6 for XXJVT from this thread: https://forum.xda-developers.com/showthread.php?t=1102881
(replace XXJVT with your baseband version which can be found under settings>about phone in your current rom)
when I have corrupted my EFS partiton, I flashed the stock rom and then it solved half the issue
My phone generated a generic IMEI adress and it's functioning as well as it did in the past
There's only one problem : each time I boot, I get the following message "A problem was detected with your device. Your device IMEI number is invalid. An invalid IMEI number could cause network issues including the inability to call emergency numbers." yet everything works fine as I said earlier
So here's my current EFS backup, I made it through TWRP
You have to uncompress it and copy it to the folder where your TWRP backups are kept
that is /sdcard/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your internal storage
and /external_sd/TWRP/BACKUPS/'RandomNumbersandLetters' in case your backups are in your external MicroSd card
Finally, Restore it! (through TWRP of course)
Click to expand...
Click to collapse
(°_o) said:
Does the stock rom have efs? Afaik.. efs is device specific?
I can just flash the efs if theres one on the stock rom.
Which stock rom did you download.
Click to expand...
Click to collapse
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...

xc-racer99 said:
Nope, a stock ROM won't have it - it's device specific and holds the IMEI. If you've corrupted the original (BML) partition then you're probably out of luck. I'm not sure what would happen if you used somebody elses. It might work, it might not. Can only try If you're on an MTD ROM (4.0+), then you should revert to stock and things should be fixed, assuming the original partition is still intact...
Click to expand...
Click to collapse
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..

(°_o) said:
His TWRP backup is just the normal one that the device creates.. so it has the generic IMEI..
But I'm kind of lazy so instead of flashing it through TWRP.. i pushed it via adb and flashed with flash_image..
And it said some bad blocks error.. which means mtd efs partition needs to be flashed with bml_over_mtd... probably the reason why i lost my imei in the first place..
do you know any way of getting the bml parition from mtd? perhaps some offset where i can directly raw read it..
Click to expand...
Click to collapse
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...

xc-racer99 said:
Well, according to the updater.sh it reads it from a mounted partition at https://github.com/xc-racer99/android_device_samsung_aries-common/blob/aosp-7.1/updater.sh#L198. The actual BML partition is at the offset specified in https://github.com/xc-racer99/andro...aosp-7.1/drivers/mtd/onenand/samsung_gsm.h#L9 - if you can dump it, mount it as vfat on your computer and then move the files over. Be very careful as the bootloaders are also around this offset...
Click to expand...
Click to collapse
The mtd doesnt interface the whole NAND storage.. so i'm gonna have to rebuild the kernel exposing the original efs partition..
Let's see how it goes.

@xc-racer99
I dumped the 10mb parition but it wasnt mountable by any means..
Then I hex viewed it and it showed.. FSR_STL in beginning..
Which lead me to, https://github.com/Benjamin-Dobell/Samsung-Read-Only-FSR/blob/master/Inc/FSR_STL.h
So unless I check out the STL implementation or use one that is I guess I have to go back to stock :\
I cannot get any valid data from the dump.
I've attached the dump of it, if youre intrested.