ROM COOK WANTED: SecureROM!

[licht77]

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.

 

[NRGZ28]

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.

Paranoid much ?

 

[wpbear]

Probably an IMO for the US Govt somewhere. They are worse than Nazis. That is why I ditched my issued blackberry for my Hermes.

 

[Mobilez6600]

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.

 

[Lordsmiff]

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.

 

[licht77]

@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... ?

 

[JasenR]

Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez!

 

[NRGZ28]

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...

 

[JasenR]

Dont get your panties in a bunch...

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.

 

[licht77]

@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

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...

 

[Mobilez6600]

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!

 

[licht77]

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

 

[licht77]

Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:

See this great theft protection Peter Poelman made here at xda-devs!
THIS WOULD BE GREAT!

IIWPO WIKI

IIWPO Thread

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.

 

[jompao]

What prevents a reflash with different rom?

 

[licht77]

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

 

[walshieau]

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

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...

 

[PAPPL]

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.

.....

@licht77: remotePROTECT is great. But how to install the 1txt file in root folder? Will this survive a hardreset?

 

[licht77]

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

 

[Shadowmite]

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.

 

[licht77]

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!