[Main-OUTDATED] The Development Chronicles... [Day 4 - 08/25/08] - Wing, P4350 ROM development

These are the development chronicles. They will chronicles the creation of Just, my next ROM. I will keep track of everything I do here. Please do not post anything on this thread. I will create a second sister thread where you can ask questions. Please keep the threads clean of anything that is not related to the subject. I am not a mod, so I cannot delete posts, so I will rely on your honor.
Note: Since I work full time (actually, about 46 hours...), am a student and I'm getting married soon, my time is a little on the limited side. This will not be updated daily. Ivan's Class will not be cancelled, but will be placed on hold for the mean time. I will probably copy and paste lessons from there to here to save time, though. Since this is going to be my next rom, let's hope that I will keep at it until we have a working ROM.)

Day 1: Our OEM
Today we'll be getting our OEM. To do so, we will follow the following:
Welcome to Lesson 2. Today, we will learn how to decompile a ROM using Hypercore. This will serve us in two ways.
1. You'll understand how to decompile a ROM and obtain files from it.
2. You'll be able to get started building your own OEM folder. This OEM folder will be the basis for every ROM that we will be building in these lessons.
To begin:
Go here and download the Hypercore.7z file. You'll need 7Zip in order to open the file. Uncompress the hypercore folder into your desktop. Uncompress the Core folder into your main drive (C for MOST people.) These are my personal folders so you'll get more tools, fixed batches, correct settings for the Herald... and probably some random junk.
Here is where the fun starts. Start by grabbing a base ROM. You can use either Tmobile's Wing ROM or HTC's Herald ROM. I'm sure you can find a copy somewhere...
If you've downloaded 7zip, you should be able to right click on the RUU file and extract it somewhere. You'll notice that one of the files is named RUU_signed.nbh. This is a ROM in its NBH format.
Extracting the files in your NBH.
Go to your newly created HyperCore folder, open up Tools, then NBH_Tools_v1.1.
On the first tab, you will notice one and only one button... Press it.
Search for your RUU_signed.nbh file and click Open.
Save the files somewhere.
As you can see... this isn't rocket science.... yet.
Blind Date with HyperCore
Just to tell you a few things about HyperCore:
You will be working with the HyperCore folder. The Core folder includes all the things that are done in the background. Don't touch it.
The Panel folder holds most if not all the batch files that make the kitchen possible.
The Build Folder is where you'll find your OEM folder once we're done with the next step.
Extracting your files
Find Windows.nb in the folder you just extracted everything to.
Rename this file to os.nb
Copy the os.nb file to your HyperCore/Extract/Source folder.
Go to HyperCore\Panel\Extract and launch DumpRom.
Press Enter and wait...
With any luck, you'll see:
{
"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"
}
Press 1 then Enter to Start the Package Tool. Press Enter again. Then 3 and Enter to do it manually.
Go to File, Open, open your HyperCore\Extract\Dump folder.
Click on Tools, then Build Packages but do not close that window.
Rename the Dump folder into Packages and then close the Package Tool.
Press 4 to move your OEM and SYS folders. Press N to bypass making a backup.
That's it. Now you have your very own OEM folder to play with. You can discard the SYS and ROM folders, as we will not be using them in this class. The next lesson will teach you about the OEM folder, what it does, how to clean it up, etc. Then we will be downloading our other kitchen. Bepe's kitchen... or maybe my own EasyBakeOven... anyhow, it's late and the only reason I'm still up is because I promised you guys a lesson. It might not be pretty, but it will get the job done. Maybe I'll fix it up and rewrite it later when I'm fully awake. lol
Click to expand...
Click to collapse
Source: My Cooking Class: Lesson 2
The XIP and SYS will be extracted next. I will be using the XIP from Bepe's kitchen as a base to port other XIP's over. The SYS will come from somewhere else... I haven't decided which SYS to use.

Day 2:
OK, so we have the OEM folder which is where most of my ROM is going to come out off. Now it's time to plan out my goals so we know what we're building.
Goals:
80mb free of storage for LZX version
30+mb of RAM
A dark red and black theme
Raw speed
Stability above all else
Starting from scratch with a new core, instead of working with my previews cores like I did with Just2Clean and JustMe.
umm.... All my ROMs are the same aren't they? lol
So we have to familiarize ourselves with the OEM folder.
Lesson 3: Getting Personal with Your OEM
In today's lesson we are going to learn what the OEM folder is, what it does, how it does it, and why it is so important to you personally as a cook. This will be your signature and where most of what makes the ROM yours will take place...
The very first thing we will do, though, is make sure that you have your computer set to show all hidden and system files.
Open up the folder that holds the OEM folder, go to Tools, Folder Options, click on View, make sure Show Hidden Files and Folders is checked, hide extensions for known types in NOT checked and Hide Protected Operating System Files is NOT checked. Please do not go around deleting files in your computer after this and then PMing me that your PC will no longer boot up.
File Structure
The file structure of a STOCK OEM folder is as follows:
LangDB
OEMAPPS
OEMDrivers
OEMMISC
OEMOPERATORS
OEMVERSION
OEM_DPI_96
OEM_Lang_0409
OEM.cer
What does this mean? - We will not be getting into all of them, only the ones important to today's lesson.
OEMAPPS - This is where all the OEM apps are stored. This means all the apps that are not originally part of the OS and were placed in by the phone manufacturer. These apps include the camera utility, a java manager (usually a crappy crippled old one, too...) etc. This folder is usually full of random useless things but has no real order within it. You'll see files for things like an FTP-Bluetooth utility and other things you might not need. Cleaning this OEM folder will be the meat of our cleaning process (although not the only place.)
OEMDrivers - This is where the drivers of the device are stored. You'll also notice that a few ringtones and such should be listed in here. These will be part of the cleanup process, too. The only driver here which you can touch will be the touch.dll (no pun intended.) This driver will be replaced later on to allow for BioTouch (the ability to touch the middle of the screen to scroll instead of the side bars.)
OEMOPERATORS - This is where a lot of the junk that your OEM puts in goes to. This is also where you can set your preferred theme and setup your UC compatibility. Unless you're me... and you use a separate package... more on this later.)
OEM_Lang_0409 - You will see a lot of MUI's here. MUI's store the wording on programs and thus the language of your device. More on this later. This is also part of the cleaning process.
So now you have a VERY basic overview on the OEM folder. We will get more indepth as we go through this class.
Click to expand...
Click to collapse
Source: My Cooking Class: Lesson 3

