Database Develop

[Q] Android 4.3 C5303 Update problem!

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.

[Q] No call sound after back to stock

Hi guys,
I know there are many similiar threads to this one and I'm sure I've read most of them. Either my issue is different, or, if the answer was in one of them, I was too stupid to realize it.
With my S4 Active GT-I9295 I had to go back to stock ROM for the Samsung S-Health and Gear related apps.
I came from spegelius' (absolutely awesome) Google Edition for SGS4A (int'l) v0.9.9.-od2 and flashed the Samsung Stock 4.4.2 with Odin (*). The procedure was: Flash -> Factory Reset -> Flash again to be absolutely sure all files are updated. Currently, I rooted the phone.
My problem persists:
After a reboot I (usually; not always) am able to make normal phone calls.
After some time (sometimes minutes, sometimes hours) I no longer have sound.
I do not hear ringing, the callee can't hear me, I can't hear the callee.
Same problem if I'm being called
Establishing a connection though works always.
Mobile Data is not affected.
WiFi works
Also observed after factory reset -> re-flash, only enter WiFi PW and Google Login Data -> try phone call
I know this problem often arises from a baseband/modem mismatch. So I investigated my CWM backup of the pre-installed 4.2.2 ROM.
That's what was pre-installed:
Bootloader: I9295XXUBMK3
CSC: I9295OXXBMK3
Modem: *I did not find the info in my backup*
This corresponds to the Romanian 4.2.2: http://www.sammobile.com/firmwares/download/22586/I9295XXUBMK3_I9295OXXBMK3_ROM.zip/
That's why I flashed the direct successor http://www.sammobile.com/firmwares/download/37083/I9295XXUCNI1_I9295OXXCNI1_ROM.zip/
PDA: I9295XXUCNI1
CSC: I9295OXXCNI1
MODEM: I9295XXUCNI1
I tried everything I could find online, nothing helped. I am really running out of ideas. Is it possible to go back to 4.2.2 to see if the problem persists?
I do have logcat logs of the radio module before and after the problem occured. But its thousands of lines. If it helps I can upload it!
Thank you guys for your help
(*): I did some intermediate flashing of several other firmware versions (especially different baseband / CSC versions of the same 4.4.2). But I assume this does not affect the result. I used Odin v3.07 & v3.09
Edit: PS: I still think that I might have the wrong CSC Version. I know the 4.2.2 PDA/CSC matches, but I am not from Romania. I'm actually from Germany. And what makes me wonder is that I cannot select the German Keyboard Style without downloading it first. I can't remember doing something similar after unboxing the phone and setting it up for the first time.

Are you aware of this thread?
http://forum.xda-developers.com/showthread.php?p=56955843
Bevare the Thanks Button

Thanks for the answer O-T!
Yes, I was aware of that thread. However, I never made it until here
http://forum.xda-developers.com/showthread.php?p=50787570
Although I did the things basically as described in that posts I have a new question:
Which country is relevant for the search on sammobile? I mean, do they ask me "Where do you live" or "For which country was your device produced?".
Edit: Okay actually they ask me for the 'product code', so it's probably the latter question.
I realized that my 4.2.2 PDA and CSC also match the French version. That would match the language of my original packaging. I already flashed the French 4.4.2 once but heard only noise when calling someone. So I gave up on that one quickly. But I'll give it another shot now.
Is it possible that I had a factory installation of the firmware for country A, and when I first registered with my local carrier I received a modem update OTA for country B?
That would really surprise me. But it could explain my issues, since there is no 4.4.2 for o2 Germany, i.e. I probably wouldn't receive another modem update OTA.
(I never looked into the carrier specific firmwares because I figured they are for sim-locked devices.)
If the above is true, I understand that the only option would be to somehow downgrade my device back to 4.2.2.
I know I'm asking a lot of questions that have been asked and answered elsewhere. But by now I tried so much and nothing worked that I'm really confused and need your guidance.

I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?

hyperion89 said:
I know I type too much, so a short summary.
Everything I tried so far didn't help, the stock ROM from sammobile.com doesn't help, currently I'm on 4.4.2 XEF (France)
I'm 80% sure I have the firmware for the correct country
From factory-side I definitely had an XX PDA and OXX CSC, so shouldn't all XX/OXX versions work, even if not the exact country?
What should I try next?
Is there a way to uniquely identify the country code from a backup of the /system or /data parition?
Click to expand...
Click to collapse
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement

JASONRR said:
I am not sure if you have done this, but one thing I always recommend is a phone factory reset from settings (not CWM/TWRP) when you are on stock firmware as this is known to correct a lot of issues caused mainly due to faulty partition / corruption. However beware of the fact that this will wipe your internal SD card therefore back it up before you do that.
Click to expand...
Click to collapse
Yes, I always did a factory reset. Most of the times I even flashed the firmware a second time after the factory reset. (This was recommended somewhere else.)
JASONRR said:
If you have flashed the correct firmware for your country & carrier (if it has a separate one) where you are using the phone, and done the above then I do no see any other issue than a faulty IC that requires replacement
Click to expand...
Click to collapse
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.

