WM 6.5 Kitchen QVGA and VGA Developer Edition - Page 388

**Young_breedent** · #**3871** (**permalink**) 05-14-2009, 04:34 PM

Quote:

Originally Posted by Zecanilis

Which xip are you using? Have you ever cooked before or is your first time?

I've cooked before but i have never cooked when having to add my own xip and sys if that makes sense. Usually the files are already there and i just make my selections and cook. I am using the xip that was provided a few posts back by Merdinh

Zecanilis · #**3872** (**permalink**) 05-14-2009, 04:41 PM

It doesn't even go to windows bootscreen? If not that looks like a xip thing...
Is your PRO also CDMA?

**savior02** · #**3873** (**permalink**) 05-14-2009, 04:56 PM

Quote:

Originally Posted by Young_breedent

I've cooked before but i have never cooked when having to add my own xip and sys if that makes sense. Usually the files are already there and i just make my selections and cook. I am using the xip that was provided a few posts back by Merdinh

all u do is replace the rom folder and sys folder in the kitchen..im using calkulins kitchen and im getting the same problem wont boot...i think the rom folder isnt working unless some one else has it working which i would like to know

**SOHKis** · #**3874** (**permalink**) 05-14-2009, 05:07 PM

sounds like XIP issues, have you guys ported the xip from da_g's dump?

decibel · #**3875** (**permalink**) 05-14-2009, 05:21 PM

Quote:

Originally Posted by Young_breedent

Has anybody successfully built a rom for the touch pro with the new build?? I put the sys and the xip in JD's kitchen and can't seem to get pass the boot screen. Any help would be greatly appreciated. Thanks in advance

I don't use JD's kitchen. So I can't help you with that. But I do have a fully booting 21231 with 21231 XIP. All courtesy of Da_G. I recmod'd my usual BrowsingIE and BrowsingCore modules. I also recmod'd 4 other files that get an I/O error 105 in G'Reloc. They get it every time, no matter what SYS build, same files. Then My G'Reloc passes without fail. Of course, don't include Sky* crap. There is a problem with the Myphone.exe lang module (like always). I also don't include other crap that isn't needed. Sim_TKIT, ADC, WelcomeCenter, etc.

Quote:

Originally Posted by conflipper

That was last febuary, I am sure there are more then that now. So going by that, it looks like there is a lot of 96dpi devices in testing.

The big thing would be WWE, but I have a feeling we will be getting more and more of those.

Thanks Da_G and con. I stand corrected. I think i was thinking "in production" as that would be all they would develop for. Didn't think about what was in their test environments. Muh bad.

Quote:

Originally Posted by savior02

i have used the above sys and rom and im getting a G'reloc error says not valid integer.....anybody have this working?

See my above comment.

Quote:

Originally Posted by Young_breedent

CAN someone please help me with building a rom for my touch pro???? I am using JD's kitchen and can't get pass the boot screen.

Same. See my above comment.

Quote:

Originally Posted by indagroove

I haven't had to recmod browsui.dll or dxtrans.dll in the browsingie folder. I did also recmod webview.dll in the browsing folder.

Just a habit for me. I have a batch file that recmod's them all. It also does other modules by giving me a menu and letting me enter the path of the module. I love me batch files. Right Da_G?

Quote:

Originally Posted by SOHKis

sounds like XIP issues, have you guys ported the xip from da_g's dump?

I agree. Probably a XIP issue. I have found that in the latest build of XIP (21222), if i included HD.dll, mencfilter.dll and some other .dll it would cause VZW users no boot. I remove those and presto, they boot. But I am using Da_G's exact 21231 XIP (copy and pasted his MSXipKernel folder from his kitchen to mine) and I boot without issues. So I don't think it pertains to this situation. It might be a bad sys. Do the lights on the navi pad light up when you get "no boot"? Usually if the lights come on, its not a XIP issue. No LIghts = stuck during XIP.

**indagroove** · #**3876** (**permalink**) 05-14-2009, 05:50 PM

Quote:

Originally Posted by decibel

I agree. Probably a XIP issue. I have found that in the latest build of XIP (21222), if i included HD.dll, mencfilter.dll and some other .dll it would cause VZW users no boot. I remove those and presto, they boot. But I am using Da_G's exact 21231 XIP (copy and pasted his MSXipKernel folder from his kitchen to mine) and I boot without issues. So I don't think it pertains to this situation. It might be a bad sys. Do the lights on the navi pad light up when you get "no boot"? Usually if the lights come on, its not a XIP issue. No LIghts = stuck during XIP.