The Clean...
Day 2: Part 2:
OK, cleaning an OEM folder is the funnest/least fun part of making a ROM, depending on how you see it. To me, it's a fun investigation game.
I'm going to just list the folders in the OEM one by one and post exactly what I've done with them.
We have a couple of ways of cleaning out files we don't want. We have the research way, which means we will research to see what the files do. This one we do AFTER we get rid of the bulk of useless files. The second way, which is actually a short cut I made up... is to find packages of programs that you do not want and copying and pasting those files into my OEM folders. By default, windows will leave those files highlighted when the copy is done. All the files, even if they overwrote the files you had in there that you don't want anyways. Then, you just delete those files. If this sounds confusing, that's how everything in my head it... lol
So....., in practice:
Open oem package of program you don't want.
Copy all the files.
Paste them into the first OEM folder.
Delete the files.
Paste them into the next folder.
Delete the files.
etc.
It's a cheap trick, but it does its job well.
So how do we know which programs are in that we don't want? Install the stock RUU and write down what you want to get rid off. Or look through the files and research to find out what they are.
If you really want to be extra picky, you can also search for all the registry keys that the RGU has in that package as well.

Hey Ivan. Nice informative thread you got here. Long time, how you been. Congrats on your wedding
There, I posted a junk post But me being a Mod, can delete useless posts from here to keep it clean (including mine) Just let me know when you wish to get this one cleaned up

lol. You're forgiven this time.
Thanks on the wedding congratulation!

Day 3: OK, So I went through all the packages for the easy cleaning process. I also looked through all the RGU's and deleted any and all references to the stuff deleted. Now I have to go file by file and find out what to keep and what not to keep. One thing to notice, PROVXML files also include a lot of info that has to be edited. Think of them as a making of an XML file and a RGU file.

Day 4: I had an idea. I'm going to use the extROM for storage of certain system files that do not require a read directory... That might give me the push I need to reach 80MB free.

Related

Share your OEM Packages for Faria ROM Kitchen

Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)

ROM Kitchen registry problem

