Develop Bugs

Unable to mount data & cache

Hi all, got my kindle fire brick. I think my partition is messed up. I bought a factory cable which able me to install twrp and i succefully(i guess) flashed energy ICS. But it prompt me "e:unable to mount '/data" e:unable to mount '/cache". I were to boot to normal boot it will just boot endlessly but i still can access to fff and twrp.i did some research on repartitioning for kindle fire but i need some guidance. Help is much appreciated
Sent from my GT-I9100 using xda app-developers app

Usually this is a fairly bad indication but do this go to the mount section in twrp and make sure there are no checks in the boxes of data and system if so uncheck them, I know you said data and cache but this should have a check in the box then try a reboot also were you previously using cwmr? If so you may have been bitten by the bug a very unsightly one that generally means the death of your kindle unless you know how to repartition around a broken emmc. What did you do prior to this that caused this to happen?
Also energy is not the best for good mounting just saying...

I was using fireparted to backup my partition when my pc suddenly shut down. Thats when everything screws up. Also my data and cache are not able to check or uncheck. I hope theres a kind soul to guide me through this process
Sent from my GT-I9100 using xda app-developers app

If you ask me I would say its toast but maybe someone knows a way to restore factory partitions I know many are looking for a solution for thier parts only kindle....

From what I understand...
Code:
fastboot oem format
...will rewrite your partition table to stock. And as long as you haven't messed with the partition sizes, your data will stay intact.
Enter:
Code:
shell cat /proc/partitions
To get a list of your current partitions and sizes to check to see if they even exist to begin with. And if so, it's likely just a case of broken or missing mountpoints.
Now, whether or not "fastboot oem format" will restore broken or missing mountpoints, I couldn't tell you for sure; I've never had to try it. But in your situation, it probably couldn't hurt to try.
You can also recreate mountpoints manually if needed.
[Edit:] It has just been explained to me that "fastboot oem format" won't do anything about mountpoints.

Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?

dean11 said:
Pardon me for my Noob-ness, are the code to be execute on pc or on TWRP?
Click to expand...
Click to collapse
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.

kinfauns said:
Step back a bit and figure out how all of these things work together by reading the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
It will be a lot easier for you to understand what you are doing and why you are doing them. It will also explain how and where to run the commands.
Click to expand...
Click to collapse
OH MY GOOOOD!!!! MY KINDLE IS ALIVE!!!! THANK YOU SO MUCH @kinfauns!

kinfauns said:
Assuming you can get into TWRP and run adb shell, execute the following command...
Code:
adb shell parted /dev/block/mmcblk0 unit b print
Note: version 2.2.0 is missing the parted binary, so you'll need to use 2.1.1
This will give you a detailed layout of your storage device and the filesystems for each partition. I'm running from memory here, but the right column should show the filesystem types it sees for that particular partition. For userdata (which is mounted as data) and cache, those should be ext4. If you don't see that, you need to remake those partitions.
Code:
adb shell mke2fs -T ext4 /dev/block/mmcblk0p10
adb shell mke2fs -T ext4 /dev/block/mmcblk0p11
Then you can repeat the parted command above and see if the commands worked. If the commands were successful, you can use the mount command or it's probably easier to just reboot into TWRP and it should do it automatically.
Click to expand...
Click to collapse
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!

june12 said:
I have the similar situation.
And when I use "parted" to check my kidle partition, there is no cache, and the userdata is ext2.
Number Start End Size File system Name Flags
1 131072B 262143B 131072B xloader
2 262144B 524287B 262144B bootloader
3 524288B 11010047B 10485760B dkernel
4 11010048B 212336639B 201326592B ext4 dfs
5 212336640B 229113855B 16777216B recovery
6 229113856B 296222719B 67108864B ext4 backup
7 296222720B 306708479B 10485760B boot
8 306708480B 311951359B 5242880B ext4 splash
9 311951360B 848822271B 536870912B ext4 system
10 848822272B 849000447B 178176B ext2 userdata
12 2448000000B 7748000255B 5300000256B fat32 media msftres
When I use the mke2fs to change the file system type, it returns this error
Not enough space to build proposed filesystem while setting up superblock.
Please help!
Thank you in advance!
Click to expand...
Click to collapse
I don't know who or what did that to your partition table, but partitions 10-12 are not right. It looks like mke2fs is complaining because your userdata partition is only ~178KB. I'm also a bit concerned that you've extended the media partition as far as you have. You might have some additional problems there.
The easiest way for you to get started on a fix is to get into fastboot mode with FFF and run...
Code:
fastboot oem format
That will bring your partition table back to stock, so you can run those mke2fs commands to remake those filesystems on the two partitions. You'll also have to remake the media partition in parted. You can find some instructions on how to do that here...
http://forum.xda-developers.com/showthread.php?t=1658885

