Device: Teclast P78HD tablet, Allwinner A31 SoC, Android 4.4.2 (rooted) :::: Software: Busybox X (with fdisk, vi, etc.)
The Teclast P78HD tablet has a small 8GB internal eMMC SDcard with an external microSD slot. In order to best make use of the Link2SD utility, I chose to split in half the almost empty 4.7GB (usable) internal SD FAT32 partition and then format the new (primary) second partition to EXT2 EXT3 or EXT4 as used by the Link2SD app.
I used Busybox X to fdisk /dev/block/mmcblk0 ( /mnt/sdcard )
{
"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"
}
After rebooting, the DiskInfo app showed P1 ( mmcblk0p1 ) partition had shrunk to 2.4GB and, as expected, a new (unmounted) 2.3GB P4 ( mmblk0p4 , type 83, Linux ) was there too.
Connecting to a PC vis USB, I tried to format P4 to ext4 using MiniTool Partitioner (Windows) but it did not see the new partition, I then tried Gparted under Linux but it indicated that neither P1 or P4 existed. Gparted just showed a large 4.7GB "unallocated" block.
[ QUESTIONS ]
1. How do I format the new P4 mmblk0p4 partition to EXT4 using Busybox X on the tablet itself ?
2. Should I use some sort of fsck command to fix any side effects of simply truncating the original P1 mmblk0p1 FAT32 partition ?
3. What entry should I add to the tablet's /fstab.sun6i file shown below to make it automount at boot time ?
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/by-name/system /system ext4 ro wait
/dev/block/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/databk /databk ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1 wait,check
/dev/block/by-name/data /data ext4 noatime,nosuid,nodev,nomblk_io_submit,barrier=1,noauto_da_alloc wait,check,encryptable=/dev/block/by-name/databk
/devices/virtual/block/nandj /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host /mnt/sdcard vfat rw,relatime,fmask=0000,dmask=0000 wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=extsd:auto
/devices/platform/sw-ehci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw_hcd_host0 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
/devices/platform/sw-ohci.1 /mnt/usbhost1 vfat rw,relatime,fmask=0000,dmask=0000 wait,check,voldmanaged=usbhost1:auto
BTW, despite the tablet's fstab entries, there is no /devices/platform directory but there is a /sys/devices/platform directory. Also note that sdcard0 and sdcard1 seem to point to the same place with the same files. I assume that my new partition should point to /storage/sdcard2
Did you ever figure it out? Thinking about splitting my internal storage and looking up for all the info I can find....
Related
Do any of you have any suggestions on how to do this? I ran parted via ADB on my 8GB tablet's internal storage (/dev/block/mmcblk0)
Code:
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 27.3MB 2097kB SBL1
3 27.3MB 29.4MB 2097kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 789MB 734MB ext4 CACHE
8 789MB 810MB 21.0MB MODEM
9 810MB 2278MB 1468MB ext4 FACTORYFS
10 2278MB 7281MB 5004MB ext4 DATAFS
11 7281MB 7818MB 537MB ext4 HIDDEN
I knew more or less what each partition did but was curious about "HIDDEN" so I mounted it to see what was there. All that was in that partition is Retail.apk (its the "Demo Mode" that runs when the tablet is sitting at Best Buy) and the sample multimedia files used in the demo. In total these files were less than 100MB and the multimedia already copied on the /sdcard/Samsung directory in the main storage.
537MB is quite significant considering how littte space there is on this 8GB model? The next time I do a factory reset can I just delete "HIDDEN" and DATAFS and create a new larger DATAFS partition with no ill effects? I'm thinking this would work because they are contiguous and enlarging DATAFS would not change its partition number so the mounting scripts during the boot process wouldn't get thrown off.
Are there any other suggestions on how I could reclaim 537 MB of internal storage?
I've done it successfully. delete p9,p10,p11 and recreate them in new size.
parted can only create ext2 partition, need tune2fs and e2fsck to convert ext2 to ext4 fs.
first, use tar to backup the system and data partition(p9,p10) to external_sd,
after repartition can restore them.
If you want to do it, must be careful, it's VERY DANGEROUS, maybe brick your device.
my device:Samsung Galaxy Tab2 P3110, CM 10.1.3RC2
{
"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"
}
For more detail you can have a look of this, it's in chinese and for kindle fire, but i think the commandline code you can understand.
http://bbs.imp3.net/thread-10515210-1-1.html
Have you succeeded in using all memory? I repartitioned device, in clockworkmod everything is fine, but I can't access all the space from system. For DATAFS I have now 5480MB instead of 5004MB, but system says me, that internal storage is still ~5GB with only 4,5GB available. I even hard resetted device - nothing changed. How to make system see all space?
it seems that all the memory of DATAFS are ok for my p3110, have a look of the snapshots below.
i use cm 10.1.3, i dont know which rom do you flash, stock rom?
sorry it is in chinese, but you could see the numbers of memory.
No problem with language, everything is clear . I'm using stock odexed Samsung 4.1.2 rom with my own changes for tabletui and a couple of others (like editing systemui.apk). I guess, that Samsung gives fixed amount of space for /data and I haven't found where it is. Anyway, thank you for idea
probably obvious to most, but don't delete all those partitions! i was in the middle of surgery via adb, and stupidly typed
Code:
du -hs
and the device rebooted.
http://forum.xda-developers.com/galaxy-tab-2/help/argh-deleted-internal-partitions-boot-t2912866
Hi people, i want to resize the internal partition of my P3100.
Can anyone help me?
First of all I decided to put all the memory available in user app (is /data?) so I can install more app, after this I need to know ho to resize /system partition and how much space I can take (I think 500MB is perfect)
After I need to enlarge my user app partitions without lost all my app and data app
Filesystem Size Used Free Blksize
/dev 345M 48K 345M 4096
/mnt/asec 345M 0K 345M 4096
/mnt/obb 345M 0K 345M 4096
/system 1G 363M 1014M 4096
/data 4G 3G 1G 4096
/cache 688M 11M 677M 4096
/efs 19M 8M 11M 4096
/storage/sdcard0 4G 3G 1G 4096
/storage/sdcard1 29G 10G 19G 32768
P.s.: what is it /mnt/asec and mntt/obb?
Can anyone make a short info about all the filesystem?
Aliendex said:
Hi people, i want to resize the internal partition of my P3100.
Can anyone help me?
First of all I decided to put all the memory available in user app (is /data?) so I can install more app, after this I need to know ho to resize /system partition and how much space I can take (I think 500MB is perfect)
After I need to enlarge my user app partitions without lost all my app and data app
P.s.: what is it /mnt/asec and mntt/obb?
Can anyone make a short info about all the filesystem?
Click to expand...
Click to collapse
I just want my girlfriend to be in the mood tonight. I think I have a better chance of that.
DigitalMD said:
I just want my girlfriend to be in the mood tonight. I think I have a better chance of that.
Click to expand...
Click to collapse
Very helpfull
Does this guide works?
[HOW-TO] Easily resize system + data partition!
The situation after 2 months is this:
System storage: 342MB used of 1024MB
Internal storage: 1.8GB used of 4.6GB
If i resize the system partition I can have a total of 5.1GB / 5.3GB for user apps
:cyclops:
{
"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"
}
I added exfat support to kernel sources, then I built the kernel.
/proc/filesystems output with the new kernel.
Code:
[email protected]:/ # cat /proc/filesystem
cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev tmpfs
nodev debugfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev devpts
ext3
ext2
ext4
nodev ramfs
vfat
[SIZE="5"][B]exfat[/B][/SIZE]
nodev cifs
ntfs
fuseblk
nodev fuse
nodev fusectl
nodev selinuxfs
[email protected]:/ #
I can mount exfat formated pendrives/flashdrives with read and write support. If SELinux set to enforced then I can't write exfat, therefore set SELinux to permissive by
Code:
# setencorfce 0
command.
Here come the problems. If I mount the flashdrive with the Terminal app then the drive is only accessable in the Terminal app and only as su. If I am not su in the Terminal app and type "mount" I can't even see the flashdrive in the mount table, but if I do the same thing as su then the flashdrive is there in the mount table. I checked the folder where I mounted the flasdrive with es file explorer, but I can't see anything.
Then I tried to mount the flashdrive with scriptmanager. I wrote a script which mounts the drive. The drive mounted perfectly and I can acces to the files but only in the scriptmanager app built in filexplorer. The built in terminal in scriptmanager app showes the flashdrive mountpoint in the mount table after issuing "mount" command, but the "mount" command in the Terminal app doesn't show it.
For some reasone the mounting is only lives in that app which mounted the flashdrive. For the other apps the mounting is never happend.
I tried StickMount with mount.exfat-fuse binary, and it worked perfectly the mount were available for all apps, but if I just mount the exfat formated flashdrive using only the mount.exfat-fuse binary the same thing happens just like with "mount -t exfat......" command.
Anyone has any idea why this happening?
Download link for boot.img
Edit: I tested a fat32 formated flashdrive to check is this thing happens only with exfat, but I get the same problem.
I run this command in Terminal app: mount -t vfat path-to-device path-to-mount-pount
but the same thing happens.
Here I run the mount command as su
{
"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"
}
and here without su
Hello,
I got stuck and I need some help.
The phone is ZTE v987. There was bgcngm's ROM V4.0B0MOD inside.
I pulled-out-&-pushed-in the battery and after boot there was a prompt that my data needed to be erased. (I'm not excatly sure what it was). I freaked out. Turned off and boot into recovery mode (vol up + power). Performed factory reset and tried to restore backup. It didn't work. I got messages:
Can't mount /system!
Can't mount /data!
Can't mount /cache!
Click to expand...
Click to collapse
So I tried to format all of the above. Then I tried to restore individually /system, /data, /cache. All the same.
When I enter the Recovery I get errors like here:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
There are mentioned some apps like Heimdall but I couldn't find a version for my device and I'm not exactly sure what I should do.
What's more, I found info about eMMC damage and followed the link to check if my eMMC was good or bad.
I typed the command and the output was empty:
adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
~ #
Click to expand...
Click to collapse
I read somewhere it's possible that I don't have grep installed (maybe because I wiped the data).
So I tried another command to list the eMMC-chip partition info:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Warning: ignoring extra data in partition table 5
Warning: ignoring extra data in partition table 5
Disk /dev/block/mmcblk0: 3853 MB, 3853516800 bytes
1 heads, 16 sectors/track, 470400 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 65 64 2147483647+ 5 Extended
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 1665 2944 10240 83 Linux
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 2945 4224 10240 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 5825 6592 6144 83 Linux
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 8385 91584 665600 83 Linux
/dev/block/mmcblk0p6 238785 64 2145573887+ 83 Linux
~ #
Click to expand...
Click to collapse
I also tried to mount /system and /data in adb but it failed:
~ # mount /system
mount /system
mount: mounting /[email protected] on /system failed: Invalid argument
~ # mount /data
mount /data
mount: mounting /[email protected] on /data failed: Invalid argument
Click to expand...
Click to collapse
I've also downloaded the ROM and tried to install from SD.
{
"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"
}
I've saved the log and here are bottom lines:
Updating kernel
open emmc partition "boot"
contents of partition "boot" didn't match EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd36c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd36c50c41b
file "EMMC:boot:4941824:a63fb5e2f91e9c21ae76325d15d98fd36c50c41b:4941824:a63fb5e2f91e9c21ae76325d15d98fd36c50c41b" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
Flashing partition: BOOT
script aborted (no error message)
script aborted (no error message)
Installer Error (Status 7)
Click to expand...
Click to collapse
Also I've got recovery.log but it's a long one and can paste here if it is needed.
I didn't try to flash trough SP Flash Tool anything because I didn't want to make things worse.
That's all the info I could gather. I don't know if it is helpful at all but I've run out of clues.
I'd be very grateful for any help.
PS. Right now I'm not able to charge the battery. For one second the red light blinks and then the screen with battery with red strip at the bottom appears and I don't believe it's charging.
I created an issue ( - github.com/meefik/linuxdeploy/issues/820 - and asked on Android Enthusiasts - android.stackexchange.com/questions/179324/linux-deploy-ext4-and-adoptable-storage) in the Linux Deploy project.
I have a smartphone with the following settings:
{
"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"
}
And the following SD:
Ok, it's not a good SD, but that's what I have for today...
I was using SD as an extension to internal storage, and I was able to store applications and files there normally.
I would like to use Kali Linux through Linux Deploy (if there is no other way), but the system can only have a maximum of 4GB (github.com/meefik/linuxdeploy/issues/395#issuecomment-177475166) per account of the created .img file and the format of the card, which is very little in my opinion.
So I tried to follow this tutorial (github.com/meefik/linuxdeploy/wiki/Installing-Kali-Linux-Guide) for an installation with more space for the operating system.
I created a three partitions:
Fat32 to continue using on my smartphone as before (with less space of course);
An additional swap...
And an ext4 for the operating system installation.
I've ejected the ext4 partition to install Kali Linux. And everything worked perfectly!
Well... Almost everything!
Kali Linux was working just the way I wanted it, but when I tried to use my smartphone as before, I realized that I could no longer transfer my applications to the fat32 partition I created for it.
The option to transfer applications to SD is no longer displayed.
I tried to transform part of SD as Adoptable Storage again but do it directly from the smartphone, formatting all the storage, undoing all created partitions.
I then followed this answer (android.stackexchange.com/a/146529/228277 - both with adb, and with Root Essentials). Which again undid my partitions. But I re-did it again following the following steps:
Format everything and use 50% for Adoptable Storage (by adb or Root Essentials).
Remove the SD from the smartphone and insert it into the computer to create the other partitions (ext4) with MiniTool (minitool.com/partition-manager/partition-wizard-home.html) because Android Partition Tool (AParted - play.google.com/store/apps/details?id=com.sylkat.AParted) was not able to do this.
Ok, now I can transfer my applications to SD, and I also have the ext4 partition for installing Kali Linux, but now Linux Deploy can not see this partition mounted or ejected by Android.
Monted:
Code:
[12:36:31] >>> status
[12:36:32] Device: MotoG3
[12:36:32] Android: 7.1.2
[12:36:32] Architecture: armv7l
[12:36:32] Kernel: 3.10.49-MPI24.241-2.35-1-g4023d70
[12:36:32] Memory: 38/898 MB
[12:36:32] Swap: 273/511 MB
[12:36:32] SELinux: yes
[12:36:32] Loop devices: yes
[12:36:32] Support binfmt_misc: no
[12:36:32] Supported FS: ext2 ext3 ext4 f2fs fuseblk vfat
[12:36:32] Installed system: unknown
[12:36:32] Status of components:
[12:36:32] :: extra/dbus ... stopped
[12:36:32] :: extra/ssh ... stopped
[12:36:32] :: graphics/vnc ... stopped
[12:36:32] Mounted parts:
[12:36:32] ...nothing mounted
[12:36:32] Available mount points:
[12:36:33] * /system 0.9/2.2 GB (ext4)
[12:36:33] * /data 4.5/11.8 GB (f2fs)
[12:36:33] * /cache 0.2/0.2 GB (ext4)
[12:36:33] * /fsg 0.0/0.0 GB (ext4)
[12:36:33] * /firmware 0.0/0.0 GB (ext4)
[12:36:33] * /persist 0.0/0.0 GB (ext4)
[12:36:33] * /mnt/runtime/default/emulated 4.5/11.8 GB (sdcardfs)
[12:36:33] * /storage/emulated 4.5/11.8 GB (sdcardfs)
[12:36:33] * /mnt/runtime/read/emulated 4.5/11.8 GB (sdcardfs)
[12:36:33] * /mnt/runtime/write/emulated 4.5/11.8 GB (sdcardfs)
[12:36:33] * /mnt/media_rw/f86f8583-23fb-d201-f063-858323fbd201 13.0/13.7 GB (ext4)
[12:36:33] * /mnt/runtime/default/f86f8583-23fb-d201-f063-858323fbd201 13.0/13.7 GB (sdcardfs)
[12:36:33] * /storage/f86f8583-23fb-d201-f063-858323fbd201 13.0/13.7 GB (sdcardfs)
[12:36:33] * /mnt/runtime/read/f86f8583-23fb-d201-f063-858323fbd201 13.0/13.7 GB (sdcardfs)
[12:36:33] * /mnt/runtime/write/f86f8583-23fb-d201-f063-858323fbd201 13.0/13.7 GB (sdcardfs)
[12:36:33] * /mnt/expand/bd43c04c-2500-40bd-9325-1de5ae577eb6 14.2/14.8 GB (f2fs)
[12:36:33] Available partitions:
[12:36:34] ...no available partitions
[12:36:34] <<< status
Ejected:
Code:
[12:39:49] >>> status
[12:39:49] Device: MotoG3
[12:39:49] Android: 7.1.2
[12:39:49] Architecture: armv7l
[12:39:49] Kernel: 3.10.49-MPI24.241-2.35-1-g4023d70
[12:39:49] Memory: 42/898 MB
[12:39:49] Swap: 216/511 MB
[12:39:49] SELinux: yes
[12:39:49] Loop devices: yes
[12:39:49] Support binfmt_misc: no
[12:39:49] Supported FS: ext2 ext3 ext4 f2fs fuseblk vfat
[12:39:49] Installed system: unknown
[12:39:49] Status of components:
[12:39:49] :: extra/dbus ... stopped
[12:39:49] :: extra/ssh ... stopped
[12:39:49] :: graphics/vnc ... stopped
[12:39:49] Mounted parts:
[12:39:49] ...nothing mounted
[12:39:49] Available mount points:
[12:39:49] * /system 0.9/2.2 GB (ext4)
[12:39:49] * /data 4.5/11.8 GB (f2fs)
[12:39:50] * /cache 0.2/0.2 GB (ext4)
[12:39:50] * /fsg 0.0/0.0 GB (ext4)
[12:39:50] * /firmware 0.0/0.0 GB (ext4)
[12:39:50] * /persist 0.0/0.0 GB (ext4)
[12:39:50] * /mnt/runtime/default/emulated 4.5/11.8 GB (sdcardfs)
[12:39:50] * /storage/emulated 4.5/11.8 GB (sdcardfs)
[12:39:50] * /mnt/runtime/read/emulated 4.5/11.8 GB (sdcardfs)
[12:39:50] * /mnt/runtime/write/emulated 4.5/11.8 GB (sdcardfs)
[12:39:50] * /mnt/expand/bd43c04c-2500-40bd-9325-1de5ae577eb6 14.2/14.8 GB (f2fs)
[12:39:50] Available partitions:
[12:39:50] ...no available partitions
[12:39:50] <<< status
Is it possible to do what I'm trying? Use half the SD as Adoptable Storage and the rest as ext4 to install Kali Linux? Am I forgetting to set something up?
Click to expand...
Click to collapse