AndrewSh said:
23668 AKU 5307 Windows CE: 5.2 Build 4585 (June 17 2010. 16:05:08)
23668_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409.7z (38.98 MB)
http://www.multiupload.com/BRBSUQU4QD
http://multi-up.com/299136
Re-uploaded by Alexx~
Click to expand...
Click to collapse
Wow! Tried it and seems sooooo faster respect to 23667. My I8000 has increased performances as never before. Now SPB MS carousel is really responsive!
I noticed a lot of changes between 23667 and 23668. Any idea?
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
fubo73 said:
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
Click to expand...
Click to collapse
Metadata package is the all the registry entries, gathered together into one place.
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
Are you saying it is built during cooking? If not, why I did not find it in packages so often?
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
can you please tell us how to edit/adjust packages.cif/packages.sof?
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
AndrewSh said:
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
Click to expand...
Click to collapse
thanks alot. is there a english version of this tool available?
HD2Owner, English version is a part of Barin's OSBuilder (which I use as a rom kitchen)
The English discussion and public downloadable release is here
Mmmm interesting I heard itbefore an effectively from you Andrew lets make it important here cause neither me use it... Thanks a lot
Just to make it more understandable - screenshots from packages cif and sof editor from OSBuilder tool
Barin is now on vacation and I have no contact with it, but I hope he will forgive me.
I translated pSofCifBuilder to English.
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Alexx~ said:
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Click to expand...
Click to collapse
Yea I am starting to like that OSBuilder now...
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
Farmer Ted said:
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
Click to expand...
Click to collapse
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
cnzqy1 said:
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
Click to expand...
Click to collapse
as i said i never ever modified them, that means it doesnt even matter with Build OS. moreover, using "all packages to one" technique strips most of the info from these files without even affecting the ROM.
In this order, which is specified in packages.sof will be building registry. It is not related to PRB, or OSB, or any other kitchen.
Building registry does rgucomp (default.hv, user.hv and boot.hv) on the list of packages (dsm) from packages.sof
It has always been, regardless of whether old or new kitchen. So no other way.
Further deletion of files dsm ("all packages to one", etc.), nothing to do with the building registry.
P.S. There is a myth that OSB is important packages.sof, and at for other kitchens, it is not needed. This is nonsense. In OSB can view and edit packages.sof and packages.cif. That's all the difference.
well, my point is just that registry is added into the hives even if package has not been mentioned in packages.sof, so why bother editing it?
It is important that packets from the SYS and from OEM (which can be attributed to the group OEMDrivers) were formed in the order of packages.sof. The rest you can adjust with the names (dsm or package, depending on the kitchen).
If you think that the roster of SYS formed not so - you are mistaken.
As an example, you might see messages about the problem of "blank page" in IE.
trust me, i've never modified that file. i always use it without editing, from whichever source i get it. i'm not saying it is useless, but in most cases we don't need to edit this file
Related
how to dump the newest 19839 ROM？
i found i can't dump it。can anybody tell me？
thanks
search my friend and it will do you wonders....
http://forum.xda-developers.com/showthread.php?t=379559
in this thread it should show you what you need...
no,this is not the way which can dump the 19839 rom your friend UDk made,and besides they just keep it as a secret and ignore every PM which were sent by the person who would be happy to know the truth.and someone just criticize that the other cookers who just start a "Cooker War" and on the other hand he just make some undumpable Rom as the prove of his selfishness.What a ridiculous phenomena....
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
NikMel said:
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
Click to expand...
Click to collapse
thanks,but the rom is only removes dsm and rgu.if u dump it ,u will find the rom is do something by the owner.
so i want to know it.
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
swtos said:
All roms can be dumped.
Click to expand...
Click to collapse
really do you think what wrote???
ervius said:
really do you think what wrote???
Click to expand...
Click to collapse
what do you mean ?
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
swtos said:
what do you mean ?
Click to expand...
Click to collapse
nothing.... dump it and rebuild.
dcd1182 said:
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
Click to expand...
Click to collapse
rgus and sdms are allways the same from build 19716, same!!!
ervius said:
rgus and sdms are allways the same from build 19716, same!!!
Click to expand...
Click to collapse
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
dcd1182 said:
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
Click to expand...
Click to collapse
yes, dsm contains version, but you solve with my dsm patcher...
and rgu, maybe only 19716 are differents, for me no differences from 19199 and last posted...
I think that microsoft provides us with TRUE SYS 19202 (Mar 24 - April 5 - 2008)....
So, there's no reason to patch dsms... to match a non existing version .....
swtos said:
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
Click to expand...
Click to collapse
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
GPRS said:
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
Click to expand...
Click to collapse
no, he cannot, only who protects roms can.....
@ervius
please can you post dsm's & rgu's that worked with your build ??
thanks.
how protected?and how dump?
anbody tell me?help!
yes, I agree with u. swtos's ROM can be dump but can't be rebuilt. I want to know what's the problem of the ROM.
GPRS said:
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
Click to expand...
Click to collapse
Hi
My ROM has some tweaks and extras that needs a soft reset after initialization wth 1st boot. How can I make a automatic reboot just the 1st time the phone boots up?
If you're using RunCC, edit your *.rgu/app.reg accordingly:
Code:
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"ResetDevice"=dword:00000001
How can I know if I use runCC?
You don't know which packages you're using for your ROM? Funny thing!
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
hehe... just using a dump of official rhodium S2, and spiced it up a bit, and deleted things I don't need
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
animelover said:
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
Click to expand...
Click to collapse
yeye... there it is Thanks
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
Funny indeed. These are the junior cooks we get these days...
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
hey hey... fair play ppl... glad to have new chefs CC is for that... new chefs and experienced chefs
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Very true..
Anyways, I love your sig And it's quite funny how true it is!
if i might stick with the topic
2 - xda_uc also offers a reboot after customization - you could add this to your ext
3 - old method: autorun + checkautorun pkg also reboots your rom (dump blackstone or kovsky)
Problem With add2config Packages?
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
I'm not sure anyone will be able to answer that without being totally lucky if you don't post your packages or build-log or at least the add2config text files. Anway, maybe you already do this, but if you don't, then start doing this: after cooking, look in the dump and make sure everything is there. Also, look at config.txt to make sure all the add2config's were compiled properly. This will save you the flash-disappointment.
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
NRGZ28 said:
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
Click to expand...
Click to collapse
lol, also I did this way...
Can't remember where I read something like "PPL: Could you make it in this language?" - " "COOK": I don't know how to!"
LOL
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
Bumping my own question
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
Found: 1 Extra Info on a Package... Populating config.txt with: CAB: \Windows\B4ALL.cab
Click to expand...
Click to collapse
and this:
Processing "B4ALL.cab" as file
Click to expand...
Click to collapse
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Failed to parse value name HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\start\Tools\Format SD Card.lnk!!!
Click to expand...
Click to collapse
Farmer Ted said:
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
and this:
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Click to expand...
Click to collapse
(disregard my last post on the other thread, I didnt realise you had replied )
Thanks for the response, yeah the add2config file has worked before in the root of the packages, seems something else it buggy :/
Yeah that cab may be so, but that was an old one just as an example, I really need to get it working for this mortscript thing we discussed on the other thread..
Maybe we could discuss more tomorrow ? Perhaps you could have a nosey in my kitchen or something, I know I should work this stuff out myself, but as a chef still in training, its quite difficult to know what to look for, and help from peopel like you is priceless
Thanks
Hello, in xxxxx_CMWifiEnroll, etc. packages there are registry keys like:
Code:
REGEDIT4
??????????????????????????????????
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\Build_Order]
"CMWifiEnroll"="0"
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PKG]
"shadow"="1"
I wonder what "??????????????????????????????????" is? Is it because the dump tool we use are not updated to date?
Thanks!
It's just broken rgu file, remove that line and you'll fix your issue .
tomcug said:
It's just broken rgu file, remove that line and you'll fix your issue .
Click to expand...
Click to collapse
I don't think all new Official ROMs have broken rgu files... I think it may be a special rgu that existing tools can't identify...
cnzqy1 said:
I think it may be a special rgu that existing tools can't identify...
Click to expand...
Click to collapse
I don't think so :E.
tomcug said:
I don't think so :E.
Click to expand...
Click to collapse
But I just can't imagine that HTC includes broken rgus in several packages and several ROMs.
I don't even have that package in either of my latest Oboe or Huashan dumps.
??
cnzqy1 said:
But I just can't imagine that HTC includes broken rgus in several packages and several ROMs.
Click to expand...
Click to collapse
You say that current tools can't identify those rgu files, it's impossible, they don't have to be identified, they are just extracted from IMGFS partition . So leave this and don't care about this.
Hi there, I am a newb chef, I have recently released my custom ROM into the world and people asked for other languages...
I have a kinda quick way to build all the languages but i have to be at the PC all the time to do it. I was wondering if there is a script or automation tool anyone has to get this done? I've tried searching but not sure exactly what to look for here-any pointers? I could probably live with switching kitchens if anyone knows it can be done easily in another as there are 5 languages now!
e.g. So I can press, say "create ROM", and it'll make ruu_signed-0409.nbh, ruu_signed-0410 etc...
Thanks for any wisdom you care to impart!
arealityfarbetween said:
I could probably live with switching kitchens if anyone knows it can be done easily in another as there are 5 languages now!
Click to expand...
Click to collapse
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
airxtreme said:
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
Click to expand...
Click to collapse
Wow! I'd read a bit about it but was already setup with EVK, guess i should have made the switch when I had to copy and paste sys packages into the right directories.
Cheers!
airxtreme said:
Oskitchen builds all the selected languages in the same pass and also picks all the right SYS packages (EA/NonEA/AH/CS/etc) while building to avoid having to keep different project files for each language.
Click to expand...
Click to collapse
Does OSkitchen also respect the _skip and _only tags that prb uses ?
NRGZ28 said:
Does OSkitchen also respect the _skip and _only tags that prb uses ?
Click to expand...
Click to collapse
I've always wondered what _skip files are for, i've not seen _only but wasn't looking for them What's the advantages of recognising them/What do they do?
Slightly OT i know...
NRGZ28 said:
Does OSkitchen also respect the _skip and _only tags that prb uses ?
Click to expand...
Click to collapse
The "_skip" file is not copied but anything else is, including _skip_* files
airxtreme said:
The "_skip" file is not copied but anything else is, including _skip_* files
Click to expand...
Click to collapse
Hmm okay. Well I was wondering if your kitchen touches these files or not. I have a huge.. 13 device kitchen.. that works soley on the ability to skip_ or _only include/exclude certain packages in the build chain. Say _skip_Diamond or _only_Leo for certain packages. I have a GUI kitchen for PRB made by myself, but I wouldnt mind trying another kitchen one of these days and yours seems very nice (but I gotta be able to keep the folder/package structure I have now, unfortunately).
NRGZ28 said:
Hmm okay. Well I was wondering if your kitchen touches these files or not. I have a huge.. 13 device kitchen.. that works soley on the ability to skip_ or _only include/exclude certain packages in the build chain. Say _skip_Diamond or _only_Leo for certain packages. I have a GUI kitchen for PRB made by myself, but I wouldnt mind trying another kitchen one of these days and yours seems very nice (but I gotta be able to keep the folder/package structure I have now, unfortunately).
Click to expand...
Click to collapse
The kitchen was designed to leave the source folders completely intact so it shouldn't change anything inside the package folders once the ROM has been imported
I apologize if this has been covered, but I can't find specific info with my search terms.
I'm cooking for Rhodium, WVGA, WM 6.5.x sys 21682. My base ROM is ATT's stock august 30th 2010 ROM. Using OSKitchen Zero, latest release.
Basically, I can't get any version of sense to work. I've tried cooking 2016, 2018, and 2019, and can't get any of them to work. The problem is that when I try to import the EXT packages with OSKZ, I get an error stating: "The OEM package you've selected doesn't seem to be valid..."
So, I thought maybe it was just being strange. So I placed the packages manually into the kitchen and tried to build the ROM and platform builder would hang and I'd have to cancel the process.
Any tips tricks or ideas?
Thanks a lot!
Smith
Where are you sourcing your sense files from?
Have you got the additional dependencies covered (ie starticonloader?)
crazyC said:
Where are you sourcing your sense files from?
Have you got the additional dependencies covered (ie starticonloader?)
Click to expand...
Click to collapse
I'm not sure what you mean by sourcing exactly, but on my PC they're located on my desktop, and I've also tried placing them straight into my kitchen without using the GUI to do it.
I got the files from a post here on XDA.
Yeah, I believe I have all the additional dependencies as well.
I've been reading and it looks like I have to modify the app.dat file and some other files?
Regards
Smith
smithisize said:
I'm not sure what you mean by sourcing exactly, but on my PC they're located on my desktop, and I've also tried placing them straight into my kitchen without using the GUI to do it.
I got the files from a post here on XDA.
Yeah, I believe I have all the additional dependencies as well.
I've been reading and it looks like I have to modify the app.dat file and some other files?
Regards
Smith
Click to expand...
Click to collapse
OK so you got them from XDA - as I am assuming you are not using the At&T standard ones. (that was what I meant).
The ones I got from XDA were already CFC'd and were already in EXT format not OEM and so did not need any importing as such, just copying into the directory.
I did not need to modify anything - cannot remember the thread I got them from tho.
I will try and have a look, but my kitchen is now such an amalgamation of packages that I couldn't be sure where it all came from.
Ahhhh ok, i was confused because it says's import, ext package then it asks for an oem location.
Ok, with that cleared up, place straight into kitchen, gotcha. How many dependencies are there, can you recall? I think i have them all but I want to make sure.
Thanks a lot!
Regards
Smith
Edit:
No go, but here's the error (attached in the pic)
You've got files inside of modules. You need to clean your modules up.
Farmer Ted said:
You've got files inside of modules. You need to clean your modules up.
Click to expand...
Click to collapse
Alright, is there any reading I could do to help me figure out what to clean and what to keep?
Thanks
Smith
Try looking inside the corrupt modules, then look in some clean ones, and figure out what doesn't belong. It should be obvious.
Someone else is just going to tell you the answer, but you're better off figuring it out yourself.
Farmer Ted said:
Someone else is just going to tell you the answer, but you're better off figuring it out yourself.
Click to expand...
Click to collapse
Couldn't agree more. I'll check it out.
Thanks for the info, much appreciated!
Regards
Smith
Edit: one last question. It's killing me finding all the WVGA dependencies for this package, they're all vga is appears. This is what I'm using: http://forum.xda-developers.com/showthread.php?t=797602
and when it lists the "required packages" when I download it it's labled VGA, not WVGA, and I think that'll be a problem. Will it?
Right, cooking sense is not my strongest point so I will probably leave it to others to take it further, but
Modules vs files - you need one or the other I think. Look up recmod and reversemod.
I just used a set of Manila files uploaded and CFC'd by someone from the latest official LEO ROM.(By Patensas I think) and maybe updated the HTC framework as well.
crazyC said:
Right, cooking sense is not my strongest point so I will probably leave it to others to take it further, but
Modules vs files - you need one or the other I think. Look up recmod and reversemod.
I just used a set of Manila files uploaded and CFC'd by someone from the latest official LEO ROM.(By Patensas I think) and maybe updated the HTC framework as well.
Click to expand...
Click to collapse
Alright, so I've figured out which packages I need to recmod and have done so. I haven't found those leo files yet, but I'm looking. Just got home. I'll post back when I see how that goes!
Regards
Smith
I have never had to recmod any of the sense files.
What you need to do is delete the files (ie the .dll) within the module. The kitchen will use the module to create the file on the device, it does not need the file as well. Hence the kitchen is giving the warning.
I think.
Hi, just re read your first post.
Could you confirm you have done the following:
Dumped the ATT base rom and rebuilt using just that with the EXTs that came from it, flashed it, and checked it worked? (So you should have had a working Sense in that) as per the Oskitchen instruction set?
If there have been problems with that, try ticking the box next to recmod on the Phone Canvas Enhancement package. I think there was an issue with the ATT ROM around this.
crazyC said:
Hi, just re read your first post.
Could you confirm you have done the following:
Dumped the ATT base rom and rebuilt using just that with the EXTs that came from it, flashed it, and checked it worked? (So you should have had a working Sense in that) as per the Oskitchen instruction set?
If there have been problems with that, try ticking the box next to recmod on the Phone Canvas Enhancement package. I think there was an issue with the ATT ROM around this.
Click to expand...
Click to collapse
Yeah, I did that. Here's the weird part though. That worked the first time. But after having all these difficulties, seeing as I haven't made much real progress, I rebuilt my kitchen. Then it wouldn't work. I would get the exact same runtime error, eventhough it worked before and I've installed all the libraries.
So, as of now the problem lies somewhere with my kitchen. I'm trying to troubleshoot it right now.
Any ideas as to why that might be? I've tried the FAQ's in the OSK thread and haven't fixed the problem :/
Regards
Smith
No sorry.
I had some kitchen problems when upgrading from oskitchen 1.32 (tried to completely reorganise my EXTs at the same time and it went horribly wrong), so went back to 1.32 to sort it out and will upgrade in due course.
If platform rebuilder crashes during the build then you dont need to waste time flashing.
Disable all EXTs and build and then add them in blocks till you identify what is causing the crash.
If it crashes with no EXTs then try the original sys, and if no joy reimport the rom?
Are all the recommended packages ticked for Recmod?
smithisize said:
Alright, so I've figured out which packages I need to recmod and have done so. I haven't found those leo files yet, but I'm looking. Just got home. I'll post back when I see how that goes!
Click to expand...
Click to collapse
I can't help you on Sense, as I don't use it, but why would you recmod anything? That's a bad idea. If you have a 6.5 kernel, use it.
crazyC said:
No sorry.
I had some kitchen problems when upgrading from oskitchen 1.32 (tried to completely reorganise my EXTs at the same time and it went horribly wrong), so went back to 1.32 to sort it out and will upgrade in due course.
If platform rebuilder crashes during the build then you dont need to waste time flashing.
Disable all EXTs and build and then add them in blocks till you identify what is causing the crash.
If it crashes with no EXTs then try the original sys, and if no joy reimport the rom?
Are all the recommended packages ticked for Recmod?
Click to expand...
Click to collapse
Actually recmodding ATT Phone Canvas fixed the problem.
I was able to generate the ROM image with sense 2017 cooked in, but sense won't launch now. "Tap to Start Sense" so I'm double checking dependencies, exe and dll files as we speak.
Thanks a lot for all the help!
Regards
Smith
So i got sense 2017 to at least load. now, however, none of the softkeys work, and tapping on a message in the message tab doesn't work.
So far so good. lots of learning to do yet, but I'll get there.
Thanks a lot for al the info!
Regards
Smith
Alright, I can't get sense to work again lol. It just kinda stopped, eventhough I'm using the same packages for manila and its dependencies.
Any ideas?
Regards
Smith
Does anyone know how to cook sense with old kitchen style(build os) for Omnia II?
Thanks in advance