Develop Bugs

[Q] Nandroid backup/Restore -sd ext

Hi !
i have a ROM with A2SD+ on EXT3 partition
1- First i'd like to know if Nandroid Backup make a copy of the EXT3 content .and if so does it restore the EXT3 content as it was ?
2- when i make a Nandroid restore do i have first to make a data,cache, dalvik,sd-ext wipe ?
3- Do i need to flash the ROM before flashing nandroid restore ?
4- if i have changed Radio or partition table does nandroid restore puts everything like at the moment of backup ?
thanks

Hi,
1 yes
2 I do wipe
3 no
4 no

LukenBoy said:
2- when i make a Nandroid restore do i have first to make a data,cache, dalvik,sd-ext wipe ?
Click to expand...
Click to collapse
In fact, it depends. There are few constellations where you don't need to wipe. But, to be on the safe side, just do it. Cause Nandroid restore doesn't restore an image, but files, thus w/o wiping you may end up with unneeded files.
This possibly answers your 4), too.
Greets, Magpie

I got the message like (when backup) sd-ext did not gone with restored files..?
Does anyone knows why..?
Thanks

petar17 said:
I got the message like (when backup) sd-ext did not gone with restored files..?
Click to expand...
Click to collapse
Please post the error message _literally_, cause the one you cited, makes no sense at all. At least for me ...
Greets, Magpie

petar17 said:
I got the message like (when backup) sd-ext did not gone with restored files..?
Does anyone knows why..?
Thanks
Click to expand...
Click to collapse
I think this means, when the nandroid backup is taken, it doesnot include ext backup file. Same thing happend to me.
I did some research on the problem and found a solution which seems to have worked for few people. However I have not tried it myself. I am going to do that though.
Summary of the solution
1.) Download Root Explorer
2.) Enable Root Mode/Mount System
3.) Navigate to /system/
4.) Create a new folder called 'sd'
5.) Ensure you're phone has at least 50% of battery
6.) Reboot and try the backup again.
link: http://android.modaco.com/topic/347662-error-backup-nandroid-ext-with-recovery-22/

[Q] What does a nandroid backup contain?

When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?

kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Click to expand...
Click to collapse
That's a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
As an example, though, I took a nandroid of my stock phone immediately after I rooted it and got S-off. I then played around with various CM7, CM9, and JB ROMs for a weekend, but reloaded the stock nandroid Sunday night before going back to work on Monday. (I need a reliable phone for work.)
My phone was restored to exactly the way it was when I took the nandroid snapshot. I had to re-download a handful of app updates and email that had arrived since the time I took the nandroid to "catch up" to the present time, but that's all.

kirkers said:
When I perform a backup from recovery (or via a front-end such as ROM Manager), what exactly is saved?
Is it like a clone of a hard drive in the PC world?
Does it contain only data, and not the actual ROM?
How should I go about using such a backup when doing a restore? Should a ROM be installed first, followed by the restore? If so, must the ROM match the backup exactly -- that is, must it be the ROM under which the backup was performed in the first place?
Click to expand...
Click to collapse
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Sent from my EVO using Tapatalk 2

