Database Develop

Xperia T - restarts after flashing new firmware

Hey.
This is my first thread so welcome all. If this issue was fixed or if there is similar thread please close it down.
I have Xperia T that was branded by Vodafone DE. I updated it once from the standard firmware (I think it was the 4.1.2 android) to 4.3 (9.2.A.0.295), everything was fine, except that on two occasions the screen just could not be forced to turn on. Everything was working, sound, calls etc. I just had to hard reset it to enable the screen. Once when I was receiving call I could not answer it, the screen was jumping, blinking and I could not do anything with it. Hard reset helped again. I thought that those were bugs from the 9.2.A.0.295 but now I'm not so sure.
I downloaded the newest version of flashtool and the UK 9.2.A.1.199 firmware from this site, not branded, not modified. I unlocked the phone using the instructions on the sony site but since i didn't wanted to root the phone I locked it again. I flashed the mentioned UK firmware without problems and then the phone started to randomly reset itself. Usually it is getting hot under the camera and it resets mainly after using facebook or basically internet. It mostly resets when my phone is in the pocked. I tried using pc companion's repair option, used the firmware from Italy, Greece and almost all 9.2.A.1.205 except the Bond release. I think it's not the firmware, I've reverted to the 9.2.A.0.295 to no success. There are from one to six resets a day at random hours. Did someone had this problem? Is it related to the firmware flashing or could be just a coincidence and my xperia is dying from motherboard\battery failure? I replaced my sim card with new one. It also happens with or without the sd card.

Hi, the most common restart's are:
a) Sim card ( you change that)
b) Software ( you change that)
c) Very rare SD card ( try to do that) get the SD out end boot the phone. Edit .. you all ready do that.
d) End must common is the Battery ( first try de c) version ,then if fail , you need to buy a new battery end try.
e) motherboard (well new phone? )
This not exactly the order, but from i have read , point d , b ,a , are the order .
So Good Luck.:good:

I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.

Nekris said:
I think it could be the battery or the board, since it happens on all firmwares. The thing I would like to know is that using flashtool for an example could somehow damage the phone or the battery? I never found any info on this.
Click to expand...
Click to collapse
I have heard that upgrading to 4.3 could actually damage the battery. So yes, it is possible.
I don't know the reason tho
Sent from my Xperia V using Tapatalk.

[Q] Mobile network crisis after flash

So, I'm having some issues regarding my recently flashed XSP C5302.
Model: C5302
Android Version: 4.3
Baseband version: 8960A-AAAAATAZQ-40031007-18
Build number: 12.1.A.1.201
I'm on locked BL.
Thing is, I flashed it as soon as I got my hands on it due to that annoying flickering screen, tried to downgrade it to 4.2.1. It was the first time I did that, so I went through many tuts to get it right.
At first I flashed a .254 rom, and when I entered the About screen, model had switched to C5303. What I did was follow DoomLord's guide to root it, instal CWR and flashed a deodexed .254 rom for C5302(this one: http://forum.xda-developers.com/showthread.php?t=2423625). Everything back to normal.
But then I noticed my mobile data wasn't working, so I thought it may have been fault of the deodexed rom. Sooo, I upgraded it AGAIN to 4.3 using PC Companion, just to find out that the mobile issue was not having the APN correctly configured. Sigh.
And well, I'm now stuck again on 4.3, but at least my mobile data package is working. However, it's extremely slow. I mean, I can see the H and H+ icon, but even on H+ it takes ages to send messages and connect. At first I wondered if the baseband had anything to do with it, but when I flashed the rom I checked everything but Kernel and System, so...
So my question is, is it possible that I did something that "damaged" my mobile data connectivity? If so, could somebody please suggest any solution? I must say, my service provider sucks, so it could be their problem too, and I'm just here crying over spilled milk with no reason at all.
Thanks in advance!

Probably your service provider - I must have tried 100's of custom roms and whilst some have meant that data didn't work, this was caused by buggy software, never damage to the phone.

