Hey guys, I've got a cingular db2010 cid49 red phone that I wanted to unlock to use with t-mobile... so after lots and lots of reading and learning about modding / flashing phones and such, I finally tried.

Unfortunately, halfway through the backup process of the gdfs (using xs++) my laptop spontaneously shut off... now, I didn't even think anything of it, and continued on my way. Turned everything back on, backed up the gdfs, flashed my firmware, tried patching it, and it didn't work. So, wondering why things weren't working, I reflashed my firmware and after that tried turning it on again.

After the reflash of the main firmware, it works, going back to the start phone or music screen. (Still no luck on "insert correct smartchip" though.

My question is, when I boot it up with xs++ I get errors in all the info like imei not matching gdfs, and "activating gdfs; cannot open gdfs" and erom: n\a, cda: n\a, firmware: n\a.

so seeing all this I tried to write the gdfs backup, and after sitting at the "loading csloader" for about an hour decided to turn it off. trying the backup with setool2lite 1.1 gives the error "wrong response break, failed that is fatal" w/ no packet errors or anything like that...

so my question is, did I brick my gdfs when I first tried to back it up by the abrupt ending of the process the first try? and / or is there anything I can do about it?

Yes you might have.

Try with setool2lite

I tried it with setool2lite, thats what gave the error wrong response break. error is fatal...

Would the phone even boot up if the gdfs was screwed? Because after reflashing the firmware I eventually got it to a point where it was back asking to go to phone or use as music player, and asking to reinsert the correct smartchip... It wouldn't be able to do that if the gdfs was messed, right?

only if the gdfs was really badly mucked up the phone wouldnt boot