I recently rooted my phone, and while using rsync to sync everything to my desktop, I noticed that logcat2 kept calling gzip constantly.
I also noticed that everytime I launched rsync it would always recopy all the devlog/* files as they were always new. Upon investigation my logs are flooded with:
Code:
01-31 07:05:34.678 W/AtomicFile( 449): Couldn't rename file /dev/block/mmcblk0p32 to backup file /dev/block/mmcblk0p32.bak
01-31 07:05:34.678 E/NetworkStats( 449): problem writing rx/tx stats:
01-31 07:05:34.678 E/NetworkStats( 449): java.io.IOException: Couldn't create directory /dev/block/mmcblk0p32
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.internal.os.AtomicFile.startWrite(AtomicFile.java:63)
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.writeNetworkRxTxStatsLocked(NetworkStatsService.java:1632)
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:1126)
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPoll(NetworkStatsService.java:1052)
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.access$100(NetworkStatsService.java:147)
01-31 07:05:34.678 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService$8.handleMessage(NetworkStatsService.java:2042)
01-31 07:05:34.678 E/NetworkStats( 449): at android.os.Handler.dispatchMessage(Handler.java:95)
01-31 07:05:34.678 E/NetworkStats( 449): at android.os.Looper.loop(Looper.java:156)
01-31 07:05:34.678 E/NetworkStats( 449): at android.os.HandlerThread.run(HandlerThread.java:60)
01-31 07:05:35.689 W/AtomicFile( 449): Couldn't rename file /dev/block/mmcblk0p32 to backup file /dev/block/mmcblk0p32.bak
01-31 07:05:35.689 E/NetworkStats( 449): problem writing rx/tx stats:
01-31 07:05:35.689 E/NetworkStats( 449): java.io.IOException: Couldn't create directory /dev/block/mmcblk0p32
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.internal.os.AtomicFile.startWrite(AtomicFile.java:63)
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.writeNetworkRxTxStatsLocked(NetworkStatsService.java:1632)
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:1126)
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPoll(NetworkStatsService.java:1052)
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.access$100(NetworkStatsService.java:147)
01-31 07:05:35.689 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService$8.handleMessage(NetworkStatsService.java:2042)
01-31 07:05:35.689 E/NetworkStats( 449): at android.os.Handler.dispatchMessage(Handler.java:95)
01-31 07:05:35.689 E/NetworkStats( 449): at android.os.Looper.loop(Looper.java:156)
01-31 07:05:35.689 E/NetworkStats( 449): at android.os.HandlerThread.run(HandlerThread.java:60)
01-31 07:05:36.690 W/AtomicFile( 449): Couldn't rename file /dev/block/mmcblk0p32 to backup file /dev/block/mmcblk0p32.bak
01-31 07:05:36.690 E/NetworkStats( 449): problem writing rx/tx stats:
01-31 07:05:36.690 E/NetworkStats( 449): java.io.IOException: Couldn't create directory /dev/block/mmcblk0p32
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.internal.os.AtomicFile.startWrite(AtomicFile.java:63)
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.writeNetworkRxTxStatsLocked(NetworkStatsService.java:1632)
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPollLocked(NetworkStatsService.java:1126)
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.performPoll(NetworkStatsService.java:1052)
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService.access$100(NetworkStatsService.java:147)
01-31 07:05:36.690 E/NetworkStats( 449): at com.android.server.net.NetworkStatsService$8.handleMessage(NetworkStatsService.java:2042)
01-31 07:05:36.690 E/NetworkStats( 449): at android.os.Handler.dispatchMessage(Handler.java:95)
01-31 07:05:36.690 E/NetworkStats( 449): at android.os.Looper.loop(Looper.java:156)
01-31 07:05:36.690 E/NetworkStats( 449): at android.os.HandlerThread.run(HandlerThread.java:60)
(Notice it's frequency)
This occurs if any app does any heavy network usage.
I've frozen any and all 'statistics' apps that I downloaded from market, but I still can't seem to stop these messages from filling the logs. - I don't know what causes the error.
Any tips for tracking this down? or what causes these messages?
Any ideas would be much appreciated.
Code:
-rw-r--r-- 1 0 0 196670 Jan 31 14:17 system_log
-rw-r--r-- 1 0 0 40634 Jan 31 14:15 system_log.1
-rw-r--r-- 1 0 0 96166 Jan 31 13:56 system_log.10
-rw-r--r-- 1 0 0 86405 Jan 31 13:56 system_log.11
-rw-r--r-- 1 0 0 90244 Jan 31 13:56 system_log.12
-rw-r--r-- 1 0 0 82079 Jan 31 13:56 system_log.13
-rw-r--r-- 1 0 0 62073 Jan 31 13:56 system_log.14
-rw-r--r-- 1 0 0 95538 Jan 31 13:56 system_log.15
-rw-r--r-- 1 0 0 95403 Jan 31 13:56 system_log.16
-rw-r--r-- 1 0 0 84653 Jan 31 13:56 system_log.17
-rw-r--r-- 1 0 0 113867 Jan 31 13:56 system_log.18
-rw-r--r-- 1 0 0 85730 Jan 31 13:56 system_log.19
-rw-r--r-- 1 0 0 86302 Jan 31 14:02 system_log.2
-rw-r--r-- 1 0 0 50431 Jan 31 13:56 system_log.20
-rw-r--r-- 1 0 0 96751 Jan 31 13:56 system_log.21
-rw-r--r-- 1 0 0 118845 Jan 31 13:56 system_log.22
-rw-r--r-- 1 0 0 108296 Jan 31 13:56 system_log.23
-rw-r--r-- 1 0 0 87772 Jan 31 13:56 system_log.24
-rw-r--r-- 1 0 0 97386 Jan 31 13:56 system_log.25
-rw-r--r-- 1 0 0 96398 Jan 31 13:56 system_log.26
-rw-r--r-- 1 0 0 88103 Jan 31 13:56 system_log.27
-rw-r--r-- 1 0 0 90497 Jan 31 13:56 system_log.28
-rw-r--r-- 1 0 0 59447 Jan 31 13:56 system_log.29
-rw-r--r-- 1 0 0 101439 Jan 31 13:56 system_log.3
-rw-r--r-- 1 0 0 93516 Jan 31 13:56 system_log.30
-rw-r--r-- 1 0 0 100282 Jan 31 13:56 system_log.31
-rw-r--r-- 1 0 0 100651 Jan 31 13:56 system_log.32
-rw-r--r-- 1 0 0 111582 Jan 31 13:56 system_log.33
-rw-r--r-- 1 0 0 97284 Jan 31 13:56 system_log.34
-rw-r--r-- 1 0 0 92448 Jan 31 13:56 system_log.35
-rw-r--r-- 1 0 0 90639 Jan 31 13:56 system_log.36
-rw-r--r-- 1 0 0 63838 Jan 31 13:56 system_log.37
-rw-r--r-- 1 0 0 90187 Jan 31 13:56 system_log.38
-rw-r--r-- 1 0 0 109815 Jan 31 13:56 system_log.39
-rw-r--r-- 1 0 0 91383 Jan 31 13:56 system_log.4
-rw-r--r-- 1 0 0 99988 Jan 31 13:56 system_log.40
-rw-r--r-- 1 0 0 113924 Jan 31 13:56 system_log.41
-rw-r--r-- 1 0 0 95536 Jan 31 13:56 system_log.42
-rw-r--r-- 1 0 0 87491 Jan 31 13:56 system_log.43
-rw-r--r-- 1 0 0 55739 Jan 31 13:56 system_log.44
-rw-r--r-- 1 0 0 94041 Jan 31 13:56 system_log.45
-rw-r--r-- 1 0 0 91800 Jan 31 13:56 system_log.46
-rw-r--r-- 1 0 0 93007 Jan 31 13:56 system_log.47
-rw-r--r-- 1 0 0 101634 Jan 31 13:55 system_log.48
-rw-r--r-- 1 0 0 91191 Jan 31 13:55 system_log.49
-rw-r--r-- 1 0 0 110852 Jan 31 13:56 system_log.5
-rw-r--r-- 1 0 0 91690 Jan 31 13:55 system_log.50
-rw-r--r-- 1 0 0 93878 Jan 31 13:55 system_log.51
-rw-r--r-- 1 0 0 85515 Jan 31 13:55 system_log.52
-rw-r--r-- 1 0 0 60744 Jan 31 13:55 system_log.53
-rw-r--r-- 1 0 0 96056 Jan 31 13:55 system_log.54
-rw-r--r-- 1 0 0 111722 Jan 31 13:55 system_log.55
-rw-r--r-- 1 0 0 88858 Jan 31 13:56 system_log.6
-rw-r--r-- 1 0 0 82870 Jan 31 13:56 system_log.7
-rw-r--r-- 1 0 0 54230 Jan 31 13:56 system_log.8
-rw-r--r-- 1 0 0 102026 Jan 31 13:56 system_log.9
Writing from Turkey. We've got a tablet brand Dark. The model EvoPAD 9740 has the Rockchip RK3188 chip in it. My intention is to put CM in it. Before I start building a custom rom from ground up I wanted to see if it is possible to build a rom by combining the image files from CM releases and manufacturer releases. The files and folders below are from the manufacturer image.
I used rpunkack to unpack r9740.img from akortek.org/download/evopad/R9740/R974031072013.rar
Here they are :
Code:
drwxr-xr-x 2 rhinestorm 4096 Oct 1 20:44 [backupimage]
-rw-r--r-- 1 rhinestorm 37228548 Oct 1 20:44 backup.img
drwxr-xr-x 2 rhinestorm 4096 Oct 1 20:44 [Image]
-rw-r--r-- 1 rhinestorm 1018399 Oct 1 20:44 boot.img
-rw-r--r-- 1 rhinestorm 1018387 Oct 1 20:44 boot.img-raw
-rw-r--r-- 1 rhinestorm 10985520 Oct 1 20:44 kernel.img
-rw-r--r-- 1 rhinestorm 10985508 Oct 1 20:44 kernel.img-raw
-rw-r--r-- 1 rhinestorm 49152 Oct 1 20:44 misc.img
-rw-r--r-- 1 rhinestorm 24969216 Oct 1 20:44 recovery.img
-rw-r--r-- 1 rhinestorm 510087168 Oct 1 20:44 system.img
-rw-r--r-- 1 rhinestorm 577 Oct 1 20:44 [COLOR="Red"]package-file[/COLOR]
-rw-r--r-- 1 rhinestorm 609 Oct 1 20:44 [COLOR="Red"]parameter[/COLOR]
-rw-r--r-- 1 rhinestorm 194926 Oct 1 20:43 r9740.img-BOOT
-rw-r--r-- 1 rhinestorm 102 Oct 1 20:43 r9740.img-HEAD
-rw-r--r-- 1 rhinestorm 32 Oct 1 20:44 r9740.img-MD5
-rw-r--r-- 1 rhinestorm 266 Oct 1 20:44 recover-script
-rw-r--r-- 1 rhinestorm 194926 Oct 1 20:44 RK3188Loader(L)_V1.24.bin
-rw-r--r-- 1 rhinestorm 584550404 Oct 1 20:43 update.img
-rw-r--r-- 1 rhinestorm 933 Oct 1 20:44 update-script
package-file
Code:
package-file package-file
bootloader RK3188Loader(L)_V1.24.bin
parameter parameter
misc Image/misc.img
kernel Image/kernel.img
boot Image/boot.img
recovery Image/recovery.img
system Image/system.img
backup backupimage/backup.img
update-script update-script
recover-script recover-script
parameters
Code:
FIRMWARE_VER:4.1.1
MACHINE_MODEL:EvoPAD R9740
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](cache),[email protected](userdata),[email protected](kpanic),[email protected](system),[email protected](user)
up!
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...
Hi,
Normally ask development question but you are all so friendly and so I wanted to ask about this file which keeps appearing as a notification and is a file in the downloads directory.
I have google as you do but I cannot see why something would keep being downloaded. It is my wife's phone so there may be something I am not telling you The contents of the package include
Code:
./data/models/classification:
total 4
drwxrwxr-x 2 jobloggs jobloggs 4096 Sep 24 2015 frontal_face_classifiers.4
./data/models/classification/frontal_face_classifiers.4:
total 320
-rw-rw-r-- 1 jobloggs jobloggs 102900 Sep 24 2015 is_left_eye_open-y0.12-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 124640 Sep 24 2015 is_right_eye_open-y0.12-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 92084 Sep 24 2015 is_smiling-y0.5-wmd.bin
./data/models/detection:
total 8
drwxrwxr-x 2 jobloggs jobloggs 4096 Sep 24 2015 multi_pose_face_landmark_detectors.8
drwxrwxr-x 2 jobloggs jobloggs 4096 Sep 24 2015 yaw_roll_face_detectors.7.1
./data/models/detection/multi_pose_face_landmark_detectors.8:
total 2740
-rw-rw-r-- 1 jobloggs jobloggs 84776 Sep 24 2015 bottom_mouth-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 91280 Sep 24 2015 bottom_mouth-yn45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87464 Sep 24 2015 bottom_mouth-yp45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 1138 Sep 24 2015 landmark_group_meta_data.bin
-rw-rw-r-- 1 jobloggs jobloggs 87372 Sep 24 2015 left_cheek-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87588 Sep 24 2015 left_cheek-yn45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 77192 Sep 24 2015 left_cheek-yn90-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 78728 Sep 24 2015 left_ear_tip-yn45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 84900 Sep 24 2015 left_ear-yn90-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 82540 Sep 24 2015 left_eye-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87260 Sep 24 2015 left_eye-yn45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 84924 Sep 24 2015 left_eye-yn90-yi45-p0-pi45-r0-ri20.lg_32-2-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 84636 Sep 24 2015 left_eye-yp45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 82280 Sep 24 2015 left_mouth-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 84400 Sep 24 2015 left_mouth-yn45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 85600 Sep 24 2015 left_mouth-yn90-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 82696 Sep 24 2015 nose_base-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 89624 Sep 24 2015 nose_base-yn45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 86248 Sep 24 2015 nose_base-yn90-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 81416 Sep 24 2015 nose_base-yp45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87940 Sep 24 2015 nose_base-yp90-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 82184 Sep 24 2015 right_cheek-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 90744 Sep 24 2015 right_cheek-yp45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 84984 Sep 24 2015 right_cheek-yp90-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 89980 Sep 24 2015 right_ear_tip-yp45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 85232 Sep 24 2015 right_ear-yp90-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87276 Sep 24 2015 right_eye-y0-yi45-p0-pi45-r0-ri20.lg_32-3-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 87936 Sep 24 2015 right_eye-yn45-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 90060 Sep 24 2015 right_eye-yp45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 85892 Sep 24 2015 right_eye-yp90-yi45-p0-pi45-r0-ri20.lg_32-2-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 86132 Sep 24 2015 right_mouth-y0-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 82260 Sep 24 2015 right_mouth-yp45-yi45-p0-pi45-r0-ri20.lg_32-tree7-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 83968 Sep 24 2015 right_mouth-yp90-yi45-p0-pi45-r0-ri20.md_32-tree7-wmd.bin
./data/models/detection/yaw_roll_face_detectors.7.1:
total 2692
-rw-rw-r-- 1 jobloggs jobloggs 183736 Sep 24 2015 head-y0-yi45-p0-pi45-r0-ri30.4a-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 168556 Sep 24 2015 head-y0-yi45-p0-pi45-rn30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 169196 Sep 24 2015 head-y0-yi45-p0-pi45-rp30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 176844 Sep 24 2015 head-yn45-yi45-p0-pi45-r0-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 182604 Sep 24 2015 head-yn45-yi45-p0-pi45-rn30-ri30.5-v24-2-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 182820 Sep 24 2015 head-yn45-yi45-p0-pi45-rp30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 182512 Sep 24 2015 head-yn90-yi45-p0-pi45-r0-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 183392 Sep 24 2015 head-yn90-yi45-p0-pi45-rn30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 181672 Sep 24 2015 head-yn90-yi45-p0-pi45-rp30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 188884 Sep 24 2015 head-yp45-yi45-p0-pi45-r0-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 183292 Sep 24 2015 head-yp45-yi45-p0-pi45-rn30-ri30.5-v24-2-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 185728 Sep 24 2015 head-yp45-yi45-p0-pi45-rp30-ri30.5-v24-2-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 183736 Sep 24 2015 head-yp90-yi45-p0-pi45-r0-ri30.5-v24-2-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 178284 Sep 24 2015 head-yp90-yi45-p0-pi45-rn30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 180944 Sep 24 2015 head-yp90-yi45-p0-pi45-rp30-ri30.5-v24-tree7-2-wmd.bin
-rw-rw-r-- 1 jobloggs jobloggs 664 Sep 24 2015 pose-r.8.1.bin
-rw-rw-r-- 1 jobloggs jobloggs 7908 Sep 24 2015 pose-y-r.8.1.bin
./libs:
total 8
drwxrwxr-x 2 jobloggs jobloggs 4096 Jan 1 1980 arm64-v8a
drwxrwxr-x 2 jobloggs jobloggs 4096 Jan 1 1980 armeabi-v7a
./libs/arm64-v8a:
total 1924
-rwxrwxr-x 1 jobloggs jobloggs 1968272 Sep 24 2015 libmobile_vision_face.so
./libs/armeabi-v7a:
total 1348
-rwxrwxr-x 1 jobloggs jobloggs 1378028 Sep 24 2015 libmobile_vision_face.so
Just a little worried about the nature of the contents
Thanks,
Iain
Hi,
Was playing with ROMs and got my phone system destroyed in the process. Can still put the phone into the download and recovery modes. In the recovery mode twrp is working fine and I can still flash files in the download with fastboot. So I have a stock KDZ file and am looking to restore the phone into a working condition.
Since I'm on Linux, flashing KDZ files with standard LG tools is a problem as they don't work on Linux. So my plan was to flash relevant parts of the KDZ file on Linux using the following approach:
1. Extract KDZ file. See [*] below.
2. Combine all system_*******.bin fragments into a single system.bin file
3. fastboot flash system /path/to/system.bin
4. No point flashing recovery and boot since the phone still boots into recovery and twrp is working fine, right?
5. ...?
Any problems with the above plan? Suggestions? Thanks
[*]
Code:
[email protected]:~/extracted$ ls -l
total 6335492
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:16 aboot_300032.bin
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:16 abootbak_304128.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 apdp_1064960.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 BackupGPT_30784512.bin
-rw-r--r-- 1 luser luser 15728640 Jul 19 19:16 boot_442368.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib_1084416.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib64_1086464.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlib64bak_1087488.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 cmnlibbak_1085440.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 devcfg_1068032.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 devcfgbak_1069056.bin
-rw-r--r-- 1 luser luser 16777216 Jul 19 19:16 dsp_212992.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 factory_704512.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 keymaster_1088512.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 keymasterbak_1089536.bin
-rw-r--r-- 1 luser luser 18874368 Jul 19 19:16 laf_507904.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 lksecapp_1082368.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 lksecappbak_1083392.bin
-rw-r--r-- 1 luser luser 88080384 Jul 19 19:16 modem_16384.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 msadp_1065984.bin
-rw-r--r-- 1 luser luser 5242880 Jul 19 19:16 persist_786432.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 PrimaryGPT_0.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 raw_resources_770048.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 raw_resourcesbak_778240.bin
-rw-r--r-- 1 luser luser 17825792 Jul 19 19:16 recovery_573440.bin
-rw-r--r-- 1 luser luser 17825792 Jul 19 19:16 recoverybak_638976.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 rpm_202752.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 rpmbak_203776.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sbl1_198656.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sbl1bak_200704.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 sec_299008.bin
-rw-r--r-- 1 luser luser 134217728 Jul 19 19:16 system_1130496.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 system_1392640.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:16 system_1394312.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:16 system_1398416.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_1658888.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_1918600.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_1922704.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_2183176.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2442888.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_2446992.bin
-rw-r--r-- 1 luser luser 5767168 Jul 19 19:17 system_2707464.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2965504.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_2967176.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_2971280.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_3231752.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_3491464.bin
-rw-r--r-- 1 luser luser 131596288 Jul 19 19:17 system_3495568.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_3756040.bin
-rw-r--r-- 1 luser luser 1048576 Jul 19 19:17 system_4018184.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_4276224.bin
-rw-r--r-- 1 luser luser 39845888 Jul 19 19:17 system_4280328.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_4538368.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_4542472.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_4804616.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5066760.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5328904.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5591048.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_5853192.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6115336.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6377480.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6639624.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_6901768.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_7163912.bin
-rw-r--r-- 1 luser luser 132644864 Jul 19 19:17 system_7426056.bin
-rw-r--r-- 1 luser luser 524288 Jul 19 19:17 system_7685768.bin
-rw-r--r-- 1 luser luser 177733632 Jul 19 19:17 system_7689216.bin
-rw-r--r-- 1 luser luser 3144155136 Jul 19 20:13 system.img
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 tz_204800.bin
-rw-r--r-- 1 luser luser 1572864 Jul 19 19:16 tzbak_208896.bin