Related
This is an (hopefully) updated collection of all roms (not android based, but other linux OS, like ubuntu, archlinux, fedora...) for nexus 7 (grouper and tilapia) available using the MultiROM system.
MultiROM is an amazing hack (I want to thank again its author, Tasssadar) that permits to boot different OS (multiboot) and different android roms. It starts between kernel and rom init, showing a sort of bootloader dialog to choose which system to boot.
It supports installing (and booting, of course) roms to USB drives.
To use MultiROM you need multirom installation zip , a modified TWRP recovery and kernels with kexec support. Relax, is not hard or long to do this.
More information and installation (of MultiROM, recovery and kernels) --> [ MULTIROM ]
PS: I need to specify I coded nothing, my only work was helping with issues, repacking roms, make them work. I want to say thank you to all devs are developing for Nexus 7, I'm doing this because I appreciate their work and I want MultiROM to rise. It deserves to.
HOW TO INSTALL A ROM.
Tasssadar provided also a zip template (see the [ WIKI ] for more info) that is incredibly easy to use.
To install a linux os to sdcard, you just need to download the zip and flash it like a normal update.zip.
It won't replace your internal rom, because it is going to install in /sdcard, not in /system or /data. And it WON'T wipe anything.
Remember that flashing ubuntu or android rom is DIFFERENT from flashing those zips. To flash ubuntu or another android rom you need to use MultiROM menu under ADVANCED voice in recovery (again, see wiki or multirom thread if you need more information).
ROM PACKS.
In the next post I'll share links for rom zips. If you have other zips or if you have built other zips, please share them. They will be (hopefully) added to the list. If not, please pm me. I can't read all posts.
If you want to share a zip, please try it first. I don't know if I'll be able to test everything real-time, and I don't want anyone to see his sdcard erased or strange things like this. MultiROM has a percent of risk, but nobody has lost his data till now. So please share zips consciously.
ROM LIST (DOWNLOADS)
* [NEW] PLASMA ACTIVE 4.0 (20140121)
mirror: http://d-h.st/Khh
old version: https://docs.google.com/file/d/0B9ZvdqAbuJi2blQ0TDgweFFKTlU/edit
description: KDE for embedded devices. Very cool and interesting. 4.0 version is more stable, video codec is working as well. Little slow booting.
* BODHI LINUX 20130109
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
*ArchLinux 20130113-2
old version: -
description: ArchLinux. Simply. Not designed for basic users. Really powerfull, with already packed KDE, Gnome-shell, LXDE, XFCE, Enlightenment environments (and many others probably). Needs testing, and some love, as it's initial release.
*WebOS ALPHA
old version: http://www.mediafire.com/?3m58uuvysxiwypw
description: still in alpha stage, unstable. Interesting project. Needs love.
* [MANUAL INSTALL] Ubuntu Touch Tablet DEVELOPER PREVIEW
old version: -
description: developer preview, android-based, with the new Ubuntu Touch UI.
[NEW] Use MultiROM app to install the latest version in the easiest way
ROMS TO BE PACKED/MADE WORKING:
fedora4nexus7?
PAY ATTENTION: NEW MULTIROM CHANGED THE ROM ZIP STRUCTURE!
NEW STRUCTURE HERE.
I GUESS YOU CAN USE OLD ZIPS, BUT I CAN'T TRY AND IT'S BETTER TO USE NEW METHOD (REPACK NEEDED)
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
[EDIT] new packing method for webos available https://github.com/Tasssadar/webos_multirom_packer [/EDIT]
MORE INFORMATION.
PLASMA ACTIVE.
known bugs: https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
username/password : mer/mer, root/mer
Interesting features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
BODHI LINUX.
known bugs: http://forums.bodhilinux.com/index.php?/forum/40-nexus-7/
username/password: armhf/bodhilinux
useful page (customization, add software, guides): http://wiki.bodhilinux.com/doku.php
ARCHLINUX.
armv7h images: http://os.archlinuxarm.org/os/ (see tegra directory)
username/password: arch/arch, root/root
useful link (bible): https://wiki.archlinux.org/
infos: needs an OTG keyboard or to use "sudo screen /dev/ttyACM0 115200" to connect via usb.
While you are connected you need to configure wifi. I use a script that simply uses iwconfig, wpa_supplicant.conf and dhcpcd to get a wifi connection.
The rest is up to you.
Enlightenment is preinstalled in build 20130113-2.
UBUNTU TOUCH.
infos: use MultiROM Manager app to install it.
GENERAL.
lintz said:
Recomended "fixes" after first install (Mer, Plasma ndr) :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Click to expand...
Click to collapse
Thanks to lintz for the suggestions.
LATEST HOT NEWS.
-updated with latest Plasma version.
-updated with Ubuntu Touch
-updated with latest Plasma & WEBOS version (repacked for new MultiROM structure)
-updated with Ubuntu Touch Dev Preview
-updated OP with arch infos.
-Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
xela92 said:
Making zip for new BodhiLinux version, that now has correct passwd
Code:
bodhilinux
as it should be.
Click to expand...
Click to collapse
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
bonzer2u said:
thx xela, I'm still having trouble creating a zip with the template. perhaps you could post the steps you took to create the new bodhi release
Click to expand...
Click to collapse
Steps how-to done
Later (when upload ends) I'll share Bodhi new version installer link
Nice thread. Can't wait to try some other distro's.
xela92 said:
ROM LIST (DOWNLOADS)
* PLASMA ACTIVE 20130109
old version: -
description: KDE for embedded devices. Very cool and interesting, but still an alpha.
* BODHI LINUX (uploading new version)
old version: INITIAL RELEASE
notes: old version passwd for root and armhf user is trustno1 (sorry for that, is my fault. In new release it is again bodhilinux)
description: Ubuntu with E17 (Enlightenment) with mobile GUI. Pretty stable and... veeery fast.
Click to expand...
Click to collapse
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
I will add those categories later
lintz said:
Needs more info.
Add following kategories
Plasma Active
Bugs : https://wiki.merproject.org/wiki/Community_Workspace/Tegra3/Nexus7/PA_Known_Issues
Username passwords : mer/mer, root/mer
Recomended "fixes" after first install :
Install custom keyboard (write this comands in terminal start with su and after the password for root by default mer)
1. zypper ar -G http://repo.pub.meego.com/home:/won...wonko:branches:Project:KDE:Trunk:Testing.repo
2. zypper up maliit-active libmaliit-quick
3. killall -9 maliit-server
Update the system (use su and root password first)
zypper ref && zypper up
Install GUI package manager (same here su and root password)
zypper in apper
Features : Plays 720p movies full screen with sound and 1080p full screen down scaled with sound.
Same thing for Bodhi. But I dont know the detales about it since I don't use it.
PS as it is now this thread feels as a start to a redundant thread to what is written in Tassadars first 3 posts in the MultiRom thread. Better if you focus on the current distros that don't have any "real" maintener here on xda.
Click to expand...
Click to collapse
thanks
this solved my onscreen keyboard problem (not working over browser) ... now only gui glitches was left (multitasking bar )
xela92 said:
STEPS TO CREATE A NEW ROM ZIP (EASY-WAY):
* first, download the template (reworked by me)
* then, unzip the template, put the root.tar.gz and rom_info.txt inside rom folder (if you don't know what I'm talking about, read again the wiki - link above)
* edit rom name inside of scripts/extract.sh script (it's the only thing you have to edit, unless you want it to do something else, but be careful in that case)
* select the 3 folders (META-INF, rom, scripts) and zip them in a zip called <DISTRONAME>-MultiROM-Installer-<VERSION>.zip (I think it's a good standard, if you don't like simply name it another way, but I reckon that using a standard would be a very good thing)
*when the zip is finished, upload your zip somewhere (I use google drive now, but I hope I'll have my storage sometime in the future) and share the link here. I will add it to the list.
If I don't, pm me.
Click to expand...
Click to collapse
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Nice Topic, i've tried your first Bodhi Zip and it seems very fast and stable to me. A few bugs, but nothing major.
I'm waiting for the new Version to finish uploading
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
xela92 said:
I couldn't find out how to mount those IMG files. I thought they were ext4 fs but they aren't. I tried to use dd to flash them on a drive but failure again. So to extract rootfs I install them with standard procedure (Ubuntu) and the repack roofs to tar.gz. It could be useful to find out how to directly extract rootfs, because it's the same method used by Ubuntu. With the difference that Ubuntu uses zsync to permit fast upgrade...!
Click to expand...
Click to collapse
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
bonzer2u said:
Hi xela,
I understand the process except for creating the 'root.tar.gz' file from a compressed image (.img or .raw) file. Do you need to extract the image file to the /root folder and then recompress with a command similar to:
sudo tar --numeric-owner -zpcf root.tar.gz ./*
Click to expand...
Click to collapse
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Rafase282 said:
If you can get the files from the .img files, you really dont need the zip to install it, just creat a dir with the name for the OS, then inside create a dir called root, then inside extract the .img
For the rom_info.txt file, just make the changes needed and put them on the same dir that ../root is and restart and you should be able to boot form it.
Click to expand...
Click to collapse
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
bonzer2u said:
I could never get it mounted as well.... Is this why your having a delay in uploading the new bodhi release?
Click to expand...
Click to collapse
I'm not at home right know, but in 30 minutes I'll post it
shared the latest bodhi linux version get the link in OP
bonzer2u said:
Unfortunately we have been unable to mount/extract anything from the image although it appears it may install via the multirom/ubuntu method
Click to expand...
Click to collapse
I think zip solution is the best and most "standard". When I make a zip I know it will work, because it's the final, multiROM surely compatible, version. And I can test it immediately, fix it, reflash, and try without messing the world up. I think update zips are the most user-friendly way too. But that's only MHO.
{
"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"
}
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.
[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 Zipalign
ArchiKitchen Tutorial
Part 1 - Setting up Linux & ArchiKitchen on Windows
https://www.youtube.com/watch?v=ktedmhWHz2M
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
[SIZE="+1"]ArchiDroid Init.d[/SIZE]
ArchiDroid Init.d is an innovative method for including init.d support in the ROM itself, and not in the kernel. ArchiKitchen supports adding ArchiDroid Init.d to any Android ROM.
ArchiDroid Init.d is based on two files. A core - debuggerd hook, and a check part - simple init.d script.
Init.d script is named 00ARCHIDROID_INITD, and it only creates a special file to notify the core that init.d has been already executed, therefore it can't conflict with anything and it's completely safe.
The core is a hook for special /system/bin/debuggerd binary, which is normally called once during initial boot. Therefore, when it's called, ArchiDroid Init.d firstly waits a specified amount of time (default: 5 seconds), in case if user has already a kernel with init.d support. This is required because otherwise all init.d scripts would be executed twice - by kernel and our init.d. After specified time, if init.d is still not executed, our hook executes all scripts in alfabetical order. Lastly, when we're done, hook is executing original debuggerd binary (default: debuggerd.real) and shares the environment, arguments and everything. This is a perfect method for implementing init.d in the ROM itself, because we don't need to trust the kernel that it supports and executes init.d properly. We give it a 5 seconds to execute it, and eventually we do the job if kernel is not interested in that. This way we can support both custom kernels with native init.d support (we wait initial delay, if kernel executes init.d, all is fine and we don't have to do so), and also pure stock kernels without init.d support (we wait initial delay, kernel doesn't care about init.d, so we're executing it).
I think that such hook works far better than relying on the kernel and modyfing stock ramdisks. Also we're sure that even if user changes kernel to any custom one, we still have reliable init.d support, regardless if custom kernel supports init.d or not.
Reserved.
JustArchi said:
It's a bit quiet in here, I was expecting more noise
Click to expand...
Click to collapse
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Harris_xx said:
Me too!
THX for your work!!!
If i get my new Laptop next few days i will dl and test it!
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
Looking forward.
i really appreciate your work, like every time
In general whole kitchen needs a magic touch more or less but firstly I'll want to make it fully usable (and modern!) then eventually rework it.
As for now it's more or less up-to-date. Also added Note3 variant.
Thanks for your work and projekt!
I will download and test it with the new Galaxy Note 10.1 2014 :good: (Android 4.3)
Feel free to test it, but keep in mind that it's still work in progress .
Today I've added new experimental method for *better* handling setting up rom directory. As for now it supports only system.img in sgs format, however it automatically extracts it (if needed) from any tar/zip package, also with properly detecting cache.img. This is the main feature I was missing in original kitchen.
https://github.com/JustArchi/Android-Kitchen/commit/cf025ebf6573d23e5d2b7cfde258d9b7c36abd29
Just please don't track "wip" branch, as it's rebased often and merged into master when ready .
This is great, as I love the kitchen it is awesome that you've updated it. I'll be trying it out tonight. Thanks for your work.
Sent from my XT1032 using XDA Premium 4 mobile app
Great work :good:
Tested New device LG G2
Looks very good, thanks for updating the kitchen.
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Perka said:
Got an error when using the kitchen:
Code:
-----------------------------------------------------------------
BusyBox is an executable file that combines tiny versions of
many common UNIX utilities. It is required for some root-enabled
applications.
-----------------------------------------------------------------
Add BusyBox (y/n)? (default: y):
Found ./system/xbin/su
Found /system/xbin
Working folder already has /system/xbin/busybox
Replace with BusyBox 1.21.1 (y/n)? (default: y):
Replacing /system/xbin/busybox
Adding /system/xbin/busybox
Error: No update-script found!
Press Enter to continue
Due to that I converted the update-script to edify.
Click to expand...
Click to collapse
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
JustArchi said:
Actually kitchen can work only with update-script, although it converts it to updater-script when building rom.
This is on my todo but it's a bit complicated (many dependencies), so it needs major rework.
As for now I suggest avoiding conversion before final build.
Click to expand...
Click to collapse
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Perka said:
Thanks.
Also
1. with koush rooting theres no deamonsu in xbin, is this right?
2. when rooting the kernel is still ro.adb.secure=1 should be 0 or?
3. would be great if the kitchen adds a modded adbd in ramdisk/sbin (to get root directly in adb)
Again thanks
Click to expand...
Click to collapse
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
JustArchi said:
1. That's right, koush doesn't have direct support for su daemon.
2. User should be able to modify this, on todo with many other things...
3. I think we can do it, soon .
Click to expand...
Click to collapse
Sounds good
---------- Post added at 03:50 PM ---------- Previous post was at 03:44 PM ----------
Donation made
4T106212CC7164407
i worked with planty firmwareswith the latest kitchen for my devices but anytime the SuperSu after installation was saying something like "there is a SuperSu, but not Supersu binary installed". that thing was gone after i flash the SuperSu update binary. Does your kitchen gonna give me SuperSu from the start (instalation)?
--- copied with permission from nathanpfry.com ---
Architekt is a custom Virtual Machine that can be used with Mac OSX, Windows, and Linux. It includes everything you need to sync with the repo of your choice (Cyanogenmod, AOKP, AOSP, etc) and start compiling Android ROMs. This version includes Java 6 for compiling Gingerbread thru Kitkat. To compile Android L, switch to OpenJDK7.
Features:
- Latest Arch system
- XFCE Desktop Environment
- All necessary packages for compiling
- No junk (games, etc)
- Geany for editing code
All you have to do is download the source!
The only requirement is that your host machine supports a 64 bit OS. 32 bit systems will not work!
Instructions:
1. Download and install VirtualBox for your host system from here.
2. Download the latest architekt zip archive and extract architekt.ova to your hard drive.
3. Start VB, click File > Import Appliance. Select "Open Appliance" and choose architekt.ova, then click Next to import the virtual machine.
4. Highlight architekt in VirtualBox Manager and open Settings. Under "System" you will want to give it more RAM and Processor Cores. The higher these values are, the faster you will compile ROMs.
5. Start the machine, pull up a terminal and initialize a git repo. Once the source is finished downloading, you're ready to go!
Download:
Click here for download mirrors
Username/Password: android/android
Feel free to buy me a Zico coconut water (donate) if you like my work. It would be greatly appreciated!
Please hit the "Thanks" button if this post helps you out!
please can you help me how to change java version jdk6 to jdk7 using command?I've tried command that used in ubuntu but Those command are not working in this virtual machine. Also there is no app to extract file and can't edit xml file
Røbin said:
please can you help me how to change java version jdk6 to jdk7 using command?I've tried command that used in ubuntu but Those command are not working in this virtual machine. Also there is no app to extract file and can't edit xml file
Click to expand...
Click to collapse
You might want to try BuilduntuVM instead.
Architekt is getting pretty dated, and I don't have any time or plans to update it. BuilduntuVM received a lot more attention and is up to date with the latest versions of OpenJDK etc. for compiling Android M.
sylentprofet said:
You might want to try BuilduntuVM instead.
Architekt is getting pretty dated, and I don't have any time or plans to update it. BuilduntuVM received a lot more attention and is up to date with the latest versions of OpenJDK etc. for compiling Android M.
Click to expand...
Click to collapse
Thank you
AUTOSCRIPTS
Hi Everybody!
That's my first work for the Moto X Style & Pure (ported from my work on Moto X Play) so I hope You'll appreciate it.
It's simply an automatic flash script, just in case You won't have to remember all these shi*ty codes.
It's personally created and tested by me, so I'm sure it works, but I don't assume any responsibility for damaged devices.
!!REMEMBER! I DON'T PROVIDE ANY STOCK ROM!!
My script (as you'll see) works both with Ubuntu (and derivates), Fedora (yes, both with dnf and yum installer), ArchLinux (and derivates) and Windows.
If you have any question/suggest feel free to post it here and if I helped you feel free (too) to hit thank and maybe buy me a coca (I don't really like alchoholic drinks).
HOW TO1) Download it from THE DOWNLOAD TAB.
2) Put on your Home Folder (or anywhere You want).
3) Unzip it (You'll see a file called flash.sh, for linux users, and some files for windows users).
4) Open a terminal and cd the folder where you have saved flash.sh.
5) Copy the code below (for Linux) or simply double-click on flash.bat (for Windows. It doesn't request administrator privilegies).
Code:
$ chmod +x flash.sh
$ ./flash.sh
6) Follow the instructions on screen.
7) Enjoy.
BUGSAll the Scripts is tested personally by me before any upload so I'm sure they'll work. Anyway if you encounter any problems please post it in bug's tab HERE!
VERSIONSAutoScript Linux
First Version
Added support for ArchLinux (both with pacman and yaourt)
BugFix
AutoScripts Windows
First Version
Added ability to relock the device
BugFix
F.A.Q.1) Why it doesn't work with device XYZ?
It's because my AutoScripts is developed only for Moto X Play, Pure & Style.
2) The Scripts have only formatted my device. You piece of sh*t!!1!11!
Have you downloaded the ROM and put the files on the Flash's folder? You can find it HERE FOR STYLE and HERE FOR PURE.
3) When do you upload an update?
I'll do it as soon as possible. Don't hassle me with that unuseful quest please.
4) Thank man, your work is fantastic!
Please hit thank button, don't write a post for that.
5) I've read your work and the codes is fuc*ing ugly and long.
I know. If you have a suggestion please tell me and I'll see if i can do anything.
XDA:DevDB Information
AutoScripts, Tool/Utility for the Moto X Style (Pure)
Contributors
ScardracS
Version Information
Status: Stable
Current Stable Version: 2016-10-04
Created 2016-10-04
Last Updated 2016-10-25
Disclaimer: I am not responsible for anything bad that may occur from the use of this kitchen, but I will take all the credit you can give me if it works for you
{
"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"
}
Please read the troubleshooting in post #4 of the standard kitchen thread before asking for help.
Please indicate your OS when asking for help.
Please send a fast link to your firmware that does not require registration when asking for help.
Donate Release Thread
Donate Changelog
Donate version Info
See terms and conditions below.
Spoiler: Terms and Conditions
Terms and Conditions for SuperR's Kitchen Donate version:
Allowed:
An active kitchen account grants usage privileges of the donate kitchen and the sr-code.com website.
One kitchen account provides kitchen access to one user, on one operating system, on one personal computer.
Not allowed:
Sharing your kitchen account and/or privileges.
Transfer and/or resale of your kitchen account.
Suspicious activity.
Definition:
Suspicious activity - Decided exclusively by SuperR at the time of an incident.
Resolution:
If anything from the not allowed list occurs, your kitchen account will be disabled.
See this post for more details on the Single PC license.
Donation Options:
No longer accepting donations or new users.
EXISTING DONORS: GitLab is no longer used. See this post if you previously had GitLab access and are unable to download/update/install.
NOTE: The Plugin Repo is included in the Donate kitchen. If you wish to see a description of the available plugins, they can be found here.
Dependencies:
WINDOWS:
Java 8 or higher (Windows download)
LINUX/MAC:
Java 8 or higher
Python (to run the launcher (could be bypassed by running tools/source/superr in the terminal from the main kitchen directory))
Download/Install/Run:
Free version:
Found here
WSL2 (Windows 10):
WSL2 Help and information (Donate Version)
With the release of v3.2.1.0, there are many improvements to the Linux version of the kitchen compared to the native Windows version. WSL2 on Windows 10 is the perfect way to run the Linux kitchen on Windows. Installation takes a few more steps...
forum.xda-developers.com
Linux/Mac (Terminal):
Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
Enter the following command where "/location/of/kitchen" is the directory where the kitchen lives:
Code:
/location/of/kitchen/superr
Windows:
NOTE: The native Windows version has reached end of life. Consider running the Linux kitchen in WSL2 using the guide above.
Download the kitchen.zip from the download page sent through PM. Extract to a new directory.
Make sure Java listed above is installed and in your system environment PATH (Check Google for the many guides on this if you need help)
Double click superr.exe in newly extracted kitchen directory.
NOTE: After you start the kitchen, it will ask you for your Kitchen username and password. Make sure you enter it correctly or it will not work. Thanks for the donation, enjoy
Known Issues/Limitations:
Does not unpack/repack f2fs file systems.
Linux:
None
WSL2:
None
WSL1:
Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
Mac:
Does not use e2fsdroid for building img files as I am not able to compile it for Mac so far.
Windows:
No longer being updated. v3.2.1.3 is the last version. The Linux kitchen runs perfectly in WSL.
Does not use e2fsdroid for building img files as I am not able to compile it for Windows.
Crashes with xattr not defined error when unpacking some img files due to a bug in the Python ext4 module.
If you run Windows as administrator and have issues with the Boot Menu, please see this post.
If superr.exe gets removed by your antivirus program, whitelist the kitchen directory in your antivirus program.
If the kitchen can't find an internet connection, try whitelisting sr-code.com in your antivirus browsing security. If it still does not find a connection, try using a VPN.
The colors are not perfect due to Windows not supporting ASCII escape codes by default. If you want it to look more like Linux, you can run the Linux version in WSL (formerly known as "Bash on Ubuntu on Windows").
Video tutorials by @chevycam94
Credits:
@osm0sis - For Busybox Installer and Android Image Kitchen
@Chainfire - For SuperSU
@JesusFreke - For [Bak]smali
@nkk71 - For TWRP minzip patch, and make_ext4fs improvements
@Captain_Throwback - For providing a pre-compiled update-binary with the minzip patch and squashing bugs
@cubinator - For Python ext4 module
@_riddle - For oat2dex
@iBotPeaches - For Apktool
@AOSP - For zipalign, aapt, adb, img2simg, simg2img, make_ext4fs
@xpirt - for img2sdat & sdat2img
@yoanf_26 - For French translation
@anestisb - For vdexExtractor
@iuss - For payload_dumper.py
Contributors
SuperR.
Version Information
Status: Beta
Created 2018-11-16
USAGE:
Run the kitchen (instructions in OP)
Create new project using the menu
Copy ROM zip into the superr_NAME directory of this tool (NAME = the name of your new project).
OR
Copy system.ext4.tar and boot.img into the superr_NAME directory of this tool.
OR
Copy system.ext4.win and boot.emmc.win into the superr_NAME directory of this tool.
OR
Copy system.img and boot.img into the superr_NAME directory of this tool.
OR
Copy official Nexus tgz into the superr_NAME directory of this tool.
OR
Copy Samsung firmware zip into the superr_NAME directory of this tool.
OR
Copy Moto firmware zip into the superr_NAME directory of this tool.
OR
Leave superr_NAME directory empty to extract from rooted device or custom recovery
Extract for new ROM from the Main menu.
Enjoy!
Features:
*Extract and create ROM from:
Rooted Device
Custom Recovery
Existing ROM zip
system.img/boot.img (and cache.img on Samsung devices)
system.ext4.tar/boot.img
system.ext4.win/boot.emmc.win (including multi-file .win000, .win001, etc)
Moto and other factory firmware zips containing sparsechunk files
cm12 + roms with sparse dat files
Zips that contain system.img and boot.img
Zips that contain payload.bin
Samsung firmware zips that contain tar.md5 file
Official Nexus/Pixel firmware tgz/zip
Official Nexus/Pixel preview tgz/zip
system directory that contains symlinks and boot.img
*Create flashable zips of many varieties including:
Full ROM
Switch between set_perm, set_metadata (KitKat+), raw_img, and sparse_dat (Lollipop+)
Kernel (including init.d if you added it with the kitchen)
Recovery
Media
app, priv-app, and framework
*Deodex the following:
Android 10 ROMs
Pie ROMs
Oreo ROMs
Nougat ROMs
Marshmallow ROMs
Lollipop ROMs
KitKat and earlier ROMs
*Root features:
Root/unroot
Choose Magisk
Choose SuperSU
Add other root zips to /tools/root/root_zips directory
Choose system OR systemless root for M+ and Samsung 5.1.1 roms
Add/remove su.d support
*Boot features:
Unpack/repack boot/recovery img (Big Thanks to @osm0sis for Android Image Kitchen!!!)
Add/remove insecure boot
Remove dm-verity
Add/remove forceencrypt
*By-name auto-detection from:
Device
Existing ROM
boot.img
kernel.elf
**OR**...manually enter it
*mmcblk auto-detection from:
recovery.img
*Kitchen updater:
View the last 3 changelogs when an update is available.
Update to the latest version
Option to check for updates when the kitchen starts
*Pack/Unpack super.img
*Create system.img
*Device database for mmcblk devices (currently very small, but will grow over time)
*Add devices to the assert
*Add custom asserts
*Zipalign apks
*Debloat ROM
*Custom Debloat list support
*Remove Knox
*Add/remove busybox (Big thanks to @osm0sis for his Busybox Installer)
*Add/remove user app support (/data/app)
*Sign zips
*Cross-platform: Windows and Linux are fully supported
*Does not say Built with SuperR's Kitchen in the updater-script
*Does not replace ro.build.display.id with Built.with.SuperRs.Kitchen
*Allows you to create a custom entry in the updater-script below the ROM name
*Removes all the Place holders (#ASSERT, #SYM, #PERM, etc) from the updater-script before zipping.
*Custom ro.build.display.id
*Option to convert updater-script to update-binary for all rom zips EXCEPT sparse_dat.
*Add custom directory to be included in and flashed with rom zip to location of your choice.
*Ability to choose an apk, decompile, modify it manually, recompile, sign, and move it back to where it came from.
*Plugin support - Add your own script to the /kitchen/tools/plugins directory and the kitchen will run it for you.
*AutoROM - Unattended ROM development using a config file.
Nice to see the windows version! Thx SuperR!
Sent from my unknown using XDA Labs
Got the notification from Gitlab
Bangin'! [emoji41]
shoey63 said:
Got the notification from Gitlab
View attachment 4139244
Click to expand...
Click to collapse
Me too. [emoji16]
Sent from my N9515 using Tapatalk
@SuperR.
I've been enjoying your free version greatly. It suites my needs just enough. But I still wanted to contribute to get the Pro version, just to Help Donate to you. The many lines of script you wrote are AMAZING!!! THANK YOU for your amazing work!!! :good:
Heres my GitLab username: aaron74xda
My 14.04 is also 64bit version maybe is better i update to the version that you offer in the other kitchen thread ?
https://forum.xda-developers.com/showpost.php?p=72066578&postcount=4 << on this post
gitlab username: OMJ
thanks again!
SuperR. said:
Thanks for the info. This project is still Beta as marked in the OP. Once we figure out how to solve all the small issues I will update the documentation and the kitchen to try and help everything along as much as possible.
Running as admin in windows brings up another point I forgot about. Apparently Windows can only create symlinks as admin, so if you need to create a system.img you will need to run as admin.
Click to expand...
Click to collapse
You could try creating a batch script that self escalates, and calls "python superr" as Admin. I'm not great with Python by any means. I have a bit more experience with batch.
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Is there no log file anywhere for errors? Tried to extract a 7.1.2 ROM, and it says there was a problem, but no info or anything.
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
dkionline said:
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
Click to expand...
Click to collapse
I believe he wants to hold off on a "free" release until more issues have been resolved. That leave those that paid for it with access (limited number of people) to help test it. Also sounds like it leaves those with a slightly more vested interest in it to help with input, as they paid for it, and therefore use it more than those that typically just have the free version.
At least in my case, the $10 I put up is all I needed. No additional money is (currently) required.
chevycam94 said:
You could try creating a batch script that self escalates, and calls "python superr" as Admin. I'm not great with Python by any means. I have a bit more experience with batch.
Click to expand...
Click to collapse
I don't know anything about batch scripts. If you want to write it to help out, I am sure some people would find it useful. I don't even know how to start cmd.exe as admin without right clicking lol
chevycam94 said:
Is there no log file anywhere for errors? Tried to extract a 7.1.2 ROM, and it says there was a problem, but no info or anything.
Click to expand...
Click to collapse
There is currently very limited logging. It is something that I would like to improve on for sure. Please send firmware as requested in the OP and I will have a look.
edit: I just downloaded and extracted the latest bullhead 7.1.2 release on Windows and Linux with no issues.
edit2: Just added the pip commands to the install instructions in the OP
dkionline said:
@SuperR. Do you provide a Free version soon? Does we have to pay another $10 if we using version 2?
Click to expand...
Click to collapse
There is already a free version of the kitchen https://forum.xda-developers.com/ap...chen-superr-s-kitchen-v1-1-50-v2-1-6-t3597434
There is no plan for a free Python version. The free version is Bash and the donate version is Python. Eventually, support for the Bash donate version will end. All donors have already been added to the Python repo. There is no need to donate again for access unless you want to
I'm going to donate again (it'll be later this weekend)...because WOW! thank you for the rewrite in Python! I might love you geeky bro man love.
@SuperR. Ok cool, but no access here on 3.0
name: dkionline
Edit: Im in i see, but no sources visible yet, think you not open before beta is done.
GraveDigger176 said:
I got this Error message when i want start the Kitchen and psutil is installed. I'm on ubuntu 14.04
Click to expand...
Click to collapse
I dont think basic psutils is enough
Might be overkill, but enter this in your terminal
Code:
sudo apt-get install psutils && sudo apt-get install python-psutil && sudo apt-get install python3-psutil && sudo apt-get install python3.5
I had the same error on Linux Mint 18 Sarah, but the kitchen fired straight up for me after I entered the command and received the updates.
Hello,
SuperR. said:
All donors have already been added to the Python repo. There is no need to donate again for access unless you want to
Click to expand...
Click to collapse
I have a small problem:
Code:
[email protected]:~/Documents$ git clone https://gitlab.com/superr/superrs-kitchen3.git
Clonage dans 'superrs-kitchen3'...
Username for 'https://gitlab.com': migascalp
Password for 'https://[email protected]':
remote: Not Found
fatal: repository 'https://gitlab.com/superr/superrs-kitchen3.git/' not found
[email protected]:~/Documents$
migascalp said:
Hello,
I have a small problem:
Click to expand...
Click to collapse
Do it again. It will eventually work.
Edit: Unless you haven't donated.
dkionline said:
Access was granted and notification is there, but source on gitlab not visible.
404 Page not found.
Click to expand...
Click to collapse
Just git clone again. It worked for me after a couple of attempts. Gitlab is unpredictable sometimes.
shoey63 said:
Do it again. It will eventually work.
Edit: Unless you haven't donated.
Click to expand...
Click to collapse
I am already a donor user
thank you for the answer