Parkside said:
Probably your service provider - I must have tried 100's of custom roms and whilst some have meant that data didn't work, this was caused by buggy software, never damage to the phone.
Click to expand...
Click to collapse
Yes, I'm pretty sure too, but oh I was so damn worried! Thanks

[Q] Possible to restore stock firmware w/o root or unlocked bootloader?

Hey Guys,
So my brother recently received his Sony Xperia Z1 on a two year plan. When he received it, it was running stock firmware (android 4.2) and it was working completely fine. He then, using Sony PC companion, updated his phone to the latest official firmware (kitkat). But afterwards, his phone's microphone didn't work. He then called both Sony and his carrier asking what to do to fix the issue and they told him to restore the device, which he did, but that did nothing as his phone was still on kitkat and still glitchy.
So now the only option for him is to send it in for repairs, but that will take at least a month, and he needs the phone in the meantime. So brilliant people at xda, is there any way for him to restore his firmware to android 4.2 or another official firmware in order to fix the problem without rooting or unlocking the bootloader. If he unlocked the bootloader it would mean that he would never be able to send it in for repairs, which is vital in case it is not a software problem and a coincidence that the microphone broke at around the same time.
After the problem is fixed, I'll probably install cyanogenmod on it for him but he would not like to do that until we know we wont need to send it in for repair.
Thanks!

This is a guide to root the phone, it includes downgrading the phone... So you could just go ahead and do that step only. Good luck.
http://forum.xda-developers.com/showpost.php?p=45464115&postcount=2

NFC not working on any ROM after root

Hi guys. I am dealing with some serious problems with this Xperia Z1.
First of all my friend gave me the Z1 of some dude. That guy was modifying it - rooting, bootloader and everything - and said that NFC just stopped working. He tried so many roms and different configurations and nothing worked.
Finally he just ended up with returning to stock. And NFC still didn't work.
Then I gave it a try. Same procedure - root, unlock, custom recovery, custom roms, kernels etc.
Nothing.
I've read about renaming the usf folder to usf1 to get the NFC to work.
Nope. Phone just creates his own usf folder after reboot. I deleted that folder multiple times and it always comes back.
Finally I got to a point where I must force shutdown the phone because it just won't shutdown on its own or reboot.
Wifi stopped working on KitKat - on Lollipop the switch just hangs for about 30 seconds and then turns on.
What is also interresting I can't enter the Configuration option in service menu because it hangs and force closes.
Model is Xperia Z1 6902
Help me, please. I have no idea what to do.

Hi,
Seems something is wrong with the device wireless. Since neither the WiFi, nor the NFC is working, my S4 already showed a similar problem and was solved flashing another modem, have you tried flashing another baseband on your Xperia Z1?
All the best,
~Lord
Sent from my SM-G920I using XDA-Developers mobile app

It turned out that I was flashing firmwares for a wrong model. It's not 6902 but 6903...
Fortunately I got rid of all the problems except the NFC ofcourse.
Any ideas?

v-valdy said:
It turned out that I was flashing firmwares for a wrong model. It's not 6902 but 6903...
Fortunately I got rid of all the problems except the NFC ofcourse.
Any ideas?
Click to expand...
Click to collapse
Hi,
Can you give me more details about how is the NFC behaving? You press the button and it doesn't turn on? It turns on but it doesn't works? Because since the other wireless features are working I wonder if it's a hardware problem.
All the best,
~Lord
Sent from my SM-G920I using XDA-Developers mobile app

It's not possible to turn on the switch. But I don't mess with this bullcrap anymore; the guy took back his Z1. Probably it's just a hardware problem. Case closed.

Xq-at52 not certified devixe

