PDA

View Full Version : Porting Sys & Xip From Diamond/touch Pro Question


ryncppr
18th July 2008, 08:50 PM
OK, so burn me if you'd like but for the past year or so everyone has been porting the Kaiser SYS and XIP to their devices... but with the recent release of the Diamond, Xperia and TouchPro builds it seems like us Kaiser users want to Port too!!!! So here is my problem

I am having issues right now for some reason as I am \porting the SYS from the Touch DIamond ROm. OS,OSFiles, Shell, .VM, changing the .VM with G'Reloc but for some reason the build # is not changing....WHY I HAVE NO IDEA

In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.

I also have used BuildOS+packageTools4.b3 in order to do a XIP port??? I am clueless. I used to do this no problem but for some reason it is not working now??? :mad:

mbarvian
18th July 2008, 10:40 PM
do drop by to www.ebayfoco.com look through the articles there. With information on anything from getting the you like products,

enough of this bot already, he was in the development and hacking section as well

P1Tater
18th July 2008, 10:56 PM
enough of this bot already, he was in the development and hacking section as well

Not anymore. Banned for spam.

mbarvian
18th July 2008, 11:37 PM
Not anymore. Banned for spam.

thanks, I guess you need a reason to ban :)

dcd1182
19th July 2008, 12:21 AM
In a nutshell I am taking the Touch ROM SYS and replacing only the OS, OSFIles, SHell, .VM folders. THen I am running G'Reloc and entering the proper values. When I cook the rom for some reason it is not changing the build any idea.

why are you only bringing over those parts of SYS? take it all.
oh, and replace *DPI_192* from new source with *DPI_96* from kaiser original.

ryncppr
19th July 2008, 12:24 AM
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....

I'll try once more before I whip my computer across the room

dcd1182
19th July 2008, 12:29 AM
I did that but then the phone wouldn't work???? I dont know whats wrong, I have port other builds no problem but for some reason the new Xperia ROM and TOuch Pro are killing me....

I'll try once more before I whip my computer across the room

if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.

also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.

oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.

i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously :)

ryncppr
19th July 2008, 12:59 AM
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!

The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???

Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?

lennysh
19th July 2008, 12:59 AM
if you do what i said above, then g'reloc with original kaiser values, it should boot.
dont use .vm and .rom from kaiser original, use the new ones from new source but g'reloc will change values.
use original kaiser xip until you get sys working then do your xip.

also if you are using original kaiser xip then wincenls_wwe is in xip and doesnt have to be in imgfs. if you are using a cooked xip it may be missing and would be reason for no boot.

oh and on my device htc switched slot values around at a certain ver, i dont know if this is the case on kaiser. i have to match my new xip with new slot values for g'reloc.
in other words if youre using a kaiser wm61 xip from ROM version 3.00 then feed g'reloc the slot values you found in kaiser ROM version 3.00.

i am speaking from experience with your issue, i ported tons of builds then tried new diamond/xperia/etc and suddenly those didnt work with the method i was using previously :)

I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.

lennysh
19th July 2008, 01:02 AM
WEll all seems to be working now since I ported the whole SYS over... the device is booting fine and the phone is working too!!!

The only problem I have with the port is when the screen boots and gets to the green WM6.1 screen the start icon is in the middle of the screen and the top is blue???

Otherwise it all works fine after the green screen clears the icons are all where they are supposed to be. I didn't mess with this OEM folder where the welcomehead.96.bmp is so thats now confusing?

welcomehead.96 is in sys.

ryncppr
19th July 2008, 01:07 AM
I've ported every new XIP build (Diamond, Raphael, and Xperia) to the Kaiser with "0" problems. All the way up to the newest 20270. Only replacing .VM in SYS.

SO you only ported the .VM? That isn't really a SYS port then is it?

lennysh
19th July 2008, 02:20 AM
SO you only ported the .VM? That isn't really a SYS port then is it?
Lol...

I think you took my statement backwards... Ported the entire SYS, all except the .VM. I have four devices all running Build 20270.

Let me rephrase so it's not twisted, they are all four running CE OS 5.2.20270 (Build 20270.1.3.1)