Hey,
My current ROM is fine, but I can't mount data & cache in TWRP.
Nothing happens when I click mount data or mount cache in TWRP 2.6.3.1
I reflashed twrp two times and checked the md5sum.
When I try to backup my rom:
When I try a factory reset:
This is what I tried in fastboot:
Code:
fastboot oem format
...
OKAY [ 0.064s]
finished. total time: 0.065s
fastboot oem idme bootmode 4000
...
OKAY [ 0.081s]
finished. total time: 0.081s
fastboot reboot
rebooting...
finished. total time: -0.000s
adb shell cat /proc/partitions
major minor #blocks name
7 0 8348 loop0
179 0 7553024 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
179 64 512 mmcblk0boot1
179 32 512 mmcblk0boot0
254 0 8347 dm-0
The parted command isn't working for me.
I have never repartitioned them as far as I know.
Wha't wrong with my partitions?

[Q] Pulling my hair out over Dual Booting!

Ok, I'm 90% of the way to getting my Kindle exactly how I want it, but I'm getting stuck at the last hill. Let me take you through a step by step of what I've done, and then what I want to do, and lets see if I can get some help and finally get this thing working!
I bought my 1st Gen Kindle a year after it came out, and immediately rooted it. Within a month, I put some old version of TWRP on and flashed to a custom ROM. Since then I've purchased Amazon Prime and wish to be able to use my Kindle with it. this involves having a perfectly Stock, non-rooted ROM installed. Thus began my nightmare of trying to get it back into such a state.
After 3 hours of running down dead end paths, I finally ran the latest Kindle Fire Utility (0.9.9) and had to finally use COTR recovery to flash the 6.2.3 stock rom because I was getting all sorts of errors using TWRP.
Now I have a perfectly back to Stock Kindle, but I still want Gapps and Netflix, but without rooting my device to break video streaming. Solution? Dual boot!
Ran the TWRP installer, and then the FFF installer. Then ran the Dual Boot installer, choosing the option to prepare FFF for dual booting. Now my kindle has the FFF bootloader, can boot into Stock as the primary and can boot into TWRP Recovery. However, when I tried to flash an alt rom (SBloods' ROM found https://code.google.com/p/kindle-alt-roms-cm10-cm9-dev/downloads/list ) it says it completes successfully, however when I attempt to boot into the alterante boot, it just stays at the Fastboot Booting screen.
What do I need to do and/or use in order to get my alt ROM (or any alt ROM) booting properly?

asrrin29 said:
Ok, I'm 90% of the way to getting my Kindle exactly how I want it, but I'm getting stuck at the last hill. Let me take you through a step by step of what I've done, and then what I want to do, and lets see if I can get some help and finally get this thing working!
I bought my 1st Gen Kindle a year after it came out, and immediately rooted it. Within a month, I put some old version of TWRP on and flashed to a custom ROM. Since then I've purchased Amazon Prime and wish to be able to use my Kindle with it. this involves having a perfectly Stock, non-rooted ROM installed. Thus began my nightmare of trying to get it back into such a state.
After 3 hours of running down dead end paths, I finally ran the latest Kindle Fire Utility (0.9.9) and had to finally use COTR recovery to flash the 6.2.3 stock rom because I was getting all sorts of errors using TWRP.
Now I have a perfectly back to Stock Kindle, but I still want Gapps and Netflix, but without rooting my device to break video streaming. Solution? Dual boot!
Ran the TWRP installer, and then the FFF installer. Then ran the Dual Boot installer, choosing the option to prepare FFF for dual booting. Now my kindle has the FFF bootloader, can boot into Stock as the primary and can boot into TWRP Recovery. However, when I tried to flash an alt rom (SBloods' ROM found https://code.google.com/p/kindle-alt-roms-cm10-cm9-dev/downloads/list ) it says it completes successfully, however when I attempt to boot into the alterante boot, it just stays at the Fastboot Booting screen.
What do I need to do and/or use in order to get my alt ROM (or any alt ROM) booting properly?
Click to expand...
Click to collapse
Boot into recovery and enter the following commands:
Code:
adb shell parted /dev/block/mmcblk0
print
If the shell complains that 'parted' isn't installed, you can install it temporarily (until reboot).
1)Download 'parted' here: http://d-h.st/h81
2) place the 'parted' binary in the same directory from which you are entering your commands and enter the following:
Code:
adb push parted /sbin/parted
adb shell chown 0.0 /sbin/parted
adb shell chmod 755 /sbin/parted
Once you have 'parted' running and have entered the 'print' command to print the partition table, copy it and post it here.

Here's the output:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
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) print
print
print
Model: MMC MMC08G (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 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)