Hi everyone,
Need some serious help please,
I have a xqat52, bought in January 21.
In the UK, on three the handset would not go into 5G.
After reading up, I decided to flash xq-at51 successfully to the UK rom. Everything was working lovely...
Received OTA updates and never had issues with updates or Google.
Device was certified and google pay and bank apps work fine.
2 weeks ago I received ota update and since then my device is no longer certified.
1 week ago received another ota now build 58.1.A.5.507 and device is still not certified.
I tried experia companion full repair with no luck, still same issue.
I sent the handset to Sony Uk for repair, and they factory reseted it back to stock XQat 52, but the device still shows as not certified and bank app and google pay no longer works,
at this point I am thinking in rooting my device and use magisk....
my bootloader is locked, never unlocked (i checked and so did Sony) but I am able to unlock it...
what do you guys think I should do, I want it to be a XQat51 for Uk and have it certified or rooted hidden.
any advise will be really appreciated, and this will bring back memories of rooting android when i had my HTC and where it all started
Thanks in advance

Update.
Went the rooted way. Not looking back.
Not so simple, but we'll worth it
Plenty of google search.
Android Kitchen which I didn't use before
Didn't really have a choice to get my 1ii working properly again.
All repairs / flash stock did not help no matter what I flashed UK / eu dual Sim / single Sim
Back to full stock from Sony HK version still didn't help
My android is now how I want it.
Shame on Sony for not helping and still waiting for a response.
Google store device now certified again.
Google pay working again.
All banks working
Fingerprint working
Netflix l3 not l1 but I don't use anyway.
Cinema Pro and photo Pro working
4k creator mode and Sony dynamic vibration working
Full root permission and able to customise like I use to when I 1st started with kitkat
Android is going down the apple way unfortunately, not so open anymore...
Good luck to anyone doing the same,

xdamanu1000 said:
Update.
Went the rooted way. Not looking back.
Not so simple, but we'll worth it
Plenty of google search.
Android Kitchen which I didn't use before
Didn't really have a choice to get my 1ii working properly again.
All repairs / flash stock did not help no matter what I flashed UK / eu dual Sim / single Sim
Back to full stock from Sony HK version still didn't help
My android is now how I want it.
Shame on Sony for not helping and still waiting for a response.
Google store device now certified again.
Google pay working again.
All banks working
Fingerprint working
Netflix l3 not l1 but I don't use anyway.
Cinema Pro and photo Pro working
4k creator mode and Sony dynamic vibration working
Full root permission and able to customise like I use to when I 1st started with kitkat
Android is going down the apple way unfortunately, not so open anymore...
Good luck to anyone doing the same,
Click to expand...
Click to collapse
I'm glad for you.
I just bought a second hand XQ-AT51, and didn't noticed when I bought it that the Wi-fi and Bluetooth are not working.
And also that the bootloader is unlocked, and it seems that fast charging is not working.
Everything works fine as far as I see (camera, features).
I don't know what the previous owner did.
I didn't find anybody saying about Wi-fi and Bluetooth not working after Bootloader unlock/root Xperia 1 ii.
I tried locking bootloader and Xperia Companion software repair, same version 58.1.A.5.507 (as I see the latest) before repair and after.
Nothing changed.
Then I unlocked the bootloader, flashed twrp as recovery (probably not necessary in my case) and flashed the stock software with Flashtool, latest (the same as before) from xperifirm. But I got some messages some things didn't flashed (didn't save the message).
Still the same.
Do you have any idea about DRM keys needed (as I know older Xperias pretty much lost the camera without backup and restore to some files)
Or do you have any "spare" backup files that I might need and work for different devices?
Thanks!

n8f said:
I'm glad for you.
I just bought a second hand XQ-AT51, and didn't noticed when I bought it that the Wi-fi and Bluetooth are not working.
And also that the bootloader is unlocked, and it seems that fast charging is not working.
Everything works fine as far as I see (camera, features).
I don't know what the previous owner did.
I didn't find anybody saying about Wi-fi and Bluetooth not working after Bootloader unlock/root Xperia 1 ii.
I tried locking bootloader and Xperia Companion software repair, same version 58.1.A.5.507 (as I see the latest) before repair and after.
Nothing changed.
Then I unlocked the bootloader, flashed twrp as recovery (probably not necessary in my case) and flashed the stock software with Flashtool, latest (the same as before) from xperifirm. But I got some messages some things didn't flashed (didn't save the message).
Still the same.
Do you have any idea about DRM keys needed (as I know older Xperias pretty much lost the camera without backup and restore to some files)
Or do you have any "spare" backup files that I might need and work for different devices?
Thanks!
Click to expand...
Click to collapse
I flashed xq-at51 from Xperia with flasher.
I don't think drm will affect Bluetooth or WiFi?
Mine are lost anyway, once bootloader unlocked its gone! I was prepare to loose them.
Connectivity issues you mention I
Never had that problem despite locking unlocking bootloader and flashing various rom xqat52 HK or Asian and xq-at51 UK and EU.
Might be something else you are experiencing on the phone directly , run a sony test through the app "support" it has a connectivity section. Might give you a better idea before flashing anything else.
I think you can also do it via phone codes *#.......
Google it, it will enter service menu, you can test your handset this way too.

