Related
hey,
I had 4.2.2 in my 5503. Couple days ago I decided to upgrade it to 4.3 using flashtool, because there wasn't official 4.3 for my region yet . After that, I noticed my led and NFC are dead. Led isn't working (no flash when making pics, not working as a flashight). NFC unchecks just after when I click on it. Tried: downgrade, delete/rename usf (like in xperia z), many others official roms. tried fix and upgrade by SUS and SPCC. No changes. Also tried CM11 4.4, but still led is dead, NFC option can't be even marked. Now I'm on rooted 4.3. Any ideas how to bring them back? And no, backup doesn't exist
waw that's not cool.. do you erase the whole system when you flash?
Made in ZR
Yes. I thought it is better to have clean instal. Habit of installing roms on old phone. Everything else seems to work fine. I'm out of ideas.
hmm it's weird dude. well I suggest :
ensure that you bootloader is locked
do a fresh full flash with all wipes
do a reset in settings > backup & reset
then go into service menu > service tests > flash led
for the service menu, at the stock dialer, type : *#*#7378423#*#*
if it still doesn't work after this, I'm afraid this is hardware related.
Ilko said:
hmm it's weird dude. well I suggest :
ensure that you bootloader is locked
do a fresh full flash with all wipes
do a reset in settings > backup & reset
then go into service menu > service tests > flash led
for the service menu, at the stock dialer, type : *#*#7378423#*#*
if it still doesn't work after this, I'm afraid this is hardware related.
Click to expand...
Click to collapse
Did that many times. To have clear conscience I connected phone to another usb. formated, flashed .67 with wipes. After reset, in service menu led is still dead. connected to pc, updated with SUS to .569. and same story. I'm sure they were working before 1st flash and upgrade. If this is hardware problem, should NFC unchecks itself just after I click on it?
Ehh I suppose, I have to deal with it. There is no cure for my zr
ps. in /system/app/ I can see ncf.apk & nfc.odex only. That's it, right?
well I don't know mate, did you ever unlocked the BL? It may be drm related also
Made in ZR
NFC firmware needs update?
I got my ZR a few weeks ago, it came with 4.1.2 on it.
Straight away I hooked it up to PC companion and it updated to 4.2.2, during the first reboot I got a message on the screen for quite a while: "Updating NFC firmware"
I then had problems and thought it was due to 4.2.2, I downloaded & flashed a 4.1.2 ROM, once again, on the first reboot I got the "Updating NFC firmware" message.
Then I realized that the problems weren't due to 4.1.2 and flashed 4.2.2 again, once again got the "Updating NFC firmware" message.
This might not be much use to you but it seems to me that the NFC firmware needs to match the version of Android you're running.
Sorry, no idea how to update it manually, just thought it's something you might like to investigate.
Maybe start here ....
http://forum.xda-developers.com/showthread.php?t=2284166
Ilko, yes. BL was unlocked. I had thought, drm can be involved with it. If yes, I'm pretty ***. I don't see any other explanation. many official roms. repairs by sus and companion. checked in buildprop editor, and everything looks ok.
alan573819, when I bought mine it was 4.1.2 also. Couple weeks later upgrated it to 4.2.2. but I don't remember that NFC dialog. I just don't remember, so it doesn't mean I never had it it was long time ago. I know that topic. Believe me, I know them all I'm silent reader xda since se k800i. Always found answers without asking. Until now.. I had to register, because no1 have same problem. with z, there is problem only with NFC (no1 complains about led), and they can fix it by deleting usf. It doesn't work for me. anyway, on 4.2.2 I had no problems with NFC or led. everything worked perfect until I decided to upgrade it to 4.3 with flashtool.
my phone was unlocked, rooted, had .310, .67, .569 for at least 3 different regions, had CM11 4.4, was repaired and upgraded by SUS and Companion. No changes. It just has to have something with drm, because I don't believe that hardware was broken during update. drm can explain it. but.. that's weird if NFC and especially led has something to do with it.
okay, then did your ever relocked it? backed up TA? restored it?
Made in ZR
yes, I have relocked zr.
Like I said before, I didn't make any backups. Didn't expect any problems so I just wiped and flashed my phone. On the other hand- who expects them? . I can risk with my own phone. If I do something for others, I always do backups, double checks etc.
I am experiencing headphones detection problem with my Xperia Z1. Headphones are correctly detected first time after reboot. If I try to plug them in after that phone doesn't detect them any more (external speaker is used even after I've plugged them in).
I contacted Sony support and they suggested it might be Smart connect. I cleared it's cache. Didn't help. I disabled/removed it. Didn't help either. I downgraded to an older ROM (don't remember if it was 4.2 or 4.3) and it worked as expected. Then I downloaded fresh .ftf of latest rom. Same problem re-appeared. Tried with Kit Slim custom ROM (based on 4.4) and experienced same problem.
It is obviously a SW problem. Is there any app which would allow me to manually direct sound to either destination? I have SSH server running on my phone. Is there any way to do this via shell? Any API call that I could utilize? I have no experience with Android dev but I am SW engineer and I think I could implement a simple app like this if someone would point me in the right direction.
Thanks!
it's definitely something with smart connect. had the same issue some days ago...... unistalled smart connects updates and installed them again -> works!
Tried that already. Didn't help
I contacted Sony support again and they suggested to try PC Companion's repair feature. What will that do? How that relates to the fact I'm running a rooted custom kernel?
Thank you!
hm try to flash .157 with flashtool. after that flash trinity kernel via flashtool and fastboot -> should work like charm dont forger to save your data before that I did the same and it worked for me
Where could I download that?
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.
So I just flashed C6603_10.7.A.0.228_CE.ftf on my Xperia Z after getting tired of using CM12.
I'm not a noob, I built the FTF from an XperiFirm download and flashed successfully, and the phone starts up ok but after a few seconds of the "NFC Upgrading" overlay, the phone crashes and enters a bootloop following the exact same pattern.
I suspect I have a bad NFC chip, I've never used it anyway and I want to know if there's a way I can disable the firmware update for NFC so that I can escape the bootloop. Or else any fixes?
Any ideas guys?
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