Related
SuperJustKitchen v0.7 Released.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
For more information on the kitchen, please read: http://forum.xda-developers.com/showthread.php?p=4288668
Word of warning:
None of the new EXT's have been tested and fixed for the Herald, Opal, Hermes AND Artemis. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
(I'm no longer updating each thread separately for each device but just updating my site and posting the release info here.)
ivanmmj said:
Now with Opal support!!
Wait until you see the announcement on my site to know that it's been updated/uploaded.
Word of warning:
SJK v.5 has had some major changes. None of the new EXT's have been tested and fixed for the Herald and Opal. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
Take not that there are many versions of certain packages. Let me know if the older ones are close enough to the new ones so that I can delete the old ones.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
At the moment, consider SJK v0.5 to be a test... Don't expect to have THAT many builds when it goes into v0.5.5
Right now it has the following builds available to you:
21054 (wm6.1)
21864 (COM2 - old style gui - wm6.5)
23064 (COM4 - newer gui - wm6.5)
5.5 will only have 21054, 21864, and 23064 unless something new gets released.
Click to expand...
Click to collapse
Thanks for providing us a new kitchen for opal. Can u give me a tutorial on using this kitchen for opal. Full explaination plz
It works exactly the same as your other Ervius based kitchen. You can follow that tutorial as well.
http://forum.xda-developers.com/showpost.php?p=4446173&postcount=3
The real difference is that I do the porting of new builds and the addition of new EXT packages for you.
(Granted, I've added more options under the Extra Buttons section, but you can go in there and figure out what most things are from their names and descriptions.)
Thanks BUT....
Thanks for your work man BUT: When i make my rom everything works Except the HOME settings and COMM manager,it is the same thing with BesFen kitchen,sometimes it works and then sometimes it does not.
I have tried and tried but nothing seems to help,i give up. I hope you guys can figure it out. Thanks.
What Home settings?
As far as the COMM Manager, don't choose the Comm manager in the EXT list. It's meant for older devices (like the Herald). Don't choose a Comm Manager at all. The OEM still has a comm manager built in. It will automatically insert a working comm manager.
Sorry i meant when you go to start/settings/Today does not work and i did not choose the comm manager, the one that comes with the oem does not work. Like i said sometimes they work and then it does not.
theglen35 said:
Sorry i meant when you go to start/settings/Today does not work and i did not choose the comm manager, the one that comes with the oem does not work. Like i said sometimes they work and then it does not.
Click to expand...
Click to collapse
Weird... The Today works fine on the Herald and it's part of the SYS, not the OEM. Are adding or not adding the MyCPL?
So the Comm Manager, even the one that's made FOR the phone has problems?
No i left out MyCpl. What is that BTW. The same thing happens in BesFen kitchen but it works when you put the PP on 12,anything higher it will not work.But i tried it on 12 & 16 PP in your kitchen but it does not work at all.Also when using file explorer and when selecting a theme when Today is working i have to long press or hold down the stylus to select something.
theglen35 said:
No i left out MyCpl. What is that BTW. The same thing happens in BesFen kitchen but it works when you put the PP on 12,anything higher it will not work.But i tried it on 12 & 16 PP in your kitchen but it does not work at all.Also when using file explorer and when selecting a theme when Today is working i have to long press or hold down the stylus to select something.
Click to expand...
Click to collapse
So it happens with BesFen's kitchen as well? The Opal is so strange and different than the other devices when it comes to cooking, I wonder what other changes I must make to the kitchen to get it work properly. At the moment, without an Opal, I can only make a kitchen as good as BesFen can when it comes to proper NB creation. Does anyone have a current WORKING kitchen for the Opal that doesn't have these problems? If so, point me to it and I will study the differences.
As a side note: Doesn't the Opal use myCPL by default? If it does, then you MUST choose it.
If you know PhamQuang you can ask him what kitchen he uses,his roms are usually buggy but i think the last one he made was good and everything works smooth.
You can find more detailed info on the kitchen in the main thread.
http://forum.xda-developers.com/showthread.php?t=545572&highlight=superjustkitchen
theglen35, I'll go ahead and try to contact PhamQuang. Thanks.
ivanmmj said:
As a side note: Doesn't the Opal use myCPL by default? If it does, then you MUST choose it.
Click to expand...
Click to collapse
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
BesFen said:
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
Click to expand...
Click to collapse
Hey BesFen THANKS very much for making a kitchen for the Opal,I have made many roms with it and except for a few problems it works good.But i think you should try and get all the bugs and problems worked out so we don't have to rely or wait for PhamQuang or PDAVIET to get any roms.
Because of the problems i am using Opals original WM 6.1 until you guys can figure it out.
theglen35 said:
Hey BesFen THANKS very much for making a kitchen for the Opal,I have made many roms with it and except for a few problems it works good.But i think you should try and get all the bugs and problems worked out so we don't have to rely or wait for PhamQuang or PDAVIET to get any roms.
Because of the problems i am using Opals original WM 6.1 until you guys can figure it out.
Click to expand...
Click to collapse
If your ROM can boot, it mean the kitchen work great.
The problem that you figure is not causes by the kitchen, it's pure something in the ext or OEM or SYS, try to read more reference from others device thread, I can't fix it since I don't have opal for test it, I am sorry about that.
ivanmmj said:
Now with Opal support!!
Wait until you see the announcement on my site to know that it's been updated/uploaded.
Word of warning:
SJK v.5 has had some major changes. None of the new EXT's have been tested and fixed for the Herald and Opal. Please test test and test and then let me know which packages don't work and what YOU've done to fix them. (I don't have time to fix ALL of them by myself.)
Take not that there are many versions of certain packages. Let me know if the older ones are close enough to the new ones so that I can delete the old ones.
Go to my site: http://justkitchen.info to get the updates and the info. It takes to long to update every device's forum that is supported, and I plan to support all devices.
At the moment, consider SJK v0.5 to be a test... Don't expect to have THAT many builds when it goes into v0.5.5
Right now it has the following builds available to you:
21054 (wm6.1)
21864 (COM2 - old style gui - wm6.5)
23064 (COM4 - newer gui - wm6.5)
5.5 will only have 21054, 21864, and 23064 unless something new gets released.
Click to expand...
Click to collapse
thanks ivan u've done great... thanks for having opal too in ur kitchen.. hopfully everything work great like the herald... ur the best... i thought i'll never see u since my phone is not the wing no more its touch viva now.. cuz i like wat u done for herald lots cooks already doing different roms... it is impressive... hopfully i'll start my own too... for here... thanks alot ivan keep it up...
BesFen said:
Official Opal's ROM have MyCPL, it should be include in ROM.
The reason I made opal's kitchen because no one share working kitchen here, some one asked me to make kitchen for Opal.
PhamQuang is from PDAVIET, and as we all know they always don't want to share the kitchen and source. You can try to contact him, maybe they change their mind now.
Click to expand...
Click to collapse
Yea, if the Opal comes with the MyCPL and they don't choose it, then that's part of the problem.
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
I also appreciate you working on that Opal kitchen. It's what I used as an example to get the Opal compatibility on my own kitchen. I appreciate your advise about PDAVIET.
ob_izzy, now it's your turn to be a great cook. ^_^
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
theglen35 said:
I agree with you, though. Technically, the issue is not with the kitchen but with what you DO with the kitchen as a cook. Since I don't have an Opal either, I won't be able to look around and preemptively fix all the bugs by pre-packaging certain EXT's into the OEM.
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
Click to expand...
Click to collapse
The kitchen only puts things together. What the stuff does depends on the OEM's and EXT's included. If you took all the EXT's that came with the official Opal ROM, you may not have any bugs because the manufacturer has worked out all those little bugs. If I had an Opal to play with, I'd probably find all the bugs myself and fix them (like I did with the Herald.) Unfortunately, we need the help of a very experienced Opal cook who HAS an Opal. (Or I need an Opal, which isn't happening since I have a G1 as my main phone and wouldn't buy an Opal to replace it (nothing wrong with the Opal, but I love android. )
theglen35 said:
Come on guys, what are you saying? Both of you are making a kitchen for a device that you don't have and can't test and you are saying it's not the kitchen! I beg to differ because believe me i have tried all sorts of ways to get the rom to work including reading alot, re-arranging files, adding, leaving out, different PP. Maybe it still has stuff to add or leave out that i don't know about, so that is where you guys come in. I need PLEH.
Click to expand...
Click to collapse
You can make an experience, dump the official opal's ROM (ruusigned.nbh) with Visual kitchen from mine or ivanmmj, go to the official rom folder, there is a "dump" folder there with Ervius kitchen tools, then run that kitchen and build the rom, it will build ROM same as official that you dump. If it run well, no problem with the kitchen.
BesFen said:
You can make an experience, dump the official opal's ROM (ruusigned.nbh) with Visual kitchen from mine or ivanmmj, go to the official rom folder, there is a "dump" folder there with Ervius kitchen tools, then run that kitchen and build the rom, it will build ROM same as official that you dump. If it run well, no problem with the kitchen.
Click to expand...
Click to collapse
Great suggestion man. I tried it and it did build the 6.1 rom without problems but it builds 6.1 good but not 6.5. When it builds wm 6.5 there are problems.
I haven't finished my kitchen (it doesn't work reliably at all) so I won't be posting it publicly (I'll be posting it when I get home today, if you know what you're doing, drop me a PM and I'll send you a beta version).
There are two batch scripts, "dump" and "build" (and "verify").
For "dump", you'll need to drop your TSW in \Base, and edit the set INPUT_FILE to reflect the name of your TSW.
From there, just run dump.bat.
You can then edit the OEM/SYS/XIP.
In theory, the MSXIPKernel and MSXIPKernelLTK from ROM\XIPDonor\xip.bin are combined with OEMXIPKernel, WinceNLS and LangDB are taken from ROM\XIPDevice\xip.bin. This does cause some odd errors because XIPPort isn't perfect. I'll try and write some code that dumps the XIP properly and merges the two. XIPPort is used because it builds a map.txt and ROMHDR.txt (these should be buildable with the tools I've got, but haven't finished them)
During the rebuild, both the XIP and SYS\OEM are relocated, based off ROMHDR and the .VM/.ROM, this and XIPPort aren't perfect. They cope with the stock ROM well, but less well with different XIPs/SYSs.
The Build.bat contains
Code:
set INPUT_FILE=
set OUTPUT_FILE=
INPUT_FILE is the name of the original TSW file (or whatever you want TGTool to build a new TSW from). It must be in \Base.
OUTPUT_FILE is the name of the output TSW. It will be placed in the root of the kithcen.
Verify.bat (along with the verify folder) are designed for distributing the ROM. Verify runs TGTool to check the tsw, and generates an MD5 for the TSW. Please distribute this with the ROM, so we don't end up with bad flashes.
You flash any ROMs built using this at your own risk.
TGTool is the (excellent) work of cedesmith. Without it, none of this is possible.
Don't use it if you don't know what you're doing.
Without Wen (from WMPU) I wouldn't have had a TG01 for testing, so this wouldn't have happened, and thanks to anyone who donated.
I'm going on holiday tomorrow, so I've uploaded the kitchen here. It may not work, things may go wrong, it's not my fault if they do etc. Download, and use only if you know what you're doing!
(Password is l3v5yTG01Kitchen)
Reserved...
Also reserved.
Thanks for this, it's nice to just see some progress.
i will have the uk rom with german lang? can i make this with the scripts and tools?? it´s only the langdb... to change... or???
ps. sorry for my englisch...
greetz
scoobydoo2k1
Thanks I3v5y!
Looking forward to this kitchen and a WM6.5.5 Rom. I don't need a clean WM6.5.0 Rom because that doesn't make my phone faster That's why I'm waiting for your Rom.
I also noticed, that you got a problem while flashing your TG01? The pictures shows NAND error.
Did you manage it to get the phone working again? Maybe with the short pin method?
Best regards,
DunkDream
It's look like the error which minhanh_tran got
http://forum.xda-developers.com/showpost.php?p=5920208&postcount=6
DunkDream said:
Thanks I3v5y!
Looking forward to this kitchen and a WM6.5.5 Rom. I don't need a clean WM6.5.0 Rom because that doesn't make my phone faster That's why I'm waiting for your Rom.
I also noticed, that you got a problem while flashing your TG01? The pictures shows NAND error.
Did you manage it to get the phone working again? Maybe with the short pin method?
Best regards,
DunkDream
Click to expand...
Click to collapse
I had a NAND error too flashing a .enc with short pin method days ago, but I just restarted and the flashing worked again. I think it may happen when you don't have the bridge over the pins enought time after starting the device. But this can be another thing maybe.
Short pin vs SDDL+
I was wondering why everyone seems to use the short pin method and not SDDL+? I have used SDDL+ to flash different roms as long as tgtool came back with no errors. I have not had much success with an upgraded Windows Mobile 6.5.5 rom, probably because I have been using HTC kitchens. But I have always been able to recovere using the short pin method.
Should I stop using SDDL+ and switch to short pin?
SDDL+ is fine. Short pin method should only need to be used when you don't have access to SDDL or SDDL+.
Novembre5 said:
I was wondering why everyone seems to use the short pin method and not SDDL+? I have used SDDL+ to flash different roms as long as tgtool came back with no errors. I have not had much success with an upgraded Windows Mobile 6.5.5 rom, probably because I have been using HTC kitchens. But I have always been able to recovere using the short pin method.
Should I stop using SDDL+ and switch to short pin?
Click to expand...
Click to collapse
I use shortpin when I can't get in to WM to use SDDL+.
I managed to recover. I tried flashing the ROM a few times last night, but then charged it overnight and it worked fine just now. I suspect it may have something to do with battery power.
Da Mafia said:
SDDL+ is fine. Short pin method should only need to be used when you don't have access to SDDL or SDDL+.
Click to expand...
Click to collapse
Completely agree. Have been flashing Arag0n85's clean-up Betas repeatedly and works very well. Personally I would avoid the pin short for anything other than when half-bricked and no option.
I'm going on holiday tomorrow, so uploaded a build of the kitchen I have.
It may or may not work, depending on what you put in to it, but I've had a few booting 23554 ROMs out of it!
Enjoy!
If you need me, drop me an email or something and I should respond.
Thanks for your work .When you plan to release a stable 6.5.5 rom with multilanguage, sense and the correction of 20% battery limitation?I can't wait for it .
Great news!
Alucard24 said:
Thanks for your work .When you plan to release a stable 6.5.5 rom with multilanguage, sense and the correction of 20% battery limitation?I can't wait for it .
Click to expand...
Click to collapse
I agree. Also could you check into the GPS cutout issue that has been seen on the debranded Rom? Something seems to be happening to cause the GPS to cutout after 1-2 minutes on the debranded rom
is someone on the way to built a rom with this kitchen??
Hamido123 said:
is someone on the way to built a rom with this kitchen??
Click to expand...
Click to collapse
The unbraded+manila builds that i've released have been done with this kitchen... I also tried a 6.5.5 without succes. It's the same kitchen that he had already released 1 week ago to some of us.
l3v5y said:
I'm going on holiday tomorrow, so uploaded a build of the kitchen I have.
It may or may not work, depending on what you put in to it, but I've had a few booting 23554 ROMs out of it!
Enjoy!
If you need me, drop me an email or something and I should respond.
Click to expand...
Click to collapse
can you publish these bootable roms?...or can someone try to built up a23554 rom?
mtwaldman said:
I agree. Also could you check into the GPS cutout issue that has been seen on the debranded Rom? Something seems to be happening to cause the GPS to cutout after 1-2 minutes on the debranded rom
Click to expand...
Click to collapse
Exactly, i also believe (and wish) this is only software-related problem! Haven't tried 6.1 though to see if the problem persists, i've only used the phone with 6.5 roms installed since i bought it. Can someone confirm that this problem exists in 6.1 roms?
Maybe try a different gps driver if it's a driver problem and such a driver exists. I don't know the gps chipset used in tg01, maybe a driver can be found from another phone that uses the same chipset.
Hi l3v5y
In theory, the MSXIPKernel and MSXIPKernelLTK from ROM\XIPDonor\xip.bin are combined with OEMXIPKernel, WinceNLS and LangDB are taken from ROM\XIPDevice\xip.bin. This does cause some odd errors because XIPPort isn't perfect. I'll try and write some code that dumps the XIP properly and merges the two. XIPPort is used because it builds a map.txt and ROMHDR.txt (these should be buildable with the tools I've got, but haven't finished them)
Click to expand...
Click to collapse
You are not here to end right.
There are modules with Original MSXIPKernel, you must leave.
That is a rule in Samsung
Utility Link: http://www.4shared.com/zip/KBQLOO9d/TG01toT01A_Converter_Utility.html
How to use it:
There is 2 ways to use it.
1- Drop a TG01 ROM at the "TG01toT01AConverter" batch file, and a CMD window will appear showing the process.
2- Run a CMD and use the comand "TG01toT01AConverter rom.tsw"
In both cases, a file called "T01A_to_SP50_wm65.tsd" will be created if all it's OK. That's your ROM.
That's all, simple right?
I hope you enjoy it!
PD: The TG01 to T01A Converter includes my TG01 Tool set for simple ROM dumping and repack. If you need to redefine packages you should need to use l3v5y kitchen.
PD: This pack includes cedemish TGTool.
arag0n85 said:
Well, since finally someone has reported that my TG01->T01A method works properly, I decided to release for public a converter instead T01A/TG01 ROM's Version. In my ROM's threads, will be up to people to re-upload the T01A version and share the link, but I will only release TG01 version of the ROM and link to this thread.
Click to expand...
Click to collapse
you should not call MY TG01->T01A method yours just because you put it in a bat. maybe i should point you to tgtool 1.3.20 announcement post, your .bat is more or less a copy/paste of sample code there.
so how my tool+my sample = your tg01->t01a method ?
arag0n85 said:
PD: The TG01 to T01A Converter includes my TG01 Tool set for simple ROM dumping and repack. If you need to redefine packages you should need to use l3v5y kitchen.
Click to expand...
Click to collapse
The TG01 to T01A Converter only needs tgtool and rom files, the rest of tools for this purpose is just bloatware.
keep up the great work
Long time ago, some old dispute, I think it's time to move on!
What each of you is doing complements each other's work, but giving appropriate credit in your every posting is just too much overhead. IMHO there's a bit of a wording issue, I'm sure arag0n85 didn't intend to claim this batch to be entirely his own achievement or neglect cedesmith's role/involvement.
I've seen some very bright members leaving xda-devs because their work was not treated here with due respect. I'm sure everyone would hate to see either of you go or give up your projects. The truth is that if you are not ready to witness other people using, reusing and even abusing results of your work, then either don't release it or protect it from abuse.
Take it easy. Peace...
stepw said:
What each of you is doing complements each other's work, but giving appropriate credit in your every posting is just too much overhead. IMHO there's a bit of a wording issue, I'm sure arag0n85 didn't intend to claim this batch to be entirely his own achievement or neglect cedesmith's role/involvement.
I've seen some very bright members leaving xda-devs because their work was not treated here with due respect. I'm sure everyone would hate to see either of you go or give up your projects. The truth is that if you are not ready to witness other people using, reusing and even abusing results of your work, then either don't release it or protect it from abuse.
Take it easy. Peace...
Click to expand...
Click to collapse
Wisdomly said...
Couldn't agree more...
bib*oops said:
Wisdomly said...
Couldn't agree more...
Click to expand...
Click to collapse
bib*oops，do you have tg01 sim free version???can it used in my T01A?
btw,the convert link I can not open it,can argu post it in forum,thanks!h
bird_9527 said:
bib*oops,do you have tg01 sim free version???can it used in my T01A?
btw,the convert link I can not open it,can argu post it in forum,thanks!h
Click to expand...
Click to collapse
The file is arround 20Mb, can't be placed on the forum attached... By the way, I tested the link and should be working.
bird_9527 said:
bib*oops，do you have tg01 sim free version???can it used in my T01A?
btw,the convert link I can not open it,can argu post it in forum,thanks!h
Click to expand...
Click to collapse
My tg01 is sim-unlocked by code(IMEI dependant)...
TG01toT01AConverter rom
many time i try to use this App. But still can not convert rom.
everybody already convert it susses...to teach to step by step please ! thanks
sory my bad english
nhattuong said:
many time i try to use this App. But still can not convert rom.
everybody already convert it susses...to teach to step by step please ! thanks
sory my bad english
Click to expand...
Click to collapse
The idea is easy. There is an instruction to extract payload from a tsw and an instruction to merge payload to a tsd. So, I placed the tgtool with a tsd rom with an empty payload side by side and a .bat file that calls the proper instructions for the conversion from a tsw file. The file is called TG01toT01AConverter, and you have 2 ways to act with it.
a) Click on a tsw ROM, and move it over the .bat and drop it.
b) Open a MSDOS Command Window at the directory and type: "TG01toT01AConverter yourrom.tsw"
In both cases you should see a file called "T01A_to_SP50_wm65.tsd T01A_to_SP50_wm65.tsd" as output.
thank so much your support. It have done, after converted i flashed it. Successful.
Enjoin it.
Can it be used to convert any new ROM in the future, such as 6.5.3 or 6.5.5?
Thanks
I already to use this tool to Converted new Rom 6.5.5. Then flash it Sucsess.
nhattuong said:
I already to use this tool to Converted new Rom 6.5.5. Then flash it Sucsess.
Click to expand...
Click to collapse
i'm using t-01a too .so may i know which version of rom do you have use to your phone
Thankk you
WM6.5.5 WM6.5.5 OS 5.2.23563 Build 23563
Rom By ffboy
WM6.5.5 WM6.5.5 OS 5.2.23563 Build 23563
Rom By ffboy
nhattuong said:
WM6.5.5 WM6.5.5 OS 5.2.23563 Build 23563
Rom By ffboy
Click to expand...
Click to collapse
in this step do i have to chance from T01A_to_SP50_wm65-theduyet.tsd to T01A_to_SP50_wm65-theduyet.enc ???
{Rename your ROM extension from (.tsw) to (.enc) at the PRG folder.}
Thank you again ＾＿＿＾
cant download it. it says file tempo not avail...
use tsd extension and pin method to flash your device...i am using Novembre5 6.5.5 rom,very stable and fast,i liked...
Pls help me. My phone is currently using English rom. I would like to change it to Japanese rom. How can i change it?
I used the converter but it didnt work. My pc is windows 7 (64bit). May I know the reason why it failed?
Greetings!
First off, I have little idea what I'm doing, this is my first attempt to create a custom ROM. I've searched around and can't seem to find a solution.
I've got an Xperia X1 and am using osKitchen.
The ultimate goal is to have a Japanese ROM with WM build 25369 with no additional UIs, i never use sense or whatever anyway, just the old today screen with cal, messaging, and time/date items.
I have:
Latest stock ROM for X1 (GENERIC_NAM_R3AA011)
23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 (Just Eng)
initflashfiles-dat-all-langs-updated-feb-24-2010.zip
RUU_Diamond_eMobile_JPN_1.81.881.2_Radio_Signed_Diamond_52.48.25.26_1.09.25.07_Ship.exe (6.1 JPN ROM)
Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip
WM6550-23563-Rollup-All-Pkgs.rar (This has all languages)
Here's what I'm doing, anyone of them (or all) could be very wrong, hopefully I've done at least one thing right:
Imported X1 ROM for OEMDrivers, OEMApps, OEMOperators, oemversion, oem_dpi
Imported 6.1 JPN ROM for OEM Lang 411
-What i did here is i copied everything over from the JPN rom's oem 411 folder into the X1 OEM Lang folder, overwrote any conflicts, deleted any 0409 muis, and copied over the file from initflashfiles zip for 0411.
Replaced OEMXipKernel with the one from Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65.zip and selected custom XIP when making the rom with the one also found in that zip. Put the rest of the files (os.nb.payload, xip.bin, uldr.nb0, romhdr.bin) into the ROM Parts folder.
Then, I Used OS, OSFiles, MSXIPKernel, MSXIPKernelLTK from the 23569_MSXIPKernel_SYS_QVGA_WQVGA_VGA_WVGA_0409 zip, and the rest of the packages i used from the WM6550-23563-Rollup-All-Pkgs rar (because it had 0411 files).
I deleted dpi and lang folders that my device doesn't use (it uses 192dpi 480x800 and 0411) and built the ROM, flashed, and it shows the Sony Ericsson splash screen, and then goes black forever.
I know I must be doing something very wrong, any hints as to what?
Thanks
Pfff, what a big list,
Okay I did it this way, and I make my rom in 12 languages and they are all working.
1. Install oskitchen and import xperia rom
2. After finishing import 23563 build
3. Install another oskitchen and import diamond jpn rom
4. Copy the oem_lang 0411 and the ext packages to your kovsky kitchen be aware you put them in the right place.
5. Open the kovsky kitchen and select the Japanese language and select the packages you wanna use in your rom and you're done.
Regards,
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
nemasu said:
Cool thanks!
That would be for 23563 though right? What if i wanted to use 23569 with 23563 packages? ....No real reason, higher number, figure it's better somehow....that even possible?
Click to expand...
Click to collapse
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Rataplan said:
Just start with 23563, it's a good package and if you have a working rom you can alway's make the change.
Greetz,
Click to expand...
Click to collapse
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
nemasu said:
Ok sounds good, I was just thinking I probably shoulda tried with something a bit easier haha.....how would i make the change? is my approach correct?
Click to expand...
Click to collapse
If you extract the 23569 build, you only have to change the All and Common folder, but in your first post you where talking about a 25369 build and I didn't know what kind off build that was.
Succes buddy,
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Farmer Ted said:
Make sure you have the proper wince.nls in your build. If you leave it out, the rom won't boot.
Click to expand...
Click to collapse
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
nemasu said:
I used the one that came with the Kovsky-xip-bin-oemxipkernel-nk-exe-native-WM65 zip.
Click to expand...
Click to collapse
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Rataplan said:
I don't think there is any difference between those 2 wince.nls but if you wanna be sure just use the one in the 23563/COMMON folder.
Click to expand...
Click to collapse
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
nemasu said:
Hmm, I've got a wince.nls in:
Sources\Devices\HTC Kovsky\Profiles\default\OEMXipKernel
Sources\Windows Mobile Builds\23569\0411\WinCENLS_Lang_0411
and
Sources\Windows Mobile Builds\23569\Common\WinCENLS_WWE
they are all different sizes....should they all be the same? or only have one? or?
Click to expand...
Click to collapse
No I have them also, never take a look at it, only checked the file when I cooked my rom's never changed anything or replaced it with another version or from another build.
Hi all,
so I am new to the world of Windows Mobile - use to be a Symbian fan and then got the HTC Touch Diamond recently due to my Nokia dieing of old age.
I want to learn how to cook ROMs so I can customize what I want as I want. I tried sending Da_G a PM as he seems to be quite knowledable about cooking - although he seems to be MIA (his last post was a long time ago) and I have not gotten a reply yet.
So now onto some questions which are probably stupid, but I do not know the answers to.
So I have an HTC Touch Diamond which originally comes with Windows Mobile 6.1, I am using osKitchen as it seems really popular and it looks easy enough to use. I followed the guide which is here but it does not give me the complete info I want.
So in order to cook a ROM you first need to have an original ROM (so in my case an original ROM for the HTC Touch Diamond off the HTC site?)... I got that(RUU_Diamond_HTC_WWE-AFK_2.03.421.2_Radio_Signed_Diamond_52.51.25.26_1.09.25.23_Ship.exe)
Then you open it up with osKitchen, it extracts it blah blah blah.
I then get a popup about a new ROM has been imported and it asks me if I want to automatically configure the project to use the ROM. I click yes.
Then it says the device profile currently selected uses a pre 6.5 kernel, module allocation space will be extremely limited. Do I want to auto enable module to file conversion for a list of files? Now I read somewhere that if you are using pre 6.5 kernel you want files, if you are using the 6.5 kernel you want modules? I am not sure what to click here as I want to upgrade to windows mobile 6.5 ...
So do I enable the conversion or not?
Then it pops up with the project settings, under SYS Packages I can see all of the phones services. OEM packages, I am not too sure what that is... One thing which is worrying is that there is a red circle with an X in it infront of OEM Drivers... If I hover over it, it says there are issues detected in the OEMdriers. They all seem to be errors detected in the registry and the registery key path entry is invalid due to 2 adjacent backslahes? So is this normal? What do I do?
Also there is a block "RecMod" under OEM Packages. What does that do and what is it used for?
EXT Packages, over here we have all of the applications which will be preinstalled when you flash the ROM? I know how to add .cab packages to it and it seems simple enough. Once again there is a RecMod with a tick box?
ROM Tweaking I have not really bothered with yet, would first like to learn the basics. Anything I should know about in ROM Tweaking?
Now back to SYS Packages. This is where you update/port/upgrade ? to newer windows mobile versions? Now I think if you are changing between window mobile major build versions or what ever you want to call it (like from 6.1 to 6.5) kernel changes perhaps? You call it porting? Anyways, so now I want to change to the latest build in WM6.5 .
I took a look at this thread: http://forum.xda-developers.com/showthread.php?t=650783
Now it seems like the first 3 digits indicate something, what exactly I am not too sure. Perhaps someone could explain?
There is HTC HTC which is made by HTC I think and possibly meant for HTC?
Then there is COM 2 and LG. Now since I have an HTC do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
Anyways, I downloaded the HTC one. Now I want to port / upgrade to it. It is WM6.5 now as well. So I click Import, then goto Import a new WM build. Select the appropriate build dump, then click on start importing. It will import it and then what? Is there anything else I need to do?
I am assuming go back to Project Settings and under SYS build change it to the newer one which I have just imported? Although is this really all I need to do? Will I now have a proper functioning cooked ROM running WM6.5 with the new build?
Thanks
If you're cooking a 6.5 rom, and you have a 6.5 native kernel (there should be one out there, unless you're using a cdma diamond), then DO NOT RECMOD (convert to files). If you have to use a 6.1 kernel, then you have to recmod a lot of modules. Look around, there are threads with native kernels for many older devices. I'm not going to dig up a link, I'll let you find it. Just get the Diamond native kernel and use it.
If you have a cdma diamond, then I believe that people use the cdma raphael native kernel, but supposedly it's buggy.
OEM Drivers has an .rgu that usually has a few mistakes in it; that's probably the error you're getting. I wouldn't worry about it, but the kitchen may tell you which line the error appears in, and you can fix it.
As far as rom tweaking goes, all you need to know is that manila sucks, and Sense is blight on humanity. Good luck and have fun.
Real Beginners Stuff Please.
PsyCLown89 said:
Hi all,
so I am new to the world of Windows Mobile......
I want to learn how to cook ROMs so I can customize what I want as I want.....
So now onto some questions which are probably stupid, but I do not know the answers to......
...... I followed the guide which is here but it does not give me the complete info I want.....
..... What do I do?
..... What does that do and what is it used for?
..... would first like to learn the basics......
..... so now I want to change to the latest build in WM6.5 .
..... do I have to use the HTC one or not? Also it seems some have newer / higher WM builds? So why are there these many different builds and what difference does it make as to what they are? Also what are the COM 2, 3 and 5 ?
.....and then what? Is there anything else I need to do?
.....Thanks
Click to expand...
Click to collapse
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
It all comes down to the basics. If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
Kitchens available today make a lot of things heaps easier than they were several years ago.
Try starting with this thread.... it is not for your device, but you get to learn the basics and actually understand what happens in the background.
http://forum.xda-developers.com/showthread.php?t=335631
Cooking is not just clicking around with your mouse.
pkoper said:
.... If you do not know what a kitchen actually does, then there probably is no point in cooking to start of with.
..... Cooking is not just clicking around with your mouse.
Click to expand...
Click to collapse
This may be new to me, but it also was to EVERY cook there is, or has been at sometime. We all learn something new at some time, and all I was asking for is a little starter to get me going. I realaise it isn't a point and click exercise, otherwise I would have made a ROM by now, and not asked for help. I didn't write the software for the kitchen, so I don't know how it works.
http://forum.xda-developers.com/showthread.php?t=335631
Click to expand...
Click to collapse
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Please, give me a break.
Fish-Man said:
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Click to expand...
Click to collapse
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Fish-Man said:
Thanks for that, I hadn't seen that one, but unfortunately, it also doesn't give the procedure for starting with a WM6.1 ROM and adding/changing files to end up with a WM6.5 Native Kernel.
Click to expand...
Click to collapse
Thats exactly what I meant. Do you know what the kernel actualy is?
pkoper said:
Using search you would have found the native kernel:
http://forum.xda-developers.com/showthread.php?t=619663
Click to expand...
Click to collapse
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Thats exactly what I meant. Do you know what the kernel actualy is?
Click to expand...
Click to collapse
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Fish-Man said:
Hi,
So many questions
I too am new to the world of Windows Mobile, and have learnt how to flash different ROMs sussessfully.
I have spent my time reading hundreds of threads about flashing, and having a go - the tutorials and threads have been great source of knowledge.
Now I want to start cooking a ROM and things are different..... I have read thousands of posts and tutorials and watched videos, but I haven't found a real Noobs method of: starting, choosing a kitchen, finding a ROM, importing the new bits, and making the changes. It all goes wrong right from the very start.
Choose a kitchen, and then what ? (exact steps, not just "find a ROM you like, then..", etc. etc.)
None of the threads I have read seem to be able to give the nitty gritty to start, they all skip over it.
I have a Kaiser, and am in a similar position to you, there isn't a native 6.5 kernel for the Kaiser, so how do I make a 6.5 build in a kitchen, when I don't have a 6.5 build to start off ?
Please can someone give a REAL NOOBS guide to starting off.
Thanks & Regards,
Click to expand...
Click to collapse
I don't think what you're looking for exist, persay. There are several kitchens out there to choose from. The only thing that helped me when starting out was frequenting the thread of the kitchen that I was using. It's in the kitchen's thread that you'll find all the nitty gritty answers you're looking for and other people that are in the same boat as you, and more experienced users of the same kitchen who would probably be more apt at answering questions about specific kitchen.
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Yes, It's a piece of code, usually written in assembly language (for speed of execution), that sits between the hardware devices and the system drivers and programs, to translate what the programs want, to what the hardware can understand, and deliver the results from the hardware, back to the programs.
It is the core of the Operating System, and is the first thing that is loaded into memory when the system boots, and stays there until you turn off the device (unlike other programs that are loaded, and unloaded as needed). It is loaded into a seperate and protected area of memory, where it executes processes, handles interrupts, memory management, process management, file management and I/O management.
The User, cannot interract directly with the kernel (or hardware), but has to go via a seperate program (usually containing a GUI), that can send it's requests to the kernel for processing. After the kernel has processed the programs requests, the kernel gives the information to the program, which then outputs it to the User.
Is that enough of an explanation ? Sorry I had to simplify it, but there are a lot of other noobs here that may have gained some knowledge from that, so rather than blow thier minds with acronyms and babble, I thought it best to explain it simply.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
Nice quick knowledge drop on kernel. It sounds to me like you already have a better grasp on things then some!
Fish-Man said:
Thanks, but I already have them. They are "files" not a "stock build" that the cooks tell you to start with. Again, do I need to start with a "stock build" of WM6.1, or can I use those WM6.5 "files" instead, if so, what am I missing from the "stock build" that I need to continue ?
Click to expand...
Click to collapse
Thats because there is no stock 6.5 for the Kaiser. Not sure what "those WM6.5 files" are, but you do need the drivers for your device. Any leaked build will not contain those.
Dumping a stock rom will give you insight as to what is actually in the rom. When you then download one of the leaked builds you can you will recognize the files and hence see what needs replacing in order to upgrade.
Now, are there any more questions you want me to answer, before telling me what I need to know, to understand the first few steps in cooking a ROM ?
Regards,
Click to expand...
Click to collapse
What kitchen are you using? As there are obviously slight differences as to what is where.
I would just get a ready kitchen and study it.
http://forum.xda-developers.com/showthread.php?t=517957
for your reference maybe you should read this....
http://forum.xda-developers.com/showthread.php?t=901712
i had made the tutorial how to cook ROM, step by step. it has different device and different OS but worth to read.....
i don't have enough capability to Cook but i try to....
also in this http://forum.xda-developers.com/forumdisplay.php?f=385
some of members also made tutorial as well.......
i hope it can help.