yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy M12] Edne12803:
Does anyone knows something about this error
[Samsung Galaxy M12] physwizz:
What error?
[Samsung Galaxy M12] Edne12803:
this one... install twrp in Galaxy M12 but it starts over and over again
[Samsung Galaxy M12] physwizz:
Try using my kernel.

Just add it to your twrp
[Samsung Galaxy M12] _Osmio:
I'm trying to compile TWRP using the 12.1 branch but I'm getting this error...

I tried modifying "build/make/core/board_config.mk" so it sets it to false, and it works? but im not sure if that's the correct way to do it.

Also, the "Device a12s not found" error was ignored so it probably was intended right?

I only got this after I modified board_config.mk

Any ideas?

Computer specs (just in case) :
[Samsung Galaxy M12] _Osmio:
Tried building it and it gives me this error

( lowering the -j value didn't change anything either )

Any ideas?
[Samsung Galaxy M12] physwizz:
I used the Android 11 manifest.

The Android 12 one doesn't have a12s specs.

You are building a12s yes?

If not you need to change this line

lunch twrp_a12s-eng
[Samsung Galaxy M12] physwizz:
The Android 12 one doesn't have a12s specs.

You are building a12s yes?

If not you need to change this line

lunch twrp_a12s-eng
[Samsung Galaxy M12] Anonymous V:
hi sir im getting an error while building my twrp heres the log im stuck at the 93 percent build and i dont know what to doh

4 warnings generated. [ 93% 6651/7077] build /home/osboxes/TWRP/out/target/product/CPH1717/obj/ETC/file_contexts.bin_intermediates/file_contexts.local.tmp FAILED: /home/osboxes/TWRP/out/target/product/CPH1717/obj/ETC/file_contexts.bin_intermediates/file_contexts.local.tmp /bin/bash -c "m4 -s system/sepolicy/file_contexts /home/osboxes/TWRP/out/target/product/CPH1717/obj/ETC/sectxfile_nl_intermediates/sectxfile_nl > /home/osboxes/TWRP/out/target/product/CPH1717/obj/ETC/file_contexts.bin_intermediates/file_contexts.local.tmp" /bin/bash: line 1: m4: command not found [ 93% 6651/7077] target thumb C: libncurses_32 <= external/libncurses/ncurses/tty/tty_update.c ninja: build stopped: subcommand failed. make: *** [build/core/ninja.mk:158: ninja_wrapper] Error 1 osboxes@osboxes:~/TWRP$
[Samsung Galaxy M12] physwizz:
How much ram do you have?
[Samsung Galaxy M12] Anonymous V:
well if i talk about my pc i have exactly 8gb ram but im using Ubuntu in virtualbox which has atleast 4gb if i put the max ram in my ubuntu i can put up to 6gb but it will cause some error in my Pc sometimes thatswhy i allocate my ram in exactly 4gb
[Samsung Galaxy M12] halexys:
i got this error while building:

oot/vendor/bin/hw

[100% 15712/15712] build out/target/product/N30/recovery.img

FAILED: out/target/product/N30/recovery.img

/bin/bash -c "(out/host/linux-x86/bin/mkbootimg --kernel out/target/product/N30/kernel --ramdisk out/target/product/N30/ramdisk-rec

overy.img --cmdline \"bootopt=64S3,32N2,64N2 buildvariant=user buildvariant=eng\" --base 0x40078000 --pagesize 2048 --recovery_dtbo de

vice/doogee/N30/prebuilt/dtbo.img --os_version 11 --os_patch_level 2099-12-31 --header_version 2 --ramdisk_offset 0x11a88000 --tags_of

fset 0x07808000 --dtb device/doogee/N30/prebuilt/dtb.img --output out/target/product/N30/recovery.img ) && (size=\$(for i in out/tar

get/product/N30/recovery.img; do stat -c \"%s\" \"\$i\" | tr -d '\\n'; echo +; done; echo 0); total=\$(( \$( echo \"\$size\" ) )); pri

ntname=\$(echo -n \" out/target/product/N30/recovery.img\" | tr \" \" +); maxsize=\$(( 33554416-69632)); if [ \"\$total\" -gt \"\$ma

xsize\" ]; then echo \"error: \$printname too large (\$total > \$maxsize)\"; false; elif [ \"\$total\" -gt \$((maxsize - 32768)) ]; th

en echo \"WARNING: \$printname approaching size limit (\$total now; limit \$maxsize)\"; fi ) && (out/host/linux-x86/bin/avbtool add_ha

sh_footer --image out/target/product/N30/recovery.img --partition_size 33554416 --partition_name recovery --algorithm SHA256_RSA4096

--key external/avb/test/data/testkey_rsa4096.pem --prop com.android.build.recovery.fingerprint:\$(cat out/target/product/N30/build_fin

gerprint.txt) --prop com.android.build.boot.os_version:16.1.0 --prop com.android.build.boot.security_patch:2099-12-31 --rollback_index

1 )"

/mnt/Almacen/reco/out/host/linux-x86/bin/avbtool: Partition size of 33554416 is not a multiple of the image block size 4096.

22:34:19 ninja failed with: exit status 1

#### failed to build some targets (01:14:56 (hh:mm:ss)) ####
[Samsung Galaxy M12] physwizz:
Edit the image size so it is a multiple of 4096
[Samsung Galaxy M12] Apostalus:
all good and well, but when I get to the lunch commands, I receive the following:

device/nubia/NX709J/device.mk:24: error: PRODUCT_STATIC_BOOT_CONTROL_HAL is obsolete. Use shared library module instead. See https://android.googlesource.com/platform/build/+/master/Changes.md#PRODUCT_STATIC_BOOT_CONTROL_HAL.

What do I do From Here???
[Samsung Galaxy M12] physwizz:
I've only done samsung
[Samsung Galaxy M12] Apostalus:
but it is the same concept, ultimately. I've done it before off of a shamu twrp, however this time I wanted to build from source, and ran into this snag. please help...?
[Samsung Galaxy M12] physwizz:
PRODUCT_STATIC_BOOT_CONTROL_HAL is obsolete {#PRODUCT_STATIC_BOOT_CONTROL_HAL}

PRODUCT_STATIC_BOOT_CONTROL_HAL was the workaround to allow sideloading with statically linked boot control HAL, before shared library HALs were supported under recovery. Android Q has added such support (HALs will be loaded in passthrough mode), and the workarounds are being removed. Targets should build and install the recovery variant of boot control HAL modules into recovery image, similar to the ones installed for normal boot. See the change to crosshatch for example of this:

device/google/crosshatch/bootctrl/Android.bp for bootctrl.sdm845 building rules

device/google/crosshatch/device.mk for installing bootctrl.sdm845.recovery and android.hardware.boot@1.0-impl.recovery into recovery image
[Samsung Galaxy M12] Apostalus:
Stuck at lunch again. This time I get the following;

09:03:12 Build sandboxing disabled due to nsjail error.

In file included from build/make/core/config.mk:291:

In file included from build/make/core/envsetup.mk:266:

frameworks/base/data/sounds/AllAudio.mk:17: error: _nic.PRODUCTS.[[device/NX709J/twrp_NX709J.mk]]: "device/nubia/NX709J/device.mk" does not exist.

09:03:12 dumpvars failed with: exit status 1

Device NX709J not found. Attempting to retrieve device repository from TeamWin Github (http://github.com/TeamWin).

Repository for NX709J not found in the TeamWin Github repository list.
[Samsung Galaxy M12] Apostalus:
BTW, the file is confirmed in the folder
[Samsung Galaxy M12] physwizz:
NX709J not found in the TeamWin Github repository list.
[Samsung Galaxy M12] Don.K:
this worked but the screen was kinda messed up
[Samsung Galaxy M12] physwizz:
What device?

First you tried the one for M127 F127. Now you're trying the one for A127
[Samsung Galaxy M12] Apostalus:
That's because it isn't, yet. Got released 2022. How do I post my tree?
[Samsung Galaxy M12] physwizz:
Push it to github
[Samsung Galaxy M12] Apostalus:
GitHub - TheApostalus/android_device_nubia_NX709J

Contribute to TheApostalus/android_device_nubia_NX709J development by creating an account on GitHub.

github.com
[Samsung Galaxy M12] Apostalus:
I have been getting this when I lunch then mka recovery.img, and then I can't find the recovery image or it just doesn't exist

root@debian11:~/nx709j-twrp# lunch twrp_NX709J-eng

00:07:11 Build sandboxing disabled due to nsjail error.

Trying dependencies-only mode on a non-existing device tree?

00:07:11 Build sandboxing disabled due to nsjail error.

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=16.1.0

TARGET_PRODUCT=twrp_NX709J

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_ARCH=arm64

TARGET_ARCH_VARIANT=armv8-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=arm

TARGET_2ND_ARCH_VARIANT=armv7-a-neon

TARGET_2ND_CPU_VARIANT=generic

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-5.10.0-23-amd64-x86_64-Debian-GNU/Linux-11-(bullseye)

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=RQ1A.210205.004

OUT_DIR=out

============================================

root@debian11:~/nx709j-twrp# mka recoveryimage

00:07:20 ************************************************************

00:07:20 You are building on a machine with 15.5GB of RAM

00:07:20

00:07:20 The minimum required amount of free memory is around 16GB,

00:07:20 and even with that, some configurations may not work.

00:07:20

00:07:20 If you run into segfaults or other errors, try reducing your

00:07:20 -j value.

00:07:20 ************************************************************

00:07:20 Build sandboxing disabled due to nsjail error.

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=16.1.0

TARGET_PRODUCT=twrp_NX709J

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_ARCH=arm64

TARGET_ARCH_VARIANT=armv8-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=arm

TARGET_2ND_ARCH_VARIANT=armv7-a-neon

TARGET_2ND_CPU_VARIANT=generic

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-5.10.0-23-amd64-x86_64-Debian-GNU/Linux-11-(bullseye)

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=RQ1A.210205.004

OUT_DIR=out

============================================

ninja: no work to do.

#### build completed successfully (3 seconds) ####
[Samsung Galaxy M12] physwizz:
Where did you put the device Tree inside the twrp11 folder?
[Samsung Galaxy M12] Apostalus:
I don't even know. rebuilding it all now so I can verify
[Samsung Galaxy M12] Apostalus:
my device tree? you mean the folders with device.mk in it? /home/NX709J-twrp/device/nubia/NX709J

where should it be?
[Samsung Galaxy M12] physwizz:
Correct spot
[Samsung Galaxy M12] aminegames125:
Traceback (most recent call last):

File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main

return _run_code(code, main_globals, None,

File "/usr/lib/python3.10/runpy.py", line 86, in _run_code

exec(code, run_globals)

File "/home/amineos/TWRP/twrpdtgen/twrpdtgen/__main__.py", line 11, in <module>

main()

File "/home/amineos/TWRP/twrpdtgen/twrpdtgen/main.py", line 37, in main

device_tree = DeviceTree(image=args.image)

File "/home/amineos/TWRP/twrpdtgen/twrpdtgen/device_tree.py", line 66, in __init__

self.device_info = DeviceInfo(self.build_prop)

File "/home/amineos/.local/lib/python3.10/site-packages/sebaubuntu_libs/libandroid/device_info.py", line 117, in __init__

self.codename = self.get_first_prop(DEVICE_CODENAME)

File "/home/amineos/.local/lib/python3.10/site-packages/sebaubuntu_libs/libandroid/device_info.py", line 177, in get_first_prop

raise AssertionError(f'Property {props[0]} could not be found in build.prop')

AssertionError: Property ro.product.bootimage.device could not be found in build.prop
[Samsung Galaxy M12] Apostalus:
so then, what do I do to get it to fully produce the recovery.img file? I have a folder that says recovery, and another that says obj, so which do I use?
[Samsung Galaxy M12] Apostalus:
And what files should go into it to manually make the recovey.img?
[Samsung Galaxy M12] physwizz:
show me /home/NX709J-twrp/device/nubia/NX709J
[Samsung Galaxy M12] Apostalus:
Here you go. Sorry about the quality...
[Samsung Galaxy M12] Apostalus:
Does this look right?
[Samsung Galaxy M12] physwizz:
Yeah it looks ok
[Samsung Galaxy M12] Apostalus:
Then why isn't it making an img or even an iso file?
[Samsung Galaxy M12] physwizz:
I'm not sure
[Samsung Galaxy M12] Apostalus:
Well, that kinda sucks... Any suggestions? Maybe check out the GitHub I set up for the device tree? Is there a way to build the recovery.img manually from the files? What would that look like?
[Samsung Galaxy M12] Subaru!Natsuki:
is this only for samsung and not for mediatek chips ?
[Samsung Galaxy M12] physwizz:
It can be used for all but I give the Samsung a12s as an example
[Samsung Galaxy M12] YZBruh:
hello. I'm a bit new to this stuff... I had a question, which is in the BoardConfig.mk file BOARD_SUPER_PARTITION_SIZE and BOARD_manufacturer_DYNAMIC_PARTITIONS_SIZE Where should I extract the values that will come in the rows?
[Samsung Galaxy M12] PokemzX:
yo, what do I do with this:

# Inherit some common Omni stuff.
$(call inherit-product, vendor/omni/config/common.mk)
[Samsung Galaxy M12] physwizz:
Delete
[Samsung Galaxy M12] ZG_DEV:
Hi

I want to build twrp for Samsung A13 (a137f) but I don't know how , can u tell me how to build one for this phone ?
[Samsung Galaxy M12] physwizz:
I have built a kernel for that phone but not a twrp.

Just follow the instructions here
[Samsung Galaxy M12] ZG_DEV:
A kernel ?

Where ?

+ can u build a custom kernel for oppo a5s ?

I have got the kernel source Here
[Samsung Galaxy M12] kingkwahli:
No problems, got it done for my off brand tablet, just wanted to say that as a 13 year old, I completed this on my HP laptop running ChromeOS. Just sayin, anyone can code. Screenshots:
[Samsung Galaxy M12] physwizz:
Great work
[Samsung Galaxy M12] kh.v:
Hi all,

Any help to build twrp for Redmagic 7pro, nx709j

Here is all file i had

TWRP_nx709j - Google Drive

drive.google.com
[Samsung Galaxy M12] physwizz:
My experience is with Samsung
[Samsung Galaxy M12] MEYSAMKIA:
Here's the log file

########################################################

gitpod /workspace/empty/twrp (main) $ mka recoveryimage

build/make/core/soong_config.mk:196: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.

build/make/core/soong_config.mk:197: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=16.1.0

TARGET_PRODUCT=omni_CAP_sprout

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_ARCH=arm64

TARGET_ARCH_VARIANT=armv8-a

TARGET_CPU_VARIANT=generic

TARGET_2ND_ARCH=arm

TARGET_2ND_ARCH_VARIANT=armv7-a-neon

TARGET_2ND_CPU_VARIANT=generic

HOST_ARCH=x86_64

HOST_2ND_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-6.1.54-060154-generic-x86_64-Ubuntu-22.04.3-LTS

HOST_CROSS_OS=windows

HOST_CROSS_ARCH=x86

HOST_CROSS_2ND_ARCH=x86_64

HOST_BUILD_TYPE=release

BUILD_ID=SP2A.220405.004

OUT_DIR=out

PRODUCT_SOONG_NAMESPACES=device/hmd/CAP_sprout

============================================

[ 29% 27/93] including bootable/recovery/Android.mk ...

bootable/recovery/prebuilt/Android.mk:441: warning: vendor_hw: bootable/recovery/prebuilt/relink.sh out/target/product/CAP_sprout/recovery/root/vendor/bin/hw

[ 86% 80/93] including system/sepolicy/Android.mk ...

system/sepolicy/Android.mk:57: warning: BOARD_PLAT_PUBLIC_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PUBLIC_SEPOLICY_DIRS instead.

system/sepolicy/Android.mk:62: warning: BOARD_PLAT_PRIVATE_SEPOLICY_DIR has been deprecated. Use SYSTEM_EXT_PRIVATE_SEPOLICY_DIRS instead.

ninja: no work to do.

###################################################################################

the source: https://github.com/kinguser981/Nokia-5.3-twrp/tree/android-12.0

what is the problem??? ninja: no work to do.
[Samsung Galaxy M12] physwizz:
Hmm
[Samsung Galaxy M12] aks brar:
Do this work for every device out there?

Will it work for a/b partition device?

Can you assist me?

Thanks!
[Samsung Galaxy M12] kingkwahli:
I had the same questions.
[Samsung Galaxy M12] physwizz:
Yes it should.

I only use it for Samsung
[Samsung Galaxy M12] kingkwahli:
So I can use it for Motorola devices?
[Samsung Galaxy M12] physwizz:
Try and see
[Samsung Galaxy M12] lyinceer:
hey bro what do you mean by change omni to twrp?
[Samsung Galaxy M12] physwizz:
Just delete the word omni and type twrp
[Samsung Galaxy M12] lyinceer:
I only have these two 'Omni" in my twrp.mk

# Inherit some common Omni stuff.

PRODUCT_NAME := omni_essi

So just replace those 'omni' to'twrp' ?
[Samsung Galaxy M12] lyinceer:
Also, i got an error like this when building :
[Samsung Galaxy M12] physwizz:
Show me your device tree
[Samsung Galaxy M12] lyinceer:
GitHub - twrpdtgen/android_device_samsung_essi

Contribute to twrpdtgen/android_device_samsung_essi development by creating an account on GitHub.

github.com
[Samsung Galaxy M12] physwizz:
omni_essi.mk should be twrp_a55x.mk
[Samsung Galaxy M12] lyinceer:
yes i've renamed it to twrp_a55x.mk but as the result i got the error like before

Edit :

I also tried to manually add the repository for a55x to ".repo/local_manifests/roomservice.xml"
[Samsung Galaxy M12] physwizz:
What manifest are you using
[Samsung Galaxy M12] kevin5806:
Help with twrp for SM-A137F/DSN ?
[Samsung Galaxy M12] physwizz:
Are you going to build it?
[Samsung Galaxy M12] Matheus-TestUser1:
hi
[Samsung Galaxy M12] Matheus-TestUser1:
Please help me, please, I'm finishing a device tree, for a device that apparently doesn't have recovery.fstab and twrp.flags, how did you organize it? look how I organize this from the a135m also with exynos 850? # mount point fstype device device2 flags

# Logical partitions

/system f2fs system flags=display=system;logical,flashimg

/system ext4 system flags=display=system;logical,flashimg

/system erofs system flags=display=system;logical,flashimg

/vendor f2fs vendor flags=display=vendor;logical,flashimg

/product f2fs product flags=display=product;logical,flashimg

/odm f2fs odm flags=display=odm;logical,flashimg

# Linked partitions

/system_image emmc /dev/block/by-name/system flags=backup=0;flashimg;display="System Image"

/vendor_image emmc /dev/block/by-name/vendor flags=backup=0;flashimg;display="Vendor Image"

/product_image emmc /dev/block/by-name/product flags=backup=0;flashimg;display="Product Image"

/odm_image emmc /dev/block/by-name/odm flags=backup=0;flashimg;display="ODM Image"

# physical partitions

/boot emmc /dev/block/by-name/boot flags=display=boot

/recovery emmc /dev/block/by-name/recovery flags=display=recovery,flashimg

/metadata ext4 /dev/block/by-name/metadata flags=display=metadata

/data f2fs /dev/block/by-name/userdata flags=display=data

/cache ext4 /dev/block/by-name/cache flags=display=cache

/efs ext4 /dev/block/by-name/sec_efs flags=display=efs

/sec_efs ext4 /dev/block/by-name/sec_efs flags=display=sec_efs

/carrier ext4 /dev/block/by-name/carrier flags=display=carrier

/preload ext4 /dev/block/by-name/hidden flags=display=preload

/modem emmc /dev/block/by-name/radio flags=display=modem

/misc emmc /dev/block/by-name/misc flags=display=misc

/keydata ext4 /dev/block/by-name/keydata flags=display=keydata

/keyrefuge f2fs /dev/block/by-name/keyrefuge flags=display=keyrefuge

/dtbo emmc /dev/block/by-name/dtbo flags=display=dtbo

/prism ext4 /dev/block/by-name/prism flags=display=prism

/optics ext4 /dev/block/by-name/optics flags=display=optics

/vbmeta_system emmc /dev/block/by-name/vbmeta_system flags=display=vbmeta_system

/vendor_boot emmc /dev/block/by-name/vendor_boot flags=display=vendor_boot

/vbmeta_samsung emmc /dev/block/by-name/vbmeta_samsung flags=display=vbmeta_samsung

/system_ext f2fs system_ext flags=display=system_ext;logical,flashimg

/vendor_dlkm f2fs vendor_dlkm flags=display=vendor_dlkm;logical,flashimg

/system_dlkm f2fs system_dlkm flags=display=system_dlkm;logical,flashimg

/init_boot emmc /dev/block/by-name/init_boot flags=display=init_boot

# Removable partitions

/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable

/usb-otg auto /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
[Samsung Galaxy M12] physwizz:
A135m already has recovery.fstab
[Samsung Galaxy M12] Matheus-TestUser1:
where do I find this recovery.fstab?
[Samsung Galaxy M12] physwizz:
If you use twrpdtgen it will be there

This is my a127f recovery.fstab
[Samsung Galaxy M12] Matheus-TestUser1:
thank you .
[Samsung Galaxy M12] kevin5806:
If it's the only option, yes.

I tried some unofficial twrp build i found around, but none of them seem to work with my specific model.
[Samsung Galaxy M12] physwizz:
I can't see the error
[Samsung Galaxy M12] Matheus-TestUser1:
here it is
[Samsung Galaxy M12] physwizz:
I meant I can't find where the error is in the text
[Samsung Galaxy M12] Matheus-TestUser1:
:confused:
[Samsung Galaxy M12] physwizz:
Reduce -j value
[Samsung Galaxy M12] Matheus-TestUser1:
thanks you.
[Introductions] Vian.mdc:
hai.. im newbie here , i regist here for learning , thanks ;)
[Introductions] orb3000:
Hi welcome aboard!
[Linux] jenneh:
Hi I am trying to learn Linux better so I can dump my android boot.img. I was able to figure out the unpackbootimg tool and the dump part, but I am caught up on something that will probably be simple for you guys, how do I access the Documents folder in CLI?

View attachment 5755173

I couldn't figure it out so I typed a . to see if the unpack tool would get past the segmentation fault and it did, but idk where it put the kernel and ramdisk.. so if someone could help me at all I'd appreciate it.

Edit I remembered the sudo nautilus command and was able to locate the root directory and find my kernel and ramdisk

View attachment 5755183

But if someone is able to help me with the exact pathing to Documents that would help me a lot
[Linux] jenneh:
Well I figured it out before anyone woke up I guess XD

Spoiler content hidden.

The trouble is that is too long for what I was trying to do and since the . period works for root like it does android I just built in the root folder. Is this bad? I am trying to make the steps easy for other users to recreate.

bootimg.zip

drive.google.com

For instance, if user takes these tools and unzips them. The instructions go like this:

Add your boot.img to the bootimg folder

Open terminal, run this code:

sudo nautilus

paste bootimg in the root folder

Open the bootimg folder. Right click and open terminal.

Run this code to install 32 bit binary support:

sudo apt-get install gcc-multilib -y

Then Run this code to extract the kernel and ramdisk from boot.img

sudo ./unpackbootimg -i boot.img -o /bootimg/bootmod

The kernel and ramdisk files will be in bootmod

Ref:

How to extract boot.img?

I am trying to see the content in a boot.img file from an Android image. I googled and found this article to extract system.img, but it doesn't work for boot.img. When trying to do this for boot.i...

unix.stackexchange.com

Spoiler content hidden.
[Linux] jenneh:
TBH I am going to use a tool that Miss Renate shared for windows since it will be easier to walk others through.

BUT Just So I stand a better chance of having my one linux question I have left, answered, I will re-ask here so no one has to read through my mess.

Is it bad to build a toolset in the root directory on linux, or What Exactly is the root file system on linux in comparison to a windows system?

Why do windows users not have that or is that like the hidden files and folders on windows? Like this example?

Spoiler content hidden.

I appreciate anyone that can answer the question in this context. I am trying to understand file systems specifically, and since I take things to literally, it really makes it hard to just google this.

Plus google is more of a rabbit hole these days without dorks and dorks involve time.. maybe someone can just explain it in a way that makes sense. Thank you...
[Linux] jenneh:
So two months later and I figured out how to answer my original question.

Adding a "~" to the beginning of a home folder name will allow you to access the Documents, Downloads, and other Home folders without having to type in the entirety of the home path (/home/x0110/Downloads)

cd ~/Downloads

mkdir ~/Documents/Blahblahblah

"~" allows you to execute commands outside of the folder too

example:

mkdir ~/android/system_dump/

cd ~/android/system_dump/

unzip ~/Downloads/lineage-17.1-20220202-nightly-mdarcy-signed.zip

The code above was able to change into the android/system_dump folder and then take the contents of the lineage zip in downloads and paste it into system_dump.

I don't quite understand much of anything well enough to answer the root file system question but will come back to it when it is understood if no one else does