asrrin29 said:
Here's the output:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ←[6nparted /dev/block/mmcblk0
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) print
print
print
Model: MMC MMC08G (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 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 7690MB 5380MB fat32 media
(parted)
Click to expand...
Click to collapse
Well there's your problem. In order to have a dual boot, you have to have separate sets of partitions for both boots. You should go back to the instructions for dual booting and see what you missed.
Hint: you should have a total of 16 partitions.

Ok, so I redid the the dual-boot and set up the partitions, but now I am unable to copy files to the sdcard. I keep getting an Error: 80070057 the parameter is incorrect.
I tried installing SBlood's ROM and this time it restarts the recovery everytime it goes to initialize scripts. I then tried to get a different ROM (The MIUI one) onto the kindle by using ADB push, and I get an unknown error when trying to install it.

asrrin29 said:
Ok, so I redid the the dual-boot and set up the partitions, but now I am unable to copy files to the sdcard. I keep getting an Error: 80070057 the parameter is incorrect.
I tried installing SBlood's ROM and this time it restarts the recovery everytime it goes to initialize scripts. I then tried to get a different ROM (The MIUI one) onto the kindle by using ADB push, and I get an unknown error when trying to install it.
Click to expand...
Click to collapse
What did you use to set up your partitions? Did you create them manually or did you use the format-all.zip?

soupmagnet said:
What did you use to set up your partitions? Did you create them manually or did you use the format-all.zip?
Click to expand...
Click to collapse
I used the altrom-format-all.zip that came with KFU 0.9.9.

asrrin29 said:
I used the altrom-format-all.zip that came with KFU 0.9.9.
Click to expand...
Click to collapse
The error you are receiving may be a problem with Windows, and not necessarily the device or the dual boot.
Try the following and see if it makes a difference:
http://support.microsoft.com/kb/982736

soupmagnet said:
The error you are receiving may be a problem with Windows, and not necessarily the device or the dual boot.
Try the following and see if it makes a difference:
http://support.microsoft.com/kb/982736
Click to expand...
Click to collapse
The error only happens on the dual booted Kindle. I can plug any other android device, or my kindle when it's in single boot mode, and it doesn't happen.

asrrin29 said:
The error only happens on the dual booted Kindle. I can plug any other android device, or my kindle when it's in single boot mode, and it doesn't happen.
Click to expand...
Click to collapse
When you print your partition table, does the media partition have "msftres" beside it?

[Q&A/T][ROM][OFFICIAL][4.4.4] AICP for OtterX

[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting[/SIZE]​ [SIZE=+2]Specific to[/SIZE]
[ROM][OFFICIAL][4.4.4] AICP for OtterX
Click link here>> http://<a href="http://forum.xda-de...fire/development/rom-aicp-otterx-t2820557</a>http://forum.xda-developers.com/kindle-fire/development/rom-aicp-otterx-t2820557 <<Click link here Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on the topic described in the OP

Does this ROM support /cache and /data F2FS? Thanks!

Koopa777 said:
Does this ROM support /cache and /data F2FS? Thanks!
Click to expand...
Click to collapse
Yes it does.

Hi, I've got an insufficient system memory error trying to install AICP Gapps mini.
Here is aicp_gapps.log:
# begin pa gapps properties
# This file contains information needed to flash PA GApps
current_gapps_version=unknown
current_gapps_type=unknown
installing_gapps_version=20140608
installing_gapps_type=mini
total_system_size_kb=0 9 516040
used_system_size_kb=450324
free_system_size_kb=65716
free_space_reqd_kb=86924
total_gapps_size_kb=214120
install.chrome=false
install.faceunlock=true
install.camera=false
install.gallery=false
gallery.device=none
replace.launcher=false
replace.mms=false
replace.browser=false
replace.picotts=false
device.name=otterx
# end pa gapps properties
What should I do to install it?
Sent from my Amazon OtterX using XDA Premium 4 mobile app

Are you on the otterx 2.05 boot loader and partitions
Sent from my OtterX running AICP using Tapatalk.

joshuabg said:
Are you on the otterx 2.05 boot loader and partitions
Sent from my OtterX running AICP using Tapatalk.
Click to expand...
Click to collapse
Right if using. 2.04 bootloader system partition will be smaller
---------- Post added at 02:06 PM ---------- Previous post was at 02:01 PM ----------
As posted
Hashcode said:
The v2.04 otterx partitions are smaller:
system = 512MB)
cache = 265MB
Vs the newer larger partitions in v2.05:
system = 768MB
cache = 512MB
The idea was to protect from future required wipes do to low system/cache space.
The bootloader doesn't need to support f2fs only recovery and the ROM/kernel.
Click to expand...
Click to collapse

joshuabg said:
Are you on the otterx 2.05 boot loader and partitions
Sent from my OtterX running AICP using Tapatalk.
Click to expand...
Click to collapse
Where can I check it? When booting there is v2.05 in the upper right corner.
Partitions: otterx
Sent from my Amazon OtterX using XDA Premium 4 mobile app

Duddha said:
Where can I check it? When booting there is v2.05 in the upper right corner.
Partitions: otterx
Sent from my Amazon OtterX using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you follow hashcodes instuctions to amke a new partitions for otterx 2.05?
http://forum.xda-developers.com/showpost.php?p=52995722&postcount=286

joshuabg said:
Did you follow hashcodes instuctions to amke a new partitions for otterx 2.05?
http://forum.xda-developers.com/showpost.php?p=52995722&postcount=286
Click to expand...
Click to collapse
Yes. More than month ago
And I was using this ROM http://forum.xda-developers.com/showthread.php?t=2410112 last month
Sent from my Amazon OtterX using XDA Premium 4 mobile app

Duddha said:
Yes. More than month ago
And I was using this ROM http://forum.xda-developers.com/showthread.php?t=2410112 last month
Sent from my Amazon OtterX using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Verified md5 checksum for rom and gapps after downloading? https://sites.google.com/site/sdshadowscollection/home/hash-checksums

sd_shadow said:
Verified md5 checksum for rom and gapps after downloading?
Click to expand...
Click to collapse
MD5 checksum is Ok.
How can I check the size of system partition on my Kindle?
Sent from my Amazon OtterX using XDA Premium 4 mobile app

Duddha said:
MD5 checksum is Ok.
How can I check the size of system partition on my Kindle?
Sent from my Amazon OtterX using XDA Premium 4 mobile app
Click to expand...
Click to collapse
first you should verify bootloader still says otterx partition and not Amazon.
------
For this, your device must be booted into recovery.
To print your partition table:
with kindle In TWRP, on PC in command prompt
Code:
$ adb shell
~ # parted /dev/block/mmcblk0
(parted) print
I haven't tried it, command is posted in
[HOW TO] Fix "Failure to mount" sdcard, system, data or cache

Partitions size
sd_shadow said:
first you should verify bootloader still says otterx partition and not Amazon.
------
For this, your device must be booted into recovery.
To print your partition table:
with kindle In TWRP, on PC in command prompt
Code:
$ adb shell
~ # parted /dev/block/mmcblk0
(parted) print
I haven't tried it, command is posted in
[HOW TO] Fix "Failure to mount" sdcard, system, data or cache
Click to expand...
Click to collapse
Here is what I've got:
/sbin # ←[6nparted /dev/block/mmcblk0
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) print
print
print
Error: Can't have overlapping partitions.
Model: MMC M8G2FA (sd/mmc)
Disk /dev/block/mmcblk0: 7734MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 850MB 1049kB ext4 spacer
11 850MB 1118MB 268MB ext4 cache
12 1118MB 7734MB 6616MB userdata
(parted)
Partition mode is OtterX

