[Backup Script]Backup all paritions on i9505 to odin rom - Galaxy S 4 Developer Discussion [Developers-Only]

This morning I was coding this script, but didn't feel like extending it further. it basically just dumps all known partitions to the chosen dir and then makes a (compressed) odin rom from it, if chosen.
if anyone wants to use this, feel free to do whatever you want with it. I will occasionally dump some items on this forum that I find share worthy. just to share some inside stuff that will never get released when I don't share it here
Code:
#!/system/bin/sh
# Complete backup for Galaxy S4 (i9505)
# Created by broodplank1337
# Developer Sample (free for all kinds of use)
# www.broodplank.net
MAKEODIN="n";
ODINUSECOMPRESS="n";
BACKUPNONODIN="n";
OUTPATH="/storage/sdcard1/backup/";
echo "Starting backup..."
echo "Overall process may take upto 30 minutes"
echo
echo "BACKUP MODEM"
echo
echo "1. NON-HLOS.bin"
busybox dd if=/dev/block/mmcblk0p1 of=${OUTPATH}NON-HLOS.bin
echo "2. modem.bin"
busybox dd if=/dev/block/mmcblk0p2 of=${OUTPATH}modem.bin
echo
echo "BACKUP BOOTLOADER"
echo
echo "1. sbl1.mbn"
busybox dd if=/dev/block/mmcblk0p3 of=${OUTPATH}sbl1.mbn
echo "2. sbl2.mbn"
busybox dd if=/dev/block/mmcblk0p4 of=${OUTPATH}sbl2.mbn
echo "3. sbl3.mbn"
busybox dd if=/dev/block/mmcblk0p5 of=${OUTPATH}sbl3.mbn
echo "4. aboot.mbn"
busybox dd if=/dev/block/mmcblk0p6 of=${OUTPATH}aboot.mbn
echo "5. rpm.mbn"
busybox dd if=/dev/block/mmcblk0p7 of=${OUTPATH}rpm.mbn
echo "6. tz.mbn"
busybox dd if=/dev/block/mmcblk0p8 of=${OUTPATH}tz.mbn
echo
echo "BACKUP PLATFORM"
echo
echo "1. system.img.ext4"
busybox dd if=/dev/block/mmcblk0p16 of=${OUTPATH}system.img.ext4
echo "2. recovery.img"
busybox dd if=/dev/block/mmcblk0p21 of=${OUTPATH}recovery.img
echo "3. boot.img"
busybox dd if=/dev/block/mmcblk0p20 of=${OUTPATH}boot.img
echo
echo "BACKUP CSC"
echo
echo "1. cache.img.ext4"
busybox dd if=/dev/block/mmcblk0p18 of=${OUTPATH}cache.img.ext4
if [[ $MAKEODIN != "n" ]]; then
echo
echo "Making odin package, this may take a while"
echo
cd ${OUTPATH}
GETDATE=`busybox date -I`;
if [[ $ODINUSECOMPRESS != "n" ]]; then
echo "Making compressed tar ball"
busybox tar -cz NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar.gz
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar.gz >> odin-${GETDATE}.tar.gz
echo "Renaming..."
busybox mv odin-${GETDATE}.tar.gz odin-${GETDATE}.tar.md5.gz
else
echo "Making tar ball"
busybox tar -c NON-HLOS.bin modem.bin sbl1.mbn sbl2.mbn sbl3.mbn aboot.mbn rpm.mbn tz.mbn system.img.ext4 recovery.img boot.img cache.img.ext4 > odin-${GETDATE}.tar
echo "Writing MD5 sums..."
busybox md5sum -t odin-${GETDATE}.tar >> odin-${GETDATE}.tar
echo "Renaming..."
busybox mv odin-${GETDATE}.tar odin-${GETDATE}.tar.md5
fi;
echo
echo "Odin package has been created"
echo
fi;
if [[ ${BACKUPNONODIN} != "n" ]]; then
echo
echo "backup non odin (others).."
echo
busybox dd if=/dev/block/mmcblk0p9 of=${OUTPATH}PAD
busybox dd if=/dev/block/mmcblk0p10 of=${OUTPATH}efs.img.ext4
busybox dd if=/dev/block/mmcblk0p11 of=${OUTPATH}nvrebuild1.bin
busybox dd if=/dev/block/mmcblk0p12 of=${OUTPATH}nvrebuild2.bin
busybox dd if=/dev/block/mmcblk0p13 of=${OUTPATH}m9kefs1.bin
busybox dd if=/dev/block/mmcblk0p14 of=${OUTPATH}m9kefs2.bin
busybox dd if=/dev/block/mmcblk0p15 of=${OUTPATH}m9kefs3.bin
busybox dd if=/dev/block/mmcblk0p17 of=${OUTPATH}PERSIST
busybox dd if=/dev/block/mmcblk0p19 of=${OUTPATH}param.lfs
busybox dd if=/dev/block/mmcblk0p22 of=${OUTPATH}FOTA
busybox dd if=/dev/block/mmcblk0p23 of=${OUTPATH}BACKUP
busybox dd if=/dev/block/mmcblk0p24 of=${OUTPATH}FSG
busybox dd if=/dev/block/mmcblk0p25 of=${OUTPATH}SSD
busybox dd if=/dev/block/mmcblk0p26 of=${OUTPATH}persdata.img.ext4
busybox dd if=/dev/block/mmcblk0p27 of=${OUTPATH}hidden.img.ext4
busybox dd if=/dev/block/mmcblk0p29 of=${OUTPATH}userdata.img.ext4
busybox dd if=/dev/block/mmcblk0p28 of=${OUTPATH}carrier.img.ext4
fi;
echo
echo "BACKUP COMPLETED!"
echo

