Develop Bugs

Shell commands

Here you will find a list of some shell commands you can use on your android phone, either with a terminal emulator or over adb shell from your PC. I would recommend using connectbot as your terminal emulator.
The commands listed are in no way limited to what is described below, I am just scraping the surface here. For more information on these commands type ' --help' after your command, e.g. 'mount --help' or use google, most of these commands are exactly the same as what you would find on any Linux system, so you will find EXTENSIVE information on the web if you want to know more.
These commands work on my HTC Desire running Cyanogenmod 6 (Android 2.2), most, if not all of them should work on other devices and/or roms.
If you have any suggestions post them below or pm me and I will edit this post to include them.
Notes
Most of these commands require root privileges, type su first.
Everything after a # is a not and not a part of the command.
busybox
What it does
Provides a selection of commands not built into android by default.
Example(s)
busybox cp a b
Notes
busybox is included in most custom roms and has aliases set up so you do not need to type busybox before the commands eg, 'cp' is the same as 'busybox cp' in most custom roms.
cat
What it does
Prints the contents of a (text)file onscreen.
Example(s)
cat file
cd
What it does
Changes the current directory. You may find it easier to change to the directory you will be working in before issuing other commands so you dont need to include the full path in your commands.
Example(s)
cd .. # Go up 1 directory level, eg go from '/sdcard/download/ to '/sdcard'.
cd /sd-ext # Change to '/sd-ext'.
chmod
What it does
Makes a file executable
Example(s)
chmod 755 /data/bin/yourbin
cp
What it does
Copies files/directories
Example(s)
cp filea fileb
cp -rf directorya directoryb # Copy entire directory recursively and forces copy.
df
What it does
Displays information on all mounted filesystems (free space).
Example(s)
df -hm # Show disk usage in human readable format in Megabytes.
du
What it does
Diplays the size of files/directories.
Example(s)
du -md 1 # Prints the size of all directories in Megebytes.
du -sh file # Prints the size of file in human readable format.
du -sh directory # Prints the size of directory in human readable format.
export
What it does
Sets environment variables.
Example(s)
export PATH=$PATH;/sd-ext/bin;
free
What it does
Display the amount of free and used system memory
losetup
What it does
Associates loop disk images with loop devices.
Example(s)
losetup /sdcard/disk.img /dev/block/loop7
Notes
Android 2.2's implementation of apps2sd uses one loop device for each app saved to SD. There are 8 loop devives by default (loop0-loop7) so if you have 8 or more apps saved to SD you will not be able to use this command. There is no issue when using 'oldschool a2sd'
ls
What it does
List Directory contents.
Example(s)
ls -a # List directory contents including hidden contents.
mount
What it does
Mounts a filesystem.
Example(s)
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 # Remounts /system as writable.
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 # Remounts /system as read only.
mount -t ext2 /dev/block/loop6 /sdcard/disk # Mount loop6 on /sdcard/disk.
mount /sd-ext /sdcard/sd-ext # Mount /sd-ext on /sdcard/sd-ext.
Notes
On other devices it may be possible to mount disk images without going through losetup and using the option -loop in mount instead.
If you are having trouble with mount try using busybox mount instead, the busybox version seems more capable than the one shipped with Android.
mv
What it does
Move/rename files/directories
Example(s)
mv download/file stuff/file
mv picture4.jpg mydog.jpg
ping
What it does
Pings a server to check for conectivity.
Example(s)
ping -c 5 http://www.google.com # Ping google 5 times
Notes
if you do not include the -c option ping will work indefinatly.
pwd
What it does
Prints the current directory.
rm
What it does
Remove file/directory.
Example(s)
rm file
rm -rf directory # Delete a directory and its contents.
rmdir
What it does
Removes a directory
Example(s)
rmdir emptydir
Notes
If a directory has contents us 'rm -rf' instad.
su
What it does
Gives you root privelages.
touch
What it does
Makes an empty file
Example(s)
touch file.txt
wget
What it does
Download things from http or ftp.
Example(s)
wget http://www.google.com

Excellent, thank you.
Just what the doctor ordered for n00bs like me

[Q] extend internal memory

hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??

royalrose said:
hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??
Click to expand...
Click to collapse
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.

royalrose said:
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
Click to expand...
Click to collapse
For LeeDroid 2.4 you might look here. Beware that there may be some issues ... It's sort of experimental !

