Related
Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: http://www.scpsoft.com/remoteprotect.htm [Attention MODs: This is NOT a WAREZlink!])
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.
licht77 said:
Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: LINK REMOVED
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.
Click to expand...
Click to collapse
Paranoid much ?
Probably an IMO for the US Govt somewhere. They are worse than Nazis. That is why I ditched my issued blackberry for my Hermes.
Well, I think that this is not much paranoid.
I spent for my PDA over 700 euros, so if it is stolen it isn't very good!!! ;-)
For this reason, I bought a legal copy of UTA (Ultimate Theft Alert v.3) and I updated my Schap's 3.30c ROM with all necessary files from the original "UTA v3.CAB" (no Config, only program, dll, and configuration and license files...).
It seems to run very well!!!
Today, after reading this thread, I tried remoteProtect, but I don't like it so much, because if I send a SMS to my PDA, then the theft will see it and can go to flight mode.
If you want to do the ROM upgrade, you must choose your preferred ROM. After, I suggest the "CorePRO_HermKitchen.exe", that contains all the tools you need, with a tutorial about dumping and cooking your ROM.
If you need help, I'm here!
Bye Bye.
I think it's a good idea - I used to work in the Netherlands and on an emergency trip home one weekend, my phone was stolen by someone after my luggage was checked in at Schipol (it was the first HTC Canary smartphone, actually ) Anyway, I didn't notice that it was missing until I got back to NL 4 days later as I thought I'd just missed it in my rushed packing, but in that time, the thieving toerag had run up a £650 phone bill (it was stolen in NL and I got stiffed for roaming charges too
So anyway, I'd be interested too
Smiffy.
@NRGZ28: Yes - I am really paranoid... - this comes with the job
But as Mobilez6600 states correctly - its a question of hardware value too...
@Mobilez6600: Ill have a look into CorePRO_HermKitchen.exe - all I played around so far was Bepes Kitchen... there was no howto and i just cooked a german ROM - i think i was just lucky
Ill give it a try - but if there is a tutorial anywhere i would be glad!
greetz, licht
PS: On my installation the thief cant see the incoming sms... ?
Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez!
JasenR said:
Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez![/QUOTE
Dont get your panties in a bunch...
Click to expand...
Click to collapse
NRGZ28 said:
Dont get your panties in a bunch...
Click to expand...
Click to collapse
Thanks NRGZ28, I guess, for your concern about my comfort, everything is fine in that department.
Even more thanks to the mods for their continuous efforts in keeping this site warez free.
@Mobilez6600: Thx for your informations!
I read into Core Kitchen, dumped my preferred rum (Schaps 3.30c german) and created a package out of the desired cab according to theese snippets from the forum:
I don't know if the new Office will work on other builds....
Sorry i can't be more specific...but i didn't tried it so far. So i can't tell you what files to copy or if it will work.
Just try and if you get it working...then you could share that with us too.
I am in the middle of something now and can't try this now....Hope you understand.
Regarding on How to make a package....
* Take a CAB
* Open it with CabAnaliser ...in Extra folder
* Select the XML tab...there save the registry settings in an unicode txt file.
* Extract all files
* Place all files in an folder , and add there an .dsm and rename the previous txt file in .rgu ....assign both the .dsm and the .rgu an UUID (both same UUID)
* Run the initflashfile generator...in Extra folder. Follow instructions...
* Place the generated "initflashfiles.txt" in the same folder you placed previous files
* Give a friendly name to your folder , move it into the OEM folder and pray it will work.
That's it. If you read previous posts you'll know what an .dsm is and how to make one and what is an UUID and where to get it from.
- TIP : If that doesn't work, open the initflashfiles.txt and replace all the "squares" with an tap on ENTER button....It's easy to check the initflashfiles.txt than to create it without that program, trust me.
to create a .dsm
* Create a new empty .txt document
* Go here http://www.famkruithof.net/uuid/uuidgen/ and create a "RANDOM" UUID (example of UUID :2981dd18-0f2c-11dc-8314-0800200c9a66)
* Rename the *.txt into 2981dd18-0f2c-11dc-8314-0800200c9a66.dsm (the UUID is only for example, create your own)
* If you have registry settings, use THE SAME UUID ...so for example rename the *.reg file into : 2981dd18-0f2c-11dc-8314-0800200c9a66.rgu
Click to expand...
Click to collapse
So far - so good. Additionally, a single txt file needs to be copied into rootfolder of the device before installing my custom cab... i put it into rootfolder of the cab for testing.
Unfortunately i get an error during build_os: "Could not find file d:\core\kitchen\temp\dump\Program Files\imageinfo.bin" when build_os is processing my created folder in OEM.
Any advice is highly appreciated...
There is a .DOC tutorial about dumping and re-creating ROM in CorePro_HermKitchen. I used it and I only inserted my files in a folder. After, I modified "initflashfiles.dat", to copy a link in \Windows\StartUp directory, so UTA could run automatically on soft-reset (and hard-reset ;-).
I don't know if it is right way, but it runs, and I'm happy!
Sorry for my late answer, i was - ehm unavaliable - some days.
You are talking about initflashfile.txt and not .dat right?
I still get this error, but i will keep working on it
Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
PAPPL said:
See this great theft protection Peter Poelman made here at xda-devs!
THIS WOULD BE GREAT!
IIWPO WIKI
IIWPO Thread
Click to expand...
Click to collapse
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
2. UTA v3 (commercial Trial avaliable) Recognizes SIM change (supports several SIMs), sends SMS. No SMS commands possible. Optionally (commerical plugin) sends contactlist too. Needs 2 individual files included in ROM.
3. IIWPO (free, xda-dev)
Recognizes change of owner name. Needs 1 individual file included in ROM. No SMS commands possible, no recognation of SIM change.
What prevents a reflash with different rom?
nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me
licht77 said:
nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me
Click to expand...
Click to collapse
im sure if you had a quick talk to Olipro about the bootloader... he might be able to help you out with a BL that wont allow you to flash without a special CID...
licht77 said:
Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
.....
Click to expand...
Click to collapse
@licht77: remotePROTECT is great. But how to install the 1txt file in root folder? Will this survive a hardreset?
Hi Pappl!
Yes, it should survive a hardreset... thats why i dont want to put it into extRom (because the installation of all the extRom - stuff can be cancelled too easy by a hardreset followed by a softreset after screen calibration) but in ROM itself.
This way you have a) your data pretty secure and b) may track down a possible thief. The only thing a (skilled) thief could do is to completely reflash the device (but if he is curious before and tries to access your data with his SIM or so... hehe then u got him)
Like walshieau proposed, it should be possible even to block a complete reflash of the device by a custom booloader - but i dont want to nag olipro before the other tasks are finnished. In that case a stolen hermes is really useless for the thief... and thats a nice idea if this could prevent theft
remotePROTECT can be installed without that text file to the root folder, you just need to set it up first, and extract the setupE.txt file from it's running folder then rebuild it into that folder from the cab file.
I however would like to do this without the cab, cab's can be prevented from running by simply softresetting during that phase of the setup. I have built all the files into one of my roms and put in all the registry entries however the application does not work this way! Setup.dll seems to do some important things and I'm not sure what.
Anyone have any ideas? I'm gonna email the author asking.
You are right... didnt see that encrypted "setupE" file...
Which kitchen are u using? What were the steps u did until now? I am sure we can solve this!
OEM supplied by Schaps. This version already integrated in his last ROM.
Not like previous version, this version Profile Tab already work correctly. No need to do anything. I have use it for several days and I dont notice any notifications queue issue or wild vibrate at all.
But I do change the following:
-Installation directory change to \HTCHome instead of \Windows
-To get Brightness shortcut working, the same patch as previous version applied.
-The same patch applied to enable the Tab Setting through registry.
Other than that Nothing. Much better version than v1.5
Color version uploaded!!!!
If you are ROMcooker, download the htchome.dll for rom cooker .
Install sdkcert.cab if you have not done so.
There are about 100 pages of discussion about v1.5. Lets not repeat what have been discussed over there like: Clicking left most mail icon will take you to MMS, how to change music tab tolaunch HTC Audio Manager, and so on and so on. I dont plan to follow up closely on these thread as I think this version is very good already. Should there be any fix, change, etc please refer to the respective post.
Enjoy
Is this better than the one you had released with your kaiser skin?
Currently i am using that, is it worth me updating?
Thanks
Bennec, the one you are using is v1.5.xxxx. Very earlier and uncomplete version that has been tweaked to make it reliable enough to be used. This version is a new build with the profile tab working and additional features in the contact tab thatenable you to select what number ina contact for the speed dial. Definately worthed.
Can you post a version where the files do go in the windows directory? I want to cook this in, but not have duplicates.
TooSharp said:
Can you post a version where the files do go in the windows directory? I want to cook this in, but not have duplicates.
Click to expand...
Click to collapse
you can, just use windiff on the SYS and OEM folders of your kitchen, the dump folder is created by processing these 2 folders, so any file dups will be in there BEFORE you run buildos.exe.
add you package, then run windiff ont he SYS and OEM folders, it will find the file duplicates, and delete the ones that ARE NOT from your new package!!
bennec83 said:
you can, just use windiff on the SYS and OEM folders of your kitchen, the dump folder is created by processing these 2 folders, so any file dups will be in there BEFORE you run buildos.exe.
add you package, then run windiff ont he SYS and OEM folders, it will find the file duplicates, and delete the ones that ARE NOT from your new package!!
Click to expand...
Click to collapse
Maybe I should have been more clear.
When creating a rom, all files will be placed in the windows directory, if you need files in a different directory like the cab posted above you will have to use initflashfiles which just copy the files to a new folder, then you will have duplicates. I just don't want 2megs of photos in two spots.
Garphical Anomolies
@schen you need to swap some of the icons for my fixed ones!!
please Download this Original Icons Fix and add it to you package. 2 of the black and white icons (Music and People) dont react properly when you select them.
that link fixes them!! (it is not just yours, it is a common problem with all htc home plugins!!!)
TooSharp said:
Maybe I should have been more clear.
When creating a rom, all files will be placed in the windows directory, if you need files in a different directory like the cab posted above you will have to use initflashfiles which just copy the files to a new folder, then you will have duplicates. I just don't want 2megs of photos in two spots.
Click to expand...
Click to collapse
Your question makes no sense then!
When you COOK this in obviously you would remove the version you already have in the ROM therefore you would not have the duplicates.
Also if you just created an package out of the cab above you will get NO initflashfiles therefore the package will install to the windows directory!!!
bennec83 said:
Your question makes no sense then!
When you COOK this in obviously you would remove the version you already have in the ROM therefore you would not have the duplicates.
Click to expand...
Click to collapse
You still don't understand. My problem is NOT buildos failures. I don't want duplicates when the rom is complete. Any time you use a initflashfile you will have duplicates in the finished rom. That is what they are for. Again the problem is not with duplicates in the OEM and SYS. If you go back and check my posts you will see I helped you with this exact problem. I know how to create a rom!!!! What I don't know how to do is edit the dll file to redirect it to look in the windows directory for the png files. Hence why I'm posting.
bennec83 said:
Also if you just created an package out of the cab above you will get NO initflashfiles therefore the package will install to the windows directory!!!
Click to expand...
Click to collapse
Yes you do get a initflashfile that copies all the png files to HTCHome. See attached.
schen, installed & everything working fine, except for one, am unable to use the hardware navigational pad when accessing music tab, from there u can't proceed to go up, go to ff, rw or play button.
Touchscreen function (for all of the above ff, rw & play tabs) in music tab is working though.
thanks anyway.
TooSharp said:
You still don't understand. My problem is NOT buildos failures. I don't want duplicates when the rom is complete. Any time you use a initflashfile you will have duplicates in the finished rom. That is what they are for. Again the problem is not with duplicates in the OEM and SYS. If you go back and check my posts you will see I helped you with this exact problem. I know how to create a rom!!!! What I don't know how to do is edit the dll file to redirect it to look in the windows directory for the png files. Hence why I'm posting.
Yes you do get a initflashfile that copies all the png files to HTCHome. See attached.
Click to expand...
Click to collapse
Funny, i created the package and i didnt get that!!!
il have to look into the flashfile generator in using (im not using the core one that you are!!)
Thanks for the heads up and apologies for the confusion!!!
bennec83 said:
Funny, i created the package and i didnt get that!!!
il have to look into the flashfile generator in using (im not using the core one that you are!!)
Thanks for the heads up and apologies for the confusion!!!
Click to expand...
Click to collapse
No problem. Thanks for the help. Sometimes it's hard to convey what you are thinking in words, especially about something so confusing.
TooSharp said:
No problem. Thanks for the help. Sometimes it's hard to convey what you are thinking in words, especially about something so confusing.
Click to expand...
Click to collapse
Well then my answer to your question would be to remove the initflashfile, then everything would get installed to the windows directory and since you have no need for shortcuts, this would be fine!!!
been using this for a while and saw the new version a while ago. has option of more when u go to the 4 day detail in weather. fonts seem nicer and all. looks like a good upgrade to 1.5 Bennec83 irc bro
schen said:
OEM supplied by Schaps. This version already integrated in his last ROM.
Not like previous version, this version Profile Tab already work correctly. No need to do anything. I have use it for several days and I dont notice any notifications queue issue or wild vibrate at all.
But I do change the following:
-Installation directory change to \HTCHome instead of \Windows
-To get Brightness shortcut working, the same patch as previous version applied.
-The same patch applied to enable the Tab Setting through registry.
Other than that Nothing. Much better version than v1.5
I will create a separate Cab based on Schaps color version as well in a minute after a few try this cab with no problem.
Enjoy
Click to expand...
Click to collapse
Thank you for the new version, and tab setting is essential. Thanks again!
bennec83 said:
Well then my answer to your question would be to remove the initflashfile, then everything would get installed to the windows directory and since you have no need for shortcuts, this would be fine!!!
Click to expand...
Click to collapse
Just tried that. It doesn't work without the png files in the HTCHome directory. I guess we can't have everything.
The special dll for installing n Windows directory uploaded. Use that dll.
On the subject of weather plugin.
I am not sure why is there a need for a pre-configured xml file. Anyway, you need a gui to choose the city. Why not have a gui where you could enter the data which is stored on xml file. I suppose rather than sending an entire xml line when communicating with xml service, build an xml file base on the data entered via gui.
As I understand it, the DLL was just edited using a hex editor as \HTCHome and \Windows has the same number of characters, it sounds like it wasn't a decompile thing or something like that.
I'm not at home at the mo so I can't check but if you load the DLL up into a hex editor (winhex?) then replace all the \HTCHome text with \Windows, you should be good to go.
This is just my uderstanding though of what I've read in the previous....saga
Smiffy.
schen said:
The special dll for installing n Windows directory uploaded. Use that dll.
Click to expand...
Click to collapse
Thanks for the fix!!
Does anyone know how to make custom roms for devices like the Excalibur or other Smartphones. I want to remove a lot of the clutter and add some applications of my own.
JAmerican
Not there yet AFAIK.
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
momentarylapseofreason said:
This is something I hope to see... I mean why even bother with getting the HTC unbranded version if we can remove all the clutter ourselves?
Click to expand...
Click to collapse
Bug fixes! Even if you build a custom rom, you would want to start with the latest available OS to get in on whatever bug fixes have been added. Then you would rip it apart and add/remove whatever you wanted. Sometimes the new OS would also have added/improved features, but the bug fixes is the main one.
mar11974 said:
The closest I have gotten is extracting the rom components and mixing them. I took the HTC Splash, the HTC Radio, and the T-Mobile OS; made a custom ruu and flashed successfully. Now my Dash shows HTC Screen when it boots and I have the updated Radio. I managed to dump the T-Mobile OS, but haven't been able to rebuild. HTCRT by Dark Simpson will create the ruu_signed.nbh for use with the uspl though. NBHEXTRACT will break the nbh into its components. Tried the HYPERCORE tools, that's how I got the dump of the OS, but cannot do the xip parts with these tools for some reason. PKG Tool works. Have the OEM and SYS folders, but XIP comes up empty.
Click to expand...
Click to collapse
Thanks for the insight. I reached as for as extracting the .NBH into .NB files with OS, GSM etc. How do you extract these. The PKG Tool didn't work for me and the Hypercore tools aren't working right either.
JAmerican
Hey all,
I was able to downgrade to WM5 and I am starting to understand a few things regarding ROM building but I still don't know how to edit the Windows.nb or OS.nb file. Can anyone offer suggestions. I am trying to optimize it so that there is less clutter.
JAmerican
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
da_mayhem said:
I was able to extract the the OS.nb before and edit it, but unfortunately, it was not fully extracted as i was hoping, at first i thought i was able to fully extract it, but when i tried to reflash again the OS, it was flashed normally but not as functional as normal one, many were not included, the Start Menu seems to be incomplete, no keypad lock, no quickapp etc... so i came up with a conclusion that it was not fully extracted..even the initflashfiles.dat were not present on the dumped files, i thought that file was the only one missing and i tried to manually copy it from /Windows/ directory and put it on the dumped files folder..but it wasn't a success.
Anyone successful to fully extract the OS? I'm slowly compiling a kitchen for Excalibur and the full extraction of the OS is only the missing part of the kitchen and i'm stuck with it. Once it is up and found a solution, then we can come up with cooked roms for Excalibur.
Click to expand...
Click to collapse
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
JAmerican said:
Cool. I went back to WM5 to see if it was more efficient but with all the lack of features (email instant search, alpha-dialing, file syncing, etc.) It was not worth it. I went back to WM6. I hope we can get some cook ROMS soon. I really want more usable RAM. Could you give me the exact steps you used to extract the ROM? I tried HyperCore but it doesn't work for me for some reason.
JAmerican
Click to expand...
Click to collapse
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
da_mayhem said:
Try this mate:
Aserg's Imgfs Tools, attached on THIS thread
Place OS.nb on the same folder then execute !UI_wwe.cmd
Choose P - Unpack OS.nb <for Herald-Prophet> to dump-folder
the ROM will be dumped on the "dump" folder, but i don't think it's a complete dump, if there's anyone knows how to do the complete dump, please share
Click to expand...
Click to collapse
Thanks for sharing! I was finally able to dump it. Now to see if I can mess around and get it to build! Wish me luck .
JAmerican
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
da_mayhem said:
You can easily build it again, but the question again is, are the files on the dump folder complete? i wish you luck mate! keep us posted.
Click to expand...
Click to collapse
I deleted some files from the ROM and rebuilt it but it was in .NBA format. I don't remember exactly what I did but I think I renamed the file to .NB and made a .NBH file out of it. Then Flashed my device. I got as far as the WM screen and was stuck there. I reflashed with the Standard WM6 ROM from T-Mobile. .
I'll try some more messing around. I really want to get some cooked roms for Smartphone edition.
JAmerican
Your right about files missing. I was able to extract the ROM and its packages and get two folders (ROM and SYS) along with other packages. The program I used (Package Tool) states that I am missing the following files:
[Missing Files]
SYS\MSXIPKernel
MODULE: busenum.dll
MODULE: cachefilt.dll
MODULE: certmod.dll
MODULE: coredll.dll
MODULE: device.exe
MODULE: devmgr.dll
MODULE: diskcache.dll
MODULE: encfilt.dll
MODULE: fatfsd.dll
MODULE: fatutil.dll
MODULE: filesys.exe
MODULE: fsdmgr.dll
MODULE: fsreplxfilt.dll
MODULE: hd.dll
MODULE: imgfs.dll
MODULE: mspart.dll
MODULE: osaxst0.dll
MODULE: pm.dll
MODULE: regenum.dll
SYS\WinCENLS_WWE
File: wince.nls
OEM\LangDB
File: initflashfiles.dat
File: mxip_lang.vol
OEM\OEMXIPKERNEL
File: boot.hv
File: boot.rgu
MODULE: cecompr.dll
MODULE: ceddk.dll
MODULE: HtcFsdspy.dll
File: mxip_initdb.vol
MODULE: nk.exe
MODULE: ONDisk.dll
and these files are in the Windows folder as well as other locations on my device. The only problem is that the device denies me access to these files. Is there a way to access these DLLs with a powerful file manager. I tried Resco and Total Commander to no avail. Anyway to trick the device into allowing me to copy these files?
Thanks.
JAmerican
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Ok so I was able to extract the T-Mobile WM6 ROM, I was able to use the Package Tool to get it seperated into a SYS and OEM folder. I deleted things like Live Messenger and Windows Live. I put the updated version of Live Search in ROM. I only added one other application, CeleTask. I didn't want to put too much work into tweaking this thing and find it not working. I am downloading the CreateOS.exe and CreateROM.bat files and will try to compile this thing. Wish me luck.
JAmerican
jockyw2001 said:
I believe there is a need for a simple ROM cooking procedure on devices such as Excalibur and Vox. I'm thinking of a "Norton Ghost" procedure to backup and restore the entire OS and User Filesystem partitions.
The ROM cook procedure would then be something like this:
1. customize the device (all changes stored on device memory of course)
2. backup OS partition (using special USPL)
3. backup User File System (using special USPL)
And a user would just do this:
1. restore OS partition (using RUU)
2. restore User File System (using RUU)
3. personalize device
Does that sound acceptable?
Click to expand...
Click to collapse
Hey friend. I know this is not appropriate place to post this, but since you know my situation on the wifi of my phone. Would it be possible to put a working reverse flash of a tmobile dash onto mine and fix the wifi. I have tried everything. And you have been very helpful and it is much appreciated.
keep up the progress guys, i can't wait to try some of the cooked roms from users on this site
Good luck, i can't wait either....
Hey guys,
I used a tool to try and convert my unpacked ROM back to a packed (one folder ROM) and it deleted all my progress. Go figure. So I have to basically start all over again. This time though, instead of making all the changes. I am just going to remove like myFaves, update LiveSearch and add one of my own applications as well as one of my favorite applications and see if I can flash my Dash with it.
Somewhat but its my fault for not backing up.
JAmerican
Hi, everyone! I´m still working on a Wizard (don´t want to touch my Hermes, yet). I´m pretty advanced... but
I dump the [latest] original cingular WM5. I rebuilt it with office 2007 and realize that the original shortcuts are still there. Of course, they are both useless (as I have new names for the apps) and annoying (because I can´t remove them before compiling).
This is the whole point: Those shortcuts are not coming from neither an xml update for the XIP nor an initflashfiles.txt
HOW ON EARTH DO I REMOVE THEM. I can´t find what is creating and copying those shortcuts
Are they embedded in the OS.nb file? If so, how do I take that file apart?
Any help is very much appreciated!
..provxml, m8..
Nope, had checked already
*.mopvxml, etc had been checked.
But... what did you mean by m8?.
BTW: I will check inside os.nb now, but please give me fresh ideas
You may also want to check for a file called initflashfiles.dat. That contains a lot of shortcut information as well. Especially for apps that are default for that particular ROM. It should be found in the OEM\OEM_LANG_* folder in the kitchen. The (*) is the locale number. For example, a WWE ROM would have the folder as OEM_LANG_0409.
Yep, solved (initflashfiles.dat)
Hey, thanks! You´re FAST!
I was about to post it. But thanks, you could have saved me hours
Anyways. If anyone ever reads this thread, remember: scavenging os.nb(a) isn´t that great. An automated kitchen does it all (Hypercore in this case).
I also found somebody claiming that certain shortcut came from a dll. Just keep as a sidenote.
Cheers!
***CHANGE LOG START
2009-09-23
- New:file preview (please note that cou can even preview manila encoded images inside cab file, since they are converter internaly!)
- in preview you can choose to extract manila file or PNG image.
- bug fixes, cosmetic changes... new bugs ...
- you probably realized that I publish versions I got at the moment - raw, not too much tested, relative big changes from day to day, version is detected by the pub date... so expect new staf soon...
- !!! IMPORTANT !!! Please download cfc.exe and put it at c:\windows\ "c:\windows\cfc.exe" !!! Download last version from http://forum.xda-developers.com/showpost.php?p=2798441&postcount=1 !!!
(without cfc.exe app won't be able to decode mailla images)
2009-09-22
**IF YOU HEVE BEEN HERE PLEASE READ THE WHOLE POST SINCE IT IS ALL UPDATED!!!
- "Cab Album" support:
A Cab Album is collected information about many Cab files in one place.
Application will here "create" a new Cab Album by scaning folder. (It is possible to include subfolders in search path.)
Since creating a "Cab album" could be time consuming (depends on how many files it has to scan),
collected information - an "Album" can be saved (in xml structured file).
So next time, you can just use the same information by "loading" a saved album from disk (without scaning again).
Creating album is the process that will
a) detact all *.cab files in scaning folder (and subfolders)
b) for each found cab, program will try to locate "_setup.xml" within .cab file and extract information about real / target file names and paths
c) all information will be collected to memory
After that you will be able to
a) browse an album by cab files (from the tree)
b) browse an album by target file names (also from the tree where these files are grouped an counted)
c) search / filter the album by target file names
Also you can
a) click on "save" icon to save the album.
b) double click on cab file (lef side - tree) to open separate window tith that cab info
c) double click on file on the right side to extract it on disk
2009-09-21
- new version suports drag & drop files (from windows explorer)
- small cosmetic changes
2009-09-19
- first published version
***CHANGE LOG END
DID you ever try to find some fine resource (manila file, bmp for phone skin ... or whatever), which you know you have seen somewhere. And you are sure you got it somewhere on your hard or stick or ....
DID you ever wanted to create a new skin based on a few existing skins in some cab files.
DID you ever ask yourself - what will that XY.cab install on my device? Will it remove parst of my customization that I don't want to be changed?
In case you didn't this app is probably NOT for you.
But if you DID then you probably know that
a) most cab extractors will NOT extract files with the correct filenames on your hard disk.
Instead of some "5acc5861_manila" that will be installed on your device, what you get on your pc is some file named "0CABA635.001".
The real target file name "5acc5861_manila" is actually set in _setup,xml which is part of cab file for mobile device.
b) it is hard to find all "5acc5861_manila" resources on your hard disk without decompression of all cab files, and fixing a problem described before - see a
What do you think about a new point of view - an "Album" view.
Album view will help you to "scan" your hard disk folders, searching for cab files, extacting information from them (without extracting cab files on disk), and collecting all important information in one Album list.
That's not all.
Since "scanning" or building an album could be time consuming, you can "save" the album (xml file structure) so next time you just open existing album and you got all information very quick.
You can search albums - for example "Assets*.bmp" will find all files located in album containing dialer skins.
With another few clicks you can extract found files on disk and use you favourite tools to view or edit them.
Prease note tha this application is extended version of
"[APP][v2009-09-17] Cab utility - RENAME cab content/files to normal target names" located at http://forum.xda-developers.com/showthread.php?t=561533
Requirements: .NET framework 3.5 on your PC
BTW: If someone know some good .NET library for converting / previewing or updating _manila files please do let me know.
Also if someone would like to use some of functionality of this app in other projects ... I will be glad if I can help providing details about my libraries.
I hope you'll like it...
Weeeeeeeeeeell
Awesome thank you!
UPDATE
Missing drag & drop support was anoying, so I add it to v2009-09-21.
You can find / download new version in fist post
cablib error
I get an error when opening a cab-file:
FileLoadExeption
Could not load file or assembly 'Cablib, version 10.3.0.0 ... or one of its dependencies. This application has failed to star because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT:0x800736B1)
cc62 said:
I get an error when opening a cab-file:
FileLoadExeption
Could not load file or assembly 'Cablib, version 10.3.0.0 ... or one of its dependencies. This application has failed to star because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT:0x800736B1)
Click to expand...
Click to collapse
Yes in some systems you can get this error. On my laptop I have no problems but on my home PC I had exat the same error.
What I did to solve this problem is to replace version of CabLib, and also I put 2 dlls in the same folder where is application.
You can find CabLibFix in additional attachment in first post. Just put those files in the same directory (replace existing CabLib + additional 2 new files).
Please do let me know if that helps
Could not load file or assembly 'Cablib
Please note that v2009-09-22 should fix problems with error "Could not load file or assembly 'Cablib.." on some systems.
"FIx files" are included in that version, so I removed "fix..." archive.
However if you still have problems please do let me know,
thanks
v2009-09-22
v2009-09-22 works like a charm.
Thank you again
v2009-09-23 now has image / text preview + info about manila type of file (xml, SQLite, Lua_Script, Mode_9 ...)
Also you preview manila IMAGE files (decoded using cfc.exe to png)
The only inconvinience is that I manage to hardcode path to cfc.exe ( "c:\windows\cfc.exe").
Sory!
Error on win64 with an 'any CPU' build
Hi
We are using your CabLib.dll v2009-09-23 to load cab files inside our c# application. It works really well, except for one case.
When we build the application for target 'any cpu' and then install on a windows xp64 machine, we get an error message:
System.BadImageFormatException: Could not load file or assembly 'CabLib, Version=10.3.0.0, Culture=neutral, PublicKeyToken=5c838b77b53f84a0' or one of its dependencies. An attempt was made to load a program with an incorrect format.
File name: 'CabLib, Version=10.3.0.0, Culture=neutral, PublicKeyToken=5c838b77b53f84a0'
Everything works fine when we change the target to 'x86', but that then causes problems with our test suite. The 'Any CPU' build only fails in x64 machines.
I was wondering how you build your DLL and if you have any ideas to help us fix this problem.
Here's my config:
Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1
The build and test is on an xp64 SP2 machine.
-- update --
I've also found that aiCabExplorer.exe has the same problem on my win64 machine. I see you are including the 32 bit C run time DLL's which you provide in the release - that appears to be the problem, as the OS is trying to dynamically link against the 64 bit version of MSCOREE.DLL, KERNEL32.DLL, OLE32.DLL and OLEAUT32.DLL and doesn't like mixing them up.
So the solution, I think, is for you to build without explicit dependencies on the 32 bit libraries. Is there any chance of getting a version like that?
Thanks,
Mark
Hi,
I use this app all the time.
Super duper.
Thank you very much.
Keith
Seems great Gonna try it