Custom OEM Requests ...Get them here! Updated: 4/18/09

[Whosdaman]

Rstoyguy, can you please make an OEM for S2U2 1.13

[DHarvey]

Originally Posted by Whosdaman

Rstoyguy, can you please make an OEM for S2U2 1.13

Here's a link to the cab. I figured I would post a link because even with google it took a few minutes to find

http://forum.xda-developers.com/showthread.php?t=412418

[rstoyguy]

Originally Posted by Whosdaman

Rstoyguy, can you please make an OEM for S2U2 1.13

The cab install seemed to work fine for me. So I'll put part of my name on this one.

OEM_S2U2-1_13-QVGA...............................Slide 2 Unlock v1.13

[fredcatsmommy]

Originally Posted by rstoyguy

The cab install seemed to work fine for me. So I'll put part of my name on this one.

OEM_S2U2-1_13-QVGA...............................Slide 2 Unlock v1.13

I saw on xda that A_C posted a fix for 1.13 that has to be added to the installed program, so if using this oem, I guess you can add the fix after installation, or it will need to be added to the oem:

Changes of v1.14 hotfix
- fixed the misbehaviour (lock failure; improper CallerID screen) when there is a data connection.
- fixed the bug of showing events of day after tomorrow as tomorrow.
(please d/l the iLock2-1.14hotfix.zip at the bottom of this post; stop iLock2; overwrite iLock2.exe with the extracted one; start iLock2 again.)

I'm posting the fix as posted on xda by A_C. Any chance of an updated Slide 2 megapack with the fix incorporated in with s2u2 1.13? Thanks again!!

[rstoyguy]

Originally Posted by fredcatsmommy

I saw on xda that A_C posted a fix for 1.13 that has to be added to the installed program, so if using this oem, I guess you can add the fix after installation, or it will need to be added to the oem:



I'm posting the fix as posted on xda by A_C. Any chance of an updated Slide 2 megapack with the fix incorporated in with s2u2 1.13? Thanks again!!

To apply the hotfix to the v1.13 OEM do the following:

1. Extract the archive.
2. rename ilock.exe to 000-ilock.exe
3. copy to your OEM directory

Done.

I will not be updating the S2U2 OEM until a more stable/final version is released.

I do this as a hobby, I can't spend 2 hours doing an oem just to do it again the next day....sorry...

[fredcatsmommy]

Originally Posted by rstoyguy

To apply the hotfix to the v1.13 OEM do the following:

1. Extract the archive.
2. rename ilock.exe to 000-ilock.exe
3. copy to your OEM directory

Done.

I will not be updating the S2U2 OEM until a more stable/final version is released.

I do this as a hobby, I can't spend 2 hours doing an oem just to do it again the next day....sorry...

understandable!! thanks for the instructions.

[xd1936]

Is there an OEM that I'm missing that does Mortscript 4.1?

http://www.sto-helit.de/index.php?mo...n=view&menu=29

The CAB doesn't have a _setup.xml, so I'll try to put one together by hand

[xd1936]

Alright, I have a TEST VERSION (READ: BETA) of what I came up with...
Mortscript 4.1

Download and put the folder that's zipped up in the USER_OEM of the Kitchen

I'll be testing as well... Lemme know if there's any problems. I'm kinda iffy about the Registry changes I had to make, so feedback please!

-Link Removed; files not assosiating correctly-

[Vancer]

Hey rstoyguy,

How's it going? Quick question...

When I make an OEM with OEM Package Creator I notice that many of the files have 000- in front of them. and this is represented in the initflashes.txt as well. Then when I look at the OEMs from the PPCGeeks_OEM.rar, none of these OEMs have the 000- in them. Do you know if they just went in and removed the 000- from the file names and the associated syntax in the initflashes files? Or maybe they were created a different way or created with a different version of OEM Package Creator?

When I first noticed this difference b/t the PPCGeeks OEMs and the ones I created it made me hesitant to use mine and think I was doing something wrong.

Thanks,

Vancer

[xd1936]

Hmm... That OEM kinda worked. The .mscr files had the right icon, but I got the 'not a trusted certificate' error... I'll try again later, unless someone else has an already-built one