bobsie41 said:
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.
Click to expand...
Click to collapse
thanx bro but as i'm new in this site i can't post any question there
i expereinced many kind of roms(include d2xt) but i had the same problem

Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.

mercianary said:
Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.
Click to expand...
Click to collapse
thanks but I think there should be an easier way too.

no answer?????

royalrose said:
no answer?????
Click to expand...
Click to collapse
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690

snakeeyes21 said:
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690
Click to expand...
Click to collapse
i had that rom too.it's so nice and fast but after instaling 15 apps or game my internal memory became full again.
is it usual??

Do you have an EXT partition on your sdcard?

cgmorris89 said:
Do you have an EXT partition on your sdcard?
Click to expand...
Click to collapse
yes bro
both ext 3 & 4
but still i have low memory

stumped
are your partitions in the correct order?

cgmorris89 said:
stumped
are your partitions in the correct order?
Click to expand...
Click to collapse
I think it's
usualy it's in this form
first fat32(6.5g)
2nd ext2(500mb)
3rd ext4(500mb)
4th swap(500mb)

You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM

Try this:
Download a terminal app from the market.
Open it, allow SU permissions.
Type "a2sd cachesd"
The phone should now reboot.
And, if need be, try my guide here.
http://androidforums.com/desire-tip...ed-device-noobs-guide-updated-09-02-11-a.html

sibere said:
You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM
Click to expand...
Click to collapse
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....

royalrose said:
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
Click to expand...
Click to collapse
Here is the problem, your recovery doesn't have sd-ext directory. You must create it with a mkdir /sd-ext command
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....
Click to expand...
Click to collapse
How this is the old way with an ext2 file mounted via a loop device. Now it's an ext4 partition of max 2GB. Default is without journal but informations are provided to use journal for safety specially on AOSP ROMs.
Droidzone has created also some ready 2 flash ZIP files for both AOSP and SENSE ROMS. Check-out the OP page again.

thanks for tips

[Q]: repartitioning hiccup [solved]

Ok, I posted this question in 2 other threads that had info on the process (will delete the posts when this one goes live), but no responses after a couple of days. One of them is old though.
I have TWRP 2.1.1 installed. ADB seems to be working normally. Superuser is working fine after booting to android. I'm running a custom ICS ROM (Energy); read that stock ROM can cause issues repartitioning.
I started with this How-to as it looked very straight forward.
I start throwing the commands at ADB and here's what I got for my efforts:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ # cd /data
cd /data
/data # ls
ls
/data #
decided to go ahead and check the mount command:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
~ #
and parted just for giggles:
Code:
~ # parted /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)
Ok, so that much worked. Now I tried to shrink 12 so I could double the size of 9. I want to get Switchme set up for his/her profiles and 500MB just isn't going to cut it.
That's when I hit a brick wall:
Code:
(parted) resize 12 2846 7690
resize 12 2846 7690
resize 12 2846 7690
Error: Unable to satisfy all constraints on the partition.
(parted)

One thing that jumps out at me right away is this:
Code:
adb shell
~ # su
su/sbin/sh: su: not found
It seems you are not actually rooted.
To check, enter:
Code:
adb shell
ls /system/xbin
If you don't see "su" in the list, then you don't have root permissions, which would probably prevent you from doing what you need to accomplish.

That's what I was wondering, but apps are able to ask for and receive root permission from within the ROM. SU does exist, just not where the shell is looking when in recovery.
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # ls /system/xbin
ls /system/xbin
ls: /system/xbin: No such file or directory
~ #
I did an ls /system/xbin from adb shell and from Terminal Emulator within Android and both returned a long list containing SU.