hyperion89 said:
Now that really helps me! Thanks. BUT: There is a seperate firmware for my carrier. However, I did not purchase the phone from that carrier. That's why I never tested the carrier specific firmware. Moreover, there is only the old 4.2.2 available, so I can't test it, since I cannot downgrade.
Click to expand...
Click to collapse
You can flash only the modem & non-holos from the 4.2.2 firmware and check

JASONRR said:
You can flash only the modem & non-holos from the 4.2.2 firmware and check
Click to expand...
Click to collapse
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?

hyperion89 said:
Tried it and it didn't work; completely crashed my Phone Application. It rang on the other side, but no conversation was possible. Is this because of the bootloader / modem mismatch?
Does anyone have instructions to safely downgrade to 4.2.2 again? Should I open another thread for this discussion?
Click to expand...
Click to collapse
Identify the bootloader version and Knox state:
http://forum.xda-developers.com/showthread.php?p=57332718
Knox is not a counter - it's a like a fuse.

Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?

hyperion89 said:
Hi O-T,
the bootloader is I9295XXUBMK3 and it does not yet have the warranty bit which I assume you mean by KNOX state.
Are there maybe any new ideas?
Click to expand...
Click to collapse
There's 3 stock 4.2.2 TW ROM I9295XXUBMK3 to choose for flash by Odin. All have different Germany CSC (Carrier Specific Code) - Generic, O2, T-Mobile. PDA=MODEM=I9295XXUBMK3 for all of them. Not sure if O2 or T-Mobile versions are locked, but they usually have operators bloat apps.
Remember to power OFF before entering download mode, flash ROM in Odin, factory reset.
https://www.samdownloads.de/download/i9295xxubmk3-dbt-4-2-2-germany/
https://www.samdownloads.de/download/i9295xxubmk3-via-4-2-2-germany-o2/
https://www.samdownloads.de/download/i9295xxubmk3-dtm-4-2-2-germany-t-mobile/
Your choice.

O-T I'm so sorry. My post from yesterday was a lie; I can't read my own OP. :crying: :angel:
I9295XXUBMK3 was preinstalled
Now I'm on I9295XXUCNH2, which implies 4.4.2 and makes a downgrade to 4.2.2 impossible (afaik).
Please note that I already tried the generic German (4.4.2) firmware. I never had operater bloat apps and I bought a simlock-free version of the device. Thus I never tested the o2 / T-Mobile ones. (I did, however, once flash the o2 modem over the generic 4.4.2, which turned out to be a bad idea).
I would love to extract the modem info from my CWM backup. The bootloader / CSC strongly suggest I have a French phone, but the modem would ultimately clarify that.
What is your opinion on trying a different custom-ROM? I never built one so I have no idea from where designers obtain their NON-HLOS and modem files. I know many don't come with any of those and require an already working ROM before flashing so these drivers can be kept. On the other hand, Darkman's StockyROM has an additional modem pack.... which, in my case, didn't help.
I simply cannot believe that it's a hardware issue. Everything worked fine until the update to 4.4.2 and new radio drivers should be thoroughly tested before distribution.

[Q] Z3 Compact (Hotspot Not Working after Lolipop) UK

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.

[Q] Unable to connect to mobile network after failed flash.

So trying to put CyanogenMod onto my phone, I haven't been able to use it for a while because all I had was a black screen. Late last year, I manage to get it up and running again. Everything worked fine until an hour after flashing the stock ROM onto my phone, the connection to the Mobile network disappears. I flash the phone again and the mobile network connection is only temporary. Anywhere between 20 mins to 3 hours. The phone can't scan for any mobile networks at all. Everything else seems to work fine but what's the point of a phone that doesn't make calls?
Any ideas or additional information you guys need to get this cellular-less cellphone working again?

sentouyousei said:
So trying to put CyanogenMod onto my phone, I haven't been able to use it for a while because all I had was a black screen. Late last year, I manage to get it up and running again. Everything worked fine until an hour after flashing the stock ROM onto my phone, the connection to the Mobile network disappears. I flash the phone again and the mobile network connection is only temporary. Anywhere between 20 mins to 3 hours. The phone can't scan for any mobile networks at all. Everything else seems to work fine but what's the point of a phone that doesn't make calls?
Any ideas or additional information you guys need to get this cellular-less cellphone working again?
Click to expand...
Click to collapse
maybe there's a messed up with the baseband. what FW currently you are?

