New ROM!!! - TechLust ver1 BETA <SJK> - Help me cook better! - Wing, P4350 ROM development

Hey Wing Nuts! Sorry... I'll never make that joke again...
I'm new to cooking, so I need help. This is my first ROM. I have done minimal testing and have made no changes as of yet. I'm hoping a couple of you can help me figure out what to add, change, or remove from this ROM and work out any of the other bugs so I can get better at making them.
The goal of this build was to make something aesthetically pleasing, not too stripped, and still lightweight enough to make the most of the limited space on the P4350.
This build is for the Wing only (Herald keyboard is not supported) and was designed for use with an RUU. I have no idea if it will actually work via SD re-flash, but if you decide to try, let me know.
Any and all help is greatly appreciated. Thanks in advance.
Message me to get a DL link.
On a side note, does anybody know how to add CABs into SJK so I can cook them into ROMs?

Maybe I can post the link like this...
Code:
Go to mediafire and use the following extensions, but replace the commas with slashes:
,file,widwm4iji4y,T L ver 1 - BETA.nbh

If you want, follow my guide in my sig to learn how to utilize .cab files in your building experience.
I'll also give the ROM a run and test it out for you.
Please also do me a favor and let me download your kitchen .erv file so I can help you better..
Navigate to C:\kitchens\SuperJustKitchen\Working_Folder\TOOLS\RomSaved and you'll see the saves that you saved.. If you didn't save, try to mimic your ROM again in the kitchen and save for me and then upload it here in a .zip file.

I think I understand. I'm cooking a new version right now, so I'll get those files to you as soon as it's done. I'm using the most recent version of SJK, just fyi (the one based in osKitchen1.0). I know where the .fe file is, but I don't have a Working_Folder in my SJK files...
I tried using your guide, but the pictures you have posted don't match what I see, so it confuses me...

My kitchen files are based off of Bebe's kitchens. I have links on my guide on the first post of that thread.

What build are you using?

Version 7. And in my guide I have all the Sys & Xip files that are also up to date too.

lol @ "wingnut." Made me chuckle.

So, update...
Recent computer issues have lost me some cooking time...
Also, when trying to cook the new ROM, SJK seems to have lost a file that is integral to the creation of a new rom, so I have to go back and find it in the original .7z files.
I also installed Ivan's JustStable5 Micro onto the test wing, and now it won't accept a reflash either through SD or RUU. So I have to work on that issue as well. I'll let you know when we're back up and running.
Otherwise, any existing feedback on the ROM will be helpful before the new version is finished. Thanks everyone!

New Release
Ok, so all off the issues I was having have been solved. I've switched to bebe's kitchen (thanks Trib!) with Ivan's files and have a new version uploaded. Link below.
Changes:
Some icons changed to fit theme. More to come!
Custom splash animation added.
(Trib, how do I change the ugly orange Windows image, as well as get rid of the greenscreen startup?)​Rid ROM of several useless files and added a few new ones.
ROM size dropped 20MB (From 77MB to 57MB)​
After Flash:
Storage Memory:
Total: 45.92
In Use: 7.64
Free: 38.28​Program Memory:
Total: 49.83
In Use: 40.42
Free: 9.41​
Code:
http rghost net,1487003

Tribulattifather said:
My kitchen files are based off of Bebe's kitchens. I have links on my guide on the first post of that thread.
Click to expand...
Click to collapse
Thanks Trib. I actually like Bebe's version better...

You're welcome. I feel bebes is easier to work with..

I'll get the save file uploaded soon. There's an issue that I noticed with the "incoming caller" icon not showing. I modified it so that the sihlouette(sp?) is outside the original square size, but not outside the original image size? Is that a picture demension issue?

Archive your complete working_folder for me and upload. I'd like to see all files so I can help..

Unfortunately, the work computer isn't working again. I've never gotten so many BSODs in my life without any real explaination as to the problem. It seems to do it whenever it feels like it.
Anyways, I digress, I'll get you the working folder as a 7z asap. Post any thoughts you have on the ROM in the meantime.

Hey, I can't get the file to upload to rghost. I zipped it with "ultra" compression. Should I have done something different?

Use mediafire or 4shared or megaupload then.. I have an account with all of them.

Is it normal that the WorkingFolder.7z file is over 300MB?