TWRP provides an unsecured (unsecure? insecure?) boot. Whatever the terminology, it gives you immediate access to root privileges. Apparently CWMR (which was used in the OP of the thread you used) does not and so that author had to use su. For TWRP, it's not necessary and not even available. You already have root privileges as indicated by the hash prompt.
I tried resizing my /sdcard partition and it worked fine with the command you tried. I'm not sure what's going on with your storage device that it wouldn't resize it for you. At first I thought it might be mounted, but your mount command shows otherwise and parted gave me a different error when I had it mounted.
I don't know if this is going to help you, but you might try giving it the "MB" suffix in your numbers....
Code:
resize 12 2846MB 7690MB
Maybe even try changing units to bytes and giving the resize command byte sized boundaries.
Code:
unit B
print
will show you the numbers in bytes and you'd have to use the "B" suffix as in the "MB" example above.
If none of that works, you can always remove and remake the partition. For example...
Code:
rm 12
mkpartfs primary fat32 <start> <end>
name 12 media
You'd obviously need to insert acceptable boundaries for the start and end into that command. It might even be easier to just remove all 9, 10, 11, and 12 and remake/rename them, but remember 9, 10, and 11 are ext4 filesystems so the above mkpartfs command needs to be tweaked accordingly.
One thing I noticed while I was experimenting with the partition table this morning... all of the existing partitions have been allocated in 128MB chunks. I have no idea if this affects performance. I'd imagine you'd only need to stick to the 512B sector sizes, but you might want to stay with those conventions if it's not too inconvenient for you.
If you mess up the partition table, you can always go back to fastboot mode in FFF and use the...
Code:
fastboot oem format
feature to bring your partition table back to stock.
Good luck.

Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Wow, excellent response. Just the kind of detail I was hoping to get and it confirmed a few suspicions I had while searching the kindle threads. I'll report back on my degree of success when I get some free time to tinker.
I have a nandroid backup (also saved to PC) just in case and saved the partition table as-found. If everything gets hosed and I do an oem format I can just restore that and go or try from square one again, yes?
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I'd say that's a safe bet. Just be very careful about handling partitions 1 and 2 because those two are critical to getting anything to boot on your device. As long as you don't touch the xloader in partition 1 and have FFF installed in partition 2, you can rebuild the rest of it.... in theory. I only say "in theory" because I've never actually had to do it, but I don't see why it wouldn't work.
A couple of additional things I figured out after you put me to work with parted....
It looks like parted doesn't know how to make an ext4 filesystem, so mkpartfs balks if you tell it to make one. You'll have to use mkpart which just makes the partition, but not the filesystem. Then exit out of parted and use mke2fs, which despite its name knows how to make an ext4 filesystem. Like this for the cache partition...
Code:
mke2fs -T ext4 /dev/block/mmcblk0p11
The other thing is that parted sets a "msftres" flag on the fat32 filesystem it makes. The flag apparently is to tell the OS that it's reserved for Windows, or something like that. I didn't have a problem mounting in Linux and MacOS X, but the stuff I've read seems to indicate that older OS's have a problem with it. Unfortunately, the version of busybox on TWRP doesn't have a module to make a fat32 filesystem. I'm looking around to see how to get around that.
In any case, this should get you most of the way there. I'll followup if I find something out.

Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb

