[ Discontinued ][ v4.2 ][ 6.5.x / 6.5 / 6.1 ] Calkulin's Visual VGA Kitchen & ROMs - Page 64

chuckz07 · #**631** (**permalink**) 01-27-2009, 11:39 AM

Quote:

Originally Posted by Isriam

I'm not an idiot, I just haven't updated my profile. I have a touch pro on cricket. Obviously if I have an OEM that works on PPCKitchen I'm not trying to flash my "mogul" with a caulkin touch pro ROM.

Back to my question, I have a cricket OEM that works on ppckitchen just fine, however when I add it to caulkin kitchen the rom will not boot. And yes I did edit option.xml to match the other carrier OEM's in the kitchen.

Obviously I should have assumed you had a TP and not used the information I had at my disposal. I apologize for you thinking I was calling you an idiot, I was simply making clarification. I further apologize for not having more information about what you are flashing on.

Anyway, as I don't know exactly where to look for the problem, you could search for another Cricket Carrier OEM from another kitchen. It is possible that the PPCKit OEM is different in some way to work properly with that Kitchen.

Isriam · #**632** (**permalink**) 01-27-2009, 11:45 AM

This carrier OEM is from bepe kitchen. It works there also. I simply changed the "group" tag in the option.xml to read "Carriers - Select One" (NOT EXACT) to match what the other carrier oem's option.xml said.

As for the other info you're forgiven

I wouldn't post here unless I had a touch pro on a carrier not listed in caulkins kitchen.

chuckz07 · #**633** (**permalink**) 01-27-2009, 11:53 AM

Quote:

Originally Posted by Isriam

This carrier OEM is from bepe kitchen. It works there also. I simply changed the "group" tag in the option.xml to read "Carriers - Select One" (NOT EXACT) to match what the other carrier oem's option.xml said.

As for the other info you're forgiven

I wouldn't post here unless I had a touch pro on a carrier not listed in caulkins kitchen.

Ok, one more thing you can try (and I know this from testing) is swap the OEMDrivers folder with the one from bepe's kitchen. If that works, then it is something in that folder. Start there and if that doesn't work, we'll try and figure something out.

Isriam · #**634** (**permalink**) 01-27-2009, 11:58 AM

Thanks, I'll try that next. It may be awhile but I'll update here.

**aceracer24** · #**635** (**permalink**) 01-27-2009, 02:30 PM

Quote:

Originally Posted by chuckz07

Ok, one more thing you can try (and I know this from testing) is swap the OEMDrivers folder with the one from bepe's kitchen. If that works, then it is something in that folder. Start there and if that doesn't work, we'll try and figure something out.

I am not sure I would swap the entire drivers folder, no telling what new problems you could run into.

What is the error you are getting when you run BuildOS? There will be a pop up as well as what OEM the process ran into the problem showing at the bottom of BuildOS. I am wanting to know if it's failing during the creation of the registry or actually at the carrier folder.

rjmjr69 · #**636** (**permalink**) 01-27-2009, 02:32 PM

Quote:

Originally Posted by aceracer24

I am not sure I would swap the entire drivers folder, no telling what new problems you could run into.

What is the error you are getting when you run BuildOS? There will be a pop up as well as what OEM the process ran into the problem showing at the bottom of BuildOS. I am wanting to know if it's failing during the creation of the registry or actually at the carrier folder.

I can testify to this one DO NOT TRY unless your ready to start looking real hard to find errors

Anyhow I solved my problem you HAVE TO INSTALL a skin and THE STA what is that?

**aceracer24** · #**637** (**permalink**) 01-27-2009, 02:35 PM

Quote:

Originally Posted by rjmjr69

I can testify to this one DO NOT TRY unless your ready to start looking real hard to find errors

Anyhow I solved my problem you HAVE TO INSTALL a skin and THE STA what is that?

STA or normally refered to as S2A = Slide to Answer. It's something that came from the Touch HD I believe. I assume when you say a "skin" you mean Phone canvas/Black/white/slide to answer and so on? Yes that would be correct. You do not have to chose the slide to answer though. You can pick the black or white stock.

Isriam · #**638** (**permalink**) 01-27-2009, 03:12 PM

I don't get any errors. It builds perfectly. When I flash the rom it flashes. On reboot it just sits at Touch Pro screen with radio versions.

**aceracer24** · #**639** (**permalink**) 01-27-2009, 03:48 PM

Quote:

Originally Posted by Isriam

I don't get any errors. It builds perfectly. When I flash the rom it flashes. On reboot it just sits at Touch Pro screen with radio versions.

How long have you let it sit on that screen? I ask because I don't know the extent of your experience with this and it can seem like it takes forever on that screen. Far longer on the initial boot after a flash.

Isriam · #**640** (**permalink**) 01-27-2009, 03:51 PM

I've let it sit for 20 minutes

As I said I've flashed about 15 different roms, and made my own with ppckitchen. Even made some non cricket roms with caulkin and erice. Just seems when I add my carrier OEM it hangs up on that screen.

If we don't have any valid ideas here I don't mind working in messenger with someone but I don't really want to upload the carrier OEM here because it was given to me for personal use by the creator.