>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
Symbian phones
> Bricked P1i through SEUS!
Bookmark topic
Hi there, i have used the search function but to no avail so i thought to create a new topic. Basically i was just in the process of updating the P1i, so i download the latest SEUS, and i follow the instructions on screen remove the battery, reconnect battery, hold c etc...
Anyways there was no indication my firmware was up to date so i continue with the update process.
The whole thing was going smoothly up until it reached 100% at which point i receive an "update failed, please reconnect and try again" error, well words to that effect.
So i disconnect the phone restart the whole process, and now the phone fails to be identified. It connects fine with the SEUS but when it comes to the idenification screen it always fails.
I have tried turning the phone one but all i get is a black screen with the keys lighting up and the only way to turn off the phone is to remove the battery.
Could anyone please help me?
My phone is with o2, and stupidly i did not write down the firmware versions i had on the phone prior to the update. So i cannot comment on those types of questions.
Many thanks.
--
Posted: 2007-10-22 00:57:49
Edit :
Quote
I think your phone had the original fw before seus bricked it.
If you hadn't flash your phone try warranty then.
--
Posted: 2007-10-22 01:05:00
Edit :
Quote
I would suggest contacting o2. The phone is still under warranty and repairable that way.
If you are brave, you could try using XS++ to update your phone, see this thread here :-
http://www.esato.com/board/viewtopic.php?topic=130758
Alternatively there is a pay service called Davinci
http://www1.davinciteam.com/index.html I would suggest that as it is a pay service that you email them with your problem and see what they say. As a plus, you would then get your phone unbranded to a Generic World Firmware - which as a more up to date and stable firmware than the O2 one. I unbranded my phone in this way - it takes a while and involves updating using the davinci software and then again using SEUS to get the latest firmware installed. All in all I found it quite painless. They charge 20 euros as I recall.
If the above don't work then there is still getting warranty repair as an option.
--
Posted: 2007-10-22 10:52:20
Edit :
Quote
Right finally the 24 n00b ban is over for me.
Ok i got in contact with my provider and they said they will be giving me a new handset. In any case, when i do get this new handset i will look into the firmware version and whatnot and post details.
I have noticed many new phones update and keep updated via firmware flashes, after this experience with SEUS i am not too confident doing a firmware update, could you guys either:
Tell me what have been the major changes since the p1i's release in terms of firmware because i don’t feel like going through this potential hassle again if the update was something small and insignificant.
And i would also like to know if there is a safer way to upgrade the firmware as i do not want to have this problem.
Funny thing is this happened while using SEUS, had it been a 3rd party program you could argue it is expected as it is a 3rd party program. But when it comes directly from SE the fact that the flash failed and subsequently bricked the phone despite following the instructions makes you wonder if this service should be reconsidered.
--
Posted: 2007-10-23 00:07:26
Edit :
Quote
I would unbrand to the generic world firmware myself, you'll get the firmware updates first that way.
The d23 > e30 update didn't contain anything major, but wlan is much more reliable - its worth it for that, from personal experience i'd say the e30 is more stable than the d23.
Again, your choice. As to seus, you might wanna check your usb ports, they seem to be the root of many a firmware update problem. It seems some ports don't give as "clean" a connection as others, which seems to cause problems for the update process.
--
Posted: 2007-10-23 00:31:15
Edit :
Quote
Ok well i received the phone this morning hadn't had a chance to use it just yet as i had to get ready and go to work. But when i do get home i will have a look at the firmware versions it is running.
Just out of curiosity how would i be able to check which of the usb ports offer this so called "clean connection"?
--
Posted: 2007-10-23 12:10:27
Edit :
Quote
Not sure, tbh, i think its just a case of trial and error mostly. You should also ensure your phone is fully charged before you do it and that all contacts between the phone and your PC are clean.
Hopefully your previous experience was just an abberation, good luck!
--
Posted: 2007-10-23 12:50:27
Edit :
Quote
Ok, my update experience wasn't as traumatic as yours but it didn't go too smooth either (all of the my backups failed to restore, meaning a tedious painful, manual reconfiguration/reinstallation). I think, like you, I'll probably think twice before updating next time too..
--
Posted: 2007-10-23 14:50:59
Edit :
Quote
Hi there, me again
Anyways, i got my new phone from the provider and i thought i would update with some information and a question:
Data from the phone says:
Phone: CXC162037 R9G007
Bluetooth: CXC162143 R1C
Organiser: CXC162108 R6D23
CDA: CDA162024/9 R7A
Now for my question would anyone know what this all means in terms of the state of the firmware?!
And secondly upon doing some reading i came across this little gem about the SEUS:
"Depending on your phone model, you need DSS-25 Deskstand, DSS-25 compatible phones or DCU-60 USB cable, DCU-60 compatible phones"
Well i looked at the cable provided in the box and found that mine is a DCU-65 cable. Does this mean that the cable is no good for the update service and thus that is what caused the phone to be bricked?
Many thanks in advance to anyone who may reply
--
Posted: 2007-10-24 01:45:32
Edit :
Quote
No. The 60 and 65 are identical i myself have unbranded and updated my p1 with the 65 without issue.
--
Posted: 2007-10-24 11:09:41
Edit :
Quote
New Topic
Reply
