Database Develop

dead NFC and rear led on all roms

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.

[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

ROG Phone 2

Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.

What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.

This is a boot image issue

Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution

He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.

Hekp restoring ANY working ROM on my Z3C

Hey all. I have tried to get my old Sony Xperia Z3 Comapct to work again. At the moment the phone works, boots, and everything, but I can't make nor receive calls. So i want to restore the original ROM, or any other ROM that might work on my phone, but I am struggling with it.
First of all, FlashTool / EMMA / PC companion all recognize my phone as an Xperia M4 aqua, and when i try to flash the original ROM with FlashTool i get error: "the bundle does not match the connected device". I guess years ago I have flashed a wrong ROM but without ROOT.
I then managed to unlock the Bootloader (Took 2 tries), but rooting was more difficult. At last I tried to ROOT with this guide (Made for M4 Aqua) https://forum.xda-developers.com/m4-aqua/guide-rooting-xperia-m4-aqua-t3407215 and it worked (And confirmed working with FlashTool and App)
So far so good, now i wanted to install TWRP recovery, and that I have not managed to success with. I have flashed both Z3C newest and oldest version, flashed (With no problem = success) and same for M version (nicki), they all flash successfully, but I have never been able to boot into recovery, not with app/adb/vol op/down multiple times or by any other means
Any suggestion on what i can try?

Did you try restoring using Emma again after unlocking the bootloader?
If it still chooses the wrong phone model, does Emma allow you to manually choose the correct firmware?
You can find a tool to download any Xperia firmware manually here:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142
.

No IMEI, Wi-Fi mac

Hello. Noob here. A few years ago I bought used XZ1 Compact which had the green screen camera problem, and you couldn't receive calls. Seller also told me that bootloader is messed up. I flashed the phone with Emma, and everything started functioning. I used the phone for ~3 months, and one day it just lost almost every info about itself. IMEI, Wi-Fi mac address, bluetooth, baseband, prob gps as well. I started searching online for info and I came to conclusion that the chip maybe lost it's contacts with the board and that I would need to cook it in the oven. I have just put in the drawer, and took a backup phone, and didn't come back to look at it until few days ago.
I tried flashing the firmware with Emma, Flashtool, newflasher, TWRP with at least 10 different firmwares that I could find, flashed kernel, installed Lineage OS 18.1, tried to root the phone with Magisk 22 and confirmed that the phone was rooted with Root Checker 6.5, yet I wasn't able to get access with ES file explorer, adb, or Flashtool. I tried also Magisk 20, but the OS didn't see it was installed. I wanted to try things suggested in these 2 links https://nerdschalk.com/fix-empty-im...d-wifibluetooth-issues-restoring-twrp-backup/ , https://romprovider.com/repair-imei-qualcomm-snapragon/ , but since the phone wasn't really rooted I couldn't get the access to some files so couldn't really say if these how to guides would fix my problem. I did delete modemst1 and modemst2 through twrp, but that didn't help.
I probably lost attest keys in this whole process. I did manage to get Bluetooth to work, I think I got some baseband info in some of the instances, and Wi-Fi mac address moved from unknown to 02:00:00:00:00:00. I can read my (at least I think it's mine) IMEI with Emma, and Wi-Fi MAC address with Emma, Flashtool or adb (not sure which one).
Can someone tell me if there is any hope for this phone? I really hate throwing things that can be fixed in the garbage, but I think I'm loosing too much energy to try to save this phone from becoming waste.