I have been currently making another ROM kitchen to use but I have gotten stuck. When trying to use BuildOS create the new dump, I always get an error creating registry with a dialog that says "The system cannot find the file specified."
I dumped the ROM with Tadzio's revised IMGFS tools and used PackageTool to create the OEM and SYS folders.
Where are the default.hv and user.hv files located?
Any suggestions?
ND4SPD said:
I have been currently making another ROM kitchen to use but I have gotten stuck. When trying to use BuildOS create the new dump, I always get an error creating registry with a dialog that says "The system cannot find the file specified."
Click to expand...
Click to collapse
Does the error say anything else? Usually this indicates an error in one of your packages (possibly a syntax error in a .rgu file). Try disabling some packages in the OEM folder (either uncheck them in buildos.exe or move them out of the OEM folder to some holding folder) and see if it will run to completion. If it does, then move them back one at a time to find the offending package. Then go look at the .rgu file.
Also verify the files are saved in Unicode (.rgu, initflashfiles.txt) as that can cause issues too.
OK. I tried to fix this by unchecking all of the OEM packages. I still got the error. It shows the same error. On the status bar it says, "Error, last status: "Creating Registry..."". I then get the dialog mentioned before. When I do the same thing through Anichillus's kitchen, it works perfectly with the same OEM and SYS folders.
Is there something wrong that I'm doing in the dump procedure that could affect this?
Thanks
ND4SPD said:
OK. I tried to fix this by unchecking all of the OEM packages. I still got the error. It shows the same error. On the status bar it says, "Error, last status: "Creating Registry..."". I then get the dialog mentioned before. When I do the same thing through Anichillus's kitchen, it works perfectly with the same OEM and SYS folders.
Click to expand...
Click to collapse
Ahhh... I had a similar issue with the Faria Kitchen rom and trying to move it to other kitchens. There seems to be slight variations in buildos.exe. Never figured out exactly what it was... You can just take the buildos.exe from Core Kitchen and move it to the one you are using now (that gets the errors) and it will work. I think it has to do with where it expects to find certain files, but from what I could tell they all work exactly the same.
Just tried that too. Got the same error. I don't remember, but I think I had already gotten the BuildOS from the Core Kitchen. Sorry, but do you know of any other versions that work? Or if it isn't to much trouble, do you think you could attach the version you are using?
Could you tell me if this process is correct or if there is something in this that is causing the problem?
1. Split the Rom with typho5
2. Split the nb with ImgfsFromNb or prepare_imgfs
3. Dump from bin using ImgfsToDump or viewimgfs
4. Use PKGTool and make packages
5. After adding/removing packages, use BuildOS to recreate ROM
6. use BuildImgfs to recreate the bin file
7. use make_imgfs to recreate OS file
Thanks for your time
ND4SPD said:
Just tried that too. Got the same error. I don't remember, but I think I had already gotten the BuildOS from the Core Kitchen. Sorry, but do you know of any other versions that work? Or if it isn't to much trouble, do you think you could attach the version you are using?
Click to expand...
Click to collapse
I use the Core Kitchen and the scripts in the Extract and Panel folders there to break apart and build roms (its basically all setup and scripted that way).
Try extracting and rebuilding with Core Kitchen and see if that works (I know you said the build works with Core Kitchen). Is there a reason for this other kitchen tools you are trying to use (something newer/better)? Just curious.
While most of the kitchen tools are basically the same, there are some slight variations, and aparently something with this rom or kitchen doesn't quite mesh up...
OK. I will try that. Thank you for the suggestions. If it doesn't work, I'll let you know
Try extracting and rebuilding with Core Kitchen and see if that works (I know you said the build works with Core Kitchen). Is there a reason for this other kitchen tools you are trying to use (something newer/better)? Just curious.
Click to expand...
Click to collapse
I'm not too sure what you mean by this question, but if you are asking why I'm making another kitchen, it is so that cookers can build their own roms from a GUI without having to worry about putting things in certain folders.
Here is a screenshot:
{
"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"
}
The only thing not working right now is the rebuilding of the OS.
Nice and well done! Interested to see this in action...
I will say that while I like most everything about Core Kitchen, one thing I don't care for is the scripts all assume everything is on your SystemFolder drive (C:\) and assume top level folder names. I'm going to look at modifying this so its generic (like most other kitchens) just haven't had the time to do it yet.
So I guess what I'm saying is, if you build this project, don't hardcode the location of the kitchen
BuildOS needs some files in same folder with it in order to work if i remember corectly. Maybe you missed that.
I wonder though...Are you sure you completely understand the big scheme ?
I mean ... you are trying to build a kitchen not knowing all the steps necessary to do that. Maybe you should collaborate with someone. I don't want to have a wave of bricked wizards around here. Again...your choice...and...btw i wanted to do that for some time also so you would save me the work.
The Wizard ROM doesn't use the SPLIT option. If you use typhoon decode.
Don't worry mfrazzz , i will redo my kitchen. Today was my last exam, and as i promised i will get on with it
Sorry it took me some time to reply, I was busy with something else
@anichillus:
i guess it would be a VERY good idea to collaborate on this. I have been trying to build a kitchen based on the way yours and Molski's works. Or, I could give you the source code if you want. It's in VB, but I haven't put a single comment in the whole thing.
So I guess what I'm saying is, if you build this project, don't hardcode the location of the kitchen
Click to expand...
Click to collapse
Oops! I probably should change that then. Right now, it's all hardcoded to a folder "C:\Autosculpt"
Btw I named it Autosculpt from the customization of a car's parts in the game Need For Speed Carbon. Just thought you would like to know.
Also, with the progress bars, don't take any notice of them, they are time based and automatically go to 100% when the certain task is done.
I have attached the current build of my program and kitchen. See what problems you can find. I have been doing this from a computer on which typho5 doesn't work so I have only tested it twice on a different computer.
Also, don't worry about the splash screen tool makers. They don't do anything just yet as I haven't added code for them.
Make sure that the directory of the Kitchen is C:\Autosculpt!
Once again, please tell me if you want the source code. If you want to use it, you will need Microsoft Visual Basic 2005 Express Edition which you can get as a free download from microsoft. If you can turn this into something successful, you don't need to give me credit for the original. I just did because I was bored and I had to anyways learn a few programming languages so for a class I will be taking.
good work,
im interested in sorce code if u dont mind.
Please wait till about 12:30. I have summer school and can't upload it now
Here is the link:
ftp://xdaupload:[email protected]/Upload/testapp.zip
Place the folder testapp projects folder in the Visual Studio 2005 folder in My Documents. Then you can just open up the project file from Microsoft Visual Basic Express Edition.
Be warned: I haven't placed a single comment in the program. If you want I can send one with the comments later today. I can't do it immediately as I have to go and practice tennis with my friend.
Also, as mentioned before, I haven't put the code to activate the splash tools yet. I asked the-equinoxe about them yesterday and will be implementing them later today.
Now have gotten a little further with this. I still haven't made any effort to fix the registry problem.
Changes to kitchen:
Added Splash editing support
Added G4 flashing support (not that this will do any good until I fix the registry problem)
Note: progress bar has not been binded to any running of an application at this time. Instead, you will get a dialog box telling you when a certain process is done.
If anyone has looked at the kitchen, do you think you can figure out what is going wrong with the registry.
Updated source code is posted on ftp server at the same link
Here is the link to the updated kitchen: ftp://xdaupload:[email protected]\Upload\Autosculpt.rar
make "temp" folder in kitchen folder.....if i understood your prob correctly....
also having problems
hi,
i'm trying to cook a rom using buildOS i get this error message:
'error building defaul.hv and user.hv'
anyone got a clue how to fix this??
ND4SPD said:
I have been currently making another ROM kitchen to use but I have gotten stuck... I always get an error creating registry with a dialog that says "The system cannot find the file specified."
Click to expand...
Click to collapse
In my case it was lacking the rgucomp.exe utility in the tools folder.