Sony Xperia Z1 C6903 screenshots
yoorie016 said:
maybe there's a messed up with the baseband. what FW currently you are?
Click to expand...
Click to collapse
Baseband Version:
8974-AAAAANAZQ-10270054-61
Kernal version:
3.4.0-perf-gaee6e5a
[email protected] #1
Thu Oct 09:14:33 2014
Build number:
14.4.A.0.157
Phone Software Version:
1272-6084_14.4.A.0.157
File System Version:
GLOBAL-LTE_14.4.A.0.157
S1 Boot Version:
1270-3115 S1_Boot_MSM8974_Rhine1.2_LA1.04_19
ETS Software Version:
1272-5079_19
Customization Version:
1276-7937_R4C
Active Customization:
1276--7937_R4C
LTA version
/lta-label/1278-1097_7-elabel-c6903-row.html
Content Version:
PA40
Type Number:
PM-0450-BV
Touch Firmware Version:
d
I was going screenshot but I haven't made enough posts to be able to do that so I hope I wrote down the information you needed.

Same here
Hey,
My Z1 has also been having a mobile connection issue for a while now.
Scans for networks, finds some of them, but cannot connect to any.
Flashed every stock F/W i could find, tried several working SIM cards, did a TA restore.
A few days ago I replaced the chip with the speaker, radio and antenas on it ( 13 $ from china ).
nothing.
Any ideas are welcome.
Thanks guys

sentouyousei said:
Baseband Version:
8974-AAAAANAZQ-10270054-61
Kernal version:
3.4.0-perf-gaee6e5a
[email protected] #1
Thu Oct 09:14:33 2014
Build number:
14.4.A.0.157
Phone Software Version:
1272-6084_14.4.A.0.157
File System Version:
GLOBAL-LTE_14.4.A.0.157
S1 Boot Version:
1270-3115 S1_Boot_MSM8974_Rhine1.2_LA1.04_19
ETS Software Version:
1272-5079_19
Customization Version:
1276-7937_R4C
Active Customization:
1276--7937_R4C
LTA version
/lta-label/1278-1097_7-elabel-c6903-row.html
Content Version:
PA40
Type Number:
PM-0450-BV
Touch Firmware Version:
d
I was going screenshot but I haven't made enough posts to be able to do that so I hope I wrote down the information you needed.
Click to expand...
Click to collapse
bahkata said:
Hey,
My Z1 has also been having a mobile connection issue for a while now.
Scans for networks, finds some of them, but cannot connect to any.
Flashed every stock F/W i could find, tried several working SIM cards, did a TA restore.
A few days ago I replaced the chip with the speaker, radio and antenas on it ( 13 $ from china ).
nothing.
Any ideas are welcome.
Thanks guys
Click to expand...
Click to collapse
You both try first to restore TA and relock your phone. then reflash stock .157 FTF. Or maybe, flash a custom kernel that match to the current FW you are running. if it is based on .157, look for custom kernel that runs at .157

yes, dear tried all the flashing, TA and custom kernel crap. got fed up with it already
I never went outside stock firmware, tho. I saw that OP was trying CM before it happened.
and my phone used to be carrier locked, but I unlocked it with a code about 2 years ago. Could that be acting up? I am not familiar with the low-level stuff

Yep... I did all that flashing too. All started with that failed CM flash.

Sounds like a failed modem flash or baseband
Sent from my D2303 using XDA Free mobile app

I have just noticed when I dial *#*#6463#*#* to get the phone menu up and selected the 3 vertical dots, under select band, I only have the USA bands. Where did all the others go? How do I get all the others back?

cryptoncore said:
Sounds like a failed modem flash or baseband
Sent from my D2303 using XDA Free mobile app
Click to expand...
Click to collapse
Would that not be fixed by a stock FTF flash?

bahkata said:
Would that not be fixed by a stock FTF flash?
Click to expand...
Click to collapse
Normally it would, if you choose a Pure Stock (with no additional stuffs). i experience it also one time. I was on LB then installed the ParanoidAndroid (CM Based ROM) then i lose my network. i just relock my BL, flash the custom kernel.

yoorie016 said:
Normally it would, if you choose a Pure Stock (with no additional stuffs). i experience it also one time. I was on LB then installed the ParanoidAndroid (CM Based ROM) then i lose my network. i just relock my BL, flash the custom kernel.
Click to expand...
Click to collapse
I never unlocked my BL tho. It is still locked and I am flashing Official Release ROMs
I guess I'll just send it for repair service. hope they can unravel the mistery

bahkata said:
I never unlocked my BL tho. It is still locked and I am flashing Official Release ROMs
I guess I'll just send it for repair service. hope they can unravel the mistery
Click to expand...
Click to collapse
Just flashed a stock ftf, let see if it works.

yoorie016 said:
Just flashed a stock ftf, let see if it works.
Click to expand...
Click to collapse
Come on man. I know you are trying to help but read the previous posts. I have flashed more than 20 stock FTFs, in the past weeks. Today even flashed the lollipop one. No change.

