dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/mmcblk0p13.img
dd if=/dev/block/mmcblk0p28 of=/mnt/sdcard/mmcblk0p28.img
dd if=/dev/block/mmcblk0p29 of=/mnt/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p30 of=/mnt/sdcard/mmcblk0p30.img
all of these are blank or almost blank for me and tis causing my 3g not to work..
if someone can dump them and upload, i'd be really happy
usual command is adb shell
su
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p13 of=/mnt/sdcard/mmcblk0p13.img
dd if=/dev/block/mmcblk0p28 of=/mnt/sdcard/mmcblk0p28.img
dd if=/dev/block/mmcblk0p29 of=/mnt/sdcard/mmcblk0p29.img
dd if=/dev/block/mmcblk0p30 of=/mnt/sdcard/mmcblk0p30.img
mmcblk0p5 has the cid and imei and mmcblk0p13 says SkaBHT231V208772 other files are empty for me
ercineker said:
mmcblk0p5 has the cid and imei and mmcblk0p13 says SkaBHT231V208772 other files are empty for me
Click to expand...
Click to collapse
thank u!
Related
Hi there,
Is it possible to make a full backup of my stock ROM via ADB?
I know that it was possible on SGS I9000 (something like below code)
Code:
adb shell
su
mkdir /sdcard/BackupRom
dd if=/dev/block/bml1 of=/sdcard/BackupRom/boot.bin bs=4096
dd if=/dev/block/bml2 of=/sdcard/BackupRom/pit.pit bs=4096
dd if=/dev/block/stl3 of=/sdcard/BackupRom/efs.rfs bs=4096
dd if=/dev/block/bml4 of=/sdcard/BackupRom/Sbl.bin bs=4096
dd if=/dev/block/stl6 of=/sdcard/BackupRom/param.lfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/BackupRom/zImage bs=4096
dd if=/dev/block/stl9 of=/sdcard/BackupRom/factoryfs.rfs bs=4096
dd if=/dev/block/stl10 of=/sdcard/BackupRom/dbdata.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/BackupRom/cache.rfs bs=4096
dd if=/dev/block/bml12 of=/sdcard/BackupRom/modem.bin bs=4096
tar -czvf /sdcard/BackupRom/data.tar.gz /data
I want to do this because nandroid implies modifying kernel, and ADB backup would be the cleanest way.
Thanks!!
I think its possible, but you probably need your phone to be rooted in order to do such a thing.
kaukassus said:
I think its possible, but you probably need your phone to be rooted in order to do such a thing.
Click to expand...
Click to collapse
You are right... Root is needed.
Thanks
Hey
I found another post which details a way to get all of the relevant files together from your device, and then bundled into a tar, so that you can use Odin to reflash your own 'custom' backup. I have put the commands below, does anyone know how to tailor this for the SGS2 ? The \dev\block\* devices are different as when i try through adb shell or terminal emulator it doesn't recognise the devices ::
Sys:
dd if=/dev/block/stl10 of=/sdcard/factoryfs.rfs bs=4096
Kernel:
dd if=/dev/block/bml8 of=/sdcard/zImage bs=4096
Recovery:
dd if=/dev/block/bml9 of=/sdcard/recovery.bin bs=4096
(personal info)
Cache:
dd if=/dev/block/mmcblk0p3 of=/sdcard/cache.rfs bs=4096
DBData:
dd if=/dev/block/stl11 of=/sdcard/dbdata.rfs bs=4096
Data:
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096
and then to make the image for Odin to flash:
tar -H ustar -c cache.rfs dbdata.rfs factoryfs.rfs movinand.bin recovery.bin zImage > package_name.tar
md5sum -t package_name.tar >> package_name.tar
mv package_name.tar package_name.tar.md5
Any help appreciated
Thanks
I'm interested in this, too!
hi sea_salt !
I got the commands from another post:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
I have tried them using adb shell and they work .
The question is how do i get them now into a .tar/.md5 so that Odin can flash them ?
spoonflames said:
hi sea_salt !
I got the commands from another post:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
I have tried them using adb shell and they work .
The question is how do i get them now into a .tar/.md5 so that Odin can flash them ?
Click to expand...
Click to collapse
hey this sounds great. thanks for your reply!
Does EFS, PARAM, KERNEL, MODEM, FACTORYFS, HIDDEN contain ALL stuff of the sgs2-phone's-rom and data, so that it can be used to completetely backup the device?
but I suppose that these adb-commands only work when you already have a root-kernel, or not?
are there the same commands to use adb to restore all this stuff?
i there,
I'm working at creating a solution for JTAG repair on the SGS III USC model and I'm in need of a SCH-R530M SBL dumps and a few other zones. I need a rooted user to simply perform the following command from a terminal on the phone, or while using ADB SHELL under the su user. Once at the command line issue this command, then simply upload the files which end up on your sdcard to me here. That's it!
Thanks in advance!
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl2 bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl3 bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/aboot bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/tz bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/pad bs=4096
dd if=/dev/block/mmcblk0p10 of=/sdcard/param bs=4096
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery bs=4096
tomy1986.nt said:
i there,
I'm working at creating a solution for JTAG repair on the SGS III USC model and I'm in need of a SCH-R530M SBL dumps and a few other zones. I need a rooted user to simply perform the following command from a terminal on the phone, or while using ADB SHELL under the su user. Once at the command line issue this command, then simply upload the files which end up on your sdcard to me here. That's it!
Thanks in advance!
Code:
dd if=/dev/block/mmcblk0p2 of=/sdcard/sbl1 bs=4096
dd if=/dev/block/mmcblk0p3 of=/sdcard/sbl2 bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/sbl3 bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/aboot bs=4096
dd if=/dev/block/mmcblk0p6 of=/sdcard/rpm bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/tz bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/pad bs=4096
dd if=/dev/block/mmcblk0p10 of=/sdcard/param bs=4096
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery bs=4096
Click to expand...
Click to collapse
Reported your other thread - Reporting this one. USE THE APPROPRIATE DEVICE FORUM. One of the simplest rules!
Thread Closed.
OP Please follow the rules about double posts... Also please post in the correct sections.
For those who do not know, EFS partition containing IMEI, MEID, and other important data. Once lost, these partitions can not be recovered, because they are unique to your phone only.
Since we do not have a custom recovery yet, the only solutions to backup EFS partitions are in terminal or adb. I prefer adb because it is more easier to do.
1.Create a folder in internal sdcard named efs
2.Run these commands in adb or terminal
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/sdcard/efs/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/sdcard/efs/modemst2.img
3.If you want to backup all partitions on your phone create a folder named backup in internal sdcard can run these commands:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/backup/aboot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/backup/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/DDR of=/sdcard/backup/DDR.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/encrypt of=/sdcard/backup/encrypt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/backup/fota.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc of=/sdcard/backup/fsc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/backup/fsg.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/backup/laf.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/sdcard/backup/misc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/mpt of=/sdcard/backup/mpt.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/backup/persist.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rct of=/sdcard/backup/rct.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/backup/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/backup/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/sdcard/backup/sbl1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sns of=/sdcard/backup/sns.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/sdcard/backup/ssd.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/backup/tz.img
Less important partitions:
dd if=/dev/block/platform/msm_sdcc.1/by-name/abootb of=/sdcard/backup/abootb.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cust of=/sdcard/backup/cust.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/drm of=/sdcard/backup/drm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/eksst of=/sdcard/backup/eksst.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/factory of=/sdcard/backup/factory.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/grow of=/sdcard/backup/grow.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/backup/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/sdcard/backup/pad.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpmb of=/sdcard/backup/rpmb.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1b of=/sdcard/backup/sbl1b.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sdi of=/sdcard/backup/sdi.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tzb of=/sdcard/backup/tzb.img
For dd commands your phone has to be rooted.
Please do not ask me how to install and use adb.
If you want to restore your original EFS partitions just run the commands below in adb ot terminal:
dd if=/sdcard/efs/modemst1.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst1
dd if=/sdcard/efs/modemst2.img of=/dev/block/platform/msm_sdcc.1/by-name/modemst2
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could hard brick your phone.
Very nice work.
I thought that EFS is only used by Samsung. Guess not.
Sent from my D620R [Stock 4.4.2]
I just got a fresh Fire HD 7 with 4.1.1, and updated it first to 4.5.3, and then to 5.2.2u2 with 5.2.0 bootloaders. While doing so, I kept track of the state of all the internal partitions that the updates do not seemingly touch (see this post for partitions http://forum.xda-developers.com/fire-hd/help/internal-memory-structure-hidden-t3122246 )
I've been using a simple script pasted from adb window on the PC side (needs root access):
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/
I can now compare 2 different Fires (old & new), and also the new Fire on the path from 4.1.1 to 4.5.3 to 5.2.0
Between the 2 different Fires, the only partition that has the same md5 is :
72fe4bd35179bc299674c781033ae1f7 10_misc.img
The other dark partitions differ between the 2 Fires (pro_info, pmt, kb, dkb)
Now, on the new Fire, partition that always changes between boots is :
8c72758dff50208f74b7bbc12725e46a 11_persisbackup.img
(so this is probably the boot counter lives and so on)
Finally, when the new Fire went from 4.1.1 to 4.5.3, (pro_info, pmt, kb, dkb) all stayed the same. But when I updated it to 5.2.0 bootloaders, dkb changed md5. The other 3 are still the same.
It'd be nice to run this script on a Fire with 5.2.2u2 bootloaders, and see if persisbackup is the same.
It could be possible to replace some of these dark partitions, and convert the Fire into an "unbricking" state.
Just to confirm: One can copy your whole script and paste it into the CMD window. It runs and doesn't do anything to the Fire HD. It just gets info that can help you, right? Whoever does this can drag the mouse over all the output to select it and hit ENTER to copy to clipboard, then paste it into a post for you.
I ask because my guide doesn't install the 5.2.0 bootloaders, so anyone who used it in the last month or so will have 5.2.2.u2 bootloaders. If no one else jumps in, perhaps @comapro or @benyaki or @sunilzs would have the time to run it for you.
If time permits tomorrow, I'll run that for you. (And if I remember!)
benyaki said:
If time permits tomorrow, I'll run that for you. (And if I remember!)
Click to expand...
Click to collapse
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
C:\adb>adb shell
su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ $ su
dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
cd /sdcard/
md5 *.img
rm *.img
cd /sdcard/[email protected]:/ # dd if=/dev/block/mmcblk0p1 of=/sdcard/01_pro_info.img
256+0 records in
256+0 records out
131072 bytes transferred in 0.105 secs (1248304 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p2 of=/sdcard/02_pmt.img
8192+0 records in
8192+0 records out
4194304 bytes transferred in 1.357 secs (3090865 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p3 of=/sdcard/03_tee1.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 2.069 secs (2534016 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p4 of=/sdcard/04_tee2.img
10240+0 records in
10240+0 records out
5242880 bytes transferred in 1.930 secs (2716518 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p5 of=/sdcard/05_uboot.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.128 secs (4096000 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p6 of=/sdcard/06_boot.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.146 secs (3908950 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/07_recovery.img
16384+0 records in
16384+0 records out
8388608 bytes transferred in 2.113 secs (3969999 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p8 of=/sdcard/08_kb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.323 secs (3246365 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p9 of=/sdcard/09_dkb.img
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.265 secs (3956890 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p10 of=/sdcard/10_misc.img
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.131 secs (4002198 bytes/sec)
[email protected]:/ # dd if=/dev/block/mmcblk0p11 of=/sdcard/11_persisbackup.img
32768+0 records in
32768+0 records out
16777216 bytes transferred in 4.256 secs (3942015 bytes/sec)
[email protected]:/ # cd /sdcard/
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
benyaki said:
Here you go. Hope I did it correctly. If you need anything else, let me know.
Code:
[email protected]:/sdcard # md5 *.img
40ab8a444a6bb38a77c8b023c8c28498 01_pro_info.img
976b7613ac6ccd0f8221b5dc13d01676 02_pmt.img
a25016f54a524f93e0c1225539273404 03_tee1.img
eb83b62828a361f33c6ed0ac62c872e7 04_tee2.img
233387047f6eb2e5e9f760cfc3adb5c7 05_uboot.img
e9a0260c940a03510662c74ee269c72e 06_boot.img
7082205b20052ae93c9215460de8f891 07_recovery.img
96b0de56e2e022e07e6dbaa0df49fcae 08_kb.img
32dadf8d79d0749dd054b11bd34051bf 09_dkb.img
72fe4bd35179bc299674c781033ae1f7 10_misc.img
ef16264f4b03b8879441e49478587528 11_persisbackup.img
[email protected]:/sdcard # rm *.img
[email protected]:/sdcard # cd /sdcard/
[email protected]:/sdcard #
Click to expand...
Click to collapse
I think the issue is pretty tough. KB and DKB look like candidates to have clues for bricking. Most of "dark" partitions are non-trivially different between the 2 Fires I have, so overwriting them with different copies is probably not advisable
Actually, what would really help is to run md5 before running 5.2.2u2 bootloaders for the 1st time, and then after to see if it's just DKB that changed. One could back up these partitions before playing with the device, so if 5.2.2u2 bootloaders get accidentally loaded, there could be a way to go back.
Fire 7 2015 has similar bricking phenomenon (5.0.1 to 5.1.1 transition). So it might be safer to attempt to explore it with Fire 2015. One just captures all the partitions under 5.0.1, loads up the 5.1.1 bootloaders, captures all the partitions again. Then the 5.1.1 bootloaders and the relevant partitions (those that changed) is overwritten by 5.0.1 copies, to see if that allows 5.0.1 to boot again. If not, at least those Fires are still under warranty.