Skip to main content

How Nokia refused to repair my phone after a hardware failure

After 4 years of using Windows Phone devices using Nokia phones, this year I had to ‘fight’ Nokia services. A few weeks ago I had the unique chance to wake up in a morning with the following error message:
“Unable to find a bootable option error”
The black screen of dead from another device with the same problem:

I said “What the hell….”, I tried to restart the phone , but I ended with the same error message. Trying to use Nokia Recovery Tool to rewrite the OS… no result…. The phone is not seen by PC… The phone is completed dead.
From what I found from the internet, it seems that there is a problem with the internal flash memory. It is a common problem for Nokia and the phone cannot be repaired. In USA a lot of people sad that the device is replaced with another one.
Okay, I said no problem. The phone is still in warranty and I will send it back to the dealer. The screen of the phone has in the bottom left a small part of the screen broken (I broke it 1 year ago). But this is another problem and it is not connected to this. See below pictures.

The phone was bought from Emag, so I ended up at Depanero service. They send the phone to another company called Regeneris.
And there was a big surprise. My warranty was removed because the screen issue. Even if the error related to bootable option is a well know issue at Nokia and is not caused by the screen.
They offered me to repair outside the warranty with around 1150 RON (250E) with the condition that they need to change the screen also. Why? Because the internal problem that my phone means replacing the phone with a new one.
I still not understand in this moment why Nokia refuse to repair the problem related to boot error. I don’t want a new screen, I don’t want a new phone I only need to resolve an issues that is caused by hardware failure.
In the last 10 years I had only Nokia phones in my hand and never the cheap ones. And now, when I need a reparation of the phone, which is caused by a hardware failure they are refusing it.
Similar situations I know from friends that had iPhones and Apple changed their phones without any kind of problems or repaired the hardware failure.
I’m disappointed about customer support and services that Nokia and Microsoft has in this moment related to phones….
Why? Because I had to pay for their hardware failure. Even if we are talking about premium devices.
I wanted to upgrade this year to Lumia 1520 or Lumia 930 but I’m starting to have doubts. Why should I go Nokia when the customer support is so lame?


  1. How *Microsoft* refused to repair my phone after a hardware failure - fixed the title for you :p

  2. Lousy hardware & software in these Lumias. I was also a nokia fan, just until a year ago when i went through the same crap with nokia care service support. My lumia 800 which i had since 2012 played dead on me. The battery was depleted to that point where it didn't even recognised the charger or the USB cable. It only showed me the empty battery and nothing. I went through hell with nokia care and ultimately i went to a local repair shop which resofted my device with a custom built thing named JTag or something like this. It costed me about 45E. And after about 8 or so months it happened again.

  3. lame in Romania :-) but good point ...


Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.