[Moto G4 Plus Questions & Answers] MK+2017:
Thank you once again. The firmware MPJ24.139-48 that has links around did not help before. I tired it.

About the shop, I just went today for repair. While waiting, I felt I had to get a sneak look on the technicians monitor to see which tool he is using. Please, no laughing, I found him browsing XDA Forums for stock images :confused::eek::laugh:

I told him that I have been roaming here crazy for like a week. He asked when you know more than I do, why did you bring me the phone? I told him I thought he had a tool box :eek:

Anyway, since the place is smartphone mall, I asked at other shops. i found the best one, which had "many toolboxes" and promised to fix my phone. I left the phone with them. Still trying!

Now, in case all my efforts end fruitless, if I go for this idea:

1- buy a new phone of the same model, from the same shop where I bought my first.

2- Unlock bootloader.

3- Boot TWRP on the fly (without flashing)

4- dd every single partition on the phone.

5- copy dd images to PC.

6- get my IMEI-dead set and... you see the picture!

Questions:

1- Would that work first place?

2- If it works, would the 2 sets be sharing the same dual IMEIs?

3- Apart from IMEI, which partitions do I really need/need not to flash to get away with this?

All comments are welcome!

---------- Post added at 10:44 PM ---------- Previous post was at 10:32 PM ----------

This might help with the cloning idea!

Original partition listing of *my* working XT1642:

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 DDR -> /dev/block/mmcblk0p15

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 aboot -> /dev/block/mmcblk0p18

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 abootbak -> /dev/block/mmcblk0p19

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 boot -> /dev/block/mmcblk0p28

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cache -> /dev/block/mmcblk0p46

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cid -> /dev/block/mmcblk0p23

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 clogo -> /dev/block/mmcblk0p25

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 cmnlib -> /dev/block/mmcblk0p38

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 config -> /dev/block/mmcblk0p32

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 customize -> /dev/block/mmcblk0p44

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 devcfg -> /dev/block/mmcblk0p35

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 dip -> /dev/block/mmcblk0p36

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 dsp -> /dev/block/mmcblk0p12

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 frp -> /dev/block/mmcblk0p40

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 fsc -> /dev/block/mmcblk0p2

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 fsg -> /dev/block/mmcblk0p16

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hw -> /dev/block/mmcblk0p43

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hyp -> /dev/block/mmcblk0p10

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 hypbak -> /dev/block/mmcblk0p11

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 keymaster -> /dev/block/mmcblk0p39

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 kpan -> /dev/block/mmcblk0p27

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 limits -> /dev/block/mmcblk0p33

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 logo -> /dev/block/mmcblk0p24

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 logs -> /dev/block/mmcblk0p20

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 metadata -> /dev/block/mmcblk0p26

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 misc -> /dev/block/mmcblk0p31

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 modemst1 -> /dev/block/mmcblk0p13

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 modemst2 -> /dev/block/mmcblk0p14

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 mota -> /dev/block/mmcblk0p34

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 oem -> /dev/block/mmcblk0p45

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 padC -> /dev/block/mmcblk0p41

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 persist -> /dev/block/mmcblk0p30

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 recovery -> /dev/block/mmcblk0p29

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 rpmbak -> /dev/block/mmcblk0p7

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 sbl1 -> /dev/block/mmcblk0p4

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 sbl1bak -> /dev/block/mmcblk0p5

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 sec -> /dev/block/mmcblk0p17

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 sp -> /dev/block/mmcblk0p42

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 ssd -> /dev/block/mmcblk0p3

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 syscfg -> /dev/block/mmcblk0p37

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 system -> /dev/block/mmcblk0p47

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx 1 root root 20 1970-01-17 09:44 tzbak -> /dev/block/mmcblk0p9

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 userdata -> /dev/block/mmcblk0p48

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 utags -> /dev/block/mmcblk0p21

lrwxrwxrwx 1 root root 21 1970-01-17 09:44 utagsBackup -> /dev/block/mmcblk0p22

And, now I notice something from the TWRP backup log (attached, the backup that I took before messing up all things up, which had only bootloader unlocked, TWRP flashed and LineageOS installed and running):

- TWRP is naming the MODEM partition FIRMWARE. Does this have any possible side effects?

- I do not have the set now since I left it at repair shop, but I think I recall seeing a new FIRMWARE partition when I list partitions, one that did not exist before as outlined above?