New BuildOS - Report Bugs Here

[kevdawg]

Originally Posted by gguruusa

3. Invalid format error when trying to start application on x64 OS. Not sure you can flash from an x64 OS even if it does run, but i'll try to resolve the Invalid format problem.

I dont know if the tools have changed drastically since the old kitchen but with the older tools we have always been able to use x64 OSes (Vista and XP) to flash the ROMs.

[gguruusa]

Originally Posted by kevdawg

I dont know if the tools have changed drastically since the old kitchen but with the older tools we have always been able to use x64 OSes (Vista and XP) to flash the ROMs.

Really? I'll remove that then. The tools have changed substantially, however. Please see me in the chat room - I need you to test a few things so I can narrow the problem down.

[imnuts]

Originally Posted by gguruusa

Really? I'll remove that then. The tools have changed substantially, however. Please see me in the chat room - I need you to test a few things so I can narrow the problem down.

Yeah, I haven't had any issues to date on Vista x64, not even connection problems that require new drivers or the change in the connection settings in WMDC. Hopefully you can get this resolved then, it would be much appreciated.

[phoenx06]

Me and GGuruUSA are working on the 64 bit OS problem

[dpdurst]

I'm not sure this is a bug, but did not notice this till the new kitchen build. If I go into the phone, options, services and then network service and change the setting from EVDO to 1x or the other setting or just go in there and do nothing but say ok, it resets the phone. If I have one of the task managers on the top bar (HTC) then it locks up the device. I have to either hard reset it and then remove the task manager and put it back or leave it off. If I do remove it and put it back its fine after this and no longer locks up

[gbm85]

Originally Posted by dpdurst

I'm not sure this is a bug, ... no longer locks up

This thread is for bugs with BuildOS, not with the kitchen itself. But to answer your question, that has happened with every ROM as far as I know. Simple solution: don't open that panel unless you plan to change the mode

[dpdurst]

Thanks, and sorry didn't pay attention to where this was posted.

[dierrecook]

Originally Posted by gbm85

This thread is for bugs with BuildOS, not with the kitchen itself. But to answer your question, that has happened with every ROM as far as I know. Simple solution: don't open that panel unless you plan to change the mode

everytime i go to build os after the update it says the application failed to intialize properly (0x0000135).
Quote:

[MaryZ]

I used the solution to the Verizon 2.05 bootloader problem that was posted and it worked perfectly. Then used the new build os to make my rom. I tried multiple times to flash my phone and it kept giving me an error of "wrong model".. and I was using the correct Verizon file to encode. However after reading another post here, I then tried changing the ruu from "standard" to "no id" and it worked right off!.. Is this ok? or should it have worked with the other, meaning something went wrong when I reverted the bootloader?
P.S.
And by the way I am really jazzed about this..I just fell in love with my phone all over again! You guys are great to put this out here for those of us with little to no experience-My paypal will be on it's way soon.

[rspppcgeeks]

Yep - that's the way it works after doing the 2.05->2.02 bootloader downgrade. You have to just keep using the NoID RUU. At least that's what I was told.