Related
Greetings,
I want this version of faria to put in any rom of my like,
I want help, to get it integrated in the rom or in any other to get it.
I have tried to put the all the file of this application taken out from molski 3.3 to muns rom by deleting the original camera file and replacing it with farias camera application, but i failed, after i cooked the rom i was surprised to see the old htc camera application although i put the file.
Can anybody tell me (or Faria), which file i require to put, to get the faria's camera application.
thanks
I have the same version and build number, except mine does not say faria. What is different between the two?
well, I googled and found faria's camera app and loaded it to my phone. so far so good. liking the extra templates.
Edit** Night mode puts out some great results!
tROZAN PLEASE GIVE ME THE LINK
do a google for faria3.3camera.rar and make sure you show omitted results.
Hey trozan im searching from quite a long time please can give me the application i cannot find did the show ommited results.
samy.3660 said:
Hey trozan im searching from quite a long time please can give me the application i cannot find did the show ommited results.
Click to expand...
Click to collapse
i found it
ftp://xda:[email protected]/Uploads/WIZARD/Applications/faria3.3camera.rar
and
http//tonblom.com/ftp/faria3.3camera.zip
links not working
i tried those 2 links and neither 1 worked
http://4pda.ru/forum/index.php?skinid=1&showtopic=29629&st=90
Found out
Thanks to trozan.
Direct link
Moderators If thats not supposed to be here, than do tell me i will take it out.
Thanks
how to?
how do u import the camera reg key
i didn't see a camera reg key and therefore did not import it. I just rebooted after copying all the files and it's working fine on my phone
Greetings,
How did you copy it just doesnt copy in windows folder.
Thanks
copy reg key using total commander and task manager
samy.3660 said:
copy reg key using total commander and task manager
Click to expand...
Click to collapse
What am I missing? I didn't see or find a reg key in the .rar file.
hey tell me how you copy the file as i cannot???
And to see reg file you must set view hidden file in the folder option.
I first put the files that are to be copied to the windows folder in a folder on my storage card (any folder). I then opened total commander and selected all the documents in that folder and did a copy to the windows folder. done. Restarted the phone (using the power button) and when it came back up, Faria camera, at your service.
Did you find the difference in camera.?
Apply this fixes it will become more better
"Gamma_User"=dword:00000000
"Brightness_User"=dword:00000064
"Contrast_User"=dword:00000004
"Gamma"=dword:00000000
"Brightness"=dword:00000064
"Contrast"=dword:00000004
tommorow i will give more.
After working with the extended ROM, another thought occurred to me. This is all working fine for faria's ROM... but in future I may not have a ROM Kitchen to reconfigure the ROM. Is there another more generic way to solve my problem of getting my custom apps and settings on a new ROM release? Setting up the extended ROM and using autorun.exe to autoexecute .cab files got me thinking....
Is it possible to run autorun.exe manually after a ROM installation and by setting registry keys appropriately point it to a group of cab files on a storage card? Or is there some other way to do this? For a vanilla ROM, I have like 20+ cab files to install to get all my applications and customizations installed. Automating this process as much a possible would be hugely helpful !
Thoughts? Anyone doing something like this?
So what would you like this app to do?
Auto install all cabs in the ExtROM
Configure the network of your choice
Process some XML which has all of you personal tweaks and speedials or even activesync settings in it
This is all possible with a simple c# application.
Maybe this will do the job
http://www.freewarepocketpc.net/ppc-download-pocket-pc-installation-creator-v1-8.html
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,
I am using the hypercore kitchen and using its right's TNT.1437 TouchFlo as a base for building off of for my own Rom and I want to replace the standard SMS application with the WM6 Threaded SMS app in Rom instead of having to install a cab file every time I hard-reset.
Basically I want the standard SMS application gone, and the new Threaded SMS app in Rom. I want it to be just like a cab installation but without an actual installation.
Below attached is a zip file for "WM6 SMS Files"
Please someone help me out on this one.
Does nobody know how to do this?
I didn't download the zip file, but if there's a cab in there, just follow the directions in Sambartle's tutorial under the packaging section.
http://forum.xda-developers.com/attachment.php?attachmentid=44308&d=1184780703
I just used these directions today and it works great.
Alternatively, you can also add the cab to the ext ROM. There is a file you add the filename of your cab into and when the customization process starts, it'll auto-install your cab. I haven't yet figured out how to set up an ext ROM so I can't help with that part.
The link doesnt work but its right is helping me with this already. Thanks though.
You would add it to the extended rom.......
How to do this...I'm still...learning myself
dwny said:
You would add it to the extended rom.......
How to do this...I'm still...learning myself
Click to expand...
Click to collapse
There's a tutorial on XDA Ftp made by faria on how to edit the extended rom.
Basically you open the Extended Rom with WinImage, edit the config.txt and update the cabs you want in it.
Pretty easy thing to do.
P.S. You can also find an empty extended rom on the ftp. You can add autorun.exe and config.txt with the cabs you want.
Hi everybody? I am trying to find a solution to a issue with sasimi on the new 6.5.X roms (with the start button on the lower bar). The issue is that sashimi cant install cabs to storage card. I searched the web and foud some ideas that u need to hack the sashimi.mrsc file but none of them was working.
Can anybody who succeeded in runing sashimi post his workoround? That would really help me. Thanks ion advance.
Nobody here uses sashimi?
Hello
unpack attached and replace the file in \\SASHIMI\Program\Bin\SASHIMI.mscr
and it will work with Win 6.5.X
Man, I love you, thanks.
secoseco said:
Hello
unpack attached and replace the file in \\SASHIMI\Program\Bin\SASHIMI.mscr
and it will work with Win 6.5.X
Click to expand...
Click to collapse
Will it also still work with older winmo versions? Or does this break that functionality... thanks though! (Thinking of it, only using 6.5.x now anyway...)
dagrim1 said:
Will it also still work with older winmo versions? Or does this break that functionality... thanks though! (Thinking of it, only using 6.5.x now anyway...)
Click to expand...
Click to collapse
no it will not working with 6.5, first backup SASHIMI.mscr original first for using later with 6.5
secoseco said:
Hello
unpack attached and replace the file in \\SASHIMI\Program\Bin\SASHIMI.mscr
and it will work with Win 6.5.X
Click to expand...
Click to collapse
Faaaaaaaaaantastic, it works.
Now, is there a way to install cabs to the device as well. I have tried "device" and nothing for the ASL directory, but nothing installs.
I have the Autoinstall facility on my rom but am a bit dubious to have have Autoinstall and Sashimi both working after a re-rom.
steveianson said:
Faaaaaaaaaantastic, it works.
Now, is there a way to install cabs to the device as well. I have tried "device" and nothing for the ASL directory, but nothing installs.
I have the Autoinstall facility on my rom but am a bit dubious to have have Autoinstall and Sashimi both working after a re-rom.
Click to expand...
Click to collapse
you need to install Sashimi program once in you device to storage card
1- if you already install Sashimi.cab you will get SASHIMI folder in storage card
2- copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\
3-copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\SC\
3-copy reg files that you want to install in SASHIMI\Auto\REG\
and so on
after you upgrade your Leo or hardreset it, run Autorun.exe from SASHIMI\Program\2577\
and chose AUTO
secoseco said:
Hello
unpack attached and replace the file in \\SASHIMI\Program\Bin\SASHIMI.mscr
and it will work with Win 6.5.X
Click to expand...
Click to collapse
I'm so glad that it works again...
secoseco said:
Hello
unpack attached and replace the file in \\SASHIMI\Program\Bin\SASHIMI.mscr
and it will work with Win 6.5.X
Click to expand...
Click to collapse
I just replaced my SASHIMI.mcsr and it does fix files installed to the device memory but for cabs installed to the storage card, I have to still select storage card and hit 'OK'. Then I have to go to the Home menu and come back to SASHIMI before SASHIMI will carry on with the next cab (in which then I have to repeat the steps for all cabs to be installed to the SC).
Anyone know what could be wrong?
I'm running: Energy.RHODCDMA.23549.Sense2.5_with_Cookie_HomeTab.Mar.20.7z
on a TP2
Me too
It seems that the "SendSpecial ("Down")" is not working and the script may be hanging on the command, or something like that. You don't see the selection change, so it could also be the "SendSpecial("Space")" not working. Either way, the "SendSpecial("LeftSoft")" just after is obviously not firing. Not sure why it's different now, but it apparently is. There used to be a "SendSpecial("CR")" instead of the "SendSpecial("Space")", so I'll try that to see if it's working again (worked in win6.1, not in win6.5). Mine's been working just fine, up till the very latest Energy ROM on my CDMA TP2.
LightC said:
I just replaced my SASHIMI.mcsr and it does fix files installed to the device memory but for cabs installed to the storage card, I have to still select storage card and hit 'OK'. Then I have to go to the Home menu and come back to SASHIMI before SASHIMI will carry on with the next cab (in which then I have to repeat the steps for all cabs to be installed to the SC).
Anyone know what could be wrong?
I'm running: Energy.RHODCDMA.23549.Sense2.5_with_Cookie_HomeTab.Mar.20.7z
on a TP2
Click to expand...
Click to collapse
I think it connected to the roms u are using. For me it worked with one rom, then I flashed other rom and I experencied the same thing as you.
sorry to ask, but so far I have no clue about Sashimi but would like to use it and read therefore as much as I could.
Is point 3 a typo?
>3-copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\SC\
shouldn´t it be:
3-copy cab's programs that you want to install in Storage Card to SASHIMI\Auto\cab\SC\
Sorry to ask maybe the obvious but for a newbie it is helping to sort out missunderstanding.
Best regards,
dingolino
secoseco said:
you need to install Sashimi program once in you device to storage card
1- if you already install Sashimi.cab you will get SASHIMI folder in storage card
2- copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\
3-copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\SC\
3-copy reg files that you want to install in SASHIMI\Auto\REG\
and so on
after you upgrade your Leo or hardreset it, run Autorun.exe from SASHIMI\Program\2577\
and chose AUTO
Click to expand...
Click to collapse
dingolino said:
sorry to ask, but so far I have no clue about Sashimi but would like to use it and read therefore as much as I could.
Is point 3 a typo?
>3-copy cab's programs that you want to install in main memory to SASHIMI\Auto\cab\SC\
shouldn´t it be:
3-copy cab's programs that you want to install in Storage Card to SASHIMI\Auto\cab\SC\
Sorry to ask maybe the obvious but for a newbie it is helping to sort out missunderstanding.
Best regards,
dingolino
Click to expand...
Click to collapse
You're right there off course
I am having no luck with the v8.0 of Sashimi. I have the Artemis ROM (WinMo v. 6.5.5).
Auto mode only installs cabs from cab/ASL folder. I replaced the Sashimi.mscr with the one posted in this thread but to no avail.
Do you guys have any suggestions?
me too,
sashimi doesnt install (not works) for new artemis v7. It install all my cabs from auto/SC to device becasue it can not move cursore down anymore..
any suggestions?
I also had a problem with cabs not auto installing onto my Storage Card, instead they were installing to My Device. I have been doing some hunting around for the solution and i think i have managed to find it. (its worked for me anyway).
Go to SASHIMI > Program > Bin, BACKUP SASHIMI.mscr and then replace with the one i have attached. I am no coder so please don't ask me about specifics, there were just some hashes added to the beginning of a couple of lines of code. Like i say it worked for me, so hopefully it will work for you Let us know if it works for you. Cheers.
I'm surprised that either of the attachments on this thread works on HD2 Leo. I found that there is a very basic problem with mortscript and all sashimi scripts will hang. Two symptoms:
1) if not in flight mode, sometimes hangs during initialisation
2) if auto install to storage card, will hang (leaving you to select the radio button and press install)
and there is no easy cure.
padlad said:
I also had a problem with cabs not auto installing onto my Storage Card, instead they were installing to My Device. I have been doing some hunting around for the solution and i think i have managed to find it. (its worked for me anyway).
Go to SASHIMI > Program > Bin, BACKUP SASHIMI.mscr and then replace with the one i have attached. I am no coder so please don't ask me about specifics, there were just some hashes added to the beginning of a couple of lines of code. Like i say it worked for me, so hopefully it will work for you Let us know if it works for you. Cheers.
Click to expand...
Click to collapse
thx m8,
i will try it
i'm on wm 6.5.x and sashimi stalls at SASHIMI INITIALIZATION COMPLETE.... HEEEEELP!