in bootloader: change back to amazon partitions
reboot
change back to OtterX partitions
boot to recovery
Wipe>wipe cache>
reboot recovery>
format data>home>wipe>advanced wipe>wipe system
reboot recovery> install rom/gapps

Thanks
sd_shadow said:
in bootloader: change back to amazon partitions
reboot
change back to OtterX partitions
boot to recovery
Wipe>wipe cache>
reboot recovery>
format data>home>wipe>advanced wipe>wipe system
reboot recovery> install rom/gapps
Click to expand...
Click to collapse
Thank you sd_shadow :good:
After all steps the ROM and GAPPS were successfully installed

What about games on this ROM?
I'm starting Cut the Rope 2 and getting black screen just after game's slash screen. Something like that with Angry Birds GO! - there is a music starts playing but the screen is black and in a few seconds my Kindle is back to home screen

Duddha said:
What about games on this ROM?
I'm starting Cut the Rope 2 and getting black screen just after game's slash screen. Something like that with Angry Birds GO! - there is a music starts playing but the screen is black and in a few seconds my Kindle is back to home screen
Click to expand...
Click to collapse
Hmmm, Games seem to work for me, I just downloaded Cut the Rope 2 and it works.

joshuabg said:
Hmmm, Games seem to work for me, I just downloaded Cut the Rope 2 and it works.
Click to expand...
Click to collapse
I've just restarted Kindle. Run Cut the Rope 2, play 1 level (not very smooth), go to the next level and... I'm on the home screen.
Maybe there is still something wrong with my one. Please help me to find out what is wrong (log files or something else)

Duddha said:
I've just restarted Kindle. Run Cut the Rope 2, play 1 level (not very smooth), go to the next level and... I'm on the home screen.
Maybe there is still something wrong with my one. Please help me to find out what is wrong (log files or something else)
Click to expand...
Click to collapse
Cut the rope 2 runs very well on CyanogenMod linaro builds. http://forum.xda-developers.com/showthread.php?t=2853658

joshuabg said:
Cut the rope 2 runs very well on CyanogenMod linaro builds. http://forum.xda-developers.com/showthread.php?t=2853658
Click to expand...
Click to collapse
Thank you joshuabg.
I'm now using SlimKat ROM. I will try this build a bit later ))

[Tutorial+Video] How to Re-partition Nokia X/XL (Increase System & Data size)

