[YU Yureka Q&A, Help & Troubleshooting] tirta.agung:
Welcome darkspr1te

OMG, darkspr1te is in the thread. So quakze, this is a serious project after all.

Hi darkspr1te, it seems that Qualcomm has changed the "9006" and "9008" mode. Please see the pictures below, they are taken from Windows' "setupapi.dev.log", and you will notice that "9006" mode are gone (sorry for mentioning the word windows:p):

Qualcomm also introduces a new "mbn" file called prog_emmc_firehose_XXXX.mbn (as well as a new tool called "QFIL"), and upon some hex comparison between the firehose*.mbn and mprg*.mbn, I found some interesting differences as pictured from the images below (you can download YU's "prog_emmc_firehose_8936.mbn" from HERE, remove the ".txt" from the file name):

1. Hex taken from "MPRG8916.mbn" and you can donwload it HERE (remove the ".txt" from the file name).

2. Hex taken from "prog_emmc_firehose_8916.mbn" and you can donwload it HERE (remove the ".txt" from the file name).

By the way, our phone doesn't use MBR but GPT, and you can download the dumped "gpt_main0.bin" and "gpt_backup0.bin" from my old fried YU Yureka HERE. And below is YU's partition layout:

1. ls -al /dev/block/bootdevice/by-name/

lrwxrwxrwx root root 1970-01-01 15:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-01 15:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-01 15:00 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-01 15:00 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-01 15:00 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-01 15:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-01 15:00 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-01 15:00 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-01 15:00 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-01 15:00 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-01 15:00 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-01 15:00 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-01 15:00 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-01 15:00 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-01 15:00 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-01 15:00 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-01 15:00 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-01 15:00 DDR -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-01 15:00 fsg -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-01 15:00 sec -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-01 15:00 boot -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-01 15:00 params -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-01 15:00 panic -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-01 15:00 autobak -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-01 15:00 system -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-01 15:00 persist -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-01 15:00 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-01 15:00 recovery -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-01 15:00 userdata -> /dev/block/mmcblk0p29

2. Using "partx"

NR START END SECTORS SIZE NAME UUID
1 65536 196607 131072 64M modem 4a42fcff-dfa8-2176-fbf4-0220e3bafe00
2 196608 197631 1024 512K sbl1 6f5a4b29-8f73-28fa-5fbe-d55fe00e7e15
3 197632 198655 1024 512K sbl1bak 3f2a85a7-15e2-e31c-4635-42d9822e0c92
4 198656 229375 30720 15M aboot 7d00faa0-b6e1-81b3-bcaa-bb0fc3fce2e8
5 229376 260095 30720 15M abootbak 4b124653-bb2c-fddc-7a29-17ac4c5fa51b
6 260096 261119 1024 512K rpm df4eb777-76f1-6e1e-29e0-cd895287fc5c
7 261120 262143 1024 512K rpmbak 00f2e67b-f3b4-ff9b-115f-978f44a496e5
8 262144 263167 1024 512K tz 386a6ae9-28b3-6cc7-ff61-cc4b42268e33
9 263168 264191 1024 512K tzbak 8e588f8a-9752-a93f-98f2-96b1d9e0b4fe
10 264192 265215 1024 512K hyp fb6ab6d7-cd88-b358-7a25-77e8cc84bdf5
11 265216 266239 1024 512K hypbak 9b91d4cd-74c3-efcb-a08f-6a35a915ff6f
12 266240 268287 2048 1M pad 9835bf5b-11a2-d295-b0c4-6fb55908559e
13 268288 271359 3072 1.5M modemst1 e38a07db-534d-98b1-65b8-75377f75551c
14 271360 274431 3072 1.5M modemst2 b112718b-0665-fb44-c321-fa7e48628b12
15 274432 276479 2048 1M misc ab905f34-a0d9-b60b-208a-dcd802cb3f6a
16 276480 276481 2 1K fsc 97324915-732c-a60f-8f14-f033ebba0d2a
17 276482 276497 16 8K ssd 05d74d6d-267f-b046-d5d2-485b3b8753e4
18 327680 327743 64 32K DDR 41e6142e-5eeb-3362-43c4-c0a32843d64e
19 327744 330815 3072 1.5M fsg 6cc1c313-3ef9-0ab7-abef-59834122a056
20 330816 330847 32 16K sec c9c9e248-33cc-8a8d-d8b4-dea2e4cbd100
21 330848 371807 40960 20M boot aa1e9358-b507-773b-aee1-efc10e6483fb
22 393216 395263 2048 1M params dc8c03e3-6922-c976-a24c-3f02304b945c
23 395264 436223 40960 20M panic 86a9e723-1110-44a0-0a03-d782311b8bf8
24 436224 456703 20480 10M autobak 9292b0c0-9973-5195-69ed-4f20b979b073
25 458752 2916351 2457600 1.2G system 85485b97-47ea-eff4-2e0d-03c86ba45f54
26 2916352 2936831 20480 10M persist f8962f2a-7dcd-ae5e-b125-db5ac982a946
27 2936832 3198975 262144 128M cache 1415a7f7-b65c-bf73-60e7-f59ff8197c97
28 3198976 3239935 40960 20M recovery 12063475-2c6b-fde1-7a80-6d6926398e71
29 3239936 30785502 27545567 13.1G userdata 20cfe83d-98a8-1b5c-20b0-571480403801

Notice that now Qualcomm make "bak" partitions on its most important partitions, "sbl1", "aboot", "rpm", "tz", and "hyp", and I don't know what those partitions are for. However, through a hex reading on those "bak" partitions, I found out that they really resemble their sibling partitions (for instance "hypbak" has the same hex code with "hyp"). The complete "partition.xml" could be downloaded from HERE (remove the ".txt" from the file name).

Furthermore, the new *msimage.mbn only contain "sbl1", "rpm", "DDR", and "tz" as pictured from the image below (you can download YU's 8936_msimage.mbn from HERE):

So any suggestion on what to do next? I mean of course in Linux (I use ubuntu).