---

Thanks friend! :good:
regards!

---

I'm pretty sure this needs to run as root because some of those partitions are likely read protected.

---

CNexus said:
I'm pretty sure this needs to run as root because some of those partitions are likely read protected.
Click to expand...
Click to collapse
Anyone tried restoring an odin tar generated with this using the odin app? I thought the files had to be signed by samsung to be accepted by odin?
Also, do you set the tar.md5 file generated in the "PDA" field of Odin?

---

prisonnet said:
Anyone tried restoring an odin tar generated with this using the odin app? I thought the files had to be signed by samsung to be accepted by odin?
Also, do you set the tar.md5 file generated in the "PDA" field of Odin?
Click to expand...
Click to collapse
Nope, only zips to be flashed through (stock) recovery need to be signed by Samsung

---

found a typo:
line 38: if [[ ${BACKUPNONODIN} != "n" ]]; then
and on some roms may need to edit:
OUTPATH="/storage/extSdCard/backup/";

---

TRusselo said:
found a typo:
line 38: if [[ ${BACKUPNONODIN} != "n" ]]; then
and on some roms may need to edit:
OUTPATH="/storage/extSdCard/backup/";
Click to expand...
Click to collapse
That first one isn't a typo btw.

---

CNexus said:
Nope, only zips to be flashed through (stock) recovery need to be signed by Samsung
Click to expand...
Click to collapse
Trying to flash with Odin 3.07, MD5 verifies but getting this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> system.img.ext4.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> system.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
Click to expand...
Click to collapse
Any idea?

---

