Coolpad Catalyst 3622a - Unbrick Quest - Android Q&A, Help & Troubleshooting
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...
Related
[Q] Restoring Stock Partitions
A while back I converted my e970 to an N4, afterwards I also did the 8gb to 16gb conversion as well. I have since converted back to "stock" however my partitions aren't quite the same as what I believe to be stock. Another stock dump. Can anyone suggest a process to restore my partitions back stock / true? Here is where I am at currently, partition wise: Code: ~ # ./parted /dev/block/mmcblk0 GNU Parted 1.8.8.1.179-aef3 Using /dev/block/mmcblk0 Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p p Model: MMC 016G92 (sd/mmc) Disk /dev/block/mmcblk0: 15.8GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 8389kB 75.5MB 67.1MB fat16 modem 2 75.5MB 76.0MB 524kB sbl1 3 76.0MB 76.5MB 524kB sbl2 4 76.5MB 78.6MB 2097kB sbl3 5 78.6MB 79.2MB 524kB aboot 6 79.2MB 79.7MB 524kB rpm 7 83.9MB 109MB 25.2MB boot 8 109MB 110MB 524kB tz 9 110MB 110MB 1024B pad 10 110MB 113MB 3146kB modemst1 11 113MB 116MB 3146kB modemst2 12 117MB 118MB 799kB m9kefs1 13 118MB 119MB 799kB m9kefs2 14 119MB 120MB 799kB m9kefs3 15 126MB 134MB 8389kB ext4 drm 16 134MB 143MB 8389kB ext4 sns 17 143MB 143MB 8192B ext4 ssd 18 143MB 159MB 16.8MB misc 19 159MB 176MB 16.8MB ext4 factory 20 176MB 177MB 524kB encrypt 21 177MB 177MB 524kB eksst 22 185MB 1778MB 1594MB ext4 system 23 1778MB 2617MB 839MB ext4 cache 24 2617MB 14.9GB 12.3GB ext4 userdata 25 14.9GB 14.9GB 8389kB ext4 persist 26 14.9GB 15.2GB 268MB tombstones 27 15.2GB 15.2GB 25.2MB recovery 28 15.2GB 15.2GB 3146kB fsg 29 15.2GB 15.2GB 8192B DDR 30 15.3GB 15.3GB 33.6MB fota 31 15.3GB 15.3GB 33.6MB mpt 32 15.3GB 15.3GB 524kB tzbak 33 15.3GB 15.3GB 524kB rpmbak 34 15.3GB 15.3GB 16.8MB reserved 35 15.3GB 15.8GB 423MB grow (parted) check 17 check 17 Warning: Partition 17 is 8192B, but the file system is 16.8MB. Ignore/Cancel? i i Error: The file system is bigger than its volume! Ignore/Cancel? i i No Implementation: Support for opening ext4 file systems is not implemented yet.
[List] Partition List - LG G Watch
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?
[Info] List of LG G2 D802 32GB devices and partitions
To run this commands you need a rooted device with BusyBox and parted.
Code:
[email protected]:/ #[COLOR="Blue"] [B]cat /proc/partitions[/B][/COLOR]
major minor #blocks name
179 0 30535680 mmcblk0
179 1 65536 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 512 mmcblk0p3
179 4 512 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 1 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 1 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 16384 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 1 mmcblk0p19
179 20 512 mmcblk0p20
179 21 8192 mmcblk0p21
179 22 8192 mmcblk0p22
179 23 32768 mmcblk0p23
179 24 32768 mmcblk0p24
179 25 32768 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 8 mmcblk0p29
179 30 2834432 mmcblk0p30
179 31 622592 mmcblk0p31
259 0 81920 mmcblk0p32
259 1 16384 mmcblk0p33
259 2 49152 mmcblk0p34
259 3 26460160 mmcblk0p35
259 4 61423 mmcblk0p36
179 32 4096 mmcblk0rpmb
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-num/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 1970-01-15 23:14 p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 p9 -> /dev/block/mmcblk0p9
Code:
[email protected]:/ # [B][COLOR="Blue"]ls -l /dev/block/platform/msm_sdcc.1/by-name/[/COLOR][/B]
lrwxrwxrwx root root 1970-01-15 23:14 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-15 23:14 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-15 23:14 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-15 23:14 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 1970-01-15 23:14 cust -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 1970-01-15 23:14 dbi -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-15 23:14 dbibak -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1970-01-15 23:14 drm -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-15 23:14 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-15 23:14 fota -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-15 23:14 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-15 23:14 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-15 23:14 grow -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 1970-01-15 23:14 laf -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-15 23:14 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-15 23:14 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-15 23:14 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-15 23:14 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-15 23:14 mpt -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1970-01-15 23:14 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-15 23:14 pad1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-15 23:14 pad2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-15 23:14 persist -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-15 23:14 rct -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 1970-01-15 23:14 recovery -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-15 23:14 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-15 23:14 rpmbak -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1970-01-15 23:14 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-15 23:14 sns -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-15 23:14 spare -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 1970-01-15 23:14 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-15 23:14 system -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 1970-01-15 23:14 tombstones -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 1970-01-15 23:14 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-15 23:14 tzbak -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 1970-01-15 23:14 userdata -> /dev/block/mmcblk0p35
Code:
[email protected]:/ # [B][COLOR="Blue"]parted /dev/block/mmcblk0[/COLOR][/B]
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16.8MB 83.9MB 67.1MB fat16 modem
2 83.9MB 84.9MB 1049kB sbl1
3 84.9MB 85.5MB 524kB dbi
4 101MB 101MB 524kB DDR
5 117MB 118MB 1049kB aboot
6 118MB 120MB 1049kB rpm
7 134MB 151MB 16.8MB boot
8 151MB 152MB 1049kB tz
9 152MB 152MB 1024B pad
10 168MB 171MB 3146kB modemst1
11 171MB 174MB 3146kB modemst2
12 174MB 174MB 1024B pad1
13 185MB 201MB 16.8MB misc
14 201MB 235MB 33.6MB ext4 persist
15 235MB 252MB 16.8MB recovery
16 252MB 255MB 3146kB fsg
17 268MB 269MB 524kB fsc
18 269MB 269MB 524kB ssd
19 269MB 269MB 1024B pad2
20 269MB 270MB 524kB encrypt
21 285MB 294MB 8389kB ext4 drm
22 294MB 302MB 8389kB ext4 sns
23 302MB 336MB 33.6MB laf
24 336MB 369MB 33.6MB fota
25 369MB 403MB 33.6MB ext4 mpt
26 403MB 403MB 524kB dbibak
27 403MB 404MB 1049kB rpmbak
28 404MB 405MB 1049kB tzbak
29 405MB 405MB 8192B rct
30 419MB 3322MB 2902MB ext4 system
31 3322MB 3959MB 638MB ext4 cache
32 3959MB 4043MB 83.9MB tombstones
33 4043MB 4060MB 16.8MB spare
34 4060MB 4110MB 50.3MB ext4 cust
35 4110MB 31.2GB 27.1GB ext4 userdata
36 31.2GB 31.3GB 62.9MB grow
Code:
[email protected]:/ # [B][COLOR="Blue"]mount[/COLOR][/B]
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc,errors=continue,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=050,gid=1028 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Code:
[email protected]:/ # [B][COLOR="Blue"]df[/COLOR][/B]
Filesystem Size Used Free Blksize
/dev 926.51M 128.00K 926.39M 4096
/sys/fs/cgroup 926.51M 12.00K 926.50M 4096
/mnt/asec 926.51M 0.00K 926.51M 4096
/mnt/obb 926.51M 0.00K 926.51M 4096
/system 2.66G 2.17G 495.23M 4096
/data 24.80G 20.77G 4.03G 4096
/sns 7.83M 4.03M 3.80M 4096
/persist-lg 7.83M 4.35M 3.48M 4096
/mpt 31.46M 12.96M 18.49M 4096
/cache 597.97M 9.59M 588.38M 4096
/persist 31.46M 4.05M 27.41M 4096
/firmware 63.95M 52.36M 11.59M 16384
/cust 46.22M 8.18M 38.04M 4096
/storage/emulated 926.51M 0.00K 926.51M 4096
/mnt/shell/emulated 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/0 24.80G 20.77G 4.03G 4096
/storage/emulated/0/Android/obb 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy 24.80G 20.77G 4.03G 4096
/storage/emulated/legacy/Android/obb 24.80G 20.77G 4.03G 4096
Code:
[email protected]:/ # [B][COLOR="Blue"]find /dev/block/platform/msm_sdcc.1/ -name 'mmc*' -exec fdisk -l {} \;[/COLOR][/B]
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36: 62 MB, 62897664 bytes
4 heads, 16 sectors/track, 1919 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p36 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35: 27.0 GB, 27095203840 bytes
4 heads, 16 sectors/track, 826880 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p35 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34: 50 MB, 50331648 bytes
4 heads, 16 sectors/track, 1536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p34 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p33 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32: 83 MB, 83886080 bytes
4 heads, 16 sectors/track, 2560 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p32 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31: 637 MB, 637534208 bytes
4 heads, 16 sectors/track, 19456 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p31 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30: 2902 MB, 2902458368 bytes
4 heads, 16 sectors/track, 88576 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p30 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29: 0 MB, 8192 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p29 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p28 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p27 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p26 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p25 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p24 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p23 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p22 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p21 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p20 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p19 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p18 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p17 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p16 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p15 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14: 33 MB, 33554432 bytes
4 heads, 16 sectors/track, 1024 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p14 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p13 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p12 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p11 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10: 3 MB, 3145728 bytes
4 heads, 16 sectors/track, 96 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p10 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb: 4 MB, 4194304 bytes
4 heads, 16 sectors/track, 128 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0rpmb doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9: 0 MB, 1024 bytes
4 heads, 16 sectors/track, 0 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p9 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p8 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p7 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p6 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p5 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p4 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p3 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2: 1 MB, 1048576 bytes
4 heads, 16 sectors/track, 32 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p2 doesn't contain a valid partition table
Disk /dev/block/platform/msm_sdcc.1/mmcblk0p1: 67 MB, 67108864 bytes
4 heads, 16 sectors/track, 2048 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1p1 ? 12158374 29994462 570754815+ 72 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p2 ? 2635774 32886216 968014120 65 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p3 ? 29216898 59467339 968014096 79 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/platform/msm_sdcc.1/mmcblk0p1p4 ? 1 56831664 1818613248 d Unknown
Partition 4 does not end on cylinder boundary
Partition table entries are not in disk order
Disk /dev/block/platform/msm_sdcc.1/mmcblk0: 31.2 GB, 31268536320 bytes
256 heads, 63 sectors/track, 3786 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/platform/msm_sdcc.1/mmcblk0p1
Additional links:
[GUIDE] Making Dump Files Out of Android Device Partitions
parted from cyanogenmod repo
The 4 partitions modified by AutoRec are the following, so backup with dd before applying.
bender_007 said:
^ aboot, boot, laf + recovery
Click to expand...
Click to collapse
I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot)
sandys1 said: I had this question elsewhere as well - can we force our phone into QH-USB 9006 mode ? This shows all the other partitions like aboot, boot, recovery etc and is directly flashable using "dd" . I recovered my bricked phone through this method, but I was in QH USB 9008 mode... not sure how to get this for people who are stuck in LG boot screen (and can neither get to download mode or fastboot) Click to expand... Click to collapse Didn't try either using dd to write a custom recovery being root either. Gor the QH USB 9008 mode here's a guide. [FIX] Unbrick LG G2 stuck in Qualcomm HS-USB QDLoader 9008 mode
so what's grow partition function? i managed to delete it to give some extra space on userdata.
hyperionx7 said: so what's grow partition function? i managed to delete it to give some extra space on userdata. Click to expand... Click to collapse You deleted a system partition that you don't know what's for to get 62.9MB more space?
TWRP from similar device
Booting is CONFIRMED! Flashing not possible due to recovery partition non-existant. https://androidfilehost.com/?fid=11410963190603864372 To flash this you need an unlocked bootloader and adb files Do the following command; fastboot boot twrp-deen-0.img I'm NOT responsible if you brick your device. Warranty is COMPLETELY void! You have been warned. Every single peice of credit goes to the one, the only; @Alberto97 he got TWRP to boot on our device, l personly don't own the device yet, but people tested and booting is confirmed. This is how to remove data encryption; https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595 if you can help out our device, please attempt to follow this guide to remove data encryption and make a backup of our device.
Deleted
The recovery at the Motorola Ona runs over the boot.img so you have to use the command: fastboot boot <imagename.img> I'll test it later, but I suspect it's not working.
Deleted
bb2k22 said: The recovery at the Motorola Ona runs over the boot.img so you have to use the command: fastboot boot <imagename.img> I'll test it later, but I suspect it's not working. Click to expand... Click to collapse Progress?
There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed. Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal
Alberto97 said: There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed. Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal Click to expand... Click to collapse Wow! Your a legend! Tysm!
Alberto97 said: There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed. Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal Click to expand... Click to collapse Hi. I haven't tried the TWRP recovery you provided yet. Just wanted to share some partitions. First one is different command but I guess output is pretty much the same. Code: deen_sprout:/ $ ls -al dev/block/platform/soc/7824900.sdhci/by-name total 0 drwxr-xr-x 2 root root 1280 1970-02-02 13:53 . drwxr-xr-x 4 root root 1360 1970-02-02 13:53 .. lrwxrwxrwx 1 root root 21 1970-02-02 13:53 DDR -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 aboot_a -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 aboot_b -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 apdp -> /dev/block/mmcblk0p48 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 boot_a -> /dev/block/mmcblk0p40 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 boot_b -> /dev/block/mmcblk0p41 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 carrier -> /dev/block/mmcblk0p37 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cid -> /dev/block/mmcblk0p34 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib64_a -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib64_b -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib_a -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 cmnlib_b -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 devcfg_a -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 devcfg_b -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dpo -> /dev/block/mmcblk0p50 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dsp_a -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dsp_b -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dto_a -> /dev/block/mmcblk0p42 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 dto_b -> /dev/block/mmcblk0p43 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 frp -> /dev/block/mmcblk0p33 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsc -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsg_a -> /dev/block/mmcblk0p30 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 fsg_b -> /dev/block/mmcblk0p31 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 hw -> /dev/block/mmcblk0p54 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 keymaster_a -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 keymaster_b -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 kpan -> /dev/block/mmcblk0p39 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logo_a -> /dev/block/mmcblk0p35 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logo_b -> /dev/block/mmcblk0p36 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 logs -> /dev/block/mmcblk0p47 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 metadata -> /dev/block/mmcblk0p38 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 misc -> /dev/block/mmcblk0p44 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modem_a -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modem_b -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modemst1 -> /dev/block/mmcblk0p28 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 modemst2 -> /dev/block/mmcblk0p29 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 mota -> /dev/block/mmcblk0p45 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 msadp -> /dev/block/mmcblk0p49 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 oem_a -> /dev/block/mmcblk0p56 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 oem_b -> /dev/block/mmcblk0p57 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 padA -> /dev/block/mmcblk0p53 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 persist -> /dev/block/mmcblk0p32 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 prov_a -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 prov_b -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 rpm_a -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 rpm_b -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 sbl1_a -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 sbl1_b -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 sp -> /dev/block/mmcblk0p55 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 ssd -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 syscfg -> /dev/block/mmcblk0p46 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 system_a -> /dev/block/mmcblk0p60 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 system_b -> /dev/block/mmcblk0p61 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 tz_a -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 1970-02-02 13:53 tz_b -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 userdata -> /dev/block/mmcblk0p62 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 utags -> /dev/block/mmcblk0p26 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 utagsBackup -> /dev/block/mmcblk0p27 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vbmeta_a -> /dev/block/mmcblk0p51 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vbmeta_b -> /dev/block/mmcblk0p52 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vendor_a -> /dev/block/mmcblk0p58 lrwxrwxrwx 1 root root 21 1970-02-02 13:53 vendor_b -> /dev/block/mmcblk0p59 deen_sprout:/ $ deen_sprout:/ $ cat /proc/partitions major minor #blocks name 253 0 524288 zram0 179 0 61071360 mmcblk0 179 1 512 mmcblk0p1 179 2 512 mmcblk0p2 179 3 256 mmcblk0p3 179 4 256 mmcblk0p4 179 5 1792 mmcblk0p5 179 6 1792 mmcblk0p6 179 7 64 mmcblk0p7 179 8 64 mmcblk0p8 179 9 1536 mmcblk0p9 179 10 1536 mmcblk0p10 179 11 1024 mmcblk0p11 179 12 1024 mmcblk0p12 179 13 1024 mmcblk0p13 179 14 1024 mmcblk0p14 179 15 1024 mmcblk0p15 179 16 1024 mmcblk0p16 179 17 192 mmcblk0p17 179 18 192 mmcblk0p18 179 19 102400 mmcblk0p19 179 20 102400 mmcblk0p20 179 21 4 mmcblk0p21 179 22 8 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 16384 mmcblk0p24 179 25 32 mmcblk0p25 179 26 512 mmcblk0p26 179 27 512 mmcblk0p27 179 28 2048 mmcblk0p28 179 29 2048 mmcblk0p29 179 30 12288 mmcblk0p30 179 31 12288 mmcblk0p31 259 0 32768 mmcblk0p32 259 1 512 mmcblk0p33 259 2 128 mmcblk0p34 259 3 16384 mmcblk0p35 259 4 16384 mmcblk0p36 259 5 16384 mmcblk0p37 259 6 512 mmcblk0p38 259 7 8192 mmcblk0p39 259 8 65536 mmcblk0p40 259 9 65536 mmcblk0p41 259 10 16384 mmcblk0p42 259 11 16384 mmcblk0p43 259 12 1024 mmcblk0p44 259 13 512 mmcblk0p45 259 14 512 mmcblk0p46 259 15 2048 mmcblk0p47 259 16 256 mmcblk0p48 259 17 256 mmcblk0p49 259 18 8 mmcblk0p50 259 19 64 mmcblk0p51 259 20 64 mmcblk0p52 259 21 13056 mmcblk0p53 259 22 8192 mmcblk0p54 259 23 8192 mmcblk0p55 259 24 196608 mmcblk0p56 259 25 196608 mmcblk0p57 259 26 524288 mmcblk0p58 259 27 524288 mmcblk0p59 259 28 2621440 mmcblk0p60 259 29 2621440 mmcblk0p61 259 30 53813231 mmcblk0p62 179 32 4096 mmcblk0rpmb 252 0 2580508 dm-0 252 1 516068 dm-1 252 2 193500 dm-2 252 3 53813231 dm-3
tys0n said: Hi. I haven't tried the TWRP recovery you provided yet. Just wanted to share some partitions. First one is different command but I guess output is pretty much the same. Click to expand... Click to collapse Okay! Tell me if it boots ???
borksek said: Okay! Tell me if it boots Click to expand... Click to collapse I probably won't have time to tamper with it for a few days so I don't think I'll be the first one to try. Trevligt med en till svensk i denna del av forumet Nice to see another swede in this part of the forum
tys0n said: I probably won't have time to tamper with it for a few days so I don't think I'll be the first one to try. Trevligt med en till svensk i denna del av forumet Nice to see another swede in this part of the forum Click to expand... Click to collapse Japp haha Yep haha
Alberto97 said: There's no chance that TWRP for Moto Z Play will work on the One since the last one adopts the AB partition layout. Anyway I took some time to build TWRP for deen, you can find a first release here. Be aware that I don't own this device and it is the first time I build for one with AB partition layout, it could work but I can't test it myself. Just try to fastboot boot it, it is not supposed to be flashed. Oh and it would be super helpful if someone could post the output of ls -l dev/block/bootdevice/by-name and cat /proc/partitions (this one requires root) from a terminal Click to expand... Click to collapse The output of ls -l dev/block/bootdevice/by-name is following: Code: lrwxrwxrwx 1 root root 21 1970-01-01 03:56 DDR -> /dev/block/mmcblk0p25 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 aboot_a -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 aboot_b -> /dev/block/mmcblk0p10 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 apdp -> /dev/block/mmcblk0p48 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 boot_a -> /dev/block/mmcblk0p40 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 boot_b -> /dev/block/mmcblk0p41 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 carrier -> /dev/block/mmcblk0p37 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cid -> /dev/block/mmcblk0p34 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib64_a -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib64_b -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib_a -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 cmnlib_b -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 devcfg_a -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 devcfg_b -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dpo -> /dev/block/mmcblk0p50 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dsp_a -> /dev/block/mmcblk0p23 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dsp_b -> /dev/block/mmcblk0p24 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dto_a -> /dev/block/mmcblk0p42 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 dto_b -> /dev/block/mmcblk0p43 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 frp -> /dev/block/mmcblk0p33 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsc -> /dev/block/mmcblk0p21 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsg_a -> /dev/block/mmcblk0p30 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 fsg_b -> /dev/block/mmcblk0p31 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 hw -> /dev/block/mmcblk0p54 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 keymaster_a -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 keymaster_b -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 kpan -> /dev/block/mmcblk0p39 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logo_a -> /dev/block/mmcblk0p35 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logo_b -> /dev/block/mmcblk0p36 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 logs -> /dev/block/mmcblk0p47 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 metadata -> /dev/block/mmcblk0p38 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 misc -> /dev/block/mmcblk0p44 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modem_a -> /dev/block/mmcblk0p19 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modem_b -> /dev/block/mmcblk0p20 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modemst1 -> /dev/block/mmcblk0p28 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 modemst2 -> /dev/block/mmcblk0p29 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 mota -> /dev/block/mmcblk0p45 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 msadp -> /dev/block/mmcblk0p49 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 oem_a -> /dev/block/mmcblk0p56 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 oem_b -> /dev/block/mmcblk0p57 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 padA -> /dev/block/mmcblk0p53 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 persist -> /dev/block/mmcblk0p32 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 prov_a -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 prov_b -> /dev/block/mmcblk0p18 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 rpm_a -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 rpm_b -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 sbl1_a -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 sbl1_b -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 sp -> /dev/block/mmcblk0p55 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 ssd -> /dev/block/mmcblk0p22 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 syscfg -> /dev/block/mmcblk0p46 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 system_a -> /dev/block/mmcblk0p60 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 system_b -> /dev/block/mmcblk0p61 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 tz_a -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 20 1970-01-01 03:56 tz_b -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 userdata -> /dev/block/mmcblk0p62 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 utags -> /dev/block/mmcblk0p26 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 utagsBackup -> /dev/block/mmcblk0p27 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vbmeta_a -> /dev/block/mmcblk0p51 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vbmeta_b -> /dev/block/mmcblk0p52 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vendor_a -> /dev/block/mmcblk0p58 lrwxrwxrwx 1 root root 21 1970-01-01 03:56 vendor_b -> /dev/block/mmcblk0p59 Unfortunately I don't have root so I can't execute the second one. But TWRP booted up!
Polyparadox said: Unfortunately I don't have root so I can't execute the second one. But TWRP booted up! Click to expand... Click to collapse That's good news! Did you try to perform any actions, or check if MTP etc was working?
tys0n said: That's good news! Did you try to perform any actions, or check if MTP etc was working? Click to expand... Click to collapse I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption. Mounting seemed to work fine (not for internal- external- and USB OTG storage). I forgot to check MTP but I don't think that it'll work because of the encryption. I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt. Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here. Edit: Here's what /proc/partitions looks like: Code: 179 0 61071360 mmcblk0 179 1 512 mmcblk0p1 179 2 512 mmcblk0p2 179 3 256 mmcblk0p3 179 4 256 mmcblk0p4 179 5 1792 mmcblk0p5 179 6 1792 mmcblk0p6 179 7 64 mmcblk0p7 179 8 64 mmcblk0p8 179 9 1536 mmcblk0p9 179 10 1536 mmcblk0p10 179 11 1024 mmcblk0p11 179 12 1024 mmcblk0p12 179 13 1024 mmcblk0p13 179 14 1024 mmcblk0p14 179 15 1024 mmcblk0p15 179 16 1024 mmcblk0p16 179 17 192 mmcblk0p17 179 18 192 mmcblk0p18 179 19 102400 mmcblk0p19 179 20 102400 mmcblk0p20 179 21 4 mmcblk0p21 179 22 8 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 16384 mmcblk0p24 179 25 32 mmcblk0p25 179 26 512 mmcblk0p26 179 27 512 mmcblk0p27 179 28 2048 mmcblk0p28 179 29 2048 mmcblk0p29 179 30 12288 mmcblk0p30 179 31 12288 mmcblk0p31 259 0 32768 mmcblk0p32 259 1 512 mmcblk0p33 259 2 128 mmcblk0p34 259 3 16384 mmcblk0p35 259 4 16384 mmcblk0p36 259 5 16384 mmcblk0p37 259 6 512 mmcblk0p38 259 7 8192 mmcblk0p39 259 8 65536 mmcblk0p40 259 9 65536 mmcblk0p41 259 10 16384 mmcblk0p42 259 11 16384 mmcblk0p43 259 12 1024 mmcblk0p44 259 13 512 mmcblk0p45 259 14 512 mmcblk0p46 259 15 2048 mmcblk0p47 259 16 256 mmcblk0p48 259 17 256 mmcblk0p49 259 18 8 mmcblk0p50 259 19 64 mmcblk0p51 259 20 64 mmcblk0p52 259 21 13056 mmcblk0p53 259 22 8192 mmcblk0p54 259 23 8192 mmcblk0p55 259 24 196608 mmcblk0p56 259 25 196608 mmcblk0p57 259 26 524288 mmcblk0p58 259 27 524288 mmcblk0p59 259 28 2621440 mmcblk0p60 259 29 2621440 mmcblk0p61 259 30 53813231 mmcblk0p62 179 32 4096 mmcblk0rpmb
Polyparadox said: I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption. Mounting seemed to work fine (not for internal- external- and USB OTG storage). I forgot to check MTP but I don't think that it'll work because of the encryption. I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt. Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here. Click to expand... Click to collapse We need to have a way to skip it aka no-verity or force-decrypt. We don't have a developer who can do this. @Alberto97 helped us getting twrp and I don't think he has any more intentions of helping. But he gave us a super head up! What a legend ❤
borksek said: We need to have a way to skip it aka no-verity or force-decrypt. We don't have a developer who can do this. @Alberto97 helped us getting twrp and I don't think he has any more intentions of helping. But he gave us a super head up! What a legend Click to expand... Click to collapse Man, I wish I had the skills to port TWRP. But yeah that's true, a huge thank you to @Alberto97! Also look at my last post in this thread, I've got the partitions.
Does anyone have the guts to flash the twrp image?? The command is "fastboot flash recovery twrp-dean-0.img
Polyparadox said: I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption. Mounting seemed to work fine (not for internal- external- and USB OTG storage). I forgot to check MTP but I don't think that it'll work because of the encryption. I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt. Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here. Edit: Here's what /proc/partitions looks like: Code: 179 0 61071360 mmcblk0 179 1 512 mmcblk0p1 179 2 512 mmcblk0p2 179 3 256 mmcblk0p3 179 4 256 mmcblk0p4 179 5 1792 mmcblk0p5 179 6 1792 mmcblk0p6 179 7 64 mmcblk0p7 179 8 64 mmcblk0p8 179 9 1536 mmcblk0p9 179 10 1536 mmcblk0p10 179 11 1024 mmcblk0p11 179 12 1024 mmcblk0p12 179 13 1024 mmcblk0p13 179 14 1024 mmcblk0p14 179 15 1024 mmcblk0p15 179 16 1024 mmcblk0p16 179 17 192 mmcblk0p17 179 18 192 mmcblk0p18 179 19 102400 mmcblk0p19 179 20 102400 mmcblk0p20 179 21 4 mmcblk0p21 179 22 8 mmcblk0p22 179 23 16384 mmcblk0p23 179 24 16384 mmcblk0p24 179 25 32 mmcblk0p25 179 26 512 mmcblk0p26 179 27 512 mmcblk0p27 179 28 2048 mmcblk0p28 179 29 2048 mmcblk0p29 179 30 12288 mmcblk0p30 179 31 12288 mmcblk0p31 259 0 32768 mmcblk0p32 259 1 512 mmcblk0p33 259 2 128 mmcblk0p34 259 3 16384 mmcblk0p35 259 4 16384 mmcblk0p36 259 5 16384 mmcblk0p37 259 6 512 mmcblk0p38 259 7 8192 mmcblk0p39 259 8 65536 mmcblk0p40 259 9 65536 mmcblk0p41 259 10 16384 mmcblk0p42 259 11 16384 mmcblk0p43 259 12 1024 mmcblk0p44 259 13 512 mmcblk0p45 259 14 512 mmcblk0p46 259 15 2048 mmcblk0p47 259 16 256 mmcblk0p48 259 17 256 mmcblk0p49 259 18 8 mmcblk0p50 259 19 64 mmcblk0p51 259 20 64 mmcblk0p52 259 21 13056 mmcblk0p53 259 22 8192 mmcblk0p54 259 23 8192 mmcblk0p55 259 24 196608 mmcblk0p56 259 25 196608 mmcblk0p57 259 26 524288 mmcblk0p58 259 27 524288 mmcblk0p59 259 28 2621440 mmcblk0p60 259 29 2621440 mmcblk0p61 259 30 53813231 mmcblk0p62 179 32 4096 mmcblk0rpmb Click to expand... Click to collapse Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP. This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers
tys0n said: I was greeted by a "Decrypt data" screen. I did set up phone encryption when first booting into the firmware, however I couldn't decrpyt using the pin I set up for phone encryption. Mounting seemed to work fine (not for internal- external- and USB OTG storage). I forgot to check MTP but I don't think that it'll work because of the encryption. I did a factory reset (using Android, not the bootloader) and it still won't let me Decrypt. Running the command I needed root for also worked flawlessly. I will transcribe the command output and'll post it here. Edit: Here's what /proc/partitions looks like: Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP. This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers Click to expand... Click to collapse Try it and post results! Mildly interested
borksek said: Does anyone have the guts to flash the twrp image?? The command is "flashboot flash recovery twrp-dean-0.img Click to expand... Click to collapse Recovery is not a valid partition. I always use "fastboot boot twrp-dean-0.img" to boot up twrp. tys0n said: Yeah, We need to format data and then patch boot and fstab so that forced encryption gets disabled so that we can mount data in TWRP. This should probably work Universal DM-Verity, ForceEncrypt, Disk Quota Disablers Click to expand... Click to collapse I'll back up my phone and try it out right now
System resize?
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.