Just receved my GNex back from the Repair Centre and its totally differentfrom when i sent it away!!

TallPaul86

Member
Dec 16, 2010
12
0
0
Needing your help guys!!

My GNex was running Android 4.2.2, it was completely (heck, it wasn't even rooted!) and after speaking with the customer service rep at Samsung UK regarding the screen burn I was getting on my GNex (the keyboard was permanently ghosting on the bottom third of the screen) they suggested to send the phone away sans battery and battery cover...

10 days later I received my GNex and its totally different to the one I sent away: -

1) The screen has a bluey/greeny tinge to it now (after being replaced by Kamil the engineer)
2) It has been rooted (padlock at the Google start up screen was the big giveaway)
3) it has been left in its engineer test mode (I currently have AngryGPS and Dev Tools as "apps" in the app drawer)
4) Its currently running Android 4.0.1 (after the letter stating it was, and I quote, "For peace of mind, your repaired device has also been independently checked by our Quality Team to ensure it is fully working order before we return it to you. We've also installed the latest approved software as part of our standard repair process - can't be that great a process!! Where the hell were the Quality Team when Kamil handed my phone over to be checked? Out to lunch maybe?!?)
5) I cannot run a software update due to their being no option to update the software OTA, like you can with a retail version of an Android device

I'll be sure to mention this to Samsung UK when their customer service desk opens tomorrow to complain however in order to have a fully working device either tonight or now, can someone suggest how I fix this? I have not a clue how to and I thought a simple Factory Reset would have fixed it however regardless of how many times I do that it just reverts back to the engineering mode, im gonna call it that for now.

Help?!?:(
 
It almost sounds like they sent you a completely different device all together, perhaps a refurbished model?

What I would do is try a factory reset if the option is there. This wont fix the unlocked bootloader (which is what the pad lock is, not root) but that won't cause any harm if you plan to leave it alone. If a factory reset doesn't work you might want to consider flashing stock Jellybean on the device using ADB or Wugs toolkit.
 
Sorry to hear that.

I am leaving my phone tommorrow - also because of the screen issue - and now I m wondering if it's a good idea... ;-)

Keep us updated of what you will find out and good luck.
 

Trending Posts

Forum statistics

Threads
957,124
Messages
6,971,579
Members
3,163,723
Latest member
trixie909