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 all, I post this little apps that maybe can help you if you want dump a protected rom (not all, obviously.....) but in some cases it can help.....
how it works:
put a .payload or a .nb file in the same folder of the app, open a command prompt and write:
rom_deprotector os.nb
or
rom_deprotector os.nb.payload
where os.nb / os.nb.payload is the name of your target file.....
wait and finger cross that the target file was protected in a way known by my apps, if my apps "deprotect" the target file, you can dump it then
good lock.....
version 2 a bug on output string solved!
There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?
chavonbravo said:
There are a couple different ways to protect a rom. Which method does this one unprotect? imgfs signature mod? file/module header swap?
Click to expand...
Click to collapse
there are other ways to protect roms, not only theese 2, bwt... it deprotects the 1st one that you told......
so, maybe an old wise will be able to build another "new???" rom.....
haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.
conflipper said:
haha very nice tool, i am yet to test this out, but it looks very nice. I am going to go out an guess that you and UDK are about 4 steps ahead, and have already been using new ways to protect your roms.
very nice work though once again. you never stop amzing everyone with the work you do.
Click to expand...
Click to collapse
what about???
did it work well???
Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?
@ervius
Amazing achievement,,,
How can I tell the type of protection added on the rom? Is there a way to find out which rom is capable to be deprotected by your method?
And if you don't mind, I think your tool can be useful as relatively handy to my thread here
johnpatcher said:
Maybe I'm doing something wrong, but it doesn't seem to work for me.
I have extracted the nb file out of a nbh file (using NBHextract). Now I try to execute "ROM_Deprotector.exe os.nb" (whereas "os.nb" is the name of my nb file).
But nothing is happening, the command is executed (that means I can type in a new command), but the file stays untouched, and the computer isn't working at all.
What am I doing wrong?
Click to expand...
Click to collapse
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
if my apps "deprotect" the target file, you can dump it then
Click to expand...
Click to collapse
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?
NOBELOVE said:
I tested couple of roms and same results keep happening to me.
@ervius,,, would you mind share the details of handling one sample rom as a tutorial to understand this method better?
How can i tell if the file got deprotected successfully, and can you explain how you dump it after all?
Click to expand...
Click to collapse
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!
ervius said:
try version 2 attacked to the 1st post!!!!!
to see if it works, try to dump, for example a DIB rom (os.nb), then use deprotector and try to redump it..... to see if rom_deprotector works...
bye!
Click to expand...
Click to collapse
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?
So am I. The initiative is so great. I had tested with most ROMs out there but didn't have luck at all. Does not matter you use nb or payload.
Hope you find a real way to break it!
hugs
Ameet said:
This rom deprotector doesnt work on my ROMs My ROMs are cooked in your visual kitchen Any ideas ervius?
Click to expand...
Click to collapse
If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.
conflipper said:
If i rememember right Bepe new kitchen, what ervius is based off, it takes the apps.reg and inserts that into the hives, and so you can not decompile it.
also i think this tool just reconstructs the imgfs start address if a chef decided to mess up the imfgs address.
Click to expand...
Click to collapse
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!
ervius said:
yes, you are right!
bepe kitchen produces a dumpable rom, but unusuable to rebuild new roms!
bye!
Click to expand...
Click to collapse
Oh ok. Now I get it. So the tool only reverses the protection which is done on the ROM IMGFS header to make it really undumpable. Right? You right about Bepe's kitchen producing dumpable ROMs but due to lack of dumped DSMs & RGUs the ROM is not re-packagable Cool.. Now I get the drift
Mind sharing how to protect the ROM so can be documented in the tutorials?
Used your deprotect tool, it said deprotection done successfully.
But after dumping bepe's rom, all file names, sizes are correct.
Some files, e.g. .lnk files are correct too.
But all .dll and .sys files are all zero padded, and unusable.
if
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?
joshkoss said:
we provide you with updated ways roms get protected are you up for updateing this sweet little tool?
Click to expand...
Click to collapse
sorry for late.....
no, becouse there are a lot of protection, and I don't know all of them... maybe.....
bye!
Dear Ervius
amd NOOB
will this tool will work with ur kitchen build roms. casue when I try to dump ur kitchen's build rom (which is CRACING's wm 6.5 23034 rom) through visual kitchen's build 1.8.1 .. its just build ur kitchen's structure but did nothing with sys, oem and ext folder.. its just resume language as 0000 and dpi as 00
please help me.. I tried ever rom in it. but didnt get result yet
hi all..
we all have suffered from one common things while making a rom..
after all your hard work and spending so much time and reading on and on for improvements u encounter this
stuck at smart mobility
so i request all people who faced such problems and have solved them,,plz write here about it..
what u have done..??
what is the cause??
this will easier for lots of people to understand why they have non booting rom..
so afterall i got this solution..
1.Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
byDOTCOMPT
2.if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system.
byTWOPUMPCHUMP
3.recmod ALL modules in your EXT folder
recmod these three folder in sys...browsing, browsingcore, and browsingie
BYTWOPUMPCHUMP
4.ALSO SEE THE ATCHED TXT FILES BY KOKOTAS FOR WHICH FILE TO RECMOD ON PAGE 3
This could be caused by many things.
I suggest you check all last changes you did, which packages/edits etc...
Before I edit my kitchen I always make sure I have a backup incase stuff like this happens so I can refert back.
I recommend editing step by step and not edit to many things at once.
Grtz Leo
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
kokotas said:
Totally agree with Laurentius.
Just some points to look:
1.wince.nls
2.XIP
3.boot.rgu
4.UPXed files
Best Regards!
ps:A Hard Reset would be nice after flashing
Click to expand...
Click to collapse
almost done..
ok i made a rom 23544..works like a charmm..
but i just upgrade new build like 23548,49,52
all have non booting issue..
no changes have been made from 23544 build not even new application added..
but no luckk.
checked wince..found xip is ok..
also done recmod but no luck..
so now???
i tell u what i just change build 23544,,i got bootable rom..then just chang build ..48..49
non bootable rom
Try XIP 23544, SYS 23548,49,52.
Maybe a bad XIP source?!
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Laurentius26 said:
If you change to a new MS build you only need MSXipkernel plus SYS.
No recmod is needed, I never use recmod.
Try playing with wincenls, move it from SYS to XIP or maybe viceversa.
Click to expand...
Click to collapse
but without recmod the kitchen even not building a rom
That's weird, the kitchen should run without recmodding modules.
Maybe you have a conflict in your kitchen where a file is overwriting a module?
saurabh88 said:
but without recmod the kitchen even not building a rom
Click to expand...
Click to collapse
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
twopumpchump said:
so your rom gets stuck at first screen, with radio info ect on bottom of screen? what modules are you recmodding? do you have hidden and system files visable on your pc? what kitchen are you using? there are alot of things that could cause your rom not to boot, the more info you give the easier it is to help
Click to expand...
Click to collapse
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
Make sure the following packages are cooked:
. NetCF or NetCF 3.5
. Dummy FWUPDATE
. Dummy SQM
. WinCENLS_WWE
Could you post your Build_log.txt here.
-
saurabh88 said:
i use evk..
other things i have already stated before that with same kitchen i can make rom of 23544;but what the fkkkk..i just change build to23548;4951 non bootibg rom...
strange but true.
i just use extra button in evk to recmod as someone already made a post to use extra button via batch file..
Click to expand...
Click to collapse
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
twopumpchump said:
then obviously something different has been done with the newer builds you are trying to use that wasnt done with 23544. did you recmod 23544 the exact same way as you did the newer ones that didnt work? if your rom gets stuck on radio screen and the screen doesnt dim after a lil bit then you have problem with xip...if the screen does dim it usually means a problem with system. you can use beyond compare to compare the working build to the non-working one, if there is something different you will be able to tell.
Click to expand...
Click to collapse
yes screen does not dim..
so what is your suggestion??
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
saurabh88 said:
yes screen does not dim..
so what is your suggestion??
Click to expand...
Click to collapse
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
kokotas said:
Then XIP(MSXIPKernel) is probably the cause.
Did you try a different XIP or a combination of XIP(MSXIPKernel) 23544 and SYS 23548 as I told you before?
From where did you get the 23548-49-52 builds?
Maybe you should download them again?
Best Regards!
Click to expand...
Click to collapse
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
twopumpchump said:
thats why i asked if you have hidden and system files showing on your pc...maybe you left some files/dsm/rgu out of msxipkernel.
Click to expand...
Click to collapse
ok i will compare them and see.l
saurabh88 said:
yes did it but no luck.....
i download them from da_g thread..
if u can plz give me the link of them to dwnld again
Click to expand...
Click to collapse
Have you tried the 23554 that I posted (It is in my Rollups folder, link can be found in NRGZ sticky in this forum)
build log of 23554
still stuck at smart mobility,,,here i attached file plz someone look at it and help me...
i have just sorted them through dump sorter..
Saurabh: see also this post by twopumpchump: http://forum.xda-developers.com/showpost.php?p=6032341&postcount=14
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
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