Impact of EXT4 partition on nandroid backup + restore?
sully9292 said:
It is everything on your phone at the current time when you made a backup. Including your rom, apps, files, boot animation and e.t.c.
Click to expand...
Click to collapse
MysticCobra said:
[The PC clone image is] a pretty close analogy. Only difference is I don't think it captures partitions...but I'm not sure about that. (It's not clear to me, for instance, if you did a nandroid of a phone with the EXT4 mod implemented and tried to install it on a phone without the EXT4 mod, exactly how that would play out.)
Click to expand...
Click to collapse
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!

kirkers said:
Thanks for the clarifications and the personal experience story. It helps calm my nerves. :fingers-crossed: Now it is clear that the nandroid is a full snapshot, close to being a clone image.
Can anyone address MysticCobra's point about the EXT4 partition?
As a rule, I have followed ROM Manager app's recommendation to partition the sdcard to allow apps to be stored on it. This is what the EXT4 partition is designed to do, as far as I understand such things.
If I format the sdcard with EXT4 (which in my experience wipes out all data on the card), and then restore a nandroid that came from an older EXT4-formatted sdcard of the same size or smaller than the new sdcard, would the nandroid restoration go smoothly?
What would happen if the new sdcard did NOT have an EXT4 partition?
Thanks in advance for further advice.
:good: Cheers!
Click to expand...
Click to collapse
Nandroid backup/restores don't touch the sdcard. They backup to the sdcard but the nandroid only handles /system, /data, /data/data, /cache, boot, and recovery.
The ext4 partition is not the same as the ext4 mod that MysticCobra mentioned. The mod converts /data, and /cache to ext4 and changes the ramdisk to mount them as ext4. The no data limit one also disables the mounting /data/data so the phone will share the apps and app data with a 750MB. Your app data is intact with the no data limit mod but a backup is still advised. No wipe updates don't touch the filesystem in /data or /cache but the mod may need to be flashed again for the ROM to boot correctly as the ramdisk is overridden on all updates. Technically with the normal data one you are good on later cm7 and ICS/JB ROMs as it's already ext4.
If you want to undo the mod the best thing is to wipe /data and /cache and reflash the ROM.
For further reading check the first link in the link below:
http://forum.xda-developers.com/showthread.php?t=1623038

Why cant i restore from backup in CWM ?

Ever since i installed Android 4.2, this whole emulated storage thing is a mess. I have some backups, and i am trying to restore from them in CWM touch. When i go to restore, it always says "cant open directory/cant find files" or something of the sort. I have verfieid that the files are in the 0 storage.
Its frustrating. Does anyone know of a way to restore from a cwm backup ? It would be much appreciated ! I have the latest CWM touch by the way.
Thanks !

Did you update your cwm recovery to one that supports the new 4.2 sdcard layout?
Sent from my Galaxy Nexus using Tapatalk 2

Search is your friend
saadkhan07 said:
Ever since i installed Android 4.2, this whole emulated storage thing is a mess. I have some backups, and i am trying to restore from them in CWM touch. When i go to restore, it always says "cant open directory/cant find files" or something of the sort. I have verfieid that the files are in the 0 storage.
Its frustrating. Does anyone know of a way to restore from a cwm backup ? It would be much appreciated ! I have the latest CWM touch by the way.
Thanks !
Click to expand...
Click to collapse
This is a problem with flashing 4.2. TWRP has a fix for the issue you are talking about, but right now the fix for you can be found in this post, or others like it. This is how I fixed my problem!
http://forum.xda-developers.com/showthread.php?t=1762846&page=256
ual4720 said:
I flashed this build and later tried to go back and do a restore on my CWM backup. When I attempted the restore it couldn't find any backups! I found the problem to be that it moves the sdcard contents to /data/media/0 then mounts /sdcard/ to /data/media/0. Clockwork mounts the folder /data/media and is searching for the backups in that directory. It fails to find it because it is not there. To fix this I made a backup of my sdcard by doing an adb pull then moved the clockwork folder in the /data/media/0 to /data/media/. so the commands that I executed are as follows:
adb shell <enter>
su <enter>
cp /data/media/0/clockworkmod /data/media/clockworkmod <enter> (you could also replace the cp command with mv. This will keep from creating a duplicate of your backups - suggested by tiny4579)
reboot recovery <enter>
go through the process of restoring a clockworkmod recovery and when it is finished reboot into your restored backup. If you explore the sdcard with root explorer or adb you will notice the 0 folder inside your sdcard.
I suggest you dont try this if you are unfamiliar with the command line. Has anyone else experienced this issue and have a better fix?
Click to expand...
Click to collapse

ual4720 said:
This is a problem with flashing 4.2. TWRP has a fix for the issue you are talking about, but right now the fix for you can be found in this post, or others like it. This is how I fixed my problem!
http://forum.xda-developers.com/showthread.php?t=1762846&page=256
Click to expand...
Click to collapse
BUT if TWRP is installed....can i restore from a CWM backup ???

saadkhan07 said:
BUT if TWRP is installed....can i restore from a CWM backup ???
Click to expand...
Click to collapse
No
Sent from my Galaxy Nexus using Tapatalk 2

If there is way to point CWM to the proper directory, is there a way ? Can i restore via ADB ?
I have all the CWM files to restore from, just cant due to the location of the files i guess. Does CWM default to the 0 ?

re
saadkhan07 said:
If there is way to point CWM to the proper directory, is there a way ? Can i restore via ADB ?
I have all the CWM files to restore from, just cant due to the location of the files i guess. Does CWM default to the 0 ?
Click to expand...
Click to collapse
I actually ended up resetting the whole device, and actually was able to restore by using the MD5 mismatch fix. I have reinstalled CWM and everything.

i am currently running cm10.0.0 and completely satisfied with it. just for curiosity reasons i would love to flash 4.2 to see how it feels. my problem now is, can i simply return to cm (4.1) by reflashing my cwm backup?
as with 4.2 the file-system was changed (sdcard0), is that pretty easy with cwm recovery, or do i have to invest an hour of work with adb pulls and pushes?
thanks for your experiences!

saadkhan07 said:
I actually ended up resetting the whole device, and actually was able to restore by using the MD5 mismatch fix. I have reinstalled CWM and everything.
Click to expand...
Click to collapse
Same with me... :/ it was annoying... Just because of that new sdcard layout on 4.2

If I TWRP backup everything except System will a Restore work later on?

I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...

lit_lee said:
I dont know what I did but I know it was my fault.
Whenever I try to create a full backup of all partitions I get "createTarFork() process ended with ERROR=255"
But when I exclude the System partition it works fine.
So if I restore everything else later on will everything work fine? I'm not exactly sure whats getting left out in the partition.
Btw, my bootloader is unlocked, I'm currently on FreedomOS 2.1, I have Magisk, Xposed, all the good stuff...
ALSO! I did an ADB backup on my computer with "adb backup -apk -shared -all -system -f"
I'd be fine with the ADB backup but "backup.ab is only 1.5 GB and my nandroid backups are usually around 11GB...
Click to expand...
Click to collapse
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.

Airwolf79 said:
Team Win recommends using the system image backup instead of just system for dm-verity devices, but I still get the same problem as you when trying to perform a backup. What you could try is clean flashing the ROM and then just restore data from ur backup. That should work.
Click to expand...
Click to collapse
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.

lit_lee said:
Yeah I read in other places a fresh flash would work but I wanted to weight my options.
How does one go about doing the image backup? That sounds a lot better.
Click to expand...
Click to collapse
When you select backup in TWRP, it's one of the available boxes to check. Uncheck system, check system image. This hasn't solved my problem of backups not completing though. I always remove my fingerprints and pin before a backup, and I've been able to complete backups before, but usually the problem lies in encrypting the backup itself. However, I've still had backups hang at 95% even without encryption. Maybe someone else can shed some light on to why this is happening.

the createTarFork() process ended with ERROR=255 is not from system its from data and issues with parallel apps on ur OP5T
download Android Terminal and type
Code:
su
pm remove-user 999
then u can backup with twrp, never tried to do a restore yet though

Is my encrypted data lost forever after the Android update?

Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my android version and test the latest features. I downloaded xiaomi firmware and A13 ROM, flashed them, made a full wipe and... here is where my problems started. Please don't school me here - I'm pretty sure that I messed up, I'm just looking for possible solutions.
What happened?
My phone had an encrypted data partition and as I read later, it was pretty normal that A12 installation messed it. The recovery (regardless of the version) has stopped prompting me to give the encryption password, instead it was mounting the internal drive encrypted. I tried to downgrade android version to 10 (both LOS and MIUI), but I had bootloop bringing me back to recovery. I tried decrypting it via ADB, but it didn't work. Since I need my phone, I made a backup of the whole internal storage with ADB and I have it in .img form on my hard drive. Since I've never encountered any problems like this, I wasn't prepared for losing all of my data, especially pictures and Signal archive, so I'm wondering - what can I do to try to get my data back, giving I have the full memory dump and I know the password used for en/decrypting it?
Thanks in advance, I spent hours looking for an answer, but I don't feel like getting close to the solution.

reip said:
Hello,
this is somewhat similar to this thread, but there are no answers and I have a bit of a different problem at the moment.
I've been using official LOS 17.1 for some time on my Note 8T, but it started to get slow, so I decided to upgrade my
Click to expand...
Click to collapse
Encryption is effective if you protect your phone with a password or schema etc on the lock screen.
You cannot restore data from an AOSP rom to a MIUI rom and vice versa.
The backup will only work with the same rom as the backup.

So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?

reip said:
So if i have a filesystem that was encrypted on lineage os 17.1, i should make a clean install of it and then try to push the whole .img backup through adb?
Click to expand...
Click to collapse
Same rom, same password, not 100% guaranteed that it works.

reip said:
.
Click to expand...
Click to collapse
Since you have a backup try flashing DFE
let me know if it work

loopypalm said:
Since you have a backup try flashing DFE
let me know if it work
Click to expand...
Click to collapse
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?

reip said:
the problem is i pulled the whole mmcblk0 dump with adb, which gives me more than twenty partitions in the .img file (I can easily say which one is the /sdcard one because of the size) and I am not sure if pushing the whole image with incorrect rom won't bring me to the exact state i was in before. Is there a way to push a particular partition from a .img file or should i try to push everything and flash dfe, as you're saying?
Click to expand...
Click to collapse
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray

loopypalm said:
if the partitions inside are .IMG file you can restore with orangefox
pick the img and set the target to restore
restore just data 1st then DFE then wipe cache+dalvik then reboot and pray
Click to expand...
Click to collapse
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?

reip said:
This sounds like a plan, but to which partition should I flash it? I don't see 'data' option there.
+ just to make sure, do I have to reflash and set up the exact rom and password I was on when I had the encryption working before I start the operation you're suggesting?
Click to expand...
Click to collapse
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)

loopypalm said:
aah, i forgot it don't have data as target
but there must be a way using ADB
-if you are going to restore the whole backup = no need to recreate the same conditions you did before
-if you are going to restore just the userdata backup = recreate the same conditions
in both cases format DATA is important (format nt wipe then reboot to recovery)
Click to expand...
Click to collapse
so format data, restore, flash DFE, reboot?

reip said:
so format data, restore, flash DFE, reboot?
Click to expand...
Click to collapse
yes