Hey, I was wondering, is there anyone else who would like to see a GUI Kitchen with support for multiple devices as modules( compatibility packs if you want to call 'em that ), and that would fetch packages from a central repository?
It would allow you to create a new project, choose from several target devices, if it's not on the list it would fetch a list from the server allowing you to download the module, some modules could have a 'supported devices list' on its description files.
The packages would work the same way, fetch the list, download package.
Auto-update for everything including the kitchen itself.
IMHO it's a great idea, there's currently lots of file duplication/scattering, it would also be great because chefs would only need to create packages, base roms, developers would create the device modules, I mean, it's simpler.
Users would have the choice of picking a base rom, selecting the packages from the menu and create their own rom configurations, thousands and thousands of them, no more complaining about softwareXXX being or not included on the final rom and creating a rom with updated software would be as simple as "Update>Packages" "Project>Rebuild".
Even if the final product has a price( :X ) I think it is worth it.
You bet I would.
we're the only ones though
ME 2
Apoc said:
we're the only ones though
Click to expand...
Click to collapse
Dnt Forget me...i am trying using command type..but iwished of GUI
although its aawailable by Xpload for BA only..i want for Himalaya
This is a nice ROM tool but if there were only more detailed instructions...
This is a nice ROM tool but if there were only more detailed instructions...
http://forum.xda-developers.com/showthread.php?t=324682
cash365 said:
This is a nice ROM tool but if there were only more detailed instructions...
http://forum.xda-developers.com/showthread.php?t=324682
Click to expand...
Click to collapse
Yeah, that's a nice set of tools and batch files.
There's also a multi-device version here: http://forum.xda-developers.com/showthread.php?t=324680
It isn't hard to use, and it's quite complete in terms of functionality, plus, the method he used to make it multi-device is nice, you only need to change one line and it's done, all the parameters for a specific device are on a separate conditional batch file.(tho I tested it and it didn't work, previous CORE kitchens worked nice)
But the ideal would be something like this: http://forum.xda-developers.com/showthread.php?t=304461
To be available to public and have all the functionality of the CORE kitchens.
btw, I don't think this is a noob vs pro issue, the kitchen I try to describe in the 1st post would centralize all packages, and IMHO is something the whole xda-devs needs.
up up and away
Apoc said:
Yeah, that's a nice set of tools and batch files.
There's also a multi-device version here: http://forum.xda-developers.com/showthread.php?t=324680
It isn't hard to use, and it's quite complete in terms of functionality, plus, the method he used to make it multi-device is nice, you only need to change one line and it's done, all the parameters for a specific device are on a separate conditional batch file.(tho I tested it and it didn't work, previous CORE kitchens worked nice)
But the ideal would be something like this: http://forum.xda-developers.com/showthread.php?t=304461
To be available to public and have all the functionality of the CORE kitchens.
btw, I don't think this is a noob vs pro issue, the kitchen I try to describe in the 1st post would centralize all packages, and IMHO is something the whole xda-devs needs.
Click to expand...
Click to collapse
It may be multidevice but it doesn't cover the hx4700.
Is there a kitchen for the trusty ipaq?
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
xelasha said:
Hey guys was wondering about flashing my HTC Touch Diamond, But I want a decent ROM.
Something that's not too packed up full of junk, Easy to use and a better performance.
Also maybe a guide to unlocking/debranding this phone along with a flash guide if that's not too much?
cheers.
Click to expand...
Click to collapse
From one newbie to another, you should read the sticky posts... they are full guides and information about flashing your phone's ROM / Radio etc.
The forum 'Search' facility is your friend, it like's to be used. That's what I did and found all I needed to know about the available ROM's and Flashing process without having to ask a single question.
The New World ROM introduced a much-improved version of the Open Firmware interpreter, version 3.0, which added many missing features, fixed most of the bugs from earlier versions, and had the capability to run CHRP boot scripts. The Toolbox ROM was embedded inside a CHRP script in the System Folder called "Mac OS ROM", along with a short loader stub and a copy of the Happy Mac icon (in Mac OS X 10.2 and higher, this was replaced with a silhouette of the Apple logo on a blank gray screen) suitable for display from Open Firmware. Once the ROM was loaded from disk, the Mac boot sequence continued as usual. As before, Open Firmware could also run a binary boot loader, and version 3.0 added support for ELF objects as well as the XCOFF files versions 1.0.5 and 2.0 supported. Also, version 3.0 (as well as some of the last releases of version 2.x, starting with the PowerBook 3400) officially supported direct access to the Open Firmware command prompt from the console (by setting the auto-boot? variable to false from Mac OS, or by holding down Command-Option-O-F at boot).
rajas
new rom
Here is my full gui tool for creating boot logo files, for a number of Motorola Devices.
You get a preview of the picture, exactly how it would look on your device.
Features
Open Existing Logo.bin files
Open Existing Flashable zip files
Create logo.bin files
Create Flashable zip files
Export images from Logo.bin / Flashable zips.
Instructions
To use, you just double click on the treeview entries, select your picture, and repeat that process for all of the files that would be in logo.bin You then go to File / Save, and then save either as a .bin file, for flashing using fastboot, or as a Flashable zip file, for flashing using TWRP or CWM. In general, boot_logo is used on a factory locked device, and as a result, you probably should clear that one, as you would be wasting your space. logo_battery is your 0-3% indicator when the battery is run dry, and you plug it in to charge. logo_unlock is the actual boot screen logo you see on unlocked devices.
You can also open existing logo.bin files, wither from zip files, or directly, in order to modify them. Custom mode is for the advanced users, or for cases where a new Motorola device is released, where its logo.bin contains files that are not known. This tool auto-detects whether the file is the pre-kitkit format or not, and pictures that are larger than screen resolution, or in the case of pre-kitkat format, 540x540 is automatically scaled down. Upscaling options are provided, but centering the image is the default selection.
Bugs
None that I am aware of. If any are found, report them.
Limitations
The tool will not create any logo.bin files that are greater than 4MiB. This is a device limitation, specifically the logo flash partition is exactly 4MiB in size on all the known devices that I specifically support with this tool. As such, you may have to downscale or reduce the bpp formats of your images, to get them all to fit within the 4MiB. (Moto X Play has 6MiB, and Moto X Style has 8MiB).
Version History
Version 2.4 - Released Oct 21, 2015 - Download
All 3 Moto G listings merged into one listing, due to screen size and logo.bin size being the same across ALL 3 of them.
Updated the Moto E listing, with the 2nd gen, (no seperate listing due to both generations having same screen size, and same logo.bin max size.)
Older versions:
Version 2.3 - Released Oct 19, 2015
[new] Added Moto X Play, Moto X Style (Pure), and Moto G 3rd Gen to device list.
Moto X Play has a 6 MiB logo.bin size
Moto X Style (Pure) has a 8 MiB logo.bin size
Version 2.2 - Released Sept 15, 2014
[new] Metadata added to created logo.bin files - The following data is present.
Version of this program that created the bin file. (was present since Version 2.0)
Motorola Device Selected
Motorola Device Resolution
User Comment
Version 2.1 - Released Sept 9, 2014
[new] Default logo_charge image predefined, where applicable.
[new] logo_boot and logo_unlocked are now linked together, unless you load different images for each of them.
[new] Duplicate images loaded no longer wastes space in logo.bin
Version 2.0 - Released Sept 8, 2014
[new] Last selected device is now remembered between sessions.
[new] Added in Moto G 2nd Gen. (2nd gen does not have a logo_charge in its current firmware.)
[new] Added in Moto X 2nd Gen. (Larger screen in Moto X 2nd Gen, logo_charge and logo_lowpower present. The one thing that bugs me, is that motorola did not expand the logo partition size, still retains it at 4MiB for that device, so one is pretty limited in full screen picture complexity.)
[fixed] Fixed a few bugs that were introduced in Version 1.9
Version 1.9 - Released Sept 3, 2014
[new] Added in the stock images for logo_battery, logo_lowpower, and logo_unplug, that the program will put into the logo.bin, if you don't specify a custom logo for these images.
Version 1.8 - Released Aug 30, 2014
[changed] Turns out Moto G as of the Android Kitkat 4.4.4 OTA update supports logo_charge. Updated accordingly, and put a note in the tool tips on its use case.
Version 1.7 - Released Aug 24, 2014
[changed] Big performance boost of saving logo.bin/flashable zips.
Version 1.6 - Released Aug 22, 2014
[fixed] Fixed a null reference bug that happens if you switch logo.bin versions right from program startup, as well as a few other potential null reference bugs.
Version 1.5 - Released Aug 20, 2014
[changed] More improvements to the logo compression algorithm.
[new] Added Landscape mode
[new] Logo fill/Layout options can now be set per image, for example, logo_battery with fill on landscape, and logo_boot with center on portrait.
Version 1.4 - Released Aug 17, 2014
[changed] Made the device selector a combo box. Each device prepopulates the tree with the logo options available to it, as well as controlling what logo.bin formats are available.
[fixed] Corrected a bug in 540x540 color encoding/decoding.
[fixed] Corrected a bug where if 540x540 formats were selected, and you didn't pick an image for at least one of the logos, the process would error out with an exception.
[new] Added some info to the about box, regarding optional donations via bitcoin or paypal.
Version 1.3 - Released Aug 17, 2014
[changed] DotNetZip library now statically linked.
[changed] Source code now lives on Github
Version 1.2 - Released Aug 17, 2014
[new] Added Support for Raw 540x540x24bpp logo.bin format
[changed] No longer creates temp files for any of the processes.
[changed] updater-script and update-binary are now built in.
[fixed] Loading of images no longer locks them from being renamed/deleted till the program is closed. (They are loaded into program memory.)
[fixed] logo.bin can now be loaded from any zip file, even if logo.bin is not at root within that zip file, such as from stock firmware zip files.
[changed] Process of creating zip/bin now outright aborts if there was an error loading every image loaded in the process.
[changed] An opportunity to abort the process is presented if you try to save bin/zip with no images loaded.
[new] Tool tips now added on the tree nodes for logo_boot, logo_battery, and logo_unlocked. As I do not have a Moto E, I cannot determine what causes logo_lowpower and logo_unplug to show, to be able to advise on these.
[new] logo.bin and flashable zips can be dragged and dropped onto the application.
Version 1.1 - Released Aug 16, 2014
[new] Added Export Image
[changed] Far fewer temp files created, and the program attempts to clean up after itself.
[new] Progress info added on file loading
[fixed] Progress info runs smoother now.
[new] Now info is displayed as to how much logo.bin is too large by, when the selected images result in too large a logo.bin
Version 1.0 - Released Aug 15, 2014
Initial Release
XDA:DevDB Information
[APP] Motorola Boot Logo Maker, App for the Moto G
Contributors
caitsith2
Source Code: https://github.com/CaitSith2/MotoBootLogoMaker
Version Information
Status: Stable
Current Stable Version: 2.4
Stable Release Date: 2015-10-21
Created 2014-09-17
Last Updated 2015-10-21
Reserved
Is "logo_battery" the one that appears when the phone is at 0%?
And when does the "logo_unlocked" screen appear?
@caitsith2 ..... Very nice I've added thanks ..... I have been using caroc's script to create my logos and paint.net to modify the images ..... this App makes it much simpler :good:
rpcll said:
Is "logo_battery" the one that appears when the phone is at 0%?
And when does the "logo_unlocked" screen appear?
Click to expand...
Click to collapse
logo_battery is indeed your phone at 0% image. logo_unlock is typically the image you should replace, as that as the one that contains the unlock warning screen.
And when does the "logo_boot" screen appear?
When I boot my phone i see logo_unlocked screen
@caitsith2 ..... The comments I made in post #3 were made when I had run your App to see what it looked like but had not used it to try and make a boot logo. I have to say that the GUI interface is attractive and that made me comment as I did. When I used your App it failed to make a single logo, each time leaving me with just a "white" illuminated screen before the bootanimation started.
Having made 20 or 30 Boot Logos both for myself and others I have an ample supply of images to use, with the knowledge that each of the images has already successfully been used in the creation of Boot Logos for the XT1034 Moto G.
Looking at the files associated with your App, I see that you have used (word for word) two files (1) update-binary and (2) updater-script which have been associated with other scripts dating back to 2013 but you have not kept the same file structure i.e. ..... META-INF>com>google>android..... and it's in the folder "android" that files (1) & (2) above appear. Is it possible that you have missed this?
I haven't tried flashing with "fastboot" - I prefer to flash through Recovery and I think the majority of noobs prefer that easier method so maybe you could check your scripting. I used 12 different images all of which have been used to successfully create Boot Logos so maybe you could check
I was able to create a new bootlogo from scratch, but wasn't able to open any logos from this thread (http://forum.xda-developers.com/showthread.php?t=2686441) to edit them.
metpolds said:
@caitsith2 ..... The comments I made in post #3 were made when I had run your App to see what it looked like but had not used it to try and make a boot logo. I have to say that the GUI interface is attractive and that made me comment as I did. When I used your App it failed to make a single logo, each time leaving me with just a "white" illuminated screen before the bootanimation started.
Click to expand...
Click to collapse
For this, bit, you may have missed that you should be replacing logo_unlocked, as that is the logo your phone is going to show, if you did indeed unlocked it.
If you could help me out, upload one or two of your unsuccessful zips, and I will have a look.
metpolds said:
Looking at the files associated with your App, I see that you have used (word for word) two files (1) update-binary and (2) updater-script which have been associated with other scripts dating back to 2013 but you have not kept the same file structure i.e. ..... META-INF>com>google>android..... and it's in the folder "android" that files (1) & (2) above appear. Is it possible that you have missed this?
Click to expand...
Click to collapse
Actually, the program creates the directory structure in the zip file itself. Just open up the zips created. You will see that the zip contains
META-INF>com>google>android>updater-script
META-INF>com>google>android>update-binary
logo.bin
All of which are part of a normal flashable zip file.
metpolds said:
I haven't tried flashing with "fastboot" - I prefer to flash through Recovery and I think the majority of noobs prefer that easier method so maybe you could check your scripting. I used 12 different images all of which have been used to successfully create Boot Logos so maybe you could check
Click to expand...
Click to collapse
rpcll said:
I was able to create a new bootlogo from scratch, but wasn't able to open any logos from this thread (http://forum.xda-developers.com/showthread.php?t=2686441) to edit them.
Click to expand...
Click to collapse
Okay, I had a look at the contents of some of them, and was not aware of a third logo.bin format, which is just a raw 540x540x24bpp image.
Guess I will have to specifically add support for that format. You should be able to edit the logos that look like they fill the entire screen in the mean time, as that requires using the "kitkat" formatted logo.bin format.
Delgado666 said:
And when does the "logo_boot" screen appear?
When I boot my phone i see logo_unlocked screen
Click to expand...
Click to collapse
logo_boot is strictly for boot-loader locked phones, while logo_unlocked is strictly for boot-loader unlocked phones.
@caitsith2 ..... SUCCESS :laugh:..... Your comments have cleared up the misunderstanding that I think at least two of us were to having i.e. If we are using an unlocked bootloader then we have to chose "logo_unlocked" whereas if our bootloader is still locked then we must use "logo_boot". I used 4 of my previous "failed" images and had 100% success this time around.
I endorse what I said originally, the GUI is elegant and a pleasant and effective advance on the cmd line scripts that most of us have been using, in consequence I have "rated" the thread. Please take the following comments as suggestions NOT as criticism. I think you will find that 90% of the thread users have unlocked their bootloaders and you could consider changing the tree "titles" to more clearly indicate which is which ..... alternatively ..... you could add a couple of lines to the instructions to clear up any misunderstanding.
I take heed of your comments regarding the two META-INF scripts and apologise for not researching deeper.
I think this thread deserves more publicity and will do what I can in this respect.
metpolds said:
@caitsith2
I endorse what I said originally, the GUI is elegant and a pleasant and effective advance on the cmd line scripts that most of us have been using, in consequence I have "rated" the thread. Please take the following comments as suggestions NOT as criticism. I think you will find that 90% of the thread users have unlocked their bootloaders and you could consider changing the tree "titles" to more clearly indicate which is which ..... alternatively ..... you could add a couple of lines to the instructions to clear up any misunderstanding.
I take heed of your comments regarding the two META-INF scripts and apologise for not researching deeper.
I think this thread deserves more publicity and will do what I can in this respect.
Click to expand...
Click to collapse
And now, you no longer have to worry about those META-INF files, as I have now embedded them into the program,
And the tree now shows a tool-tip as to the purpose of the items, when you hover the mouse over the item.
The next version will be built with the Ionic.Zip.dll zip library built into the program, so that the program can truly stand alone.
Yeah, additional awareness would be good, as this should work with any motorola phone that has a flashable boot logo.
Phones that are Moto E and later, will likely have logo_boot, logo_unlocked, logo_battery, logo_lowpower, and logo_unplug.
Moto X/Moto G/Droid Ultra has logo_boot, logo_unlocked, logo_battery.
Motorola phones released mid-late 2012 have just logo_boot and logo_unlocked. Motorola phones released early 2012 (Droid 4) and earlier, have just the raw 540x540 logo. Although those phones only have 1MiB partitions, it will never be exceeded on those devices.
Very nice, does everything I need.
Got to repeat myself here ..... this App is by far the best which has emerged in this Forum in respect of creating boot logos ..... the GUI is by far the best, cleanest, easiest and is simplicity itself to use ..... had to "bump" it back to top of the queue, couldn't let it languish on page 2.
I second that!! indeed this is one of the best app for me that i have found till now for creating boot logos
thanks for the tools
like this
check my bootlogos: here
Version 1.5 released. Check OP for details.
Version 1.6 released. Fixed a fairly major bug.
Excelent! i will change my bootlogo once a week with this!
Do you plan to make custom boot animations possible with this on a future update? Or this is just for the logos?
Anyway, thank you for efforts on this :good:
UncolourTV said:
Excelent! i will change my bootlogo once a week with this!
Do you plan to make custom boot animations possible with this on a future update? Or this is just for the logos?
Anyway, thank you for efforts on this :good:
Click to expand...
Click to collapse
This is just for the boot logos and anything that Motorola decides to store in the boot logo partition.
With the release of Xiaomi's Windows 10 rom, is there a possibility that this could be ported over to phones such as the LG G3 with the same chipsets, chips and ram??
Would definitely breath new life into the device and something i would be willing to donate for.
It would definitely be a possibility, but devs would have to be willing to put a lot of time and work into learning the structure of the new os and adapting it to the dissimilar hardware between the g3 and the mi4
I was guessing the same thing but the first emerging problem is the following (please correct me if I'm wrong, I'm here to learn):
when you extract this specific rom, you find out about 20 partitions (unlike other lumias)..and it's almost the same number of partitions that an android rom for xiaomi has.
So my guessing is: xiaomi's bootloader hasn't changed, it's the same for windows 10 mobile and for android. They build a rom (probably working on the NT kernel of windows) suitable for this specific device. Of course lg's devices manage the memory with a different partition scheme..so, if I haven't written wrong things (otherwise correct me), to make a port is necessary to have an in dept knowledge of window's kernel (a not so simple task since it's closed source) in order to change *at least* the partition scheme and to make it suitable with lg's bootloader. People who can manage with this task, as far as I know, are not too much..