Ultimate Guide to Re-partition Nokia X/XL
(Increase System & Data size)
​
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Disclaimer:
By doing this, of course your warranty is now void, This method is VERY ADVANCED, I don't recommend newbies & beginners to do it, You may BRICK your device !
FIRST read to the end then do it !! I am not responsible for the "BRICKs".
If you have any question before doing this method i'll be happy to answer you in comments below.
Before doing anything make sure to do FULL DD Backup of your mobile, to restore it if anything went wrong.
Check @mdfzhi Guide Here
Part 1: Information:
Nokia X/XL have 3.9 GB EMMC Storage (26 Partition), System is 560 MB , Data is 1.1 GB and Internal Storage is 1.2 GB.
Nokia X Partitions & Blocks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nokia XL Partitions & Blocks:
by looking to this table, we don't know about These Partitions (p1-p2-p4-p5-p6-p7-p8-p9-p10-p11-p12-p13-p15-p20-p24-p26) Mounts, So before doing anything YOU HAVE TO BACKUP Them.
The Main idea of Re-partitioning:
Increasing some partitions size by decreasing some others, WITHOUT dealing with any partition we don't know.
So you can control size of: System - Cache -Data - Storage - Preload
Open my Partitions Table Here and look:
Choose your mobile then Read
I have two MODs:
1- 2.30 GB Data With 150MB.
2- 950 MB System + 2.30 GB Data With 150MB.
In these MODs i didn't changed any partition size except ones i have marked.
How to Calculate Size of Any partition?
End - Start = Total (Number of blocks)
Total * 8 = Blocks (Size in Blocks)
Blocks / 1024 = Size in MB
Editing Partitions Sizes:
In order to edit any partition size you need to delete all partitions before it.
Ex. To edit Storage (p21) i have to delete partitions from p26 to p21.
Then you'll create them again with modified sizes.
The next step is set each partition ID like table (YOU CAN'T CHANGE ANY ID)
Final step is Syncing Partitions table & Apply changes.
Lets GO !
You'll need to:
- Many spare times to read and follow this tutorial.
- Your phone with battery not below 50%.
- Any Custom Recovery as long as it can unmount all partitions & use adb (Make Sure Recovery won't reboot suddenly)
I have done it with TWRP 3.0.2-0 Recovery - I think Miui Recovery is good choice also.
Download Miui Recovery Here
- A reliable PC with Nokia X/XL Drivers & ADB installed.
Drivers on Windows/Linux/Mac Here
Download ADB & Fastboot Here
- A reliable USB cable.
- About 700 MB Free space in SD Card.
- Choose MOD you'll do as you like. (But READ the two before DOING ANYTHING)
Part 2: Re-Partitioning:
Copy All Commands & Sizes From My Excel Sheet
MOD 1: Increase System To 950 MB & Data Size to 2.30 GB (The Best !)
Nokia XL
Nokia X
http://i.imgur.com/EYcizum.png
We'll Re-partition all partitions from p18 to p26) with sizes in above picture, to make System 950 MB - Data 2.30 GB - Internal Storage 150 MB & Preload 30 MB - Check Page 3 in Partition Table.
A-Preparing:
1- Copy whole data from Internal Storage to SD Card or PC
2- Boot to Custom Recovery then Unmount all partitions except SD Card.
3- Connect phone to PC via USB cable then open ADB tools (Shift + Right Click in ADB Folder - select Open CMD.
4- Type
Code:
adb shell
you'll see # sign, Now type
Code:
fdisk -l /dev/block/mmcblk0
5- You'll see your partitions table, make sure it's like "First Page in Partition Table"
Nokia XL
Nokia X
B-Backing Up Unknown Partitions :
1- Backup Partitions from 23 to 26, type:
Code:
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20.img
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23.img
dd if=/dev/block/mmcblk0p24 of=/sdcard/mmcblk0p24.img
dd if=/dev/block/mmcblk0p25 of=/sdcard/mmcblk0p25.img
dd if=/dev/block/mmcblk0p26 of=/sdcard/mmcblk0p26.img
2- Make sure this backup stored in SD Card not Internal Storage.
C-Re-Partitioning-Deleting Partitions:
1- Continue in ADB, type:
Code:
busybox fdisk /dev/block/mmcblk0
2- We'll use "d" command to delete partitions from 26 to 21
Type each line command below then hit enter after every command
Code:
d
26
d
25
d
24
d
23
d
22
d
21
d
20
d
19
d
18
D-Re-Partitioning-Creating New Partitions:
1- Now we'll use "n" command to create new partitions with modified sizes, command usage:
n - Enter: To start creating new partition.
Start block - Enter: First cylinder of partition.
End block- Enter: Last cylinder of partition.
2- Continue in ADB After last command, type:
Code:
n
16931
134688
n
134690
147487
n
147489
147491
n
147493
166690
n
166692
452514
n
452516
464674
n
464676
465954
n
465956
469794
n
469796
477184
E-Re-Partitioning-Set New Partitions Type:
1- Now we'll use "t" command to set new partitions type as (Original Partition Table) with modified sizes, command usage:
t - Enter: Start Partition Type Modification.
Partition Number - Enter: Choose Partition.
Type ID - Enter: Set Partition ID.
2- Continue in ADB After last command, type:
Code:
t
18
83
t
19
83
t
20
4c
t
21
c
t
22
83
t
23
83
t
24
7d
t
25
83
t
26
83
F-Re-Partitioning-Apply Modifications And Saving:
Till now we haven't done any real changes, you can cancel these changes by Closing ADB Window.
To Apply Changes:
1- use "p" command to sync new partitions to table, type:
Code:
p
then press Enter.
2- You'll see Modified Partition Table, Make sure all changes is OK.
3- Type
Code:
w
to save New Partition Table, then Wait till changes.
G-Restoring Unknown Partitions Backup:
We are finished Re-Partitioning, it's time to restore backup we made in step "b".
1- Type:
Code:
dd if=/sdcard/mmcblk0p20.img of=/dev/block/mmcblk0p20
dd if=/sdcard/mmcblk0p23.img of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p24.img of=/dev/block/mmcblk0p24
dd if=/sdcard/mmcblk0p25.img of=/dev/block/mmcblk0p25
dd if=/sdcard/mmcblk0p26.img of=/dev/block/mmcblk0p26
2- Now Exit ADB, type:
Code:
exit
then
Code:
adb reboot
H-The last step:
In order to use New Partitions we need to wipe it through Custom Recovery.
Boot to Custom Recovery and Wipe all partitions except SD Card.
Congratulations ! you have done it successfully, Now Flash any ROM / Restore Custom Recovery Backup to use your phone.
MOD 2: Increase Data Size to 2.30 GB
We'll Re-partition (p21 & p22) with sizes in above picture, to make Data 2.30 GB & Internal Storage 150 MB - Check Page 2 in Partition Table.
A-Preparing:
1- Copy whole data from Internal Storage to SD Card or PC
2- Boot to Custom Recovery then Unmount all partitions except SD Card.
3- Connect phone to PC via USB cable then open ADB tools (Shift + Right Click in ADB Folder - select Open CMD.
4- Type
Code:
adb shell
you'll see # sign, Now type
Code:
fdisk -l /dev/block/mmcblk0
5- You'll see your partitions table, make sure it's like "First Page in Partition Table"
Nokia XL
Nokia X
B-Backing Up Unknown Partitions :
1- Backup Partitions from 23 to 26, type:
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23.img
dd if=/dev/block/mmcblk0p24 of=/sdcard/mmcblk0p24.img
dd if=/dev/block/mmcblk0p25 of=/sdcard/mmcblk0p25.img
dd if=/dev/block/mmcblk0p26 of=/sdcard/mmcblk0p26.img
2- Make sure this backup stored in SD Card not Internal Storage.
C-Re-Partitioning-Deleting Partitions:
1- Continue in ADB, type:
Code:
busybox fdisk /dev/block/mmcblk0
2- We'll use "d" command to delete partitions from 26 to 21
Type each line command below then hit enter after every command
Code:
d
26
d
25
d
24
d
23
d
22
d
21
D-Re-Partitioning-Creating New Partitions:
1- Now we'll use "n" command to create new partitions with modified sizes, command usage:
n - Enter: To start creating new partition.
Start block - Enter: First cylinder of partition.
End block- Enter: Last cylinder of partition.
2- Continue in ADB After last command, type:
Code:
n
101413
120613
n
120613
406437
n
406437
418597
n
418597
419877
n
419877
469797
n
469797
477184
E-Re-Partitioning-Set New Partitions Type:
1- Now we'll use "t" command to set new partitions type as (Original Partition Table) with modified sizes, command usage:
t - Enter: Start Partition Type Modification.
Partition Number - Enter: Choose Partition.
Type ID - Enter: Set Partition ID.
2- Continue in ADB After last command, type:
Code:
t
21
c
t
22
83
t
23
83
t
24
7d
t
25
83
t
26
83
F-Re-Partitioning-Apply Modifications And Saving:
Till now we haven't done any real changes, you can cancel these changes by Closing ADB Window.
To Apply Changes:
1- use "p" command to sync new partitions to table, type:
Code:
p
then press Enter.
2- You'll see Modified Partition Table, Make sure all changes is OK.
3- Type
Code:
w
to save New Partition Table, then Wait till changes.
G-Restoring Unknown Partitions Backup:
We are finished Re-Partitioning, it's time to restore backup we made in step "b".
1- Type:
Code:
dd if=/sdcard/mmcblk0p23.img of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p24.img of=/dev/block/mmcblk0p24
dd if=/sdcard/mmcblk0p25.img of=/dev/block/mmcblk0p25
dd if=/sdcard/mmcblk0p26.img of=/dev/block/mmcblk0p26
2- Now Exit ADB, type:
Code:
exit
then
Code:
adb reboot
H-The last step:
In order to use New Partitions we need to wipe it through Custom Recovery.
Boot to Custom Recovery and Wipe all partitions except SD Card.
Congratulations ! you have done it successfully, Now Flash any ROM / Restore Custom Recovery Backup to use your phone.
Video Tutorial
Notes:
1- If you get "Warning" Error in Step F-3. Check Partitions using "p" command, if changes can't be done then Change Custom Recovery then do Steps again.
2- If Custom Recovery rebooted suddenly, don't worry do Steps again.
3- If TWRP couldn't wipe New Partitions, boot to ClockWorkMod Recovery 6.0.4.8 and Wipe them.
4- Nokia X doesn't have p26 partition.
Final Result
- Data Only:
Thanks:
netware @ 4pda For helping me doing this on Nokia XL
 @ani00 For testing on Nokia X
Me For Testing and writing this guide
Don't Forget To make BACKUP And Hit Thanks :good:

With this good news in hand, will there be any rom development coming on Nokia X/XL?

veez21 said:
With this good news in hand, will there be any rom development coming on Nokia X/XL?
Click to expand...
Click to collapse
I am still trying with MM but till now build can't complete

YSH ALSAGER said:
I am still trying with MM but till now build can't complete
Click to expand...
Click to collapse
Can you share the link if there is any, i wanna have a look.:good:

veez21 said:
Can you share the link if there is any, i wanna have a look.:good:
Click to expand...
Click to collapse
Link for what?

YSH ALSAGER said:
Link for what?
Click to expand...
Click to collapse
Source code

veez21 said:
Source code
Click to expand...
Click to collapse
See my github.com repository

You Are Useng PAC Rom On Your Phone Did The Hotspot Work And Ring With Vibration Too And What Is The Clock Speed
Please Tell me How You Fix It

Sofiane omega said:
You Are Useng PAC Rom On Your Phone Did The Hotspot Work And Ring With Vibration Too And What Is The Clock Speed
Please Tell me How You Fix It
Click to expand...
Click to collapse
I've Nokia XL, so everything works perfectly

YSH ALSAGER said:
I've Nokia XL, so everything works perfectly
Click to expand...
Click to collapse
Can You Fix The Patch For X And What I Need To Send You From The Logcat To Fix Wifi Hotspot

Sofiane omega said:
Can You Fix The Patch For X And What I Need To Send You From The Logcat To Fix Wifi Hotspot
Click to expand...
Click to collapse
On Nokia X everything works expect hotspot, try to grab adb logcat and send it to me

YSH ALSAGER said:
On Nokia X everything works expect hotspot, try to grab adb logcat and send it to me
Click to expand...
Click to collapse
Not Every Think I Test Ring With Vibration And It Doesn't Work And The Over clock Speed Is Lock To 122MHz And He Should Be 245MHz And For The Logcat I Send You It All

Sofiane omega said:
Not Every Think I Test Ring With Vibration And It Doesn't Work And The Over clock Speed Is Lock To 122MHz And He Should Be 245MHz And For The Logcat I Send You It All
Click to expand...
Click to collapse
122Mhz is the minimum frequency because it uses null kernel or another kernel that was based on it,

Guide has been updated !
Add Nokia X Partitions & Instructions
Thanks @ani00

I just lost mmcplk0p20 and mmcplk0p25. Now my pc only show unknown device when i plug in. Any suggest

vatva69 said:
I just lost mmcplk0p20 and mmcplk0p25. Now my pc only show unknown device when i plug in. Any suggest
Click to expand...
Click to collapse
You Forgot to make them or what??

YSH ALSAGER said:
Guide has been updated !
Add Nokia X Partitions & Instructions
Thanks @ani00
Click to expand...
Click to collapse
Yeah, i was waiting for it.
Sent from my ASUS_X014D using Tapatalk

YSH ALSAGER said:
You Forgot to make them or what??
Click to expand...
Click to collapse
I make them, but i forget to backup

vatva69 said:
I make them, but i forget to backup
Click to expand...
Click to collapse
Why man! You shouldn't have done this!
Sorry but I think you lost your iemi

I have a mmcplk0 backup but cannot restore because my pc dont detect my phone

[GSI][ANDROID 12 STABLE] Android 12 and any GSI larger than 2.6GB

If you need help, feel free to post logs here. For more discussions about Android 12/GSIs join the telegram group!!
*REQUIRED FOR GSI* Follow the guide I made here to increase your system partition.
Click to expand...
Click to collapse
Download Android 12 Stable (Pixel 4a) GSI here: Direct link.
You don't need Gapps, they are preloaded.
Click to expand...
Click to collapse
Make sure to use Android 11 as base before flashing the GSI.
After that, you can install any GSI/flash any size Gapps without issue.
Reboot into fastboot mode.
Wipe your data partition: fastboot format:ext4 userdata
Clean cache and factory reset: fastboot -w
flash the GSI: fastboot flash system_a path/to/system.img
flash the GSI in other slot: fastboot flash system_b path/to/system.img
Test boot.
If it doesn't boot, download vbmeta for your device and flash in fastboot mode.
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot -w
Bugs:
No sound in call.
Some fixes:
Install GMS with adb install -r -d path/to/gms.apk to login to Google (not necessary anymore)
After flashing system image, don't reboot into system, immediately boot into TWRP and flash this file! This is necessary to disable encryption, so TWRP can boot successfully.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download

@Dollscythe
Appreciate the resize guide, especially as i like a full GApps install
But the ROM is impossible to download it seems...
Note: Im able to download other files at SF
Update: Finally found a working mirror - for anyone else try the Gigenet mirror (Chicago), by clicking "Problems Downloading"

Dollscythe said:
If you need help, join the telegram group.
Follow the guide I made here to increase your system partition.
USE STOCK RECOVERY!!!!!!!!
After that, you can install any GSI/flash any size Gapps without issue.
Download Android 12 Beta 3.1 GSI here: Direct link
You don't need Gapps, they are preloaded.
Reboot into fastboot mode.
Wipe your data partition: fastboot format:ext4 userdata
Clean cache and factory reset: fastboot -w
flash the GSI: fastboot flash system_a path/to/system.img
flash the GSI in other slot: flash system_b path/to/system.img
Test boot.
If it doesn't boot, flash this file in fastboot mode.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w
View attachment 5371367View attachment 5371395View attachment 5371423View attachment 5371425View attachment 5371427View attachment 5371429View attachment 5371431View attachment 5371433
Click to expand...
Click to collapse
Be great to know who's working who no on this rom. Thank you

irmas5 said:
Be great to know who's working who no on this rom. Thank you
Click to expand...
Click to collapse
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.

Wait... Does it for Pixel 3 but not Pixel 2 XL?

123哆3 said:
Wait... Does it for Pixel 3 but not Pixel 2 XL?
Click to expand...
Click to collapse
This guide is for pixel 2xl.
the GSI is ported from pixel 3 android S beta 3.1, but it works on pixel 2xl and all A/B devices.

Dollscythe said:
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.
Click to expand...
Click to collapse
it's necessary resize system partition? i'm scared to brick phone.

irmas5 said:
it's necessary resize system partition? i'm scared to brick phone.
Click to expand...
Click to collapse
for android 12 and some GSI, yes.

Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there's no sound! Any devs can chime in and help?

Dollscythe said:
Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there's no sound! Any devs can chime in and help?
Click to expand...
Click to collapse
tryed repart and get a bootloop. deleting partition disconected phone from laptop, Tryed flash via deuces script. showing installed, restarting, but never not booting. stuck at google logo. Can you help me please?

irmas5 said:
tryed repart and get a bootloop. deleting partition disconected phone from laptop, Tryed flash via deuces script. showing installed, restarting, but never not booting. stuck at google logo. Can you help me please?
Click to expand...
Click to collapse
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda

Dollscythe said:
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda
Click to expand...
Click to collapse
PS C:\platform-tools> adb push "C:\Users\irmas\Desktop\Pixel 2 xl\parted"/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
(parted)

I fixed.

irmas5 said:
PS C:\platform-tools> adb push "C:\Users\irmas\Desktop\Pixel 2 xl\parted"/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
(parted)
Click to expand...
Click to collapse
You didnt finish the partitions.
there's supposed to be aes_b, and userdata, etc.
you didnt follow the tutorial properly

plus, from what you sent me, your system is still 2.6 GB. you didnt properly finish deleting the partitions with 'rm' command. you stopped at aes_b.

Dollscythe said:
plus, from what you sent me, your system is still 2.6 GB. you didnt properly finish deleting the partitions with 'rm' command. you stopped at aes_b.
Click to expand...
Click to collapse
I restarted again everything from begining and now goes well. Now flashed proton aosp and booting. now showing
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 3269MB 3100MB ext2 system_a
3269MB 3269MB 459kB Free Space
8 3269MB 6369MB 3100MB ext2 system_b
9 6369MB 6379MB 9953kB pstore
10 6379MB 6380MB 999kB aes_a
11 6380MB 6381MB 999kB aes_b
12 6381MB 6391MB 9998kB align_parti
6391MB 6391MB 69.6kB Free Space
13 6391MB 62.5GB 56.1GB ext4 userdata
62.5GB 62.5GB 12.3kB Free Space

73sydney said:
@Dollscythe
Appreciate the resize guide, especially as i like a full GApps install
But the ROM is impossible to download it seems...
Note: Im able to download other files at SF
Update: Finally found a working mirror - for anyone else try the Gigenet mirror (Chicago), by clicking "Problems Downloading"
Click to expand...
Click to collapse
since opengapps is back, this guide is perfect to flash the highest gapps package possible. i have 4GB system partition XD

134|taimen:/ # parted /dev/block/sda
Warning: Device /dev/block/sda has a logical sector size of 4096. Not all parts
of GNU Parted support this at the moment, and the working code is HIGHLY
EXPERIMENTAL.
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
p free
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
What caused this？？？？

make sure to push parted again and give it chmod perms (even if you did it before.)

This tutorial only applies to Taimen (2XL).
Can this operation not be performed in win10 environment