Can someone post a walkthrough on how to change language on a dumped ROM. (say chinese to WWE)
Thanks
re-flash the ROM....
lostlife said:
re-flash the ROM....
Click to expand...
Click to collapse
LOL; that's not really helping!
iago_00 said:
Can someone post a walkthrough on how to change language on a dumped ROM. (say chinese to WWE)
Thanks
Click to expand...
Click to collapse
You have to replace all language-related files with the proper ones in your language! Search in the SYS folder for *.mui files (mostly modules in a SYS folder) and replace them! But you need to edit the RGU's as well, if they exsisting in that package! DO the same with the OEM folder but here the MUI files are real files and not modules, like in the SYS folder! After that, cook your ROM and try it!
You forgot to mention the lang/mui in the registry.
animelover said:
LOL; that's not really helping!
Click to expand...
Click to collapse
animelover said:
You have to replace all language-related files with the proper ones in your language! Search in the SYS folder for *.mui files (mostly modules in a SYS folder) and replace them! But you need to edit the RGU's as well, if they exsisting in that package! DO the same with the OEM folder but here the MUI files are real files and not modules, like in the SYS folder! After that, cook your ROM and try it!
Click to expand...
Click to collapse
The mui language files are not related to the XIP build are they? I mean I can replace those files with another build's mui files and everything will run fine, or do I have to replace them with a concordant build.
adwinp said:
You forgot to mention the lang/mui in the registry.
Click to expand...
Click to collapse
where do I find that?
iago_00 said:
The mui language files are not related to the XIP build are they? I mean I can replace those files with another build's mui files and everything will run fine, or do I have to replace them with a concordant build.
Click to expand...
Click to collapse
No, MUI files aren't really XIP related but it's better to use MUI files from an official build as near as possible with the desired one!
For an example:
I'm using a 21042 build with MUI files from a 20764 build and all working fine!
iago_00 said:
where do I find that?
Click to expand...
Click to collapse
Normally you'll find the registry files as RGU files inside of each package! You can edit them with Notepad, or what I prefer, EditPad Lite!
animelover said:
No, MUI files aren't really XIP related but it's better to use MUI files from an official build as near as possible with the desired one!
For an example:
I'm using a 21042 build with MUI files from a 20764 build and all working fine!
Normally you'll find the registry files as RGU files inside of each package! You can edit them with Notepad, or what I prefer, EditPad Lite!
Click to expand...
Click to collapse
Thanks, for your prompt reply. will try right away
Good luck with cooking!
anyone tried to do it with a 21042 on a 21500 rom? i want to translate a wwe edition to italian
sakara said:
anyone tried to do it with a 21042 on a 21500 rom? i want to translate a wwe edition to italian
Click to expand...
Click to collapse
It's not a good idea because the changes in MUI files from WM6.1 to WM6.5 may be to huge for a proper translation! It's better to wait for an official ITA Build from HTC in my opinion!
I like this EnergyROM
and I am looking for some way to make the cooked rom support CHT.
I have read the post in this thread.
What you guys are talking is changing the *.mui file with other language version. Am i right?
I don't mind using program in English. English is good to read.
But most of my contact's name, sms, email ...etc are in CHT.
All chinese character became a Rectangle.
If i just want the OS to support CHT, how can i do it?
Thanks!!
Related
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
zohaer21 said:
i had the same problem... then i came up with a briliant solutiion
you know the user.hv and initdata can be edited without any probs..also this version of the rom deploys the ext rom aswell.. so what i did was i edited config.txt and added a cab with the HKLM etc regs that go into default.hv into the dump folder and generated a rom with that cab inside..
and VOILA... now i have a custom rom with all my settings... i figured this way out after hours of frustratingly trying to edit the default.hv
hope this helps
Click to expand...
Click to collapse
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
dont know if this would help you but take a lot here :
www.asukal.jp/hv_rom/hive2.txt
or simply use Make_HV, found it in the development & hacking thread.
First covert the hv file to rgu (which is simply REGEDIT4 Format) then make changes and convert it back.
qooqoo said:
i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
Click to expand...
Click to collapse
This is my little surprise
qooqoo said:
thank u, i have tried ur solution, but there is a big problem, .cab file doesn't support chinese caracter, so edit default.hv is the only way.
Click to expand...
Click to collapse
You don't need a .cab for this. The program that goes through Config.txt can handle XML files with registry settings directly. So, grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want. If I'm not mistaken, it's even available bundled with a Chinese ROM already. There you can edit the .rgu files from which the Registry will be created. This eliminates the need to read any of the .hv files. Worked very well for me! Also, since bepe's kitchen recreates the packet structure of the ROM, it's so much easier to understand which files and registry entries have a dependency or belong together. Highly recommended!
Cheers
Daniel
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
weird suprise
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
Why would that be a surprise? Is there more to this than meets the eye?
dutty said:
weird suprise
Click to expand...
Click to collapse
Indeed, I've been hitting my head against it for some days now...
lvsw said:
This is my little surprise
Click to expand...
Click to collapse
himan，give us a solution plz, it is a so good rom, but i can't add anything i want.
tadzio said:
grab any of the .xml files listed in Config.txt as a template for your own .xml file. Then just add your new .xml file plus a line in Config.txt referencing this new file, and you're all set.
Click to expand...
Click to collapse
thk u but i don't know how to edit a xml file, any suggestion?
tadzio said:
There's another solution which I found much more convenient: use bepe's Rom Kitchen, and import whatever ROM you want.
Click to expand...
Click to collapse
it is for CHT but not for CHS, there is a lot of CHT roms yet, cooked or offcial, but there isn't a official rom in CHS, a just want to convert 0320 vesion to CHS vesion.
I will be watching this thread.
Waiting for good news.
qooqoo said:
i have cooked successfully more than 10 roms, WWE vesion to CHS vesion, they all work fine.
but when i want to cook a new rom based on LVSW 0320 vesion, i failed. i found that the default.hv can't be transfered to txt file, once i edit this file, os can't boot and stick on the SubSplash screen. but user.hv can do that.
sorry for post this new thread but i have posted under lvsw's thread and no one answer me.
can anyone help me plz, i really like this ROM.
thanks in advance.
Click to expand...
Click to collapse
I have the same problem...the LVSW 0313 version was fine...then the new LVSW 0320 won't boot..stopped at the subsplash screen...it is strange that the default.hv is there but doesn't seem to booting the file.
qooqoo said:
thk u but i don't know how to edit a xml file, any suggestion?
Click to expand...
Click to collapse
Any Unicode-capable editor will do. Personally, I use UltraEdit.
Cheers
Daniel
Please don't take offense, but I'm starting to think you got the ROM as it is..."protected" that's why all the customizations are done via AutoRun.exe and xml files.
i found that lvsw 0325 edition can be edit.
qooqoo said:
i found that lvsw 0325 edition can be edit.
Click to expand...
Click to collapse
Yes, 0320 can't be edited. But 0325 could. But you can't use the regular tools..you have to use the "more Storage" tool, then just manually copy the "default.hv" and "user.hv" from the "dump" folder, use the regular tool and covert it to .reg. Then you make modifications to the registry file, convert it back to .hv and copy them back to the "dump" folder..you can add files by just copying files into the "dump" folder..after you are all done with it, just continue with the "more storage" tool to make your new-os.nb
Hello there.
well, i'm trying to cook a new version of my ROM, but i have sawn on Fanman release that there's no RGU files...
Because he seems to have merged all of them in the default.hv.
I've tried, but many keys disappear when flashing it to phone...
Have you got any ideas ?
Thanks
Best regards
What kitchen are you using to cook the rom? I've been using the Core Pro kitchen but noticed that none of the changes I made to the .hv files were being included in the cooked rom so this would explain why none of yours are either. For now stick all the changes into 1 rgu file, will be much easier to insert into the hives once it is working again that way I'd imagine.
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
kulbut0r said:
one or more .rgu, each one under a OEM subfolder, will do the trick...
do not forget their corresponding empty .dsm file !
HTH
Click to expand...
Click to collapse
Is that not what he already has tho? I thought the point of his post was how to get all the rgu files into the hives but since this is not currently possible (as far as I am aware, kitchen dependant of course) he may as well place them all into one rgu file.
yep, all changes are not tooked in the hv files, i wanna have only the hives to gain more spaces...
I'll try again
aje_fr said:
to gain more space...
Click to expand...
Click to collapse
kulbut0r said:
Click to expand...
Click to collapse
No more RGU = More space on ROM
This evening, i tried to copy HV after buildos and before createrom, but nothing more....
And when i looked on the temp folder of kitchen, the hv files are really small and doesn't include the hv files in sys\metadata...
Really strange, it seems that modifications in the hives of sys\metadata are not included in final rom ?!
aje_fr said:
No more RGU = More space on ROM
Click to expand...
Click to collapse
small benefit however !
why not to stay with markquinton's recommendation : place all you updates into one rgu file.
So, i finally make it work but strangely i have more memory but software couldn't start and claim an memory error...
I can't even access to program folder
Anybody don't know why ?!
Thanks
aje_fr this is file FRE mui in Faman Rom and RGU file..!
http://rapidshare.com/files/44793173/MUI_RGU_040C.exe
method :
Dump Faman Rom and Copy All file to Dump Folder.Then it.Run PKT tools make OEM and SYS.Now u have OEM and Sys.In OEM and SYS copy all file FRE lang u need..!
Cheers..!
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
aje_fr said:
Thanks tom, i think i'll already have this files but i'll try with your method.
Thanks again
Bye
Click to expand...
Click to collapse
u online yahoo mesenger ???
i'm online now...!
Has anyone managed to successfully edit the hive files and have the changes included in their built rom? As I've been playing around with this for a while but have as yet still not managed it. I'm getting annoyed with having to set a lot of default settings in rgu files when they could easily be included in the hives from the start.
try it!!!!
no more needs external cab extractor...
(from an idea of:"ArHon" with his: OEM Packages Compiler, that opened my mind about....)
full registry compatible now....
new version 2.2 solved problem with "spaced" folder for remodule!!
bye!
lastest 2.7 version
solved unicode saving iusse for rgu files!
solved bug on "\" folders creation into registry, the good keys were with "\\" not only with "\"
Thanks ervius GREAT AGAIN!!!
i will try, you have save us a lot of work creating OEM Packages.
Here is my little contribution. Added Spanish language to lang.xml.
Thanks again.
can you explain what can it do?
Hello
Thank you very much, this is my contribution french language added to lang.xml.
thanks guys, I added both xml files, and now at 1st post can download yet included francays and spanish language, 2.1 version.
addedd "cab" filter on openfile...
P.S.: the package creator, is able to remodule all files inside only if executed on non "spaced" folder,
example:
c:\documents and settings\... (no GOOD)
c:\_a_b_c_C\kitchen_deV_Trin_19900\ (is GOOD!)
ok???
bye!
yuzanuvole said:
can you explain what can it do?
Click to expand...
Click to collapse
it trasforms cabs into package to insert in kitchen to cook roms...
ervius said:
it trasforms cabs into package to insert in kitchen to cook roms...
Click to expand...
Click to collapse
And it adds even registry keys automatically??(I am not very expert in cooking ROMs!!)
yuzanuvole said:
And it adds even registry keys automatically??(I am not very expert in cooking ROMs!!)
Click to expand...
Click to collapse
yes it do!!!
ervius said:
yes it do!!!
Click to expand...
Click to collapse
Very very great!!!
ervius said:
it trasforms cabs into package to insert in kitchen to cook roms...
Click to expand...
Click to collapse
Is there any posibilities of doing the inverse process, i mean to take and OEM package, and build .CAB file automactly?
I know it is not very usefull for ROM cooking, but i have many OEM Package translated to Spanish and a lot of users like to install LITE ROM and then add .cabs of dessired applications...
I think it will be the perfect complement for this GREAT!!! application.
Very Good Work Ervius, congratulations... you are allways surprising us...
axl79 said:
Is there any posibilities of doing the inverse process, i mean to take and OEM package, and build .CAB file automactly?
I know it is not very usefull for ROM cooking, but i have many OEM Package translated to Spanish and a lot of users like to install LITE ROM and then add .cabs of dessired applications...
I think it will be the perfect complement for this GREAT!!! application.
Very Good Work Ervius, congratulations... you are allways surprising us...
Click to expand...
Click to collapse
if initflashfiles.txt inside, I think is possible....
have to study about...
hi ervius
thank's is good packtages creator v2.1
if possible share kitchen_deV_Trin_19900 ?
Posted in the correct thread.
http://forum.xda-developers.com/showthread.php?p=2159891#post2159891
Sorry for ask here off-topic.
Thanks.
hi
axl79
rom 19701 rom pdaviet
POLARIS_WM6.1_v1.52.61.06_B19701
extract xip polaris =>> trinity not fonction ... 42.b3 ....
extract polaris =>> xip polaris ok ...
patch polaris to trinity ??? i don't no ??
if possible xip polaris =>> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00340000
trinity xip ==> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00300000
?????
oggi1969 said:
hi
axl79
rom 19701 rom pdaviet
POLARIS_WM6.1_v1.52.61.06_B19701
extract xip polaris =>> trinity not fonction ... 42.b3 ....
extract polaris =>> xip polaris ok ...
patch polaris to trinity ??? i don't no ??
if possible xip polaris =>> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00340000
trinity xip ==> \TOOLS\insert -i ..\ROM\out.bin -o OS.nb.payload -d 0x00320000 -s 0x00300000
?????
Click to expand...
Click to collapse
this 3d is for package creator v2 not for xipporting.
news:
in 1st post version 2.2, solved problem for "spaced" folders for remodule files, now you can use also "c:\documents and settings\..." folders..... for example!
axl79 said:
i didn´t realise "My rom: Italian WM6.1 os 5.2.19900 build 19900 1.0.4!!!"
have you ported build 19900 from another device????
where it is released... i dind´t see anything about this build...!!!
sorry for offtopic, but where trying to port build 19701 from hermes to trinity with your kitchen and the resultant ROM won´t boot, we take XIP dump from hermes ROM (PDAVIET), put files into new XIP folder, push "Port IT!", and choose XIP from other device when asked, but it doesn´t boot!!
What we are doing wrong?, is this the correct procedure?.
Thanks.
Click to expand...
Click to collapse
xipporting on mi kitchen maybe needs some corrections....
try this last version of buildos....
and tell me if works xipporting now...
download here:
http://rapidshare.com/files/111296473/kitchen.zip
bye!
FOR package creator, we all need other language into lang.xml, so if someone can insert other languages, I'll happy to update the program!!
bye!
Portuguese Language
ervius said:
FOR package creator, we all need other language into lang.xml, so if someone can insert other languages, I'll happy to update the program!!
bye!
Click to expand...
Click to collapse
Hi!
Find attached the XML file with Portuguese language.
Thanks
FInixNOver said:
Hi!
Find attached the XML file with Portuguese language.
Thanks
Click to expand...
Click to collapse
good, thanks!
ervius said:
try it!!!!
no more needs external cab extractor...
(from an idea of:"ArHon" with his: OEM Packages Compiler, that opened my mind about....)
full registry compatible now....
new version 2.2 solved problem with "spaced" folder for remodule!!
bye!
Attached Files package-creator-v2_2.zip (297.5 KB, 40 views)
__________________
.....nothig.....
My rom: Italian WM6.1 os 5.2.19900 build 19900 1.0.4!!!
if you appeciate my works and want drink a beer with me... Donate to me!!!
bye!
Click to expand...
Click to collapse
Let's sit down and Bottoms up!!
Thank you so much
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
- Enjoy!
- Download link:http://www.rayfile.com/files/e148b5d4-297e-11de-b80f-0014221b798a/
- Password:www.xda-china.com
Hi Childe. Can you also post the OEMs? I believe thats native VGA so it will be easier for our amazing devs to work on the manilla and other OEM stuff
Better yet post the whole shipped ROM
@Ameet: This is a CHS VGA.
Hi, can you upload rom to some other website like rapidshare or easyshare,please? rayfile.com sucks, it needs to install a client to download...
adwinp said:
@Ameet: This is a CHS VGA.
Click to expand...
Click to collapse
True but cant we simply translate the mui files to WWE? or use Topaz's WWE mui files in the OEM packages?
Sorry, it's not a NBH file, just resources copied from present rom, you should clarify that.
Ameet said:
True but cant we simply translate the mui files to WWE? or use Topaz's WWE mui files in the OEM packages?
Click to expand...
Click to collapse
Yes, for the most part you can use your 0409 muis.
for those having problems with rayfile, here is another mirror, password is the same as in first post!
http://rapidshare.com/files/221610248/21210.rar
c3ro
c3ro said:
for those having problems with rayfile, here is another mirror, password is the same as in first post!
http://rapidshare.com/files/221610248/21210.rar
c3ro
Click to expand...
Click to collapse
Thank you for the link. Much better speed.
Can someone had a 4shared mirror for it please?
Cheers
Edit : Nevermind. Thanks anyway
Ameet said:
Hi Childe. Can you also post the OEMs? I believe thats native VGA so it will be easier for our amazing devs to work on the manilla and other OEM stuff
Better yet post the whole shipped ROM
Click to expand...
Click to collapse
Bump. Someone?
is the new xip a real wm6_5 Aku5 ?
I must know to use Xipportex correctly
Röchelhilpert said:
is the new xip a real wm6_5 Aku5 ?
I must know to use Xipportex correctly
Click to expand...
Click to collapse
But why would you choose that? nk.exe exists in OEMXIPKernel