[Q] Help porting SYS to new rom.

[anubis23]

Need help porting sys folder..

I've successfully ported XIP to 20757 and now i've been trying to port the sys build folder 20757 and up, from multiple roms, such as the xperia x1 roms, the blackstone roms, and other's from the site.

But all of my attempts has fail, so was hoping someone could tell me what im doing wrong.

First sys attempt i tried was;
How to port a SYS folder
Open your old SYS folder and copy the .VM and WinCENLS_WWE folders into your new SYS folder
Go to your old SYS\Shell and copy shell32.exe and shellres.dll into your new SYS\Shell

found here http://forum.xda-developers.com/showthread.php?t=389772

Second i tired, to port it from a thread on the kaiser forum, http://forum.xda-developers.com/showthread.php?t=437264

and third i tried this following guide from the elf forms, http://forum.xda-developers.com/showthread.php?t=379598

so for short

1. made 1 folder for old sys, and 1 for new system with the build number

2. copy .vm .rom WinCENLS_WWE, shell/shellresand shell/shell32 folder, with my already ported XIP

3. swap out the res folder like 800 and 640 ones for the diamond, (where ever it is needed to port the rom)

4. then ran g'reloc

so yeah finally when i tried all this, form the guide, it doesnt work

[seatone]

What about the easiest way?:D
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779

[Ameet]

Ervius's tool is to port XIP ;)

To port SYS is the easiest porting :D Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required

Simple! :D

[omaga]

Ervius's tool is to port XIP ;)

To port SYS is the easiest porting :D Simply run Greloc on old SYS and note all the values. Then run Greloc on new SYS and change the values as per old SYS. No replacement needed, no swapping required

Simple! :D

I thought that to;) but every time i tried to port the Blacstone sys and Greloc
the rom doesnt boot, I have tried many times and allways the same result.
havent test for a wile, the xip port I get whit your exellent manual xip port but not the sys, so now I have a rom os 20757 Build 19665

[TekTonik]

have you tried replacing all except the Metadata folder ?

for your XIP which is the base used 1.93, 1.96, 1.97 ?

I have tried the xiportereex tool but some modules are missing, so I tryied to add it by myself, it boot but sometime touch screen doesn't responde at first tap, very strange, I have also a pb with default ringtone witch is not the one it should be by mxipupdate

[anubis23]

thank you for your reply everyone but several attempts trying you methods but none has worked ; ;

UPDATE; i give up trying to port sys build, thnx for you help everyone.

[Nixeus]

Same problem for me, if I try all these method in order to port the sys 20764 ( blackstone) to me ELF, the phone don't boot :-(

[lufeig]

if the problem is running poutlook, please check if you have custsat.dll in your rom.

if removed, poutlook won't run.

[Bxsteez]

This is the sam exact problem i'm running into. I can't just not port the SYS because the XIP i'm using opens the windows in a tiny little corner in the top left hand corner. Has anyone figured out how to actually port the SYS since none of the tutorials seem to work.

[Vic5870]

Hi All,

Try this:

1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook

Good luck !

[omaga]

a tiny little corner in the top left hand corner

take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick :) gwes.exe u find in Os folder

[adwinp]

Hi All,

Try this:

1. Copy all modules and dsm ONLY from these few folders (BaseApps, Shell, Phone, PhoneRedist and Redist) from new SYS to your old SYS folder. No need copy ***_DPI_*** (images), ***_0409 / ***_0804 (language files) and the rgu because they never change even how high the build number goes
2. Copy gwes.exe from new build OS folder to your OS folder (if you don't want to get small little window on the top left corner)
3. g'reloc
4. Cook

Good luck !


In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs

[Bxsteez]

take gwes.exe from a vga rom and replace that... you have same problem I had the sys was from a no vga rom and when I took the gwes from my stock rom it make the trick :) gwes.exe u find in Os folder

I had this problem when i was porting the Touch HD ROM to the Xperia X1 and thats wvga to wvga. I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there

[omaga]

I honestly thought porting the SYS would be the easy part but the SYS is why my phone doesn't boot up it just sits there

Ye I thought that sys is the easy part;) I got so many sys port that the rom doesnt boot. Now i get 2 in a row 21109 and 21014 sudden and If I remember right I have allways done the same way:rolleyes:

[Bxsteez]

Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?

[adwinp]

Thats the one that i'm working on now. I'm trying to port the 21109 from the touch pro to the xperia but i can't get it to work. Can u give me any tips?


Maybe you should post in the X-Peria ROM dev. forum!?

[Bxsteez]

I have but as we all know the xperia doesn't get as much attention as to the full blown htc devices. I figure that the porting method should be about the same with the exception of changing some things based on resolution. Am i wrong?

[davideuck]