Thanks for the suggestions, I didn't think of trying Support.
But forgot to say, in the Settings at About it says MAC address unavailable for both Wi-fi and BT.
With code *#*#4636#*#* it says Wi-fi Mac address 02:00:00:00.....
As I found some older forums for other devices with about the same issue and being from flashing not proper firmware, I honestly don't know what's going on, since I flashed the stock firmware again, maybe some files are not flashed again because I'm flashing over the same firmware.
Hopefully, I will find a solution.

n8f said:
Thanks for the suggestions, I didn't think of trying Support.
But forgot to say, in the Settings at About it says MAC address unavailable for both Wi-fi and BT.
With code *#*#4636#*#* it says Wi-fi Mac address 02:00:00:00.....
As I found some older forums for other devices with about the same issue and being from flashing not proper firmware, I honestly don't know what's going on, since I flashed the stock firmware again, maybe some files are not flashed again because I'm flashing over the same firmware.
Hopefully, I will find a solution.
Click to expand...
Click to collapse
Latest ver of flasher ? V52
With flasher, if I remember correctly
I chose command a android reboot
N to dump (did once the 1st time as a backup)
I did choose partition persist
No to everything else.
Maybe try and repair with companion make sure it gets back to factory stock rom with correct variant.
Do a factory reset within the phone
(I know I did several, after each flash)
Then reflash with flasher, also might be worth redownloading a clean rom and put in a new folder, so it's clean and not changed.
Add flasher (latest) to that folder and do another clean install.
The rapair tool from Sony failed few times on me, not sure why, but sony software somehow still knew my Xperia 1ii was originally a xq-at52 and would not repair / so I had to flash using flasher xq-at52 stock rom, then repair then flash back using flasher to xq-at51.
Sony repair if successful is your best bet... Once repaired properly you can do it again and again.

I just realised you mention flash tool, use flasher. Exe no issues...
Download from Xperia firm your rom. (always the same or higher)
Downloader flasher (latest)
Few files to copy straight into the same folder as the extracted Xperia firm folder.
Run the flasher. Exe
Follow instructions
Should flash everything correctly.
I bootloop mine and bricked few times...
Flasher rebooted it every time.

xdamanu1000 said:
I just realised you mention flash tool, use flasher. Exe no issues...
Download from Xperia firm your rom. (always the same or higher)
Downloader flasher (latest)
Few files to copy straight into the same folder as the extracted Xperia firm folder.
Run the flasher. Exe
Follow instructions
Should flash everything correctly.
I bootloop mine and bricked few times...
Flasher rebooted it every time.
Click to expand...
Click to collapse
Thanks, I didn't knew about newflasher.
But I see that it's skipping persist (flashtool was also skipping persist)
Skipping persist_X-FLASH-ALL-2389.sin
And also
Skipping partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin
And I read somewhere that it's skipping .sin that are not matching.
But maybe if I flash them I will solve my issue.
As I see older versions have the options to write or skip. Did you write it? If I write it I will lose attest keys? Because at mine it says Android Attest Key Provisioned after relocking the bootloader, but was Not Provisioned before.
I guess I have to backup persist.sin if I want to flash it and for that I need to root.
Do you think that flashing persist might solve my issues? Or it will give me more issues