Related
The Team Lambent Corrosion member presents:
UpdatezipCreator
Some of you remember my old app UpdateThemeCreator. I've found some time to build a new app that can create updates (as zip archive flashable via recovery).
Changes/Improvements since the last version of ThemeUpdateCreator:
-new interface
-adding files to other folders than system/framework and system/app
-new algorythms
-editing update-script (saving, loading, making default etc)
-saving settings
I hope that app will work without any bugs
Changelog:
1.0.0.1
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
1.0.0.2
-Adding folders
-Drag&Drop
-Signing single zip archive
1.0.0.3
-Fixed bug with the wrong name of edify scripts
1.0.0.4
-Not signed archive is kept in temporary directory
-Functions library (inserting functions)
1.0.0.5
-Problem with update_ont_signed path solved (I hope so)
1.0.0.6
-Log mode
1.0.0.7
-Signing bug fixed
1.0.0.8
-Handling linux newline character in scripts
DOWNLOAD:
Rar archive - about 500 kb
Source code - about 1,3 MB - Visual Studio C#
Windows installer (source included) - about 830 kb
I'll use it tomorow for my theme
Sent from my GT-I5800 using CM 6.2 Cyanbread themed
Looks cool
Maybe you can add an option to switch between amend (all cwm versions before 3.x - what we currently use ) and edify (3.x + - like in cm7 and apollo's dual/tri boot kernel)
Then it'ld be universal
Thank you.
cdesai said:
Looks cool
Maybe you can add an option to switch between amend (all cwm versions before 3.x - what we currently use ) and edify (3.x + - like in cm7 and apollo's dual/tri boot kernel)
Then it'ld be universal
Click to expand...
Click to collapse
Yeah, it's already done
Waiting for a permission for use update-binary.
I haven't made phone databes for mounting points, I think that everyone who will be using edify scripts will change it manually in script-editor.
benzyniarz1 said:
Yeah, it's already done
Waiting for a permission for use update-binary.
I haven't made phone databes for mounting points, I think that everyone who will be using edify scripts will change it manually in script-editor.
Click to expand...
Click to collapse
I replied to your email... (same link as the email contained)
Also if you'd like to utilize the database xml from my amend2edify project, feel free to (someone is already using it in a market app).
Your tool looks nice and simple, I've considered doing something similar in the past, never got around to doing it, and now looks like I don't have to. Good work.
Also, maybe this could be moved to a more general section, as it's not restricted to Galaxy 3 devices. (Suggestion, you could add in zip signing to better support more devices.)
=]
nubecoder said:
I replied to your email... (same link as the email contained)
Also if you'd like to utilize the database xml from my amend2edify project, feel free to (someone is already using it in a market app).
Your tool looks nice and simple, I've considered doing something similar in the past, never got around to doing it, and now looks like I don't have to. Good work.
Also, maybe this could be moved to a more general section, as it's not restricted to Galaxy 3 devices. (Suggestion, you could add in zip signing to better support more devices.)
=]
Click to expand...
Click to collapse
Thanks a lot!
Zip signing is available and it's executed automatically (unless JRE is not available)
I'll post the thread in General Android Development and try to impelement your PhoneDatabase
So, app updated. Changes:
-adding update-binary to edify scripts (possibility of choosing own update-binary)
-added default scripts for edify scripts
-settings not stored in my documents
Thanks so much
Ability to sign already made update.zips(with some other tool or manually) would be nice!
EDIT:
Just tried it with folders and it wont work
aka
i can manually add all files and add path(bt tat'ld be a pain)
So how about selecting whole folders?
Drag and drop would be a nice option!
Version 1.0.0.2, changelog:
-Adding folders
-Drag&Drop
-Signing single zip archive
benzyniarz1 said:
Version 1.0.0.2, changelog:
-Adding folders
-Drag&Drop
-Signing single zip archive
Click to expand...
Click to collapse
Very nice (and fast) improvements.
I'll be sure to test this on Ubuntu under Mono sometime and lat ya know how it goes.
=]
Nice app ......nice share
nubecoder said:
Very nice (and fast) improvements.
I'll be sure to test this on Ubuntu under Mono sometime and lat ya know how it goes.
=]
Click to expand...
Click to collapse
It'd be nice, but I think that there are some changes in code neccessary.. the main: replacing executting "cmd.exe" to "adb", in ProccesStartInfo variables, so also parameteres are need to be changed (it's necessay to remove "adb" from parameters). I will probably install Linux in a few weeks on the virtual machine, so I'll have the environment to testing the code.
In the meantime, new version - fixed the wrong name of update-script for edify (changed to "updater-script" for edify, and left "update-script" for amend)
benzyniarz1 said:
In the meantime, new version - fixed the wrong name of update-script for edify (changed to "updater-script" for edify, and left "update-script" for amend)
Click to expand...
Click to collapse
aah, good update
benzyniarz1 said:
It'd be nice, but I think that there are some changes in code neccessary.. the main: replacing executting "cmd.exe" to "adb", in ProccesStartInfo variables, so also parameteres are need to be changed (it's necessay to remove "adb" from parameters). I will probably install Linux in a few weeks on the virtual machine, so I'll have the environment to testing the code.
Click to expand...
Click to collapse
What are you using adb for this app? It's just flash-able zip creation correct?
I can't think of a reason you would need to use adb for this (or how adb would be useful for this other than pushing to the phone's SD card).
Just curious, I haven't bothered to look at the sources.
=]
nubecoder said:
What are you using adb for this app? It's just flash-able zip creation correct?
I can't think of a reason you would need to use adb for this (or how adb would be useful for this other than pushing to the phone's SD card).
Just curious, I haven't bothered to look at the sources.
=]
Click to expand...
Click to collapse
ADB is used only for pushing created file to SD card, nothing more.
thanx a lot..... it helped me very much and saved me from full rom flash.....
Updated to new version. Changelong in the 1st post. Enjoy
awesome!thnx a lot!!! its really easy
edit:not tha easy as i thought can someone tell me the script i need to use to copy and maybe replace system apps?
edit1:figured it out
--- copied with permission from nathanpfry.com ---
---If you would prefer a Builduntu install disc, click here to check out this post for an ISO---
BuilduntuVM is a custom branch of the Ubuntu operating system for compiling Android ROMs from source. It includes everything you need to sync with the repo of your choice (Cyanogenmod, AOSP, etc) and start building.
Features:
- Xubuntu 16.04 base
- Installed all necessary software for compiling (list available in the guide link above)
- Unnecessary programs removed (media players, games etc.)
- Geany for editing code
- Repo located in ~/bin and added to PATH
- Quick access drop-down terminal (Ctrl-F12)
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 builduntu zip archive and extract builduntu.ova to your hard drive.
3. Start VB, click File > Import Appliance. Select "Open Appliance" and choose builduntu.ova, then click Next to import the virtual machine.
4. Highlight builduntu 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 mirrors!
Username/Password: android/android
Feel free to donate to the new hardware fund (donate) if you like my work. It would be greatly appreciated!
Please hit the "Thanks" button if this post helps you out!
Code:
[U][B]Changelog:[/B][/U]
v1 - Initial Release Dec 26, 2013
v1.0.1 - Released Jan 03, 2014
.. Added swap space
.. Increased dynamic drive max to 100 GB
.. Installed latest VirtualBox Guest Additions
.. Updated
.. Optimized
v1.1 - Jan 16, 2014
.. Updated and repackaged OVA file for VMWare
v1.2 - Feb 04, 2014
.. System updated
.. Packaged Manifest for data integrity verification
.. FINAL 13.10 edition (future releases will be based on 14.04)
v1.3 - Feb 08, 2014
.. Revised version numbering because I felt like it
.. Rebuilt with Ubuntu 14.04 base system
.. Increased swap space to 4 gb
.. Increased max disk size to 500 GB
v1.3.1 - Mar 02, 2014
.. Rebuilt from scratch using the latest Xubuntu 14.04 Beta 1 release
.. Testing semi-automated environment script
.. Began torrent distribution
v1.3.2 - Mar 20, 2014
.. Rebuilt from scratch again with new Builduntu Install Disc
.. It's just plain better
v1.4 - Apr 20, 2014
.. Rebuilt using Xubuntu 14.04 LTS Official Release base (via Builduntu Install Disc)
.. Added Guake drop-down terminal for more efficient command line, check it out!
.. HD space reduced to 250 GB dynamically allocated (was anyone ever getting close to 500 before?)
.. Shared folders should be working now (you can build in a directory on your host system, add the folder via Settings in VirtualBox)
v1.5 - Dec 27, 2014
.. Xubuntu 14.10 base
.. Installed ccache
.. JDK7 for Android L builds
v1.6 - Jul 17, 2015
.. Xubuntu Core 15.04 base
.. Switch to LVM
.. Reduced OVA size (almost 1 GB smaller!)
.. Removed Guake in favor of xterm drop-down. Ctrl-F12 for the terminal hotkey
.. Cleaned up package list
v2.0 - Apr 29, 2016
.. Rebase to Xubuntu 16.04 with Builduntu ISO v2
.. Transition to OpenJDK 8 for Android M builds
Thanks, downloading it...
Wow! Thank you very much! Will try soon! :good:
Sent from my HTC One using XDA Premium 4 mobile app
Giving it a shot
Been oddly having trouble setting up my environment. Your previous post got me further then any other instructions. I'll give this a shot and see if it resolves my problem. Thanks in advance!
So far its working great! Thanks again! :good: :good:
I am on vmware fusion on Mac OSX 10.9.1, can I install your pre configured ubuntu on it?
Edited:
Oracle seems better in this circumstance anyhow. I was able to optimize ram and cpu settings but how to increase virtual drive. Its a PCIe SSD 1TB. I wanted to increase the VM up to 150GB. I did not see any easy way of doing it?
EDITED:
Figured out with some googling and using the cloneHD and ModifyHD tools built into virtual box and using terminal commands. I was able to resize the VWMK. The real tricky part is once that is done you have to resize in Linux because its still 60GB again google search found an easy way using gparted and modifying the /etc/fstab!!
Edited again:
I think the swap file was really set too low. I made it 16GB which is recommend by the source.android site. I know this helped a lot because it was lagging until I changed it.
Hi
Is it ok to export appliance using virtual box and import it from vmware?
Cos i use vmware workstation 10
Jaskaran498 said:
Hi
Is it ok to export appliance using virtual box and import it from vmware?
Cos i use vmware workstation 10
Click to expand...
Click to collapse
You can load it up perfectly fine in vmware :good: did that myself as I prefer vmware myself ^^
Sent from my HTC One using XDA Premium 4 mobile app
not working for me.
that's what i get when i try to import in VMware.
c4cyro said:
not working for me.
that's what i get when i try to import in VMware.
Click to expand...
Click to collapse
I imported the download into VMware workstation with no problems. I didn't try exporting from virtual box nor with VM player although the player should work the same as workstation.. Maybe try importing the original download without messing with virtual box?
Sent from my HTC One using XDA Premium 4 mobile app
i downloaded and just imported into vmware nothing else.
did not work. using the same file on virtual box works okay.
Hmm idk then, like I said, using VMware Workstation 10 I had NO problems importing and running it
Sent from my HTC One using XDA Premium 4 mobile app
Thanks a lot for providing Builduntu, saves alot of trouble
i was wondering..
how much free space do i need to have to get the compiling done? i mean...how much is recommended?
Nice one, thanks!
I think this needs to get a sticky!
Uzayr said:
Thanks a lot for providing Builduntu, saves alot of trouble
i was wondering..
how much free space do i need to have to get the compiling done? i mean...how much is recommended?
Click to expand...
Click to collapse
i also want to know same thing
mor_1228 said:
i also want to know same thing
Click to expand...
Click to collapse
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
sylentprofet said:
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
Click to expand...
Click to collapse
i have one till this step now what to do ?
1. Download and install VirtualBox for your host system from here.
2. Download the latest builduntu zip archive and extract builduntu.ova to your hard drive.
3. Start VB, click File > Import Appliance. Select "Open Appliance" and choose builduntu.ova, then click Next to import the virtual machine.
4. Highlight builduntu in VirtualBox Manager and open Settings. Under "System" you may 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!
now how to get psx rom latest build ? can make tutorial to add or remove or merge features of different roms into 1 ? :highfive:
sylentprofet said:
All said and done you're looking at 40-50 Gb.
It's 10 or so for the repo source of your choice and device trees (AOKP, CM, etc.) then the build process itself takes another 30ish. You can "make clobber" in between builds to free up that 30 gig, but any time you compile a ROM it's going to need that space again.
By the way - the virtual hard drive on the VM is dynamically allocated, so it will only expand out the space as it is required. However, it won't "shrink" back down again, even after you delete the files.
Click to expand...
Click to collapse
i tried the 2.0 build with virtual box. i get to choose whether i need to start ubuntu normally or in recovery..and after i make my choice i'm stuck in a black screen....nothing happens
i'm going to try 2.1 and give it another shot.
When I open terminal and enter su to grant root permission and enter password android, it says Authentication Failure
what is the password in that instance? how do i get root permission?
jblazea50 said:
When I open terminal and enter su to grant root permission and enter password android, it says Authentication Failure
what is the password in that instance? how do i get root permission?
Click to expand...
Click to collapse
yeah su doesnt work but sudo command work well with password android.
i tried to change password but system hang
--- 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
Building A Kernel For A6k
Hello Folks, Looks like A6000 Forums Are On Fire So Now I AM HErE TO POuR Oil In The FIRE
Lets Get Straight To The POint
This Guide Will Help you build a kernel for our little Precious One
Requirements:
Ubuntu[DOnt Ask How]
Required Libs like libncurses, and stuff [If you face any such error realted to libs, just google Once]
Good Internet
AT least 2GB RAM and a good processor
A bit of your time
Patience and brain
Steps:
1) Create A folder anywhere with any name you want and open it
2) Open terminal in that folder and Run This COmmand Which will install all required Libs
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
3)After It gets done now we need a toolchain so now type " mkdir kernel" and "cd kernel" without quotes
4) Now we will dload toolchain so first install GIT and GCC libs for ex
"sudo apt get-install git"
Now Run This to clone the toolchain
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
5)After toolchain gets downloaded now we need kernel sources, to simplify it clone the sources from my GIT using this command in terminal
Code:
git clone https://github.com/varunhardgamer/kernel_lenovo_a6000.git
6)After Dloading kernel sources open the kernel sources folder which may have name Semar Kernel or something like that and open BuildingKernel.txt and understand the way you need to edit Build.sh
Its not hard you just need to type the address to your kernel folder which you made
7)Now type
Code:
make ARCH=arm
and press enter
8)Then RUn
Code:
make wt86518_defconfig
9)THen Run
Code:
make menuconfig
and a popup will appear showing you all the tweaks that can be included in the kernel, select accordingly and save it
10)After you Finish tweaking it, open build.sh and edit it acordingly and then run the script by " .build.sh " in the terminal and wait till you get the zimage which is the kernel
8)Now download semar kernel r5zip and push your zimage inside it and flash your first Kernel
COmment here if you face any Errrors
Kernel Source _ https://github.com/varunhardgamer/kernel_lenovo_a6000
Credits to-
Me
Mr.AW
@3lambda
Orata
@mshoaib7
@dev_harsh1998
and XDA Forums
Reserved
Link To the original Thread
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks To @3lambda
[Really THanks Man]
Just In Case
DualBoot Coming Soon By The WAy
The MErc With A MouTh is Back
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
dev_harsh1998 said:
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
Click to expand...
Click to collapse
Ok but the build.sh that i have mentioned will have to be edited again
Oh man
OK wait
Some Modifications To the guide will be done by tomorrow
No worries you doing good work
dev_harsh1998 said:
No worries you doing good work
Click to expand...
Click to collapse
Thanks Limit DOne
WIll thanks Tomorrow
You need to edit build.sh
Change -j64 to -j4 or it'll mess up for everyone.
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
dev_harsh1998 said:
The source you have mentioned isnt the proper source for Kernel and is Limpy when it comes to New stuff support better you link them to this repo :- https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916
and GCC-4.7 is old and has regression bugs Better use gcc-4.8
Regards,
dev_harsh1998
Click to expand...
Click to collapse
+1
Use this kernel it's updated nd better.
Has.007 said:
You need to edit build.sh
Change -j64 to -j4 or it'll mess up for everyone.
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
+1
Use this kernel it's updated nd better.
Click to expand...
Click to collapse
Oh Thanks for pointing that 64 out:good:
Thanks
The Hard Gamer said:
Oh Thanks for pointing that 64 out:good:
Thanks
Click to expand...
Click to collapse
Welcome. Keep up the good work. :good:
Lol, just rechecked your git.
The kernel will not compile. You need to define the toolchain.
Has.007 said:
Lol, just rechecked your git.
The kernel will not compile. You need to define the toolchain.
Click to expand...
Click to collapse
I myself used this method and compiled a kernel
And for toolchain
I already mentioned
export cross_compile in .sh
The Hard Gamer said:
I myself used this method and compiled a kernel
And for toolchain
I already mentioned
export cross_compile in .sh
Click to expand...
Click to collapse
bad command practise..
is it work for any version of Android? currently I'm using RR 5.8.2
hayatnas18 said:
is it work for any version of Android? currently I'm using RR 5.8.2
Click to expand...
Click to collapse
Wait till i update the guide again
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