Error 150: ROM upgrade utility error
 

OK....I'm at wits end.

I cannot update to ANY ROM....

Ran Saridnours on my old 6700, got a new one and cannot update my ROM


I was stuck in bootloader mode a few weeks ago.

Now that I'm back up and running, I tried Saridnours again, later tried Phoenix - error 150 :

This ROM is not designed for your device. Please get proper ROM upgrade utility and try again.

BEfor eyou ask or suggest, I searched high and low for a solution. These are things I've tried.

1. just run the upgrade again...no luck
2. Flash to stock rom and run upgrade....cant flash to stock rom
3. change cables...no luck
4. change PC's ....still working on that one, will try my laptop by morning
5. reboot PC and or PPC...done that, no luck
6. Just keep trying.....doing that


ANY help would be appreciated.

Is it possible that they made the phone non-flashable (is tha possible)???

Is there some simple step I am missing????

Use the NOID flasher and make sure to put in bootloader mode before trying to flash

Put your phone in bootloader mode, and check the bootloader version (it's at the bottom of the screen when you are in bootloader mode). Follow the directions in the kitchen for your bootloader version.

Error 150: ROM Upgrade Utility Error
 

I have a Verizon XV6700 phone flashed to Cricket. It is currently running WM5 without any issues. I would like to upgrade to theApache WM6 ROM available at the start of this thread.

I have downloaded the Cricket ROM and attempted install it, but continuously receive this error:

ERROR 150: ROM UPGRADE UTILITY ERROR
This ROM upgrade Utility is not designed for your device.
Please get the proper ROM Upgrade Utility and try again.

I'm not quite sure if this matter, but my bootloader version is 1.00. I thought about trying the generic ROM but not sure if this a good idea. Can someone get me some direction? Thanks.

Solved.
 

I am posting this in hopes that it helps someone else. The problem is Windows Vista.

Use a Windows XP machine and you will be able to do everything without a problem. I found that in Vista (at least on my machine) when in bootloader mode it is using different drivers then when on the Today screen.