Error: " 12 3kB" has invalid syntax for locations.
1 Like
253867577.7kB as the end point maybe? 
1 Like
Yes that worked. Here is the partition table:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 123kB 98.3kB ALIGN_TO_128K_3
2 123kB 131kB 8192B ssd
3 131kB 33.7MB 33.6MB ext4 persist
4 33.7MB 34.7MB 1049kB misc
5 34.7MB 35.3MB 524kB keystore
6 35.3MB 35.8MB 524kB frp
7 35.8MB 67.1MB 31.3MB ext4 metadata
8 67.1MB 277MB 210MB ext4 oempersist
9 277MB 9082MB 8805MB rawdump
10 9082MB 15.5GB 6442MB super
11 15.5GB 254GB 238GB userdata
254GB 254GB 1049kB Free Space
1 Like
Overall this looks great but that Free Space at the end doesnāt match, so we probably are off with the sizes of the last 3 partitions, hmmm hmmm hmmm
I suspected that might happen, Iād try resizepart 11 100%, but that probably wonāt fix it.
Maybe try to install stock FPOS after that (make sure you have critical partitions unlocked) and letās try to solve the errors that come up during that tomorrow.
2 Likes
This is epic. I follow with bated breath ā¦
4 Likes
You are welcome 
3 Likes
Okay, i have tried the resizepart, it has accepted. Now I try the FPOS. Thank you very very much for your help. Bis morgen
1 Like
Someone with knowledge of Android partitioning is probably facepalming 
pretty hard right now at the sight of two idiots stumbling through this process, but hey, gotta try stuff to learn stuff 
Good luck 
1 Like
Sure as hell. And sometimes like it. Thatās why I keep an old FP2, among other thingsā¦
1 Like
It cannot flash on super partition. 
ERROR: Could not flash the super partition on device
1 Like
That probably means the partition size / position (at least for super) is wrong. Iāll check the sizes on the two FP4s I have access to tomorrow, this has to be fixable 
Is the error the same you got when you last tried installing FPOS?
1 Like
Indeed.
Short intermission:
You could question whether it would make much sense, or how well GApps would even work considering further degoogling steps taken in the OS, but not possible?
4 Likes
Uups, yes sorry
If you deinstall microg.
Was not in my mindā¦
1 Like
Is the error the same you got when you last tried installing FPOS?
Yes it is the same.
1 Like
Iām short on time and just skimmed through this thread, so I might have missed some pieces of information. Android is using dynamic partitioning, the guide linked is not applicable at all. You might want to look into it (dynamic partitioning that is)
If I happen to have some spare time later this week I might have a look at is as well, good luck
3 Likes
Thank you very much.
2 Likes
Alright, letās get back into it
I checked the partition table for /dev/block/sda on a FP4 running stock FPOS and it matches the one you had before. Couldnāt get TWRP to boot on the one with CalyxOS, but I think weāve got enough data to push forward now.
So, hereās the partition table with the units shown as sectors:
(parted) unit s print free
Model: SKhynix H9HQ21AFAMADAR (scsi)
Disk /dev/block/sda: 61979648s
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
3s 5s 3s Free Space
1 6s 29s 24s ALIGN_TO_128K_3
2 30s 31s 2s ssd
3 32s 8223s 8192s ext4 persist
4 8224s 8479s 256s misc
5 8480s 8607s 128s keystore
6 8608s 8735s 128s frp
7 8736s 16383s 7648s ext4 metadata
8 16384s 67583s 51200s ext4 oempersist
9 67584s 2217164s 2149581s rawdump
10 2217165s 3790028s 1572864s super
11 3790029s 61979642s 58189614s userdata
61979643s 61979645s 3s Free Space
Now please compare that with your data and letās get those last 3 partitions right this time
I believe @Aaanze has tried running GApps on iode before IIRC. The problem is you can only uninstall microG during the first run wizard, but GApps have to be flashed to the phone before the first boot to work properly.
Dynamic partitioning only applies to the partitions inside super according to the docs:
With dynamic partitions, vendors no longer have to worry about the individual sizes of partitions such as
system,vendor, andproduct. Instead, the device allocates asuperpartition, and sub-partitions can be sized dynamically within it.
We are trying to recreate the original partition table so that the super partition can be reflashed from the factory images. Because, as you mentioned, that guide is not applicable at all.
1 Like
Yes the last three do not match
Number Start End Size File system Name Flags
3s 5s 3s Free Space
1 6s 29s 24s ALIGN_TO_128K_3
2 30s 31s 2s ssd
3 32s 8223s 8192s ext4 persist
4 8224s 8479s 256s misc
5 8480s 8607s 128s keystore
6 8608s 8735s 128s frp
7 8736s 16383s 7648s ext4 metadata
8 16384s 67583s 51200s ext4 oempersist
9 67584s 2217285s 2149702s rawdump
10 2217286s 3790039s 1572754s super
11 3790040s 61979642s 58189603s userdata
61979643s 61979645s 3s Free Space
1 Like
Great, that means we at least got the other ones right 
Please delete those last 3 and recreate them with the start and end sectors from the table I posted, so mkpart rawdump 67584s 2217164s and so on.
1 Like
Yes now all match.
Number Start End Size File system Name Flags
3s 5s 3s Free Space
1 6s 29s 24s ALIGN_TO_128K_3
2 30s 31s 2s ssd
3 32s 8223s 8192s ext4 persist
4 8224s 8479s 256s misc
5 8480s 8607s 128s keystore
6 8608s 8735s 128s frp
7 8736s 16383s 7648s ext4 metadata
8 16384s 67583s 51200s ext4 oempersist
9 67584s 2217164s 2149581s rawdump
10 2217165s 3790028s 1572864s super
11 3790029s 61979642s 58189614s userdata
61979643s 61979645s 3s Free Space
1 Like