Related
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.
Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.
I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.
Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?
A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )
just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.
Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...
About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...
I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.
I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..
It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?
CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
You may want to have a look at ababrekars SYS and XIP porting guide in Elf section....
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
2. Just replace the wince.nls version in the SYS\WINCENLS_WWE with the CHS one you have.
3. Modify all the MUI files and registry as to point to your Language of choice.
4. The OS.NB is needed as the shell/container for your new cooked ROM because it's the requirement for using the Tadzio's tools. So, leave it as is.
5. Cook the ROM.
At least that what I did when doing my Hermes version long before.
Cyphol.
ruffruff said:
Hi every gurus and chefs,
Thanks to creators of kitchens and tools, i have had so much fun in cooking my own rom. Thank you so much.
Recently, i tried to convert the 1.93.456.2 WWE ROM to CHS. I have managed to transform 99% of the ROM into CHS. but there is only one problem. When creating the rom using the diamond kitchen or kaiser kitchen, at the ending part, it will fall back to use os.nb within the ROM\ folder.
From my understanding, the OS.NB file is an extracted OS from the original WWE ROM thus, the boot.hv, boot.rgu and wince.nls is still the WWE version. how do I replace these files?
Another question would be, when dumping the official rom, the dump_XIP folder is created. what is the use of this folder? if i make changes to the folder, how to i merge them into a usable part for cooking?
i have did a lot of reading on XIP porting, big storage rom cooking and etc. i just can't seems to locate one which explains how to replace files in os.nb or merging the XIP folder to usable part.
Can any kind soul please kindly advise?
Thanks you so much!
Click to expand...
Click to collapse
please correct me if i was wrong..
afaik, XIP part is the same for every language,
also in the end part of the building, you need os.nb only as a "template" to rebuild the new one... it wasn't really use the content inside...
normally, you need to copy all content in the dump_xip to the ROM\XIP directory...
to learn about the process of diamond kitchen (which is based on kaiser kitchen so i assume the tools are the same), i think you better use the kaiser ROM, and try to dump it.. and see what directories and files are generated...
in kaiser kitchen, to rebuild the rom you need 3 dirs, OEM, SYS, and ROM\XIP
cyphol said:
Hi,
1. You don't have to replace/port XIP from the ROM of the same device. Only do this if you want to port other devices' ROMs such as Kaiser to Hermes, Diamond to Kaiser, Raphael to Diamond etc. It will boot.
Click to expand...
Click to collapse
He would need to if he wants a different OS build. Or am I wrong?
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
of course....
pkoper said:
He would need to if he wants a different OS build. Or am I wrong?
Click to expand...
Click to collapse
Yes, that's right for the reason. If that's the only reason, why don't you replace the core.dll
thank you everyone for your advise.
looks like i just need more reading.
thank you cyphol, pkoper and teamee for your kind advice.
I have replace the SYS\wincenls_WWE folder with SYS\WINCENLS_0804. i believe this might be one of the problems. i will try replacing just the wince.nls within the folder instead of replacing the entire folder.
files which i have modified includes the boot.hv, user.hv, default.hv, boot.rgu, a bunch of other rgu as well. i might have missed out a few others. so i will check again.
thanks everyone for your kind advice. if there is any other suggestions or points to take note of, please kindly let me know.
your guys rocks! XDA rocks!
Hello every1
I've tried to port 20755 xip from xip.bin (20755). I think I've done every thing allright. Because I can read OS CE 5.2.20755 in About. But, with this new XIP I can not send or transfer files. I can't select this option with File Explorer.
I've came back to my last ROM folder (20273) and It works properly.
I use Bepe's extended kitchen. there are \XIP folder, OS.nb.payload, out.bin (I think it's XIP) and another file, *.bin (I don't remember now), into \ROM folder.
What am I doing bad ?
Thanks in advance.
Best regards !!!
Did you port any of the modules or files that belong to the OEM packages? This can cause all sorts of issues.
mpattman said:
Did you port any of the modules or files that belong to the OEM packages? This can cause all sorts of issues.
Click to expand...
Click to collapse
Thanks.
Yes, I've ported everything. I'll try again without porting that folder.
Regards !
EDIT: Everything has gone properly. THX.
Hi all, i have complety translated, .rgu / .dsm / .bmp / dpi 96 to 192 / 0409 to 0406.
from 20924.
But, when i cook it, and flash my phone, it dosen't book. I can see the version, but i can't not come to wm6 startscreen.
Do some1 know what it could be ?
Could some1 please look at my files maybe :/?
http://rapidshare.com/files/161467646/sys.rar
Bump, no one want to look in it and help me ??
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
NotATreoFan said:
Search for and download a tool called G'reloc.
A common issue with ported OS builds is that they fail to boot due to improperly coded/placed files. G'reloc will fix this for you. Just run it right before cooking, and then once compiled and flashed, your ROM should boot fine.
*You will need to find the correct codes for G'reloc and a Diamond ROM. I have only used this tool on the Kaiser, so I cannot tell you what they are.
Click to expand...
Click to collapse
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
danny_and_2 said:
As I can see, my package builder+buildos run it before it is done.
But anyway, could allways try it ), what shall i put in ? Some1 knows it ?
Click to expand...
Click to collapse
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
NotATreoFan said:
I tried using a newer BuildOS for the Kaiser that included G'reloc, and it never worked properly. I would run G'reloc on it's own, and then uncheck the box to run it as part of BuildOS.
If those values are auto filled in for you, then give it a shot with them. Worst case, the phone still doesn't boot.
Click to expand...
Click to collapse
Yes they just came automatic, so. Yes i will try that one, will report back if it dosen't
--- Edit ---
I couldn't i get an I/O error 105. ? Some1 knows what this it ?
--
Run-time error 105: File not open for output.
This error occurs if you try to use standard input and output functions
like Readln and Writeln without the Uses WinCRT; statement.
To correct this error, add Uses WinCRT; to your program.
How exactly did you translate the 96.DPI files?
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Noonski said:
How exactly did you translate the 96.DPI files?
Click to expand...
Click to collapse
I have copyed the files from the diamond (192) to it.
Noonski said:
Safe yourself the headaches and use the Diamond 1.96 as a base.
That would give you all the SYS 192 dpi files you need.
Click to expand...
Click to collapse
I also would, but it ain't released on danish
Noonski said:
Are you making the ROM true 0406?
Or just translating or renaming the 0409.mui files?
Click to expand...
Click to collapse
I have copied the danish 0406.mui files, and changed it in every .rgu and .dsm file.
Bump, bump, bump.
Must be some1 out there, there can help me find my mistake ;/
danny_and_2 said:
Must be some1 out there, there can help me find my mistake ;/
Click to expand...
Click to collapse
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
if you have Greloc error replace files mentioned in error
try this.
ask if you need help
Click to expand...
Click to collapse
Hi there.
Thanks for you guide, I'll try it right away.
And I will say if I run into a problem.
xboxmod said:
HI
For port this os build i've made this:
first try to port only the xip
Delete folder from your old working kitchen:
MSXIPKernel
MSXIPKernelLTK
AND OEMXIPKernel if exist
Click to expand...
Click to collapse
They aren't in my kitchen with this rom. Don't know why.
xboxmod said:
Delete your old OS.NB in ROM folder of your kitchen
Now you need to Extract OS.NB From a diamond ROM 20924 protected or not !
(My rom for exemple)
take the 20924 OS.NB in your ROM folder
then just cook with your old sys and oem folder without the folder mentioned on top. flash & verify xip version.
Click to expand...
Click to collapse
It boot, and it works. Haven't looked so much on the rom, just verify'ed the xip version.
xboxmod said:
if this work ,change your sys with the 20924 you have
but keep some files from your old working sys
if i have a good memory i've keep this:
.ROM folder
.VM folder
.Metadata folder
.hd.dll folder
.osaxst0.dll folder
.gwes.exe folder
possible some other files...
Click to expand...
Click to collapse
I have tried what you said, but the mobile just won't boot, and i don't know why ! /:
I think i need some more files?
xboxmod said:
if you have Greloc error replace files mentioned in error
Click to expand...
Click to collapse
I don't have that.
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
TekTonik said:
have a look here :
http://forum.xda-developers.com:80/showthread.php?t=379598
Click to expand...
Click to collapse
Hi there, trust me. I have looked the thread many times ..
Anyway, i got an update.
I have get the phone to boot, with the orginal OS & OSFILES.. Now i just need to find what files i need to have, to get it boot..
But i still got a bug, when it boot, touchflo3d won't start, it just skips. ?
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
ababrekar said:
The problem you are facing might be (99%) because of improper XIP porting. Just for suggestion, go through my XIP porting guide (in my signature) and try again with a working 20924 XIP (if you cant find one then I'll up the xip.bin from which I ported and am using)
Click to expand...
Click to collapse
Hi there.
I finally got it to work (more or less), someone, know the files i have to keep in the shell ?, it wont lunch flo3d. :S ?
Some1 know why ?
ababrekar said:
Using original OS folder would not qualify as SYS porting If you check the SYS build no, you will see the original no and not the ported build
Click to expand...
Click to collapse
But i needed to find out, witch folder there was stopping me from booting, and that was my answer , now i just need to find out what files i have to keep, and there are only 587 files..
I will report back soon
anything new about an issue, I try to port build 20757 from BlackStone and I'm facing the same problem too : replacing SYS only doesn't boot
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
What about the easiest way?
Take a look here:
http://forum.xda-developers.com/showthread.php?t=452779
Ervius's tool is to port XIP
To port SYS is the easiest porting 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!
ababrekar said:
Ervius's tool is to port XIP
To port SYS is the easiest porting 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!
Click to expand...
Click to collapse
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
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
hi
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.
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 :-(
if the problem is running poutlook, please check if you have custsat.dll in your rom.
if removed, poutlook won't run.
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.
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 !
Bxsteez said:
a tiny little corner in the top left hand corner
Click to expand...
Click to collapse
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
Vic5870 said:
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 !
Click to expand...
Click to collapse
In fact, you can take the rest of the OS folder too, with the exception of the rgu and ossvcs
omaga said:
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
Click to expand...
Click to collapse
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
Bxsteez said:
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
Click to expand...
Click to collapse
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
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?
Bxsteez said:
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?
Click to expand...
Click to collapse
Maybe you should post in the X-Peria ROM dev. forum!?
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?
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.
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?
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.