austinsnyc
19th July 2008, 03:37 AM
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it :( Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.

Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?

ryncppr
19th July 2008, 03:40 AM
I am using the KaiserKitchen to dump my rom. THough I had to rebuild my XIP and separate OEM and SYS for some reason...

I am dying for someone to update the Kitchen for the Kaiser. I am not familar with writting .bat files or I would try.

There is alot of newer programs that need to be implemented into the Kitchen

BuildOS+PackageTool is now 4.b3
HTCTool is newer
PackageTools is newer

I sent a PM to several master chefs but have not heard anything back....

ryncppr
19th July 2008, 03:44 AM
The way that I ported the SYS is as follows....

1st, I dumped both ROMS I want to use. I name the folders accordingly on my C:/ Drive.... KaiserKitchen_BUILD and KaiserKitchen_TOUCHPRO (example)

After dumping both ROMS I make a folder on my desktop and name it NEWSYS. I copy all the files to my NEWSYS folder from the Dumped ROM Folders that I want. PRetty much everything except the .92 files (like stated earlier) after making my NEWSYS the way I want it, I cut my SYS from my KaiserKitchen_BUILD rom to my desktop and replace it with NEWSYS (remember to rename to SYS after copying)

Then I put G'Reloc in the Kitchen folder (same folder as the OEM,XIP,SYS,TOOLS,PACKAGE---main folder) and run it. Since I change the .VM I have to place my numbers back into and press "do it".

The SYS should be fine now.

austinsnyc
19th July 2008, 04:04 AM
Thanks buddy, Maybe dutty and his new crew did something to lock the rom down as his was the one i was trying to dump. I find what the other guy said about just changing out the .VM folder if thats the case porting roms couldn't be an easier!

ryncppr
19th July 2008, 04:06 AM
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...

lennysh
19th July 2008, 04:38 AM
QUESTION since you all are having no issues here, every time I try and dump a diamond rom using the Diamond kitchen RecMode.exe stops working while its dumping the rom so I can't dump it :( Any hints or do I need to set attributes or anything like that? I am using Windows Vista maybe thats the issue here.

Also your just taking the .VM folder from the kaiser and putting it in the diamond and thats it it works fine? or put it in run G'rec?
That depends on what rom your dumping... If it's a stock rom, you should not have this issue...

g77
20th July 2008, 11:56 PM
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...

Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.

Now the same ROM + OEM and switch back to older SYS: everything OK.

Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?

raiisak
21st July 2008, 01:31 AM
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.

Now the same ROM + OEM and switch back to older SYS: everything OK.

Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?

RUU_Diamond_HTC_Europe_1.35.401.3_Radio_Signed_Dia mond_52.26.25.09_0.93.25.26_Ship (http://rapidshare.de/files/39698084/RUU_Diamond_HTC_Europe_1.35.401.3_Radio_Signed_Dia mond_52.26.25.09_0.93.25.26_Ship.exe.html)
+
RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40. 02_1.65.16.25_Ship (http://rapidshare.com/files/117054028/RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40. 02_1.65.16.25_Ship.zip)
Copy .VM from WWE to Diamond
Use G'Reloc (http://forum.xda-developers.com/attachment.php?attachmentid=59282&d=1195845913)

Cook it up!

Boots just fine, no problems whit provxml, shortcuts, activesync, execute or.cabs here.

lennysh
21st July 2008, 02:54 AM
Same happened to me. I've ported SYS from Diamond, replaced all VGA *.192.* package folders with kaiser's QVGA*.96.*, build rom and flash. The result: it boots everything fine except it doesn't execute any .provxml so no shortcuts no activesync no execute .cabs.

Now the same ROM + OEM and switch back to older SYS: everything OK.

Tried to change .vm values and replacing shell.dll+shellres.dll: the same result. Any idea?
Are you saying you cannot install .CAB files? I know that can happen if the mxip_lang.vol file is missing. Make sure that file is either in you oem/sys or xip.

scotchua
21st July 2008, 03:12 AM
I think i saw this same discussion on another site...now where was it???

schizo
21st July 2008, 03:18 AM
Actually I just want to sit tight and learn from all of you, masters. Excuse me for this, but I can't refrain to comment that this topic is actually more or less the same with Raiisak's. Many has also answered there. Why new threads?

edit: skatdawg beats me in matter of seconds, LoL.

qtotter
28th July 2008, 12:39 PM
I know it seems simple after I flashed my device like 20 times in the last two days.... now I want to figure out another issue about the blue bar with the start icon in the middle on the top of the green WM6.1 screen...

so have you found the cure?

lennysh
28th July 2008, 01:16 PM
so have you found the cure?Try replacing services.exe from an older build. Reply when you've tried this.

qtotter
29th July 2008, 06:56 AM
Try replacing services.exe from an older build. Reply when you've tried this.

it worked!! thanks for the info, lennysh!

qt

ryncppr
30th July 2008, 02:17 PM
Yes it did work to verify the services.exe file was causing the error on the boot screen.....