Hi there,
I have a Pantech Vega Iron IM-A870L that is suffering from Baseband Version Unknown issue.
By now I am pretty sure that it is a hardware fault and the baseband chip is gone.
I just want to use it as a none GSM device, but if I let it on for a while, it takes battery juice pretty quick. Like 30% gone in just 3 hrs idle (no usage). The batter stats show that "Android System" is responsible.
Also the cell is working very slow and hangs on mobile network related pages. Like if I try to view mobile network settings etc. If I press power button to turn of screen, I cannot turn it back on until upto 5 mins, it just wont turn the screen on, because I guess at this event too it tries to access the baseband.
In the UMTS menu secret page ##7593#, I get a message something like "rild is not reachable".
When I go to info secret menu *#*#4636#*#* and then Phone Information, it shows a white screen then black screen and no activity. I can press the back and home buttons to activate the task manager though and kill this page.
I understand this is because it keeps on trying to access baseband and it does not find it.
I have two questions:
1) Is there a sure way to find out if it is a hardware fault in baseband or just a s/w fault? My phone uses custom ROM and is rooted.
2) Is there a way to tell the os that there is no baseband chip in the cell and it should not try to contact the baseband chip. Just like it works for tablets without sim card.
Thanks
It looks like my phone's baseband chip is intact.
Past few days I flashed a Lollipop ROM and the phone got stuck on startup. So I downloaded another JellyBean ROM and flashed it. The phone started but the baseband issue was still there.
After few days, when I restarted the phone, it suddenly asked me for usim, I turned it off and inserted sim and then turned on, and the phone was working perfect! like no issue at all!!! baseband was showing some version as well as calls were going out and everything.
After a while, suddenly it gave me an error like:
System restart due to application operation error
if you detach battery now, may seriously damage your phone
so I waited for the phone to restart and the baseband was gone again
But after that, it is doing the same thing on and on, it suddenly shows baseband and then after a while phone shuts down with message and then baseband again unknown.
This gave me the idea that the hardware is intact, and there is no problem with it. Only the rom is not good.
If I can get the proper rom for it, and can flash it, then may be all these problems go away.
I do have a .binx rom but the method to flash it using the IE page does not really work. it gives me some USB error while all my usb drivers are installed. I will give it another try though.
But atleast I have found out that there must be a solution to my problem and my phone is not actually bricked!
I will update the post as there is any further development.
Related
well to start with, i bought this samsung galaxy s2 mobile, it has been working absolutely fine until 3 days ago. My battery was low and it went into flight mode, i connected my mobile to the wall charger and it started charging up but since then, my mobile is in flight mode, i keep turning it off and it internally goes into flight mode, in settings it shows its off but on top bar of my screen, there is the flight icon, i cant make or receive any calls/texts since this started happening, I tried soft reset (removing the battery for few mins), didnt work. I tried to factory reset my mobile but its asking for some password, i tried my google password from which i configured the device at the time of purchase, but it says the password is incorrect. Pls help
Thanks
Jibran
Make sure that when you enter your password you are connected to your/a wifi network because I assume you don't have mobile internet on flight mode.
Also, this may sound stupid but make sure you don't have any app or WIDGET that enables/disables fly mode, also long press your power button until the popup and see if flightmode is disable there too.
Last, go into your Phone Information and make sure you have a baseband and an Imei
*#06# on your dialer.
security password to protect your data,assuming you tried to master reset in android,if you didnt make one and have warranty,take it back, because the other process will void your warranty
flash with odin on windows
status of my mobile
Model no : GT-I9100
Android Version : 2.3.4
Kernel Version : 2.6.35.7-I9100XWKI4-CL575468 [email protected]#2
Base Version : unknown
Build no : GINGERBREAD.XWKI4
I'm having the same problem, but i assume that i got it when the phone was updated OTA to 4.0.3 (LPG). I certainly did'nt have the problem beforehand.
It's absolutely useless to try to disable flightmode, both with powerbutton and manually inside settings - the phone never goes out of flightmode, even that it says that flightmode is disabled in settings, and when pressing powerbutton.
My solution though, is to disable flightmode and rebooting the phone. That works, but i don't know if that solves your specific problem. Irritating problem though - it somehow destroys the feeling of a good phone...
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Hmm, sounds like a faulty phone to me. Try taking it back to get it exchanged for onother one. S3 was built to fly not crawl.
You'll want to go through a process of elimination to figure out when might be causing it.
Something you can try and test with (one at a time)
-turn on airplane mode
-turn off live wallpaper
-shut down all running tasks
-change your lock screen security method
-limit the number of widgets running on all the screens
-reduce the number of active screens
Probably other things you can try to pull out of the equation, but thats a good start
After looking up dial-a-phones returns policy it would seem that I have 28 days to return if the handset is faulty, so this atleast gives me some breathing room to try out any suggestions for fixes. I will begin to eliminate each of the suggested items above however as the lock screen problem is intermittent it make take a day so actually see if it has had an effect, which is annoying at the least.
On another note a numberupted of people are stating high battery life on their devices however mine doesn't seem to be as good and I do have power saving on as well as nfc etc. turned off. This makes me believe my handset could have a fault, but tbf I haven't allowed for a discharge to 5% and the recharging to 100% which I heare allows for optimisation of the battery.
EDIT**** I have changed the lock screen previously and found it had no effect on the problem and I do not have a live wallpaper in use.
Phone Freezing after reboot and auto wifi signal found on.
Same here, been happening the last few days after I installed Avast. Also, turning off and on the auto on wifi seemed to replicate the problem.
The phone will boot to the lock screen and freeze a bit, and sometimes the news ticker freezes, and then after unlocked, I try to turn off wifi signal has been found on the notification dropdown and then tries to auto connect to wifi, the phone will freeze up if I dont turn it off in time.
Once the auto wifi connect is off and reboots, then the phone will keep glitching up until it catches up processing alot of processes it was trying to do for about 1/2 hr. Also, if phone freezes up for too long, like after trying too many time of unlocking the screen while freezing up, the phone gets stuck at the lock screen and the phone almost overheated, in an area right below the battery. I had to pull the battery out to cool it off.
It seems to be a glitch in the auto wifi, especially if alot of resources are being used. Once Avast was on my phone about 1.5GB RAM is being used sometimes and since has really slowed the phone down. Going uninstall alot of apps.
JCrinage said:
Hey guys,
I know there has been a couple of posts like this that I have found through searching but none have actually found a solution, so instead of resurrecting a old thread I thought I would start a new one.
Basically I am having some issues with my new pebble blue (yey) S3 . I have found that sometimes when the phone is sleeping when I press the power button to bring it out of sleep the lock screen begins to hang. This is followed by a number of different things, the screen either glitches for a bit and then begins to work or it stays locked and needs a battery pull. As well as this I've found that randomly either when charging or not and the phone is sleeping it simply becomes unresponsive, staying on a black screen and needing a battery pull to fix (this has only occured a few times, the hanging lock screen occurs quite often).
I have done some searching and found little in the way of a solution or what the problem is, however I have found that when the lock screen hangs -if it begins to work again after glitching out the 'WIFI connected to ****' appears at the bottom of the screen. Anyway if anyone has any ideas or also recieves this problem I would really appreciate some help as it's driving me crazy and I'm unsure if it is a common S3 bug or a faulty handset, in which case I have limited time to RMA.
Cheers in advance
Click to expand...
Click to collapse
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
sassorock said:
Same problem.
No problem if Wifi is switched off prior to sleep.
No problem if Wifi connection is still available.
Problem to lockscreen if Wifi connection is broken (move away from connected router).
Any suggestion?
Click to expand...
Click to collapse
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
S3 black screen after unlocking
Has there anyone experience S3's screen went on black? I have pebble blue S3 - GT-I9300. Cases when unlocking, answering an incoming call or attempting to turn off an
alarm? Mine happens when after unlocking the screen then it goes black and screen becomes unresponsive. It happens intermittently and even after 3 times of
reprogramming. I am now going to have it replaced. I am having a lot of troubles -- it exits on its own when im reading or composing an SMS; files were deleted after
restarting the unit, and an app opens up even not touching the scree. This is expensive and I am paying a lot just to experience this king of inconvenience.
DavidNieuwpoort said:
Exactly the same here. Driving me crazy. I did root the phone using the Samsung Galaxy S3 Toolkit. I don't know if the problem also exists on non rooted devices.
Click to expand...
Click to collapse
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Flodas said:
I also rooted my S3 a few days ago (with the S3 toolkit), and have had lots of problems with unresponsive lockscreens (I use PIN, because of exchange connection). It takes a few seconds or maybe up to as long a minute before I'm able to punch in the PIN-numbers. Before this the screen lights up but does not respond to input.
But the WiFi-connection issue might be what is the triggering factor, because after a boot it wotks just fine for several hours, if I'm not moving out of my current WiFi zone. First I thought it was either Secure Settings or Tasker that made my device lock up in this matter, but now as they are both uninstalled, the problem still occurs.
Are you running some kind of custom rom, or just the latest stock ROM, but rooted?
Click to expand...
Click to collapse
Just the latest stock ROM but rooted. I've found out that turning off the wifi power safe mode fixes the problem for me. To do this:
- In the dailer enter *#0011#
- Press the menu key
- Select wifi
- Press the on/off button.
The wifi power safe mode will however be turned on during boot. So rebooting will set it back on.
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
I am also on stock Rom and rooted. Interested to know any non-rooted phone got this problem?
BTW. I found a quick (at least quicker than pull the battery) way to get out of the forzen lock screen (sometimes forgot to do the 0011 trick): press the power button (screen will Dim instead of OFF), then hold the home button for few seconds, as soon as you see the "menu" and "back" button lit up, the lock is un-freeze...
A permanent solution is appreciated for such an advance phone....
sassorock said:
*#0011# seems does the trick. But is annoying had to do this every time after power off (change battery, change Sim, flying).... Anyway to keep the setting?
Click to expand...
Click to collapse
Not that I know of.
Problem solved. For me anyway. Hope works for all of you having the same trouble.
My trouble begin with recent upgrade to LH3. My S3 was rooted by S3 toolkit v2.0. CWM installed was v4 something.
I un-rooted the phone. Uninstalled S3 toolkit v2.0. Re-installed the S3 Toolkit v5.0. Rooted the phone again (CWM become v6....).
I do not know it was CWM version caused the trouble or not. But my S3 is ok now.
I got it on my non-rooted phone, any additional solutions/suggestions? or service?
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
JB 4.1.1 caused these WiFi issues on my phone
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
Exact opposite for me...never had the problem then since loading stock JB 4.1.1 with root I get lockups or freezes whenever WiFi is turned off or I leave my router's range. As soon as I disconnect from WiFi the whole phone freezes.
The *#0010# also locks up the phone when I turn off the WiFi power saving feature.
None of this happened before JB...and I replaced my phone with week via warranty due to this and the new phone does the exact same thing as soon as I upgraded to JB with root.
Any ideas?
Black screen / random reboot solution
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
giz_zard said:
Hi All,
I've had the black screen / random reboot issue for a few days. The only way to restore functionality on black screen lockup was to remove the battery.
I tried changing to Chrome browser and stopping the stock browser as suggested in some threads but it kept crashing.
I searched everywhere and most threads suggest a dodgy motherboard.
For me the issue was related to either a single PDF download via the stock browser or the fact I had quite alot of saved PDF files on my phone (S3 Stock firmware I9300XXELLA)
After deleting all the files listed in Internet downloads (look for Downloads with a green arrow Icon in apps) my trusty S3 has returned to normal. No black screen lockups, no hanging, runs like a dream!
I appreciate this may not solve everyones black sceeen issues but I haven't found any other thread with this solution. Hope it works for you.
Thanks,
Giz.
Click to expand...
Click to collapse
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Jodatnia said:
I found solution for problem . And my phone is working well. I downloaded rom file android 4.1.2 and flash my phone
Click to expand...
Click to collapse
For me this also worked. Resolved everything. (on i9300 int)
Boomer6345 said:
Thanks for the tip...
Was this happening on JB for you? You mention stock firmware (not familiar with I9300)...so I am guessing it was ICS.
For me the issues are with JB and I had no files at all in the Downloads folder after a certain point when I wiped / formatted the SDCard...so I do not think my lockups were related to PDFs. But I did (and still do) have a ton of music and a lot of movies on the External MicroSD Card....and quite a few custom notification and ringtone MP3s on the Internal SDCard. Next time I load JB I will run it a few days with none of this media loaded....
Click to expand...
Click to collapse
This is on JB 4.1.2, Phone had been updated to 4.1.2 for about a month. The issues started after a pdf download. Once all pdf's were deleted the handset works perfectly.
Giz
I have a strange problem.
My Galaxy S2 (9100) is not turning off the screen anymore.
When I press the power button, usually the phone would turn off the screen and go into sleep mode.
Now the phone immediately wakes up again, showing me the lock screen.
I got that phone on Android 2.3.3 (Gingerbread) where it ran fine in the beginning.
Then this behaviour appeared. I have updated to ICS (4.0.4) via Kies software and problem still exists.
I then thought I might try a completely new ROM, so got CyanogenMod latest stable release from their website and installed that (with google apps).
No other software installed, so I can exclude this as a problem.
Problem still persists.
So it seems not connected to any ROM neither to any software.
The strange thing is:
The power button is working, because I can
- long press to bring up the menu to shut down the phone (which works ok)
- short press and the screen will turn off - only it comes on a second later again.
Obviously this drains the battery quickly.
Help please!
TheMobilist said:
I have a strange problem.
My Galaxy S2 (9100) is not turning off the screen anymore.
When I press the power button, usually the phone would turn off the screen and go into sleep mode.
Now the phone immediately wakes up again, showing me the lock screen.
I got that phone on Android 2.3.3 (Gingerbread) where it ran fine in the beginning.
Then this behaviour appeared. I have updated to ICS (4.0.4) via Kies software and problem still exists.
I then thought I might try a completely new ROM, so got CyanogenMod latest stable release from their website and installed that (with google apps).
No other software installed, so I can exclude this as a problem.
Problem still persists.
So it seems not connected to any ROM neither to any software.
The strange thing is:
The power button is working, because I can
- long press to bring up the menu to shut down the phone (which works ok)
- short press and the screen will turn off - only it comes on a second later again.
Obviously this drains the battery quickly.
Help please!
Click to expand...
Click to collapse
Hmm this is really strange
Maybe it's a "loose connection" of homebutton?!
Try do press a bit "harder" "softer" "more up" etc... hope u know what I mean....
If one of the pressings work it seems to be a hardware prob.
If always the same it must be a software problem and u can try to flash a new kernel (if u also on Cyanogenmod)
Much success
CHEERS
Of course I have already tried to press the power button in any way I could imagine (soft, hard, more up, more down, etc) - always the same result: Screen turns off and comes back on immediately.
The question is, what kind of hardware failure can this be? The power button seems to works.
Are there any hardware features on this phone that would either automatically turn on the screen or prevent the phone from going into standby? I know some of the newer phones have a function that detects if one is watching the screen and then prevents standby. Maybe such a feature is malfunctioning? Only I am not aware that the S2 has such a thing.
I don't think it is a software issue, because I have had the same experience with 3 different ROMs now (Gingerbread, Stock ICS, CyanogenMod 9)
Same issue Here .......
I updated to the latest nightly (9/22) to try and relieve this problem to no avail. I've been running CM Nightlies on my P4 since they've been available. I always manually download them since, for whatever reason, Rom Manager seems to detect my device as the P4-wifi. I assure you the 3G (HSPA) modem works. I have a SIM slot, with SIM that has activated service (UMTS/HSPA). My cell phone is on the same networks and it picks up signal from my carrier fine.
With that out of the way; My issue:
Two days ago, I was leaving my house to visit family, and I wasn't going to bring my charger for my Tab, so I put the device in airplane mode to conserve battery. In hindsight, I should have just asked the device to power off, but that's besides the point. When I tried turning off Airplane mode, the cellular network did not become available again; this situation has not changed since.
What I've done: Rebooted the device after switching out of airplane mode, re-entered airplane mode and left it again, updated to the latest CM. I've opened my tab and reseated the connections for SIM and antenna (at least, the connections I can reseat, I have), I've also completely disconnected power by unplugging the battery and reconnecting it. Additionally, I got into some of the hidden menus and verified that WCDMA, which, I believe is the underlying tech for the local HSPA connection, is preferred to the cell radio.
Looking at the device, if I ask it to check for mobile networks, the list comes back blank. The network status shows "UNKNOWN:0" and the lockscreen shows "NO SERVICE." instead of "NO SIM" (which is what it shows when I remove the SIM). From what I can tell the radio has shut off and will not come back on.
Throughout all this Wifi still works perfectly, so the device isn't useless, however, I'm planning to sell this device and I would like it to be as fully functional as possible when I hand it off to it's next owner, so getting this solved is very important to me. Any and all suggestions are appreciated and I'm basically willing to try anything at this point. I feel as though I've tried everything short of a factory reset, which I'm not sure if that would help (I've even wiped cache and dalvik).
In case it's relevant, I'm in Canada, carrier is Telus.
Thanks for reading.
EDIT: I've just finished restoring the device to Stock 4.0.4 (I've used this stock image before when I had issues with the device and confirmed it is fully functional) and I am still having trouble. this points to either a carrier issue or a hardware issue. I will be calling the carrier in the morning, despite believing that this isn't the case. any suggestions on what could be the problem are still welcome, I'm willing to try just about anything at this point.
@Mystik
Back in the CM 4.1.2 days on the e4gt...we had a similiar problem. Now, I don't have you're device. But when this problem arose in the epic. We had a work around where we would turn airplane mode on and power off the device. Then power the device back up. When that didn't work we had to flash a modem, then flash back to the one we wanted.
Also, make sure after you turn off airplane mode.. that the mobile data under settings/more is enabled... sometimes it will not re-enable itself.
Let me know if this works.. if not I would be happy to help you search up a fix..
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service