bahkata said:
Come on man. I know you are trying to help but read the previous posts. I have flashed more than 20 stock FTFs, in the past weeks. Today even flashed the lollipop one. No change.
Click to expand...
Click to collapse
Hey man, sorry i forgot to read my own comment about flashing the FTF. Can you try to insert another SIM in your phone? or inserting your SIM to another phone? (Maybe your network provider has the problem?) Have you tried also using the PC Companion? or the Flashtool for Xperia? though you need to unlock your phone if your gonna use the Flashtool for Xperia, but you can relock it later.
Let's try to do anything we can do before you let go some of your cash.

yoorie016 said:
Hey man, sorry i forgot to read my own comment about flashing the FTF. Can you try to insert another SIM in your phone? or inserting your SIM to another phone? (Maybe your network provider has the problem?) Have you tried also using the PC Companion? or the Flashtool for Xperia? though you need to unlock your phone if your gonna use the Flashtool for Xperia, but you can relock it later.
Let's try to do anything we can do before you let go some of your cash.
Click to expand...
Click to collapse
Good ideas, bro Sadly i tried all of them ( except Flashtool for Xperia, since my bootloader is not unlockable ). Several SIM cards, various operators in 2 countries. As I mentioned in my first post, I even went as far as ordering a new radio unit ( a chip that houses the speaker and radio + two antenas ) and swapping it in. Did all possible factory resets. retored TA ( even tho my IMEI and Baseband show up ok ).
2 years ago when I had to carrier unlock my phone, I did it with a code and it worked alright for a very long time. This is the only thing I can think of that might be wrong with it, but I tried a SIM card from the operator it was originally locked for and its the same.
It detects the SIM card, it scans for networks normally, but when I try to connect manually to a network it says "unable to connect to network, check if sim card is in or you are allowed bla bla" . Automatic network selection gives no result

Updating issue

hello everybody , So, i bought this XZ2 a while ago on some one that labelled it as "Slightly used" and been using it for a while now and its been working okay apart from the fact that it randomly overheats some times . I think the phone is refurbished.
The other Big issue is that ive been stock on the same software version since i got it wich is : 51.1.A.2.213. The update manager finds an update wich is : 51.1.A.3.159 and downloads it normally but then faills installation at 99% and tried again maaany times always the same. i also tried with Xperia companion and its the same
So is there any sollution to the problem , i note that i dont have much knowledge on software and i dont want to accidentally brick the phone

Harper55 said:
hello everybody , So, i bought this XZ2 a while ago on some one that labelled it as "Slightly used" and been using it for a while now and its been working okay apart from the fact that it randomly overheats some times . I think the phone is refurbished.
The other Big issue is that ive been stock on the same software version since i got it wich is : 51.1.A.2.213. The update manager finds an update wich is : 51.1.A.3.159 and downloads it normally but then faills installation at 99% and tried again maaany times always the same. i also tried with Xperia companion and its the same
So is there any sollution to the problem , i note that i dont have much knowledge on software and i dont want to accidentally brick the phone
Click to expand...
Click to collapse
If you have the original packet with the phone name you see the hardware revision somewhere.
At least revision 2 is okay.
Revision 1 was not available for sold.
You can use xperifirm to download the latest firmware and newflasher v13 to flash the phone in download mode.
You'll find the download mode manual in the TWRP thread.
Feel free to flash the phone country you want but maybe a different firmware needs a full wipe.
And what's important, remove the userdata.sin if you don't want to full wipe the phone.
But a full wipe may fix your bugs.

MartinX3 said:
If you have the original packet with the phone name you see the hardware revision somewhere.
At least revision 2 is okay.
Revision 1 was not available for sold.
You can use xperifirm to download the latest firmware and newflasher v13 to flash the phone in download mode.
You'll find the download mode manual in the TWRP thread.
Feel free to flash the phone country you want but maybe a different firmware needs a full wipe.
And what's important, remove the userdata.sin if you don't want to full wipe the phone.
But a full wipe may fix your bugs.
Click to expand...
Click to collapse
Thanks a lot for the answer. no risk to brick the phone if i do a mistake or something goes wrong ? i want to update the phone to Pie should i look directly for the Pie update ?

and i also read that it was possible to fix it by using the "repair" Function on Xperia companion which way should i go for ?

Of course you can try the repair function.
About the brick.
The worst thing happen is that you need a full wipe to fix a bootloop.
But btw I recommend a fullwipe after pie upgrade in your case and Everytime if you switch an entire Android version

Maybe your phones bootloader have been unlocked.
Then it will fail on OTA and also in Xperia companion.
You can se the status if you put this in the dailer *#*#7378423#*#*
Skickat från min H8266 via Tapatalk