please help i think i messed up my mda using the rom kitchen

[beowolf]

I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.

And it appears that I cannot flash the rom again. Am I screwed?

 

[mfrazzz]

What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.

BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...

 

[beowolf]

I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.

 

[mfrazzz]

I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.

ok, cool... wasn't sure... So can you get to the bootloader?

 

[beowolf]

yes I can get to it

 

[beowolf]

I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?

 

[mfrazzz]

"doesn't have problems" is the catch

I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close

Core 2.0n is very good and nice and clean.

Also NBD and Wizard Mobile 6 are both supposed to work well.

The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).

As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )