[SuperR Kitchen] DoR3M3:
Could different Shells have an effect? Because I don't use bash, I use zsh... hmm

Looking throught the script I thought maybe aapt="$ttools/aapt" being in quotes " " the issue, some others I see aren't quoted... hmm

zipalign=$ttools/zipalign

p7z=$ttools/7z

aapt="$ttools/aapt"

[MENTION=5787964]SuperR.[/MENTION] yes everything is in linux_tools nothing is missing.

Here's the steps I'm doing/trying to make deoxed rom and zip it...

1. Create new project

Enter new project name

Essential

Copy your firmware to the following

directory and choose option 4 to extract it:

/home/foo/Build/superrs-kitchen/superr_Essential

~/Build/superrs-kitchen/superr_Essential >ls

00_project_files boot.img system.img vendor.img

4) Extract for new ROM

1) system.img

Should we extract system.img

to the current project? y/n

y

Would you like to extract vendor.img? y/n

y

Would you like to include the files from

vendor.img in your rom? y/n

y - by the way, not sure if I should include them?

What is the name of your zip?

Oreo-8.1.0-dex

How would you like to get your partition info?

1) Detect by-name from boot/recovery images (recommended)

Which perm type would you like to use?

4) raw_img

8) ROM Tools Menu

1) Deodex ROM (CURRENT: Odexed)

Would you like to try anyway? y/n

y

CURRENT PROJECT: Essential

ANDROID VERSION: 8.1.0

API LEVEL: 27

ARCH: arm64

ARCH2: arm

METHOD:	vdexExtractor_64

Would you like to continue deodexing? y/n

y

Deodexing complete

Press ENTER to return to ROM Tools menu

ROM Tools Menu

1) Deodex ROM (CURRENT: Deodexed)

Now This Is Where The Problems Start.

Build Menu

1) Build full ROM Zip

Should we zipalign before building the zip? y/n

y

Would you also like to zipalign the apk files in /framework? y/n

y

Choose partition detection method for system

1) Device through adb shell

2) Project directory (BETA): system

3) Enter manually

4) system.img

I choose 1)

This operation requires root.

You may need to agree to allow root on your device.

Would you like to continue? y/n

y

Phone shows a popup, shell was granted superuser

Menu comes back now saying;

Choose partition detection method for vendor

1) Device through adb shell

2) Project directory (BETA): vendor

3) Enter manually

4) vendor.img

I choose 1) again

This operation requires root.

You may need to agree to allow root on your device.

Would you like to continue? y/n

y

ERROR:

Something went wrong building the image.

Make sure your partition size is correct and

that the directory is not too big to fit.

Press ENTER to return to the Main Menu

Then it repeats this message again...

ERROR:

Something went wrong. Check the zip.log for errors.

And I'm seeing the same as before;

tools/source/superr: line 2343: /home/foo/Build/superrs-kitchen/tools/linux_tools/aapt: No such file or directory

tools/source/superr: line 2741: /home/foo/Build/superrs-kitchen/tools/linux_tools/aapt: No such file or directory

appt is there, it's not missing.

~/Build/superrs-kitchen/tools/linux_tools >ls

7z 7z.so aapt adb adb64 bootimg brotli make_ext4fs_32 make_ext4fs_64 sdat2img.py simg2img_32 simg2img_64 vdexExtractor_32 vdexExtractor_64 zipalign

You have perms for everything in linux_tools as; -rwxrwxr-x so I thought to change the perms instead to chmod +x for everything in linx_tools as -rwxr-xr-x but this didn't help. Then I even added linux_tools to my $PATH, and it didn't help too;

echo $PATH

/usr/bin:/usr/local/bin:/bin:/usr/games:/usr/lib/java/bin:/usr/lib/java/jre/bin:/usr/lib64/qt/bin:/usr/sbin:/usr/local/games:/usr/bin/32:/home/foo/Build/superrs-kitchen/tools/linux_tools

Still logs show aapt: No such file or directory...

There's also Unexpected argument: in the main.log I've attached.

I also attached the deodex.log, I noticed Unexpected checksum messages...