Related
Hi all,
I am trying to port the mediaplus from AtomLife ROMs which has the second version of mediaplus with icons in circle.
I was successfull in extracting the imgfs.bin but there is onemore file ExROM.img which is not giving up.
I Tried
1. winimage
2. extended drive creator
3. scooter kitchen tools
but i am not able to look into the contents, it has the required _QHiddenPartition directory which has all the theme and image files for FMRadio/Mediaplus and Equaliser.
can anybody help me .
regards
Shreedhara
Mediaplus is very tricky..the images are in Ext ROM..but the links to executables are somewhere from the XIP section..any way keep working
Well
I don't think u understand my problem.
I was able to run the Mediaplus(v1.0) app on my Eten M700 earlier when I had WM5 on my eten.
But after I changed it to WM6, I want something new and hence I am trying to get the Atom Life Mediaplus (v2.0), which is better looking than the earlier one.
But SInce the latest ROM's from O2 have differenct format
It contains
lot of asm.mbss files (Motherboard assembly ) and FLASH.DIO and ExROM.img
with XLDR.nb and EBoot.nb0 files also.
But that Extended rom is hardnut to crack, it does not open at all for any tools we have here.
That'swhy I asked for help, so that I can extract it.
Here is the link of the new HTC camera from raphael (build 32018) OEM packages:
http://rapidshare.com/files/147099153/Raphael_CAMERA.rar
this is the cab:
http://forum.xda-developers.com/attachment.php?attachmentid=117220&d=1222712363
Works with- Kaiser, Polaris (confirmed)
Other devices are being tested.
but it DONT works in my Diamond
the post say that work only in cook rom
(This OEM files are for those who cook roms. Camera doesnt work on simply coping these files in windows folder. if u hav done that mistake then delete the 'camera.exe' in your windows folder with file explorer to get your camera working again.)
Can samebody help Diamond users???
I have tried that too, but dont work for me. some error txt about low memory came up on screen!
There are 3 extra files in this folder voColorConversion.dll, voJPEGDec.dll, voJPEGEnc.dll is this files belong to OEMDriver folder or....in the pacage folder?
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.
Can anyone give me some insight on this problem. I am porting 21159 to the Treo 700wx, and it keeps stopping on the WM 6.5 startup screen. I can turn off/on the display, but it never progress onto screen calibration or anything else.
I have replaced the gwes.exe file in order to get the rom to boot, as well as wincenls_wwe, but it doesn't seem to make any difference. At the moment, I'm stumped. Any help would be greatly appreciated.
86 views so far, and no replies. That can't be good...
I think I might need a gwes.exe for 240x240 screen on a 211xx build. Does anyone have one?
Any progress?
untarded said:
Any progress?
Click to expand...
Click to collapse
Nope. No responses. I did find a 6.5 rom for the treo 750, but they removed all of the dsm files, so I can't port it. I have to try to manual piece it back together.
This is really a good build, but believe me that stabilniejszy is 21,109, this is fast
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.
!Aman! said:
not necessarily. i had the same troubles too and i got it working after including HTC's TouchFLO OEM package and ConfettiCore package (which i was deleting before) in SYS.
Click to expand...
Click to collapse
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere
cruzzmz said:
both of the above is not in the rom? could you share the link of ur successful SYS folder somewhere
Click to expand...
Click to collapse
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.
!Aman! said:
i think all of the SYS 21159 floating around have ConfettiCore package inside, so u can try any. i thought it was useless, so deleted it. but it lead to the problem mentioned above. in addition to that, i had to use TOuchFLO OEM package also of my device which i deleted coz i wanted to use M$ default touchflo.
Click to expand...
Click to collapse
sad to say dude of of the rom now have protection on it including urs so i cant use package tool to make it to SYS folder ....
cruzzmz said:
stuck at boot screen usually because of
1. wrong xip porting
2. wrong wince_nls
that is what i am facing now also
Click to expand...
Click to collapse
Already tried this. Both are correct. It's not hangs on the boot screen. It's hanging on the welcome screen. Well it's not exactly hanging. I can still power it on and off. I still get the press the middle button to unlock thing. I can turn the radio on and off. It just never moves on from the welcome screen.
I pieced some of the 750 rom into my SYS. I noticed they had modified some of the .cpr files for 240x240, so I included those as well. Flashing now, we'll see what happens.
Update: Same problem. It stops at the welcome screen.
Tryed using my existing .rom folder, and shell32.dll and shellres.dll. Still no luck.
same problem since 21xxx builds with welcome-center
I'am a german rom-cooker for glofiish m800-device.
i work since over one week on windows mobile 6.5.
I'am not success today.
The Problem is:
- No Calibration (Welcome.lnk) is launched by initflashfiles.dat
but in the file the entry is included
the biggest problem, becouse the device is unusable
- The Startmenu is wrong, only a white screen open. (very small) no solution with gwes.exe from wm61 20924 sys.
- the grey taskbar on the today-screen
i have replaced gwes.exe from working windows mobile 6.1 sys 20924
i have changed shell.exe and shellres32.dll in shell-directory from sys
to change user.hv and default.hv from metadata
to delete user.hv and default.hv from metadata
to replace folder for shell
to replace folder for phone
to replace folder for redist.
to include wince.nls in sys-folder too
The wince.nls is in my xip (rom-directory) (my kitchen need the extracted version of xip.bin)
I don't know what the problem is.
I have ported XIP 21159 from Diamond, from TouchPro, from glofiish m700, from glofiish m500 and much more. I'am sure i use actually an VGA-XIP (from Diamond, 1.post in this Thread)
but i don't know which version this is (21139 or 21159 ???)
all the same problem.
i use my kitchen based on windows mobile 6.1 and included the g'reloc.exe from WM65 Kitchen (forwarder) and the wmreloc.exe.
since my kitchen is ready for wm65. all works great by compiling the new temp.dat (the flash-file for glofiish devices)
I read i must use the same sources for XIP and SYS !!!
But what are the same Sources ???
Can anyone send me an working 21159 XIP for VGA ???
When i try to port "Diamond Payload 21159" from XDA-Developers with Xipport and Xipporterex the xip is ok, but when i insert in my kitchen, the prog "buildos" stop their working, nothing happens in command-window.
So i'am very pleasent when you can send me an working source 21159 SYS for VGA and an working Source 21159 XIP for VGA...
i have big problem with windows mobile 6.5
acutally i try windows mobile 6.1 21114 there are the same problem.
the problem is, after os-logo no calibration screen come.
big problems to call "welcome.lnk"
only whenn i insert in wrong path to welcome.lnk the today-screen display ???
do you know this bug ???
here is the rgu of the welcome-center, i think it's not compatible with m800 ???
is this welcome-center new in the 21xxx-builds ???
over one week and no succed with wm65.
at the moment the same problems with wm61 21115
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Rai\:M SWelcomeCenter]
"0"="MSWelcomeCenter" ; class name
"1"="wcsan.exe" ; exe to launch
"2"=dword:1 ; perf hint (RAI_PERF_*)
"3"=dword:0 ; app type (?)
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome\CWelco meCenter]
"Disabled"=dword:0
[HKEY_CLASSES_ROOT\.wcml]
@="wcmlfile"
"Content Type"="text/html"
[HKEY_CLASSES_ROOT\wcmlfile\DefaultIcon]
@="browsres.dll,-6703"
[HKEY_CLASSES_ROOT\wcmlfile\Shell\Open\Command]
@="iexplore.exe file:%1"
[HKEY_CLASSES_ROOT\welcomecenterapp\DefaultIcon]
@="coreres.dll,-20797"
[HKEY_CLASSES_ROOT\welcomecenterapp\SelectIcon]
@="coreres.dll,-20798"
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Redirect"=":MSWELCOMECENTER"
[HKEY_LOCAL_MACHINE\System\WelcomeCenter]
"CmdLine"=""
[HKEY_LOCAL_MACHINE\ControlPanel\WelcomeCenter]
"Group"=dword:1
hope you can help...
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Thanks
Everal
everal said:
I'am at the end...
I think WM'Reloc is not compatible with my device ???
Click to expand...
Click to collapse
I had issues with it as well. I had to go back to using g'reloc.
hey guys any solution to this problem? I've been facing it on my Samsung i780.. damn this won't move past the Windows mobile logo.. yet it plays the welcome screen sound.. what a shame..
chef raven,
not trying to hijack your thread but can you please answer my PM.
i've been waiting for weeks now.
thanks
im new to this cooking thing and wanted to make sure of somethings.
1. what exactly goes into the SYS folder? i read somewhere on the forums that the only folders needed in this folder are the .ROM, .VM, and the shell folder with the shell32 folder is all that is needed in there. is this true.
2. does the my programs and games i want to cook into the rom go in the OEM folder after i use the cab2oem program? oh yeah and where do i put the cab files that dont want to seem to convert?
3. what would i need to make my rom a RBSC rom and how do i get rid of the ULD partition?
4. where would i put the files in for like the different shells so that it starts up on these shells after it is flashed like for example: the iphone shell or http://forum.xda-developers.com/showthread.php?t=354866&highlight=SCLPF
I think thats about it. Oh and before you start scolding me and say "its called a search box" or "maybe you should look"...well just know that i have and cant find anything. I have been seeking these answers for about three days now.
Many answers to wich i know the meaning and knowledge...
1.-In sys folder goes all the OS Base...
What do i mean by this? well it depends on the kitchen you use... if ou can see on the kitchen of Josh its a modified kitchen betwen ervius visual and bepes platform rebuilder so not so much folders in it! the sys hs two folders more... 0409 and common... in this original kitchens you can do many lang OS or many devices OS, so thats why there is more folders than OLD School way... so there are so much folders in it like the office... the bronzeres the manilla 2d and many more...
in old school the OEM folders becomes sys when dump again the rom so imagine how many things must be on SYS!!!
the .rom .vm and shell and shell 32 is a way to port the sys... but is not ported well with this method. and yes that folders must be on SYS anyways.
2.- Yes exactly the programs you wish to add to the rom must be on OEM folder... and the cabs that dont wants to be converted into OEM must be in OEMOPERATORS to install them on first UC... you must to edit the config file like the SD config way...
3.-RBSC is related to the os.nb.payload... so get a dumped rom with RBSC and get it's os.nb.payload... and add it where this file must be... On ROM folder of the kitchen, to get rid of changing the ULD partition many people is working on it... so the modules can be added there to have more storage... wel its not so much i thing 3 MB of storage not RAM.
4.- Well dude that link is not a shell... but what do you mean by "SHELL"?
This is a program that emulates... the htc cube... that was an app too so it is not a shel but if you said you want a new theme... home plugin... or UI use them as it is a programm add it via OEM or cab thats all.
thank man that was really helpful that cleared my everyting up