Help How do i create a NANDroid backup which contains boot.img, recovery.img and system.img?

[pollock83]

How do i create a NANDroid backup which contains boot.img, recovery.img and system.img? I created a NANDroid backup with my TWRP recovery but it created a load of files which did not include boot.img, recovery.img or system.img. Then i reflashed Philz Recovery (Based on CWM) And did a NANDroid backup which was better as it included a boot.img and recovery.img but no system.img. This concerns me as i was wanting to install the Xposed framework but was worried by the popup which said i could bootloop or softbrick my phone and was wanting to know how to fix a bootlooped phone and i found a way using fastboot but i need boot.img, recovery.img and system.img but only have the first two in my Philz (CWM) NANDroid Backup. How do i create a NANDroid backup that create boot.img, recovery.img and system.img?

I am using a Samsung Galaxy S5 (SM-G900F).

Any help would be greatly appreciated,
Thanks,
Pollock83

 

[scary alien]

pollock83,

What were the file names that those two recoveries did create?

I'm guessing that the /system partition might have been named system.ext4.win (in TWRP)--not sure about Philz Recovery as I've never used that one.

I also believe there are checkboxes that you can select to tell TWRP which partitions to include the backups.

Also, you manually backup some of your smaller partitions if you know there device paths. I've included a feature in one of my apps that allows you to do this, but having them included in the Nandroid backup (and later restorable) is certainly more desireable.

Cheers!

 

[pollock83]

pollock83,

What were the file names that those two recoveries did create?

I'm guessing that the /system partition might have been named system.ext4.win (in TWRP)--not sure about Philz Recovery as I've never used that one.

I also believe there are checkboxes that you can select to tell TWRP which partitions to include the backups.

Also, you manually backup some of your smaller partitions if you know there device paths. I've included a feature in one of my apps that allows you to do this, but having them included in the Nandroid backup (and later restorable) is certainly more desireable.

Cheers!

These are the files the two recoveries created:

Philz:

TWRP:

It's just that i have seen people on youtube saying flash over recovery.img, boot.img and system.img but i do not have a system img so i dont know how i would restore my phone if it bootlooped using fastboot or ADB without a system.img.

Thanks,
Pollock83

 

[scary alien]

These are the files the two recoveries created:

<snip>

It's just that i have seen people on youtube saying flash over recovery.img, boot.img and system.img but i do not have a system img so i dont know how i would restore my phone if it bootlooped using fastboot or ADB without a system.img.

Thanks,
Pollock83

Yeah, I can see in your TWRP backup that you've got your recovery partition (often named recovery.img where the ".img" portion is just a suffix to indicate it's a partition image file--it could have been called ".xyz" since what is important is the prefix portion and the file's contents, of course) named as "recovery" (just the recovery binary) and "recovery.emmc.win" (likely the full recovery partition which is usually larger than the recovery binary requires) and recovery.emmc.win.md5 (the MD5 checksum for the recovery.emmc.win file).