CNexus said:
That first one isn't a typo btw.
Click to expand...
Click to collapse
really? seems like it is, and my script editor was highlighting it too as an error. that bracket never ends {

---

prisonnet said:
Trying to flash with Odin 3.07, MD5 verifies but getting this error:
Any idea?
Click to expand...
Click to collapse
Hmm thats kinda strange, it should work just fine actually. can you list the files inside the .tar.md5 please?
TRusselo said:
really? seems like it is, and my script editor was highlighting it too as an error. that bracket never ends {
Click to expand...
Click to collapse
At first I though you were wrong but you're actually right, it should be either $VAR OR ${VAR}, despite that the script runs successfully.

---

I'm curious to know why we can only flash modems (modem.bin and non-hlos.bin) via odin
Why won't the following commands for example work in a shell called in a CWM.zip?
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
What is causing the restriction for modems to only be able to be flashed through Odin and not CWM?
Has this also got something to do with the fact that you can only successfully flash a modem if entered download mode through a complete power-off, and not via the power menu?

---

hawkerpaul said:
I'm curious to know why we can only flash modems (modem.bin and non-hlos.bin) via odin
Why won't the following commands for example work in a shell called in a CWM.zip?
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p2
What is causing the restriction for modems to only be able to be flashed through Odin and not CWM?
Has this also got something to do with the fact that you can only successfully flash a modem if entered download mode through a complete power-off, and not via the power menu?
Click to expand...
Click to collapse
The thing is no one ever tries to do this. I'm almost 100% sure that this is just possible.
Maybe you cannot directly flash those 2 files, but you can do this without any problems:
Backup modem partition and just flash it on an other device. same amount of blocks, so should be no problem.
dd if=/dev/block/mmcblk0p1 of=/sdcard/NON-HLOS.bin
dd if=/sdcard/NON-HLOS.bin of=/dev/block/mmcblk0p1
but it still forced you to use odin once atleast to flash it
(no confirmed results though)

---

I agree with you. I just don't see any reason why the device dump commands can't also work for modems. I've just taken it as one of those things that cannot be done via cwm.
I was worried in case I did dump to those partitions it might screw the device taking into consideration it just isn't the done thing to do.
I will write a shell script to be called through cwm to see if it can be done..... just hope it don't bugger my device up!
Edit:
I've just tried the following:
dd if=/dev/block/mmcblk0p2 of=/sdcard/modem.dd.bin
I then opened the downloaded modem.tar file that I have for my current modem (currently I'm on XXUFNBE), extracted modem.bin onto pc, then copied it to /sdcard/modem.bin
Unfortunately, these 2 files differ in a diff command, and if I do an ls -l, they differ quite drastically:
ls -l:
-rw-rw-r-- root sdcard_rw 52354048 2014-03-07 21:13 modem.bin
-rw-rw-r-- root sdcard_rw 54030336 2014-03-07 21:07 modem.dd.bin
Obviously its not even worth attempting to dd this modem.bin file back to /dev, as its not the same as original modem.dd.bin I created.
Either there is a problem with the way modem.bin gets extracted from the .tar file on PC through 7zip, (as 7zip does complain with "no correct record at the end of the archive" when I extract it) or I need to supply dd with different command line parameters.

---

You have to know that this is totally normal when using dd, the thing with dd is that it dumps the WHOLE partition, so also all zero's (no data) to a file. for example if you dd boot.img you will get a file that is EXACTLY 10mb, since that is the size of the partition. but when flashing it back to the partition it won't cause any problems afaik. I have done it a couple of times.
(To lookup how big the files will turn out, check: 'cat /proc/partitions')
Code:
[email protected]:/ # cat proc/partitions
major minor #blocks name
7 0 4190 loop0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p29
254 0 4189 dm-0
sizes are expressed in KiloBytes
Here is my little experiment to prove it to you:
Code:
[email protected] ~ $ [B]adb shell[/B]
[email protected]:/ # [B]dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 2.283 secs (4592974 bytes/sec)
[email protected]:/ # [B]dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.470 secs (7133170 bytes/sec)
[email protected]:/ # [B]reboot[/B]
and my phone just booted as it normally does.
What you could do, but NEVER EVER should do is removing all zeros from the partition file with a hexeditor to get the actual size. but if you will flash back this image you probably screw up your partition as it's an invalid image for that partition.
So long story short, you can NEVER EVER flash modem.bin directly to the partition, but you can flash a partition dump you made earlier to the partition without causing damage (at least to your own device).
It's just a pity the modem does not come in .img format by default.
When using dd better be sure to know what you're doing :good:

---

broodplank1337 said:
You have to know that this is totally normal when using dd, the thing with dd is that it dumps the WHOLE partition, so also all zero's (no data) to a file. for example if you dd boot.img you will get a file that is EXACTLY 10mb, since that is the size of the partition. but when flashing it back to the partition it won't cause any problems afaik. I have done it a couple of times.
(To lookup how big the files will turn out, check: 'cat /proc/partitions')
Code:
[email protected]:/ # cat proc/partitions
major minor #blocks name
7 0 4190 loop0
179 0 15388672 mmcblk0
179 1 12772 mmcblk0p1
179 2 52764 mmcblk0p2
179 3 128 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 2048 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 16896 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 780 mmcblk0p13
179 14 780 mmcblk0p14
179 15 780 mmcblk0p15
179 16 2826240 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 2119680 mmcblk0p18
179 19 6144 mmcblk0p19
179 20 10240 mmcblk0p20
179 21 10240 mmcblk0p21
179 22 10240 mmcblk0p22
179 23 6144 mmcblk0p23
179 24 3072 mmcblk0p24
179 25 8 mmcblk0p25
179 26 9216 mmcblk0p26
179 27 512000 mmcblk0p27
179 28 20480 mmcblk0p28
179 29 9728000 mmcblk0p29
254 0 4189 dm-0
sizes are expressed in KiloBytes
Here is my little experiment to prove it to you:
Code:
[email protected] ~ $ [B]adb shell[/B]
[email protected]:/ # [B]dd if=/dev/block/mmcblk0p20 of=/sdcard/boot.img[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 2.283 secs (4592974 bytes/sec)
[email protected]:/ # [B]dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20[/B]
20480+0 records in
20480+0 records out
10485760 bytes transferred in 1.470 secs (7133170 bytes/sec)
[email protected]:/ # [B]reboot[/B]
and my phone just booted as it normally does.
What you could do, but NEVER EVER should do is removing all zeros from the partition file with a hexeditor to get the actual size. but if you will flash back this image you probably screw up your partition as it's an invalid image for that partition.
So long story short, you can NEVER EVER flash modem.bin directly to the partition, but you can flash a partition dump you made earlier to the partition without causing damage (at least to your own device).
It's just a pity the modem does not come in .img format by default.
When using dd better be sure to know what you're doing :good:
Click to expand...
Click to collapse
Hey broodplank, your scripts are excellent btw. But I just wanted to let you know flashing modems through recovery does work and there's quite a few ways to do this.
1. assert extract dir "/tmp/modem.bin" then write raw image method
2. run program "/sbin/sh" "script.sh" method
3. run program "dd if=/..... method
4. Use the flash_image binary
You get the picture from the above I hope, 1-3 are updater-script related. I have a Verizon S4 Modem thread where I include zips that flash modems but also the modem.bin files can be extracted from the zips and used in odin.
I regularly hexedit the padded bootloaders to cut the trailing zeroes so the partition registers as signed (I recommend only experienced individuals do this though). When you say the partition would be invalid I take it you mean that unless the individual who is hexediting knows how to correctly do it that it will be invalid.

---

Surge1223 said:
Hey broodplank, your scripts are excellent btw. But I just wanted to let you know flashing modems through recovery does work and there's quite a few ways to do this.
1. assert extract dir "/tmp/modem.bin" then write raw image method
2. run program "/sbin/sh" "script.sh" method
3. run program "dd if=/..... method
4. Use the flash_image binary
You get the picture from the above I hope, 1-3 are updater-script related. I have a Verizon S4 Modem thread where I include zips that flash modems but also the modem.bin files can be extracted from the zips and used in odin.
I regularly hexedit the padded bootloaders to cut the trailing zeroes so the partition registers as signed (I recommend only experienced individuals do this though). When you say the partition would be invalid I take it you mean that unless the individual who is hexediting knows how to correctly do it that it will be invalid.
Click to expand...
Click to collapse
Thank you. Oh ok, I didn't know that
I actually know those methods, but with the second one what script do you mean, or just a partition flash script in general?
So I downloaded one of your zips and found this.
Code:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
That's amazingly easy! Wow! Never knew this was so easy to do, I thought a special flashing binary would be needed.
Thanks a lot for this tip! It's great
And yes I mean do not ever use hexeditor if you don't know what you're doing :good:

---

I still can't get a modem flash to work in recovery. (I happen to be using Philz)
I use the Modem tar files in djembey's thread.
I open the modem.tar file, and 7zip says tar error: there is no correct record at the end of archive
It opens regardless, so I extract modem.bin
I then place the modem.bin in a typical cwm-flashable zip file, which includes updater-script as above post, ie:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
However, the script hangs, and I have to long-press the power button in recovery to reboot.
Is the modem.bin incorrect from the original extraction via 7Zip perhaps? (Although the .tar file from which I extracted modem.bin flashes successfully in Odin by the way.)
Any ideas appreciated.

---

hawkerpaul said:
I still can't get a modem flash to work in recovery. (I happen to be using Philz)
I use the Modem tar files in djembey's thread.
I open the modem.tar file, and 7zip says tar error: there is no correct record at the end of archive
It opens regardless, so I extract modem.bin
I then place the modem.bin in a typical cwm-flashable zip file, which includes updater-script as above post, ie:
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p2"),
delete("/tmp/modem.bin"));
However, the script hangs, and I have to long-press the power button in recovery to reboot.
Is the modem.bin incorrect from the original extraction via 7Zip perhaps? (Although the .tar file from which I extracted modem.bin flashes successfully in Odin by the way.)
Any ideas appreciated.
Click to expand...
Click to collapse
Actually this is kind of a known issue. I believe some have found a work around with Philz. @Bait-Fish what was it that you guys do to flash modems with Philz?

---

Surge1223 said:
Actually this is kind of a known issue. I believe some have found a work around with Philz. @Bait-Fish what was it that you guys do to flash modems with Philz?
Click to expand...
Click to collapse
I would be extremely interested and appreciative to find this out
:good:
EDIT:
Just tried a flash through TWRP, and no joy, so this is not specific to Philz.

---

hawkerpaul said:
I would be extremely interested and appreciative to find this out
:good:
EDIT:
Just tried a flash through TWRP, and no joy, so this is not specific to Philz.
Click to expand...
Click to collapse
Im able to flash modems quite easily hmm... can you send me the modem zip package you are trying to flash so I can take a look at it?
P.S. This dev talk forum is finally starting to be useful again!