Does the System Image(Backup) include Boot partition files? - General Questions and Answers

I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance

Tanmay_B said:
I am a newbie!
So I wanted to start flashing custom ROMS on my device...
So I flashed the Custom Recovery(TWRP) and downloaded compatible Custom ROM...
Ok so by following some blogs and videos I took the system backup of boot, system.
And yes I am able to restore it...
I also read about Android Partitions(https://forum.xda-developers.com/general/general/android-partitions-explained-t3657183)
But when taking the Backup I saw a System Image partition there.
So I am wondering what is its use and should I backup that for pure Stock ROM Backup?
And also does it include the boot partition files or I also need to backup the boot partition with it?
And if I create this file using which option can I install this type of Backup?
Thanks in Advance
Click to expand...
Click to collapse
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank You Bro So Much for explaining this:laugh:
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...

Tanmay_B said:
Thank You Bro So Much for explaining this[emoji23]
Ok So I can keep the backup of the system image if I want a complete stock rom backup, right?
But what about the other partitions like Recovery, IMEI, FRP, Pinfo, Logo?
I mean to say if I clear all these partitions for eg IMEI, will my device's IMEI number be deleted?
Or after flashing the system img these partitons will be regenerated?
And yes I am using the default TWRP backup and I am able to restore my android backup...
Click to expand...
Click to collapse
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk

Droidriven said:
It isnt complicated, just boot into TWRP, then choose the "Backup" option, the default partitions that TWRP automatically selects to backup are all you "need" to backup. TWRP backs up the boot partition, recovery partition and system partition by default, that is all you need.
To restore the backup, just boot into TWRP then select the "Restore" option, then restore the backup file.
The "system.img" backup creates a backup of the complete system.img, it is effectively the same thing as using adb shell to dump the system.img to obtain a copy, it contains everything involved with the system partition, including boot.img and kernel(zimage). This system.img backup can restored by using fastboot flash system command, adb shell with dd command, terminal emulator with dd command or by using the option in TWRP that allows flashing .img files.
Another option for devices that are rooted is to use apps like Flashify to flash the system.img, but these apps are risky and don't always flash correctly.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Droidriven said:
The default TWRP backup is all you really need. It will completely backup everything you need to backup/restore your ROM, the system.img backup isn't necessary. It is no different than the system.img that can be extracted from your stock firmware file.
As for IMEI, the method of backing up and restoring IMEI doesn't involve TWRP, there are other tools for that. Do a Google search for:
"How to backup and restore IMEI"
I suggest that you don't mess with any of the other partitions
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
OK Thanks Bro...

Related

Restoring data from backups

I have searched the forums and I cant find out the answer.
I have several nandroid backups on my sdcard. Is there a way to restore my messages from the backups onto my phone?
Everytime I load another build I lose all my txts.
Please help.
Pretty sure it's stored in your /data partition along with your phones settings\apps.
fastboot flash userdata userdata.img
will that erase my current data?
d00m said:
Pretty sure it's stored in your /data partition along with your phones settings\apps.
fastboot flash userdata userdata.img
Click to expand...
Click to collapse
fastboot flash userdata data.img
when u flash data it restored whatever data u had when u made the nandroid backup....
i dont think it keeps what is on the phone after nandroid...
since nandroid backup is a complete byte by byte copy of your phone's internal flash chip, you've backed up all the data that could survive a reboot (apps, settings, etc.), so restoring it will overwrite everything you did after that point. If you used another system build and that build requires a wipe (i.e. formating /data) to run, restoring the old userdata will probably render the new system unbootable (if that's a word).
The safest way is restore the whole system (boot, system and userdata) with fastboot and backup your messages using another tool.
If you don't want to restore, you can try mounting that data.img with the android emulator in the SDK.
It's better to use applications like smsbackup or mybackup to do such a thing..
its too late now for me to use another program. but if i load it into the emulator can i back up from there? I've never used the emulator before so I don't know what all it is capable of doing.

flash rom failed openrecovery V3 optimized with miui

(sdcard/nandroid/openrecovery)
recovery boot
nandroid -restore- xtmiuioptimized-restore all
boot not backed up
bpsw not backed up
lbl not backed up
logo not backed up
devtree not backed up
system not backed up
data not backed up
cache not backed up
cust not backed up
cdrom not backed up
ext2 not backed up
restoring finished successfully
done
Why does this happen ... thanks
I'm using V2froyoXToptimized update v2 v3 update
sorry translation
did you unrar the file and then place it in sdcard/nandroid/openrecovery or just place the rar. you must first unrar khals rom down to just the folder with boot.img boot.md5 system.img and system.md5 in it then place the folder with those in the sdcard/nandroid/openrecovery folder
the procedure that you're saying I have performed and the result is that in post....
so inside the Xtmiuioptimized folder there is 4 items? boot.img boot.md5 system.img and system.md5? and in open recovery when you select xtmiuioptimized in the restore menu it should say only boot and system in the restore options.
yes..the files are 4
restore option for xtmiuioptimized
go back
restore all
restore selected
The directory structure on the sdcard should be...
Code:
/sdcard
/nandroid
/openrecovery
/xtmiuioptimized
boot.img
boot.md5
system.img
system.md5
if your folders match these I would try coping them from your pc again.
Çheck restore all and if that doesn't work your file might be corrupt so try tranfering the folder again.
is the path and just... 3rdstring...Thank you
easye420.. I had already tried I'll try again tomorrow...Thank you
did you try checking the boxs next to system and boot in the partitions sections of the restore menu in open recovery. try that and if that doesnt work and you say you already tried replacing the folder and that didnt work id say your download must have been corrupt id try to redownload it and try again. this happened to me before and if that doesnt work try try making a back up of your current phone and restoring that back up and see if that works. and if that doesnt work try reistalling Open recovery thru the system recovery app and try again. lot of trial and error unless anyone else has better ideas
The ROMs we're flashing only update boot and system. When nandroid restore says "not backed up" it just means it's skipping restore of a partition because there isn't a backup to restore. It's harmless.
Mioze7Ae said:
The ROMs we're flashing only update boot and system. When nandroid restore says "not backed up" it just means it's skipping restore of a partition because there isn't a backup to restore. It's harmless.
Click to expand...
Click to collapse
if you reed his first post its says all partitions are not back up boot and system included. so its like theres nothing in the folder to restore like restoring a empty folder.
exact is just so happens to me
solved
extract rar folder then take the (sub xtmiuioptimized folder) and put the SD card installed .... ok .......sorry

Nandroid backup..

I did a nandroid backup bit it said fatal error while backing up bpws...or something like that...(one more thing...will nandroid backup...backup my apps if I lost them??)
Sent from my XT720 using XDA App
vari9 said:
I did a nandroid backup bit it said fatal error while backing up bpws...or something like that...(one more thing...will nandroid backup...backup my apps if I lost them??)
Click to expand...
Click to collapse
For some reason we can't back up all the partitions in nandroid. It should be enough to backup system and data. Optional: boot, logo (if you modified M boot logo), cache (usually not necessary), sd data (if you use ext partition on SD card).
With nandroid of system and data (and the others, but only if you use them) you should expect to be able to go back to exactly how your phone was at the time you made the backup. But you will lose changes you made after you made the backups.
When I'm about to start testing ROMs, I backup system and data. To go back to my pre-testing ROM I restore system and data and then wipe cache partition.
Mioze7Ae said:
When I'm about to start testing ROMs, I backup system and data. To go back to my pre-testing ROM I restore system and data and then wipe cache partition.
Click to expand...
Click to collapse
You want to say system and boot ?
Because changing a room modify system.img and boot.img
The boot.img is the same on all the ROMs thanks to the locked bootloader.
Yeah, I never even bother changing boot.img from the sbf version. If I did I'd probably use the Russian one because I think it was the most recently compiled.
Ok, I wasn't knowing that I always flash boot.img that come with ROM.

Restore TWRP Backup How?

How do you do a restore of a TWRP Backup of a ROM or the original Asus JB OS? I tried to restore the backup I did before flashing the CROMi-X ROM. When I try to do a restore in TWRP and goto the Micro SD Memory card I have the backup on it does not show any files. Do you have to use the same version of TWRP that you backed up in order to restore or can you use the same version or higher?
Thanks
TWRP can only read fat32. Are you sure your microSD is formatted correctly?
Unless the TWRP version you used to make the nandroid and your current one are miles apart, it should work. Hard to tell since you didn't post any versions.
I have TWRP 2.6.3 and it is able to read the memory card and see the Flash ZIP file. I used TWRP 2.6.1 to back up The Asus Stock ROM before flashing the custom ROM. When TWRP does a backup does it backup the Data and how my screens are set up or only the operating system?
berndblb said:
TWRP can only read fat32. Are you sure your microSD is formatted correctly?
Unless the TWRP version you used to make the nandroid and your current one are miles apart, it should work. Hard to tell since you didn't post any versions.
Click to expand...
Click to collapse
daldude786 said:
I have TWRP 2.6.3 and it is able to read the memory card and see the Flash ZIP file. I used TWRP 2.6.1 to back up The Asus Stock ROM before flashing the custom ROM. When TWRP does a backup does it backup the Data and how my screens are set up or only the operating system?
Click to expand...
Click to collapse
It depends what options you checked when you made the nandroid. If you left the default selection, TWRP backed up both system and data.
If TWRP can read your microSD, what's your problem? I don't understand - since you wrote earlier that TWRP doesn't see any files??
2.6.3 and 2.6.1 are compatible. You shouldn't have a problem restoring the nandroid.
Sent from my HTC6525LVW using Tapatalk
Let me Rephrase that I meant when I do a restore funtion it does not see any files but if I do a Flah funtion or use the file manager it does see files.
berndblb said:
It depends what options you checked when you made the nandroid. If you left the default selection, TWRP backed up both system and data.
If TWRP can read your microSD, what's your problem? I don't understand - since you wrote earlier that TWRP doesn't see any files??
2.6.3 and 2.6.1 are compatible. You shouldn't have a problem restoring the nandroid.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
daldude786 said:
Let me Rephrase that I meant when I do a restore funtion it does not see any files but if I do a Flah funtion or use the file manager it does see files.
Click to expand...
Click to collapse
Did you manually copy the nandroid to the card?
It has to be nested exactly like TWRP created the folder or TWRP will not recognize it.
Something like TWRP/Backups/your-serial-number/date of backup/
Sent from my K00C using Tapatalk
I can't see my serial number because I'm in a bootloop, how can I see it inside twrp?
While in recovery run this command frog your PC:
Code:
adb get-serialno
There's also a Terminal cmd that you could run in TWRP's terminal. Not certain but I think it's just
Code:
id

EFS problem, how to restore?

Hi! I have a problem with efs partition of a Galaxy S7 (g930f)
In practice I flashed an efs (do not ask me why) corrupted in the same partition through an app I do not remember the name. Now it does not start anymore, it goes directly to recovery with 3 same mistakes "failed to mount / efs (invalid argument)" I tried installing a 4-file stock rom, successfully flashed with Odin but the problem persists. Before doing this stupid thing I fortunately backed up the radio and efs partition, but I do not know how to restore it!
The device only goes into recovery and download mode. I also flash autoroot and supersu through TWRP recovery to launch commands with adb type "adb shell" and "su" (which do not work, probably isn't good rooted or not enabled debug mode that I can't turn it on )
Fastboot fails to recognize the device.
I tried to flash the .tar backup file via Odin (I also have it .img, unfortunately it's not possible to flash it via Twrp) placing it in AP but it returns Fail. For the rest I tried to do all the possible wipe by deleting the entire OS and reflashing the stock with Odin by activating "re-partition" and "efs clean" but without solving, always the usual error in recovery.
What do you suggest me to do?
ElPocho796 said:
Hi! I have a problem with efs partition of a Galaxy S7 (g930f)
In practice I flashed an efs (do not ask me why) corrupted in the same partition through an app I do not remember the name. Now it does not start anymore, it goes directly to recovery with 3 same mistakes "failed to mount / efs (invalid argument)" I tried installing a 4-file stock rom, successfully flashed with Odin but the problem persists. Before doing this stupid thing I fortunately backed up the radio and efs partition, but I do not know how to restore it!
The device only goes into recovery and download mode. I also flash autoroot and supersu through TWRP recovery to launch commands with adb type "adb shell" and "su" (which do not work, probably isn't good rooted or not enabled debug mode that I can't turn it on )
Fastboot fails to recognize the device.
I tried to flash the .tar backup file via Odin (I also have it .img, unfortunately it's not possible to flash it via Twrp) placing it in AP but it returns Fail. For the rest I tried to do all the possible wipe by deleting the entire OS and reflashing the stock with Odin by activating "re-partition" and "efs clean" but without solving, always the usual error in recovery.
What do you suggest me to do?
Click to expand...
Click to collapse
Hi mate
I know you said "dont ask me why" but why you flashed someone else EFS? , the only reason I can think of is to change the IMEI...........
I you have your old EFS partition backup use the same tool you used before to restore, usually tool work both ways, what utillity you used to backup your EFS?
You cant use Odin for that.....can you get in download mode? flash a stock firmware again , make sure it boots now try to restore YOUR EFS backup with the same utility you made it
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
ElPocho796 said:
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
Click to expand...
Click to collapse
Hi
So is back in working order then? Great
ElPocho796 said:
Thank you for the reply. For backup I used an app with the function to save and restore partitions, I could not use it to restore because it is an app that should be installed and used with the device started while i was in bootloop.
I resolved through the terminal of the TWRP with the following string, inserting backup efs.img into the internal sd:
dd if=/sdcard/efs.img of=/dev/block/platform/155a0000.ufs/by-name/EFS
Click to expand...
Click to collapse
can you help me please. I have the same problem with my G930F. I had the superman-rom.zip and installed it through the manual on xda and now I have an unknown imei / Baseband and no sim. I saw that you had restored a backup and started working on it. I see an EFSbackup folder with efs.img and build.prop files. I could also put it back.

Categories

Resources