How did you get this to work??? The official AKU33 upgrades the bootloader to V2.05. Devel4 doesn't work with that bootloader, at least not for me.

](*,) I accidentally ran the wrong AKU 3.3 update and it updated my bootloader to 2.05! I meant to run the one I got from here that removed teh bootloader update. That's what I get for doing it while watching a football game. I tried the devel4 kit, but it complained about the RUU.

Now I'm incredibly disappointed. I've been running Helmi's rom for weeks and was loving it. Now I'm stuck back on the standard WM5 from AKU3.3!

I've been hunting like made for someone with a tip that will help me out of this jam, but haven't found anything.

So did you REALLY run the official AKU3.3 before devel4?

Thanks!

I haven't tried this, but I was thinking that maybe you could try copying the .nbf file from devel4 and putting it in place of the .nbf of the AKU 3.3. My thinking is that it will think your flashing AKU 3.3 again, which is compatible with the new bootloader, but it will really flash WM6 devel4 because you tricked it by switching the .nbf file out. I think verizonguy renamed his rom file to os.nbf or something though, so you would have to rename it back to nk.nbf. I know if that doesn't work... there is the old bootloader floating around here somewhere. I think the link is in the thread regarding the new official AKU 3.3 release.

Same Problem...
 

I'm in the same boat, I flashed with the vzw 3 and now my bootloader is 2.05. I tried flashing devel4 and it fails. Is the best thing to do backrev the bootloader?

Ok you dirty bastids, I've spent the last week putting together a treat for you to play with this weekend. Behold the first Apache WM6 Kitchen:

http://www.megaupload.com/?d=6X0AAKZL

It is a rough draft at this point :) Still much to do to get it where it should be, but it will provide a framework for you all to build off of. Enjoy.

Yes I ran the AKU 3.3 ROM first. There is a thread out here called VZW AKU 3 Official ROM. A member took the AKU 3.3 VZW ROM and compiled it for users that did not want to upgrade their bootloader. I am running bootloader 2.02 on my 6700. Once I finished the AKU 3.3 ROM I then re-flased right back to VerizonGuy's Devel4. The only difference I see now is that the stock Verizon splash screen is default, not VerizonGuy's.

BTW - the 1.43 radio is working well so far. No issues and it does not seem to lock up like 1.41 would do from time to time.

Steve

oh neato! now we can create more issues for ourselves :)

does it have the ability to add 1.43 radio? guys are claiming its increasing signal strength.

thanks!

Thanks for the suggestions
 

Thanks for the suggestion - I was able to use the RUU from helmi's 3.5 kitchen and after renaming the devel4 os.rom to nk.nbf, I was able to flash it to my device. Even though the new RUU says it is for 2.04, it seems to work fine with my device's 2.05.

But, then of course, once the rom was on the device and I reset, it comes up but hangs with the white screen of death.

I d/l'ed verizonguy's new WM6 kitchen this morning and have started playing with it as well. Any roms I build with it so far also hang with the white screen of death also.

So I may go back to helmi's original WM6 rom and try that one a bit later.

For now, I've just backed down to helmi's 3.5.

Thanks for the help and suggestions!

The Radio has nothing to do with the windows rom. You can flash the windows ce rom, the extended rom and radio rom all at the same time or individually, but the radio rom isn't a module of the ce rom or anything like that.

I know I was just hoping you had tested it with your ROM and had it baked into the kitchen. No worries, I'll just flash it seperate. People seem to be liking it so far....

Does this mean that there will be no A5 release, or is A4 as far as you're taking it? We really do appreciate all your work - I'm just trying to decide if I'm going to start playing around with the kitchen - something I've never done.

Thanks again,
-PH