lg expo forum
Find Your Forum
  
Welcome, Guest. Please login or register.

News: Do you like LG eXpo?
Advanced search
Get invisibleSHIELD for LG eXpo      Scratch Protector for LG eXpo      Hottest Ringtones for LG eXpo Awesome Price on AT&T phones
Pages: 1 ... 3 4 [5] 6
Print
Topic: How to Cook ROMs using Spocky's Kitchen  (Read 6902 times)
zalooa
Jr. Member
**

Cookies: 1
Offline Offline

Posts: 92


View Profile
« Reply #60 on: May 03, 2010, 02:25:27 AM »

I am out of ideas, i can not get past platform builder, it keeps giving the error

System.ArgumentException: Item has already been added. Key in dictionary: 'device'  Key being added: 'device'

I got it when building, never happened b4, couldnt get rid of it. Completly redump/ported build worked randomly off and on. Now i cant get it to work at all...

I have no idea :S.

Alright Jug6ernaut I had this exact issue too first i was using windows 7 x64 it did this exact problem then i switched to my XP 32 it still did this problem but i noticed one thing. If i ran Erviuskitche.exe through the start.bat option E it gave me this trouble. When i ran erviuskitchen.exe in the kitchen root folder i never got this problem again. I dont know why or how but definately its working for me with that trick see if that helps.

@ eviltuna
i was using windows 7 x64 then i switched to xp 32 and im getting at least some results of course the dreaded issues ur having too but at least its compiling. I have looked all over xda and abroad and the problem might be as Dark described the XIP.bin file it contains important stuff the real question now is how does it get corrupt or why the dumping process corrupts the xip.bin file. Another issue and this is a MAYBE is that the DSM files located in i guess every folder containts a list of the contents of that folder. if we were to say delete monopoly.exe from the sys/oemmisc folder then i suspect that the DSM file still thinks monopoly.exe is there even though it isnt? its just a thought i am sure we are on the brink of success like Dark has managed to do but still gotta find that little issue haha
Logged
eviltuna
Newbie
*

Cookies: 0
Offline Offline

Posts: 13


View Profile
« Reply #61 on: May 03, 2010, 03:24:56 AM »

Well I'm just glad its not just me or I'd feel like a pretty big idiot, anyways haven't had the time to figure it out yet, but I'll take a look hopefully this week. Looking at the log file though, it does look like its adding everything right, as the modules in the OEMDrivers directory are being added to the rom so I'm not sure whats wrong, I'm sure its just a problem with 1 of the config files.
I am out of ideas, i can not get past platform builder, it keeps giving the error

System.ArgumentException: Item has already been added. Key in dictionary: 'device'  Key being added: 'device'

I got it when building, never happened b4, couldnt get rid of it. Completly redump/ported build worked randomly off and on. Now i cant get it to work at all...

I have no idea :S.

Alright Jug6ernaut I had this exact issue too first i was using windows 7 x64 it did this exact problem then i switched to my XP 32 it still did this problem but i noticed one thing. If i ran Erviuskitche.exe through the start.bat option E it gave me this trouble. When i ran erviuskitchen.exe in the kitchen root folder i never got this problem again. I dont know why or how but definately its working for me with that trick see if that helps.

@ eviltuna
i was using windows 7 x64 then i switched to xp 32 and im getting at least some results of course the dreaded issues ur having too but at least its compiling. I have looked all over xda and abroad and the problem might be as Dark described the XIP.bin file it contains important stuff the real question now is how does it get corrupt or why the dumping process corrupts the xip.bin file. Another issue and this is a MAYBE is that the DSM files located in i guess every folder containts a list of the contents of that folder. if we were to say delete monopoly.exe from the sys/oemmisc folder then i suspect that the DSM file still thinks monopoly.exe is there even though it isnt? its just a thought i am sure we are on the brink of success like Dark has managed to do but still gotta find that little issue haha
Logged
Jug6ernaut
Full Member
***

Cookies: 6
Offline Offline

Posts: 166



View Profile
« Reply #62 on: May 03, 2010, 03:30:56 PM »

wow ur exactly right, man i was so close to going insane...thank xD
Logged

LG Monaco/LG Expo
-------
HTC Raphael/AT&T Fuze
-------
HTC Kaiser/AT&T Tilt
-------
HTC Wizard/Cingular 8125

