New BuildOS - Report Bugs Here

[gguruusa]

Originally Posted by n8mack33

I'm getting the "Unknown Carrier Type" error when I open BuildOS. And then when I try to flash I get a FAT16 filesize error (and yes I am SURE I am using the correct folder for the prj). I am a Verizon user. I tried to save Verizon as my carrier and reopen BuildOS, but still get the same error.

Any ideas?

Unknown carrier type error is because you did not pick your carrier in the carrier drop down on the tool bar. This should be done in addition to the carrier selection in the OEM list (which you should also pick).

The FAT16 filesize error is from running an old version of HTC64_Encoder. If you pick your carrier in the toolbar dropdown, this will be irrelevant.

Unlrelated to this issue, everyone should _always_ hard reset after flashing. I added that message because of the large number of people who were not doing this. I'll be expanding the messages in future releases in an attempt to alleviate confusion between the instructions in the RUU tool and what you _should_ be doing.

[Chevellelv]

When I try to run the new buildos I get this error message the application failed to initialize properly )0xc0000135). Click on OK to terminate the application. I am running windows xp service pack 2 with .net framework 3.

[pdx77]

Originally Posted by Chevellelv

When I try to run the new buildos I get this error message the application failed to initialize properly )0xc0000135). Click on OK to terminate the application. I am running windows xp service pack 2 with .net framework 3.

This problem was fixed in the IRC chat, ended up uninstalling .net framework 3.0 and installing 2.0 which fixed it.

[nelly48237]

Originally Posted by gguruusa

When you push the "save to file" button it creates a file in the install directory called "buildos {date}.txt". Alternativevly, you can push the "copy to clipboard" button, open your favorite text editor (wordpad, notepad, etc), and paste the clipboard contents.

Your problem is that you installed PPCgeeks_OEM.rar incorrectly. PPCGeeks_OEM.rar should be placed in c:\buildos. It should be left in .rar form. It appears you have extracted it into the USER_OEM folder, which is incorrect.

sorry for not responding sooner. i've been working.

you was right. i had put the OEM in the wrong spot. another mistake that i had made was when i realized that i had opened it the wrong way. i call myself deleting the files. but come to find out, i was deleting the files, but not the 'buildos folder' off of the C drive. i also see what you mean about saving the installed directory when i mentioned that it wouldn't save for me. when i found the 'buildos folder' , i found all of the saved files i was trying to save and i thought wasn't being saved, i found that they all had been save. i am mentioning all of this because others new at this may make this mistake, and i wanted you to know that your assistance in helping me understand this is working , so please don't give up on me. but i did get another error. i attached a picture of that too in hope you will be able to help me.

[avaya]

Originally Posted by nelly48237

sorry for not responding sooner. i've been working.

you was right. i had put the OEM in the wrong spot. another mistake that i had made was when i realized that i had opened it the wrong way. i call myself deleting the files. but come to find out, i was deleting the files, but not the 'buildos folder' off of the C drive. i also see what you mean about saving the installed directory when i mentioned that it wouldn't save for me. when i found the 'buildos folder' , i found all of the saved files i was trying to save and i thought wasn't being saved, i found that they all had been save. i am mentioning all of this because others new at this may make this mistake, and i wanted you to know that your assistance in helping me understand this is working , so please don't give up on me. but i did get another error. i attached a picture of that too in hope you will be able to help me.

you have too many oem selected. remove some more and try again.

avaya

[Wm_user]

After creating my new ROM, my Apache gets stuck on main sprint bootscreen. What should I do?

[nelly48237]

i removed some of the OEM's and i still get the same error. could you tell me what the selections in the top boxes of the kitchen? i have a sprint 6700, and i'm running it with Hemi's 3.5 kitchen. the boxes are: RUU? Boot splash? Sub splash? and Main splash?

[guitardoc64]

Originally Posted by nelly48237

i removed some of the OEM's and i still get the same error. could you tell me what the selections in the top boxes of the kitchen? i have a sprint 6700, and i'm running it with Hemi's 3.5 kitchen. the boxes are: RUU? Boot splash? Sub splash? and Main splash?

Splash screens are the boot screen choices, and more asthetic than critical. RUU and Carrier are important. RUU-try standard first, NoId if you get errors on flashing. Since you are on Sprint you'll need to select that on both the top bar and in the carrier select. Then go to File and save. make your selections, and save as with a unique name so you'll be able to recall if you want to reflash with the same selections, or post if you need help.

[gguruusa]

Originally Posted by nelly48237

i removed some of the OEM's and i still get the same error. could you tell me what the selections in the top boxes of the kitchen? i have a sprint 6700, and i'm running it with Hemi's 3.5 kitchen. the boxes are: RUU? Boot splash? Sub splash? and Main splash?

Your RUU choice depends on what you've done to your phone in the past. If your bootloader is 2.04/2.05, you need the X.04/.05 RUU. In all other cases, you should try the Standard RUU. Try the NoID RUU if you got a country code error using the standard RUU.

Sub Splash is not available for Apache, and it should be grayed out. Boot splash and Main splash are the 1st and 2nd pictures you see when booting, respectively. If you don't want the default built into the ROM, change them to what ever you want...a preview will show in the top left corner of BuildOs.

You need to keep removing OEMs until the "size is larger than max rom size" error in the last line of the BuildStatus window goes away. If you have a 2.04/2.05 bootloader, you'll have to remove even more to avoid a white screen on boot.

[avaya]

[QUOTE=nelly48237;128061]i removed some of the OEM's and i still get the same error. could you tell me what the selections in the top boxes of the kitchen? i have a sprint 6700, and i'm running it with Hemi's 3.5 kitchen. the boxes are: RUU? Boot splash? Sub splash? and Main splash?[/QUOTE

can you post your selections here so we can see. Some of the big one are

ms voice command,
.net CF framework
MS office
Flash plugin
etc...