ProfEngr said:
Ok. I used to run n*x, but use only M$ right now. Haven't touched a 'mac' since Jr High (IIgs)
Sent from my TBolt with the XDA App using 1 opposable thumb
Click to expand...
Click to collapse
I have a IIgs sitting in the basement... but it's not a mac, it's an Apple ][.
Found the last piece...
Code:
/system/bin/newfs_msdos /dev/block/mmcblk0p12
will make a fat32 filesystem correctly. I think that's all you'll need.
EDIT: OK, I must have been half asleep when I posted the above. That binary is on the stock system software I had mounted. There's nothing on TWRP to create a fat32 filesystem correctly.

Yeah, ][e was my first computer that didn't crash at the drop of a keystroke. Had an Adam tape drive model, but it froze up constantly.
Sent from my TBolt with the XDA App using 1 opposable thumb

So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.

no device found
ProfEngr said:
So, I met with success following the repartition thread and tweaking it with your suggestions. I didn't quite move and many MB around as I thought, but it was enough to move me a little farther down the road with SwitchMe. At least it doesn't tell me I don't have enough memory for a 2nd profile now.
I still think it has issues with ICS or EnergyROM itself. When I created a new profile and rebooted to it I was stuck on Nova launcher instead of GO like the main profile. Strange.
I'll consider this thread to have fulfilled its usefulness. Thanks again for the help.
Click to expand...
Click to collapse
I get
(parted)
Error: No device found
Retry/Cancel

size partition for BoardConfig.mk

Hi
this is from the BoardConfig.mk
Code:
# fix this up by examining /proc/mtd on a running device
BOARD_BOOTIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_USERDATAIMAGE_PARTITION_SIZE := 0x105c0000
BOARD_FLASH_BLOCK_SIZE := 131072
I want to find the actual size partition adb shell cat /proc/mtd" or "adb shell cat /proc/emmc" or "adb shell cat /proc/dumchar_info" doesn't work !

Steps:
*root your device;
*install TWRP or CWM for your device ;
*install busybox tools ( Busybox Free Goolge Play);
After this, enter to recovery mode. Mount /system into TWRP or CWM.
Plug USB cabe, and in your computer input these commands:
adb devices --> verify if device is connected
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Now, insert this command:
parted /dev/block/mmcblk0 unit B print
The output is similar :
Code:
~ # parted /dev/block/mmcblk0 unit B print
Model: MMC 008GE0 (sd/mmc)
Disk /dev/block/mmcblk0: 7818182656B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 4194304B 6291455B 2097152B MRD
2 6291456B 8388607B 2097152B MRD_BK
3 8388608B 10485759B 2097152B MEP2
4 10485760B 31457279B 20971520B ext4 EFS
5 31457280B 46137343B 14680064B Reserved
6 46661632B 48234495B 1572864B LOKE_2ND
7 48758784B 50331647B 1572864B LOKE_1ST
8 50331648B 67108863B 16777216B PARAM
9 67108864B 83886079B 16777216B RECOVERY
10 83886080B 100663295B 16777216B KERNEL
11 100663296B 125829119B 25165824B MODEM
12 125829120B 142606335B 16777216B ext4 NVM
13 142606336B 352321535B 209715200B ext4 HIDDEN
14 352321536B 713031679B 360710144B ext4 CACHE
15 713031680B 2307915775B 1594884096B ext4 SYSTEM
16 2307915776B 7817134079B 5509218304B ext4 USER
Use the column size to fill in the BoardConfig values.
The first column it refers to the mount point.
Ex.: the kernel partition has 16.777.216 bytes mounted in /dev/block/mmcblk0p10
Links references:
http://forum.xda-developers.com/showthread.php?t=2450045
http://stackoverflow.com/questions/...ormation-for-android-device/15639867#15639867
http://forum.xda-developers.com/attachment.php?attachmentid=2397268&d=1384688569

naufragoweb said:
Now, install parted into /system/bin:
adb push <path-to-file>/parted /system/bin
Click to expand...
Click to collapse
Path to.. what file?

Nicofisi said:
Path to.. what file?
Click to expand...
Click to collapse
Path to the "parted" file in your PC

How to unpack & repack GSIs? I want to edit GSIs so I can make it smaller then flash it [Question]

I want a method/tool to unpack and repack GSIs, I want to do some edits like removing unnecessary bloatware to make GSI smaller in size so I can flash it on my device. There is custom android 12 GSI I want to flash it on my device (Evolution X), it's size about 4 GB after extracting and System Image partition in my device is 3 GB and 3.5 GB after resize by TWRP recovery and still can't flash it (Size of image is larger than target device). so how can I unpack to do some edits and repack it again?

on Linux environment (ubuntu)
write the following in the terminal
Code:
mkdir folder_d
mount -o loop,rw nam_of_GSI.img folder_d
then open folder_d and delete "system_ext/apex/com.android.vndk.vXX" where xx other vndk (if your device vndk 28 then delere other files 29,30,31, 32)
then write the following in the terminal
Code:
umount d
e2fsck -f -y nam_of_GSI.img || true
resize2fs -M nam_of_GSI.img
or you can use this script
https://github.com/Abdelhay-Ali/huawei-creator/blob/android-13/run-huawei-ab-a13-yahia.sh

Abdelhay.ali said:
on Linux environment (ubuntu)
write the following in the terminal
Code:
mkdir folder_d
mount -o loop,rw nam_of_GSI.img folder_d
then open folder_d and delete "system_ext/apex/com.android.vndk.vXX" where xx other vndk (if your device vndk 28 then delere other files 29,30,31, 32)
then write the following in the terminal
Code:
umount d
e2fsck -f -y nam_of_GSI.img || true
resize2fs -M nam_of_GSI.img
or you can use this script
https://github.com/Abdelhay-Ali/huawei-creator/blob/android-13/run-huawei-ab-a13-yahia.sh
Click to expand...
Click to collapse
You Android hero! Thanks for your help.