Re: Error 120 fixed but now error 150
Ok so it appears it is,
I purchased a Cellular South UTStarcom to replace my terminal Verizon XV.
I thought I'd have to change ESN's to activate it on Verizon but they said no problem and it's up and working well. Really cool since I had no idea the ESN stuff was a no no.
The UT phone has ROM 2.11.20 WWE dated 04/04/06 and I updated 1.16 radio to 1.41. The radio upgrade works well.
It has bootloader 1.0 and once I was able to actually build a rom that didn't make the chefs giggle and flatulate, I met steady opposition in the form of 120 errors.
Dug about and read the 1.0 bootloader wanted RUU "noID"
that seemed to cure the 120 error only to reward me with a 150 error
so I tried carrier "cellular south" instead of verizon
no dice
I tried unbranding it and then trying to flash with both carriers
no dice
I've tried this on vista and xp-pro and have even tried uninstalling and reinstalling BuildOS several many times.
I did notice that after reinstalling previous build files remained on each particular computer.
Is there an easy answer or did I need to cough up more info?
Is there a hard answer?
I'm hoping for easy and expecting impossible so lay it on me.
Thanks I'm in over 20 hours and I'm starting to have visions of smashed xv's and plasma monitors as well as sheet rock repairs looming in my future.
|