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.
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 Recently began to have issues with my Z1 (Google frameworks and gapps were wrecked(dont ask how)) anyways long story short it ended up bricking itself for a moment, i eventually got it working through flashtool and flashed an old firmware as a result [.108] anyways since the new firmware had taking my phone, ive been getting issues with wifi and coverage has gone to hell. anyone got any ideas, it doesnt seem to be firmware related as i've tried a few at the time of writing...possibly something to do with 3g-4g stuff?, (Apologies for bad formating and gramatical errors currently writing this from a ps4 lmao)
Go to Settings and About phone and see the "Baseband" if it says "Unknown" then flash this and are you sure you are flashing the right FTF? look for the right firmware.
So I think I messed up my phone.
TL;DR: Messed up phone by removing stock rom, Costume roms don't work except 1 and in that one IMEI is set to zero and I can't connect to any network.
several month ago I had the stock xperia z Lolipop and made a decision to root the device. I unlocked it's bootloader and did the rooting... all as planned. about a month later my phone started acting funny, so I decided to reset it, the problem is I had installed TWRP and as noob in using the app, I accidentally wiped the entire device. I thought I had bricked the thing so I left it aside.
I had been using an older phone as replacement until last week when I thought I'd give the Z another chance. I looked around this forum, found a bunch of stuff, tried a lot of roms and after failing to make 4 roms work (Cyan nougat, Cyan MM, Costumised sony 5.1.1 and a stock one I found here) I managed to find a fifth one that worked (http://forum.xda-developers.com/xperia-z/general/android-5-1-available-yuga-pabx-t3054304). I always followed the tutorials but I may have done a lot of mistakes... for example I'm not even sure what kernel is and if I needed to change it for any of the roms or if I needed to like wipe the entire system or not before flashing ( I did all the time), and what about rooting? does the system require a previous rooted rom to install new ones? don't we simply format the entire device?.
Now the major problem of the working rom is that my phone can't connect to it's simcard network, the simcard is working since it requires pincode on start and the phone can find the networks by manual search, it simply gives an error "network XXX unavailable". I looked around and saw that my IMEI is set to all zero's in the phone about section. this could be unrelated to the network problem... but I don't have much expertise in these stuff.
So right now it seems like I can't install any other roms (they won't even start up, most get stuck during boot) and the only one I can install doesn't give me network access.
Any Ideas?
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.
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