Have you deleted some folders from official HD SYS??
If yes, notice that the rom doesn't boot without SqlCeMobile and SqlCeMobile_Lang_0409 folders. I'm speaking from my experience with HD.
And I remember I've ported these official builds to Toshiba G900 without problems. Then, make attention to these things too.

And control if into your original SYS, you have some different folders in comparison to the new SYS.

Another thing, Ervius xipporterex rev-35, deletes some things from xip, but it works perfect in that way. The only thing you have to notice, is that it deletes WinCENLS_WWE from xip, then you have to add it into SYS folder.

@Bxsteez,
chek your 21109 SYS, and change mxip_system.vol(into Shell), with your original and see if mxipcold_wpc_2.provxml is into Base_DPI_192 folder, if not, copy your original one there. Change MobileCalculator.exe into baseapps folder too.

[Bxsteez]

Just gave this a shot and nothing works again.... I can't even port the XIP and use the standard SYS and get it to boot. I wonder if i'm using a some corrupted build of 21109. Can someone point me in the direction of where to get OS CE 21109 and 21109 build?

[davideuck]

Search on ppcgeeks the calkulins kitchen for diamond, then extract the xip from os.nb.payload and use that to port, worked for me with ervius xipporterex-35.
And make those changes into SYS folder, they are needed to boot properly.

[Bxsteez]

With your help i was finally able to port the sys but xip i got from calkulins kitchen isn't 5.2.21109 but the build is correct. The OS that its showing is 5.2.0

[davideuck]

With your help i was finally able to port the sys but xip i got from calkulins kitchen isn't 5.2.21109 but the build is correct. The OS that its showing is 5.2.0


Strange, on mine was right, 5.2.21109. Anyway, I remember that into the xip there's a registry key, AKU="calkulins", and the same into SYS, I don't remember the exact folder, it could be Shell. I've deleted this registry key into the xip before porting it, and I've changed the one into SYS with ".5.0.0".

In any case, if you want a suggestion, try 21014 build too, in my opinion it's a little faster thatn 21109(this build seem to be hexedited), and much stable.;)
You can find it here:
http://forum.xda-developers.com/showthread.php?t=467460

[Bxsteez]

I Just tried this XIP and it gives the same thing it shows the OS to be 5.2.0. Is it possible that i'm using xipporterex wrong? I'm using version 32 cause 35 always crashes on me


*****EDIT****
I found what that issue was. Apparently when you delete cachefilt, mencfilt, and encfilt then it always shows up as 5.2.0. Once i unchecked deleting those the build comes up correctly. But as usual with the solving of one issue i run across 5 more :( I'm wondering what files are needed from the donor SYS. Once i tried to copy everything over from the hermes 21014 i have no icons and nothing looks correctly. I'm assuming this is because i'm going from QVGA to WVGA. I'm wondering if there is a list of actually needs to be ported over for the build to work.

[davideuck]

Obviusly you have to leave all the folders resolution dependant. All the folders with "DPI_192" or "DPI_192_RESH_480_RESV_800" are resolution dependant. Then leave the original folders of these.;)

[Bxsteez]

Obviusly you have to leave all the folders resolution dependant. All the folders with "DPI_192" or "DPI_192_RESH_480_RESV_800" are resolution dependant. Then leave the original folders of these.;)

Yea i figured that.. I still can't get a successful port. I don't know what i'm doing wrong but none of these guides seem to be remotely correct. I can't get a boot again unless i use my original SYS.

[adwinp]

I Just tried this XIP and it gives the same thing it shows the OS to be 5.2.0. Is it possible that i'm using xipporterex wrong? I'm using version 32 cause 35 always crashes on me