Rom Files

Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Tambuyeye said:
Hey guys im trying to build my own rom using a tutorial i found on this site. the thing is that im at the section where im suppose to put the missing files where they r to go but i cant seem to get pass that section.
my problem is that the PKG Tool shows me the missing files, but where do i find them using the explorer window opened.
i am frustreated man and really need help.
Click to expand...
Click to collapse
When creating packages with Package tool it creates the following folders:
SYS
OEM
Missing <-- Thats what you are looking for.
I suggest that if this is your 1st attempt and you are building based on a custom rom, use HyperCore Kitchen. Its very easy to use and does the extraction much quicker and easier than doing it by hand. Once you have the hang of it then just move your stuff to another kitchen. Nice part about HyperCore you can dump just about any rom if you set it for that specific device. Just a note: some cookers protect their roms and you end up with almost everything in Missing. You can dump WizFlo from 6.1.1.3 upwards easily
When you have run the PkgTool - Build Packages option, don't mistaken the Missing Manifests for the same thing as Missing Files or Missing Packages. The missing "dsm" manifest files the Pkg Tool refers to are contained in the XIP files (which you will be doing next, i.e., extract XIP). So, you can just ignore the Missing Manifest message and continue on, however be aware that you must use compatible XIP that contains these "missing" dsm manifest files when you go to re-build your rom.
If there are indeed missing packages or missing files, it will tell you exactly what they are and where (what folder) they are supposed to go into. These missing packages/files will be in the dump folder along side the OEM and SYS folders after you run the Build Packages option in the PkgTool app.
This took me a while to realize as it was not explained (or at least I did not see it anywhere) in the various forums/threads on rom building.
If I am wrong on any of this someone please correct me as I too am relatively newbie to this and still learning.
Good Luck!

(6-16-09)TPC & Joshkoss Collaborative 6.1 and 6.5 Kitchens for Noobs-updated builds!

