Hi,
i've checked out the partition list of my watch, using adb and parted.
Code:
D:\Handy\LG_G_Watch\ota>cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.
D:\Handy\LG_G_Watch\ota>adb shell cat /proc/partitions
major minor #blocks name
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 512 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 2048 mmcblk0p10
179 11 512 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 22528 mmcblk0p14
179 15 22528 mmcblk0p15
179 16 22528 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 262144 mmcblk0p19
179 20 262144 mmcblk0p20
179 21 3182592 mmcblk0p21
179 22 495 mmcblk0p22
179 32 4096 mmcblk0rpmb
D:\Handy\LG_G_Watch\ota>
[email protected]:/ # ls /dev/block/platform/msm_sdcc.1/by-name
ls /dev/block/platform/msm_sdcc.1/by-name
DDR
aboot
abootb
boot
cache
grow
imgdata
laf
metadata
misc
persist
recovery
rpm
rpmb
sbl1
sbl1b
sdi
ssd
system
tz
tzb
userdata
Model: MMC H4G1d♦ (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 524kB 1573kB 1049kB sbl1
2 1573kB 2097kB 524kB rpm
3 2097kB 2621kB 524kB tz
4 2621kB 3146kB 524kB sdi
5 3146kB 3670kB 524kB aboot
6 3670kB 4719kB 1049kB sbl1b
7 4719kB 5243kB 524kB rpmb
8 5243kB 5767kB 524kB tzb
9 5767kB 6291kB 524kB abootb
10 6291kB 8389kB 2097kB imgdata
11 8389kB 8913kB 524kB metadata
12 8913kB 25.7MB 16.8MB misc
13 25.7MB 42.5MB 16.8MB ext4 persist
14 42.5MB 65.5MB 23.1MB laf
15 65.5MB 88.6MB 23.1MB boot
16 88.6MB 112MB 23.1MB recovery
17 112MB 112MB 524kB ssd
18 112MB 113MB 524kB DDR
19 113MB 381MB 268MB ext4 system
20 381MB 650MB 268MB ext4 cache
21 650MB 3909MB 3259MB ext4 userdata
22 3909MB 3909MB 507kB grow
(parted)
regards
starbase64
How exactly do I interpret this now? Do the numbers on the first block correspond to the numbers on the third one? So, as example, boot is mmcblk0p15?
When I look inside /dev/block, I see a lot of partitions on mmcblk0 (and I have confirmed, just to be certain, the combined size of all partitions almost exactly equals the size of mmcblk0 on its own):
Code:
~ # ls mmcblk0*
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p13
mmcblk0p14
mmcblk0p15
mmcblk0p16
mmcblk0p17
mmcblk0p18
mmcblk0p19
mmcblk0p2
mmcblk0p20
mmcblk0p21
mmcblk0p22
mmcblk0p23
mmcblk0p24
mmcblk0p25
mmcblk0p26
mmcblk0p27
mmcblk0p28
mmcblk0p29
mmcblk0p3
mmcblk0p30
mmcblk0p31
mmcblk0p32
mmcblk0p33
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
What is even more bizarre is I get even more partitions listed when I use fdisk:
Code:
~ # fdisk -l -u /dev/block/mmcblk0
Warning: deleting partitions after 60
Disk /dev/block/mmcblk0: 2432 MB, 2432696320 bytes
1 heads, 16 sectors/track, 296960 cylinders, total 4751360 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 1000 500 4d Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1001 1128 64 45 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 1129 10128 4500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 10129 4751358 2370615 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p6 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p7 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p8 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p9 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p10 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p11 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p12 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p13 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p14 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p15 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p16 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p17 163328 163839 256 76 Unknown
/dev/block/mmcblk0p18 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p19 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p20 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p21 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p22 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p23 196096 196607 256 73 Unknown
/dev/block/mmcblk0p24 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p25 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p26 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p27 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p28 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p29 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p30 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p31 4504944 4505085 71 90 Unknown
/dev/block/mmcblk0p32 4505087 4505598 256 23 Unknown
/dev/block/mmcblk0p33 4505600 4702191 98296 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p34 10130 70129 30000 49 Unknown
/dev/block/mmcblk0p35 70131 95130 12500 50 Unknown
/dev/block/mmcblk0p36 95132 99227 2048 51 Unknown
/dev/block/mmcblk0p37 99229 105372 3072 52 Unknown
/dev/block/mmcblk0p38 105374 109469 2048 53 Unknown
/dev/block/mmcblk0p39 109471 111518 1024 54 Unknown
/dev/block/mmcblk0p40 111520 113567 1024 56 Unknown
/dev/block/mmcblk0p41 113569 131071 8751+ 55 Unknown
/dev/block/mmcblk0p42 131073 139264 4096 4a Unknown
/dev/block/mmcblk0p43 139266 147457 4096 4b Unknown
/dev/block/mmcblk0p44 147459 149506 1024 74 Unknown
/dev/block/mmcblk0p45 149508 163326 6909+ 75 Unknown
/dev/block/mmcblk0p46 163328 163839 256 76 Unknown
/dev/block/mmcblk0p47 163841 165888 1024 47 Unknown
/dev/block/mmcblk0p48 165890 167937 1024 34 Unknown
/dev/block/mmcblk0p49 167939 170498 1280 36 Unknown
/dev/block/mmcblk0p50 170500 187901 8701 71 Unknown
/dev/block/mmcblk0p51 187903 196094 4096 48 Unknown
/dev/block/mmcblk0p52 196096 196607 256 73 Unknown
/dev/block/mmcblk0p53 196609 200702 2047 26 Unknown
/dev/block/mmcblk0p54 200704 1835006 817151+ 83 Linux
/dev/block/mmcblk0p55 1835008 3833854 999423+ 83 Linux
/dev/block/mmcblk0p56 3833856 4095998 131071+ 83 Linux
/dev/block/mmcblk0p57 4096000 4452350 178175+ 83 Linux
/dev/block/mmcblk0p58 4452352 4456446 2047+ 33 Unknown
/dev/block/mmcblk0p59 4456448 4504942 24247+ 19 Unknown
/dev/block/mmcblk0p60 4504944 4505085 71 90 Unknown
Partition table entries are not in disk order
The thing is, those extra partitions don't seem to be in use. Running mount only lists the following partitions as mounted somewhere (irrelevant mounts excluded from the output)
Code:
/dev/block/mmcblk0p25 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p26 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
What are all these extra partitions for?
Is this specific to my particular device (HTC One V, with firmware for Cricket Wireless), or do all Android devices have this sheer number partitions?
Hello XDA!
I'm on a quest to unbrick a Coolpad Catalyst 3622a. I'm going to list what I have compiled to aide me with a question at the end.
My phone is currently in QDLoader 9008 mode. Dead as dead can get.
Correct me if I am wrong here but I need to get the phone into QDLoader 9006 mode to accomplish a flash.
What I have compiled is a rom dump of a working Coolpad Catalyst 3622a.
Code:
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tz
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tzbak
-rw-rw-rw- 1 don 0 1825361920 2017-01-12 21:00 system
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpm
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpmbak
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1bak
-rw-rw-rw- 1 don 0 16384 2017-01-12 20:57 sec
-rw-rw-rw- 1 don 0 8192 2017-01-12 20:57 ssd
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:57 recovery
-rw-rw-rw- 1 don 0 33554432 2017-01-12 20:57 persist
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 params
-rw-rw-rw- 1 don 0 20971520 2017-01-12 20:57 panic
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst2
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 oem
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 pad
-rw-rw-rw- 1 don 0 67108864 2017-01-12 20:57 modem
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst1
-rw-rw-rw- 1 don 0 1024 2017-01-12 20:57 fsc
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 fsg
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 keystore
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 misc
-rw-rw-rw- 1 don 0 268435456 2017-01-12 20:57 cache
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 config
-rw-rw-rw- 1 don 0 32768 2017-01-12 20:57 DDR
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 devinfo
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:56 boot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 aboot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 abootbak
I have also obtained the partition.xml which I also think is needed.
Code:
Model: MMC FN12MB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 542kB 524kB sbl1
2 542kB 1066kB 524kB sbl1bak
3 1066kB 4212kB 3146kB aboot
4 4212kB 7357kB 3146kB abootbak
5 7357kB 7882kB 524kB rpm
6 7882kB 8406kB 524kB rpmbak
7 8406kB 8930kB 524kB tz
8 8930kB 9455kB 524kB tzbak
9 9455kB 10.5MB 1049kB pad
10 10.5MB 12.1MB 1573kB modemst1
11 12.1MB 13.6MB 1573kB modemst2
12 13.6MB 14.7MB 1049kB misc
13 14.7MB 15.7MB 1049kB params
14 15.7MB 36.7MB 21.0MB ext4 panic
15 36.7MB 36.7MB 1024B fsc
16 36.7MB 36.7MB 8192B ssd
17 36.7MB 37.3MB 524kB keystore
18 37.3MB 37.8MB 524kB config
19 37.8MB 38.8MB 1049kB oem
20 41.9MB 109MB 67.1MB fat16 modem
21 109MB 110MB 1049kB devinfo
22 110MB 110MB 32.8kB DDR
23 110MB 112MB 1573kB fsg
24 112MB 128MB 16.8MB boot
25 128MB 128MB 16.4kB sec
26 128MB 1954MB 1825MB ext4 system
27 1954MB 1987MB 33.6MB ext4 persist
28 1987MB 2256MB 268MB ext4 cache
29 2256MB 2273MB 16.8MB recovery
30 2273MB 7818MB 5546MB ext4 userdata
From reading over the past few days. I have come to the proverbial road block.
1: Use PartitioningTool.py in conjunction with Partition.xml to output rawprogram0.xml as well as patch0.xml.
I have obtained and installed python27. The python executable is system wide.
I'm not 100% sure about what arguments or the command line itself to issue to python in order to produce: rawprogram0.xml and patch0.xml.
I thought it was as simple as passing something like this: python PartitioningTool.py Partition.xml.
If somebody could help me here it would be very much appreciated.
Then I know I have to use emmcldl and partiton.xml to produce the file 8909_msimage.mbn. After words with a lot of luck I use QPST to get the device into QDLoader 9006 mode.
Hopefully then I will be able to flash.
Thanks for reading!
coolpad 3622a revived from the dead....
thanks for the help?
I'm about stuck on this same phone. I flashed a homemade twrp onto the phone, and bricked it pretty good in the process. First (!!!) time around, it would go into the recovery however touch didnt work. Second time around killed it. Now phone turns on, goes to the recovery for about 5 seconds, then drops to QLoad 9008 or whatever. I have the prog_emmc_firehose_8909_ddr.mbn file for emmcdl or QFil, however something is strange with this phone. I believe its a non-standard msm8909 or something. I tried making the 8909_msimage.mbn file, however that was kinda pointless because I dont have a programmer hex file to go with it... Any clues as to what to do any1?
Help
I have a coolpad 3622a in good condition and I want to make a backup to help several who are with their catalyst in bad condition as would make that box or program
regards
kinehumane said:
Hello XDA!
I'm on a quest to unbrick a Coolpad Catalyst 3622a. I'm going to list what I have compiled to aide me with a question at the end.
My phone is currently in QDLoader 9008 mode. Dead as dead can get.
Correct me if I am wrong here but I need to get the phone into QDLoader 9006 mode to accomplish a flash.
What I have compiled is a rom dump of a working Coolpad Catalyst 3622a.
Code:
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tz
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tzbak
-rw-rw-rw- 1 don 0 1825361920 2017-01-12 21:00 system
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpm
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpmbak
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1bak
-rw-rw-rw- 1 don 0 16384 2017-01-12 20:57 sec
-rw-rw-rw- 1 don 0 8192 2017-01-12 20:57 ssd
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:57 recovery
-rw-rw-rw- 1 don 0 33554432 2017-01-12 20:57 persist
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 params
-rw-rw-rw- 1 don 0 20971520 2017-01-12 20:57 panic
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst2
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 oem
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 pad
-rw-rw-rw- 1 don 0 67108864 2017-01-12 20:57 modem
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst1
-rw-rw-rw- 1 don 0 1024 2017-01-12 20:57 fsc
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 fsg
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 keystore
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 misc
-rw-rw-rw- 1 don 0 268435456 2017-01-12 20:57 cache
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 config
-rw-rw-rw- 1 don 0 32768 2017-01-12 20:57 DDR
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 devinfo
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:56 boot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 aboot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 abootbak
I have also obtained the partition.xml which I also think is needed.
Code:
Model: MMC FN12MB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 542kB 524kB sbl1
2 542kB 1066kB 524kB sbl1bak
3 1066kB 4212kB 3146kB aboot
4 4212kB 7357kB 3146kB abootbak
5 7357kB 7882kB 524kB rpm
6 7882kB 8406kB 524kB rpmbak
7 8406kB 8930kB 524kB tz
8 8930kB 9455kB 524kB tzbak
9 9455kB 10.5MB 1049kB pad
10 10.5MB 12.1MB 1573kB modemst1
11 12.1MB 13.6MB 1573kB modemst2
12 13.6MB 14.7MB 1049kB misc
13 14.7MB 15.7MB 1049kB params
14 15.7MB 36.7MB 21.0MB ext4 panic
15 36.7MB 36.7MB 1024B fsc
16 36.7MB 36.7MB 8192B ssd
17 36.7MB 37.3MB 524kB keystore
18 37.3MB 37.8MB 524kB config
19 37.8MB 38.8MB 1049kB oem
20 41.9MB 109MB 67.1MB fat16 modem
21 109MB 110MB 1049kB devinfo
22 110MB 110MB 32.8kB DDR
23 110MB 112MB 1573kB fsg
24 112MB 128MB 16.8MB boot
25 128MB 128MB 16.4kB sec
26 128MB 1954MB 1825MB ext4 system
27 1954MB 1987MB 33.6MB ext4 persist
28 1987MB 2256MB 268MB ext4 cache
29 2256MB 2273MB 16.8MB recovery
30 2273MB 7818MB 5546MB ext4 userdata
From reading over the past few days. I have come to the proverbial road block.
1: Use PartitioningTool.py in conjunction with Partition.xml to output rawprogram0.xml as well as patch0.xml.
I have obtained and installed python27. The python executable is system wide.
I'm not 100% sure about what arguments or the command line itself to issue to python in order to produce: rawprogram0.xml and patch0.xml.
I thought it was as simple as passing something like this: python PartitioningTool.py Partition.xml.
If somebody could help me here it would be very much appreciated.
Then I know I have to use emmcldl and partiton.xml to produce the file 8909_msimage.mbn. After words with a lot of luck I use QPST to get the device into QDLoader 9006 mode.
Hopefully then I will be able to flash.
Thanks for reading!
coolpad 3622a revived from the dead....
thanks for the help?
Click to expand...
Click to collapse
Are you able to unbrick it?
3622a Dump files
Hey all,
I'm new to the forum but not new to the tinkering if you know what I mean. So I have a brand new 3622a with good working ROM and I was able to Root with no problem. I then installed a partition managing app (needs root access to work) and was able to copy all the partitions (with the files) from the 3622a.
Using an extractor tool, I can open the backup partition copies and extract all the files like the recovery.img, etc... If CWM or TWRP could install on a 3622a, we would be in the game. For we could flash the 3622a using just the recovery.img and help some softbricks come back to life. I also have a softbrick 3622a that I am trying to fix, just for fun. I like a challenge. I can get into the recovery option with no problem. We was playing with the device just trying to see what we could do with it before we bricked it. Once in the device, it's pretty much open and pretty straight forward when it comes to low end Chinese Android devices. Nothing new here. So this should be an easy one to fix.
There are a few directions we could take on this. One, is to work on the CWM or TWRP custom recovery tool development for the 3622a. For with these programs, we could flash our own custom ROM and not have to worry about certificate checks, etc...
Two, try to rebuild a stock recovery from all the files we know we have, and hope we can compile it together in an authorized update.zip file that would work even with the basic ABD sideload option. This file must pass the proper cert checks in order for the sideloader to continue with the install.
I've been trying to make cert compliance update.zip files and have tried installing them through the sideloader and by using the option to install from SD Card. I even found the files META-INF, the CERT.RSA, CERT.SF, etc... And have created several update.zip files that currently don't work. All fail the CERT checks.
I'm willing to help as much as I can. We need to form a group that can work on this. I'm willing. We need to find the best approach to this. We have all the pieces except one. We just can't reinstall what we have yet. Not sure if it would be better to work on creating a workable stock ROM or would it be better to work on the CWM or TWRP development for the 3622a.
I'll put all the files and backup partitions I currently have in a dropbox and share it with the group. This is an easy one. I had more of a challenge with Samsung phones and Knox. I was able to crack most of those firmware's too. Let me know.
So I am new to this site has anyone come up with a solution yet? Can anyone send me any of the files that they already have.
I have two of these phones. One is soft bricked\stuck on startup animation thanks to kingroot, the other is qdload bricked after flashing a homebrew twrp recovery. The soft bricked one can go into recovery, plus while its attempting to boot it enables a usb interface with the hardware id of USB\VID_1EBF&PID_707D&REV_0310. Urm anyhow, I am 99.9% sure this phone can be debricked using the qualcomm sd card method. Just for kicks I tried booting the qdload phone with a samsung debrick sd card, and it WANTS to work however the locked bootloader prevents it from loading. I have most all of the partitions backed up from the soft bricked phone.. If I could get my hands on a complete system image I could almost assuredly fix the qdload phone. If someone has a complete image, hook a brother up!
Anybody still working on this?
I have my phone in a stuck condition I had the same coolpad catalyst 3622a it's stuck on the metropcs screen when trying to start I had it rooted no problem but tried installing a different SU app and now its stuck please help with this and thanks for all your good work so far
This thread need some attention
please say y'all are still pursuing this quest I really would love my phone to work again if anybody still working on it or already has a solution please post a reply sorry for bugging you guys
Coolpad 3622a
kinehumane said:
Hello XDA!
I'm on a quest to unbrick a Coolpad Catalyst 3622a. I'm going to list what I have compiled to aide me with a question at the end.
My phone is currently in QDLoader 9008 mode. Dead as dead can get.
Correct me if I am wrong here but I need to get the phone into QDLoader 9006 mode to accomplish a flash.
What I have compiled is a rom dump of a working Coolpad Catalyst 3622a.
Code:
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tz
-rw-rw-rw- 1 don 0 524288 2017-01-12 21:00 tzbak
-rw-rw-rw- 1 don 0 1825361920 2017-01-12 21:00 system
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpm
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 rpmbak
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 sbl1bak
-rw-rw-rw- 1 don 0 16384 2017-01-12 20:57 sec
-rw-rw-rw- 1 don 0 8192 2017-01-12 20:57 ssd
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:57 recovery
-rw-rw-rw- 1 don 0 33554432 2017-01-12 20:57 persist
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 params
-rw-rw-rw- 1 don 0 20971520 2017-01-12 20:57 panic
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst2
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 oem
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 pad
-rw-rw-rw- 1 don 0 67108864 2017-01-12 20:57 modem
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 modemst1
-rw-rw-rw- 1 don 0 1024 2017-01-12 20:57 fsc
-rw-rw-rw- 1 don 0 1572864 2017-01-12 20:57 fsg
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 keystore
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 misc
-rw-rw-rw- 1 don 0 268435456 2017-01-12 20:57 cache
-rw-rw-rw- 1 don 0 524288 2017-01-12 20:57 config
-rw-rw-rw- 1 don 0 32768 2017-01-12 20:57 DDR
-rw-rw-rw- 1 don 0 1048576 2017-01-12 20:57 devinfo
-rw-rw-rw- 1 don 0 16777216 2017-01-12 20:56 boot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 aboot
-rw-rw-rw- 1 don 0 3145728 2017-01-12 20:56 abootbak
I have also obtained the partition.xml which I also think is needed.
Code:
Model: MMC FN12MB (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 542kB 524kB sbl1
2 542kB 1066kB 524kB sbl1bak
3 1066kB 4212kB 3146kB aboot
4 4212kB 7357kB 3146kB abootbak
5 7357kB 7882kB 524kB rpm
6 7882kB 8406kB 524kB rpmbak
7 8406kB 8930kB 524kB tz
8 8930kB 9455kB 524kB tzbak
9 9455kB 10.5MB 1049kB pad
10 10.5MB 12.1MB 1573kB modemst1
11 12.1MB 13.6MB 1573kB modemst2
12 13.6MB 14.7MB 1049kB misc
13 14.7MB 15.7MB 1049kB params
14 15.7MB 36.7MB 21.0MB ext4 panic
15 36.7MB 36.7MB 1024B fsc
16 36.7MB 36.7MB 8192B ssd
17 36.7MB 37.3MB 524kB keystore
18 37.3MB 37.8MB 524kB config
19 37.8MB 38.8MB 1049kB oem
20 41.9MB 109MB 67.1MB fat16 modem
21 109MB 110MB 1049kB devinfo
22 110MB 110MB 32.8kB DDR
23 110MB 112MB 1573kB fsg
24 112MB 128MB 16.8MB boot
25 128MB 128MB 16.4kB sec
26 128MB 1954MB 1825MB ext4 system
27 1954MB 1987MB 33.6MB ext4 persist
28 1987MB 2256MB 268MB ext4 cache
29 2256MB 2273MB 16.8MB recovery
30 2273MB 7818MB 5546MB ext4 userdata
From reading over the past few days. I have come to the proverbial road block.
1: Use PartitioningTool.py in conjunction with Partition.xml to output rawprogram0.xml as well as patch0.xml.
I have obtained and installed python27. The python executable is system wide.
I'm not 100% sure about what arguments or the command line itself to issue to python in order to produce: rawprogram0.xml and patch0.xml.
I thought it was as simple as passing something like this: python PartitioningTool.py Partition.xml.
If somebody could help me here it would be very much appreciated.
Then I know I have to use emmcldl and partiton.xml to produce the file 8909_msimage.mbn. After words with a lot of luck I use QPST to get the device into QDLoader 9006 mode.
Hopefully then I will be able to flash.
Thanks for reading!
coolpad 3622a revived from the dead....
thanks for the help?
Click to expand...
Click to collapse
Can you zip your dump file or whatever you used to fix your Coolpad please. And post a link please you would make me and alot of people happy.. thank you.
It would be great indeed, i have one device is stuck on bootscreen after rooting
Did you unlock the BL?
Oh this device needs to open the bootloader didn't knew that.
You have a Coolpad 3622a complete firmware on Dropbox for everyone to use, yet I can't find the link anywhere, unless I missed it?
if you end up creating an update.zip file or custom recovery or even just the image file, email it to me [email protected] please....very much appreciated.. i have a catalyst that i rooted with kingoroot then accidentally updated the firmware...soft bricking it. i have no idea how to recover it without custom recovery or a stock rom . please help !
hey guys here its a software to unbrick the coolpad 3622a metro pcs, credits to the creator. https://drive.google.com/file/d/0Byi69Jpw2ZDtWEpNVm1UUjI3X2s/view
Ok, so after quite literally months of searching, I believed I had found a working 3622a rom. Twas on a spanish forum, and claimed to be a coolpad catalyst 3622a metro pcs rom. And to be honest, it LOOKS like it would work. Its a marshmallow based rom, definitely for a 8909 based handset... Check it out: h**ps://drive.google.com/file/d/0Byi69Jpw2ZDtWEpNVm1UUjI3X2s/view
dOh didnt see above post
Its looking like the above mentioned rom probably isnt the answer we are seeking. I brought over the above roms' sbl1, aboot, rpm and tz to my unbrick image, and the bootloader pukes on it. Back to the drawing board.
If anyone would like to mess around with emmcdl and a 8909 singleimage file, they are attached to this post. I was able to initialize the emmc with this singleimage... Give her a whirl maybe you'll get lucky. =)
This may or may not be of any assistance to hard bricked catalyst owners... You can get into fastboot on these devices by pulling the battery, holding down volume up, then plugging the device into USB with volume up still held in. It seems as though these phones ship with an overly crippled fastboot however...
Hello experts,
Need help,
I have one android phone with a eMMc chip, It is stuck in bootlogo.
I can enter into bootloader, so I did
Then I booted in twrp tru
fastboot boot twrp.img
Now I checked the disk partition table thru fdisk /dev/block/mmcblk0
The print command gives me output
Command (m for help): [6np
Disk /dev/block/mmcblk0: 30785536 sectors, 2744M
Logical sector size: 512
Disk identifier (GUID): 98101b32-bbe2-4bf2-a06e-2bb33d000c20
Partition table holds up to 28 entries
First usable sector is 34, last usable sector is 30785502
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0M 0700 modem
2 262144 262145 1024 0700 fsc
3 262146 262161 8192 0700 ssd
4 262162 263185 512K 0700 sbl1
5 263186 264209 512K 0700 sbl1bak
6 264210 265233 512K 0700 rpm
7 265234 266257 512K 0700 rpmbak
8 266258 267281 512K 0700 tz
9 267282 268305 512K 0700 tzbak
10 268306 269329 512K 0700 hyp
11 269330 270353 512K 0700 hypbak
12 270354 273425 1536K 0700 modemst1
13 273426 276497 1536K 0700 modemst2
14 276498 296977 10.0M 0700 splash
15 393216 393279 32768 0700 DDR
16 393280 396351 1536K 0700 fsg
17 396352 396383 16384 0700 sec
18 396384 398431 1024K 0700 aboot
19 398432 400479 1024K 0700 abootbak
20 400480 466015 32.0M 0700 boot
21 466016 531551 32.0M 0700 recovery
22 531552 4725855 2048M 0700 system
23 4849664 4980735 64.0M 0700 cache
24 4980736 5046271 32.0M 0700 persist
25 5046272 5048319 1024K 0700 misc
26 5048320 5049343 512K 0700 keystore
27 5049344 5050367 512K 0700 config
28 5050368 30785502 12.2G 0700 userdata
Command (m for help): [6n[Jm
However,
I have checked the same in a same model phone in all working condition, there it is
Number Start (sector) End (sector) Size Code Name
1 131072 262143 64.0 MiB 0700 modem
2 262144 262145 1024 bytes FFFF fsc
3 262146 262161 8.0 KiB FFFF ssd
4 262162 263185 512.0 KiB FFFF sbl1
5 263186 264209 512.0 KiB 0700 sbl1bak
6 264210 265233 512.0 KiB FFFF rpm
7 265234 266257 512.0 KiB 0700 rpmbak
8 266258 267281 512.0 KiB FFFF tz
9 267282 268305 512.0 KiB 0700 tzbak
10 268306 269329 512.0 KiB FFFF hyp
11 269330 270353 512.0 KiB 0700 hypbak
12 270354 273425 1.5 MiB FFFF modemst1
13 273426 276497 1.5 MiB FFFF modemst2
14 276498 296977 10.0 MiB FFFF splash
15 393216 393279 32.0 KiB FFFF DDR
16 393280 396351 1.5 MiB FFFF fsg
17 396352 396383 16.0 KiB FFFF sec
18 396384 398431 1024.0 KiB FFFF aboot
19 398432 400479 1024.0 KiB 0700 abootbak
20 400480 466015 32.0 MiB FFFF boot
21 466016 531551 32.0 MiB FFFF recovery
22 531552 4725855 2.0 GiB FFFF system
23 4849664 4980735 64.0 MiB FFFF cache
24 4980736 5046271 32.0 MiB FFFF persist
25 5046272 5048319 1024.0 KiB FFFF misc
26 5048320 5049343 512.0 KiB FFFF keystore
27 5049344 5050367 512.0 KiB FFFF config
28 5050368 30785502 12.3 GiB FFFF userdata
The only difference is,
Partition code, mine is 0700 in all partiions,
but in the working phone it is, 0700 or FFFF.
Rest all are same.
I cant mount /system, /data etc.
Deleting/reformatting partition in parted not working.
Can anybody explain the meaning of partition code ??
I searched in googled but could not find.
Which code means what ?? 0700 & FFFF.
What is the difference when code is changed ?
How to repartition ??
Hello there!
On clean Havoc 2.8 install, in storage i has 12GB under system!
Like instruction here https://forum.xda-developers.com/nexus-4/general/guide-increase-nexus-4s-partition-space-t3800264 i try to look at partition on device.
clover:/ # ./parted /dev/block/mmcblk0 p
Model: MMC DH6DAB (sd/mmc)
Disk /dev/block/mmcblk0: 62.5GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67.1MB 70.8MB 3670kB xbl
2 70.8MB 74.4MB 3670kB xblbak
3 74.4MB 78.6MB 4194kB tz
4 78.6MB 82.8MB 4194kB tzbak
5 82.8MB 83.4MB 524kB rpm
6 83.4MB 83.9MB 524kB rpmbak
7 83.9MB 84.4MB 524kB hyp
8 84.4MB 84.9MB 524kB hypbak
9 84.9MB 85.5MB 524kB pmic
10 85.5MB 86.0MB 524kB pmicbak
11 86.0MB 88.1MB 2097kB fsg
12 134MB 201MB 67.1MB boot
13 201MB 3423MB 3221MB ext2 system
14 3423MB 5570MB 2147MB ext2 vendor
15 5570MB 5571MB 1049kB keymaster
16 5571MB 5572MB 1049kB keymasterbak
17 5572MB 5573MB 1049kB cmnlib
18 5573MB 5574MB 1049kB cmnlib64
19 5574MB 5575MB 1049kB cmnlibbak
20 5575MB 5576MB 1049kB cmnlib64bak
21 5576MB 5581MB 4194kB mdtpsecapp
22 5581MB 5585MB 4194kB mdtpsecappbak
23 5585MB 5618MB 33.6MB mdtp
24 5618MB 5652MB 33.6MB mdtpbak
25 5652MB 5920MB 268MB fat16 modem
26 5920MB 6189MB 268MB fat16 modembak
27 6189MB 6205MB 16.8MB ext4 dsp
28 6205MB 6222MB 16.8MB ext4 dspbak
29 6222MB 6223MB 1049kB abl
30 6223MB 6224MB 1049kB ablbak
31 6224MB 6225MB 1049kB dip
32 6225MB 6225MB 4096B devinfo
33 6225MB 6226MB 262kB apdp
34 6226MB 6226MB 262kB msadp
35 6226MB 6226MB 1024B dpo
36 6226MB 6260MB 34.2MB splash
37 6260MB 6260MB 4096B limits
38 6260MB 6261MB 1049kB toolsfv
39 6308MB 6317MB 8389kB logfs
40 6375MB 6376MB 1049kB ddr
41 6376MB 6376MB 16.4kB sec
42 6376MB 6377MB 1049kB bluetooth
43 6377MB 6379MB 1049kB bluetoothbak
44 6442MB 6442MB 1024B fsc
45 6442MB 6442MB 8192B ssd
46 6442MB 6445MB 2097kB modemst1
47 6445MB 6447MB 2097kB modemst2
48 6447MB 6480MB 33.6MB ext4 persist
49 6480MB 6749MB 268MB ext4 cache
50 6749MB 6750MB 1049kB misc
51 6750MB 6817MB 67.1MB recovery
52 6817MB 6817MB 524kB keystore
53 6817MB 6818MB 1049kB devcfg
54 6818MB 6819MB 1049kB devcfgbak
55 6819MB 6820MB 524kB frp
56 6820MB 6887MB 67.1MB logdump
57 6887MB 6889MB 2097kB sti
58 6912MB 6912MB 131kB storsec
59 6979MB 7114MB 134MB rawdump
60 7114MB 7114MB 65.5kB vbmeta
61 7114MB 7114MB 65.5kB vbmetabak
62 7181MB 8053MB 872MB ext4 cust
63 8053MB 8087MB 34.2MB logo
64 8087MB 62.5GB 54.4GB userdata
Is there useless partitions, and can somebody help to resize it, maybe delete some and use more storage under sdcard? Or maybe all 12Gb is used?
This is the reported allocation on my device:
# fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 122142720 sectors, 2296M
Logical sector size: 512
Disk identifier (GUID): de1c6fbc-8d97-ad88-8aba-dd5af5595598
Partition table holds up to 64 entries
First usable sector is 34, last usable sector is 122142686
Number Start (sector) End (sector) Size Code Name
1 131072 138239 3584K 0700 xbl
2 138240 145407 3584K 0700 xblbak
3 145408 153599 4096K 0700 tz
4 153600 161791 4096K 0700 tzbak
5 161792 162815 512K 0700 rpm
6 162816 163839 512K 0700 rpmbak
7 163840 164863 512K 0700 hyp
8 164864 165887 512K 0700 hypbak
9 165888 166911 512K 0700 pmic
10 166912 167935 512K 0700 pmicbak
11 167936 172031 2048K 0700 fsg
12 262144 393215 64.0M 0700 boot
13 393216 6684671 3072M 0700 system
14 6684672 10878975 2048M 0700 vendor
15 10878976 10881023 1024K 0700 keymaster
16 10881024 10883071 1024K 0700 keymasterbak
17 10883072 10885119 1024K 0700 cmnlib
18 10885120 10887167 1024K 0700 cmnlib64
19 10887168 10889215 1024K 0700 cmnlibbak
20 10889216 10891263 1024K 0700 cmnlib64bak
21 10891264 10899455 4096K 0700 mdtpsecapp
22 10899456 10907647 4096K 0700 mdtpsecappbak
23 10907648 10973183 32.0M 0700 mdtp
24 10973184 11038719 32.0M 0700 mdtpbak
25 11038720 11563007 256M 0700 modem
26 11563008 12087295 256M 0700 modembak
27 12087296 12120063 16.0M 0700 dsp
28 12120064 12152831 16.0M 0700 dspbak
29 12152832 12154879 1024K 0700 abl
30 12154880 12156927 1024K 0700 ablbak
31 12156928 12158975 1024K 0700 dip
32 12158976 12158983 4096 0700 devinfo
33 12158984 12159495 256K 0700 apdp
34 12159496 12160007 256K 0700 msadp
35 12160008 12160009 1024 0700 dpo
36 12160016 12226863 32.6M 0700 splash
37 12226864 12226871 4096 0700 limits
38 12226872 12228919 1024K 0700 toolsfv
39 12320768 12337151 8192K 0700 logfs
40 12451840 12453887 1024K 0700 ddr
41 12453888 12453919 16384 0700 sec
42 12453920 12455967 1024K 0700 bluetooth
43 12455968 12458015 1024K 0700 bluetoothbak
44 12582912 12582913 1024 0700 fsc
45 12582920 12582935 8192 0700 ssd
46 12582936 12587031 2048K 0700 modemst1
47 12587032 12591127 2048K 0700 modemst2
48 12591128 12656663 32.0M 0700 persist
49 12656664 13180951 256M 0700 cache
50 13180952 13182999 1024K 0700 misc
51 13183000 13314071 64.0M 0700 recovery
52 13314072 13315095 512K 0700 keystore
53 13315096 13317143 1024K 0700 devcfg
54 13317144 13319191 1024K 0700 devcfgbak
55 13319192 13320215 512K 0700 frp
56 13320216 13451287 64.0M 0700 logdump
57 13451288 13455383 2048K 0700 sti
58 13500416 13500671 128K 0700 storsec
59 13631488 13893631 128M 0700 rawdump
60 13893632 13893759 65536 0700 vbmeta
61 13893760 13893887 65536 0700 vbmetabak
62 14024704 15728639 832M 0700 cust
63 15728640 15795487 32.6M 0700 logo
64 15795488 122142686 50.7G 0700 userdata
Although both system and vendor partitions on your unit are ext2 (instead of ext4), your partitions look fine to me and don't need any resizing.
You could try to re-format system and vendor using either TWRP or a root shell.