Impossible to get a logcat when it doesn't even go beyond the Google logo aka bootloader... I would've been done that with my first post in here if it was possible.
[EOL] [KITCHEN] ArchiKitchen - Android Kitchen [Linux]
- Thread starter JustArchi
- Start date
Impossible to get a logcat when it doesn't even go beyond the Google logo aka bootloader... I would've been done that with my first post in here if it was possible.
Ah, *that* logo (I'm not familiar with these devices). Yes, in that case the only source of information is /proc/last_kmsg if it exists after the reboot.
I finally got my N6 deodexed 5.1.1 (LMY47Z) to boot after building with Archi. The problem was in the metadata --- I replaced the metadata portion of the updater _script generated by Archi with the metadata from this rom Thanks @scrosler and @mikeyxda. Not sure what was needed but it worked. We need someone to teach us how to pull/check the required metadata !!!!!!!!! @scrosler or @mikeyxda please???????
Last edited:
Negan
Recognized Themer/ Retired Forum Moderator
Ok so I haven't used this tool for a while but after cloning his repo and running it I was a bit surprised that it doesn't appear to be updated to deodex lollipop. Is this project abandoned or something?
Lollipop deodex not supported. He has been doing other things with AOSP I believe so hasn't needed to update for himself.
Not sure it matters but I run these lib commands.
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
sudo apt-get install lib32z1 lib32z1-dev
Last edited:
Not sure it matters but I run this lib command also.
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5
sudo apt-get install lib32z1 lib32z1-dev
Thanks for the reply!
I would be using this kitchen on Samsung 4.4.2 stock ROM so
just wanted to stay as safe as possible without encountering any issues.
I will run those commands as recommended by you!
Mine is setup to build roms and kernels from source. These are all the libs required to build anything. May not need for Kitchen but will future proof any other dev efforts.
Mine is setup to build roms and kernels from source. These are all the libs required to build anything. May not need for Kitchen but will future proof any other dev efforts.
Got your point!
It is future proof.
It was nice communicating with you and gaining some more knowledge!
Thanks for your efforts!
No problem. We all started somewhere. Linux a big learning curve so no need for problems due to simple things like a missing lib with no way to know that was causing a major problem.
Hy everyone !
Thx for the work JustArchi ! I am a noob rom maker, i compile with success AOSP and cm 12 but when i want to make a zip (cm12), i have a problem with kernel path. I don't know what it is and where i can found it. I tried to find it in /fstab.qcom, with mount command or in ls-a /dev/block/plateform/ but i don't understand what it is and i don't want make any mistake.
This is for a Galaxy S4 LTE European.
Maybe i forgot one thing ?
Thx for your help.
Thx for the work JustArchi ! I am a noob rom maker, i compile with success AOSP and cm 12 but when i want to make a zip (cm12), i have a problem with kernel path. I don't know what it is and where i can found it. I tried to find it in /fstab.qcom, with mount command or in ls-a /dev/block/plateform/ but i don't understand what it is and i don't want make any mistake.
Code:
WARNING ! kernel has been found but there's no path in the current updater-script.
This is typical when you're converting stock image partition to ZIP-flashable ROM
Detected ROM model : jfltexx
This model does not yet exist in our database. Please fill your kernel path manuallyMaybe i forgot one thing ?
Thx for your help.
S
sawdoctor
Guest
That's normal it just means it's not in the database. Use either the diskinfo or storage partions apk's from playstore to find your kernel path and then enter it
View attachment 3425412
See mine is 17
Sent from my SM-N910F using Tapatalk
Tried checking that attachment out but keep getting "invalid attachment"
Sent from my N9510 running CM12.1!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
283
ArchiKitchen - Brand new Android Kitchen
Commits/Changes -> https://github.com/JustArchi/ArchiKitchen/commits/master
Source -> https://github.com/JustArchi/ArchiKitchen
TODO list -> https://github.com/JustArchi/ArchiKitchen/issues?state=open
Download. Of course you can also clone my repository to stay up to date.109[SIZE="+1"]Features:[/SIZE]
- Compatible with every Linux, which provides bash shell (every available distro nowadays)
- Full ARM/X86 support for all included android binaries (Root, Busybox)
- Dynamic permissions - A generic list of all available permissions, with proper filter for your local build and device
- Dynamic symlinks - A generic list of all available symlinks, with proper filter for your local build and device. Additionaly if you're building from stock image, support for including symlinks from image itself, which results in best 1:1 copy
- FS-friendly method of flashing - ROMs created with ArchiKitchen are fully compatible with every available partition, which means that they don't reformat /system partition during flashing. This is extremely important for dual-FS support for example for EXT4 and F2FS on SGS3.
- Kernel repacking - Powered by mkbootimg, repacking a kernel never was easier. With one click you're extracting the kernel along with ramdisk to the proper folder, and with the second you repack it back
- Deodexing - With one click you can easily deodex your whole ROM. With multi-threaded process and automatic API detection, this never was easier as well.
- ArchiDroid Init.d - Forget about relying on kernel's ramdisk. Implement init.d in your ROM, not the kernel!
- Latest [Bak]smali
- Latest SuperSU
- Latest Busybox
- Latest Zipalign
- And many more in the unique shell ktichen
[SIZE="+1"]Credits:[/SIZE]
@osm0sis - For mkbootimg
@Chainfire - For SuperSU
@Stericson - For BusyBox
@JesusFreke - For [Bak]smali
@bgcngm - For MTK-Tools
AOSP - For Zipalign64ArchiKitchen Tutorial
Part 1 - Setting up Linux & ArchiKitchen on Windows
By watching above step-by-step video, you'll learn:
1. How to install Debian on your VirtualBox machine
2. How to connect Windows with Linux through a shared VBox folder
3. How to install ArchiKitchen
4. How to create your first custom ROM, with built-in Root and Busybox
Extra information:
- You can use any virtualization method you want. I suggest using VirtualBox, as it's very easy, flexible and free virtualization solution.
- You can use nearly any Linux distro. I suggest either Debian or Ubuntu, as both of them have excellent support and are very easy to install and use, compared to some other ones. However if you feel fine in Linux environment, you can install nearly any distro you like.
Mini.iso link
Weekly Debian Testing.iso link
Installing virtualbox additions: apt-get install virtualbox-guest-dkms
Installing required tools: apt-get install zip unzip openjdk-7-jdk
Mounting a shared VBox folder: mount -t vboxsf yourName /path/to/yourFolder
Tutorials made by other developers: @bigrammy
Part 1. Prepare for linux Installation https://www.youtube.com/watch?v=aDsQTcDvSMY
Part 2. Install Linux (Ubuntu/Zorin) https://www.youtube.com/watch?v=KwnIjCXXM5Y
Part 2.5. Edit Winows bootloader to boot Linux: https://www.youtube.com/watch?v=gNpQucQxcFQ
Part 3. Work as Root Mod & Install ArchiKitchen https://www.youtube.com/watch?v=T_ad7uML8QM
Part 4. How to add your device locally to the Kitchen: http://youtu.be/YXNDcmf6GhI
ArchiKitchen Questions & Answers
Q: What is this "ArchiKitchen"?
A: A Linux-based kitchen, with a main objective of converting stock ROM drops in .img, .tar.md5 or similar formats to CWM-flashable .zip.
Q: So I can create my own custom ROM based on stock ROM with it?
A: Exactly.
Q: Is it for Linux only? Why windows is not supported?
A: Let's face it, Android is based on Linux kernel and we could call it a mobile UNIX fork. It's hard to work with Linux-based things on Windows, in fact, Windows doesn't even offer Bash (Bourne-again shell), which is absolutely core for ArchiKitchen. Working with windows is painful, for example - .img mounting. I can very easily mount any filesystem image on Linux with just one command, while doing so on Windows usually requires a massive convertion of whole image to .zip file, then extracting a single files. Also, Windows doesn't support symbolic links, and this makes it impossible to create 1:1 copy of the image "translated" to zip file. Therefore, making a Windows port would require lots of more work and solving issues, and even with that it would still cause some core features to be unavailable. However, launching Linux on Windows is very easy thanks to VirtualBox and other virtualization software, so you don't need to reformat your PC or stick purely with Linux. In fact, this is the proposed way of using ArchiKitchen - Installing a native Linux distro (suggested: Debian or Ubuntu) and then installing ArchiKitchen on it. Take a look at tutorial to see how easily you can install and run ArchiKitchen in Linux VBox.
Q: Is Cygwin supported?
A: No. Cygwin IS NOT supported and it's not planned to add such support. Reason is nearly the same as above one. However, ArchiKitchen is open-source project and I'm open for all pull requests, so perhaps somebody will add support for Cygwin in the future. Until then, ArchiKitchen is compatible ONLY with Linux, and if you use it on Cygwin you're on your own with the issues that may happen.
Q: Which phones are supported?
A: ArchiKitchen contains a local "database" of devices, which includes a kernel/modem blocks to be used. However, as long as you know the partition layour of your device (kernel block), ArchiKitchen works with every phone and every Android variant. I'm trying to make it as universal as possible, so even if your device does not exist in our local database, it should work.
Q: How can I add my own phone to the local database?
A: If it doesn't exist yet, take a look at "product" folder. Inside you can notice various devices with name based on their models. ArchiKitchen will detect your ROM's model and check inside if it exists, if it does, then some properties for this model will be loaded, if it doesn't exist, then ArchiKitchen will ask user for them. Probably the best idea is to copy one of the already available models (for example "m0" - Samsung Galaxy S3), then rename new copied folder to your model name and finally edit files inside.
Q: What is "NULL" text found for example in some MODEM files in the database?
A: Some phones have a possibility to flash modem directly from CWM, others don't. "NULL" text indicates that this model does not support flashing modem.bin, so even if ArchiKitchen finds and recognizes it, it will pop up an error telling you that it unfortunately can't be used.
Q: Where is SYSTEM block?
A: System block is not being used at all, as it's a valid partition and should be located in "fstab" file in recovery already. ArchiKitchen mounts system automatically through "mount" binary, with automatic filesystem and /system path. I consider providing a system block as something obsolete, because it's only required when you're formatting a partition, and even during flashing, a wipe - delete_recursive() function is enough. Therefore, ArchiKitchen does NOT require providing a /system block.
ArchiKitchen Troubleshooting
Q: It looks like something is wrong with zipalign command. I can notice errors like "./zipalign: No such file or directory"
A: This is because zipalign is x86 binary (32-bit), while you have amd64 (64-bit) Linux. Therefore, we must install some missing core packages to properly support x86 binaries. This will do the trick:
Code:apt-get install lib32stdc++6 lib32z1