(6-16-09)TPC & Joshkoss Collaborative 6.1 and 6.5 Kitchens for Noobs-updated builds!
Not too long ago, i started trying to learn how to cook roms and i was fortunate enough to have some people on here help me get started...so i thought i would try to do the same for other people who want to learn how to cook. One of the people who helped me the most was Joshkoss, we have spent alot of time testing different things and trying to make our kitchen as good as possible and its turned out pretty good Since i like to cook wm 6.1 and Josh likes to cook 6.5, we thought we would kinda share this thread..Josh doing 6.5 and me doing 6.1. We are including our base kitchens of our latest ROMS, and with our instuctions you guys will be able to customize your ROMS however you want None of the main tools in the kitchen were created by us, we just put them all together with a few batch files...all credits to creators of tools without them we would have no kitchen. We do plan on writing tutorials, but you guys will have to be patient because this is a work in progress we will try to update as much as we can. Here is a list of what will be included in the kitchen.
--choice of either LZX or XPR ROM compression(thanks ivanmj)
--option to compress all .exe's in EXT folder with UPX
--automatically hides all files in dump folder for smoother running ROM
--includes MainSplash.nb
--includes 101 RAM tweak(thanks ervius, anryl)
--includes toolset to create packages from cabs for your rom
--tool to batch compress .exe's with UPX any folders,subfolders you choose
--latest official wm 6.1 and (unofficial) 6.5 builds(thanks anryl)
all updated resources in 4th post
Download kitchens on 2nd(6.5) and 3rd(6.1) posts
{
"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"
}
thanks to these people for tools and helping with kitchen
Bepe, ervius, anryl, dark simpson, tadzio, ivanmj, upx team, abusalza, medkid, DA_G, conflipper,mbarvarian, OndraSter ??? let me know if you helped or i missed someone will update
Josh's 6.5 Kitchen for Kaiser
Hello Everyone,
TPC And I came up with a sweet idea to have a collaborative kitchen thread since him and I have done allot of work on these kitchens. Since we both love doing this and both were noobs at this not too long ago, we figured it would be cool to help out and contribute learning more peeps on becoming chefs.
Step 1: Download kitchen:
21232 6.5 Light build HERE
Step 2: Extract it
You will see the rom structure:
EXT is were all your extra packages and app you want to add will go.
OEM is essential usually device specific items are.
ROM is your xip structure
SYS is your Windows build core items are.
"go ahead and poke around "
More to come soon.
TPC-Joshkoss WM 6.1 21046 complete kitchen with instructions
Part One---COOKING YOUR BASIC ROM
1--Download TPC-Joshkoss 6.1 21046 kitchen HERE
2--extract kitchen to your root drive(ex. C:/kitchen)
3--inside you will see some folders and some .bat files...will look like this
notice the folders highlighted in yellow...those are where all your ROM files are located
SYS= all your main system files, microsolft office, welcome center, etc.
ROM= your xip structure
OEM= some apps inside but mostly device specific drivers ect.
EXT= folder where pretty much all of your applications, utilities, games, manilla, etc. will be stored in ext rom pkgs
4--some advice on editing these folders....leave your SYS and ROM folder alone unless you are an advance user(noobs do not touch). you may add packages to your OEM folder(not this time later) but do not delete any of the files that are in there now. you may also add or delete packages in EXT folder as well, but in both cases files must be in correct format(another lesson)
5--notice the file build_rom.bat in kitchen folder....this is the file you will run to create you rom this is a batch file that tells the other tools in kitchen what to do. if you are using windows vista(maybe even xp) you need to run this file from command line. the easiest way to do this is to go to main kitchen folder in room kitchen(ex. c:/kitchen), hold down the "shift" key and right click on it....you will see the option "open command window here". click on that and a black box will pop up with this text in it... C:/TPC_KITCHEN_6.120146. after this you need to enter this text build_rom.bat this tells windows to open your kitchen(see pic)
6--so whatta ya say we go ahead and cook our first rom so you have completed the above steps, now press enter...kitchen screen will pop up and will say press any key continue, do that and you will see this
for now we will just worry about one of two options....LZX or XPR compression. we will save UPX for a later lesson as all base files in EXT folder are already compressed. if you press option "1" your ROM will be compressed with LZX algorithm, which will give you 10-15% more free storage but takes longer to cook and is optional. if you press option "2" your rom will be compressed with XPR compression, this is the default compression most ROMS are cooked with. choose whichever option you want and press enter.....YOUR ROM IS NOW COOKING
7--let kitchen cook untill all steps are completed then open your kitchen folder and go to the FLASH folder and open it up.....you will see this
CONGRATULATIONS.....YOU HAVE JUST COOKED YOUR FIRST ROM!
hopefully you have flashed a rom before you are trying to cook one so you know what to do from here....click on KaiserCustomRUU.exe and follow instructions to flash your new rom.
Part Two--CUSTOMIZING YOUR BASIC ROM WITH EXT PKGS
note--there are two ways you can add pkgs to your rom, either use some that are already made or you can create your own with tools...this section is for using EXT pkgs that have already been made.
1--go to THIS link and you will see some files i have uploaded for the EXT packages, download both packages and save on your pc/extract where ever is convient for you. we will use iolite ext packages folder for example in this lesson.
2--open iolite_external_packages folder and you will see another folder inside named the same thing, click on that folder and you will see a huge list of files...these are all EXT packages from iolite dump will look like this
3--now go to your kitchen folder and click on EXT folder....you will see one folder inside...BASE, open this folder and it will look like this(see pic)....this is where your new EXT pkgs from iolite dump will be placed
note--i like to set folders side by side on my desktop and compare what packages i have in my current kitchen folder with new packages in iolite folder and decide which ones i want to replace/delete(see pic)
4--now for the fun part after you have decided which packages you want to add to your rom from the iolite folder, right click on one and click on "copy". now go to your kitchen "base" folder and right click and then click "paste"....its that simple! you have now added a new pkg to your ROM
5--THIS IS VERY IMPORTANT...if you try this and your kitchen crashes when trying to cook, then the structures of your files are wrong. ALL FILES IN EXT FOLDER MUST HAVE THIS STRUCTURE.....EXT/BASE/YOUREXTPKGS ....OR YOUR KITCHEN WILL CRASH.
6--now cook your rom again and experiment with different pkgs/configurations till you find the one that fits you the best....then start enjoying your new ROM!
SYS_XIP Ports
SYS XIP ports:
21051_SYS_XIP 6.1 ported by TPC
21275_SYS_XIP
21728_SYS_XIP
RTM_EMulator Dump for 6.5 "unedited"
RTM_21234_SYS_XIP
21806_SYS_XIP
21812_SYS_XIP
21820_SYS_XIP
from TPC:
21815_sys_xip
21820_sys_xip
23001_sys_xip
23003_sys_xip
23004_sys_xip
21921_sys_xip
21925_sys_xip
23007_Public_Kitchen
23008_Public_Kitchen
23009_Public_Kitchen
Click to expand...
Click to collapse
wm 6.1 sys-xip ports
21051_sys_xip
and 6 is mine
Cuz i'm fat and greedy
haha awesome guys. I hope u were done reserving posts
can't wait for the kitchen thread
yeah i think ive been screwing around with roms long enuff that i should probly learn how to cook em...i think i know what makes a good rom, and now with tpc doing it (even with the cheese factored in) i'm kinda inspired...time is my x factor, but since most of my work time is wasted on the computer anyway, i guess i could use it to chef it up...
thedrizzle said:
yeah i think ive been screwing around with roms long enuff that i should probly learn how to cook em...i think i know what makes a good rom, and now with tpc doing it (even with the cheese factored in) i'm kinda inspired...time is my x factor, but since most of my work time is wasted on the computer anyway, i guess i could use it to chef it up...
Click to expand...
Click to collapse
yeah i work from home office so i get to squeeze in a rom or two every now n then you should give it a try driz, just takes some hard work and alot of patience. with this kitchen you will have it alot easier than i did in the respect that all the kitchens that i had to work with were good kitchens, just based on older builds and outdated tools. the kitchen i posted is base to my v4 and v5, just need to add some apps and tweak on it a lil.
I appreciate all you have done. I would like to cook a rom by myself. Now it is simple to follow your action. Thanks very much. I hope to explain more ditail to help all newer to do this. Thanks......
Cool thanks guys.
If I use one of the other great roms here and just remove a couple of programs (i.e. windows live or messenger), what are the chances that I screw up the rom?
I just don't want to flash a bad rom and brick my phone.
tilt4life2 said:
Cool thanks guys.
If I use one of the other great roms here and just remove a couple of programs (i.e. windows live or messenger), what are the chances that I screw up the rom?
I just don't want to flash a bad rom and brick my phone.
Click to expand...
Click to collapse
i dont think you have to worry about bricking your phone, worst that can happen is that it wont boot and you have to put in bootloader mode to reflash with good rom. as far as windows live and windows messenger, they are already removed so you dont have to worry with those i am going to write tutorial in the morning for next step customization and will go in detail about things to add/delete. the roms are pretty naked so gather you up some cabs that you want to put in your rom and tomorrow you can learn how to put them in your new rom
twopumpchump said:
i dont think you have to worry about bricking your phone, worst that can happen is that it wont boot and you have to put in bootloader mode to reflash with good rom. as far as windows live and windows messenger, they are already removed so you dont have to worry with those i am going to write tutorial in the morning for next step customization and will go in detail about things to add/delete. the roms are pretty naked so gather you up some cabs that you want to put in your rom and tomorrow you can learn how to put them in your new rom
Click to expand...
Click to collapse
Well, first thing I have to do is flash your new rom and give that monster a run.
I will keep reading this thread in my free time to learn more, but I won't be able to start cooking until Tuesday once I get this paper for my journal competition mailed out. I hate law school. The work never ends even after finals.
Awesome Guys!!!
With this toolset, even a noob like me, can cook.
I can't help but notice a sudden urge comin' up.
Will definately play around with this and I'm looking forward to your customization part.
Josh and TPC - Thx for your great contribution - makes me remember what I was doin' here
looks like learning easy way to cook ...subscribing to this thread thanks to TPC and Josh
suppose we want to cook registry edits into the rom(like cleartype on landscape, etc), how would we go about doing that?
himalayasplaya said:
suppose we want to cook registry edits into the rom(like cleartype on landscape, etc), how would we go about doing that?
Click to expand...
Click to collapse
I have an entire "Device" in EXT dedicated to registry tweaks, so if I need to add one, for example, I'd just make a folder called ClearType, then app.reg in that, and put the registry in it
actually, I have one of those folders, it's attached
mbarvian said:
I have an entire "Device" in EXT dedicated to registry tweaks, so if I need to add one, for example, I'd just make a folder called ClearType, then app.reg in that, and put the registry in it
actually, I have one of those folders, it's attached
Click to expand...
Click to collapse
thanks mb yeah i plan on explaining how to do this in detail in next lesson...i just now woke up need to clear my head a lil before i get started lol. there is also a program called oemizer that i think would be easy way for noobs to make pkgs for reg entries will put link in my tools folder on server later.
twopumpchump said:
thanks mb yeah i plan on explaining how to do this in detail in next lesson...i just now woke up need to clear my head a lil before i get started lol. there is also a program called oemizer that i think would be easy way for noobs to make pkgs for reg entries will put link in my tools folder on server later.
Click to expand...
Click to collapse
no prob man, looking forward to the next lesson
yes, but then wouldn't they have to convert the package after that?
which might not work with oem2ext and oemizer, I don't know if the two are compatible
mbarvian said:
no prob man, looking forward to the next lesson
yes, but then wouldn't they have to convert the package after that?
which might not work with oem2ext and oemizer, I don't know if the two are compatible
Click to expand...
Click to collapse
when i started out i used oemizer with extpackagebuilder all the time with success great way to customize your rom! can also choose from alot of built in tweaks in oemizer as well. if anybody wants to go ahead and try it, HERE is the link

