I was lying down on the ground and my phone just slipped from my hand and fell on the floor.. although it was hardly any height, just chest high. After a few minutes I checked my phone and there was no network, neither was the sound working.
I've tried re-flashing firmwares.. Villian, then KPE.. no use. If you try to play music, it'll show it is playing, however you can't hear anything, neither from the speakers nor from the earphones.
It shows me an airplane icon on the status bar, however the Flight Mode isn't ticked, and even if I try to tick it, it tries to enable for a while but returns back to unticked state.
Any solutions? Apart from approaching the service center
nish7x said:
I was lying down on the ground and my phone just slipped from my hand and fell on the floor.. although it was hardly any height, just chest high. After a few minutes I checked my phone and there was no network, neither was the sound working.
I've tried re-flashing firmwares.. Villian, then KPE.. no use. If you try to play music, it'll show it is playing, however you can't hear anything, neither from the speakers nor from the earphones.
It shows me an airplane icon on the status bar, however the Flight Mode isn't ticked, and even if I try to tick it, it tries to enable for a while but returns back to unticked state.
Any solutions? Apart from approaching the service center
Click to expand...
Click to collapse
Try to pull out your SIM(before you must shut down your phone) and but it back then. Restart your phone. Maybe you can solve the AIRPLANE mode, but for NO sound, I dont know. Maybe you damaged something in HARDWARE(hope you dont damaged). Try to shut down your phone, like 10-15 min.(pull out your battery too) and then try again. Fingers crossed that it works!
CHEERS!
Nope, I tried everything with the SIM. Even inserted another working SIM to check, doesn't work. Shows 0 signal in the mobile network status in About.
But now that isn't my concern. I want to flash back to Froyo so I can take it to the service center for warranty. And this is where I'm ending up with a lot of bad luck
I tried flashing all these firmwares:
Asian:
S5830DDKC1
S5830ZSKA6
S5830ZTKB2
Europeon:
S5830XXKA6
S5830XXJLC
S5830XXKPE
Except the KPE, which is Gingerbread, none of the Froyo ones seem to work. They pass the Odin installation, however after the reboot, it gets stuck at the Galaxy Ace logo. Seriously.. what's the problem I can't get it. I've tried all those Froyo FULL package ROMs that I saw people suggesting. Why does it get stuck at the boot? I can't return my phone to warranty with Gingerbread, as KC1 is the official in India yet.
nish7x said:
Nope, I tried everything with the SIM. Even inserted another working SIM to check, doesn't work. Shows 0 signal in the mobile network status in About.
But now that isn't my concern. I want to flash back to Froyo so I can take it to the service center for warranty. And this is where I'm ending up with a lot of bad luck
I tried flashing all these firmwares:
Asian:
S5830DDKC1
S5830ZSKA6
S5830ZTKB2
Europeon:
S5830XXKA6
S5830XXJLC
S5830XXKPE
Except the KPE, which is Gingerbread, none of the Froyo ones seem to work. They pass the Odin installation, however after the reboot, it gets stuck at the Galaxy Ace logo. Seriously.. what's the problem I can't get it. I've tried all those Froyo FULL package ROMs that I saw people suggesting. Why does it get stuck at the boot? I can't return my phone to warranty with Gingerbread, as KC1 is the official in India yet.
Click to expand...
Click to collapse
Sorry for you, but keep trying. Still maybe some is GOOD to go! Like: S5830ZCKA7
and
S5830DXKC1
And if you try other ones then ASIAN, try them when you probably buy your phone(look when they come to your store[if they come in FEBRUARY then try January FIRMWARE. Hope you get my point]).
Dont know what to do else, just keep trying and let HOPE you get it work(of course, if you drop dont BREAK something in HARDWARE).
CHEERS!
Yeah, thanks at least for the moral support I've lost my head flashing dozens of times throughout the day yesterday, almost feel like some official flashing guy at the company but at least they get paid for doing it.
I think if nothing works, I will just give the service center the boot screen stuck Froyo ROMs, at least it might be better than giving them a working Gingerbread ROM.
nish7x said:
Yeah, thanks at least for the moral support I've lost my head flashing dozens of times throughout the day yesterday, almost feel like some official flashing guy at the company but at least they get paid for doing it.
I think if nothing works, I will just give the service center the boot screen stuck Froyo ROMs, at least it might be better than giving them a working Gingerbread ROM.
Click to expand...
Click to collapse
Ok! Let to us know, how it ended finally. Maybe we can learn something from it. THX in advance!
CHEERS!
casiocas said:
Ok! Let to us know, how it ended finally. Maybe we can learn something from it. THX in advance!
CHEERS!
Click to expand...
Click to collapse
It finally ended like this.. I gave my phone to the service center on 23rd June, and getting it back today on 4th July. ****ty service people. Kept giving excuse they're trying to update my phone to some 'new version' as they called it, but aren't able to. Finally they could on the 10th day and got my phone back. And the 'new version' was nothing other than DDKC1 But oh well, the network and sound is fixed.
Related
I have searched and searched, but can not find what seems to be an applicable fix, so here goes.
Ok here is my best description. Equipment: Rooted vibrant. The plot: Rooted. Ran fine for months. Yesterday purchased Rom Manager premium. Installed one of the premium roms. Can't remember the name of the rom. After install everything worked fine except I kept getting the error, "com.google.process.gapps has stopped unexpectedly" so I tried everything I could find related to that problem to fix it, but nothing worked. As a symptom the market, gmail, etc wouldn't work. Anyway I figured I'd just recover the last rom that I backed up and start over. So I did, but now the phone boots, goes to the "draw pattern to unlock screen" and won't recognize the fact that I'm actually drawing the pattern to unlock the screen. The "buttons" on the bottom of the screen recognize my touch (menu, home, search, back) as they darken when touching them.
So there the phone sits on the unlock screen. After a minute or two the screen goes blank, the phone vibrates once, and the unlock screen comes back and won't accept any input.
Is this fix applicable, or would it work in bringing my phone back to me?
http://forum.xda-developers.com/showthread.php?t=848737
I want to make sure as I don't want to further exacerbate the uselessness of my phone. I feel like I've lost a limb with it gone.
Thanks for any help.
Sorry to hear you found the worst gremlin of all. I'll get that from time to time when my phone feels like being stupid. Lucky for me, I can just reboot the phone, and she's back to normal.
As far your situation is concerned, I would probably try to use Odin and flash your phone back to stock so you can build it back up to whatever ROM you're on. This usually happens when you bounce back and forth between a froyo and GB ROM; or a ROM from a different dev that's used a different framework to make all his stuff work.
Jump into the link in my sig, and see if you can find the files you need. Otherwise, shoot me a message so I can link you to the files I use to go back to stock pre-rooted.
Lol, did you try this?
http://forum.xda-developers.com/showthread.php?t=749605
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
younix258 said:
Odin to stock, check the stickie about how to do so... it will solve your problem almost for sure... above all, dont panic, youll be allright
Sent from a cell tower to the XDA server to you.
Click to expand...
Click to collapse
OK. The sticky worked. I admit I panicked, but IT WORKS NOW!! I'm just ecstatic! You guys rule.
I guess I was just gun shy. I bricked the snot out of my my-touch a year ago (still doesn't work).
Anyway, on to hacking.
Thanks again!
Awesome! Glad you got it werkin
Next time just try a simple Google search of the error itself.
*EDIT*
If you still have the mytouch I'd be interested in it. PM me if so
Yeah I tried to google the problem, but I was still stuck. None of the fixes seemed to work. Until google led me here.
I do still have the my touch. Mint condition, minus the fact it doesn't work! I'd like to get it working again if possible. Is there a way to odin the my touch? I tried and tried last year when I bricked it, but I never got it to work again. Is there a my touch forum here somewhere named something other than "my touch"?
Sent from my SGH-T959 using XDA App
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Habitats said:
Hi
Recently my S2 just stopped reading my SIM when I was going to call someone. Since then it has refused to read my SIM, or any other SIM for that matter.
To fix this problem I've tried resetting the phone to factory settings (in 3 different ways ( hard-reset.com/samsung-i9100-galaxy-s2-hard-reset.html )) with no luck.
I've also tried installing alternative ROM's, but with the same result.
The phone was already rooted with an insecure kernel when this happened, so warranty is long gone.
Though, one thing I did realize was that even though I did hard-reset the phone several times, some of the settings on the phone remained untouched, like my locking pattern and a few other settings. Does this mean that hard-resetting the phone isn't really an actual hard-reset? If that's so, is there any way to properly 100% reset the phone?
In short; I'm running out of options on how to fix this. I refuse to believe it's hardware related, just because I'm stubborn like that.
Any help would be greatly appreciated (really).
Click to expand...
Click to collapse
You can refuse to believe in gravity too, but falling from high distances will still hurt.
If you tried more than one SIM in the phone and none work, but those same SIMs work in other phones, than more than likely, it is hardware related.
Did you check you imei?
078gregory brings up a good point. So if it's not missing IMEI info, THEN it's likely hardware.
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Habitats said:
Isn't it funny how everything suddenly works itself out once you cry out for help?
Today I've been trying around 10 different ROM's on the phone. Custom and stock. As one last attempt I gave a random ICS 4.0.3 march ROM a last try, and guess what. I got the SIM prompt. I can not believe it. So yeah, it's working now. I have no idea what caused it, but I believe the phone was stuck in flight mode somehow, and just needed an extra push to get out.
Either way, it's working like a charm now. Thanks for the replies though.
Click to expand...
Click to collapse
Don,t forget to press THANKS button on ctomgee
Hi people. I have the same problem Habitats decribes. Mi s2 is stuck in flightmode and cant get out! i have reset the phone in every kind of way but no succes. Now i read here on this forum that flashing my phone to ICS 4.0.3 can help solve the problem. I'm on 2.3.6 now. This flightmode thing happened al over sudden. I have done nothing strange with the phone. Its not rooted either. I was planning to go to a samsung servicepoint and let them check whats wrong. But now i read this thread and see that i can relate to this problem of Habitats. I think a also will try to flash ICS 4.0.3 and watch what happens. But theres another problem. KIES don't recognize my phone anymore so what can i do? Can someone please help me out? Thanks in advance
I'm having the exact same problem, could you please tell me which rom worked for you Habitats? Thanks in advance!
Update:Last tuesday i went to the vodafone store were they have a samsung service department also. I explained my problem to them but they don't seem to recognize the problem. Although i read that many people here at xda's and over the internet have similar issues with this phone.Strange! So they sent it to the repair centre. Yesterday i could see in the track and trace menu of the repair centre that my fone was ready and send back to the vodafone store. Status: Boardswap. So they swapped the whole board! Didn't know that the problem was that serious! So i hope i can pickup my galaxy s2 soon this coming week!! I can't wait!I'm on my old HTC Touch HD now. Its ok with the windows but on Android....Arggghh!! Whatsapp is a pain and more. Its so laggy!. I will give an update soon again!
Please forgive me for the long arse post, details are sometimes a good thing. At this point Im positive I have techherpes. I got a bad Modem last week and on the same day this. Last week I got the test letting me know ICS was available for my note so I followed all directions and downloaded Kies, after 4 attempts finally got a good DL. During the ICS update I got an error and was prompted to use the recovery feature. No dice on recovery so I took the phone to the ATT service center and they set up a return. I got my new phone on Friday and call Sumsung support to get a walk through. The tech said it would be advisable to wait until today before trying the upgrade which I did. I tried it again and the end result was the same as the first. I don't consider myself a technology dullard, hell its what I do for a living but I'm obviously doing something wrong?
At this point I still have the original phone in the return box waiting to be shipped and another phone showing:
ODIN MODE
PRODUCT NAME: SGH-i717
CUSTOMER BINARY DOWNLOAD: NO
CURRENT BINARY SAMSUNG OFFICIAL
Below that is a pic of a phone, yield sign, pc
Firmware upgrade encountered and issue. Please select the recovery mode in Kies and try again.
I spoke with another Samsung tech tonight who tried to walk me through a factory reset, vol up+down+power which brings me back to the same screen above briefly flashing the Samsung logo. She went ahead and setup a RMA and told me that it would be 5-7 days plus shipping. I said hell I'm in Austin can I drive up and have you fix it I can do the vol down+power buttons which will take me to the screen letting me know a custom OS will cause critical problems bla bla blah and when I press the up vol button I go back to the ODIN MODE screen.
Should I simply take it back to the ATT service center again, not sure they will be so accommodating since I have been down this road once already. Ive only had the original phone for just over a month and I have the insurance plan through them. All data was backed up before both attempts.
Maybe you got a bad Kies download. It's my impression it's a little squirrely, from my own experience and reading of others'. Why don't you remove and reinstall it. It seems unlikely that you got 2 bad brand new phones.
That is very possible. I had to DL it 4 times before I finally got a DL that would complete. Ill go that route and see what I can do. Does the current status of the phone mean that its bricked?
Thanks,
Chris
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
kat3k said:
I don't know much about that, but I think it would be pretty bad to be able to brick a phone that easily following manufacturer's directions. In Kies there is an option for something like an emergency firmware fix, in case you need to try that. But I'd go the normal route first. I had some trouble with mine when I did the download, and had to try more than once. The download took forever, and I understand the servers were swamped when AT&T put out the notice. Also had to disconnect the phone and try more than once, but in the end everything was fine. Good luck.
Click to expand...
Click to collapse
Yep, I tried the night I got the text and the first DL took 45 minutes with a 30mb connection. When I tried the installer it failed so I wiped it and tried again. After 4 similar attempts all taking the same amount of time to DL I finally got one that launched. The result was where Im at now with the first phone. Fortunately ATT had me one the next day and I was able to restore. I called Samsung support and the tech told me to wait until Sunday or Monday before I tried it again since Kies would be going down Sat night.
I wiped Kies and installed it this am, 3 minutes to DL and it launched the hotfix. It seems to have gone through several more steps this time so I think I know where the issue was, or at least I wont blame myself 100% for now. When I removed Kies it appears to have also removed my backups? I did another backup using two other software options just to be safe.
When I connected the phone after the new install Kies wont connect to it. I previously tried the emergency recovery since the phone directed me to go this route with no success. Im off to the ATT service center in a few and Ill see if they will go the extra mile again.
Kies wouldn't connect to my phone either at time of update, so I ended up going through the Emergency Firmware Recovery which worked. Then I had to restore my backup. I'd try that again if I were you.
Refs. rehistr
Took the phone into the ATT service center today and as soon as they looked at me they said ICS failed? They told me that their entire day had been spent on skyrockets and notes. They weren't able to correct mine so they are sending me another. I wont be attempting the update on this one for awhile. It would be nice if the replacements came with ICS so that I didn't have to worry about it. I tried the emergency firmware update which would get to 27% and also fail.
just root your phone, no more worries about bricking
About a week ago, maybe less, my xperia mini pro (gingerbread) notification led stopped working even when charging the phone. Thinking it was a software problem, I decided to factory reset it. It didn't solve the problem and I decided to just move on with my life since it isn't that important to me. With a then totally "empty" phone i updated it to ice cream sandwich just for the heck of it. Everything went fine until today.
When I wanted to unlock my phone to check if I had a text message, all it showed was a backlit screen with black on it. The back and menu button also lit up. When somebody called, the ringtone would ring but the screen stayed black. Took the battery out to turn it off and tried to turn it on again. Same thing happened, tried it few more times but nothing changed so I gave up. It didn't even display the sony logo when turning on.
A few hours later, when I try to start it again, it vibrates for a short time, then shows a backlit screen with black on it. Then it goes dark and after a few seconds lights up again. This goes on as an endless loop.
I have tried the SEUS tool. It told me my phone was updated but i tried to reinstall ice cream sandwich anyway, but it failed. And everytime the screen would lit up, the computer would make the sound when a usb is inserted; and when it would turn dark again, the sound when a usb is removed could be heard.
As I can't get into the recovery mode or any other mode I am at a loss on what I can try next.
At first I thought it might be the flex that was the problem but now I'm not so sure anymore.
The FUNNY part is that it happened today, TWO days after the 1 year warranty ended.
What options do I have?
Hope anyone can help me.
kittymeow said:
About a week ago, maybe less, my xperia mini pro (gingerbread) notification led stopped working even when charging the phone. Thinking it was a software problem, I decided to factory reset it. It didn't solve the problem and I decided to just move on with my life since it isn't that important to me. With a then totally "empty" phone i updated it to ice cream sandwich just for the heck of it. Everything went fine until today.
When I wanted to unlock my phone to check if I had a text message, all it showed was a backlit screen with black on it. The back and menu button also lit up. When somebody called, the ringtone would ring but the screen stayed black. Took the battery out to turn it off and tried to turn it on again. Same thing happened, tried it few more times but nothing changed so I gave up. It didn't even display the sony logo when turning on.
A few hours later, when I try to start it again, it vibrates for a short time, then shows a backlit screen with black on it. Then it goes dark and after a few seconds lights up again. This goes on as an endless loop.
I have tried the SEUS tool. It told me my phone was updated but i tried to reinstall ice cream sandwich anyway, but it failed. And everytime the screen would lit up, the computer would make the sound when a usb is inserted; and when it would turn dark again, the sound when a usb is removed could be heard.
As I can't get into the recovery mode or any other mode I am at a loss on what I can try next.
At first I thought it might be the flex that was the problem but now I'm not so sure anymore.
The FUNNY part is that it happened today, TWO days after the 1 year warranty ended.
What options do I have?
Hope anyone can help me.
Click to expand...
Click to collapse
Try flashing a stock Firmware using Flashtools(if you don´t know how look at Tutorials Section)
If it doesn´t help, then is a Hardware Problem
That's really hard that the warranty just ended. Maybe you could ask a local carrier if sony would be so nice to repair it under warranty because I think it is a hardware problem and if your bootloader is locked and you never rooted and tried some things, don't try to flash the stock rom first, better ask sony :good:
If they won't do it, flash stock gingerbread rom and try to boot it again. But as you tell it it's hardware related
mihahn said:
That's really hard that the warranty just ended. Maybe you could ask a local carrier if sony would be so nice to repair it under warranty because I think it is a hardware problem and if your bootloader is locked and you never rooted and tried some things, don't try to flash the stock rom first, better ask sony :good:
If they won't do it, flash stock gingerbread rom and try to boot it again. But as you tell it it's hardware related
Click to expand...
Click to collapse
I was hoping it isn't hardware related, but you're the 3rd person now who told me that it is. I never rooted or anything, so I'll just go to the sony service center then. Hopefully they'll be so nice to give a little extension of the warranty. Hahah.
Thank you for replying.
The solution is Getting Flashtool,installing ADB Drivers,Downloading stock Firmware and flashing.
But if you don't want to try,Taking it to SONY would be the solution.
If your warranty is over,then the service center guys charge a lot :crying:
Goodluck :good: And you could ask an experienced guy in your area to help you flash!
:good:
How is it that you have only a one-year varranty? The carrier varranty is usually one year only, that is true, but the manufacturer varranty, at least in Poland, is 2 years mandatory. And it's written in varranty papers included in the box
Double check before you pay
Take out your battery fir a while
Then try to install a proper kernel and flash a stock rom with flashtool
Sent from my Live With Walkman using xda premium
Graveir said:
How is it that you have only a one-year varranty? The carrier varranty is usually one year only, that is true, but the manufacturer varranty, at least in Poland, is 2 years mandatory. And it's written in varranty papers included in the box
Double check before you pay
Click to expand...
Click to collapse
Those are the advantages of being in the EU, which made it mandatory to have 2 yrs of warranty (1 by builder 1by re-seller i think), that doesn't work outside
I had the exact same thing happen to me. It happened a couple of weeks after I upgraded it to the official ICS. First I thought it was a hardware problem since my phone had fallen the previous day. I decided to try and do a software repair via PC companion which didn't help.
So, further convinced that it was a hardware problem, I brought it to the shop where I got the phone (it was still under warranty). They simply downgraded the software to GB. Problem solved.
Hi all,
I had my Z4 Tablet from O2 yesterday, and it seems to me like it might have a hardware fault perhaps?
When I first switched it on, it booted up normally so I went through the initial setup, but halfway through it froze for a couple of seconds, then the screen went off and I got a flashing red light. Seemed to flash 3 short, then on the fourth flash it stayed on for a couple of seconds, before going off and the thing rebooted.
It seemed to work ok after it rebooted, so I messed around with it for a few minutes, but it froze again, red flashing lights, and reboot. It seems to do this randomly. Sometimes it can be ok for a while, but then bang, off it goes again. I'm not doing anything heavy, just browsing internet every time it's happened.
I did a factory reset, didn't install anything other than updates, and it is still doing it.
Mine is the UK Z4 Tablet LTE version, the SGP771.
I'm still within my 14 day cooling off period, so I want to resolve this asap. If it's a hardware glitch, it's going back.
Any thoughts?
could be a hardware glitch...
I see this (red LED) when I mess up with newer kernels - but then it is a bootloop and not intermittent.
What software version are you on?
Bootloader locked?
Branded firmware?
Tried an OTA Update?
DHGE said:
I see this (red LED) when I mess up with newer kernels - but then it is a bootloop and not intermittent.
What software version are you on?
Bootloader locked?
Branded firmware?
Tried an OTA Update?
Click to expand...
Click to collapse
It's brand new, and completely stock.
Locked bootloader
O2 branded latest firmware.
It did it when there was no sim in it, or memory card, literally as soon as I turned it on and tried going through the setup. Since then it's been random. I can sit and watch a video fine, then it'll do it again while I'm just browsing.
It doesn't seem to be getting hot, just a little warm. Quite surprising cos my Z5 can get really hot sometimes.
I was going to try reflashing it. I'll get the firmware from XperiFirm later and try that and see.
I have 30 days to return it for exchange for a brand new one, so can't mess about too much.
I am sure "latest" has a number....
O2 branded latest firmware.
Click to expand...
Click to collapse
With 28.0.A.8.251 or newer you should be fine.
If you have this already I would swap the device with O2.
DHGE said:
With 28.0.A.8.251 or newer you should be fine.
If you have this already I would swap the device with O2.
Click to expand...
Click to collapse
Yes, that's the one I have lol (I just wasn't at home to check) and I think you're right. I'm going to speak to O2 and get it swapped I think.
Thanks for the advice, appreciate it :good:
Quick update …
I downloaded the O2 branded 28.0.A.8.251 firmware from XperiFirm and flashed it with Flashtool, said yes to the FSC script, and it flashed without errors.
It didn't wipe userdata (due to the script I think) even though I selected full wipe options in Flashtool, but that's fine. Didn't have to go through the setup again.
I ran a stability test in Antutu so it got pretty warm, then I downloaded some random game and ran it, ran some other apps. The tablet did get pretty warm. CPU Z was showing some temps up to 85C.
So far it hasn't reset once. I thought it might when it got hot, but it didn't.
I did go through the diagnostics and everything checked out as working properly, all the sensors seemed fine, speakers, mic, etc.
I'm kinda hoping it was only a glitch in the software, but it hasn't filled me full of confidence, so I'll be watching it like a hawk over the next few days.
When I'm happy that it's ok, I'll probably flash the CE1 region unbranded firmware (like I do on my phones) because they always seem to get the updates first, and I've already noticed the .260 update has rolled there.
Well fingers crossed. I'll be back with any updates.
Update . . .
. . . well, did it again, so factory reset, did it again, repaired it with Sony PC Companion . . .
. . . lasted 2 days, and it seemed as if it wasn't going to do it again, getting some good use out of it, then BYE!! Off it went again . . .
. . . Flashing red LED.
Rang O2 customer service and explained what it was doing, and they're doing a doorstep swap tomorrow for a brand new replacement so pretty happy with that.
In hindsight I should have rang them the first day because flashing red lights on a completely stock device is pretty much damn sure a hardware fault I reckon.
I'm quite surprised actually. This is one of many Sony devices I've owned. I started years ago when it was still Sony Ericsson, had a P900 which was way before it's time really, and had many more since, and this is the first one that's had a major fault.
Either way, should be solved tomorrow :fingers-crossed:
could be the battery warning light...
wise decision to swap the device!
a faulty battery or wiring...