Hey guys,
I just bought a Z3 Compact (D5803) for my girlfriend on eBay. It said the condition was new (other). I set up the device, and it was running 4.4.4 Kit Kat. Everything was fine and normal. I just plugged it in and updated the phone to Lollipop, and now when I boot it up there is a docomo screen, and in the settings there is a new section for docomo. All I did was update the phone through the Sony Xperia Companion program on Windows 10. Is this something I can get rid of? Or do I have to unlock the bootloader and flash a non-docomo ROM? I would hope there is a way to get rid of the docomo stuff, but I guess that's probably not possible?
Thanks.
EDIT:
I fixed it. I found the thread with all of the firmware, and I flashed the FTF for the USA 6.0.1. Now everything is great, no more Docomo!
chris23445 said:
Hey guys,
I just bought a Z3 Compact (D5803) for my girlfriend on eBay. It said the condition was new (other). I set up the device, and it was running 4.4.4 Kit Kat. Everything was fine and normal. I just plugged it in and updated the phone to Lollipop, and now when I boot it up there is a docomo screen, and in the settings there is a new section for docomo. All I did was update the phone through the Sony Xperia Companion program on Windows 10. Is this something I can get rid of? Or do I have to unlock the bootloader and flash a non-docomo ROM? I would hope there is a way to get rid of the docomo stuff, but I guess that's probably not possible?
Thanks.
EDIT:
I fixed it. I found the thread with all of the firmware, and I flashed the FTF for the USA 6.0.1. Now everything is great, no more Docomo!
Click to expand...
Click to collapse
I know you've fixed the issue so I don't really need to say anything but I thought I would anyway.
DoCoMo's a Japanese provider if I remember correctly. I'm guessing that the phone was originally from Japan so Companion just put the latest Japanese rom on. As long as it still works with your network, that shouldn't be a problem. Boot animations and settings in..er..Settings can always be changed.
Ticklefish said:
I know you've fixed the issue so I don't really need to say anything but I thought I would anyway.
DoCoMo's a Japanese provider if I remember correctly. I'm guessing that the phone was originally from Japan so Companion just put the latest Japanese rom on. As long as it still works with your network, that shouldn't be a problem. Boot animations and settings in..er..Settings can always be changed.
Click to expand...
Click to collapse
Thank you for the response. The story has gotten a bit complicated for me haha. When I put the newest firmware, NFC stopped working completely on the phone. It said the NFC firmware couldn't update. Apparently if you run firmware that is different than the DoCoMo firmware, NFC breaks. But the weird thing is, the DoCoMo variant has a different model number, and has the DoCoMo logo all over the back. Mine is supposed to be the D5803 and doesn't have the logo on the back. So now I'm trying to talk to Sony and the eBay seller to see what's going on with that. Not sure if you have any idea about that. I wonder if it was the DoCoMo variant and the eBay seller just replaced the back cover or something.
Related
Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!
I would stay on 4.1.2. 4.3 is a piece of crap. I made the mistake of upgrading and had to downgrade. I tired many roms and did not like any of them. Stock, root and xposed frameworks still best for stability, features and battery life.
spsony120 said:
Hello to everyone!
This is my first post to this great forum. Recently I bought a Sony SP C5303 and now I face a complicated problem and I want your help.
The situation:
The phone was bought as unlocked (and not rooted) and when I got it, it prompt me to update to the 4.1.2 12.0.A.2.254 as previously had an older build version. I successfully did the update and everything works fine BUT right now I am wondering why I can't see the official update for 4.3
After a lot of search I realised that the phone was supplied from T-mobile (UK) as it has customization version 1272-7168_R6A
So, the phone is unlocked, unrooted and since I bought it operates on Three network.
However either when I connect it with PC companion, or I do the manual search for updates through the headset, I am unable to see the update to 4.3
I am wondering if there is any conflict between the T-mobile unlock and the Three network that I operate the phone.
Is there any way so I can trigger the update? Should I wait a little bit more? I am not sure and I am not so good with these things.
The only I want is not to cause the phone to lock somehow or to install a custom rom, neither root it.
Thank you very much for your help and your answers!
Click to expand...
Click to collapse
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum
kidicarus1602 said:
This is due to the mobile operator themselves. I am with o2 and do not have the 4.3 update for my SP either, it is down to the operator to decide when they release the update as they have to fill it with their bloatware first!
You can of course flash 4.3 yourself using flashtool I did, their are plenty of guides on this forum
Click to expand...
Click to collapse
To be honest I am a little bit confused what determines if the phone is going to update or not.
I mean that is the provider responsible for delivering the update or the customization version? If we think that with no sim, we just plug the phone to pc companion and it is able to see the update, then it depends on customization version.
Is there any official reference for how the phone is determined to be valid for the update?
I still believe that there is a conflict here between the current provider I operate the phone (Three) and the customization version that comes from T-mobile (the phone was unlocked from T-mobile).
Thanks guys!
P.S @xEaGLeNeC Wow!!I heard completely the opposite from many people. They claimed that the phone battery last more with 4.3! I will try to search more if it finally worth to update or not.
Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))
KrychoPL said:
Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))
Click to expand...
Click to collapse
Use flashtool to flash stock firmware by ftf file. Here:
http://forum.xda-developers.com/showthread.php?t=2311964
Use an older one and if that does not work, try one or two more. Hopefully, that will help. Best of luck!
shahrukhqasim said:
Use flashtool to flash stock firmware by ftf file. Here:
http://forum.xda-developers.com/showthread.php?t=2311964
Use an older one and if that does not work, try one or two more. Hopefully, that will help. Best of luck!
Click to expand...
Click to collapse
Does it matter which country is it for? I can try some of them but i think that won't help. I've checked other sim card and it was recognized but didn't even ask me for pin. Weird Oo.
If nothing helps i will just flash stock firmware with SEUS and let sony service take care of it, hopefully. Phone still has guarantee.
KrychoPL said:
Does it matter which country is it for? I can try some of them but i think that won't help. I've checked other sim card and it was recognized but didn't even ask me for pin. Weird Oo.
If nothing helps i will just flash stock firmware with SEUS and let sony service take care of it, hopefully. Phone still has guarantee.
Click to expand...
Click to collapse
Regions perhaps. But the thing that does not make sense it that that why did it work before and not now? It should work. Anyway, my SIM was mini too. I, too, had to cut it. It works. Or possibly contact your service provider maybe something is wrong with the SIM. They might have have locked it or something?
shahrukhqasim said:
Regions perhaps. But the thing that does not make sense it that that why did it work before and not now? It should work. Anyway, my SIM was mini too. I, too, had to cut it. It works. Or possibly contact your service provider maybe something is wrong with the SIM. They might have have locked it or something?
Click to expand...
Click to collapse
If none sim card works on phone then it is IMEI problem or phone itself somehow. I'm trying to flash other roms now. Hopefully it will help if not then sending to service.
KrychoPL said:
Hello,
I've a weird problem with my Xperia SP. Today i wanted to get back to rom based on stock rom to get miracast feature.
I downloaded newest existenz rom and williams kernel for stock based roms. Installation went fine system booted ok and everything worked fine. After some time phone turned off and didn't wanted to start. Only flashmode worked. I've decided to download stock .205 CE1 rom and flash it.
It booted up, sim card was recognized(had to write PIN). After that network was not found. Signal with red "X". I've tried to manually register to network but i could not.
Next thing is that after flashing stock rom fastboot mode stopped working. Service menu shows that Bootloader can not be unlocked even that it was unlocked before and flashtool(BLU option) shows that it is still unlocked. Flashtool also shows Bootloader: NOT_ROOTABLE.
I have actually no idea what have happend. Now i'm installing stock rom using Sony PC Companion but i think this wont help for network problem.
My main network is PLUS GSM(Poland network).
Could sim card die? It is old type card (almost 10 years) and i had to cut it manually to fit micro sim for the phone.
prntscr,com/45wtip (swap ','(comma) with '.'(dot))
Click to expand...
Click to collapse
i got the exact same problem right now after using william kernel, can you fix it?
Muh_lukman94 said:
i got the exact same problem right now after using william kernel, can you fix it?
Click to expand...
Click to collapse
I've reflashed stock rom using SEUS and sended phone to sony service. Hopefully they can help. Be careful with Williams Kernel for stock roms. This may be a common bug.
For anyone who had the same problem. Sony exchanged my whole phone with information that mainboard was broken. They said that phone could not be fixed.
Good luck
PS. Topic can be closed i think.
KrychoPL said:
For anyone who had the same problem. Sony exchanged my whole phone with information that mainboard was broken. They said that phone could not be fixed.
Good luck
PS. Topic can be closed i think.
Click to expand...
Click to collapse
Where have you been before? I have the same problem after flashing William kernel for stock rom((( What to do now?
Everything i've done is described in the thread. Phone was exchanged by sony after all.
KrychoPL said:
Everything i've done is described in the thread. Phone was exchanged by sony after all.
Click to expand...
Click to collapse
I think i have the same problem, but up till now no one knows the answer, the biggest problem is my warranty is over, i hope someone here can help :crying:
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
KrychoPL said:
Everything i've done is described in the thread. Phone was exchanged by sony after all.
Click to expand...
Click to collapse
I have the same problem here, and the biggest problem is my warranty expired, hope someone here can help..
Muh_lukman94 said:
i got the exact same problem right now after using william kernel, can you fix it?
Click to expand...
Click to collapse
do a restore of Your TA will fix the problem, now my phone can detect SIM card
After updating to Lolipop on the Z3 Compact the mobile internet works on the phone (THREE Network) but when I try the teathering / hotspot it doesn't work, No point trying to contact THREE as all they say is they don't allow teathering on Pay as You Go even tho I've been teathering for years without issue till this **bleep** Lolipop came along!!!
Any one found a cure for this?
vxlomegavy said:
After updating to Lolipop on the Z3 Compact the mobile internet works on the phone (THREE Network) but when I try the teathering / hotspot it doesn't work, No point trying to contact THREE as all they say is they don't allow teathering on Pay as You Go even tho I've been teathering for years without issue till this **bleep** Lolipop came along!!!
Any one found a cure for this?
Click to expand...
Click to collapse
What customization? Unbranded or 3?
istux said:
What customization? Unbranded or 3?
Click to expand...
Click to collapse
Its a standard phone "stock" in other words its not been rooted etc... Was originally an O2 branded phone but i had it unlocked awhile ago, Used to work fine on kit kat even the day before the update, lollipop has done something by looks of it.
vxlomegavy said:
Its a standard phone "stock" in other words its not been rooted etc... Was originally an O2 branded phone but i had it unlocked awhile ago, Used to work fine on kit kat even the day before the update, lollipop has done something by looks of it.
Click to expand...
Click to collapse
Open the phone dial pad and press *#*#7378423#*#*, then tap on Service info > Software info and read the number under "Customization Version"
Tell me that number
Have you done a FACTORY RESET?
istux said:
Open the phone dial pad and press *#*#7378423#*#*, then tap on Service info > Software info and read the number under "Customization Version"
Tell me that number
Have you done a FACTORY RESET?
Click to expand...
Click to collapse
"Customization Version" is 1288-6818_R5C
Haven't tried a factory reset, Is there any reason why this could be happening? Is the network able to block hotspot on lollipop or something?
Have seen others saying they are having a similar problem, here for example talk.sonymobile.com/t5/Xperia-Z3-Z3-Dual/Tethering-hotspot-problem-with-Z3-after-Lollipop-update-23-1-A-0/td-p/955798
I tried the sim in a iPhone and the hotspot works perfectly, it's got to be something to do with lollipop.
vxlomegavy said:
"Customization Version" is 1288-6818_R5C
Haven't tried a factory reset, Is there any reason why this could be happening? Is the network able to block hotspot on lollipop or something?
Have seen others saying they are having a similar problem, here for example talk.sonymobile.com/t5/Xperia-Z3-Z3-Dual/Tethering-hotspot-problem-with-Z3-after-Lollipop-update-23-1-A-0/td-p/955798
I tried the sim in a iPhone and the hotspot works perfectly, it's got to be something to do with lollipop.
Click to expand...
Click to collapse
1) Lollipop is a major release and a factory reset is highly recommended.
Many people have had issues with this upgrade and most of them solved with a factory reset.
I know it's annoying but just give it a try.
2) Your firmware is still branded (O2) and since you are on another network, I suggest you flash the UK unbranded (1288-4954)
You can install the KitKat version from here (23.0.1.A.5.77): http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
and test the tethering.
Then, when asked, update to Lollipop and see if it works.
Don't worry, you don't lose the warranty and if you need, you can revert to 02 branded through a tool named Xperifirm :good:
istux said:
1) Lollipop is a major release and a factory reset is highly recommended.
Many people have had issues with this upgrade and most of them solved with a factory reset.
I know it's annoying but just give it a try.
2) Your firmware is still branded (O2) and since you are on another network, I suggest you flash the UK unbranded (1288-4954)
You can install the KitKat version from here (23.0.1.A.5.77): http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
and test the tethering.
Then, when asked, update to Lollipop and see if it works.
Don't worry, you don't lose the warranty and if you need, you can revert to 02 branded through a tool named Xperifirm :good:
Click to expand...
Click to collapse
I've never flashed a phone before, Could you point me in the direction of the appropriate guide for this Z3 compact
vxlomegavy said:
I've never flashed a phone before, Could you point me in the direction of the appropriate guide for this Z3 compact
Click to expand...
Click to collapse
Have you opened the link above?
Check it better, I made a tutor for beginners...
Before flashing, save everything from the phone because internal memory and user data will be wiped...
All sorted now, Its back on Kit Kat 4.4.4 and i couldn't be happier! Teathering on THREE now works once again
Thanks XDA
istux said:
Have you opened the link above?
Check it better, I made a tutor for beginners...
Before flashing, save everything from the phone because internal memory and user data will be wiped...
Click to expand...
Click to collapse
One more thing.
How do i stop the phone from badgering me about the available update, There a notification i cant swipe away or delete?
vxlomegavy said:
One more thing.
How do i stop the phone from badgering me about the available update, There a notification i cant swipe away or delete?
Click to expand...
Click to collapse
Notification can be hidden from settings>apps>all>update center (my settings are in Italian, I don't know how they're named in English, but they should sound something like that) and just uncheck "show notification" (or something like that) and enjoy your kitkat.
Anyway if I were you, I would try to update to lollipop now and see if it's lollipop the real problem with tethering. You can always flash kitkat again and again and again... now you know how to.
WiFi hotspot fix
Going back to the OP's original tethering problem, the fix is here (requires ADB):
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
I had the same issue myself on 3 UK, the fix resolved it 100%.
Perhaps this should be one for the FAQ?
grockstar said:
Going back to the OP's original tethering problem, the fix is here (requires ADB):
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
I had the same issue myself on 3 UK, the fix resolved it 100%.
Perhaps this should be one for the FAQ?
Click to expand...
Click to collapse
Yes, I could add this (actually I have already a couple of things to add)
But before I want to understand if with the new UK unbranded lollipop the problem is still there :silly: because with the unbranded kitkat it's all working...
grockstar said:
Going back to the OP's original tethering problem, the fix is here (requires ADB):
http://forum.xda-developers.com/z3/general/lollipop-tethering-t3058923
I had the same issue myself on 3 UK, the fix resolved it 100%.
Perhaps this should be one for the FAQ?
Click to expand...
Click to collapse
Worked great for me thanks. Z3 compact on Three UK
Z3 problem - hotspot not working any more
istux said:
Open the phone dial pad and press *#*#7378423#*#*, then tap on Service info > Software info and read the number under "Customization Version"
Tell me that number
Have you done a FACTORY RESET?
Click to expand...
Click to collapse
Hi, I can see I have exactly the same problem, I have actually tried the Factory Reset and did not work.
Please could you help me?
My Customisation Version is 1288-5028_R5C
Thank you so much
I'd hate to factory-reset my phone only to find this problem didn't get fixed by the act, and I'd have to slog through the entire set-up again. No, I think this is a 5.1.1 specific problem that Sony needs to address because prior to this FW everything was fine. So for now, I'll keep my fingers crossed and hope Sony will come through. If not, well, can't really do anything except roll back to 4.4.4.
Hi, Guys. I recently flashed a new Rom on my T-mobile Xperia Z. However whenever I update to 5.0.2 Lillopop I cannot get cell reception. I live in Guyana so I bought the phone online and had it shipped and unlocked. I have tried both the c66103 and the c6616 however in both , as soon as I update to Lollipop I lose cell reception. All other updates up to Kit Kat 4.4.4 work perfectly. Any advice? I figure it must be something like a baseband problem. I have already tried flashing that however the baseband # does not change. Any advice would be helpful.
Best Regards
sony rom is bugged with callings they said they repair it .
I recently even tried the 5.1.1 update but I still suffer the same problem. I get absolutely no cell reception. It's like the sim is not even being recognized by the phone. I am wondering about trying to build an ftf file however I am not sure if you can edit the baseband in that venture. I believe that it may be the baseband that is presenting the problem, however I am kind of a noob so I need to be sure before I try anything.
I just got brand new Xperia X Performance that came with 6.0.1, and I'm trying to figure out why I can update it. It's unlocked but not rooted, basically right from the factory as far as I know.
When I go into Software Update in the phone's settings, it says "Your device already has the latest available system updates."
When I use the Sony app on my PC it says my system software is up to date.
I actually can't find anything about this issue, anybody here have any ideas?
Thanks!
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
st3ch said:
try downloading and running xperifirm, find out if your region has the update at all, you should be able to update atleast to 7 anyway
There are a few variants that are considered as internal units or something like that and they don't get OTA updates, also HK units were stuck on 7 for some reason last time I checked. Mine is a french model, and yesterday I received the april security patches while the global variant got it two months ago
Click to expand...
Click to collapse
Thanks for the reply.
Here's a screenshot of Xperiafirm. https://ibb.co/dUCN3T
I'm in Canada, though I'm on Freedom Mobile, not Rogers or Bell. I don't think my carrier ever sold this phone, and I'm not sure what would happen if I flashed 8.0 made for Bell or Rogers phones.
Ideally I'd like 7.1.1 Canadian generic for Xperia X Performance, but I can't seem to find that anywhere.
I've also never done this so I don't really know what I'm doing, and don't want to void my warranty!
Thanks for you help!!
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
st3ch said:
Good the ROMs that you see for Canada are all latest 8.0 with May security patches and maybe your phone is one of these and the updates just got stucked for some reason.
First you have to check what kind of model you have to check this, to do so you should open the dialler and type
*#*#7378423#*#*
From the service menu you should select -> Service Info -> Software Info and look for Customization Version:
As I said mine is a french model so it states 1302-9342_R2E your should be something different but only the first 8 numbers matter
then look this number in Xperifirm if yours is everything different from Internal Unit (second column from the screenshot) then there is a easy way to try and update without loosing your warranty
First there is always a risk! But I have done this a few times for my Xperia U and Xperia M5 and had no problems at all.
Do a backup - contacts...everything you need as it will delete them
charge the phone to at least 80%
then you should go to the Xperia Companion and do a software repair, not update but repair
It should install the latest version for your phone but it shows the version it installed only when it's finished...
Even if it has not installed the latest update then just connect the phone to your wifi/LTE and try the OTA updates again (could take up to an hour)
This is the safest way that will not void your warranty in any way but will delete your info (contacts, pics..etc. ) so do a backup prior
And if possible use a laptop with a working battery as even a 1 second glitch in the grid could cause the phone to get bricked
And if your phone is imported from China and the customization number is considered as an Internal Unit the only way you could get 7.0 or 8.0 is by flashing and another ftf file as the ones for Bell Canada or Rogers, there are actually some ROMs uploaded in XperiaBlog
there could be some in XDA but I have not search for any
Click to expand...
Click to collapse
Thanks so much for the reply...I discovered the version of Android installed on my phone is a version meant for Journalists/Reviewers/Commercial use, and can not be updated. I just got a refund for the 3-year warranty portion of my purchase after pointing this out to them. So after the 90 day warranty that came with it runs out, I'll be able to do anything I feel like with this device.
I'll be looking for a safe way to install 7.1.1 hopefully, and if not then 8.0. There seem to be less issues with 7.1.1, but there's really only one way to find out: when I start using it.
I'll definitely need a point in the right direction when it comes to that though. I understand Sony has an official flashing tool, and you have to unlock the bootloader (which is supported on my phone even with this version). But I haven't done it before and don't know how.