The TWRP boot image is named boot.emmc.win, and the system image is named and spread-apart as several files due to their size: system.ext4.win000 and system.ext4.win001 (I'm guessing the system.info file might indicate this information, too).

Looks like Philz uses a similar naming scheme for the suffixes--i.e., adding "ext4" to indicate the partition type (and TWRP also uses "emmc" for the non-EXT4 partitions).

It looks to me that each of your above two custom recoveries have you fully covered .

 

[EarlyMon]

Most - not all but the vast majority - of how-to root youtube videos are just wrong. They're usually made by people scraping forums for the answers and then trying to score on YouTube ad hits. I can't count the ones where it's been obvious that the creator has never rooted a thing.

So - maybe you saw some good ones and maybe you didn't.

You use your custom recovery to backup and restore, yeah? So I would proceed with extreme caution using recovery to restore itself. You'd only want to try if the recovery were somehow bad or wrong but in such a case, how could you use it?

I'd question the same about the bootloader.

And maybe in the Samsung world, system.img exists now, I don't know, but it never used to.

Never back up the cache, that's completely counterproductive.

Trust the root guides here and at XDA and only trust youtubes made by known contributors with a good track record here or there.

Typically your minimum backup is boot, system and data. Optionally you may need to back up APN settings or your phone id (model and carrier dependent).

Hope this helps!

 

[pollock83]

Yeah, I can see in your TWRP backup that you've got your recovery partition (often named recovery.img where the ".img" portion is just a suffix to indicate it's a partition image file--it could have been called ".xyz" since what is important is the prefix portion and the file's contents, of course) named as "recovery" (just the recovery binary) and "recovery.emmc.win" (likely the full recovery partition which is usually larger than the recovery binary requires) and recovery.emmc.win.md5 (the MD5 checksum for the recovery.emmc.win file).

The TWRP boot image is named boot.emmc.win, and the system image is named and spread-apart as several files due to their size: system.ext4.win000 and system.ext4.win001 (I'm guessing the system.info file might indicate this information, too).

Looks like Philz uses a similar naming scheme for the suffixes--i.e., adding "ext4" to indicate the partition type (and TWRP also uses "emmc" for the non-EXT4 partitions).

It looks to me that each of your above two custom recoveries have you fully covered .

Most - not all but the vast majority - of how-to root youtube videos are just wrong. They're usually made by people scraping forums for the answers and then trying to score on YouTube ad hits. I can't count the ones where it's been obvious that the creator has never rooted a thing.

So - maybe you saw some good ones and maybe you didn't.

You use your custom recovery to backup and restore, yeah? So I would proceed with extreme caution using recovery to restore itself. You'd only want to try if the recovery were somehow bad or wrong but in such a case, how could you use it?

I'd question the same about the bootloader.

And maybe in the Samsung world, system.img exists now, I don't know, but it never used to.

Never back up the cache, that's completely counterproductive.

Trust the root guides here and at XDA and only trust youtubes made by known contributors with a good track record here or there.

Typically your minimum backup is boot, system and data. Optionally you may need to back up APN settings or your phone id (model and carrier dependent).

Hope this helps!

Ok......

So how would i go about flashing these files onto my phone if it lets say bootlooped? What software would i use? How would i go about it?

Pollock83,

 

[scary alien]

Note, I am not an SGS5 owner/user, but the restore functions of your selected custom recovery (TWRP, Philz, CWM, etc.) should allow you to restore a prior, known good / working setup, back to your device should you encounter trouble.

You should also, of course, keep an off-device copy of your Nandroid backup onto some external location like your PC's hard drive or other external media should the Nandroid backup on your device become corrupted (multiple backup copies would not be a bad idea, either).

I'll leave further, detailed comments to the folks that actually own an SGS5.

 

[pollock83]

Note, I am not an SGS5 owner/user, but the restore functions of your selected custom recovery (TWRP, Philz, CWM, etc.) should allow you to restore a prior, known good / working setup, back to your device should you encounter trouble.

You should also, of course, keep an off-device copy of your Nandroid backup onto some external location like your PC's hard drive or other external media should the Nandroid backup on your device become corrupted (multiple backup copies would not be a bad idea, either).

I'll leave further, detailed comments to the folks that actually own an SGS5.

If my phone is bootlooping then am i able to access the Recovery or is that inaccessible aswell?

EDIT: Also how much of a chance is that my phone will bootloop and/or soft brick when installing the Xposed Framework?

 

[ironass]

PhilZ CWM, (ClockWorkMod), Backup and Restore video...

How to Backup/Restore ROM on Rooted Galaxy S5!

Guide... How to Backup/Restore ROM on Rooted Galaxy S5!

TWRP Backup and Restore video, (it shows a Note 3 but it also applies to the S5)...

How to Backup/Restore ROM using TWRP on Rooted Galaxy Note 3!

Guide... How to Backup/Restore ROM using TWRP on Rooted Galaxy Note 3!

 

[pollock83]

Note, I am not an SGS5 owner/user, but the restore functions of your selected custom recovery (TWRP, Philz, CWM, etc.) should allow you to restore a prior, known good / working setup, back to your device should you encounter trouble.

You should also, of course, keep an off-device copy of your Nandroid backup onto some external location like your PC's hard drive or other external media should the Nandroid backup on your device become corrupted (multiple backup copies would not be a bad idea, either).

I'll leave further, detailed comments to the folks that actually own an SGS5.

PhilZ CWM, (ClockWorkMod), Backup and Restore video...

How to Backup/Restore ROM on Rooted Galaxy S5!

Guide... How to Backup/Restore ROM on Rooted Galaxy S5!

TWRP Backup and Restore video, (it shows a Note 3 but it also applies to the S5)...

How to Backup/Restore ROM using TWRP on Rooted Galaxy Note 3!

Guide... How to Backup/Restore ROM using TWRP on Rooted Galaxy Note 3!

Thanks! I'll have a look at those! Do either of you know how bug of a chance there is that my phone will bootloop or softbrick after installing The Xposed Framework?

 

[ironass]

Thanks! I'll have a look at those! Do either of you know how bug of a chance there is that my phone will bootloop or softbrick after installing The Xposed Framework?

Any flashing procedure carries a certain amount of risk. This is why you should always make a nandroid backup, to your external SD card, prior to any flashing. This is your, "Get out of jail FREE", card. The chief problem that I come across is that people DO NOT read and fully understand what they are doing and just, "Hope for the best". Google search is your best friend when it comes to researching ROM's, mods and rooting. Also, you should carefully and thoroughly read the developers installation instructions for any particular ROM or mod.

 

[vce2005]

I never had trouble installing xposed on either, my S3 or on my tablet.....