WM6 to WM5

downbeat · #1 (**permalink**) 09-13-2007, 11:40 PM

Does anyone know how to go back to WM5 from WM6?

Karmashock · #2 (**permalink**) 09-14-2007, 12:42 AM

you should be able to just flash back to a WM5 rom...

**guitardoc64** · #3 (**permalink**) 09-14-2007, 12:50 AM

Yep, you just have to re-flash it, either with the stock rom from UTStarComm or the 3.5 kitchen.

http://www.utstar.com/pcd/view_phone...?mcode=PPC6700

usib · #4 (**permalink**) 09-14-2007, 01:55 AM

No, this does not work. When trying to flash the official ROM, it says "not designed to work with this device". What's more, it gets stuck in bootloader

EtherealRemnant · #5 (**permalink**) 09-14-2007, 02:05 AM

Don't flash an official ROM, flash a hacked 3.5 ROM, then try flashing the official ROM again.

usib · #6 (**permalink**) 09-14-2007, 02:23 AM

Reading the kitchen intro now and trying to understand what's going on...
one thing that baffles me is all this "No_ID" utility business and why one needs it... anyone kind enough to elaborate?

usib · #7 (**permalink**) 09-14-2007, 04:22 AM

Hmm, I am completely stuck now. With any of the ROMs that I cook, the result is the same as with any of the downloaded ROMs: it does not boot them, just sitting in the bootloader. I see people talking about this "universal cure" for it, should I go for it?

usib · #8 (**permalink**) 09-14-2007, 04:26 AM

The other thing I find very weird, is that I was never able to use the "Normal" RUU (which says it's for 2.02 bl, which is what I have), I always need the No_ID one... even for the ROMs I cooked with the correct PRJ... it always says "not designed for this device".

usib · #9 (**permalink**) 09-14-2007, 04:41 AM

Ok, the uni_exitbootloader helped.
Now if I only could solve the original problem with losing my phone service...
I wonder if the "wrong device type" and the service programming problem are somehow related...