XS++3.1 Darwin broke my K800i

[Derry]

Hello all,

I have a K800i and it had a recent history of problems which I won't go into here. I got it fixed at an SE approved maintenance under warranty. I had been playing around with XS++ thinking I might be able to fix it myself, but then thought better of it. Anyway, they fixed it by updating the firmware and replacing the speaker box. After that, I connected xs++ to see what it could see about the new firmware. It worked fine, just allowing me to see the firmware, erom etc...Yesterday, after thinking for a while about unlocking my phone, I decided I would use xs++ to back up my GDFS, as I had read that this was important if all else fails and I need to recover from a bad flash. So I did that, it backed up fine, then I disconnected the phone, removed the battery, put it back in and turned on the phone, and it's the White Screen of Death! I can also feel it vibrate twice! I have never written, or tried to write anything to the phone, only backed up the GDFS with software (xs++) which had already worked with my phone. Does anyone have any ideas?

[Krizak]

You may try writing the GDFS back, if you have it, but in this case i am not sure about it. The GDFS may be incomplete and it would make it worse than it is:(How was your battery?Didnt the power went down or bad battery connection or low charge?Anytime when accessing the GDFS of the phone, it is very sensitive:(But you already know this:(Sorry, cant hel you more than this:(

[Derry]

Actually, I forgot to say that in exasperation, I then rewrote the gdfs file which I had backed up, and it appeared to write successfully, but with the same result, WSOD! My battery was avout 80% before I backed up GDFS. The only reason I did this was because I thought that at some stage in the future, after I had read enough about it, I would reflash my phone, and hopefully also unlock it. This was not a big issue for me, I just wanted to experiment more than anythign else. But now I have a broken phone having not even tried to write anything to it! Does anyone else have experience of a GDFS backup causing damage to a phone? Is it a xs++ bug?

I have tried to update the software using SEUS, but the update service days I have the latest software. So my phone is detected by both xs++ and by SEUS, but it is still giving me WSOD. Any ideas guys?

[mohdumer]

Reflash Your MAIN. It Will 100% Solve WSOD. However I'll Recommend Full Flash - MAIN+FS+Custom.

[Derry]

Yep, I was thinking the same myself, thanks for the advise. Any idea why this might have happened, or have you heard of it happening before? Is xs++ Darwin stable? How can it damage the phone if it doesn't write anything to it?

[mohdumer]

XS++ Is Not Involved In The Damage Caused. It Usually Happens When Connecting A USB Cable Which Is Not Inserted Correctly (i.e First Right Side Then Left Or Vice Versa) Or Carbon On USB Fast Port Or Phone Connectors. To Prevent WSOD, Update Your EROM.

[Derry]

Ok Mohdumer, I will take your advise, but I'm a bit confused. You first suggested I update the firmware, now you say the EROM. Are these not 2 different things? I'm pretty new to this so bear with me:)

[oleq83]

Wouldn't recommed that you update your erom. Than you'll have a CID53 phone, and that will make it much harder to flash the phone, and you'll have to pay like 50EUR if you wish to unlock it. XS++ doesn't support CID53 phones, so you can forget about patch unlocking.

[Derry]

Thanks Oleq83, I was thinking that updating the EROM should only be done if updating the firmware fails. But I am confused about what you say: can I not just write the same EROM version to the phone? Why would I have to make it CID53? It is presently CID52.

[Derry]

I have now downloaded SE Tool2lite 1.1 and once again connected my phone. Just like xs++ it can identify my phone, firmware etc. So I have now use SETool to backup my GDFS once more. The interesting thing is that this backup is only 80KB. whereas the backup using xs++ was 100KB. Could it be that xs++ somehow accessed a part of memory that it shouldn't have? Which is the correct gdfs?