XS++3.1 Darwin broke my K800i
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?
Re: XS++3.1 Darwin broke my K800i
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:(
Re: XS++3.1 Darwin broke my K800i
Reflash Your MAIN. It Will 100% Solve WSOD. However I'll Recommend Full Flash - MAIN+FS+Custom.
Re: XS++3.1 Darwin broke my K800i
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?
Re: XS++3.1 Darwin broke my K800i
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.
Re: XS++3.1 Darwin broke my K800i
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:)
Re: XS++3.1 Darwin broke my K800i
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.
Re: XS++3.1 Darwin broke my K800i
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.
Re: XS++3.1 Darwin broke my K800i
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?
Re: XS++3.1 Darwin broke my K800i
Sorry, that should have been 88KB, not 80KB!
Re: XS++3.1 Darwin broke my K800i
Guys, I am a bit confused about the terminology being used in this forum. Does anyone know if there is a tutorial which clearly explains the difference between main firmware, FS firmware, EROM firmware, and GDFS firmware. There are excellent totorials about how to burn this firmware using xs++ etc, but I'm just not sure of the exact difference, and hence, which should be used to solve a particular problem.
Secondly, I'm also confused about burning firmware and then finishing by burning a cust pack. It seems to me that once you burn both Main and FS, then you must also finish by burning a Custom Firmware. But then I see that some people advise to solve a problem by burning Main firmware only? Is this possible without burning a cust pack? Is there anywhere that this is explained in detail?
Hope someone can help me all this, as I now intend to burn something onto my phone to solve my problem, but I'm still not sure which?
Thanks in advance!
Re: XS++3.1 Darwin broke my K800i
Quote:
Guys, I am a bit confused about the terminology being used in this forum. Does anyone know if there is a tutorial which clearly explains the difference between main firmware, FS firmware, EROM firmware, and GDFS firmware. There are excellent totorials about how to burn this firmware using xs++ etc, but I'm just not sure of the exact difference, and hence, which should be used to solve a particular problem.
Look here:
SonyEricsson Hardware and Firmware Definitions!
Nice day
Re: XS++3.1 Darwin broke my K800i
Quote:
Originally Posted by
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:)
You Are Absolutely Right But Read It Carefully:
To Repair WSOD: Flash MAIN
To Prevent WSOD: Update EROM
Re: XS++3.1 Darwin broke my K800i
Ok, so the first thing I need to do is flash Main. As for preventing WSOD, I need to update EROM. Hoever, my EROM CID id 52. Can I rewrite CID 52 rather than updating to CID53? I heard CID 53 is not supported yet by a lot of the software such as xs++. I'd rather keep it at 52 in that case.
Re: XS++3.1 Darwin broke my K800i
Hi. I do not think there is enough correct info on where to flash files on the phones i.e. fs or main. Where should one put a gdfs or erom for example. What file sould they be flashed to. I have researched the internet and it seams everyone is stabbing in the dark without any real information, leading to damaged phones. If anyone can inform us better then please do.