Yeah, that's nothing.. My kitchen is over 3 gigs - thats 3072 MB's , lol.

So, I'm trying to work with rghost, filefactory, and megaupload all at the same time, but none seem to be actually accomplishing the upload. wtf.

Related

Announcement: Wizard Rom-Packer Kitchen V2.0

Welcome to the Wizard Rom-Packer Kitchen V2.0, with "Squeezer" technology!
Please read all the way through before starting, even if you've used a previous version.
USE AT YOUR OWN RISK!
This kitchen is easy to use, but is really meant for those with some previous work with other kitchens,like faria's or 004's or Molski's. (If I've left someone out, I'm sorry about that.) This kitchen is based on Bepe's Hermes kitchen, which has incorporated tadzio's reworking of maimach's imgfs tools. This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, a few megabytes at least.
In addition, I have added a new Squeezer module, based on open-source UPX technology, which actually compresses Office .exe files, freeing even more room in the rom (a few more meg), and actually decreasing load times!
Although the Wizard Rom is not quite as malleable as the Hermes in that the extra space is not translated into additional user storage memory, at least the additional freeware, shareware, themes, etc. which can be burned to the rom do not have to reduce the user storage space.
I hope over time to enhance this further, as new innovations become available, (maybe someone will figure out a way to repartition the Wizard Rom?). Also, perhaps adding some way of automatically generating the xip directory. If you have suggestions feel free to let me know about them.
Error checking is not extensive, so be sure to keep your old rom available to fall back to! Check the size of the generated .nbf file. If its around 59 mb you are close to the limit. Be ready to re-flash in bootloader mode (after paring some packages or files) if the program exits before the 100% mark.
How to use:
Download your favorite base rom, at this point one from another kitchen, which has already been broken down to SYS, OEM, and ROM directories. Delete the SYS, OEM, and ROM directories from my kitchen, and copy the ones from the other kitchen in there instead.
Make a copy of the SYS\OFFICE directory in case of later problems (not likely).
An additional caution/strong recommendation is to delete the /autoupdate package from your roms. This currently does nothing anyway, so you won't miss it, and in any case would likely only create havoc with a custom rom. But additionally the repacking method used in this kitchen removes the extra space in the rom which was to be used for that anyway, and so autoupdate will definitely be useless in a rom built with this method.
Run the SqueezeOffice.bat program. (This compresses your main Office .exe's)
Make sure there is an 80040000-os.nb file in the ROM directory. (It may be called something else and have to be renamed. It'll be around 50mb in size.)
Now click on Start.bat, and away you go...
(Optional) If you want to later go back to using another kitchen, run the PrepareNewNB.bat file. After it completes, there will be a new, compacted 80040000-OS.nb file created in the ROM directory which you can move back to your original kitchen. (Also copy the Office directory back) You will loose some packing efficiency by building in another kitchen, but you will still gain lots of space from having visited here!
Depending on the kitchen you were using, either you will see selectable packages or not during the running of BuildOS. Use whatever method you were using previously to add new packages or to remove the ones you don't want. In general, everything should work about the same way it did before, except you will be able to fit more packages in than previously! (Those who are importing faria's kitchen will have to rename his BuildOS.exe to BOS.exe and bring it into this kitchen. Also, rename his Flash file in the ROM directory to 80040000-OS.nb.)
You will be given the opportunity to go all the way to flashing the rom, similar to the way faria's kitchen is set up. Hold down the Control and "C" keys during one of the pauses provided if you do not want to go to the next step for some reason. (You have a G4, unlocked G3, want postpone flashing for later, etc.) Then press the "Y" key to abort when prompted.
If you'd like, check out the ZSqueezer directory, and the readme there. There you can compress your other programs for even more space (and speed!).
Thanks to all those who have helped me in the past, and especially those who created the tools and roms we all use and enjoy.
Version History:
Initial Unlabeled: Worked fine
V1.1: Added "pre-packing", had a bug in Start.bat
V1.2: Worked fine
V1.3: Deletion of .rgu files from the dump.
V2.0: Removed .rgu deletion (instability), and introduced "squeezer" compression.
Download Link: V2.0
http://rapidshare.com/files/33616241/Wizard_ROM-Packer_Kitchen_V2.0.rar
Standalone Squeezer Module
For those interested in having the "squeezer" technology for their own programs, but aren't comfortable cooking their own roms, I have created a standalone module for that. (Already included in the latest Rom-Packer Kitchen V2.0). I've also started a separate thread for that as well in the Upgrading section. Of course, feel free to leave comments and suggestions in either thread.
Here's the link: http://forum.xda-developers.com/showthread.php?p=1283338#post1283338
Have fun!
More space for later use.
thanks. i'll give it a go later tonight
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
ADB100 said:
I just tried these tools and didn't have much sucess....
I used the latest mUn base ROM, added some OEM stuff that I have been using without issues when creating ROM's with mUn's previous ROM. All this went OK. It got to the point of installing the ROM on the device but the ROMUpdateUtility just exited at 98% and left the Wizard in limbo. I have had put it in bootloader and re-intall a previous ROM
There was no message, it just got to 98% on the PC and the Wizard and then the ROMUpdateUtility just exited. I tried manually using the nb2nbf application and copying the resulting nk.nbf to another RUU folder and the same thing happened.
Any idea's?
Andy
Click to expand...
Click to collapse
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
edhaas said:
Can't really say. I've also flashed mUn's latest, and it seemed to go ok. Did you create your own xip directory? If not, use the version in 004's kitchen as a base.
Click to expand...
Click to collapse
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
ADB100 said:
I had the XIP directory from the original ROM kitchen (in dOUbleOfour_Wiz_Dev_5.2.1413WWE.rar). I think I might try without any OEM stuff and build it up and see where it fails. In your original post you mentioned the error checking is not extensive, does it log any errors anywhere? (apart ffrom the log.txt file that looks OK).
Andy
Click to expand...
Click to collapse
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
anichillus said:
You put too many files, that's why it existed. I presume that because it exited at 98% , meaning that almoust fit, but it didn't . Try leaving out a package ...something about 1MB or so..mabe less
Click to expand...
Click to collapse
Yep, I think that's what the issue is
When I tried cooking with this as the Base ROM previously I ran into size limitations so I was hoping that these new kitchen tools would solve this -
This allows the rom to be packed more efficiently, and thus more packages and files to be burned into the rom. The savings is not trivial, several megabytes at least.
Click to expand...
Click to collapse
Obviously not enough
I'll play around a bit more and see where I get....
Andy
I'm very sorry, but I left out a very important preparation step in my original posting. Please redownload the package to get the corrected version. (V1.1) I think you will find the results to be much more satisfying! Keep the bug reports coming..
the new start batch file doesn't have the correct paths in it. its trying to work in the root folder not temp.
the original one works good though. too late to flash tonight, but i'll give it a go tomorrow and let you know how it works
I tried to correct the start batch file to use temp but now get errors about not finding initflashfiles.dat in the temp\dump area. I don't have time to debug this right now.
I also noticed that the nb2nbf.exe is a Typhoon Smartphone version (so not sure that is correct for the Wizard).
I will say that the pre processor that does the packing is cool. The Faria Vanilla 80040000.nb (in Faria's kitchen its actually called FLASH.nb0, so I just renamed it) was 58.3MB in size. After running the PrepareNewNB.bat it was then 57.1MB, so a full meg smaller. I'll see about moving this over to the Faria kitchen and using it to rebuild my rom later and see how that changes things when its actually flashed to the phone.
i'll post the working one in a little bit.
edit... here's the one that works for me
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Thanks, I was bleary eyed last night with trying to figure out what was going on that it wasn't working for you guys, and I ended up "fixing" some things that weren't broken I guess.
Just be sure to delete the old dump file in the temp directory after you run the preparenewnb.bat file.
Has the compression been working for you?
I appreciate your help. I'm juggling lots of things with "real life" and am sorry for the slip-ups.
I am updating the first postings.
notyourdaddy said:
i'll post the working one in a little bit.
edit... here's the one that works for me
Click to expand...
Click to collapse
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
mfrazzz said:
Maybe its an issue with the Faria RK base rom and compatibility with this kitchen, but even with this updated file (thanks for that) I still get the following error when running the build os step:
Code:
Could not find file "temp\dump\initflashfiles.dat".
The other question is, is it ok to use the Typhoon Smartphone nb2nbf.exe that comes with this?
Click to expand...
Click to collapse
Yeah, I was just running through the faria kitchen and had the same issue. The workaround is to copy the initflashes.dat file in the OS folder and then paste it into the dump directory after buildos has deleted the previous dump and before it is processing the sys\os directory. (Watch the process messages at the bottom of the buildos screen.) This worked for me.
Yes the typhoon version works fine. I think they are mostly all relabeled versions of the same original tools. (Except the imgf tools which are recently updated by tadzio.)
Hope this helps.
weird. intiflashfiles.dat copied over for me using 004's kitchen
I just finished doing a build with faria's kitchen as a base, and was somewhat disappointed that I was unable to flash the entire kitchen at once. I had to leave out enterprise and voip (which is fine for me, but some may want them). I'd be interested in hearing how much extra space people are finding. I felt like I was able to cram a lot more into double_ofour's mUn release, but perhaps that's because it was more stripped down to start? Maybe "the kitchen sink" was a bit optimistic.
Re Faria kitchen
mfrazzz, The easy fix for the faria kitchen is to use faria's buildos.exe instead of the generic one I included. That one runs fine with his kitchen. Just rename it to bos.exe. (or edit the start.bat appropriately.) I don't think this will affect the packing of the files.
Update
OK, Things seem stable now. I've updated the first posting with additional information gleaned from everyone's input, and updated the version. The old start.bat that notyourdaddy posted should not be necessary.
FYI, I got feedback from one user that they got about 2.5 meg additional space from these tools vs the old tools. Not as earth shattering as I'd hoped, but helpful. Roms with more small files, as opposed to those with larger files will likely benefit more, as the savings are in the "padding" between them.
Feel free to incorporate this into your own kitchens.
Regards,

A suggestion for the benefit of the ROM chefs / users

Hi all!
Downloading custom ROMs is VERY cool, but a bit of a pain sometimes because the downloads are huge. I have a suggestion about how this could be resolved.
To explain my idea, let's look at how you would flash a ROM using the new method being suggested. You'd need the following things...
- USPL (as usual)
- Custom RUU (as usual)
- 'Control' ROM NBH
Here's the first difference. The control ROM in my proposal is the widely circulated HTC ROM NBH, which can be found here. You'd keep the NBH from this ROM (RUU_Signed.nbh) named as HTC.nbh, and it would be used by all subsequent updates.
So let's imagine that I have a device (USPL'd of course) that I want to flash to the T-Mobile ROM. I'd make sure I had a directory with the Custom RUU and Control ROM NBH in, then i'd download the file from the ROM creator. In this file would be a batch file, a ROM patch and the patcher. The batch file would patch HTC.nbh to T-Mobile spec, then run Custom RUU. The beauty of it? The download would be very small!
Would it work? YES! And to prove a point, please check out this post - where you'll find Orange, T-Mobile and Tilt ROMs in tiny downloads based off the control NBH. ROM chefs - let's start using this system, which i'm calling 'Kaiser TLR ROMs' for obvious reasons.
ROM chefs, to create the patches you just need to use bsdiff, which can be found here. Use the syntax 'bsdiff HTC.nbh YourROM.nbh YourRom.patch'. You can see a sample batch file in my link above.
So... what do u think?
TLR
I don't get it once your HTC is HardSPL'ed then there is no CID lock and you can flash any rom to your device. Most rar files containing the RUU_signed.nbh are only 40-50MB thats pretty small and can be deleted when your finished flashing. To me this seems like a lot of extra work for the cook(sometimes me) and more support issues I find it easy just to upload the ROM i made to rapidshare or some other file hosting site and people can download as they like.
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
theloanranger said:
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
Click to expand...
Click to collapse
Sounds interesting about the legal hosting capability for diff ROM files instead entire ROM. The ROM archive goes down in the past for the M$ pressing . If we can archive only diif ROMs, this can be one solution to take back the ROM archive into the FTP at XDA.
One offtopic question, where did you get the Orange Shipped ROM for Kaiser?
Cheers.
I didn't, it's a dump and repack, as is the T-Mo one.
TLR

Just an idea

I love this forum. I have learn't so much so far, but still have a lot to learn. Epecially programming for WM. Anyway, on to the reason for posting this thread.
Since learning that I could flash from my microSD card thanks to the tutorial by renaming the *.nbh to KAISIMG.nbh and placing it in the root folder. I have been making custom 1st splash screens to flash remotely as well as making a directory on my microSd ("Flashing from MicroSD") and creating directories for original roms such as (\WM6 Originals\Alex\KAISIMG.nbh) or (\WM6.1\SleuthV3\KAISIMG.nbh), (I also have KAISIMG for just Radios under a different folder) so when I want to try a new rom, flash a different radio or splash, I can at anytime.
Here's the thing I love using the splash tools (maker and converter) and Rom Builder. But obviously you need a PC. Would anyone by able to recreate a mobile version of these tools so we could do most things (customisation wise) whilst we are mobile.
I.E. I want to make and flash a new splash whilst mobile from a *.jpg. I could use this program to convert to .bmp format needed, then convert to *.nb thsn to *.nbh. I could then use a file manager to rename to KAISIMG.nbh then place in microSD root folder and flash.
What you think? Would this be too hard to do? Anyone want more mobile control of your mobile customisation?
Other tools that could be ported would also help. I make the welcome.96.png with my mobile graphics problems.
Well for the moment I'll stick to making several themed splash into the KAISIMG.nbh to flash remotely (making sure you have enough battery mind/dont flash on 10% or something/I recommend over 10% for mobile flashing your splashes and over 50% for you WM Roms)
Got a collection of around 19 Slide out Keyboard sounds inc Knightrider, Thundercats, Xbox 360 boot sound and others. When I have a couple more made I'll post my Sliding keyboard Sounds.cab if anybody wants it over the next Couple of days. (Some sounds gathered from other users share i.e. Mario etc)
Thanks anyway. Feel free to post your views and look forward to seeing if anyone is up to this challenge..
for ever an xda padawan (as no-one ever knows everything)
diigibio
You pose interesting questions, if you don't get much here, I'd try dropping those ideas into the Development and Hacking forum and see what they think. That's usually where the new programs come from.
And yes, I would at least like to see some funky sounds added to the list of things I put on my Kaiser...
( OMG...Jarek91 didn't have anything snarky to say )
Sound .cab v1 (Keyboard Slideout)
Tried to upload my .cab in both .cab and .zip formats and are well below the file size limits but forum keeps saying failed *.cab or *.zip
Any idea's??
diigiobio
I'd say try a 4shared account or talk to alltheway or HDStreetGlide about tossing it on their 4shared accounts. That seems to be the current way of getting the larger files out there unless you want to use RapidShare or MegaUpload.
diigibio said:
Tried to upload my .cab in both .cab and .zip formats and are well below the file size limits but forum keeps saying failed *.cab or *.zip
Any idea's??
diigiobio
Click to expand...
Click to collapse
You can host your file at either rapidshare or Megaupload or others out there.
Sound .cab v1 (Keyboard Slideout)
Thanks guy's. Here is the first version:
http://rapidshare.com/files/95651751/diigibio_19_V1.cab
Enjoy..
Got Loads more to come!!
diigibio
jarek91 said:
( OMG...Jarek91 didn't have anything snarky to say )
Click to expand...
Click to collapse
I was thinking the same thing.
But then I realized that you always leave a calling card with your signature on it.
jarek91 said:
I'd say try a 4shared account or talk to alltheway or HDStreetGlide about tossing it on their 4shared accounts. That seems to be the current way of getting the larger files out there unless you want to use RapidShare or MegaUpload.
Click to expand...
Click to collapse
I feel left out....
P1Tater said:
I feel left out....
Click to expand...
Click to collapse
(and you wonder why I had nothing snarky to say? ) Just kidding...I certainly left you out and I have no idea why other than the voices in my head told me to.
P1Tater said:
I feel left out....
Click to expand...
Click to collapse
Here is something interesting so you do not feel left out.
http://subfighter.com/fighters.php?op=ListEvent&eventid=265
-McMex
diigibio said:
Thanks guy's. Here is the first version:
http://rapidshare.com/files/95651751/diigibio_19_V1.cab
Enjoy..
Got Loads more to come!!
diigibio
Click to expand...
Click to collapse
Error
The file could not be found. Please check the download link.
mathew18 said:
Error
The file could not be found. Please check the download link.
Click to expand...
Click to collapse
I got to say you are an idiot.... I could not stop myself from posting a response to your stupid request. Over a year DEAD post!? what is wrong with you people?
Mods... Please Delete this post entirely.... has no value and all links are dead and there is no need for it to consume realestate space on this site.
Thank you....

µkitchen to add custom files into protected rom

Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
What is the difference in extracting ngh file, adding cab file to dump folder, updataing config.txt and recooking compared to installing the cab file using UC?
Can we add visual kitchen packages to this dump folder? If we can add do we need to just copy all the files in all the folders of the package to dump folder?
eg: in the package there are some files in 0409 and some in files folder , _skip, app.reg, all these goes to dump folder?
Thanks
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
arnoldl said:
@DarkRenegade
No problem , happy that i helped...
@kk0813
If i would buy a phone of the street , i would do the folowing.
- check if there are funny things on it
- format the card
- hardreset the phone
and gone is your remote tracker protection..
If i cook rt in, with my personal settings for it.
after a hard-reset it's installed again , so i can still gps find my stolen phone after a complete format.
only next step i want to take is to re-hard spl , to prevent reflashing if http://forum.xda-developers.com/showthread.php?t=503112posible.
but these days with new 6.5 images coming out so quick i flash so often i will wait with that one
but all other things i install by uc or later shashimi
Don't know if you can add kitchen files.
never tried it.....
btw attached a new version.
remade it to work with the new envirus kitchen the newer 6.5 roms are using..
Click to expand...
Click to collapse
Thats a nice idea. Thanks for the updated version.
DarkRenegade said:
hi arnoldl,
i want to thank you and everyone have helped you to create and publish this. i was searching something like this since many time ago, finally i found your thread and i was able to add RT to the rom i use!
i think this will be useful to many other people
i have changed something and it works perfectly with my blackstone!
thank you thank you.
bye
Click to expand...
Click to collapse
Thanks again
works very well
arnoldl said:
Hello all ,
I ran into the problem of liking a rom that was protected..
no problem , only thing i want to add was remote tracker.
the rest i do with uc.
So with the help of da_g i striped a kitchen to unpack and repack protected roms.
to add a package , just unpack..put your cab in the dump dir and add it to config????.txt
and repack.
that way i get the use the protected rom with my own package build in.
thought i would post it.
grtx , arnold
Click to expand...
Click to collapse
You have a Trojan horse in first post!!!
All this to add a couple of cabs to a ROM ? Isn't it a whole of a lot easier to just... you know... install them after ? Or maybe even UC them to make it even lazier ?
Does this work with other roms from other devices? Or just Raphael roms?
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
jagan2 said:
I tried this but it extracts os.nb and os.nb.payload and also os.nb.extra but when it starts to create dump it fails
this is the log
ImgfsToDump 2.1rc2
Cannot map file imgfs.bin
what to do help
Click to expand...
Click to collapse
Use the latest version of extractor, place the .nbh file in BaseROM, rename it to RUU_signed.nbh and run the extractor.
That worked for me.
A little late reading this, but I downloaded it to rip a rom from a little known site & guess what... Theres a trojan in that 1st post, virus software just riped it out of 2 kitchens recently downloaded as well as that 1st post file.
file namned Win32/Delfsnif.dx
I used your extractor but when i use old (1,2mb) i have problem with rom (sense 2.5 crash , windows menu crash), when i use new extractor (1,9mb) i don;t have a bootable rom (.nbh is very small 15mb-100mb) Is there any solution?
Sorry for my english I hope you can understand me.
I think there are more usefull tools that could help you.
Let's have a look here : http://forum.xda-developers.com/showthread.php?t=411915
And I believe that this tool is used by most roms makers.
Sorry but this tool is traying to rebuild protected rom into kitchen (with folders - ext, rom, sys etc.) but this is impossible.
Worked Great ! !
It worked great for me!
Moving to general section
You should just move this to the cooking forum. People are always asking if you can modify cooked roms. Then others are always answering that you can't dump and modify a protected rom, which clearly isn't true. So this would work ok in the Cooking forum (can't even remember the name of the forum, even though I'm a mod there, lol).
If this works, than this is pretty kick ass! I was recently trying to simplify the process as you did but your work looks flawless to me! I'll post as soon as I can confirm it works putting the rom back on an HTC rose (htc s743).
After the rom is dumped, what says what files go in what directories? In the dump directory ALL files are in the dump directory and not in the folder structure they would be after the ROM is flashed to the phone. Where would I find what determines the folder structure?

[WM Kitchen] Wizard Kitchen

This is a kitchen based on Cracing's CRBuilder2 that I have been using for some time now.
Many thanks to him, S.V.I and the many others that have made this kitchen possible.
This is not a visual kitchen, I have not managed to do that. Instead it is a drag and drop kitchen. You create you ROM batch and then drop it into the OVEN to cook.
Please avoid spaces in file name, it will help avoid problems that may arise.
The ROM batch folder arrangement is that of platformrebuilder.
Code:
_ROM_Batch
EXT
Wizard
Extended Packages
OEM
OEM Packages
ROM
XIP
MSXIPKernel
MSXIPKernelLTK
OEMXIPKERNEL
SYS
SYS Packages
I put the _ in front of my ROM_Batch folders to find them easier.
I have as many error checks as I can think of, but they may not catch everything. Since I drag and drop pieces in and out of my ROM batch, I sometimes drop them in the wrong place. Most of these errors should get caught. This saves having to go through the cooking process to find you have a module in another module's folder.
I also have a Configurator option in my kitchen. This will merge all config.txt files in you ROM batch into one file. This is useful if you are using AutoRun, but have some packages from a RunCC version ROM. You will want to remove any CFG: lines to avoid running a config.txt twice. Also, this is how I do something similar to add2config.txt I have seen in other kitchens. For example, if you create an EXT package that has a config.txt file with some commands you want to add to the main config.txt like EXEC:\windows\myprogram.exe these lines will get added to the new Config.txt. Configurator also adds and CAB files you do not already have listed in the Config.txt files.
Here it is Wizard_Kitchen.7z
It includes Cracing's CR96 Touch HD ROM batch he recently posted.
If you drag and drop the Extended_ROM folder into the OVEN you can build an Extended ROM by itself.
For future use
For future use
For future use
For future use
Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.
I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.
n2rjt said:
Thanks! I'll have to switch over to this. I grabbed the RC6 kitchen, and I've started cooking. So far, I've just updated the Google Maps app, as a sanity test. It worked as expected so I'm ready to try something more wild. I'll DL this kitchen tonight, compare it with CRACING's kitchen for the same version, then see if I can figure out how to plug the RC6 parts into it. I know that you've done that already, but I want to learn.
I think your ExtROM magic is going to be helpful in increasing available internal storage, but I don't see it helping the main deficiency of a 6.5 ROM on the Wizard, which is available RAM.
Click to expand...
Click to collapse
Didyou mean CR96 Touch HD™ RC5 Reloaded w/ M2D Build 21882 Cracing recently posted? For my kitchen you can do this. Copy the sample folder under Wizard_Kitchen and rename the copy to something like _CR96_RC5 or any other name that works for you. Best to have no spaces. Then copy EXT, OEM, ROM and SYS folders from Cracing's kitchen you downloaded to your new folder _CR96_RC5. Then drag and drop the _CR96_RC5 folder on to the OVEN.exe file and the kitchen will start making your ROM.
Cracing's ROM is clean you so can answer no to the Configurator as he already has a complete Config.txt file in his kitchen. Also, you can answer no to the include an Ext_ROM question or pick yes and copy the empty extended ROM I included in the kitchen. There are a few other questions to answer and yo can try it different ways to see what you like best.
You are correct. The extended ROM only lets us add more stuff into our phone during a flash. I am still watching ShaDrac as he works on Extendir.
n2rjt said:
I downloaded this kitchen, extracted it to c:/WizardKitchen, and dragged _Cracing_Latest into OVEN.exe, then answered all the questions with the defaults. The resulting OS was too big.
Click to expand...
Click to collapse
Use LZX compression. That is how I manage to fit more stuff. I do it by default now asa matter of habit.
If that alone does not help. I typically choose 0, Try Reducing, 4MB pp and include -no cert for the other question group
Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.
n2rjt said:
Thanks, much closer now. Compression was the key to making it fit.
Yes I am trying both _Cracing_Latest and _Cracing_RC6 which I copied from CRACING's recently released kitchen. I am focusing on RC6 but using your _Cracing_Latest as a sanity check.
They both build successfully now. I have not yet burned _Cracing_Latest, but when I burned RC6 it doesn't boot. I've tried twice: it gets stuck at the second screen. I will try same with _Cracing_Latest since I assume it works.
Click to expand...
Click to collapse
Both of his versions booted for me. Hmmm, I'll try to think of what it could be.

Categories

Resources