REQ: Apache WM6.1 Clean Rom

[gguruusa]

It's you. You never even made it to flashing, so how could it be the phone?

If you want a clean ROM, dont select anything other than your carrier and REV (bootloader version) in the kitchen. It will build and you will be done. It doesn't get any simpler.

I'll say it again, even though people never seem to listen...when in the kitchen, don't start by selecting everything. Select very little, if anything, then build. You'll see what success looks like and will build up some confidence.

The old helmi.exe's are buggy, as they were first releases.

[Papachabre]

Originally Posted by gguruusa

It's you. You never even made it to flashing, so how could it be the phone?

If you want a clean ROM, dont select anything other than your carrier and REV (bootloader version) in the kitchen. It will build and you will be done. It doesn't get any simpler.

I'll say it again, even though people never seem to listen...when in the kitchen, don't start by selecting everything. Select very little, if anything, then build. You'll see what success looks like and will build up some confidence.

The old helmi.exe's are buggy, as they were first releases.

Woah, time to exit Assumption City. I have used the Kitchen to successfully flash a WM6.1 ROM in the past, but recently I have tried to build and flash a "clean" ROM containing nothing but the bare minimum around 10 times now. Every time the phone boots it gets to the boot screen, shows the red text at the bottom of the screen and freezes. It never goes through the initialization process. I can remedy the problem by using the UTStarcom ROM "upgrade" to go back to WM5. Now do you see why I'm trying to find where the problem stems from?

I actually posted this in another thread that was related to this problem, but I figured in this thread I might ask for the same thing that the thread's creator asked for - a bare, pre-made ROM.

[gguruusa]

Originally Posted by Papachabre

Woah, time to exit Assumption City. I have used the Kitchen to successfully flash a WM6.1 ROM in the past, but recently I have tried to build and flash a "clean" ROM containing nothing but the bare minimum around 10 times now.

My post was for the OP, not you. The OP is getting ROM to full error using Helmi's kitchen. The solution to his problem is to check less stuff - or no stuff if he wants clean. Your problem is you're using LennySh, which needs an update.

[el_venga]

problem solved, JTSV pmed me where could i get one and im on it.

[mrgino]

Originally Posted by el_venga

problem solved, JTSV pmed me where could i get one and im on it.

if mr JTSV could pm me too, i'd love a clean vzw 6.1 rom as well =)

[NoneYa]

Originally Posted by Papachabre

Every time the phone boots it gets to the boot screen, shows the red text at the bottom of the screen and freezes. It never goes through the initialization process. I can remedy the problem by using the UTStarcom ROM "upgrade" to go back to WM5. Now do you see why I'm trying to find where the problem stems from?

I've run into the same issue using two different 6700 phones. Even using a bare-bone with Rev 1 (I also tried 2.02); RUU - Standard; and Carrier: Alltel. I get the same issue with the Red Text.

As a desparation move, I modified my Selection to point to the older Apache Kitchen (i.e. KitchenDir=Kitchens\Apache_Helmi_WM6.1.rar: instead of Apache_LennySH. Oddly enough this did work. I haven't had a chance to investigate further.

[gguruusa]

Originally Posted by NoneYa

I've run into the same issue using two different 6700 phones. Even using a bare-bone with Rev 1 (I also tried 2.02); RUU - Standard; and Carrier: Alltel. I get the same issue with the Red Text.

As a desparation move, I modified my Selection to point to the older Apache Kitchen (i.e. KitchenDir=Kitchens\Apache_Helmi_WM6.1.rar: instead of Apache_LennySH. Oddly enough this did work. I haven't had a chance to investigate further.

No need to investigate further. Lennysh 213 kitchen as available through updater is broken in that it won't boot. Theres an update, available in the lennysh 213 thread, that fixed the issue. We'll get the fix on updater shortly.