[AT&T Samsung Galaxy Note I717] darkspr1te:
Hi RussianBear,

Yes this is a good article, and the basis behind my debrick solution, i just translated the solution over to a specific device along with removing some errors but yes this is the actual solution, it's just not relevant to 'our devices' , in my case the partition table was way off, partition0.xml was to hard to build to get right, bootloader and application cpu loaders/OS placement was off, but it's still the basics of the solution, anyclub.org also mentions the same works, but again the changes are to the partition table.

The key i've seen is first that the partition type is not relevant to the data it hold but more to it's purpose,

Example from my device

Device	Boot	Start	End	Blocks	Id	System	Partiton Name	File to restore from backup	file to restore from firmware
/dev/sdc1	1	204800	102400	c	W95 FAT32 (LBA)
/dev/sdc2	*	204801	205800	500	4d	QNX4.x	SBL1	sbl1.mbn
/dev/sdc3	205801	208800	1500	51	OnTrack DM6 Aux1	SBL2	sbl2.mbn
/dev/sdc4	208801	208801	0	5	Extended	EXT	ebr.mbn
/dev/sdc5	212992	213991	500	47	Unknown	RPM	rpm.mbn
/dev/sdc6	221184	225279	2048	45	Unknown	SBL3	sbl3.mbn
/dev/sdc7	229376	234375	2500	4c	Unknown	ABOOT	aboot.mbn
/dev/sdc8	237568	258047	10240	48	Unknown	BOOT	boot.img
/dev/sdc9	262144	263143	500	46	Unknown	TZ	tz.mbn
/dev/sdc10	270336	271335	500	5d	Unknown	SSD
/dev/sdc11	278528	279527	500	91	Unknown	PIT	Shv-e160l.pit
/dev/sdc12	286720	307199	10240	93	Amoeba	PARAM	param.lfs
/dev/sdc13	311296	511999	100352	c	W95 FAT32 (LBA)	MODEM	amms.bin
/dev/sdc14	516096	522239	3072	4a	Unknown	MSM_ST1	efs.img
/dev/sdc15	524288	530431	3072	4b	Unknown	MSM_ST2

so the first partition is marked as 'c' or windows, next is 4d then 51 and so on, partition 4 or the EBR partition is really just a fake partition that points to the next one, and the next and so on.

ive done some playing and it does change the way the system boots or not changing the partition type, I've not tested swapping partition locations (in relation to the first sector of the emmc device ) or retaining the partition type (so partition 3 of type 51 moves to the location of partition 6 of part type 45)

Now post http://rootzwiki.com/topic/25858-to...-this-for-unbricking/page__st__40#entry974018 is very relevant,

<Entry type="mbr" size="512" align="false"/>
<Entry type="space" partition="0xc" size="1024KB" reformat="false"/> <!-- p1, FAT (fat.bin) -->
<Entry type="space" partition="0x4d" size="500KB" reformat="false"/> <!-- p2, CFG_DATA; rpmsbl.mbn -->
<Entry type="space" partition="0x51" size="1500KB" reformat="false"/> <!-- p3, SPBL; spbl.mbn -->
<!-- Here begins the extended partitions (extended partition p4) -->
<Entry type="space" partition="0x47" size="500KB" reformat="false"/> <!-- p5, APPSSBL; rpm.mbn -->
<Entry type="space" partition="0x45" size="500KB" reformat="false"/> <!-- p6, QCSBL; ssbl.mbn -->
<Entry type="space" partition="0x4e" size="65024KB" reformat="false" optional="true"/> <!-- p7, EFS2 -->
<Entry type="space" partition="0x4c" size="2500KB" reformat="false"/> <!-- p8, FOTA; emmc_appsboot.mbn -->
<Entry type="bootloader" partition="0x48" size="10240KB" reformat="false"/> <!-- p9, APPS; boot.img -->
<Entry type="space" partition="0x46" size="500KB" reformat="false"/> <!-- p10, OEMSBL; tz.mbn -->
<Entry type="space" partition="0x4a" size="3072KB" reformat="false"/> <!-- p11, MODEM_ST1 -->
<Entry type="space" partition="0x4b" size="3072KB" reformat="false" optional="true"/> <!-- p12, MODEM_ST2 -->
<!-- Here is palm territory. There be dragons. -->

Areas of note,

4c = aboot on both devices,

47= rpm on both devices

so names may changes but operational characters dont, so rpm (part type 47) if the same on both the HP & shv-e160 (and A810L)

most of the other information is not relevant in the thread, besides the fact users talk about the 7x and 8x devices as if they operated the same, they don't.

I will only refer to msm8x60 solution here, pre3 and 7x users will have to try and translate across to their devices, anyclub.org has a lot of info but i want to cover only msm8x60 devices.

Molten, if you could be the go between for rootzwiki users and here that would be great, i really dont want to open another account at the moment.

Right, Onto solutions.

1. Do we have access to a working unit ?

2. do we have copies of any boot loaders (complete list is sbl1,sbl2,rpm,sbl3,tz and final is little kernel or aboot.mbn)

look forward to your input.

darkspr1te