"If your not smart enough to make your own rom, you are smart enough to fuck up someone elses"[
Dark
Administrator
Hero Member
*****

Cookies: 41
Offline Offline

Posts: 885


Do you see my memories?


View Profile
« Reply #63 on: May 03, 2010, 10:18:21 PM »

What's in the DSM files shouldn't really matter. I didn't touch any of the DSM files.
Logged

My LG eXpo:
Purchased: 12/17/09
InvisibleShield
Black Leather carrying case
GPS: Garmin XT
BlueAnt T1 bluetooth headset
Pico Projector

ROM: Dragonstorm 23139 for the eXpo

Woodhole's eXpo/IQ Tweaker
zalooa
Jr. Member
**

Cookies: 1
Offline Offline

Posts: 92


View Profile
« Reply #64 on: May 04, 2010, 05:13:47 AM »

Alrighty I figure ill go through the tutorial here with everyone so we can see if there was anything we missed its like i memorized it haha.

Anyway
First well need the stock rom which we can get from this website.
Second we need to download the kitchen and extract it anywhere hopefully on an XP 32 bit system as discussed earlier.
Third stick the stock rom .dz file that we acquired into the baserom/gw820
Its at this point we are going to be DUMPING the rom so we launch the Start.bat
we need to select 7 so the dumper recognizes our expo
we will then execute options a, b, c


Thats part C there are some interesting issues that have occurred.
  5.2.21749  5028 Phone_dpi_192_resh_480_resv_800
  5.2.21749  5028 Phone_Lang_0409_DPI_192
  5.2.21749  5028 PhoneRedist_Lang_0409
  5.2.41200  5028 OEMDrivers
  5.2.21749  5028 CommonNonEA
  5.2.41200  5028 OEMMISC
  5.2.41200  5028 OEM_DPI_192
  5.2.41200  5028 OEM_Lang_0409
Different Builds here not sure if they are relevant

[Missing Manifests]
  d92a4f0a-378a-4482-8fd3-bd127a05e4de.dsm
  723fb954-d931-4348-b672-82a188e587b5.dsm
  161efb55-1b5b-2e9b-a36b-3880a74d745a.dsm
  3346da5d-3675-4a67-925e-75f623184bda.dsm
  b00d0fcf-0459-5ea5-d217-f50a2e1ce607.dsm
Maybe important maybe not

The next steps can be followed using dark's awesome tutorial
the only small note is that in step f the folder the files should be transferred too is the temp/dump/SYS/0409 instead of temp/dump/0409 as there is not 0409 folder in the dump folder.
When all is said and done and assuming we make NO CUSTOMIZATIONS AT ALL just to test out rebuilding process
We continue with step d
dump the xip.bin file
and then we will transfer the wince.nls file. and continue on with the oemxipkernel folder and msxipkernel folder stuff moving them around and so forth
Now at this point DONT press e as it seems me and other people are getting an unhandled exception instead go the root of the kitchen and open erviuskitchen.exe and select the Real WM 6.5 AKU as this tells the rom is an ORIGINAL 6.5 rom because of the increased memory slot capacity that only 6.5 has versus 6.1 very important to have this. Next make sure everything is green in the XIP SYS and OEM the rest is optional packages which we will worry about if we can get it to work first haha
Then the xip build and sys build should be the same number the rom VERSION should be changed based on a recommendation at XDA but i didnt see a difference so thats up for grabs the rom res should be dpi_ so forth and so on
then hit create rom
at this point you should not get any errors at all if running in xp 32 bit also if there is an error  related platformrebuilder.exe that is a simple fix the following line should be added to the kitchen_build_rom.bat
the lines
REM ****************     TOOLS\platformrebuilder.exe
if not "%errorlevel%"=="0" goto error
should be
REM ****************     TOOLS\platformrebuilder.exe
REM ****************    if not "%errorlevel%"=="0" goto error

Boom fixes that issue credits are once again at xda sorry forgot where exactly but it fixed that minor issue.
The next step is simply
f, g, h while naming the rom without spaces
Boom you will have  your "rom" in the buildrom folder in the root of the kitchen. Thats what i did and it seems that im getting some issues with other people. If anyone can add or tell me what im doing wrong that would roxors. not that darks 21901 isnt awesome of course!!!
Credits to most of the info i got from Dark's tut and XDA. The rest is painstaking hours of research haha trying to figure out LG's shenanigans. The log of the dump is attached see if yours matches mine i used the same option a, b , c so we should have the same Right!?!?!??! haha
Logged
Jug6ernaut
Full Member
***

Cookies: 6
Offline Offline

Posts: 166



View Profile
« Reply #65 on: May 04, 2010, 10:32:35 AM »

hmm, im starting to think that the kitchen isnt handling modules right...
Logged

LG Monaco/LG Expo
-------
HTC Raphael/AT&T Fuze
-------
HTC Kaiser/AT&T Tilt
-------
HTC Wizard/Cingular 8125

"If your not smart enough to make your own rom, you are smart enough to fuck up someone elses"[
zalooa
Jr. Member
**

Cookies: 1
Offline Offline

Posts: 92


View Profile
« Reply #66 on: May 07, 2010, 03:43:06 AM »

Question for Dark
     MSXIPKernel from ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build #
     (eg. 23563). Paste MSXIPKernel into that folder. It is important both folders are named the same.
in this part of your tutorial what do you mean both folders must be named the same
also there is already a buildnumber in this folder do we delete that one and create our own?
Logged
zalooa
Jr. Member
**

Cookies: 1
Offline Offline

Posts: 92


View Profile
« Reply #67 on: May 09, 2010, 05:45:12 AM »

Alright so i was thinking what Dark said about the xip.bin file. I wouldnt think to look at it because i wanted the exact same build just junk removed right. So the thing is that you have to do STEP 8 in this tutorial even if it is the SAME BUILD. I got the idea browsing XDA it turns out there is a forum for our little dragon. A poster said that he did step 8 even though he didnt do a different build so i tried to implement it and it actually worked the phone is back to its correct state from Dump of original rom and Cook. It went out and came in perfectly. VERY VERY Strange solution in my opinion why would we need to go through step 8 even though we are making the SAME build very wierd but doesnt matter whats done is done

So how do we do this without a NEW xip.bin file or build? On step 8 you will literally use the exact same xip.bin file located in the tools/xipport folder. its almost like i "pretended" to build a new rom build but i didnt. follow the steps to the T and Voila it worked HOLY CRAP BATMAN!!!! Dark you da Man. Go SnapDragon. Now the cooking can begin if anyone needs exactly what i did to the t let me know ill give you exactly what i did and luckily it worked.
Logged
Dark
Administrator
Hero Member
*****

Cookies: 41
Offline Offline

Posts: 885


Do you see my memories?


View Profile
« Reply #68 on: May 09, 2010, 07:24:39 PM »

Question for Dark
     MSXIPKernel from ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build #
     (eg. 23563). Paste MSXIPKernel into that folder. It is important both folders are named the same.
in this part of your tutorial what do you mean both folders must be named the same
also there is already a buildnumber in this folder do we delete that one and create our own?

Here is the part you are referring to:
10. Go to the ROM\GW820 folder. You will see a XIP folder. Go into that folder and then go into the
     WinCENLS_WWE folder and copy the wince.nls file. Now go into the OEMXIPKERNEL and paste
     wince.nls in there. After that copy the OEMXIPKERNEL folder. Next create a folder in ROM\GW820 and
     name it your build # (eg. 23563). Now paste OEMXIPKERNEL into that folder. After that copy
     MSXIPKernel from ROM\GW820\XIP. Go to ROM\SHARED and create a folder and name it your build #
     (eg. 23563). Paste MSXIPKernel into that folder. It is important both folders are named the same.

Now in this step you are only creating 2 folders. When I say it is important both folders are named the same I am referring to the 2 folders you create in this step.

As for the folder already in ROM\SHARED, just delete it. It was an old folder that spocky left in the kitchen from another build.
Logged

My LG eXpo:
Purchased: 12/17/09
InvisibleShield
Black Leather carrying case
GPS: Garmin XT
BlueAnt T1 bluetooth headset
Pico Projector

ROM: Dragonstorm 23139 for the eXpo

Woodhole's eXpo/IQ Tweaker
Dark
Administrator
Hero Member
*****

Cookies: 41
Offline Offline

Posts: 885


Do you see my memories?


View Profile
« Reply #69 on: May 09, 2010, 07:30:15 PM »

Alright so i was thinking what Dark said about the xip.bin file. I wouldnt think to look at it because i wanted the exact same build just junk removed right. So the thing is that you have to do STEP 8 in this tutorial even if it is the SAME BUILD. I got the idea browsing XDA it turns out there is a forum for our little dragon. A poster said that he did step 8 even though he didnt do a different build so i tried to implement it and it actually worked the phone is back to its correct state from Dump of original rom and Cook. It went out and came in perfectly. VERY VERY Strange solution in my opinion why would we need to go through step 8 even though we are making the SAME build very wierd but doesnt matter whats done is done

So how do we do this without a NEW xip.bin file or build? On step 8 you will literally use the exact same xip.bin file located in the tools/xipport folder. its almost like i "pretended" to build a new rom build but i didnt. follow the steps to the T and Voila it worked HOLY CRAP BATMAN!!!! Dark you da Man. Go SnapDragon. Now the cooking can begin if anyone needs exactly what i did to the t let me know ill give you exactly what i did and luckily it worked.

Glad you got it working. That is very strange. When I tested the kitchen for spocky I was able to rebuild the stock rom without step 8 since it was only for porting, but if it works then I say do it. Once again glad to hear you got it working.
Logged

My LG eXpo:
Purchased: 12/17/09
InvisibleShield
Black Leather carrying case
GPS: Garmin XT
BlueAnt T1 bluetooth headset
Pico Projector

ROM: Dragonstorm 23139 for the eXpo

Woodhole's eXpo/IQ Tweaker
equivocation
Newbie
*

Cookies: 0
Offline Offline

Posts: 43


View Profile
« Reply #70 on: May 09, 2010, 09:02:22 PM »

Alright so i was thinking what Dark said about the xip.bin file. I wouldnt think to look at it because i wanted the exact same build just junk removed right. So the thing is that you have to do STEP 8 in this tutorial even if it is the SAME BUILD. I got the idea browsing XDA it turns out there is a forum for our little dragon. A poster said that he did step 8 even though he didnt do a different build so i tried to implement it and it actually worked the phone is back to its correct state from Dump of original rom and Cook. It went out and came in perfectly. VERY VERY Strange solution in my opinion why would we need to go through step 8 even though we are making the SAME build very wierd but doesnt matter whats done is done

So how do we do this without a NEW xip.bin file or build? On step 8 you will literally use the exact same xip.bin file located in the tools/xipport folder. its almost like i "pretended" to build a new rom build but i didnt. follow the steps to the T and Voila it worked HOLY CRAP BATMAN!!!! Dark you da Man. Go SnapDragon. Now the cooking can begin if anyone needs exactly what i did to the t let me know ill give you exactly what i did and luckily it worked.


Awesome, I can confirm it works flawlessly.
Logged
zalooa
Jr. Member
**

Cookies: 1
Offline Offline

Posts: 92


View Profile
« Reply #71 on: May 10, 2010, 05:29:56 AM »

Yes i agree strange but it worked its flawless now the amount of customizing power just went sky high

Some good places to edit
initflashfiles.dat
this has all the locations of FILEs it controls the structure of the windows phone. the OEMMISC folder has all the files int he windows directory well most of them this is where u need to gut FIRST! hopefully u have great builds to come with more tips just post them i guess in a new post.
Logged
Jug6ernaut
Full Member
***

Cookies: 6
Offline Offline

Posts: 166



View Profile
« Reply #72 on: May 10, 2010, 02:26:22 PM »

if anyone has a gutted oemmisc i would love a copy, mine has the barest of dlls in it to run windows right now hehe.
Logged

LG Monaco/LG Expo
-------
HTC Raphael/AT&T Fuze
-------
HTC Kaiser/AT&T Tilt
-------
HTC Wizard/Cingular 8125

"If your not smart enough to make your own rom, you are smart enough to fuck up someone elses"[
Dark
Administrator
Hero Member
*****

Cookies: 41
Offline Offline

Posts: 885


Do you see my memories?


View Profile
« Reply #73 on: July 12, 2010, 12:09:33 AM »

I just posted an add-on package for the eXpo. It is based on the V10g update.
Logged

My LG eXpo:
Purchased: 12/17/09
InvisibleShield
Black Leather carrying case
GPS: Garmin XT
BlueAnt T1 bluetooth headset
Pico Projector

ROM: Dragonstorm 23139 for the eXpo

Woodhole's eXpo/IQ Tweaker
catiesman
Newbie
*

Cookies: 0
Offline Offline

Posts: 3


View Profile
« Reply #74 on: July 26, 2010, 10:50:33 AM »

Hello all,

I have been able to use the kitchen as described here to successfully rebuild the stock ROM (V10g - 21749) and add/remove packages without issue.  However, I've tried multiple times to port a new XIP/SYS build and every time I get the same result: the phone hangs at the orange "Windows" logo screen and won't get past it.

Can anyone point me to what I might be doing wrong?  I've checked for and corrected duplicate packages:
 - The SMS_Providers package was in the OEMDrivers folder from the ROM dump and was a SYS package on the new build, so I tried both disabling the SMS_Providers package and moving the stock one to a SYS package (so there wouldn't be a conflict)
 - The GPSID and Bluetooth (or maybe BTDUN - I don't remember which) conflicted and so I disabled (even removed at one point) those from my new SYS build

I even went as far as to write a small C# program that would analyze the new SYS directory and find ANY and ALL duplicated modules, and they all wound up being in one of the packages mentioned above.

Short of literally copying the SYS packages one at a time from the new build to the old build until I see what breaks (and even that probably won't be a good test since I'd have a "hybrid" SYS folder), I'm completely out of ideas.

My only remaining suspicion at this point (and I don't know how to troubleshoot this) is that there is something wrong with the .ROM or .VM "packages."  My new build only has a .ROM folder, not a .VM folder, and I've tried all combinations: deleting it entirely from the new SYS build as well as copying one and both folders from the dumped 21749 SYS directory, and still no luck.

Any help would be greatly appreciated......  Thank you!
Logged
Pages: 1 ... 3 4 [5] 6
Print

Jump to:  

Got a new phone? Find the forum here


Related Topics
Subject Started by Replies Views Last post
Modified LG Kitchen for GW820/GW825 « 1 2 3 4 »
ROM development..
eviltuna 53 5581 Last post May 16, 2010, 04:28:17 PM
by dalb3
[Request] XDA UC in new roms
ROM development..
godashram 2 582 Last post September 06, 2010, 01:33:37 AM
by RogueCheddar
LG-GW825V -->>>Hong Kong version, how to cook ROM for myself?
ROM development..
ken_nx 6 1527 Last post September 20, 2010, 12:30:19 AM
by ken_nx
LG IQ ROMs and Other Questions.
ROM development..
EricGrain 4 982 Last post January 04, 2011, 10:59:34 PM
by EricGrain
We need new ROMs and WM7 sucks!!
ROM development..
ewarez 3 1565 Last post November 26, 2011, 05:16:40 AM
by mobiad




Thanks for visiting LG Expo Forum Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC Sitemap

Galaxy Note | Samsung Galaxy Nexus | Kindle Fire | Atrix 4G | Motorola Xoom | Windows Phone 7
Nokia Lumia | Top Hosts | Samsung Galaxy Tab | Samsung Galaxy S2 | Samsung Galaxy S | Samsung Wave
HTC Evo 3D | HTC Evo 4G | HTC Incredible | HTC Incredible 2 | HTC Incredible S | HTC Thunderbolt
Motorola Droid Razr
| HTC Desire | HTC Desire HD | HTC Desire Z | HTC Desire S | HTC Wildfire
Motorola Droid | Galaxy Indulge | Nokia N8 | Droid Charge | Droid X | Droid X2 | Droid 2| Droid 3 | Fascinate
HTC Sensation | HTC Flyer | LG Revolution | Asus Transformer | Xperia Play | iPhone 4 | Nexus S | Droid Bionic
HTC Wildfire S | HTC Droid Eris


This is an Un-Official fan based Website. The views expressed on this website are solely those of the proprietor, or contributors to the site, and do not necessarily reflect the views or opinions of the parties it covers, and is not affiliated with, endorsed or sponsored by parties involved.
If you have a problem with any of the content posted on this website, please contact "sales@verticalscope.com"
Term of Use | Privacy Policy | BlackRain 2006 by, Crip