The lights coming on or not is a good point. I think that folks are a little quick to blame the XIP sometimes when it won't boot past the first splash. I know that personally I have had several builds which I initially thought were XIP issues that really were a combination of SYS/XIP. I think the big problem is that the CDMA Diamond and TP XIPs can't handle all the modules that the newer SYS have, because the new SYS' are based on XIPs with more available slots.

At any rate, not booting past the first splash screen may or may not be a bad XIP. Don't get stuck on that. Strip down your SYS to the bare essentials, and recmod the browsing dlls as suggested, and give it another go.

decibel · #**3877** (**permalink**) 05-14-2009, 05:58 PM

Quote:

Originally Posted by indagroove

The lights coming on or not is a good point. I think that folks are a little quick to blame the XIP sometimes when it won't boot past the first splash. I know that personally I have had several builds which I initially thought were XIP issues that really were a combination of SYS/XIP. I think the big problem is that the CDMA Diamond and TP XIPs can't handle all the modules that the newer SYS have, because the new SYS' are based on XIPs with more available slots.

At any rate, not booting past the first splash screen may or may not be a bad XIP. Don't get stuck on that. Strip down your SYS to the bare essentials, and recmod the browsing dlls as suggested, and give it another go.

Precisely! This is why I use my .VM from a dumped TP rom to run a G'Reloc on the SYS first. This will mostly eliminate a bad SYS issue from a module being too large to fit into the memory allocations. Then I look at XIP as being a culprit by having too many modules that the CDMA kernel (not 6.5 native) can't handle. Oddly, it seems the VZW has a little more of an issue with this than any other CDMA TP. I can't explain it though. That's for the guru's that know every spec and inch of these devices to explain.

**Young_breedent** · #**3878** (**permalink**) 05-14-2009, 06:03 PM

Quote:

Originally Posted by Zecanilis

It doesn't even go to windows bootscreen? If not that looks like a xip thing...
Is your PRO also CDMA?

yes it is a touch PRO

**Young_breedent** · #**3879** (**permalink**) 05-14-2009, 06:06 PM

Quote:

Originally Posted by decibel

I don't use JD's kitchen. So I can't help you with that. But I do have a fully booting 21231 with 21231 XIP. All courtesy of Da_G. I recmod'd my usual BrowsingIE and BrowsingCore modules. I also recmod'd 4 other files that get an I/O error 105 in G'Reloc. They get it every time, no matter what SYS build, same files. Then My G'Reloc passes without fail. Of course, don't include Sky* crap. There is a problem with the Myphone.exe lang module (like always). I also don't include other crap that isn't needed. Sim_TKIT, ADC, WelcomeCenter, etc.

Thanks Da_G and con. I stand corrected. I think i was thinking "in production" as that would be all they would develop for. Didn't think about what was in their test environments. Muh bad.

See my above comment.

Same. See my above comment.

Just a habit for me. I have a batch file that recmod's them all. It also does other modules by giving me a menu and letting me enter the path of the module. I love me batch files. Right Da_G?

I agree. Probably a XIP issue. I have found that in the latest build of XIP (21222), if i included HD.dll, mencfilter.dll and some other .dll it would cause VZW users no boot. I remove those and presto, they boot. But I am using Da_G's exact 21231 XIP (copy and pasted his MSXipKernel folder from his kitchen to mine) and I boot without issues. So I don't think it pertains to this situation. It might be a bad sys. Do the lights on the navi pad light up when you get "no boot"? Usually if the lights come on, its not a XIP issue. No LIghts = stuck during XIP.

can i just get your .nbh file that you cooked then so i can just flash. I'm in over my head and i definitely want to learn but i would like to play with this new build in the mean time. Also if you can give me a copy of you xip and sys that would be helpful as well. Thanks in advance

rainabba · #**3880** (**permalink**) 05-14-2009, 06:07 PM

Quote:

Originally Posted by SOHKis

i believe he is referring to de-modularizing files/folders

to do this you use redmod.exe

simply drag&drop the module you are having problems with on the redmod.exe and it will create the file w/in the module/folder.

then move the newly created file out of the module/folder, delete the module, and move the newly created file back into the folder where the module originally resided.

*here's a de-modularized BROWSINGSCORE & browsingie folders

Following this suggestion, I have 21231 working great on my TP. Prior builds had corrupted ring-tones and wouldn't launch Magicall.