Guest ElimGarak Posted December 9, 2009 Report Posted December 9, 2009 Hey folks, some might remember I told of buying a defective Omnia from eBay. Well: First of all, I was surprised, that just by hard resetting, I could get the phone to boot Windows Mobile again. However: The performance was more than poor - sometimes the device didn't respond for minutes (and the touchscreen wasn't the problem, the buttons didn't cause reactions as well). I really don't know, what the hell was wrong with this thing. So I thought I'd do flash with Grand Prix using WinXP SP2. After figuring out, that ActiveSync must also be installed for this to be working (yeah, noob - I know *g*), I had it going. I followed the instructions on a German site with an official German ROM by Debitel, dated sometime late 2008. Flashing the PDA and the Customer-part just went fine, however I can't say the same for the phone part. Waited for about 15 minutes and I just got as far as "Opening COM 3 succeed". Expecting nothing won't happen anymore, I disconnected and retried it. And again I didn't get further, just that the Samsung-Splash-Screen now has been replaced with the notorious "phone-warning-sign". The Log: "Device name:5&3a630a2b&0&1 EBoot version=01.36 Start downloading... PHONE-Switching USB to PHONE... PHONE-COM3 detected PHONE-Attempting to open COM 3... PHONE-Create COM 3 succeed... PHONE-Opening COM 3 succeed..." And in the application it said: "OnDeviceChange: DBT_DEVICEARRIVAL ------------------------------------------------------------------------------------- PDA Device 1 ready to download! ------------------------------------------------------------------------------------- PDA 1 starts downloading... Don't plug it out until the label becomes blue!!! ------------------------------------------------------------------------------------- PHONE will be written. ------------------------------------------------------------------------------------- Downloading PHONE... OnDeviceChange: DBT_DEVICEARRIVAL" Any way of getting the phone-part working? Hope I didn't mess it up. On the other hand: It wasn't really usable before. Any hints would be greatly appreciated. Best regards!
Guest ElimGarak Posted December 10, 2009 Report Posted December 10, 2009 (edited) Weird - although I get the phone-with-exclamation-mark-symbol, the phone module just seems to work fine... Anyway: Can I flash the phone-part again in a possible future update? Edited December 10, 2009 by ElimGarak
Guest dannych99 Posted December 10, 2009 Report Posted December 10, 2009 Weird - although I get the phone-with-exclamation-mark-symbol, the phone module just seems to work fine... Anyway: Can I flash the phone-part again in a possible future update? The PDA part is better match the Phone part. i.e DXID1 PDA part use DXID1 Phone part.
Guest ElimGarak Posted December 10, 2009 Report Posted December 10, 2009 The PDA part is better match the Phone part. i.e DXID1 PDA part use DXID1 Phone part. So because of the two parts not matching, I get the exclamation mark? Will official updates still work anyway? And should I even try? I read, that once you've messed up your phone-part, you cannot simply reflash it, but have to use some JTAG-chip or so?!
Guest ElimGarak Posted December 10, 2009 Report Posted December 10, 2009 Just wanted to say it all worked out after an official update to BHIC2. That'll be it for the moment. But certainly I'm soon going to switch to a custom rom. By the way: Is there any way of telling, which one also flashes phone or bootloader? Because I wouldn't want to risk flashing any of these. Best regards!
Guest huzo Posted July 19, 2010 Report Posted July 19, 2010 what ever i do i can't get this to work.... i simply can't flash the phone part!!! it gets stuck at the downloading phone... ondevicechange: dbt _devcearrival and stays at that! the drivers are installed com port connection succeeded i dunno what am i doing wrong!!!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now