[TOOL][SCRIPT] Alliance wbp2png Batch Converter

Hello XDA,
Here's a simple script, brought to you by ALLIANCE and myself, that will allow you to easily convert the .wbp files found in many newer apps to more manageable .png files, either individually, or in batches. For other image formats, such as .pkm and .atc, please see my thread here.
***This script is currently for Windows only.***​
The script utilizes a tool called dwebp to handle the decoding. dwebp can be run by itself to convert .wbp files to .png via the command prompt with the following:
Code:
dwebp <inputfile.wbp> -o <outputfile.png>
It has other commands and options, but for our purposes, that's the only one we're interested in. For creating .wbp files from other image formats, you can use its' sister tool, cwebp. For more information or to download the entire WebP package, please visit Google Developers.
On to the script....
SETUP
Download the attached zip file, and extract it to a location of your choice. Inside, you will find four files: dwebp.exe, a copy of these instructions, and two batch files.
Select the two batch files, right-click, and select Create Shortcut.
Next, open the run dialog (Start > Run, or windows key + r), type in "sendto" without the quotes, and press enter.
Either move or copy the two shortcuts that you created into the sendto folder, then close it. Now you're ready to convert....
USAGE
To convert individual .wbp files, simply right-click on one, and select Send To > wbp2png (file). The script will run for a couple of seconds, and once it finishes, you will have a .png in the same folder as your .wbp, and with the same name.
To convert multiple .wbp files at once, select the folder containing them (drawable-xxhdpi, for example), right-click, select Send To > wbp2png (folder), and let it do its' magic. Once it's finished, you will have .png versions of any .wbp files contained in the folder.
During batch conversion, you will likely notice several lines in the cmd output that say BITSTREAM_ERROR. This simply means that it encountered a file that was not a .wbp or .png file (such as .xml files) and is skipping over it. It is perfectly safe, and the error can be ignored.
Originally, I created this script so that it would delete the original .wbp files after it had finished generating the .pngs, but I decided to remove that functionality so that, should something go wrong in the decoding process, the user still has the originals, without having to decompile their apk again. In order to be able to recompile your apk, the .wbp files will have to be removed, once you have the .png equivalents. If anyone would like the script to remove them automatically, let me know and I can tell you how to add that functionality yourself.
Thank you,
~Morningstar
Morningstar said:
Hello XDA,
Here's a simple script, brought to you by ALLIANCE and myself, that will allow you to easily convert the .wbp files found in many newer apps to more manageable .png files, either individually, or in batches. For other image formats, such as .pkm and .atc, please see my thread here.
***This script is currently for Windows only.***​
The script utilizes a tool called dwebp to handle the decoding. dwebp can be run by itself to convert .wbp files to .png via the command prompt with the following:
Code:
dwebp <inputfile.wbp> -o <outputfile.png>
It has other commands and options, but for our purposes, that's the only one we're interested in. For creating .wbp files from other image formats, you can use its' sister tool, cwebp. For more information or to download the entire WebP package, please visit Google Developers.
On to the script....
SETUP
Download the attached zip file, and extract it to a location of your choice. Inside, you will find four files: dwebp.exe, a copy of these instructions, and two batch files.
Select the two batch files, right-click, and select Create Shortcut.
Next, open the run dialog (Start > Run, or windows key + r), type in "sendto" without the quotes, and press enter.
Either move or copy the two shortcuts that you created into the sendto folder, then close it. Now you're ready to convert....
USAGE
To convert individual .wbp files, simply right-click on one, and select Send To > wbp2png (file). The script will run for a couple of seconds, and once it finishes, you will have a .png in the same folder as your .wbp, and with the same name.
To convert multiple .wbp files at once, select the folder containing them (drawable-xxhdpi, for example), right-click, select Send To > wbp2png (folder), and let it do its' magic. Once it's finished, you will have .png versions of any .wbp files contained in the folder.
During batch conversion, you will likely notice several lines in the cmd output that say BITSTREAM_ERROR. This simply means that it encountered a file that was not a .wbp or .png file (such as .xml files) and is skipping over it. It is perfectly safe, and the error can be ignored.
Originally, I created this script so that it would delete the original .wbp files after it had finished generating the .pngs, but I decided to remove that functionality so that, should something go wrong in the decoding process, the user still has the originals, without having to decompile their apk again. In order to be able to recompile your apk, the .wbp files will have to be removed, once you have the .png equivalents. If anyone would like the script to remove them automatically, let me know and I can tell you how to add that functionality yourself.
Thank you,
~Morningstar
Click to expand...
Click to collapse
Will this work with linux or xposed?
sparx said:
Will this work with linux or xposed?
Click to expand...
Click to collapse
Yes. It works with both. I don't even understand how it works with xposed, but it does. Flawlessly.
[emoji23]
Morningstar said:
Hello XDA,
Here's a simple script, brought to you by ALLIANCE and myself, that will allow you to easily convert the .wbp files found in many newer apps to more manageable .png files, either individually, or in batches. For other image formats, such as .pkm and .atc, please see my thread here.
***This script is currently for Windows only.***​
The script utilizes a tool called dwebp to handle the decoding. dwebp can be run by itself to convert .wbp files to .png via the command prompt with the following:
Code:
dwebp <inputfile.wbp> -o <outputfile.png>
It has other commands and options, but for our purposes, that's the only one we're interested in. For creating .wbp files from other image formats, you can use its' sister tool, cwebp. For more information or to download the entire WebP package, please visit Google Developers.
On to the script....
SETUP
Download the attached zip file, and extract it to a location of your choice. Inside, you will find four files: dwebp.exe, a copy of these instructions, and two batch files.
Select the two batch files, right-click, and select Create Shortcut.
Next, open the run dialog (Start > Run, or windows key + r), type in "sendto" without the quotes, and press enter.
Either move or copy the two shortcuts that you created into the sendto folder, then close it. Now you're ready to convert....
USAGE
To convert individual .wbp files, simply right-click on one, and select Send To > wbp2png (file). The script will run for a couple of seconds, and once it finishes, you will have a .png in the same folder as your .wbp, and with the same name.
To convert multiple .wbp files at once, select the folder containing them (drawable-xxhdpi, for example), right-click, select Send To > wbp2png (folder), and let it do its' magic. Once it's finished, you will have .png versions of any .wbp files contained in the folder.
During batch conversion, you will likely notice several lines in the cmd output that say BITSTREAM_ERROR. This simply means that it encountered a file that was not a .wbp or .png file (such as .xml files) and is skipping over it. It is perfectly safe, and the error can be ignored.
Originally, I created this script so that it would delete the original .wbp files after it had finished generating the .pngs, but I decided to remove that functionality so that, should something go wrong in the decoding process, the user still has the originals, without having to decompile their apk again. In order to be able to recompile your apk, the .wbp files will have to be removed, once you have the .png equivalents. If anyone would like the script to remove them automatically, let me know and I can tell you how to add that functionality yourself.
Thank you,
~Morningstar
Click to expand...
Click to collapse
I don't understand. I tried to open this on my iPhone and nothing happened. Plz halp.
Morningstar said:
Yes. It works with both. I don't even understand how it works with xposed, but it does. Flawlessly.
[emoji23]
Click to expand...
Click to collapse
Ohhh bro! Downloading now!! You rock dude...alliance rules!!!!
Morningstar said:
Hello XDA,
Here's a simple script, brought to you by ALLIANCE and myself, that will allow you to easily convert the .wbp files found in many newer apps to more manageable .png files, either individually, or in batches. For other image formats, such as .pkm and .atc, please see my thread here.
***This script is currently for Windows only.***​
The script utilizes a tool called dwebp to handle the decoding. dwebp can be run by itself to convert .wbp files to .png via the command prompt with the following:
Code:
dwebp -o
It has other commands and options, but for our purposes, that's the only one we're interested in. For creating .wbp files from other image formats, you can use its' sister tool, cwebp. For more information or to download the entire WebP package, please visit Google Developers.
On to the script....
SETUP
Download the attached zip file, and extract it to a location of your choice. Inside, you will find four files: dwebp.exe, a copy of these instructions, and two batch files.
Select the two batch files, right-click, and select Create Shortcut.
Next, open the run dialog (Start > Run, or windows key + r), type in "sendto" without the quotes, and press enter.
Either move or copy the two shortcuts that you created into the sendto folder, then close it. Now you're ready to convert....
USAGE
To convert individual .wbp files, simply right-click on one, and select Send To > wbp2png (file). The script will run for a couple of seconds, and once it finishes, you will have a .png in the same folder as your .wbp, and with the same name.
To convert multiple .wbp files at once, select the folder containing them (drawable-xxhdpi, for example), right-click, select Send To > wbp2png (folder), and let it do its' magic. Once it's finished, you will have .png versions of any .wbp files contained in the folder.
During batch conversion, you will likely notice several lines in the cmd output that say BITSTREAM_ERROR. This simply means that it encountered a file that was not a .wbp or .png file (such as .xml files) and is skipping over it. It is perfectly safe, and the error can be ignored.
Originally, I created this script so that it would delete the original .wbp files after it had finished generating the .pngs, but I decided to remove that functionality so that, should something go wrong in the decoding process, the user still has the originals, without having to decompile their apk again. In order to be able to recompile your apk, the .wbp files will have to be removed, once you have the .png equivalents. If anyone would like the script to remove them automatically, let me know and I can tell you how to add that functionality yourself.
Thank you,
~Morningstar
Click to expand...
Click to collapse
Ooo haha. Thanks for the PM bro.
So it only works on windows...
Is there an ETA for when the update will come for the iPhone bro?
Thanks bro.
Morningstar said:
Hello XDA,
Here's a simple script, brought to you by ALLIANCE and myself, that will allow you to easily convert the .wbp files found in many newer apps to more manageable .png files, either individually, or in batches. For other image formats, such as .pkm and .atc, please see my thread here.
***This script is currently for Windows only.***​
The script utilizes a tool called dwebp to handle the decoding. dwebp can be run by itself to convert .wbp files to .png via the command prompt with the following:
Code:
dwebp <inputfile.wbp> -o <outputfile.png>
It has other commands and options, but for our purposes, that's the only one we're interested in. For creating .wbp files from other image formats, you can use its' sister tool, cwebp. For more information or to download the entire WebP package, please visit Google Developers.
On to the script....
SETUP
Download the attached zip file, and extract it to a location of your choice. Inside, you will find four files: dwebp.exe, a copy of these instructions, and two batch files.
Select the two batch files, right-click, and select Create Shortcut.
Next, open the run dialog (Start > Run, or windows key + r), type in "sendto" without the quotes, and press enter.
Either move or copy the two shortcuts that you created into the sendto folder, then close it. Now you're ready to convert....
USAGE
To convert individual .wbp files, simply right-click on one, and select Send To > wbp2png (file). The script will run for a couple of seconds, and once it finishes, you will have a .png in the same folder as your .wbp, and with the same name.
To convert multiple .wbp files at once, select the folder containing them (drawable-xxhdpi, for example), right-click, select Send To > wbp2png (folder), and let it do its' magic. Once it's finished, you will have .png versions of any .wbp files contained in the folder.
During batch conversion, you will likely notice several lines in the cmd output that say BITSTREAM_ERROR. This simply means that it encountered a file that was not a .wbp or .png file (such as .xml files) and is skipping over it. It is perfectly safe, and the error can be ignored.
Originally, I created this script so that it would delete the original .wbp files after it had finished generating the .pngs, but I decided to remove that functionality so that, should something go wrong in the decoding process, the user still has the originals, without having to decompile their apk again. In order to be able to recompile your apk, the .wbp files will have to be removed, once you have the .png equivalents. If anyone would like the script to remove them automatically, let me know and I can tell you how to add that functionality yourself.
Thank you,
~Morningstar
Click to expand...
Click to collapse
False advertising. It are not like simpilish as you said. I want my dorrars back.
sparx said:
Will this work with linux or xposed?
Click to expand...
Click to collapse
You Linux is xposed?
Morningstar said:
Yes. It works with both. I don't even understand how it works with xposed, but it does. Flawlessly.
[emoji23]
Click to expand...
Click to collapse
Truth or another round of bs? You act like this is your world and your rules or something.
RErick said:
I don't understand. I tried to open this on my iPhone and nothing happened. Plz halp.
Click to expand...
Click to collapse
Just double tap home button and change to McDonald's icons. All will be g00d.
sparx said:
Ohhh bro! Downloading now!! You rock dude...alliance rules!!!!
Click to expand...
Click to collapse
Won't boot on Samsung Note 3. Be careful. Ps glad to see you got your Linux tucked back in.
RErick said:
Ooo haha. Thanks for the PM bro.
So it only works on windows...
Is there an ETA for when the update will come for the iPhone bro?
Thanks bro.
Click to expand...
Click to collapse
Dagnammit. He didn't pm me [emoji35]
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.
sparx said:
Will this work with linux or xposed?
Click to expand...
Click to collapse
RErick said:
I don't understand. I tried to open this on my iPhone and nothing happened. Plz halp.
Click to expand...
Click to collapse
RErick said:
Ooo haha. Thanks for the PM bro.
So it only works on windows...
Is there an ETA for when the update will come for the iPhone bro?
Thanks bro.
Click to expand...
Click to collapse
Bubbajoe40356 said:
False advertising. It are not like simpilish as you said. I want my dorrars back.
You Linux is xposed?
Truth or another round of bs? You act like this is your world and your rules or something.
Just double tap home button and change to McDonald's icons. All will be g00d.
Won't boot on Samsung Note 3. Be careful. Ps glad to see you got your Linux tucked back in.
Dagnammit. He didn't pm me [emoji35]
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.
Click to expand...
Click to collapse
Why are all these morons quoting the op....
{
"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"
}
Good work morningstar bro

			
				
txr33 said:
Why are all these morons quoting the op....
Good work morningstar bro
Click to expand...
Click to collapse
Pffft
Cowboy from Hell on a twisted trail.
Koffed From my Big Ass Outlaw Phone.

			
				
hey @Morningstar...added to my Image Converter. if you don't mind i'll just drop it here too.
now it BATCH resizes xxhdpi and converts .atc and .wbp images to png images
IMAGE RESIZERv2

			
				
thank you so much for this incredible tool

			
				
hello friends as you can convert jpg to wbp
thanks

			
			
			
			
			
			
			
			
			
			

			
		

	
	
	



	
	







			

		



		

			
Categories

			
		


		

			
Resources