Note : I'm just sharing the work of the XDA Member Vincent8111.Only works on Windows and contains nearly 400 bootanim therefore 1.6GB.
You can send the bootanim in ADB if you enable debug or create a zip and flash it.
You can also resize the image or the display to correspond to your resolutions.
You can add your own animations, just create a directory in "bootanimations" program and put the bootanimation.zip file there
Downloads : 1.Bootanimationchanger (Full Version) - (i) http://www.oledecran.com/bootanim_changer_install.exe
(ii) ftp://XDA-Dev:[email protected]/Android/Vincent8111/bootanim_changer_install.exe
Torrents : 1. http://forum.xda-developers.com/attachment.php?attachmentid=1988797&d=1369445055
1.Bootanimationchanger (Compressed Version) - http://www.oledecran.com/bootanim_changer_install_light.exe
2.Bootanimationchanger v2 (New version with choice of uncompressed ZIP in resize) : http://www.oledecran.com/bootanim_changer_install_exe_v2.exe
Original Thread : http://forum.xda-developers.com/showthread.php?t=2278525
Credits :
Vincent8111
Click to expand...
Click to collapse
I think it would be best if you made one thread and shared everything there, as you're sharing a lot of things.
Envy-X said:
I think it would be best if you made one thread and shared everything there, as you're sharing a lot of things.
Click to expand...
Click to collapse
I know that sir but nobody would open a single thread to view all it's contents.The thread will become older and ultimately vanish from the section :/
Creating individual threads would obviously attract the members and in this way the thread will not be dead.
Hello Guys...:good:
-So,I'm here to Explain you "Create Basic Device Tree on your Own and Build a Custom Recovery".:fingers-crossed:
I'm providing you Two ways of Guide...:highfive:
1)Youtube Video
2)HTML Guide
Video Guide :
HTML Guide :
Link : https://mega.nz/#!Fxpk0T4Q!ZMShu7_VDG2HDhLCJze8DysTcjskXtTPKzsiAaoCJKc
or From Attachments
The Required File During The Process link : https://mega.nz/#!RghWgbwb!_zBLcurAg2DiejHKyw6fwTz564a3pO3UH1mhdIKClb0
Happy Developing
DevelopersWork said:
HTML Guide :
Link : https://mega.nz/#!Fxpk0T4Q!ZMShu7_VDG2HDhLCJze8DysTcjskXtTPKzsiAaoCJKc
or From Attachments
The Required File During The Process link : https://mega.nz/#!RghWgbwb!_zBLcurAg2DiejHKyw6fwTz564a3pO3UH1mhdIKClb0
Click to expand...
Click to collapse
Dear Gopinadh,
could you please re-upload the guide.zip ("the required file during the process"). It is no longer available on Mega.
Thank you
io2345
Hello,
I'm using a HTC One m7 currently running the now defunct Cyanogenmod rom, dl from them: version 12.1-20160325-nightly-m7
On this build, when browsing non-ssl website, a script tag is added at the end of the head block (most of the time):
Code:
<script src="http : / / softwarebundles . com/js/in.js"></script>
(I add to break the link to post it here (forum restrictions))
This js script seams to replace the src of some specific iframe, it seams ads related.
I have the same result in the default browser, chrome and firefox.
- Can a app be responsible for it ?
- If you are still using a cyanogenmod rom, can you check the source of some non-ssl website ?
- anything I could check ?
Thank you.
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
So this is my first time publishing an Android app. Now I successfully convert my aab into apks and then unzip it into many smaller apk. However, now I am confused about which one should I send to my beta tester? There is so many different apk like
standalone-arm64_v8a_hdpi.apk
standalone-arm64_v8a_mdpi.apk
standalone-arm64_v8a_xxxhdpi.apk
standalone-armeabi_v7a_mdpi.apk
and many more. I am guessing we need to match the apk for the specific device? However, if I want to upload my apk into a website and the user can download the apk directly from the website in the future. which apk should I upload then? Since it's impossible to determine the device info beforehand? Hope my question make sense. Thanks
Jimbotron126 said:
So this is my first time publishing an Android app. Now I successfully convert my aab into apks and then unzip it into many smaller apk. However, now I am confused about which one should I send to my beta tester? There is so many
...
upload then? Since it's impossible to determine the device info beforehand? Hope my question make sense. Thanks
Click to expand...
Click to collapse
Those version of your apk are for users running different chipset and different screen dpi. Those apks are uplaoded to google play, and when someone downloads the app, it's the right apk for them that gets installed right away (they don't have to choose).
From my experience, screen dpi isn't a problem when installing, the only problem you could face is when installing arm64_v8a on an armeabi_v7a device (installing 64bit app on a 32bit device). 32bit devices tend to be rarer and rarer so if you had to post your app for testing it would be any of the arm64 apk + any of the armeabi_v7a apk.
Because probably an Android user neither knows about the meaning of the DPI-bucket-shorthands ( MDPI, HDPI, XHDPI, XXHDPI, XXXHDPI) or ABI-shorthands, IMO it's recommended to offer in your web-site to your users a Powershell script to download what either by means of ADB gets Android device's DPI-bucket-setting & ABIs supported and then automatically selects the proper APK to get downloaded or provides a simple menu where users can select the matching APK related to their phone's ABI and/or DPI to get downloaded.
Read more here:
Use PowerShell to download a file with HTTP, HTTPS, and FTP
In PowerShell, you can download a file via HTTP, HTTPS, and FTP with the Invoke-WebRequest cmdlet
4sysops.com
Example Powershell menu skeleton:
Code:
do
{
Show-Main-Menu
$selection = Read-Host "Please make a selection"
switch ($selection)
{
'1' {
Show-DPI-Menu
} '2' {
Show-ABI-Menu
}
}
pause
}
until ($selection -eq 'q')