*****EDIT****
I found what that issue was. Apparently when you delete cachefilt, mencfilt, and encfilt then it always shows up as 5.2.0. Once i unchecked deleting those the build comes up correctly. But as usual with the solving of one issue i run across 5 more :( I'm wondering what files are needed from the donor SYS. Once i tried to copy everything over from the hermes 21014 i have no icons and nothing looks correctly. I'm assuming this is because i'm going from QVGA to WVGA. I'm wondering if there is a list of actually needs to be ported over for the build to work.


I recommend you use the new Metadata, but with your old default.hv and user.hv

Apart from that, you might post your porting steps exactly like you're proceeding, and we'll see where you're going wrong.

[Bxsteez]

Thats a good idea. To port the SYS here are the steps i'm going through.

What i'm using:
Build 21109 (http://forum.ppcgeeks.com/showthread.php?p=625196)
Stock UK Xperia X1 ROM

Steps:
1. Copy all resolution based folders from stock SYS to new SYS folder
2. Copy mxip_system.vol from stock SYS->Shell to new SYS->Shell
3. Make sure mxipcold_wpc_2.provxml is in new SYS->Base_DPI_192 folder if not i copy it from stock SYS
4. Copy WinCENLS_WWE from new XIP to new SYS folder
5. BuildOS
6. Use Kitchen to build os-new.nb
7. Build to ruu_signed.nbh and flash

Am i not doing something or doing something wrong? I'm really starting to think its this 21109 Build i was using.

[Bxsteez]

I hope someone can explain this one to me. I dumped a stock rom and ported the sys and thats it yet my OS build changed????????? I thought that couldn't change without porting the XIP. This makes no sense to me. Can someone explain how this could be possible? Did it not port the XIP and this is just some file that is representing that it is ported?

[adwinp]

I hope someone can explain this one to me. I dumped a stock rom and ported the sys and thats it yet my OS build changed????????? I thought that couldn't change without porting the XIP. This makes no sense to me. Can someone explain how this could be possible? Did it not port the XIP and this is just some file that is representing that it is ported?


The aforementioned happens when porting BaseApps/Shell

[Bxsteez]

Ahh i c thanks... So the XIP was not ported then. Is that correct?

[davideuck]

When you read the info on your pda you have two indications.
The first, for example "CE OS 5.2.21014" is XIP dependent. The second "(Build 21014.1.6.0)" is SYS dependent.
Then, looking at these info, you can check what you have done.

[Bxsteez]

When you read the info on your pda you have two indications.
The first, for example "CE OS 5.2.21014" is XIP dependent. The second "(Build 21014.1.6.0)" is SYS dependent.
Then, looking at these info, you can check what you have done.

Yea thats what i've read thats why i thought it was strange when i ported over the SYS it changed both of these. Thats why i'm confused.

[Bxsteez]

Has anyone ever had an issue with the config_AP.txt? Ever since i ported this new sys the cabs that i have in the file don't seem to be installing with the exception of one. Does anyone have any idea what would cause this?

[davideuck]

Has anyone ever had an issue with the config_AP.txt? Ever since i ported this new sys the cabs that i have in the file don't seem to be installing with the exception of one. Does anyone have any idea what would cause this?

Something similar appened when I had a bad mxip_system.vol into shell.
Other problem could be releted to autorun.exe or checkautorun.exe.
You can see if the checkautorun posted here(post #98) works better:

http://forum.xda-developers.com/showthread.php?t=474406&page=10

[Bxsteez]

Something similar appened when I had a bad mxip_system.vol into shell.
Other problem could be releted to autorun.exe or checkautorun.exe.
You can see if the checkautorun posted here(post #98) works better:

http://forum.xda-developers.com/showthread.php?t=474406&page=10

I found out what the issue was. You can't install uncertified apps with config_AP.txt unless you disable the security warning so i just made a registry tweak that disabled it and then all the apps installed ok.

I finally released my first rom and then my second. Thanks guys!!!

[davideuck]

I found out what the issue was. You can't install uncertified apps with config_AP.txt unless you disable the security warning so i just made a registry tweak that disabled it and then all the apps installed ok.

I finally released my first rom and then my second. Thanks guys!!!

Wow!:D
Very good!

[Bxsteez]

Back to the drawing board. I have no idea how to get the SYS to port again. I did the same thing i did before and again it will not boot. I wish there was some sort of tutorial for porting the SYS that actually works. Everything says copy the entire sys folder and use greloc but that does not work.

[qtotter]

Back to the drawing board. I have no idea how to get the SYS to port again. I did the same thing i did before and again it will not boot. I wish there was some sort of tutorial for porting the SYS that actually works. Everything says copy the entire sys folder and use greloc but that does not work.

not a solution, but i used sys and xip in vic's rom as a 21014 cooking base since i had the same issue in porting sys from qvga sys for diamond. he does not apply protection to his rom so that people can use it for cooking.

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

he has successfully ported 21014 sys for diamond, and obviously, he should know how to resolve your issue.

qt

[Bxsteez]

Thats what makes this so sad. I did it twice already lol... I need to write my own guide cause after about 2 weeks i can't do it again.

[qtotter]

Thats what makes this so sad. I did it twice already lol... I need to write my own guide cause after about 2 weeks i can't do it again.

thought i followed his advice in post #10, but i took os, metadata and .rom as well as my old habit without thinking. that might have been the cause. i will try his method again when a new build comes around, but i will stick with his sys until then. tired of the cook-burn-test process...

[totalcmdext]

Hello

I would like to ask if the .VM, Shell32.exe and Shellres.dll folder must be always from the old SYS folder and copy to the new(version which need to port to old) SYS folder?

[anubis23]

.vm yes but shell32 files no, i think those pertain to the vga or qvga stuff, depends what type of display your phone has.